It' s not my dog.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Steve Smith <sasd...@gmail.com> Sent: Friday, March 6, 2020 1:20 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: JCL error during TSO/E logon IMHO, a TSO logon proc should have no (0, zero, none, nada, zip) DD statements. It doesn't solve every possible problem, but it prevents this one. sas On Fri, Mar 6, 2020 at 11:15 AM Wayne Bickerdike <wayn...@gmail.com> wrote: > My presentation at Share last year hinted at a Swiss Army knife approach. > If you are a CICS shop, use REXX/CICS, a quick READ SPOOL and you have your > diagnostic info. Import the JCL and modify the offending PROC, Export back > to the proclib and log on. The REXX file system is a handy place to keep > backups of various PDS members, should a problem like this occur. > > On Sat, Mar 7, 2020, 01:32 ITschak Mugzach <imugz...@gmail.com> wrote: > > > Shmuel, > > I did mentioned the need to have an allocation free TMP procedure. > However, > > if the OP can't login, and do not have sich proc, he can see what is > wrong > > using console (JES) commands. Fixing the issue is possible using native > > edit commands. > > > > Best > > ITschak Mugzach > > *|** IronSphere Platform* *|* *Information Security Continuous Monitoring > > for z/OS, x/Linux & IBM I **| z/VM comming son * > > > > > > > > > > On Fri, Mar 6, 2020 at 4:00 PM Seymour J Metz <sme...@gmu.edu> wrote: > > > > > You don't have an alternate proc? You can't telnet to a Unix shell? > > > > > > > > > -- > > > Shmuel (Seymour J.) Metz > > > http://mason.gmu.edu/~smetz3 > > > > > > > > > ________________________________________ > > > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on > behalf > > > of ITschak Mugzach <imugz...@gmail.com> > > > Sent: Friday, March 6, 2020 6:07 AM > > > To: IBM-MAIN@LISTSERV.UA.EDU > > > Subject: Re: JCL error during TSO/E logon > > > > > > You can used recycled paper as well... I thought no one can login, so > you > > > must use the console to modify stcclass and print to viee. > > > > > > ITschak > > > > > > בתאריך יום ו׳, 6 במרץ 2020, 13:05, מאת Seymour J Metz <sme...@gmu.edu > >: > > > > > > > Why kill a tree? > > > > > > > > > > > > -- > > > > Shmuel (Seymour J.) Metz > > > > http://mason.gmu.edu/~smetz3 > > > > > > > > > > > > ________________________________________ > > > > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on > > behalf > > > > of ITschak Mugzach <imugz...@gmail.com> > > > > Sent: Friday, March 6, 2020 1:21 AM > > > > To: IBM-MAIN@LISTSERV.UA.EDU > > > > Subject: Re: JCL error during TSO/E logon > > > > > > > > Modify tso class in jess to keep the joblog. Your operators can print > > it > > > > for you to review the error > > > > > > > > > > > > ITschak > > > > > > > > בתאריך יום ו׳, 6 במרץ 2020, 1:08, מאת Jesse 1 Robinson < > > > > jesse1.robin...@sce.com>: > > > > > > > > > From the dawn of time, it was deucedly difficult to find the cause > > of a > > > > > JCL error during TSO logon. Then several releases ago, we were > > treated > > > > to a > > > > > 'fix'. The error would be displayed on the user's screen, allowing > > the > > > > > problem to be corrected within seconds. Yesterday we had such a > > > > situation, > > > > > but any helpful message flashed on the screen for milliseconds and > > then > > > > > disappeared. In this case it turned out to be missing logon proc. > > > > > > > > > > I hunted in vain for doc on this problem, including maybe a need to > > > set a > > > > > parm somewhere. We run TPX, which it just now occurs to me might be > > the > > > > > 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 > > > > > robin...@sce.com<mailto:robin...@sce.com> > > > > > > > > > > > > > > > > > ---------------------------------------------------------------------- > > > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > > > send email to lists...@listserv.ua.edu with the message: INFO > > IBM-MAIN > > > > > > > > > > > > > > ---------------------------------------------------------------------- > > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > > send email to lists...@listserv.ua.edu with the message: INFO > IBM-MAIN > > > > > > > > > ---------------------------------------------------------------------- > > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > > send email to lists...@listserv.ua.edu with the message: INFO > IBM-MAIN > > > > > > > > > > ---------------------------------------------------------------------- > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > > > ---------------------------------------------------------------------- > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- sas ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
