l-# in HCD and things
connected up properly.
Here are a few other thoughts on the subject of the base sysplex setup. I can
understand the idea of trying to save money. We all have to deal with
management wanting not to spend money. So you do what you can with what you
have.
The idea of usin
List On Behalf Of
Allan Staller
Sent: Tuesday, June 2, 2020 7:57 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Base SYSPLEX setup
This message was sent from an external source outside of Western & Southern's
network. Do not click links or open attachments unless you recognize the sender and
On Sun, 31 May 2020 12:19:16 +, Feller, Paul
wrote:
> We found out the hard way when we converted off of FICON switches you need to
> code a serial number in the control unit definition to make
> the connection work properly.
>
Does lack of a serial number really prevent these from
Metz
Sent: Monday, June 1, 2020 11:42 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Base SYSPLEX setup
[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
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Allan Staller
Sent: Tuesday, June 2, 2020 7:57 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Base SYSPLEX setup
This message was sent from an external source outside of Western & Southern's
network. Do not click l
-MAIN@LISTSERV.UA.EDU
Subject: Re: Base SYSPLEX setup
[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.]
Brian,
1. If you haven't
I can speak from experience. GRS Ring performance sucks with even 2 LPARs
compared to GRS STAR.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Gibney, Dave
Sent: Monday, June 1, 2020 11:41 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Base SYSPLEX setup
[CAUTION
KB,
The question is about sysplex signalling by XCF. It is not about TCPIP
networking. XCF does not use TCPIP protocols.
SMC-D/R are for TCP networking
HiperSockets is for IP networking
Mike Wawiorko
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
kekronbekron
Staller wrote:
See the manuals "Setting up a SYSPLEX" and "Merging Systems Into A SYSPLEX".
Both can be found on the IBM zOS Library site.
Some key items not available in a base sysplex:
GRS START (use CTC for inter-image communication.
VTAM Generic resources, VTAM MNPS
RAC
Brian,
1. If you haven't also looked at IBM Publication No. SB10-7174 yet, I'd
refer you to that one ("IBM Z FICON Channel-to-Channel Reference"). I
believe you've found SG24-5451 already.
2. You might not need additional FICON Express features at all. It depends
on how you're set up, but
, 2020 12:36 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Base SYSPLEX setup
It's all about the cost. Especially right now, there is just no money to put
into the box. If we knew for sure that the software CF would only take 1MSU or
less, then we would do it in a heartbeat, but it's a base model
t; To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Base SYSPLEX setup
>
> It's all about the cost. Especially right now, there is just no money to put
> into
> the box. If we knew for sure that the software CF would only take 1MSU or
> less, then we would do it in a heartbeat, but it's a ba
D/R or
>HiperSockets or one of those ICA-SR (or whatever it's called) connectors IF 2
>machines are involved.
>
>
>- KB
>
>‐‐‐ Original Message ‐‐‐
>On Monday, June 1, 2020 6:29 PM, Allan Staller wrote:
>
>> See the manuals "Setting up a SYS
we know it's poor configuration. Old machine, small one.
>So, what is the reason for Sysplex? What goal to achieve?
>Sysplex takes some CPU, so for "pretty close to maxed out" CPC it is not
>very fine.
>IMHO it would be reasonable to consider purchase second hand CPC as
&
als "Setting up a SYSPLEX" and "Merging Systems Into A SYSPLEX".
> Both can be found on the IBM zOS Library site.
> Some key items not available in a base sysplex:
>
> GRS START (use CTC for inter-image communication.
> VTAM Generic resources, VTAM MNPS
> RACF
See the manuals "Setting up a SYSPLEX" and "Merging Systems Into A SYSPLEX".
Both can be found on the IBM zOS Library site.
Some key items not available in a base sysplex:
GRS START (use CTC for inter-image communication.
VTAM Generic resources, VTAM MNPS
RACF data s
one.
So, what is the reason for Sysplex? What goal to achieve?
Sysplex takes some CPU, so for "pretty close to maxed out" CPC it is not
very fine.
IMHO it would be reasonable to consider purchase second hand CPC as
standalone CF and some cards. Of course the question about the goal
The box isn't maxed out, but it's pretty close. It's a base z13s and no money
to upgrade it. The cards are a cheap way to get by (they are under $400 with
$0 increase in maintenance costs), whereas the cost of a CF is far greater. We
can't use the software CF option (build a CF lpar without
:
>
> Hi,
>
> I'm looking for information on how to set up a base SYSPLEX with only Ficon
> CTC's that seem to be referred to as XCF CTC's.
>
> I'm sure someone had done this before and is probably doing it now for
> Multiple LPARs that are running on the same processor CEC
for communications.
Thanks..
Paul Feller
GTS Mainframe Technical Support
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Gadi Ben-Avi
Sent: Sunday, May 31, 2020 2:18 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Base SYSPLEX setup [EXTERNAL]
Hi Brian,
When building a sysplex using
Hi Brian,
When building a sysplex using CTC's, each LPAR mist have connectivity to all of
the other LPARS.
If you have more than two LPARS, it gets complicated very fast.
I've always had to get help from IBM for defining the CTC's in HCD.
Once you have to connectivity defined, the rest
Hi,
I'm looking for information on how to set up a base SYSPLEX with only Ficon
CTC's that seem to be referred to as XCF CTC's.
I'm sure someone had done this before and is probably doing it now for Multiple
LPARs that are running on the same processor CEC. Configuration help (parms
etc
Thank you for all your patience with me.
Getting zOSMF up is a challenge at best in a MONOPLEX. In a SYSPLEX it is a
bit of a terror. I had use ISH to chain thru OMVS and find the bbgzangl
executable. Then modify the PATHS in the ANG1 and the SRV1 after more research
than I care
In order to share the files filesystem in read/write ( ie mounted to multiple
systems at once) you have be in shared sysplex filesystem and the file system
mounted rwshare. Otherwise the attempt to mount it in a second spot will
fail. Of course, none if this applies if you mount/unmount
I have zOSMF working in a MONOPLEX and that was a challenge to itself
especially with RACF.
It's time for a SYSPLEX. We have several PARMLIB's and the concatenation is
all the same on all the LPAR's as is the
PARMLIB suffix.
The zFS for zOSMF is shared R/W, the Libery zFS os READONLY
Thank-you all for your responses. Again the IBM-Main community shows it's
strength.
I think I'll be sticking with ECS at the moment.
Much appreciated,
Peter
--
For IBM-MAIN subscribe / signoff / archive access instructions,
oet,
Kees Vernooij
KLM Information Services
z/OS Systems
Tel +31 6 10 14 58 78
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of R.S.
Sent: 24 April 2020 11:20
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Catalogs in parallel sysplex ECS vs RLS
W dniu 23.04.2020 o 16:
W dniu 23.04.2020 o 16:29, Peter Vander Woude pisze:
Ok, building parallel sysplex. For the catalogs I am planning on using ECS for
the shared catalogs (which is all of them).
What is the recommended method for handling the catalogs in a parallel sysplex,
ECS or VSAM RLS?
What
: Catalogs in parallel sysplex ECS vs RLS
Ok, building parallel sysplex. For the catalogs I am planning on using ECS for
the shared catalogs (which is all of them).
What is the recommended method for handling the catalogs in a parallel sysplex,
ECS or VSAM RLS?
Thanks,
Peter
system in the sysplex, the
associated catalog request will fail with return code RC4 and reason code
RSN124. If a catalog is currently in either ECS mode or VVDS mode and is shared
by a system that cannot support RLS for catalogs, the attempt to use the
catalog in RLS mode will also fail
, April 23, 2020 9:29 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Catalogs in parallel sysplex ECS vs RLS
[CAUTION: This Email is from outside the Organization. Do not click links or
open attachments unless you trust the sender.]
Ok, building parallel sysplex. For the catalogs I am planning on using
Ok, building parallel sysplex. For the catalogs I am planning on using ECS for
the shared catalogs (which is all of them).
What is the recommended method for handling the catalogs in a parallel sysplex,
ECS or VSAM RLS?
Thanks,
Peter
: Re: Sysplex Maintenance and USS
In a read/write sysplex aware root file system, For file systems that come with
the OS, we mount our filesystems as follows:
/* IBM Liberty Imbedded
MOUNT FILESYSTEM('SYS1.IBM.ZOS.')
MOUNTPOINT('//usr/lpp/liberty_zos')
MODE(READ) TYPE(ZFS
In a read/write sysplex aware root file system, For file systems that come with
the OS, we mount our filesystems as follows:
/* IBM Liberty Imbedded
MOUNT FILESYSTEM('SYS1.IBM.ZOS.')
MOUNTPOINT('//usr/lpp/liberty_zos')
MODE(READ) TYPE(ZFS)
PARM('AGGRFULL(99,1
Symlinks are you friend.
Mount your product files to /$VERSION/usr/lpp/ etc
the symlink ./usr/lpp/xxx to the required version mounted filesystem
Hope that gives you pointers
Regards
Bruce
--
For IBM-MAIN subscribe / signoff
>So, how does one rollout maintenance in a sysplex one system at a time without
>disrupting the ability to access these products?
The way I do it for the links that weren't totally screwed up when I started
here:
at /usr/lpp I mount a 'links'-ZFS, i.e. /usr/lpp/java gets an
OMVS. ZFS m
Our USS file system tends to follow the one recommended in the USS Planning
Guide. When we bring up a system in our sysplex with new maintenance, the
VERSION root is mounted with all its related file systems. What I noticed
today though, is that our product related file systems, which
Message-
From: IBM Mainframe Discussion List On Behalf Of
Elaine Beal
Sent: Monday, February 3, 2020 12:58 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: DR Sysplex Procedure
CAUTION EXTERNAL EMAIL
Thanks all.
We were able to issue the start policy for the DR policy and all went well
Thanks all.
We were able to issue the start policy for the DR policy and all went well!
till we got to the network :)
Elaine
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to
Thank you.
I believe you may have hit on our issue.
We're getting the in use for the LOGR which is not new and I am okay with that.
I'm confident we're picking up the DR COUPLExx but we've never had the POLICY
statement.
We were planning on issuing the SETXCF START with the new policy name.
The
These recommendations are culled from the procedure we've used for 20 years.
-- With a new (empty) CFRM data set, you should not see any reference to the
production policy.
-- 'IN USE BY ANOTHER SYSPLEX' suggests that you are pointing to (a copy of)
the prod version, not the DR version
Unless we're picking up the wrong COUPLE member, the CFRM and XCF
are pointing to the DR datasets
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO
on
01/23/2020 12:39:56 PM:
> From: Elaine Beal
> To: IBM-MAIN@LISTSERV.UA.EDU
> Date: 01/23/2020 12:40 PM
> Subject: [EXTERNAL] Re: DR Sysplex Procedure
> Sent by: IBM Mainframe Discussion List
>
> To expand on this...
> yes, we are just getting to the DR test:)
>
number, policy
> but no new LOGR and WLM, using same as prod (on another machine)
>
> defined a new policy in DR CFRM
>
> We IPLd at the other site for DR and got the following-
>
> IXC248E COUPLE DATA SET dsname ON VOLSER volser FOR typename MAY BE IN
> USE BY ANOTHER SYSPLEX.
&
the following-
IXC248E COUPLE DATA SET dsname ON VOLSER volser FOR typename MAY BE IN USE BY
ANOTHER SYSPLEX.
IXC247D REPLY U to ACCEPT USE OR D TO DENY USE OF THE COUPLE DATA SET FOR
typename.
to which both are replied to with U
ISG379E GRS UNABLE TO CONNECT TO THE ISGLOCK STRUCTURE. VALIDATE
IBM Mainframe Discussion List On
> > Behalf Of R Hey
> > Sent: Wednesday, December 18, 2019 12:51 PM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: ZOS 1.13 2.2 2.3 in the same sysplex
> >
> > Yes, HSM is used, but not installed/used during my tests.
> >
.2 2.3 in the same sysplex
>
> Yes, HSM is used, but not installed/used during my tests.
> I didn't do much with zos 2.3, didn't create new DS in CAT's, etc.
> Just log'd on to TSO/SDSF to look at syslog.
> Client is forced to use 1.13 due to their APP not supporting zos 22. They are
&g
Yes, HSM is used, but not installed/used during my tests.
I didn't do much with zos 2.3, didn't create new DS in CAT's, etc.
Just log'd on to TSO/SDSF to look at syslog.
Client is forced to use 1.13 due to their APP not supporting zos 22. They are
planning to upgrade it, but could take a while.
On Behalf Of
Mark Jacobs
Sent: Tuesday, December 17, 2019 7:06 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ZOS 1.13 2.2 2.3 in the same sysplex
EXTERNAL EMAIL
Until some shared resource breaks. Not saying it'll happen, but it might.
Mark Jacobs
Sent from ProtonMail, Swiss-based encrypted email
Out of curiosity: what is the reason?
Why to connect 3 different system levels in one sysplex?
It is unsupported - we know that.
It is somehow hard.
It is somehow risky - we are aware about that also .
Why not upgrade 1.13 system to current one and then connect it to the
sysplex?
Yes, upgrade
To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: ZOS 1.13 2.2 2.3 in the same sysplex
>
> I had build a new plex on zos 1.13, new CF, XCF CDS, SMS, RMM, RACF, Mcat,
> etc, with only 1 LPAR in it.
> IPL’d the same LPAR with zos 22 sysres/Mcat: OK IPL’d the same LPAR with
> zos 23 sys
ecember 17, 2019 5:59 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ZOS 1.13 2.2 2.3 in the same sysplex
I had build a new plex on zos 1.13, new CF, XCF CDS, SMS, RMM, RACF, Mcat, etc,
with only 1 LPAR in it.
IPL’d the same LPAR with zos 22 sysres/Mcat: OK IPL’d the same LPAR with zos 23
sysres/Mcat
@LISTSERV.UA.EDU
Subject: Re: ZOS 1.13 2.2 2.3 in the same sysplex
**CAUTION EXTERNAL EMAIL**
**DO NOT open attachments or click on links from unknown senders or unexpected
emails**
I had build a new plex on zos 1.13, new CF, XCF CDS, SMS, RMM, RACF, Mcat, etc,
with only 1 LPAR in it.
IPL’d the same LPAR
. Remember that the levels supported by 2.3 will be higher than 1.13, so you
have to run at the levels that match between those two, but you obviously know
about this as you are already running a mixed release sysplex.
Let me know how it goes,
Brian
I had build a new plex on zos 1.13, new CF, XCF CDS, SMS, RMM, RACF, Mcat, etc,
with only 1 LPAR in it.
IPL’d the same LPAR with zos 22 sysres/Mcat: OK
IPL’d the same LPAR with zos 23 sysres/Mcat: OK
IPL’d the same LPAR with zos 22 sysres/Mcat: OK
IPL’d the same LPAR with zos 1.13
If you try and add an LPAR to a sysplex without having applied the relevant
coexistence maintenance, you get a 082 wait state at IPL. See
description below.
If you try to add a system that is not even in the compatibility matrix, I
would guess the same...
082
Explanation
The system entering
I am not at all an expert on Sysplex compatibility. I bring to the table only
the knowledge of the IBM policy and years of experience with "how things work."
I think the answer is very simple: it might work and it might not. Or, more
correctly, it might IPL, and if it does, then ever
Add to this the H/W and CFCC levels of the different systems. While the
'newest' release of z/OS in the Sysplex will support the highest level of the
CFCC level in the Sysplex, does 1.13 support it?
IBM normally tests up to n-2 levels/generations of OS and H/W. Combination of
older levels MAY
Until some shared resource breaks. Not saying it'll happen, but it might.
Mark Jacobs
Sent from ProtonMail, Swiss-based encrypted email.
GPG Public Key -
https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com
‐‐‐ Original Message ‐‐‐
On Tuesday, December 17, 2019 3:14
I don't think there is any check for that. I believe that z/OS isn't that
smart when it comes to figuring that stuff out, and actually I can't really
think of a reason why it wouldn't work. Remember, just because IBM doesn't say
they "support" something, doesn't necessarily mean it doesn't
Not only is z/OS 1.13 not supported in the same sysplex with z/OS 2.3, I am
pretty sure it won’t work. Every release has sysplex changes which often
(always?) require PTFs to the prior 2 releases to participate in the same
sysplex. Even if no PTFs are required, I suspect z/OS checks to see
Thanks Mark,
Yes, I know.
My client is forced to use zos 1.13 for a while, they use it with with zos 2.2
in the same plex, which needs to be moved to zos 2.3.
Cheers
--
For IBM-MAIN subscribe / signoff / archive access
=markjac...@protonmail.com
‐‐‐ Original Message ‐‐‐
On Sunday, December 15, 2019 6:59 PM, R Hey
<00bb27d4e6cb-dmarc-requ...@listserv.ua.edu> wrote:
> Hi,
> Has anybody used these 3 versions of zos in 1 sysplex (CF, SMS, HSM, Ucats,
> etc ...) ?
&
Hi,
Has anybody used these 3 versions of zos in 1 sysplex (CF, SMS, HSM, Ucats, etc
...) ?
Cheers,
Reza
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message
s code, so from my perspective I
> have handcuffs on on some designs.
>
> Scott
>
> On Thu, Nov 28, 2019 at 10:29 AM scott Ford wrote:
>
>> Kees,
>>
>> I deal with customers who have questions and as i stated I am not a
>> Sysplex guy.
>> Secondly,
handcuffs on on some designs.
Scott
On Thu, Nov 28, 2019 at 10:29 AM scott Ford wrote:
> Kees,
>
> I deal with customers who have questions and as i stated I am not a
> Sysplex guy.
> Secondly, we are a ISV so we have help our customers and this one is huge.
> The point it was their q
or a shared CF
structure (or a shared Dasd dataset).
Kees.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of scott Ford
Sent: 28 November 2019 16:29
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Sysplex
Kees,
I deal with customers who have
Kees,
I deal with customers who have questions and as i stated I am not a Sysplex
guy.
Secondly, we are a ISV so we have help our customers and this one is huge.
The point it was their question. You can’t expect everyone to know what you
know, everyone has a different frame of reference.
Scott
.EDU
Date: 28/11/2019 14:17
Subject:[EXTERNAL] Re: Sysplex
Sent by:IBM Mainframe Discussion List
Speculation on my part but it I suspect they heard the term data sharing
and sysplex and assumed that data (in-memory) could be shared like a
subpool (231 in this case CSA / ECSA) ac
Speculation on my part but it I suspect they heard the term data sharing and
sysplex and assumed that data (in-memory) could be shared like a subpool (231
in this case CSA / ECSA) across LPARs.
Matt Hogstrom
PGP key 0F143BC1
> On Nov 28, 2019, at 04:11, David Crayford wrote:
>
&g
Sorry to nitpick Scott but "Sysplex" is a poor subject line for
newsgroup thread!
You should try to write more specific subject lines such as "Sharing
storage subpools in a Sysplex" which makes it much easier to understand
the context of threads.
On 2019-11-28 12:33 AM,
2019 18:04
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Sysplex
We use one of the system subpool SP 231 for holding messages we build from
various ESMs. The customer asked if we could share SP231 across LPARs.
My take was no because I understood sp231 was unique until each LPAR .
Scott
On Wed, Nov 27
If you have a requirement to share messages across members of a sysplex, and
the customer has a coupling facility, using notepad services might be something
to look at.
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieai600/oa3845078.htm
Sent from ProtonMail
ory.
>
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
>
>
>
> From: IBM Mainframe Discussion List on behalf
> of Charles Mills
> Sent: Wednesday, November 27, 2019 12:29 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
>
@LISTSERV.UA.EDU
Subject: Re: Sysplex
Each LPAR is from the OS's point of view another box on the other side of the
computer room. (Yes, you can quibble with that but it is a good way of thinking
about it for most practical purposes.) z/OS on LPAR A has almost no knowledge
of or visibility
:20 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Sysplex
SP231 is a part of address space. It is virtual memory. LPAR is
"hardware", so LPAR memory is real memory with no concepts like subpool,
Common Area, PVT, etc. More: LPAR can host any operating system,
including zLinux, which has
pts like subpool,
> Common Area, PVT, etc. More: LPAR can host any operating system,
> including zLinux, which has no address spaces, SP231, LPA, etc.
> To repeat: NO z/OS MEMORY MAPPED TO PHYSICAL LPAR MEMORY CAN BE SHARED
> IN SYSPLEX.
>
> --
> Radoslaw Skorupka
> Lodz, Pol
/OS MEMORY MAPPED TO PHYSICAL LPAR MEMORY CAN BE SHARED
IN SYSPLEX.
--
Radoslaw Skorupka
Lodz, Poland
W dniu 2019-11-27 o 18:03, scott Ford pisze:
We use one of the system subpool SP 231 for holding messages we build from
various ESMs. The customer asked if we could share SP231 across LPAR
>
> > Scott
> >
> > On Wed, Nov 27, 2019 at 11:56 AM Allan Staller
> > wrote:
> >
> >> Each LPAR has their own.
> >>
> >> SYSPLEX does not share (virtual or real) storage.
> >> Selected information is shared by XCF using CTC
ross LPARs.
> My take was no because I understood sp231 was unique until each LPAR .
>
> Scott
>
> On Wed, Nov 27, 2019 at 11:56 AM Allan Staller
> wrote:
>
>> Each LPAR has their own.
>>
>> SYSPLEX does not share (virtual or real) storage.
>> Selecte
has their own.
>
> SYSPLEX does not share (virtual or real) storage.
> Selected information is shared by XCF using CTC or Coupling Facility.
>
> HTH,
>
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf
> Of scott Ford
> Sent: Wednesday, Nov
Each LPAR has their own.
SYSPLEX does not share (virtual or real) storage.
Selected information is shared by XCF using CTC or Coupling Facility.
HTH,
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
scott Ford
Sent: Wednesday, November 27, 2019 10:33 AM
To: IBM-MAIN
W dniu 2019-11-27 o 17:33, scott Ford pisze:
I have a question related to storage subpool. If you running a sysplex do
you share one set of subpool, I.e., sp 1 ,,etc. or does each LPAR have its
own ?
I assumed the later.
I don't understand.
In Sysplex there is no shared memory. In Parallel
I have a question related to storage subpool. If you running a sysplex do
you share one set of subpool, I.e., sp 1 ,,etc. or does each LPAR have its
own ?
I assumed the later.
Scott
--
Scott Ford
IDMWORKS
z/OS Development
At one point, I had a setup that included a SITE system symbol in the CDSs
for XCF and CFRM to auto-resolve such things
Rob Schramm
Senior Systems Consultant
On Thu, Oct 17, 2019 at 12:41 PM Elaine Beal wrote:
> Yes, I would IPL with a different loadparm to point to COUPLExx with DR
> XCF
Yes, I would IPL with a different loadparm to point to COUPLExx with DR XCF and
CFRM
but WLM and LOGR would not change (use same ones as in current environment)
In falling back, I would use the same current (not DR) XCF/CFRM/WLM/LOGR
so I would use the same LOGR and WLM for DR and 'prod'
no
Are you talking LOGR and WLM CDS's in the couplexx member?
if so as long as they are defined in the DR's COUPLExx member
Carmen Vitullo
- Original Message -
From: "Elaine Beal"
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Wednesday, October 16, 2019 11:52:43 AM
Subject: Re:
So, both systems down
IPL LPAR1 with new XCF and CFRM, use existing LOG and WLM files
Will that cause an issue falling back?
by using the same LOG and WLM files?
Thanks,
Elaine
--
For IBM-MAIN subscribe / signoff / archive
Kees, thank you. I see that would not work and it would be better to have both
systems down and IPL one at a time.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with
"Do both LPARs need to be down (not desirable) before IPLing either of them
with the new CF and XCF?"
I would try to test the real situation as much as possible.
Besides, I think it will not work. LPAR's don't join each other, they join a
Sysplex. After ipling one system wi
We are planning to test a remote copy sysplex environment and I would like to
test it in our home DEV environment
PROD data will not be accessible during the DR test so PROD sysplex should not
be affected
To test in DEV I have defined a new XCF and CFRM since I will need to do that
for DR
Thanks everyone.
We have Managed to create $SYSNAME using ish to map it to $SYSNAME/ but only
after changing my OMVS home to sysplex root.
Just a follow up question, is there a way we can protect users to default to
System Root rather than SYSPLEX Root...e.e a user doing cd / should go
Here is an example of what we are using.
VERSION('')
SYSPLEX(YES)
ROOT FILESYSTEM('OMVS.PPLEX01.ROOT')
MODE(RDWR)
TYPE(ZFS
there's some very good doc online 'setting up a sysplex' and samples in the
samplib to create all the necessary symbolic links and examples of parmlib
(BPXPRMxx) to use $VERSION and $SYSNAME.
Carmen Vitullo
- Original Message -
From: "Munif Sadek"
To: IBM-MAIN@LISTS
I can not find my syspex OMVS symbols $SYSNAME and $VERSION. Did IPL one of
the system in the PLEX still not $SYSNAME $VERSION links.
Does anyone know how to create it.
regards
Munif
--
For IBM-MAIN subscribe / signoff /
Problem resolved.
I needed to tweak my IKJCNXAC exit to turn off bits that are on by default.
Once I did an "NI" on that flag byte, the REXX Exec could process the CONSLE
command while in a Sysplex.
I guess those bits don't matter in a non-sysplex environment.
Thanks for the help
S. V
AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Batch REXX, Consoles & SYSPLEX
I have a REXX Exec that is run in a batch job, that is invoked from a MPF exit
after the 'BPXI004I OMVS Initialization Complete' message is displayed.
The REXX Exec determines what processor and LPAR it is in and is
NNAME#*) ... and look for possible
>sysplex-wide conflicts ...
Ah, yes. Thanks. It was a lng time ago I looked around in those GRS
parmlib members.
Seemed there is an ENQ on my last few brain cells... ;-)
Groete / Greet
E=SYSZCNZ and RNAME=CONNAME#consolename.
One has to issue...
D GRS,RES=(SYSZCNZ,CONNAME#*)
...and look for possible sysplex-wide conflicts...
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Veryl Ellis wrote:
>The REXX Exec determines what processor and LPAR it is in and issues a
>'CONSOLE ACTIVATE', 'CONSOLE SYSCMD... (to start the appropriate TCPIP)' and a
>'CONSOLE DEACTIVATE'.
Please post the full commands+keywords as used for these 3 CONSOLE.
>IKJ55303I CONSOLE command
201 - 300 of 858 matches
Mail list logo
