As someone noted, the RACF STC was originally optional. That's not RACF Lord 
and Protector but RACF the Operator Command Utility. SMPE-managed 
[SYS1.IBM.]PROCLIB now supplies this element in z/OS 2.3:

//******************************************************************//
//*  RACF:                                                         *//
//*                                                                *//
//*      THIS RACF SYS1.PROCLIB PROCEDURE CAN BE USED TO START     *//
//*      THE RACF ADDRESS SPACE.                                   *//
//*      BEFORE EXECUTING IT, THE FOLLOWING PROCEDURE SHOULD BE    *//
//*      MODIFIED TO MEET YOUR INSTALLATION'S REQUIREMENTS.        *//
//*                                                                *//
//*      THE ADDRESS SPACE WILL AUTO-START DURING SYSTEM IPL.      *//
//*      THE RACF SUBSYSTEM INITIALIZATION PROGRAM WILL ISSUE      *//
//*      AN INTERNAL MVS START COMMAND TO START THE RACF STARTED   *//
//*      PROCEDURE, WHICH IN TURN WILL INITIALIZE THE RACF ADDRESS *//
//*      SPACE.                                                    *//
//*                                                                *//
//*      CHANGE ACTIVITY =                                         *//
//*      $L0=ADDRSP  JRF1922  920731 PDPJL1: PTM PIM0401           *//
//******************************************************************//
//RACF PROC                                                           
//RACF EXEC PGM=IRRSSM00,REGION=0M                                    


.
.
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 <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of 
Mark Zelden
Sent: Tuesday, May 21, 2019 1:32 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: IPL process - understanding IEFSSNxx

On Tue, 21 May 2019 10:27:20 -0400, Tony Thigpen <t...@vse2pdf.com> 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?

No, but it can start a subsystem address space.  

>
>It appears that jobs started with IEFSSNxx start as normal JES jobs. 
>Can IEFSSNxx be used to start tasks which run as SUB=MSTR.
>

Only 2 ways a subsystem ASID can start as far as I know, as an STC from a START 
command or from the INITRTN (using ASCRE I assume). 

z/OS MVS Using the Subsystem Interface should have the details. 

https://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zOSV2R3SA380679/$file/ieaf200_v2r3.pdf


Best Regards,

Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS ITIL v3 
Foundation Certified mailto:m...@mzelden.com Mark's MVS Utilities: 
http://www.mzelden.com/mvsutil.html
Systems Programming expert at http://search390.techtarget.com/ateExperts/


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to