I may have told this story before. An auditor doing a JES2 review once called to say that a JES2 proclib was missing--not found on the system. Impossible, I said. Ouch! He was right. Turns out that a colleague had been requested by the 'owner' of the proclib to remove it. So he did. Pure dumb luck that the error was caught before the next IPL. This was before the DSI option existed.
I would not eliminate DSI. The modern solution is to have most of your proclibs dynamically allocated via the init deck rather than hard-coded in the JES2 proc. That way you can at least IPL to fix a proclib problem. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Vernooij, Kees (ITOPT1) - KLM Sent: Thursday, August 24, 2017 7:03 AM To: [email protected] Subject: (External):Re: JES2 NODSI/DSI ? Yes, we know the proclib-switch trick, but the problem is that one can forget to use it. Kees. > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Allan Staller > Sent: 24 August, 2017 15:59 > To: [email protected] > Subject: Re: JES2 NODSI/DSI ? > > The NODSI operand also allows you to update the proclibs "on the fly" > RACF and dsorg attribute "u" should prevent these kinds of errors. > > I would stay with the NODSI option. > > > BTW, if SYS1.PROCLIB is moved . submit a hob with (e.g.) PROG99 which > will not be found. > JES Will then reread the proclib concat and find your "new" > SYS1.PROCLIB. > > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Vernooij, Kees (ITOPT1) - KLM > Sent: Thursday, August 24, 2017 8:15 AM > To: [email protected] > Subject: Re: JES2 NODSI/DSI ? > > With NODSI, > 1. dynamic proclibs are not enqueued by JES2 and can be deleted and > reallocated whithout notification. > 2. JES2 does not know that the proclib has been moved and remains > reading from the old allocation, which is the disc area where the old > proclib resided. > > With DSI, JES2 enqueues the proclibs, so it will prevent these errors. > > Kees. > > > -----Original Message----- > > From: IBM Mainframe Discussion List > > [mailto:[email protected]] On Behalf Of Lizette Koehler > > Sent: 24 August, 2017 15:11 > > To: [email protected] > > Subject: Re: JES2 NODSI/DSI ? > > > > What problem are you trying to solve. How will this help? > > > > Lizette > > > > > > > -----Original Message----- > > > From: IBM Mainframe Discussion List > > > [mailto:[email protected]] > > On > > > Behalf Of Vernooij, Kees (ITOPT1) - KLM > > > Sent: Thursday, August 24, 2017 12:28 AM > > > To: [email protected] > > > Subject: JES2 NODSI/DSI ? > > > > > > To protect dynamic proclibs from accidents, we are considering > > > setting > > > HASJES20 to DSI in SCHED00. > > > Is any site running JES2 with DSI? With positive of negative > > experiences? > > > > > > Thanks, > > > Kees. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
