ICH588A

Explanation
There are two explanations. Either:
If the named profile is for this sysplex and you are changing
your sysplex from non-data sharing mode into data sharing mode, it
is normal to receive this message. To ensure that your database avoids
corruption you must determine if the databases are being shared by
other sysplex members that are not enabled for RACF® sysplex communication. Systems that are
enabled for RACF sysplex communication
are members of the XCF IRRXCF00 group.First determine which systems
are sysplex members, but not IRRXCF00 group members. To display sysplex
members, enter the following command from the master console:D XCF,SYSPLEX
To
display group members, enter the following command from the master
console:D XCF,GROUP,IRRXCF00
Next issue an RVARY
LIST command from the systems in the sysplex that are not IRRXCF00
group members. This indicates if the systems are using the same databases
as the systems within the group. If there are systems using the same
databases, this is because either:The data set name table (ICHRDSNT) of the other systems sharing
the databases did not specify RACF sysplex
communication during IPL (the databases are used in the same mode
as the group). Or,
This sysplex should not be in data sharing mode. Or,
One of the systems specified an incorrect RACF database in the data set name table (ICHRDSNT)

Or:

The APPLDATA field of one or more IRRPLEX_sysplex-name profiles,
which are not for this sysplex, indicates non-data sharing mode. This
system is currently changing to data sharing mode. The data set name
table (ICHRDSNT) for this system specifies data sharing mode. A system
in data sharing mode cannot safely share a database with a system
in another sysplex. Other IRRPLEX profiles are incompatible with the
data sharing mode requested for the initialization of this environment.Note: If
the message indicates an IRRPLEX_sysplex-name profile,
which is not for this sysplex, you must also follow the procedures
in explanation 1 (assessing the systems in this sysplex).

The ICH600A WTOR is issued after this message to obtain a
response.
Specify CONTINUE if:you copied the database from an environment that shared the database
with another sysplex, but which is no longer true for this environment.
the sysplex was renamed, and the old IRRPLEX_sysplex-name profile
was detected.
one or more IRRPLEX_ profiles were manually altered or created.
They indicate a sysplex (in the profile name) that is not sharing
the database.
no other IRRPLEX_sysplex-name profiles were
found, and all sysplex members are enabled for RACF sysplex communication.

To change the system into non-data sharing mode, specify
NODATASHARE if:the profiles are correct, and you must not use the database in
data sharing mode.
there are sysplex members that are not enabled for RACF sysplex communication but share this database.

System action
The system waits for the operators reply.

Operator response
Respond to the ICH600A message or contact
your systems programmer.

System programmer response
If the identified database is being
used by another system, which is in another sysplex, and this system
requests data sharing mode, the database becomes corrupted. You must
specify NODATASHARE to protect the database. If you must use data
sharing mode on this system, but the database is being used by another
sysplex, then after specifying NODATASHARE to the accompanying ICH600A
WTOR, either:change the data set name table (ICHRDSNT) for the systems on the
other sysplex, and then reIPL those systems. Or,
if, at this time, you cannot reIPL the systems on the other sysplex,
you can follow the directions for copying your database (primary and
backup) in the z/OS Security Server RACF System Programmer's Guide.
This explains how to put the new copies onto different volumes. However,
if you want to use databases with different names, the data set name
table (ICHRDSNT) must still be changed to prevent this problem when
you reIPL the other systems.

The IRRPLEX_ profiles on the other sysplexes can be deleted from
this database. You must then issue an RVARY DATASHARE command on this
system.
If there are sysplex members that share this database,
which is not enabled for RACF sysplex
communication, you must also specify NODATASHARE to protect the database.
If you need to use data sharing mode on this system, but the database
is being used by a system, which is not enabled for RACF sysplex communication, then after specifying
NODATASHARE to the accompanying ICH600A WTOR:if the other systems need to share this database, change the data
set name table (ICHRDSNT) for systems that are not enabled for RACF sysplex communication, to
request RACF sysplex communication,
and then reIPL the systems. Or,
if the other systems do not need to share this database, they
must use a different database. Follow the preceding instructions for
changing databases when sharing from another sysplex.

You can then issue an RVARY DATASHARE command on this system.
If
the identified database is not being used by a system that is either
in another sysplex, or is on this sysplex but not enabled for RACF sysplex communication, specify
CONTINUE. After initialization, you can use the RDELETE command to
delete extraneous IRRPLEX_sysplex-name profiles.
The IRRPLEX_sysplex-name profile for this sysplex
is updated automatically during initialization.
If the message
indicates the backup database, and you did not receive this message
for the primary database, then if the backup database is intended
to be the same as the primary database, and you were able to specify
‘CONTINUE’ to this message, resynchronize the primary and the backup
databases using "IRRUT200 PARM=ACTIVATE".Note: Ensure that the database
you are using as the backup database is the correct database to be
using with your primary database. The "IRRUT200 PARM=ACTIVATE" overlays
all the data within the specified backup data set. See z/OS Security Server RACF System Programmer's Guide for
more information about IRRUT200.
If the problem persists, contact
your IBM® support center.
Do
not use RRSF to propagate the RDEFINE, RALTER, and RDELETE commands
to other databases. If automatic command direction is enabled for
the GXFACILI class, use the ONLYAT operand (on the RALTER, RDEFINE,
and RDELETE commands) when you change IRRPLEX_sysplex-name profiles
to prevent this propagation. ONLYAT must be used whether you are altering,
creating, or deleting the class GXFACILI IRRPLEX_sysplex-name profiles
on a local or remote node.

Routing code
2

Descriptor code
1