saurabh khandelwal wrote: >> In our shop, In sdsf I can see many jobs running with owner and some of them >> running without owner.
This is WAD. I believe you are referring to STCs started very early in the IPL process, not 'batch jobs'. >> I am unable to find difference in this. Can anybody help me to understand >> this process. Please post the entries you're worried about. John McKown wrote: >The only address spaces which I have ever seen which do not have an owner are >those which are started before the ESM (RACF, ACF2, TopSecret) is running. I >am fairly sure that these address space are started by NIP when z/OS is first >coming up. Indeed. These address spaces are started in IEFSSNxx, COMMxx, etc. amongst other places. You could review your SYSLOG to see what things are started before your ESM started. Oh, some address spaces just start, do its things and then die. Some of these STCs are started with something like S <STC>,SUB=MSTR , so you will not see the Owner. >Again, to my limited understanding, these address spaces do not have an owner >because they don't have a ACEE (Access Control Environment Element) pointer in >the ASXBSENV field of the "Address Space Extension Block"; which is pointed >to by the ASCB which describes the address space (the ASXB resides within the >address space, not in common storage like the ASCB does). The ACEE is >basically the information about the user from the RACF data base >(SYS1.MACLIB(IHAACEE) describes it). This control block definitely contains >information such as the OWNER and default connect group Very true. Thanks for the detailed explanation. Those address spaces are also running with AC(1) programs, usually sitting in a LINKLIST and/or APF list, depending on how+when they're started in the first place. Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
