|
|
|
The suspense file logic uses the presence or absence of certain SMF record types to determine whether a job or session is complete. Normally, the absence of the job purge record (type 26) triggers the suspension of records for a job or session. Optionally, the absence of the termination record (type 30, subtype 5) may be used. In this case, a job or session is considered incomplete only if it has not terminated by the time the SMF data is dumped. Also, in this case, a job that consists of only output writer records (type 6) would be considered complete and not be suspended.
Regardless of the presence or absence of certain record types, if the number of days between when a job was originally submitted (the Reader Start Date) and the current date is higher than a user-specified value, the job is not be suspended. For example, if a job was submitted on the 10th, is still in the suspense file on the 15th, and the specified suspend limit was four, the job is not be suspended again, but is processed. Refer to the description of the OPTION statement for information about suspense file related options.
| Copyright © 2012 CA. All rights reserved. |
|