I looked at the APAR text and I would consider it inaccurate (and/or incorrect).
>From the APAR text: It should be noted: IMS establishes a time limit using the STIMER macro and the TASK parameter to indicate that the time interval is only decreased when the associated task is running. Any ESS that WAITs or SUSPENDs the IMS dependent region will therefore not decrease the time interval during these events and will not drive STIMER exit routines to issue abends. Use of "time limit" and "time interval" surely is an unclear usage of terms. STIMER TASK provides a "CPU Time limit" (most would not think of it that way if they see only "time limit"). And there is no "time interval". The STIMER remains in effect as long as it takes to use that much CPU time. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
