Classification: Confidential You need to look at the JES output to determine the error. Use the following command S taskname,,,MSGCLASS=x where x is a held sysout class.
HTH, -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Ituriel do Neto Sent: Tuesday, January 30, 2024 8:39 AM To: [email protected] Subject: Re: GTF trace for a JCL error? [CAUTION: This Email is from outside the Organization. Unless you trust the sender, Don’t click links or open attachments as it may be a Phishing email, which can steal your Information and compromise your Computer.] 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 <[email protected]> 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 [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ::DISCLAIMER:: ________________________________ The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. ________________________________ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
