Please issue TSO command 'RVARY LIST' on both LPARs. There should be no
indication of data sharing in the response on either system. That's what I
see in my basic sysplex.
Sharing options are indicated in bit flags in module ICHRDSNT. Even though
you are using the same RACF data base as named in ICHRDSNT, if you have two
different copies of the module, the bits may be different in the two
versions. That is, LPAR2 may be set to allow sharing, while LPAR1 is not.
.
.
JO.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
jo.skip.robin...@sce.com
"Staller, Allan"
<allan.stal...@kb
M1.COM> To
Sent by: IBM IBM-MAIN@bama.ua.edu
Mainframe cc
Discussion List
<ibm-m...@bama.ua Subject
.edu> RACF Newbie question
05/07/2009 02:17
PM
Please respond to
IBM Mainframe
Discussion List
<ibm-m...@bama.ua
.edu>
I am in the process of setting up a basic sysplex. (no Coupling Facility
available) from 2 separate monoplexes.
In the process of attempting to share the RACF database (in non
data-sharing mode) I am seeing something strange.
On LPAR1 of the SYSPLEX RACF comes up with no indication of data sharing
mode. On LPAR2 of the same sysplex, message IRRX005I
is issued indicating that LPAR2 is in the desired mode.
ICHRDSNT has been validated as correct (and identical) on both LPARs. I
have verified that the same database is in use.
In this particular case, LPAR1 was the 1st LPAR IPL'ed into the sysplex.
Just to test I re-initialized the sysplex with LPAR2 as the 1st system.
Same results. i.e. Message IRRX005I only appears on LPAR2.
Is message IRRX005I to be expected on all LPARs in the RACFplex? If so,
can somebody point me in the right direction to get both LPARs to issue
IRRX005I?
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
