ICH15037I

Explanation
For each unique sysplex name, there might exist
one IRRPLEX profile. These profiles contain APPLDATA information,
and are used by the routines, which protect the database from being
used in an incorrect sharing environment, to prevent database corruption.
A sysplex name is limited to eight characters in length. No information
from this profile is considered by the anti-corruption scheme.
A
maximum of the first 20 characters of the profile name is presented
in the message.

System action
The system continues processing.

Operator response
Contact your system programmer.

System programmer response
IRRPLEX_sysplex-name profiles are
used by the routines that protect the database from bad sharing. If
the names of profiles in the GXFACILI class begin with “IRRPLEX_”,
they might remain if the environment has other uses for them, and
this message can be ignored.
If a sysplex, which runs at code
levels less than in z/OS® R10,
shares this database (RVARY LIST from the security console), and you
manually created the profile to ensure that the code, which shields
the database from bad sharing, gets more pertinent information, you
must issue an RDELETE command on the profile and reissue the command
with a valid 8-character sysplex name.
Systems running release z/OS R10 or later, automatically
create and maintain these profiles.
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, 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 and 9

Descriptor code
4