Hi, You can check the jobclass definitions of your STCs by issuing $DJOBCLASS(STC),LONG or looking into SDSF at JC screen. Probably the outdisp is (PURGE,PURGE).
In this case, you may change it to (HOLD,HOLD) to see the JCL. Best Regards Ituriel do Nascimento Neto z/OS System Programmer Em terça-feira, 30 de janeiro de 2024 às 11:31:17 BRT, Peter Ten Eyck <000004d3761a18a7-dmarc-requ...@listserv.ua.edu> escreveu: Under z/OS 2.4. I have a STC when started, fails with the following error in the SYSLOG: IEE132I START COMMAND DEVICE ALLOCATION ERROR Looking at the STC output in JES, there is a JCL error in the proc (dataset not found). Is there a way to "see" the JCL error without looking at the JES output? I have been researching and running a GTF trace with no success "seeing" the JCL error, not sure what GTF trace options to turn on or if it is possible to see that JCL error via a GTF trace. Is it possible to see that JCL error in a GTF trace, if so, what options (parms) do I need to run with? Note: We had an issue with VTAM not coming up on a LPAR and we were unable to access JES to see the JCL error. ---------------------------------------------------------------------- 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
