To reconfirm again, the load module is authorised (AC=1) and we did not break the authorisation by coding STEPLIB.
I found few interesting things related to wait on SVC 99 today, The program XYZ uses SVC 99 in two different places (both using the same allocation request block & allocation pointer). The same program XYZ after receiving Dataset information from catalog (say for eg: USERID.TEST.DATASET in VOL123) using SVC 99 does issue an SVC 99 on USERID.TEST.DATASET at a later stage. So before executing the program XYZ, we had opened the USERID.TEST.DATASET in edit mode. So the program XYZ should have failed during SVC 99 as it had done in the case of CATALOG, instead of waiting for it. But to our surprise we found the second SVC 99 waiting to get shared access on USERID.TEST.DATASET. And when I closed the dataset opened in edit mode, the job ran fine to completion. Any thoughts on why SVC 99 does not for CATALOG alone? ---------------------------------------------------------------------- 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
