We keep a TSO rescue proc with '911' in the name. It lives in SYS1.PROCLIB away from the standard location for TSO procs. '911' contains no dataset or volume references. Just the absolute bare minimum to get logged on. It never changes. Once you get to Ready, you can allocate ISPF libraries or as a last resort use TSO Edit. You just need to make sure the rescue proc is authorized to sysprogs who might need to recover from a FUBAR.
. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John Eells Sent: Tuesday, July 07, 2015 8:38 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: TSO-only proc (was Re: Product Remove from z/OS) 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. schw...@us.ibm.com (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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
