Check the JES2 INIT Deck for the STCCLAS and see what it has for DISP. Next, if there is a SYSOUT Repository ($avers for example) maybe all output from the STC will be in there
If you have a JCL Scan utility (Like JCLPLUS) then scan the JCS All else, slap a job card on it with TYPRUN=SCAN and see what that says. Sometimes in SDSF a ST function can find the output you cannot see Lizette -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Charles Mills Sent: Thursday, May 21, 2020 9:11 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Where do started PROC errors go? I have a program that runs successfully in a job. I just cloned the JCL appropriately into a PROC. When I issue a START for the PROC I get a started message and an ended message but no clue as to why it failed. (It is supposed to be long-running, so ending is a failure.) I don't think it is a JCL error because I get a JCL error message in that case, and I have evidence that it actually ran "some." The PROC includes //SYSTSPRT DD SYSOUT=H. (H is a held class.) I have strong evidence that the program is getting far enough that it would have written several lines to SYSTSPRT. I see nothing in SDSF, even with PREFIX * and OWNER *. Where is my output going? How do I determine that? How do I view it? There is nothing in the PROC statement: //procname PROC and no operands on the START other than the PROC name. The program is IKJEFT01 and a Rexx EXEC FWIW. Again, it works in a job. Thanks, Charles ---------------------------------------------------------------------- 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
