Bill, $PROCLIB control cards in JES2 rather than JCL PROCxx statements was the fix. JES2 deals with them totally different than the DD statements. As well as JCLLIBs. Both of them address this issue. The only time this is a concern is when shops still rely on PROCxx statements in JES2 startup JCL.
But the best is to get everything out of JES2 startup proc JCL and put in JCLLIBs in all jobs where needed. That way no one (except the sysprog) can actually make life interesting for JES2. Lizette <------ Snip -------------- Sounds like an opportunity to request to change the way this works in JES2: (1) add a user option at JES2 start-up time to bypass saving of TTRs and always use a system service like BLDL to find the proc; (2) add an operator command to refresh all saved TTRs; (3) other idea. Recycling JES2 sounds like massive overkill that might not always be possible. Obviously the JES2 developers did this to make proclib reading happen faster in order to support installations that run a huge number of jobs per hour. One size does not fit all very often. This is the same type of problem as that associated with Linklist processing. I bet there are other products/components with the same design and the same problem waiting to happen. Bill Fairchild ------ UnSnip --------------> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
