Have (or create from sandbox) a simple/failsafe version of the VTAN proc. Export the spool files and import into sandbox or other lpar. I suspect there are sufficwnt breadcrumbs in a standalone dump.
Test changes to VTAM proc by running it via a job before you shutdown. > -----Original Message----- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On > Behalf Of Peter Ten Eyck > Sent: Tuesday, January 30, 2024 10:11 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: GTF trace for a JCL error? > > [EXTERNAL EMAIL] > > Dave, > > It was VTAM that would not come up due to a JCL error. We could not sign on > to that LPAR and access JES. I was researching if I could see the JCL error > via a > GTF trace. Sounding like I will not be able to do that. > > In this case, starting the VTAM STC again with S <VTAM>, SUB=MSTR would > write the JCL error to the console. > > The issue has been resolved, just researching what other methods I could have > used… > > ---------------------------------------------------------------------- > 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
