P.S. When that happened to me, I manually issued a $S and that freed things up.
I expect that your new automated shutdown procedure has issued a $P command. JES2 could is still be "up", but JES2 processes required for your IKJEFT1B script have been drained. Don > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Rozeboom, Kay [DAS] > Sent: Friday, February 15, 2013 10:18 AM > To: [email protected] > Subject: What needs to be up for IKJEFT1B to execute? > > We have some started tasks that execute a IKJEFT1B step at the end. > These work fine during regular shutdowns of the started tasks. But > when testing a new automated total shutdown procedure (meant to run > prior to an IPL), the IKJEFT1B step hangs up. We think it must be > waiting for something that has already been shut down, but can't figure > out what. > > Kay Rozeboom > Information Technology Enterprise > Iowa Department of Administrative Services > Telephone: 515.281.6139 Fax: 515.281.6137 > Email: [email protected] > > > > > ---------------------------------------------------------------------- > 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
