Actually just submit a JOB naming the logon PROC and see what happens. Just be sure you have a message class that is saved to sysout
-----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jesse 1 Robinson Sent: Thursday, March 5, 2020 5:09 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: JCL error during TSO/E logon >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
