Tommy, For this type of error, the probability of someone compressing a PROCLIB that is used via JCL in the JES2 Startup procedure is a strong possibility. This is why in my shop I strongly recommend using the $PROCLIB statements in JES2 (I think z/OS V1.4 or higher) or have the JCL use JCLLIB statements. It reduces the potential for a compress or COPY/UPDATE into the JES2 proclib to cause this issue.
This is not a big error and is common with JES2 Startup JCL PROCxx DD Statements. Not unless the data set was moved out from under JES2. Then you need to cycle JES2 to pick up the new location of the data set. A JES2 startup PROCLIB dataset (via PROCxx DD statements), can be deleted while JES2 is up and JES2 will not notice it until it is cycled. Basically when JES2 starts up, it loads the TTRs into storage. It then does a look up of the member based on the known TTR. If you compress or do an Update to a PROCLIB data set (that is allocated via JCL) the TTR information is then invalid. JES2 does not refresh the TTR unless the proclib DD statement is closed and reopened. If someone has the ability to delete and reallocate the JES2 library, it is not known until JES2 is cycled (usually at IPL time) and then the fun will begin. It is best to not allow any group other than the sysprogs update and rename capabilities with JES2 Proclibs in the JCL. If a $PROCLIB statement is used or JCLLIB statement, then there is no issue for compresses, copies/updates, or delete/allocates. JES2 will read the library at access time. The IEFC603I message has been around a long time in JES2, this is not specific to z/OS V1.7. The best way to eliminate this problem is to have a procedure that 1) Has multiple PROCxx Statements in the JES2 start proc (if still allocated via JCL). You can use PROC00 for all procs and something like PROC99 pointing to just SYS1.PROCLIB. 2) If a COMPRESS or UPDATE is done on any PROC00 Data set, then a job is run that will open and close PROC99. JES2 will refresh the TTRs in PROC00 and that will reduce or eliminate the IEFC603I issue. 3) The libraries in the JES2 startup JCL only allow UPDATE access to anyone but sysprogs. They can delete/reallocate the files due to the potential of JES2 not finding a PROCLIB dataset at startup. This point can be eliminated using $PROCLIB statements or having JCl use JCLLIBs. Lizette ---------------------------------------------------------------------- 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
