TLM

• 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.

Before TLM events are generated, you must have the IEFUTL SMF exit implemented. See the MainView AutoOPERATOR Customization Guide for more information about implementing the TLM event type.

To create Rules 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:

• IMFTTLM

• IMFTSSID

• IMFTSNUM

• IMFTCPCT

• IMFTXPSC

• IMFTWTCT

• IMFTWTSC

See List of MainView AutoOPERATOR-supplied EVENT variables for more information about these variables. The IMFTEXT event variable will contain the following textual information when the event fires:

 CE0430I  jjjjjjjj tttt time exceeded by ssss
jjjjjjjj: The job, STC, or TSO address space name whose time limit has
          been exceeded.
   tttt: Type of time exceeded. Values are JCPU, SCPU or WAIT.
    ssss: Subsystem Id that selected the job. JES2, JES3, ASCH (APPC),
          OMVS, STC, TSO, or jobname if none of the above applies and
         it is less then 4 characters.

The CE0430I message is not written to the BBI Journal unless Journal ==> YES is specified in a TLM Rule.