There are more than a few threads in the archives about this. Mostly after people compressing a PROCLIB - which can cause this problem (use "compress" in your search if you want to find them). So you compressing the library could have made things worse. If you do the search, you'll find comments about the JOBPARM PROC=xx "trick" to cause JES2 to open/close the proclib concatenation, but with dynamic proclibs it is easier - and Walter hinted at it below.
Using $TPROCLIB(*) - or (RO *ALL,$TPROCLIB(*) in a sysplex that may have other systems sharing the proclib) should fix the problem without having to remove / add the proclib back in. In looking back at a previous comment of mine in the archives related to compressing a JES2 PROCLIB and your issue I found this note that won't hurt to repeat... "if you compress a PROCLIB allocated to *MASTER* (MSTJCLxx) and a proc is started with SUB=MSTR, you're SOL until you IPL if you run into "strange results". There is no refresh trick." Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:[email protected] Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ On Wed, 30 May 2012 16:25:09 +0300, גדי בן אבי <[email protected]> wrote: >Yes, and everything looks OK. >We ended up removing the offending proclib and then adding it back, and that >fixed the problem. >This might be fine on a test system, but I wouldn't want to do it on a >production system. > >Gadi > >-----Original Message----- >From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of >Walter Marguccio >Sent: Wednesday, May 30, 2012 4:20 PM >To: [email protected] >Subject: Re: JES2 using old version of procedure > >Gadi, > >have you tried with the $TPROCLIB command ? > > >Walter Marguccio >z/OS Systems Programmer >BELENUS LOB Informatic GmbH >Munich - Germany > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
