HWIBCPII is one of those magical address spaces that is started by Abracadabra:
S IEESYSAS,PROG=HWIAMIN2 IBM supplied proc IEESYSAS is a weird animal with no real content. The actual STC name is determined by the startup program. //IEESYSAS PROC PROG=IEFBR14 //IEFPROC EXEC PGM=&PROG //* THE IEESYSAS PROCEDURE IS SPECIFIED IN THE //* PARAMETER LIST TO IEEMB881 BY MVS COMPONENTS //* STARTING FULL FUNCTION SYSTEM ADDRESS SPACES. When the named STC starts up, it has nothing allocated other than what z/OS has chosen dynamically for that magical name. It runs SUB=MSTR, but you cannot specify SUB=MSTR. In our shop, HWIBCPII starts before (independent of) JES2, and continues running after JES2 shutdown. Examples of other tasks started with IEESYSAS: //SMSVSAM EXEC IEESYSAS,PROG=IDAVSJST //IOSAS EXEC IEESYSAS,PROG=IOSVROUT //CEA EXEC IEESYSAS,PROG=CEAINIT //WLM EXEC IEESYSAS,PROG=IWMINJST Despite the appearance of 'SYSOUT' in the original post, these tasks cannot use JES services to handle print output. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Steve Smith Sent: Wednesday, May 30, 2018 10:55 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: HWIBCPII I don't know anything about this STC, but the first couple of messages imply you have SYSOUT files in the JCL. Those require JES. AFAIK, any STC waits for JES unless SUB=MSTR is specified, so don't do both. sas ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
