MPE

Job report

Database

The job report is managed by AE. When the job has been processed, the Automation Engine takes the process protocol which has been stored on the agent computer and stores it to the AE databaseA database is an organized collection of data including relevant data structures..

File

The job report is managed by AE. After the job execution, the process protocol is available as a file in the target system.

On error only

In case of job interruption, the job report is saved in the AE database and/or a file in the target system. This is only available when "Database" and/or "File" have been selected.

Runtime options

The host attributes defined here are assigned to the command "JOB" as a parameter. They form the job card of the MPE job.

Job name

Specification of a name under which the job should be executed.
A maximum of 8 alphanumeric characters are allowed. The first must be a letter.

Queue

Selection list for the queue in which the job should run which determines the execution's priority. "BS" stands for the highest, "ES" for lowest priority. The default value is "DS".

The administrator administers the queue in the variable UC_MPE_QUEUE. A maximum of 8 characters is allowed for user-defined queues.

Input priority

Specification of the input priority (INPRI). This value is used for the logon of the job.

A value between "1" and "13" can be use for Input Priority. The default value is "8".

Jobs must be prioritized so that they are above the current job fence set by the system operator. If a value is specified which is less than or equal to this, access is denied.

HIPRI

Check box for activating HIPRI.

HIPRI can be used to overwrite the job fence or the limit for jobs set to be executed. The authorizations System Manager (SM) or System Operator (OM) are required.

Other

Additional parameters for the "JOB" command.

A maximum of 256 characters are possible. The parameters must be specified according to the syntax..