ICH589A

Explanation
There are two explanations. Either:The named profile is for this sysplex. It is possible that an
RVARY command or an IPL of a system that runs z/OS® R10 or later, changed the system mode to
non-data sharing mode. However, an RVARY DATASHARE command is issued
from a system that runs a version before z/OS R10. Only z/OS R10
or later can automatically update the profile. As a result, the profile
is not updated and does indicate the actual system mode. Therefore,
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 RACF sysplex communication, and because it is
not the first system to join the XCF group IRRXCF00, the databases
and the current mode are communicated by the group data set name table,
which reported that the group is in 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 that an IRRPLEX_sysplex-name profile,
which is not in 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
incorrectly.the profile name indicates a sysplex that is not sharing the database

no other IRRPLEX_sysplex-name profiles were
found, and all sysplex members are enabled for RACF sysplex communication.

Because other systems are enabled for RACF sysplex communication (members of the XCF
IRRXCF00 group), and in data sharing mode, the database might be corrupted.
When the system completes IPL, it might be in FAILSOFT mode. If so,
you must run IRRUT200 in copy and verify mode (specify SYSRACF and
SYSUT1 DD) against the primary data sets of the database. If the database
is corrupted, refresh it with a database that is not corrupted or
contact your IBM® service center.
Either do not share the database outside of the systems on this sysplex,
which are enabled for RACF sysplex
communication, or do not allow data sharing mode.
Specify FAILSOFT
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
The database can become corrupted
in the following situations:If the identified database is being used by another system, which
is in another sysplex, and this system requests data sharing mode.
Or,
Because the IRRXCF00 group of this system is in data sharing mode.

To protect the database, specify FAILSOFT to enter FAILSOFT
mode. You must run IRRUT200 in copy and verify mode (specify SYSRACF
and SYSUT1 DD) against the data sets of the database. If the database
is corrupted, refresh it with a database that is not corrupted or
contact your IBM service center.
Either do not share the database outside of the systems on this sysplex,
which are enabled for RACF sysplex
communication, or do not allow data sharing mode.
If the identified
database is not being used by a system outside of this sysplex, specify
CONTINUE. After initialization, use the RDELETE or RALTER command
on the IRRPLEX_ profiles, as appropriate. The IRRPLEX_ 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