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
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
> $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
f
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
. 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
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
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
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
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
