ICH590A

Explanation
The APPLDATA field of one or more IRRPLEX_sysplex-name profiles,
which are not for this sysplex, indicates 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 database
cannot be safely shared in data sharing mode with a system in another
sysplex, neither can a system in data sharing mode share a database
with a system that is not in data sharing mode.
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 in data sharing mode, 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
incorrectlythe profile name indicates a sysplex that is not sharing the database
the APPLDATA field indicates data sharing mode (anything that
begins with a “D”), but the system is not in data sharing mode

an automated update of one or more IRRPLEX_ profiles failed

Specify NODATASHARE if:another sysplex, which is in non-data sharing mode, is sharing
this database

Specify FAILSOFT if:the profiles are correct, and you must not use the database in
data sharing mode

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 database is being used by another
system, which is in data sharing mode in another sysplex, and this
system requests data sharing mode, the database becomes corrupted.
If systems on other sysplexes use the database in data sharing mode,
specify FAILSOFT to enter FAILSOFT mode. If systems on other sysplexes
use the database in non-data sharing mode, specify NODATASHARE to
enter non-data sharing mode.
If you specified FAILSOFT, then
to correct the situation either change the data set name table (ICHRDSNT)
to use a different database (if the database is being shared by another
sysplex), or ensure that all systems sharing the database are in non-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. You must use ONLYAT 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