Jacky - Once JES2 has started the CATALOG is no longer part of JES2's process to find its JCL defined Proclibs.
JES2 builds an internal table that probably holds information like the data set name, the volser and the TTR locations in that dataset for the PROCs. You can with the appropriate ALTER authority go out and delete - define - catalog the JES2 PROCLIB anywhere. JES2 does not enqueue this data set. Therefore the CATALOG and JES2 can disagree on where the proclib actually lives. The only way to get this correct is to reallocate the proclib back on the original volume in the original location and pray that no one has already overlaid the TTRs where the JES2 Proclib use to live. Otherwise, if the proclib on the new volumes is good, you will need to bounce JES2 (HOT START) This is done with a $PJES2,ABEND. You will need to reply with the appropriate response. JES2 will then find the new home for this JCL defined Proclib. Lizette My point is why CATALOG address space is not considering the new volume RBI035 why is it that still expecting RBI031 even though I have recreated the SCLM1.PROCLIB with catalog option and it got created in RBI035. If I see the LISTC for SCLM1.PROCLIB it shows the volume as RBI035 Error as : IEC143I 213-04,IFG0194D,JES2,JES2,PROC13-0003,9800,RBI031,SCLM1.PROCLIB Why the catalog is still expecting the dataset from RBI031 itself ? JAcky ---------------------------------------------------------------------- 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
