Re: How can I keep JES2 from being SYSPLEXed?
Thanks for the tips guys.
I am using the same node name ("JES2") on both systems--that's probably why the
XCFGRPNM parm was necessary. (I NJE with a VSE machine & when the 3.1 system
is the primary/only machine I'll move the CTC connection to the new system
without changing any of the VSE stuff.)
These are 2 development systems running under VM. No production at all. Once
everything is set up on the z/OS 3.1 system, we probably will rarely run the
2.5 system. I just need them up together once in awhile to test things using a
coupling facility, like VSAM/RLS between the 2 systems.
Thanks again!
Wendell
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: How can I keep JES2 from being SYSPLEXed?
On Sun, 21 Jan 2024 15:14:08 -0600, Wendell Lovewell wrote: >Thanks for your help Bruce and Paul. > >I was able to ask this to the IBM support team and they told me about the >"XCFGRPNM" parm on the JES2 MASDEF statement. > >I hadn't specified a value for this, so both were using the default of "JES2". > This was causing the conflict, even though my intent was that they not be >part of the same MAS. > >Adding “XCFGRPNM=someuniqueval” to the MASDEF statements allowed both systems >to come up, apparently independently of each other. (I used JES2Z3 on my S0W3 >system and JES2Z4 on my S0W1 system.) > >I did a cold start on the S0W3 JES, and these Groups/Members were used: >GROUP SYSJES MEMBER S0W3 >GROUP JES2Z3 MEMBER JES2$S0W3 >GROUP SYSJ2$XD MEMBER JES2Z3$S0W3$ > >I did not do a cold start on the S0W1 JES, and I believe it used the >former/default value: >GROUP SYSJES MEMBER S0W1 >GROUP JES2 MEMBER JES2$S0W1 >GROUP SYSJ2$XD MEMBER JES2$S0W1$$$ > > >Thanks again, >Wendell > I assume you had the same OWNNODE also? Because I thought XCFGRPNM defaulted to the OWNNODE.nodename if you don't code it. If you want to connect those two independent JES2 nodes, they are going to need a unique ownnode name. 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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: How can I keep JES2 from being SYSPLEXed?
> $HASP843 MASDEF OWNMEMB=S0W3,COLDVRSN=z/OS 2.5, > $HASP843 ENFSCOPE=SYSPLEX,SHARED=NOCHECK, > $HASP843 XCFGRPNM=JES2,ESUBSYS=HASP > > $HASP843 MASDEF OWNMEMB=S0W1,COLDVRSN=z/OS 3.1, > $HASP843 ENFSCOPE=SYSPLEX,SHARED=NOCHECK, > $HASP843 XCFGRPNM=JES2,ESUBSYS=HASP Have you verified that compatibility PTF's are installed between z/OS 2.5 & 3.1? Have you verified event notication (ENFSCOPE) is acceptable? Are you sure that you will never need both JES2 MAS running on the same LPAR at the same time? You might want to consider ESUBSYS. > $HASP792 JES2 HAS JOINED XCF GROUP JES2 THAT INCLUDES ACTIVE MEMBERS > THAT ARE NOT PART OF THIS MAS > MEMBER=JES2$S0W3,REASON=DIFFERENT COLD START TIME Message $HASP729 told you that each JES2 MAS requires a unique XCFGROUP. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: How can I keep JES2 from being SYSPLEXed?
Classification: Confidential Provide separate JES CKPT and Spool datasets for each "JESPLEX". You will also need separate NODES for NJE, lines, . You might also look at JES Checkpoint auto-tuning. HTH, -Original Message- From: IBM Mainframe Discussion List On Behalf Of Wendell Lovewell Sent: Friday, January 19, 2024 3:33 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: How can I keep JES2 from being SYSPLEXed? [CAUTION: This Email is from outside the Organization. Unless you trust the sender, Don’t click links or open attachments as it may be a Phishing email, which can steal your Information and compromise your Computer.] I have two systems that I want to share dasd and allow for VSAM RLS between the systems, but I don’t want to SYSPLEX JES2. I have MASDEF SHARED=NOCHECK. What else can I do to un-sysplex JES? Is it safe to delete the JES2 and/or SYSJES group definitions from XCF? I don't have a JES_CKPT_1 structure defined at all. Background: I’m trying to add a z/OS 3.1 (&SYSNAME S0W1) to a sysplex where z/OS 2.5 (Z3-&SYSNAME S0W3) is running, but ONLY for VSAM RLS. I don’t want to “plex” anything more than is needed for VSAM/RLS—not JES, not SYSLOG, not VTAM, not SMF or anything else. The systems are running fine stand-alone (each with their own set of disks, including the volume with the CDS), but when I try to use the same CDS disk between the systems, the first system comes up fine, but JES2 on the system brought up last complains that it cannot find the checkpoint datasets of the OTHER system: Z4 : H *$HASP284 JES2 INITIALIZATION CHECKPOINT DIALOG STARTED Z4 : H *$HASP277 JES2 CAN NOT FIND OR USE THE CHECKPOINT DATA SET(S) Z4 : H THAT WERE IN USE WHEN THE MAS WAS LAST ACTIVE BECAUSE VOLUME Z4 : H FOR CKPT1 NOT MOUNTED Z4 : H * Z4 : H CURRENT CHECKPOINT VALUES: Z4 : H CKPT1=(DSNAME=SYS1.HASPCKPT,VOLSER=B5SYS1,INUSE=YES), Z4 : H CKPT2=(DSNAME=SYS1.HASPCKP2,VOLSER=B5CFG1,INUSE=YES) Z4 : H * Z4 : H VALID RESPONSES ARE: Z4 : HCKPT1=... - UPDATE CURRENT CHECKPOINT SPECIFICATION WITH Z4 : HCKPT2=...THE VALUES USED WHEN JES2 MAS WAS LAST ACTIVE Z4 : H'RECONFIG' - THE CHECKPOINT DATA SET(S) THAT WERE IN USE Z4 : H WHEN JES2 WAS LAST ACTIVE ARE NO LONGER Z4 : H AVAILABLE (ALL-MEMBER WARM START ONLY) Z4 : H'CONT' - ATTEMPT INITIALIZATION WITH THE VALUES LISTED Z4 : H'TERM' - TERMINATE JES2 INITIALIZATION ON THIS MEMBER Z4 : H *04 $HASP272 ENTER RESPONSE (ISSUE D R,MSG=$HASP277 FOR RELATED MSG) "Z4" is the z/OS 3.1 system. The “B5SYS1” and “B5CFG1” volumes belong to the z/OS 2.5 system. If I bring up z/OS 3.1 with z/OS 2.5 down and then try to bring up z/OS 2.5, the same message is displayed except it identifies the volumes belonging to the other system. I can RECONFIG with the correct CKPT volumes, but it always ends with: Z4 : $HASP478 INITIAL CHECKPOINT READ IS FROM CKPT1 Z4 : (SYS1.HASPCKPT ON A3SYS1) Z4 : LAST WRITTEN THURSDAY, 18 JAN 2024 AT 21:57:08 (GMT) Z4 : $HASP792 JES2 HAS JOINED XCF GROUP JES2 THAT INCLUDES ACTIVE MEMBERS Z4 : THAT ARE NOT PART OF THIS MAS Z4 : MEMBER=JES2$S0W3,REASON=DIFFERENT COLD START TIME Z4 : $HASP428 CORRECT THE ABOVE PROBLEMS AND RESTART JES2 Z4 : IXZ0002I CONNECTION TO JESXCF COMPONENT DISABLED, Z4 : GROUP JES2 MEMBER JES2$S0W1 Z4 : $HASP9085 JES2 MONITOR ADDRESS SPACE STOPPED FOR JES2 Z4 : $HASP085 JES2 TERMINATION COMPLETE Like I said, I don't want a MAS at all--each JES2 should be separate. (This has already gone too long, but here are some displays that might help:) Both JES parms use the same MASDEF definition: MASDEF SHARED=NOCHECK, CKPTLOCK=INFORM, RESTART=NO, DORMANCY=(25,300), HOLD=10, LOCKOUT=1200 Z3 $dmasdef (If other system is down, after a cold start.) $HASP843 MASDEF > $HASP843 MASDEF OWNMEMB=S0W3,AUTOEMEM=OFF,CKPTLOCK=INFORM, $HASP843 COLDTIME=(2022.313,18:50:45),COLDVRSN=z/OS 2.5, $HASP843 ENFSCOPE=SYSPLEX,DORMANCY=(25,300),HOLD=10, > $HASP843 LOCKOUT=1200,RESTART=NO,SHARED=NOCHECK, <== $HASP843 SYNCTOL=120,WARMTIME=(2024.018,22:05:36), $HASP843 XCFGRPNM=JES2,QREBUILD=0,CYCLEMGT=MANUAL, $HASP843 ESUBSYS=HASP Z4 $DMASDEF (If other system is down, after a cold start.) Z4 : $HASP843 MASDEF Z4 : $HASP843 MASDEF OWNMEMB=S0W1,AUTOEMEM=OFF,CKPTLOCK=INFORM, Z4 : $HASP843 COLDTIME=(2024.019,21:00:02),COLDVRSN=z/OS 3.1, Z4 : $HASP843 ENFSCOPE=SYSPLEX,DORMANCY=(25,300),HOLD=10, Z4
Re: How can I keep JES2 from being SYSPLEXed?
Okay this wakes up some retired brain cells. Because tasks communicate across XCF (even when you don't know about it) they have to have a unique identifier for things to work properly. Some tasks will create a unique identifier by default and some will not. I forgot about that little item. I'm glad things are now working for you. Paul -Original Message- From: IBM Mainframe Discussion List On Behalf Of Wendell Lovewell Sent: Sunday, January 21, 2024 3:14 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: How can I keep JES2 from being SYSPLEXed? Thanks for your help Bruce and Paul. I was able to ask this to the IBM support team and they told me about the "XCFGRPNM" parm on the JES2 MASDEF statement. I hadn't specified a value for this, so both were using the default of "JES2". This was causing the conflict, even though my intent was that they not be part of the same MAS. Adding “XCFGRPNM=someuniqueval” to the MASDEF statements allowed both systems to come up, apparently independently of each other. (I used JES2Z3 on my S0W3 system and JES2Z4 on my S0W1 system.) I did a cold start on the S0W3 JES, and these Groups/Members were used: GROUP SYSJES MEMBER S0W3 GROUP JES2Z3 MEMBER JES2$S0W3 GROUP SYSJ2$XD MEMBER JES2Z3$S0W3$ I did not do a cold start on the S0W1 JES, and I believe it used the former/default value: GROUP SYSJES MEMBER S0W1 GROUP JES2 MEMBER JES2$S0W1 GROUP SYSJ2$XD MEMBER JES2$S0W1$$$ Thanks again, Wendell -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: How can I keep JES2 from being SYSPLEXed?
Thanks for your help Bruce and Paul. I was able to ask this to the IBM support team and they told me about the "XCFGRPNM" parm on the JES2 MASDEF statement. I hadn't specified a value for this, so both were using the default of "JES2". This was causing the conflict, even though my intent was that they not be part of the same MAS. Adding “XCFGRPNM=someuniqueval” to the MASDEF statements allowed both systems to come up, apparently independently of each other. (I used JES2Z3 on my S0W3 system and JES2Z4 on my S0W1 system.) I did a cold start on the S0W3 JES, and these Groups/Members were used: GROUP SYSJES MEMBER S0W3 GROUP JES2Z3 MEMBER JES2$S0W3 GROUP SYSJ2$XD MEMBER JES2Z3$S0W3$ I did not do a cold start on the S0W1 JES, and I believe it used the former/default value: GROUP SYSJES MEMBER S0W1 GROUP JES2 MEMBER JES2$S0W1 GROUP SYSJ2$XD MEMBER JES2$S0W1$$$ Thanks again, Wendell -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: How can I keep JES2 from being SYSPLEXed?
Hi Wendell, In our production sysplex we have 6 different JESplexes. One of those JES2 MASplex uses Checkpoint in the Coupling Facility. The other 5 all use DASD checkpoint datasets. Never had any sort of cross sysplex issues. Regards Bruce -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: How can I keep JES2 from being SYSPLEXed?
I'm not sure I have an answer for you at this time. But I do have a few questions. Are the JES2 checkpoint datasets for the two systems the same name? Are the VOLSERs the same name? I don't have access to any z/OS anymore but when I did, we had three different JES2 MAS in one sysplex and didn't have any issues. The checkpoint (and spool datasets) datasets had different names and the volumes everything was on had different VOLSERs. We even had a checkpoint structure for each MAS in our CF environment. We had full shared DASD between the different z/OS lpars. Paul -Original Message- From: IBM Mainframe Discussion List On Behalf Of Wendell Lovewell Sent: Friday, January 19, 2024 3:33 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: How can I keep JES2 from being SYSPLEXed? I have two systems that I want to share dasd and allow for VSAM RLS between the systems, but I don’t want to SYSPLEX JES2. I have MASDEF SHARED=NOCHECK. What else can I do to un-sysplex JES? Is it safe to delete the JES2 and/or SYSJES group definitions from XCF? I don't have a JES_CKPT_1 structure defined at all. Background: I’m trying to add a z/OS 3.1 (&SYSNAME S0W1) to a sysplex where z/OS 2.5 (Z3-&SYSNAME S0W3) is running, but ONLY for VSAM RLS. I don’t want to “plex” anything more than is needed for VSAM/RLS—not JES, not SYSLOG, not VTAM, not SMF or anything else. The systems are running fine stand-alone (each with their own set of disks, including the volume with the CDS), but when I try to use the same CDS disk between the systems, the first system comes up fine, but JES2 on the system brought up last complains that it cannot find the checkpoint datasets of the OTHER system: Z4 : H *$HASP284 JES2 INITIALIZATION CHECKPOINT DIALOG STARTED Z4 : H *$HASP277 JES2 CAN NOT FIND OR USE THE CHECKPOINT DATA SET(S) Z4 : H THAT WERE IN USE WHEN THE MAS WAS LAST ACTIVE BECAUSE VOLUME Z4 : H FOR CKPT1 NOT MOUNTED Z4 : H * Z4 : H CURRENT CHECKPOINT VALUES: Z4 : H CKPT1=(DSNAME=SYS1.HASPCKPT,VOLSER=B5SYS1,INUSE=YES), Z4 : H CKPT2=(DSNAME=SYS1.HASPCKP2,VOLSER=B5CFG1,INUSE=YES) Z4 : H * Z4 : H VALID RESPONSES ARE: Z4 : HCKPT1=... - UPDATE CURRENT CHECKPOINT SPECIFICATION WITH Z4 : HCKPT2=...THE VALUES USED WHEN JES2 MAS WAS LAST ACTIVE Z4 : H'RECONFIG' - THE CHECKPOINT DATA SET(S) THAT WERE IN USE Z4 : H WHEN JES2 WAS LAST ACTIVE ARE NO LONGER Z4 : H AVAILABLE (ALL-MEMBER WARM START ONLY) Z4 : H'CONT' - ATTEMPT INITIALIZATION WITH THE VALUES LISTED Z4 : H'TERM' - TERMINATE JES2 INITIALIZATION ON THIS MEMBER Z4 : H *04 $HASP272 ENTER RESPONSE (ISSUE D R,MSG=$HASP277 FOR RELATED MSG) "Z4" is the z/OS 3.1 system. The “B5SYS1” and “B5CFG1” volumes belong to the z/OS 2.5 system. If I bring up z/OS 3.1 with z/OS 2.5 down and then try to bring up z/OS 2.5, the same message is displayed except it identifies the volumes belonging to the other system. I can RECONFIG with the correct CKPT volumes, but it always ends with: Z4 : $HASP478 INITIAL CHECKPOINT READ IS FROM CKPT1 Z4 : (SYS1.HASPCKPT ON A3SYS1) Z4 : LAST WRITTEN THURSDAY, 18 JAN 2024 AT 21:57:08 (GMT) Z4 : $HASP792 JES2 HAS JOINED XCF GROUP JES2 THAT INCLUDES ACTIVE MEMBERS Z4 : THAT ARE NOT PART OF THIS MAS Z4 : MEMBER=JES2$S0W3,REASON=DIFFERENT COLD START TIME Z4 : $HASP428 CORRECT THE ABOVE PROBLEMS AND RESTART JES2 Z4 : IXZ0002I CONNECTION TO JESXCF COMPONENT DISABLED, Z4 : GROUP JES2 MEMBER JES2$S0W1 Z4 : $HASP9085 JES2 MONITOR ADDRESS SPACE STOPPED FOR JES2 Z4 : $HASP085 JES2 TERMINATION COMPLETE Like I said, I don't want a MAS at all--each JES2 should be separate. (This has already gone too long, but here are some displays that might help:) Both JES parms use the same MASDEF definition: MASDEF SHARED=NOCHECK, CKPTLOCK=INFORM, RESTART=NO, DORMANCY=(25,300), HOLD=10, LOCKOUT=1200 Z3 $dmasdef (If other system is down, after a cold start.) $HASP843 MASDEF > $HASP843 MASDEF OWNMEMB=S0W3,AUTOEMEM=OFF,CKPTLOCK=INFORM, $HASP843 COLDTIME=(2022.313,18:50:45),COLDVRSN=z/OS 2.5, $HASP843 ENFSCOPE=SYSPLEX,DORMANCY=(25,300),HOLD=10, > $HASP843 LOCKOUT=1200,RESTART=NO,SHARED=NOCHECK, <== $HASP843 SYNCTOL=120,WARMTIME=(2024.018,22:05:36), $HASP843 XCFGRPNM=JES2,QREBUILD=0,CYCLEMGT=MANUAL, $HASP843 ESUBSYS=HASP Z4 $DMASDEF (If other system is down, after a cold start.) Z4 : $HASP843 MASDEF Z4 : $HASP843 MASDE
How can I keep JES2 from being SYSPLEXed?
I have two systems that I want to share dasd and allow for VSAM RLS between the systems, but I don’t want to SYSPLEX JES2. I have MASDEF SHARED=NOCHECK. What else can I do to un-sysplex JES? Is it safe to delete the JES2 and/or SYSJES group definitions from XCF? I don't have a JES_CKPT_1 structure defined at all. Background: I’m trying to add a z/OS 3.1 (&SYSNAME S0W1) to a sysplex where z/OS 2.5 (Z3-&SYSNAME S0W3) is running, but ONLY for VSAM RLS. I don’t want to “plex” anything more than is needed for VSAM/RLS—not JES, not SYSLOG, not VTAM, not SMF or anything else. The systems are running fine stand-alone (each with their own set of disks, including the volume with the CDS), but when I try to use the same CDS disk between the systems, the first system comes up fine, but JES2 on the system brought up last complains that it cannot find the checkpoint datasets of the OTHER system: Z4 : H *$HASP284 JES2 INITIALIZATION CHECKPOINT DIALOG STARTED Z4 : H *$HASP277 JES2 CAN NOT FIND OR USE THE CHECKPOINT DATA SET(S) Z4 : H THAT WERE IN USE WHEN THE MAS WAS LAST ACTIVE BECAUSE VOLUME Z4 : H FOR CKPT1 NOT MOUNTED Z4 : H * Z4 : H CURRENT CHECKPOINT VALUES: Z4 : H CKPT1=(DSNAME=SYS1.HASPCKPT,VOLSER=B5SYS1,INUSE=YES), Z4 : H CKPT2=(DSNAME=SYS1.HASPCKP2,VOLSER=B5CFG1,INUSE=YES) Z4 : H * Z4 : H VALID RESPONSES ARE: Z4 : HCKPT1=... - UPDATE CURRENT CHECKPOINT SPECIFICATION WITH Z4 : HCKPT2=...THE VALUES USED WHEN JES2 MAS WAS LAST ACTIVE Z4 : H'RECONFIG' - THE CHECKPOINT DATA SET(S) THAT WERE IN USE Z4 : H WHEN JES2 WAS LAST ACTIVE ARE NO LONGER Z4 : H AVAILABLE (ALL-MEMBER WARM START ONLY) Z4 : H'CONT' - ATTEMPT INITIALIZATION WITH THE VALUES LISTED Z4 : H'TERM' - TERMINATE JES2 INITIALIZATION ON THIS MEMBER Z4 : H *04 $HASP272 ENTER RESPONSE (ISSUE D R,MSG=$HASP277 FOR RELATED MSG) "Z4" is the z/OS 3.1 system. The “B5SYS1” and “B5CFG1” volumes belong to the z/OS 2.5 system. If I bring up z/OS 3.1 with z/OS 2.5 down and then try to bring up z/OS 2.5, the same message is displayed except it identifies the volumes belonging to the other system. I can RECONFIG with the correct CKPT volumes, but it always ends with: Z4 : $HASP478 INITIAL CHECKPOINT READ IS FROM CKPT1 Z4 : (SYS1.HASPCKPT ON A3SYS1) Z4 : LAST WRITTEN THURSDAY, 18 JAN 2024 AT 21:57:08 (GMT) Z4 : $HASP792 JES2 HAS JOINED XCF GROUP JES2 THAT INCLUDES ACTIVE MEMBERS Z4 : THAT ARE NOT PART OF THIS MAS Z4 : MEMBER=JES2$S0W3,REASON=DIFFERENT COLD START TIME Z4 : $HASP428 CORRECT THE ABOVE PROBLEMS AND RESTART JES2 Z4 : IXZ0002I CONNECTION TO JESXCF COMPONENT DISABLED, Z4 : GROUP JES2 MEMBER JES2$S0W1 Z4 : $HASP9085 JES2 MONITOR ADDRESS SPACE STOPPED FOR JES2 Z4 : $HASP085 JES2 TERMINATION COMPLETE Like I said, I don't want a MAS at all--each JES2 should be separate. (This has already gone too long, but here are some displays that might help:) Both JES parms use the same MASDEF definition: MASDEF SHARED=NOCHECK, CKPTLOCK=INFORM, RESTART=NO, DORMANCY=(25,300), HOLD=10, LOCKOUT=1200 Z3 $dmasdef (If other system is down, after a cold start.) $HASP843 MASDEF > $HASP843 MASDEF OWNMEMB=S0W3,AUTOEMEM=OFF,CKPTLOCK=INFORM, $HASP843 COLDTIME=(2022.313,18:50:45),COLDVRSN=z/OS 2.5, $HASP843 ENFSCOPE=SYSPLEX,DORMANCY=(25,300),HOLD=10, > $HASP843 LOCKOUT=1200,RESTART=NO,SHARED=NOCHECK, <== $HASP843 SYNCTOL=120,WARMTIME=(2024.018,22:05:36), $HASP843 XCFGRPNM=JES2,QREBUILD=0,CYCLEMGT=MANUAL, $HASP843 ESUBSYS=HASP Z4 $DMASDEF (If other system is down, after a cold start.) Z4 : $HASP843 MASDEF Z4 : $HASP843 MASDEF OWNMEMB=S0W1,AUTOEMEM=OFF,CKPTLOCK=INFORM, Z4 : $HASP843 COLDTIME=(2024.019,21:00:02),COLDVRSN=z/OS 3.1, Z4 : $HASP843 ENFSCOPE=SYSPLEX,DORMANCY=(25,300),HOLD=10, Z4 : $HASP843 LOCKOUT=1200,RESTART=NO,SHARED=NOCHECK, <== Z4 : $HASP843 SYNCTOL=120,XCFGRPNM=JES2,QREBUILD=0, Z4 : $HASP843 CYCLEMGT=MANUAL,ESUBSYS=HASP Z3 d xcf,group IXC331I 17.49.11 DISPLAY XCF 833 GROUPS(SIZE): ATRRRS(3)COFVLFNO(2) DSNDPDG(2) EZBTCPCS(1)HSFIXC(1) IDAVQUI0(3) IGG0CAS(2) IGWXSGIS(4) IOEZFS(2) > ISTCFS01(1) IXCLO008(2) JES2(1) <== N1(3) SYSBPX(2) SYSDAE(4) SYSENF(2) SYSGRS(2)S
