The processing section of a rule that responds to an EOS event executes in the address space of the job or task whose step has ended. Therefore, any type of logic that could possibly suspend the processing of an EOS rule should be performed by scheduling an OPS/REXX program to a CA OPS/MVS OSF TSO, TSL, or TSP server.
The active JSCB in the ending address space is the region control task, or the initiator. This causes the ACCOUNT, EXECPGM, and MODULE operands of OPSINFO to return the values for the RCT or initiator program, rather than the application program that is ending.
Because SMF may generate more than one type 30 record for reach EOS event, only the first record containing all the job data that only occurs once is used to generate the EOS event. The additional records containing repeatable sections such as EXCP counts for every data set are not visible to the EOS rules.
|
Copyright © 2014 CA.
All rights reserved.
|
|