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 : H CKPT1=... - UPDATE CURRENT CHECKPOINT SPECIFICATION WITH
Z4 : H CKPT2=... 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) SYSGRS2(1)
SYSIEFTS(2) SYSIGW00(4) SYSIGW01(2)
SYSIGW02(3) SYSIGW03(3) SYSIKJBC(2)
> SYSIOSPX(2) SYSIOS01(2) SYSJES(2) <==
SYSJ2$XD(1) SYSMCS(7) SYSMCS2(4)
SYSTTRC(2) SYSWLM(2) SYSXCF(2)
S0W3(1)
Z3 d xcf,sysplex
IXC336I 17.47.31 DISPLAY XCF 829
SYSPLEX ADCDPL
SYSTEM TYPE SERIAL LPAR STATUS TIME SYSTEM STATUS
S0W3 1090 5809 N/A 01/18/2024 17:47:31 ACTIVE TM=SIMETR
S0W1 1090 5809 N/A 01/18/2024 17:47:27 ACTIVE TM=SIMETR
SYSTEM STATUS DETECTION PARTITIONING PROTOCOL CONNECTION EXCEPTIONS:
OPERATING AS VM GUEST
d xcf,group,sysjes
IXC332I 17.58.31 DISPLAY XCF 835
> GROUP SYSJES: S0W1 S0W3
d xcf,group,jes2
IXC332I 17.59.02 DISPLAY XCF 557
GROUP JES2: JES2$S0W3
d xcf,group,jes2,all
IXC333I 17.43.15 DISPLAY XCF 554
INFORMATION FOR GROUP JES2
MEMBER NAME: SYSTEM: JOB ID: STATUS:
> JES2$S0W3 S0W3 JESXCF ACTIVE
d xcf,group,sysjes,all
IXC333I 14.47.13 DISPLAY XCF 002
INFORMATION FOR GROUP SYSJES
MEMBER NAME: SYSTEM: JOB ID: STATUS:
S0W1 S0W1 JESXCF ACTIVE
S0W3 S0W3 JESXCF ACTIVE
TIA,
Wendell
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
