Implementing support for EOS and TLM events

MainView AutoOPERATOR Rules Processing provides support for end-of-step (EOS) and Time Limit (TLM) events.

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.

A Time Limit (TLM) event occurs when one of the following time limits expire:

  • Job processor time limit from the JOB statement.

  • Step processor time limit from the EXEC statement of the default from JES.

  • Continuous wait time for a job from the JWT parameter in SMFPRMXX.

Wait time is defined as the time waiting while the application program is in control. For example, the time that it takes for a data set to be recalled does not count as wait time unless the recall is by way of dynamic allocation written in a user’s program.

You must implement support for the EOS and TLM event types by specifying system exits in the SMFPRMxx member of SYS1.PARMLIB.

Specifying the IEFACTRT exit provides support for the EOS event type and the IEFUTL exit provides support for the TLM event type. If you do not specify both exits, you might receive unexpected messages during BBI-SS PAS startup.

See Figure 1 for an example of the SMFPRMxx parameter member with the required exits shown in bold. You should also ensure that the required exits are listed in the EXITS() parameter and verify that the SMF type 30 records are being generated. Without the type 30 records, the EOS event will not function correctly.

Figure 1. Example of the SYS1.PARMLIB member SMFPRMxx




To deactivate the IEFACTRT exit for any reason, specify DYNEXITS=N in BBPARM member BBISSPxx. When you specify N, MainView AutoOPERATOR bypasses activating the exit and it will also disable the EOS and TLM Rule event types from occurring.

Was this page helpful? Yes No Submitting... Thank you