On Wed, 17 Jun 2015 03:37:48 -0500, Jorge Garcia wrote:
I've found more information about GRS configuration between systems outsite
GRS complex: http://www-01.ibm.com/support/docview.wss?uid=isg1II14297
The information APAR says there is a possible GRSRNLxx configuration. I
suppose is not
Hello:
I've found more information about GRS configuration between systems outsite
GRS complex: http://www-01.ibm.com/support/docview.wss?uid=isg1II14297
The information APAR says there is a possible GRSRNLxx configuration. I suppose
is not dangerous. It's a IBM APAR.
Regards
Shane Ginnane wrote:
The information APAR says there is a possible GRSRNLxx configuration. I
suppose is not dangerous. It's a IBM APAR.
Suppose again. That APAR is *very* specific to catalogs and the way they are
processed. It is *NOT* generic for sharing outside a GRSplex.
Shane, it is a
W dniu 2015-06-12 o 21:34, Gibney, David Allen,Jr pisze:
Sharing without serialization can lead to errors. It's even worse with PDSE
outside Sysplex
On the other hand, here where there are only two of us who could possibly
update the IODF (and I usually leave it to the other guy)
We get away
Hello:
I've reviewed all the post and the best option is the HCD export/import in the
productions monoplex. If all the IODFs have the same HLQ yoy can do dynamic
activation and it' no necessary to do a ipl. The user catalog among sysplex is
dangerous. I agree with us.
Thanks for your posts!!
Grijn, Bart (B)
Sent: Friday, June 12, 2015 5:27 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Share IODF in different sysplex same CPC
Seeing that I originally suggested using a shared catalog in this thread, I
have
to ask why people believe this is a dangerous setup for the topic at hand
:46
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Share IODF in different sysplex same CPC
Hello:
I've reviewed all the post and the best option is the HCD export/import in the
productions monoplex. If all the IODFs have the same HLQ yoy can do dynamic
activation and it' no necessary to do a ipl
Of van der Grijn, Bart (B)
Sent: Friday, June 12, 2015 5:27 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Share IODF in different sysplex same CPC
Seeing that I originally suggested using a shared catalog in this thread, I
have
to ask why people believe this is a dangerous setup for the topic
Hello:
We are involved in a new proyect with the target of add three new system
(monoplex) in our configuration. Our actual configuration is: one production
sysplex with four lpar, one test sysplex with two lpars and next year another
three systems in monoplex. Now, when we activate a new
] On Behalf
Of Jorge Garcia
Sent: Thursday, June 11, 2015 6:58
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Share IODF in different sysplex same CPC
Hello:
We are involved in a new proyect with the target of add three new system
(monoplex) in our configuration. Our actual configuration is: one production
Hi Jorge. The IODF must be *catalogued* on each system, but it doesn't have to
be in the same catalog.
I prefer HCD Export to transmit the IODF to the other system then HCD import
it. You can also repro it to a flat file, ftp that, then repro it back out on
the other system. Here's my batch
In 5670874248161270.wa.jgarci12mapfre@listserv.ua.edu, on
06/11/2015
at 08:20 AM, Jorge Garcia jgarc...@mapfre.com said:
Yes. Our target is to do dynamic activation in the new systems. We've
seen in the Redbook HCD and Dynamic I/O reconfiguration it's not
possible if you don't share the
Hello Bart:
Yes. Our target is to do dynamic activation in the new systems. We've seen in
the Redbook HCD and Dynamic I/O reconfiguration it's not possible if you don't
share the iodf user catalog. It's mandatory has the same HLQ in all systems and
the only way is share a user catalog like
On Thu, Jun 11, 2015 at 8:20 AM, Jorge Garcia jgarc...@mapfre.com wrote:
Hello Bart:
Yes. Our target is to do dynamic activation in the new systems. We've
seen in the Redbook HCD and Dynamic I/O reconfiguration it's not possible
if you don't share the iodf user catalog. It's mandatory has
Hello John and Mary:
Our requirements are (if it's possible). Updates in one and only IODF and then
transmit it to another systems. With this option we avoid updates in two o more
IODF and we save the IODF integrity.
The share user catalog option is the fast and easy way for dynamic activation
] On Behalf
Of Jorge Garcia
Sent: Thursday, June 11, 2015 8:35 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Share IODF in different sysplex same CPC
Hello John and Mary:
Our requirements are (if it's possible). Updates in one and only IODF and then
transmit it to another systems. With this option we
On 6/11/2015 11:34 AM, Jorge Garcia wrote:
Hello John and Mary:
Our requirements are (if it's possible). Updates in one and only IODF and
then transmit it to another systems. With this option we avoid updates in two o
more IODF and we save the IODF integrity.
The share user catalog option
AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Share IODF in different sysplex same CPC
On 6/11/2015 11:34 AM, Jorge Garcia wrote:
Hello John and Mary:
Our requirements are (if it's possible). Updates in one and only IODF and
then transmit it to another systems. With this option we avoid
:57 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Share IODF in different sysplex same CPC
On 6/11/2015 11:34 AM, Jorge Garcia wrote:
Hello John and Mary:
Our requirements are (if it's possible). Updates in one and only IODF and
then transmit it to another systems. With this option we avoid
19 matches
Mail list logo
