>>Just curious: can the PROCLIB concatenation contain PDSEs? >Yes. That eliminates the COMPRESS issue or the problem you might >run into if the library takes an additional extent.
Yes, you can use PDSEs in the JES2 PROCLIB concatenation. LINKLIST too. But, not such a great idea, IMHO. Maybe I'm wrong here (and I could be), but I somehow remember that the empty space in a PDSE is not reclaimed until the dataset is closed. Now, you can't easily close a LINKLIST dataset; system shutdown doesn't quite do it. Removing it from the active LINKLIST probably will. A JES2 PROCLIB is easier to close; a temporary switch to a new concatenation usually works. However, the caveat here is that it must be closed on ALL systems sharing it, AT THE SAME TIME! Otherwise, the free space clean operation will not take place. I don't think that this has (yet) been addressed by IBM development. Additional extents are not as large of a problem with PDSEs and they are with PDSs. If a PDS (in a PROCLIB or a LINKLIST) takes a new extent, the only address space to know about it is the initiator in which the copy job executed (or the TSO user that took the new extent). Neither JES2 nor the LINKLIST will be aware. With a PDSE, all of this activity takes place within the PDSE address space. This address space can communicate this information to other images within the same SYSPLEX. All JES2s and LINKLISTs become aware. Corrections, if necessary, to the above are welcome! ---------------------------------------------------------------------- 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
