EOM

An address space ends when a Started Task (STC) or TSO User (TSU) is stopped, canceled, or ends abnormally (abends). It is important to note that an address space does not end when a batch job terminates. It ends when the initiator is terminated.

To create Rules for this event type, you should evaluate the contents of the variable IMFTERMT. See List of MainView AutoOPERATOR-supplied EVENT variables for more information about this variable. The event variable IMFJSPGM is not applicable for the EOM event. 

For EOM events, the determination of whether the address space terminates as NORMAL or ABNORMAL depends on the program running in the address space. Programs that have error recovery routines could report the termination type as NORMAL even though an abend may have occurred. You need to make the determination of what termination types will be produced by an address space before coding an EOM rule.

For example, canceling a TSO/E foreground user address space results in an EOM processing termination type as NORMAL instead of ABNORMAL termination. Because TSO recovers from the cancel request and proceeds with a normal log off to end the session, the termination type is NORMAL. Other programs might also do the same depending on the error recovery provided by the running program.

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:

 DX0430I  tttttttt EOM ASID: aaaaa A.S. Name: nnnnnnnn
tttttttt: Type of time EOM. 'NORMAL' or 'ABNORMAL'.
   aaaaa: ASID (decimal) of STC or TSO address space that is
          terminating.
nnnnnnnn: Name of STC or TSO address space that is terminating.

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