Skip to Content

EOS

The End-of-Step (EOS) event occurs whenever an address space changes steps.

An additional EOS event occurs when the address space ends; for example, at the EOJ (End of Job) event.

Before EOS events are generated, you must have IEFACTRT SMF exits implemented and generate SMF Type 30 records. See the Customizing-BMC-AMI-Ops-Automation-after-installation for more information about implementing the EOS event type.

Related topic

Special-event-types

To write Rules that fire for this event type, you should evaluate the contents of the following event variables to determine what event data is available to you for automation purposes:

See BMC-AMI-Ops-Automation-supplied-EVENT-variables for more information about these variables. For an EOJ event, the event variables IMFJSNUM, IMFJSTEP, IMFJSCPU, and IMFJCAN will have slightly different values.

There is some overlap between the EOM and EOS events for STC and TSO address spaces. The exception is that EOS events do not always occur. For example, if an address space ends by way of the SYSPROG Services commands FORCE or EXIT, an EOM event is generated, but an EOS event is not generated.

The IMFTEXT event variable contains the following information when the event fires:

 CE0330I  jjjjjjjj JS: ssssssss PS: pppppppp CC: ccccc SNum=nnn
jjjjjjjj: Job, STC or TSO address space name.
ssssssss: Job Step name, or N/A
pppppppp: Proc Step name, or N/A
    cccc: Condition code - FLUSH, nnn (return code), Abend code
          (preceded with 'S' or 'U'), or N/A.
     nnn: Step Number, zero for end of job.

The CE0330I message is not written to the BBI Journal unless Journal ==> YES is specified in an EOS Rule.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI Ops Automation 8.3.01