ICH15033A

Explanation
The APPLDATA field of one or more IRRPLEX_ sysplex-name profiles
indicates data sharing mode. However, this system is in non-data sharing
mode. The data sharing mode indicators within the IRRPLEX_ profiles
are incompatible with the non-data sharing mode of this environment.
The
ICH15041A WTOR is issued after this message to obtain a response.
Specify
CONTINUE if:the named profile is for this sysplex, and the named database
is now to be used in non-data sharing mode.
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 is no longer in data sharing mode.
one or more IRRPLEX_ profiles were manually altered or created
incorrectly:the 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 CANCEL if:the named profile is for this sysplex, the database is being used
by this sysplex in data sharing mode, the system is not enabled for RACF® sysplex communication, but
you must be in RACF sysplex
communication. Update the data set name table (ICHRDSNT) to request RACF sysplex communication and
data sharing mode, and then reIPL the system.
the profiles are correct, the database is being used by this sysplex,
or another sysplex, in data sharing mode, and you must not use the
database. Update the data set name table (ICHRDSNT) to request a different
database, and then reIPL the system.

System action
The system waits for the reply of the operator.

Operator response
Respond to the ICH15041A message or contact
your system programmer.

System programmer response
If the identified database is being
used in data sharing mode by another system, the database becomes
corrupted in the following situations:The other system is in another sysplex.
The other system is in this sysplex, but this system is not enabled
for RACF sysplex communication
(which forced this system to use the databases and mode of the IRRXCF00 RACF sysplex communication group).

You must specify CANCEL to protect the database.Note: If the other system is in another sysplex, either change the data
set name table (ICHRDSNT) to use a different database, and then reIPL
the system, or issue an RVARY NODATASHARE command from the other sysplex.
If the other system is in this sysplex, but is not being used
in data sharing mode, change the data set name table (ICHRDSNT) to
request RACF sysplex communication
or data sharing mode, or both, and then reIPL the system. This causes
the IRRXCF00 group to be joined and the RACF sysplex
communication group data set name table, which must be in the correct
mode, to be used.

If the identified database is not being used in
data sharing mode, specify CONTINUE. After the RVARY, use the RDELETE
or RALTER command on the IRRPLEX_sysplex-name profiles
as appropriate. The IRRPLEX_sysplex-name profile
for this sysplex is updated automatically during the RVARY processing.
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
1

Descriptor code
2