Thanks! That helps explain an IPL last year of a newly-created LPAR
where we removed every startup parm we could think of for the first IPL.
ACF2 messages still showed up on the console, so I figured there must be
a hook somewhere. We had copied the res-pack from an already running
system.
On 5/21/2019 12:06 PM, Wayne Driscoll wrote:
The RACF subsystem gets started out if ICHSEC00, which is invoked out of IPL.
If I recall correctly, both ACF2 and Top Secret provide a replacement for
ICHSEC00 (probably the same code for both products).
Wayne Driscoll
Rocket Software
Note - All opinions are strictly my own.
-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of
Tony Thigpen
Sent: Tuesday, May 21, 2019 11:11 AM
To: [email protected]
Subject: Re: IPL process - understanding IEFSSNxx
Thanks. That helped a lot.
One of the questions I am trying to answer is "who is starting RACF during
IPL". It's not in COMMNDxx.
Tony Thigpen
John McKown wrote on 5/21/19 10:56 AM:
On Tue, May 21, 2019 at 9:47 AM John McKown
<[email protected]>
wrote:
On Tue, May 21, 2019 at 9:27 AM Tony Thigpen <[email protected]> wrote:
I am looking at my ipl process and am trying to understand why some
of the start by themselves.
I am in a sandbox so I can play all I want.
My current IEFSSN00 is:
000001 SUBSYS SUBNAME(SMS)
000002 INITRTN(IGDSSIIN)
000003 INITPARM('ID=00,PROMPT=DISPLAY')
000004 SUBSYS SUBNAME(JES2) /* JES2 AS PRIMARY SUBSYSTEM */
000005 PRIMARY(YES) START(YES)
000006 SUBSYS SUBNAME(RACF)
000007 INITRTN(IRRSSI00)
000008 INITPARM('%,M')
000009 SUBSYS SUBNAME(CICS)
000010 SUBSYS SUBNAME(DFRM) /* NAME OF THE DFSMSRMM SUBSYSTEM */
000011 INITRTN(EDGSSSI)
000012 SUBSYS SUBNAME(TNF)
000013 SUBSYS SUBNAME(VMCF)
000014 SUBSYS SUBNAME(FFST)
000015 SUBSYS SUBNAME(IXFP) /* IXFP SUBSYSTEM */
000016 INITRTN(SIBSSIPL)
000017 INITPARM('INIT(Y),DYNDDSR(I),LANG(AMENG)')
I understand that JES will start because of the START(YES), but I am
also seeing other sub-systems like RACF start.
Does the INITRTN force an autostart as if START(YES) was specified?
I don't think so, but I can't be definitive. The INITRTN specifies a
program which will run in the master scheduler address space during
start up. Now, that program could do a START command, via SVC 34. Or
even use the ASCRE to create a new address space to run some code
which might stay around "forever". A case of "who knows unless it is
documented".
It appears that jobs started with IEFSSNxx start as normal JES jobs.
Can IEFSSNxx be used to start tasks which run as SUB=MSTR.
https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww
.ibm.com%2Fsupport%2Fknowledgecenter%2Fen%2FSSLTBW_2.3.0%2Fcom.ibm.zo
s.v2r3.ieae200%2Fiefssn1.htm&data=02%7C01%7Cwdriscoll%40ROCKETSOF
TWARE.COM%7C7798ebd9078f4f26092508d6de06e95c%7C79544c1eed224879a082b6
7a9a672aae%7C0%7C0%7C636940518619668581&sdata=kO4cc83JmfKhS3oocQU
B21nQ80nZK3QzsE5HdNE30hs%3D&reserved=0
- Once a subsystem name is defined to the system, any attempt to start
that subsystem (or any started task with the same name as that subsystem)
via a START command which does not explicitly specify SUB=JES2 (or JES3)
will result in that subsystem or started task being started under the
Master subsystem rather than under the job entry subsystem. Because the
only procedure libraries available to the Master subsystem are those
specified in the MSTJCLxx's IEFPDSI data set, any procedures being started
that are defined in the job entry subsystem's PROC00 data set, but not in
the MSTJCLxx's IEFPDSI data set, will be unavailable. Therefore they will
not be found; the system will issue message IEFC612I.
I forgot to mention. It might _appear_ that the subsystem is running
under JES when it is actually running SUB=MSTR if the code does an SSI
function code 20 "Request Job ID". That will connect it to the primary
JES so that it can do things such as dynamically allocate SYSOUT.
https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
ibm.com%2Fsupport%2Fknowledgecenter%2Fen%2FSSLTBW_2.3.0%2Fcom.ibm.zos.
v2r3.ieaf200%2Frjobid.htm&data=02%7C01%7Cwdriscoll%40ROCKETSOFTWAR
E.COM%7C7798ebd9078f4f26092508d6de06e95c%7C79544c1eed224879a082b67a9a6
72aae%7C0%7C0%7C636940518619668581&sdata=r5qn6qySAro%2ByOt60t1rY8F
ZT3N5Kx19Wx97qXIODrU%3D&reserved=0
--
Tony Thigpen
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
[email protected] with the message: INFO IBM-MAIN
================================
Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■
Main Office Toll Free Number: +1 855.577.4323
Contact Customer Support:
https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport
Unsubscribe from Marketing Messages/Manage Your Subscription Preferences -
http://www.rocketsoftware.com/manage-your-email-preferences
Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy
================================
This communication and any attachments may contain confidential information of
Rocket Software, Inc. All unauthorized use, disclosure or distribution is
prohibited. If you are not the intended recipient, please notify Rocket
Software immediately and destroy all copies of this communication. Thank you.
----------------------------------------------------------------------
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
