|
|
|
|
|
If multiple DO SYSOUT (or SYSOUT/DO SYSOUT) operations are not specified for the same FROM class, the order in which the operations are performed is not significant.
However, if different DO SYSOUT (or SYSOUT/DO SYSOUT) operations affect the same FROM class, or if multiple operations are specified without a FROM class, the order and method of implementation is significant.
Control-M merges different operations for the same FROM class into a combined instruction to JES. Likewise, Control-M merges different operations without a FROM class into a combined instruction to JES.
Operations without a specified FROM class treat the entire held sysout as a whole unit, and are therefore not merged with sysout handling requests for a specific FROM class.
JES does not necessarily process multiple SYSOUT handling instructions in the order they are issued by Control-M. Therefore, the processing results can vary if the merged instructions to JES include both FRM equals a specified class and FRM equals blank.
BMC therefore recommends that you do not include in a job scheduling definition both "FROM class" and "no FROM class" sysout handling instructions that become operational under the same situations.
When Control-M merges a set of operations into a combined instruction, some operations override or cancel other operations, and some operations are performed along with other operations. This is described below.
Parent Topic |