Thank you for bringing back the very painful memory of working for the Navy when someone deleted a library that was in the JES2 proc concatenation on a B1 secured system; JES would JCL error out and we couldn't come up. The only thing that was authorized to be run standalone on that system was DFDSS restore. I spent 55 *straight* hours restoring every DASD for that system! (shudder)
"the good old days weren't always good and tomorrow ain't as bad as it seems!" Greg -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of John McKown Sent: Tuesday, July 07, 2015 11:46 AM To: [email protected] Subject: [EXTERNAL] Re: TSO-only proc (was Re: Product Remove from z/OS) On Tue, Jul 7, 2015 at 10:39 AM, Richard Pinion <[email protected]> wrote: > Naw, card punch and card reader are your best friends in such an > emergency :) > You laugh. But I had to do that many years ago. I messed up the VTAM proc. No VTAM ==> no terminals. Back to the 129 to punch out some JCL to IEBPTPCH the VTAM proc to cards. Then interpret them. Then find the mistake and replace it. Now punch the IEBUPDTE and read it in. Oh, wow. I am so happy to have multiple system images now. And I _never_ take them all down at once. Well, unless we have a power failure. > > > > --- [email protected] wrote: > > From: John Eells <[email protected]> > To: [email protected] > Subject: TSO-only proc (was Re: Product Remove from z/OS) > Date: Tue, 7 Jul 2015 11:37:50 -0400 > > That works for updating the procs themselves, and it's an outstanding > precaution everyone should use as a matter of routine. > > But it does not work so well for a volume failure, when a data set > named in the proc is moved (and referenced by volser) or renamed, or > when the concatenation limit is exceeded for one of the DD names after > a change causes a data set to extend (I can hear TomC already, > yelling, "but-but-but...don't *do* it that way to begin with!"), or...etc. > > A TSO/E-only proc's purpose is to provide a way to recover (nearly) no > matter *what* happens to the regular procs or the data sets named in > them. With native TSO EDIT, you can list, alter, and save changes to > the logon proc you really want to use. Or, you can edit the one you > want to use to make it a batch job, save it in a new member, submit > it, and use the OUTPUT command to read the output and locate the problem. > You can do this in a standalone single-system environment, too, > without NJE or FTP access. > > Everyone should have one. Really. Even if you are sure you will > never need it. Just because "can" beats "can't" when things go wrong. > > [email protected] (Alan Schwartz) wrote: > > Or have someone stay logged on to TSO while updating the logon > > procs. If there's a problem they can fix it. > > -- > John Eells > z/OS Technical Marketing > IBM Poughkeepsie > [email protected] > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO IBM-MAIN > > > > > _____________________________________________________________ > Netscape. Just the Net You Need. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO IBM-MAIN > -- Schrodinger's backup: The condition of any backup is unknown until a restore is attempted. Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be. He's about as useful as a wax frying pan. 10 to the 12th power microphones = 1 Megaphone Maranatha! <>< John McKown ---------------------------------------------------------------------- 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
