ISG006I

Explanation
text is one of the following:
MULTIPLE
GRS COMPLEXES EXIST
SYSTEM sysname ALREADY
A GRS SYSTEM
MORE THAN 31 SYSTEMS KNOWN BY THIS SYSTEM
SYSTEM sysname BELONGS
TO A FULL GRS COMPLEX
NO ACTIVE GRS SYSTEM
GRS DISRUPTION
MAY BE IN PROGRESS
This system tried to join a global resource
serialization complex, but the system parameter GRS=JOIN or GRS=TRYJOIN
is incorrect for one of the following reasons: MULTIPLE GRS COMPLEXES EXIST
This system has channel-to-channel (CTC) links to systems in two
or more global resource serialization complexes.  For example, this
system might have connections to system SYS01 and system SYS03, but
system SYS01 belongs to one global resource serialization complex
and system SYS03 belongs to another. This system can join only one
of the global resource serialization complexes and cannot have links
to systems in other global resource serialization complexes.
SYSTEM sysname ALREADY A GRS SYSTEM
System sysname is already defined to the global
resource serialization complex. One of the following is true: This system has CTC links to a system that has the same system
name as this system.
This system has the same name as a system that is already part
of the global resource serialization complex. This can occur when
you reIPL this system if this system was an active global resource
serialization system during a previous IPL and was never purged from
the complex.

MORE THAN 31 SYSTEMS KNOWN BY THIS SYSTEM
This system knows of more than 31 systems in the global resource
serialization complex. Each of these systems is in one of the following
categories: The system is in the global resource serialization complex.
The system specified the GRS=START or GRS=JOIN system parameter,
but the system has not yet finished processing the JOIN or START parameter.

SYSTEM sysname BELONGS TO A FULL GRS COMPLEX
System sysname belongs to a global resource
serialization complex that already includes the maximum possible number
of systems.
NO ACTIVE GRS SYSTEM
No systems were found in the global resource serialization complex.
Either no other global resource serialization system exists or this
system does not have a functional CTC link to an active global resource
serialization system.
GRS DISRUPTION MAY BE IN PROGRESS
Global resource serialization systems exist, but all the systems
that can communicate with this one are either inactive or quiesced.
 One of the following is true: The complex is in a disrupted state.
A previously IPLed system has not started the global resource
serialization ring yet.
There is no functional CTC link between this system and an active
global resource serialization system.

System action
One of the following: If MORE THAN 31 SYSTEMS KNOWN BY THIS SYSTEM or SYSTEM sysname BELONGS
TO A FULL GRS COMPLEX appears in the message text and this system
is running in a multisystem sysplex environment, the system issues
message ISG167W. The system enters wait state X'0A3' with
reason code X'04'.
In all other cases, the system issues message ISG009D and processing
stops until the operator enters a valid reply.

Operator response
Notify the system programmer. See the operator
response for message ISG009D or do one of the following: MULTIPLE GRS COMPLEXES EXIST
If you want this system to join one of the existing global resource
serialization complexes, physically disable this system's CTC links
to all systems except the following: Systems that are in the global resource serialization complex
that this system is trying to join
Systems that are not in (and will not be in) any global resource
serialization complex

 Reply JOIN to message ISG009D.
SYSTEM sysname ALREADY A GRS SYSTEM
If this message appears because this system has the same system
name as another system, reIPL this system with a different system
name.  Before using a different system name, be sure there is a GRSDEF
statement for that system name in the appropriate GRSCNFxx parmlib
member. If this message appears because this system was part of
the global resource serialization complex during a previous IPL, have
the operator of an active global resource serialization system enter
the VARY GRS(sysname),PURGE command. Then reply JOIN to
message ISG009D.

NO ACTIVE GRS SYSTEM
Do one of the following: If no global resource serialization complex exists, but another
system is starting one, wait until that system completes its initialization.
Then reply JOIN to message ISG009D.
If no global resource serialization complex exists, and you want
this system to start one, reply START to message ISG009D.
If there is an active global resource serialization system but
this system does not have a functional CTC link to that active system,
establish a CTC link to that system. Then reply JOIN to message
ISG009D.

GRS DISRUPTION MAY BE IN PROGRESS
Do one of the following: If there is a global resource serialization complex but the ring
has been disrupted or all of the systems in the complex are quiesced,
wait until the global resource serialization ring is rebuilt.  Enter
a VARY GRS(ALL),RESTART command on one of the systems in the complex
if necessary. Then reply JOIN or TRYJOIN to message
ISG009D.
If another system is IPLing but is not active yet, wait until
that system is active and has issued message ISG004I. Then reply JOIN or TRYJOIN to
message ISG009D.
If there is an active global resource serialization system but
this system does not have a functional CTC link to that active system,
establish a CTC link to the system.  Contact the system programmer
for assistance if necessary. Then reply JOIN or TRYJOIN to
message ISG009D.

System programmer response
If this system regularly issues message
ISG006I with NO ACTIVE GRS COMPLEX appearing in the message
text, see z/OS MVS Planning: Global Resource Serialization 
for information about the valid specifications of GRS parameters.
If
the problem persists, search problem reporting databases for a fix
for the problem. If no fix exists, contact the IBM® Support Center.

Source
Global resource serialization

Module
ISGNGRSP

Routing code
2,10

Descriptor code
12