The modes to start up job processes include the trace mode and job object mode.
Job object mode is the default mode when performing a new installation or upgrading from an earlier version.
The differences in the operations of trace mode and job object mode are listed below:
Trace mode
If a job (parent and child processes) throws an exception, a message to that effect will be displayed in the previous log.
If a JCL job throws an exception, normal steps will be omitted and only the final job step specified as "only" will be executed.
If a child process of a job throws an exception, the exception code of the child process will become the completion code of the job.
Job object mode
Even if a job (parent and child processes) throws an exception, no message to that effect will be output.
If a JCL job throws an exception, normal steps will be executed but the final job step specified as "only" will be not executed.
If a child process of a job throws an exception, the completion code of the parent process becomes the completion code of the job.
The -nt option (non-trace mode option) of the qsub command is disabled.
Applications that use job objects cannot be started.
The startup mode of a job process can be changed for individual subsystems. If a new subsystem is created, it will inherit the startup mode of Subsystem 0. Refer to "Defining the System Operating Information" in the Systemwalker Operation Manager Installation Guide for details on how to change the startup mode for individual subsystems.
