Default Technical Settings

The second sub-object managed through the transaction /BTR/MDR is “Defaults for Technical Settings” this screen contains two main sections. The first section “Defaults for Technical Settings” allows to set default values for a specific MDR program. Once set, these values will always appear on the Technical Settings’ sub screen for that program see Technical Settings under Running MDR Programs for more details.

The second section “Technical Settings Access” we will explore in more detail.

Background Program

NOTE: This functionality requires “Wait for run to complete” to be set.

This option supresses the default display of the Run History screen after completion of an instance run. This is a useful feature that allows an MDR program to be called from another program without interrupting the latter with the Run History display.

The input field “Check for completion (in sec)” allows to set in seconds a time interval in which the parent job of a running MDR instance will wake up and check if all child parallel processes have completed. The default wake up and check time is 30 seconds which is suitable for very long running programs but not for speeding up, say, web services where every second counts.

Lock Technical Settings

This options allows to lock all input fields for Technical Settings. This is useful if when a program can repeatedly run with the same default values and users should not change those values. When this option is set, the Expert Mode in the Run History will be locked as well.

This restriction applies at program level and not at user level. That is, once set the Technical Settings will be locked for all users. Restrictions at user level can be implemented with the MDR enhancement spots (see MDR Enhancement Spots document).

Lock Expert Mode

This option is similar to “Lock Technical Settings”. The only difference is that on the Technical settings screen only the input fields under “Distribution” are locked. This allows the user to change settings like label name while protecting the more critical job distribution section from potential misuse. This option applies at program level as well. Restrictions at user level can be implemented with see the MDR Developers Guide Authority Checks