>Yes, JCL ensures the resources are available before the job starts (but not before initiation).
I don't understand what you mean by "before the job starts but not before initiation". The initiator enqueues on all data sets referred to in the job (all steps),before it starts the allocation phase for the first step (is this phase what you call "initiation"?). The initiator does not verify, if the data sets exist until allocation, so (in aJES2 environment), there is no guarantee. This is why you can get "JCL Error" after the job was started when a data set is not found or a new allocation fails (typically for duplicate name error). JES3 will (may?) verify before it hands over the job to the initiator. -- Peter Hunkeler ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
