Classification: Confidential I believe so. ISTR that you needed to submit a job with a proc that did not exist to force JES to reopen all the proclib concats and update the control block.
As another poster suggested, I would remove the proclibs from JES and use JCLLIB instead. HTH, -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of rpinion865 Sent: Wednesday, June 12, 2024 8:20 AM To: [email protected] Subject: Re: PDS compress and PROCLIB [CAUTION: This Email is from outside the Organization. Unless you trust the sender, Don’t click links or open attachments as it may be a Phishing email, which can steal your Information and compromise your Computer.] I just tested this scenario on a z/OS 2.5 system. I even went so far as to reallocate the proclib on a different volume. Unfortunately, the proclib I picked was one allocated to MSTJCL. I got S213 abends when trying to issue a start for anything. I put it back on the original volume, and all was good. I wonder if I had picked another proclib that was not in MSTJCL, if moving to a new volume would have worked. I might try that later today. Sent with Proton Mail secure email. On Wednesday, June 12th, 2024 at 9:10 AM, Allan Staller <[email protected]> wrote: > Classification: Confidential > > Re delete/reallocate is true. Jes closes the proclibs between uses > > -----Original Message----- > From: IBM Mainframe Discussion List [email protected] On Behalf > Of rpinion865 > > Sent: Wednesday, June 12, 2024 7:43 AM > To: [email protected] > Subject: Re: PDS compress and PROCLIB > > [CAUTION: This Email is from outside the Organization. Unless you > trust the sender, Don’t click links or open attachments as it may be a > Phishing email, which can steal your Information and compromise your > Computer.] > > Urban legend or false memory. But in the early 1980s, I was told that if you > started a proc that did not exist, JES2 would open and close each proclib in > the concatenation. In fact, I was told, and if I remember correctly, I was > able to backup a proclib that ran out of directory blocks, delete the > library, re-allocate the library, restore the library, issue a start on a > non-existent proc, and all was good. > > > > > Sent with Proton Mail secure email. > > > On Wednesday, June 12th, 2024 at 8:12 AM, Lennie Bradshaw > [email protected] wrote: > > > As far as I know JES2 holds proclibs open normally. There may be a way to > > get it to close and re-open them. > > JES2 runs with the NDSI bit set in the PPT. Hence it does not issue ENQs > > for any datasets it allocates. > > Lennie > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [email protected] On > > Behalf Of Paul Gilmartin > > > > Sent: 12 June 2024 12:59 > > To: [email protected] > > Subject: Re: PDS compress and PROCLIB > > > > On Wed, 12 Jun 2024 08:55:56 +0000, Lennie Bradshaw wrote: > > > > > I believe JES2 read the proclibs without data integrity (i.e. no ENQs are > > > issued for the libraries). ... > > > > Why!? Is PDSE a solution? IEB COPY with DISP=SHR? > > > > We had a developer-facing local PROCLIB catenand. I routinely updated a > > member in background using ISPF EDIT ENQs. > > Once I found another developer's content in "my" member. She had > > courteously signed it. She explained that she had updated her member from a > > test system sharing DASD. Admin explained that MIM had crashed on that > > system at that time. > > > > MIM isn't fail-safe. But the price of fail-safe might be inability to IPL > > before MIM activates. > > > > -- > > gil > > > > -------------------------------------------------------------------- > > -- For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: INFO > > IBM-MAIN > > > > -------------------------------------------------------------------- > > -- For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: INFO > > IBM-MAIN > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO IBM-MAIN > ::DISCLAIMER:: > ________________________________ > The contents of this e-mail and any attachment(s) are confidential and > intended for the named recipient(s) only. E-mail transmission is not > guaranteed to be secure or error-free as information could be intercepted, > corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses > in transmission. The e mail and its contents (with or without referred > errors) shall therefore not attach any liability on the originator or HCL or > its affiliates. Views or opinions, if any, presented in this email are solely > those of the author and may not necessarily reflect the views or opinions of > HCL or its affiliates. Any form of reproduction, dissemination, copying, > disclosure, modification, distribution and / or publication of this message > without the prior written consent of authorized representative of HCL is > strictly prohibited. If you have received this email in error please delete > it and notify the sender immediately. Before opening any email and/or > attachments, please check them for viruses and other defects. > ________________________________ > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
