Re: IEESYSAS and ARCNXXXX address spaces.
Thanks to all for the input. I will ensure everyone here knows the unique situation surrounding these address spaces. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
IEESYSAS and ARCNXXXX address spaces.
Does anyone except me think the new address spaces running as IEESYSAS with STEPNAME as ARCN is strange. I have pursued this issue with IBM and they say that is just the way it is. It seems strange that we have nothing else in the system that runs in this way. Just wanted to know if it was just me being picky. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: IEESYSAS and ARCNXXXX address spaces.
Ummm. Maybe. The TCPIP NJE address spaces appear that way as well. Based on my simple-minded understanding of how these address spaces are created, that's just the way that it is. Does it cause some kind of operational difficulty? Larre Shiller US Social Security Administration -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: IEESYSAS and ARCNXXXX address spaces.
The only problem here is that when you look for a task you usually would look for the STC name(ARCN) task not ieesysas. It is also kind of strange to code security rules and wlm specifications for a STC that does not run with the the same name as the rule or specification. In our shop the Security team and also the cappacity planning team would not know to look for these tasks under the IEESYSAS jobname. It seems like this is going to be the way it is but just wanted to ask for other opinions. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: IEESYSAS and ARCNXXXX address spaces.
Well... although we use Top Secret and not RACF, I can see that our Security Administrators have defined these Started Tasks and I'm pretty sure that I told them to use the ARC* name and it appears to be working fine. We also have the ARC* address spaces defined in the WLM classification rules as ARC* and that is working as it should, as well. So, I think you should be able to accomplish your goal (no pun intended...) using the ARC* names. Perhaps somebody else has a different experience...? Larre Shiller US Social Security Administration -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: IEESYSAS and ARCNXXXX address spaces.
I forgot to mention... when I do a D A,ARC* command on one of our systems, I get (in part): IEE115I 12.04.15 2008.129 ACTIVITY 210 JOBS M/STS USERSSYSASINITS ACTIVE/MAX VTAM OAS 000670065600233 002030008200233/00500 00740 ARC1MIGR ARC1MIGR IEFPROC NSW * A=00A6 PER=NO SMC=000 PGN=N/A DMN=N/A AFF=NONE CT=00.24.52 ET=82.54.17 WUID=JOB61406 USERID=HSM WKL=SYSTEM SCL=SYSSTC P=1 RGP=N/A SRVR=NO QSC=NO ADDR SPACE ASTE=0A83A980 So your Operations folks should still be able to find these address spaces using the ARC* names. We are a JES3 shop and we use (E)JES as our SPOOL browser and I know that there is a difference in what you must search on in the activity panel using JOB name (ARC*) as opposed to the status panel (IEESYSAS), so if you are JES2 and are using another SPOOL browser product, there may be a difference there, too. I'll agree that this particular aspect is annoying. Larre Shiller US Social Security Administration -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: IEESYSAS and ARCNXXXX address spaces.
Casey Rhodes wrote: The only problem here is that when you look for a task you usually would look for the STC name(ARCN) task not ieesysas. It is also kind of strange to code security rules and wlm specifications for a STC that does not run with the the same name as the rule or specification. In our shop the Security team and also the cappacity planning team would not know to look for these tasks under the IEESYSAS jobname. It seems like this is going to be the way it is but just wanted to ask for other opinions. What are you seeing? These ARCx address spaces look perfectly normal in my environment: |ACTIVITY PHXHQ(MVS60) Paging 0 SIO 121 CPU 7/7 |Command === |Cmd JobName StepName ProcStep JobIDASID Pos DP Real Paging |--- / --- -- -- -- |ARC2DUMP ARC2DUMP IEFPROC S0390634 006C NS FE3MB.00 |ARC2BKUP ARC2BKUP IEFPROC S0390593 0064 NS FE6MB.00 |ARC1MIGR ARC1MIGR IEFPROC S0390497 0077 NS FE 300KB.00 |D A,ARC* |IEE115I 09.09.24 2008.129 ACTIVITY 882 | JOBS M/STS USERSSYSASINITS ACTIVE/MAX VTAM OAS |00010000442 00040000282/00040 00032 | ARC1CDSB ARC1CDSB IEFPROC NSW * A=006F PER=NO SMC=000 | PGN=N/A DMN=N/A AFF=NONE | CT=004.000S ET=78.09.21 | WUID=J0390342 USERID= | WKL=SYSTEM SCL=SYSSTC P=1 | RGP=N/A SRVR=NO QSC=NO | ADDR SPACE ASTE=3C902BC0 | ARC1BKUP ARC1BKUP IEFPROC NSW * A=0029 PER=NO SMC=000 | PGN=N/A DMN=N/A AFF=NONE | CT=337.185S ET=78.07.48 | WUID=J0390348 USERID= | WKL=SYSTEM SCL=SYSSTC P=1 | RGP=N/A SRVR=NO QSC=NO | ADDR SPACE ASTE=3C903A40 | ARC1MIGR ARC1MIGR IEFPROC NSW * A=0077 PER=NO SMC=000 | PGN=N/A DMN=N/A AFF=NONE | CT=005.900S ET=64.08.47 | WUID=J0390497 USERID= | WKL=SYSTEM SCL=SYSSTC P=1 | RGP=N/A SRVR=NO QSC=NO | ADDR SPACE ASTE=3C902DC0 -- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 [EMAIL PROTECTED] http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: IEESYSAS and ARCNXXXX address spaces.
IIRC, if you look at these jobs via SDSF you will see the name IEESYSAS. If you use (E)JES you will see the correct jobname (free plug for Ed). As Ed has shown, they should display =correctly using a D A command. Bob Shannon Rocket Software -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: IEESYSAS and ARCNXXXX address spaces.
IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU wrote on 05/08/2008 12:39:07 PM: IIRC, if you look at these jobs via SDSF you will see the name IEESYSAS. If you use (E)JES you will see the correct jobname (free plug for Ed). As Ed has shown, they should display =correctly using a D A command. We just investigated this recently. For a started task, the procname is normally used as the jobname. However, some special processing is done when the procname is IEESYSAS. ASCRE and the START command replace the procname with the stepname when the procname is IEESYSAS, so that the step name is what ends up in the CHCLS (in the CSCB), ASSBJBNS, and the CSCX ( in the field pointed to by ASCBJBNS). Unfortunately, the START command does not replace IEESYSAS with the step name on the jobcard that it passes to JES2/JES3. So from at least JES2's point of view (I don't know about JES3, we were doing the investigation on a JES2 system), the jobname remains IEESYSAS, and that is what JES2 puts into the JSAB. SDSF gets the jobname from the JSAB if there is a JSAB. If there is no JSAB (i.e. SUB=MSTR was specified on the START command), SDSF gets the jobname from the CSCB. The D A command I think always gets the jobname from the CSCB. So the anomaly is due to IEEVSTAR (START command) replacing IEESYSAS with the stepname in the CSCB, but not replacing IEESYSAS on the jobcard. Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
