Re: JES2 DD Concatenation issue



On Fri, 28 Mar 2008 14:32:48 -0500, Mark Zelden <mark.zelden@xxxxxxxxxxxx>
wrote:

The "flooding" part is always how I thought it worked (and maybe it
did but has changed). See my last post:
http://bama.ua.edu/cgi-bin/wa?A2=ind0803&L=ibm-main&D=1&amp;amp;O=D&T=0&P=214254

Maybe it would be fixed after 10 jobs where submitted in a row with the
non-existing JES2 PROCxx DD.

Anyway... any time this has ever happened in a shop I was at (which has
probably been no more than 5 times in the past 15-20 years) I have always
just bounced JES2 (after making sure the PROCLIB existed and / or was moved
back to its proper location). It's quick enough and always fixes the problem.


Lots more of this in a few IBM APARs. OY45900, OW51308 and II07133.
You need IBMLINK to look at OY45900 and OW51308 as I can't find
a docview link to them. OY45900 doesn't mention anything
about "round robin" usage of the converter tasks:

"Thus, if there are multiple Converter PCEs /
tasks it will be necessary to abend JES2 and restart it to
guarantee that all proclibs are freshly opened ($P JES2,ABEND
.. HOTSTART)."

And here in II07133 (from 1993) there is more...
http://www-1.ibm.com/support/docview.wss?uid=isg1II07133

However, II07133 says:
Note: It is NOT necessary to force a close and open of a
Proclib after it's been compressed. Any I/O errors
resulting from a compress would have occurred while the
compress was in progress, and THAT would have forced a
close and open of the proclib. If no I/O errors occurred
while the compress was in progress, then no I/O errors
would be expected after the compress had completed, and
thus it is NOT necessary to perform the close and open.


In my experience, the statement above is not true. I have seen
problems caused by compress when no I/O errors occurred.

OW51308 is more recent and mentions using the dynamic proclib
facility in z/OS 1.2 instead of bouncing JES2. But it doesn't mention
anything about a COMPRESS.

Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group - ZFUS G-ITO
mailto:mark.zelden@xxxxxxxxxxxx
z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
.



Relevant Pages

  • Re: RES: JES2 Datasets in MasterCatalog
    ... I mentioned the PROCLIB statement in my last post. ... PROCLIB statements instead of JCL in the JES2 procedure may not ... "Cataloged in the master catalog (or in a user catalog, ...
    (bit.listserv.ibm-main)
  • Re: JES2 DD Concatenation issue
    ... Once JES2 has started the CATALOG is no longer part of JES2's process to ... Therefore the CATALOG and JES2 can disagree on where the proclib actually ... For IBM-MAIN subscribe / signoff / archive access instructions, ...
    (bit.listserv.ibm-main)
  • Re: IEFC614I
    ... Perferred method says you are using jes2 dynamic procs, in which case a $TPROCLIB will open/close reallocate them ... We had some programmers running COMPRESS on their PROCLIB that was in The JES2 JCL. ... This transmission may contain information that is privileged, ... confidential, legally privileged, and/or exempt from disclosure ...
    (bit.listserv.ibm-main)
  • Re: JES2 DD Concatenation issue
    ... How would you ever re-allocate a proclib if it was ENQed? ... Shutdown JES2, then run a batch job to do the rename. ... crash but fail to free the ENQS?) ... For IBM-MAIN subscribe / signoff / archive access instructions, ...
    (bit.listserv.ibm-main)
  • Re: JES2 DD Concatenation issue
    ... 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 ... Therefore the CATALOG and JES2 can disagree on where the proclib actually ...
    (bit.listserv.ibm-main)