Re: JES2 DD Concatenation issue

On Fri, 28 Mar 2008 09:44:20 -0500, Mark Zelden wrote:

The catalog has nothing to do with it. Despite the fact that someone deleted
the data set, it is still ALLOCATED to JES2 and the original extents are in the
DEB. You can rename the new one, re-allocate it to its original volume and
copy it back or just leave it where it is. Either way you have to recycle JES2
to pick up the new extents.

Are DEBs created by ALLOCATE? I had imagined it was OPEN.

In an earlier contribution, you mentioned that JES holds no ENQ
on the PROCLIBs. That sounds terribly dangerous. Why would they
design it that way?

Just curious: can the PROCLIB concatenation contain PDSEs?

-- gil

----------------------------------------------------------------------
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: JES2 DD Concatenation issue
    ... it is still ALLOCATED to JES2 and the original extents are ... Are DEBs created by ALLOCATE? ... Shutdown JES2, then run a batch job to do the rename. ...
    (bit.listserv.ibm-main)
  • Re: Allocating Large SYS1.HASPACE
    ... In order for JES2 to actually use a big volume, you have to change SPOOLDEF ... all MAS members must at a minimum release level: ... Use this JCL to allocate all of a 3390-9, ...
    (bit.listserv.ibm-main)