Re: JES2 DD Concatenation issue
- From: brian.peterson.ibm.main@xxxxxxxxxxx (Brian Peterson)
- Date: 28 Mar 2008 11:03:45 -0700
On Fri, 28 Mar 2008 12:03:54 -0500, Mark Zelden wrote:
Yes. That eliminates the COMPRESS issue or the problem you might
run into if the library takes an additional extent. The second problem
was fixed about 15 years ago in MVS/ESA V4. JES2 recognizes this
condition via I/O error and then will close and reopen the DD for
all converter tasks. Actually, knowing this works makes me think
that the "trick" mentioned an an earlier post (running jobs that point
to a nonexistent or another PROCxx DD) could work to fix the problem
without having to bounce JES2. But I don't know if there is some
extra code in the fix from 15 years ago that handles that situation
differently.
Mark
--
I was going to contribute to this before, to correct this statement you made,
Mark. Having had the actual hands-on experience of a JES2 proclib going
away "in anger", I know that the trick of running a job pointing to a non-
existing JES2 PROCxx DD actually works - IF THE PROCLIB DATA SETS ARE ON
THE SAME VOLUME AS BEFORE. JES2 will CLOSE and reOPEN the PROCnn
concatenation, and so long as the proclib data sets are on the exact same
VOLUME, new extent information is built and JES2 is happy.
Brian
----------------------------------------------------------------------
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
.
- Prev by Date: CSP/AD and zOS 1.8
- Next by Date: Re: JES2 DD Concatenation issue
- Previous by thread: Re: JES2 DD Concatenation issue
- Next by thread: Re: JES2 DD Concatenation issue
- Index(es):
Relevant Pages
|
|
