0A3 ExplanationA system could not successfully participate in
a global resource serialization complex. In order for a system to
join a sysplex, it must also be a member of the global resource serialization
complex, but the system cannot join the global resource serialization
complex for one of the following reasons: - The global resource serialization system parameters specified
are incorrect.
- Global resource serialization encountered an unrecoverable error.
The right-most four bytes of the program status word (PSW)
have the following format: x0rrrwww
where: - x
- Irrelevant information.
- rrr
- A hexadecimal reason code indicating the reason for the failure.
- www
- The wait state code.
The reason code ( rrr) is one of the
following: - 004
- The system IPLed into a sysplex with GRS=JOIN or TRYJOIN parameters,
but global resource serialization was unable to join the global resource
serialization complex. Systems in a sysplex must be in the same global
resource serialization ring. The wait state is accompanied by message
ISG167W.
- 008
- The system IPLed into the sysplex with GRS=JOIN, START, TRYJOIN
or STAR system parameter, and when global resource serialization attempted
to use the cross-system coupling facility (XCF) during initialization,
the service failed with an unexpected error.
When this wait state
occurs, message ISG152W is issued to the console. This message identifies
the XCF service and the return and reason codes.
- 00C
- Global resource serialization found an error in parmlib member
GRSCNFxx. The wait state is accompanied by message ISG043I or ISG044I.
- 010
- Global resource serialization found an error in parmlib member
GRSRNLxx. The wait state is accompanied by messages ISG062I and ISG063I.
- 014
- Global resource serialization could not establish the event notification
(ENF) exits. The wait state is accompanied by message ISG021I.
- 018
- Global resource serialization found an error in parmlib member
GRSCNFxx. The parmlib member specifies a device that is already in
use. The wait state is accompanied by message ISG045I.
- 01C
- The system IPLed with GRS=NONE and PLEXCFG=MULTISYSTEM. These
two parameters are mutually exclusive. The wait state is accompanied
by message ISG159W.
- 020
- Global resource serialization tried to remove this system from
the complex, but the attempt failed. The wait state is accompanied
by message ISG152W.
- 026
- Global resource serialization detected an unrecoverable error
in an XCF exit.
- 028
- Global resource serialization detected an internal error.
- 02C
- Global resource serialization detected an unrecoverable failure
while running in a sysplex. The wait state is accompanied by message
ISG168W.
- 030
- Global resource serialization detected an internal error.
- 034
- The system IPLed with GRS=JOIN or TRYJOIN, but global resource
serialization could not invoke the XCF Set User State service. The
wait state is accompanied by message ISG152W.
- 038
- Global resource serialization could not find the systems exclusion
RNL exit (ISGGSEEA) while trying to process a GRSRNL=EXCLUDE system
parameter.
- 03C
- Global resource serialization could not find the systems inclusion
RNL exit (ISGGSIEA) while trying to process a GRSRNL=EXCLUDE system
parameter.
- 040
- The system could not send a message via the XCF message out service.
- 044
- The global resource serialization complex is unable to restart
after a ring disruption. No active global resource serialization ring
exists, and this system has repetitively failed in its attempts to
initiate one. The wait state may be accompanied by messages ISG011I,
ISG015I, ISG021I, ISG025I, ISG173I, ISG176I, or ISG180E.
- 04C
- The operator entered a VARY GRS,PURGE command for this system,
removing it from the global resource serialization complex.
- 050
- This system is unable to enter the global resource serialization
ring. A current member of the global resource serialization complex
belongs to a different multisystem sysplex than the rest of the members
of the global resource serialization complex. Global resource serialization
only supports one multisystem sysplex per global resource serialization
complex. The wait state is accompanied by message ISG182W.
- 054
- This system is unable to reactivate a global resource serialization
ring from the quiesced state. It became quiesced because of a ring
disruption, system failure, or an operator-issued VARY GRS,QUIESCE
command. No active global resource serialization system exists. This
system had the most current global request information of all systems
in the complex.
- 058
- This system encountered an unrecoverable software error in recovery
for global resource serialization ring processing.
- 05C
- This system encountered an unrecoverable software error in recovery
for global resource serialization internal or external command processing.
- 060
- Global resource serialization tried to invoke the XCF Query service
to gather information about the sysplex, but the attempt failed. The
wait state is accompanied by message ISG152W.
- 064
- This system's inclusion resource name list (GRS RNL parmlib member)
is not exactly the same as the one the global resource serialization
complex is currently using. All RNLs must be the same within the GRS
complex. Note that RNLs that may have the same results are not considered
to be exact matches. They should be the exact same RNL values in the
exact same order. If they appear to be the same, then obtain a stand-alone
dump; in a sysplex, a SDUMP will be taken on the assisting system.
This dump should also be provided to the IBM® Support
Center.
- 068
- This system's exclusion resource name list (GRS RNL parmlib
member) is not exactly the same as the one the global resource serialization
complex is currently using. All RNLs must be the same within
the GRS complex. Note that RNLs that may have the same results are
not considered to be exact matches. They should be the exact same
RNL values in the exact same order. If they appear to be the same,
then obtain a stand-alone dump; in a sysplex, a SDUMP will be taken
on the assisting system. This dump should also be provided to the IBM Support Center.
- 06C
- This system's RESERVE conversion RNL (GRS RNL parmlib member)
is not exactly the same as the one the global resource serialization
complex is using. All RNLs must be the same within the GRS complex.
Note that RNLs that may have the same results are not considered to
be exact matches. They should be the exact same RNL values in the
exact same order. If they appear to be the same, then obtain a stand-alone
dump; in a sysplex, a SDUMP will be taken on the assisting system.
This dump should also be provided to the IBM Support
Center.
- 070
- This system encountered an unrecoverable software error during
global resource serialization queue merge processing. Obtain a stand-alone
dump; in a sysplex, a SDUMP will be taken on the 'assisting system'.
This dump should also be provided to the IBM Support Center.
- 07C
- Global resource serialization address initialization failed.
A system service called to initialize one of its modules was not successful.
When
this wait state occurs, message ISG305W is issued to the console.
This message identifies the service, the module and the non-zero return
code passed back from the service.
- 080
- Global resource serialization initialization failed. A critical
task terminated.
When this wait state occurs, message ISG306W is
issued to the console. An error code in this message identifies the
particular task that failed.
- 084
- Global resource serialization failed. The type of complex the
system initialized is not compatible with the complex currently active
in the sysplex. A system IPLed with GRS=START, JOIN or TRYJOIN, cannot
join an existing global resource serialization star complex. Similarly,
when a system is IPLed with GRS=STAR, it cannot join an existing global
resource serialization ring complex.
If the system detected the
error condition itself and issued the wait state, message ISG307W
is issued.
If the system partitioned out of the complex and
was put into a wait state as a result of action taken by an already
active system that detected the error, then message ISG307W is not
issued.
- 088
- Global resource serialization invoked a system service which did
not successfully complete. Message ISG308W is issued, identifying
the system service along with the error return and reason code.
- 08A
- During system initialization, global resource serialization was
unable to access the global resource serialization record on the sysplex
couple dataset.
When this wait state occurs, message ISG342W is
issued to the console. This message identifies the reason the record
could not be accessed.
- 08E
- During the initialization, GRS GRQA was allocated too high by
the IARV64 service to guarantee IXLLOCK processing integrity. The
wait state is accompanied by message ISG373W. See message ISG373W
for additional diagnostic data that should be provided to the IBM Support Center.
- 090
- Global resource serialization processing failed due to the unexpected
termination on one of its tasks that is critical to global resource
processing.
When this wait state occurs, message ISG315W is issued
to the console. An error code in this message identifies the task
that failed.
- 094
- During global resource serialization processing, one of its critical
task terminated. Global resource serialization is unable to reinstate
the task because the ATTACH for the task failed with an error return
code.
When this wait state occurs, message ISG316W is issued to
the console. This message identifies the module the could not be ATTACHed
and the error return code from ATTACH.
- 098
- During recovery, a primary global resource serialization control
block was damaged. Global resource serialization is unable to recover
from this error.
When this wait state occurs, message ISG317W is
issued to the console.
- 09C
- During GRS Star initialization, the system was unable to access
the GRS lock structure (ISGLOCK).
This wait state might occur if
CFRM is not available for the first system trying to come up in STAR
mode, and CFRMPOL is not specified in the COUPLExx parmlib member.
When
this wait state occurs, message ISG342W is issued to the console.
The message describes what kind of access to the structure failed.
- 0A0
- During GRS processing, an unexpected error occurred in one of
the GRS XCF exits. GRS is unable to recover from the failure. (Message
ISG310W is issued to the console.)
- 0AC
- The top level global resource serialization task from which all
other task are anchored unexpectedly received control at a point in
its processing that should not occur and is unable to recover.
When
this wait state occurs, message ISG329W is issued to the console.
- 0BC
- During initialization of a star complex, global resource serialization
was not able to allocate the global resource serialization lock structure.
The reason can be one of the following:
- Connection to the structure failed with IXLCONN RC=0C and RSN=0C08
or RSN=0C27.
- Storage on the coupling facility is insufficient or the policy
size is too small for the minimum structure size needed.
When this wait state occurs, message ISG338W is issued to
the console. This message identifies the name of the structure causing
the failure.
- 0C0
- An unexpected error occurred in one of the Global resource serialization
lock structure exits. Global resource serialization is unable to
recover from this error.
When this wait state occurs, message ISG310W
is issued to the console. This message identifies the name of the
global resource serialization lock structure that failed.
- 0C4
- During a rebuild of the global resource serialization lock structure
detected damage to the global request queue on the system. Global
resource serialization is not able to continue using the original
lock structure due to a structure failure or loss of connectivity.
Additionally,
this code is issued for a failure when the lock structure rebuild
was issued on behalf of a GRSRNL=EXCLUDE to standard RNLs migration.
The original structure does not contain an accurate reflection of
all globally managed resources and therefore cannot be used.
When
this wait state occurs, message ISG309W is issued to the console.
- 0C8
- During a rebuild of the global resource serialization lock structure,
global resource serialization received a request to stop the rebuild.
Global resource serialization can not resume processing with the
original global resource serialization lock structure, due to a structure
failure or loss of connectivity.
When this wait state occurs, message
ISG309W is issued to the console.
- 0CC
- During a rebuild of the global resource serialization lock structure,
sysplex failure management (SFM) determined that this system should
not disconnect from the structure. Global resource serialization
partitioned the system from the sysplex to insure data integrity is
maintained.
When this wait state occurs, message ISG309W is issued
to the console.
- 0D0
- During a rebuild of the global resource serialization lock structure,
sysplex failure management (SFM) determined that the original lock
structure has better connectivity than the new structure. Global resource
serialization could not resume processing with the original lock structure
due to a structure failure or a loss of connectivity condition.
Global resource serialization partitions the system from the sysplex
to insure data integrity is maintained.
Additionally, this code
is issued for a failure when the lock structure rebuild was issued
on behalf of a GRSRNL=EXCLUDE to standard RNLs migration. The original
structure does not contain an accurate reflection of all globally
managed resources and therefore cannot be used.
When this wait
state occurs, message ISG309W is issued to the console.
- 0D4
- During a rebuild of the global resource serialization lock structure,
global resource serialization was unable to connect to the new structure.
Global resource serialization partitions the system from the sysplex
to insure data integrity is maintained.
When this wait state occurs,
message ISG309W is issued to the console.
- 0D8
- During a rebuild of the global resource serialization lock structure,
global resource serialization received an unrecoverable response from
a XES service. Global resource serialization is not able to continue
processing.
When this wait state occurs, message ISG308W or ISG309W
is issued to the console.
- 0DC
- During a rebuild of the global resource serialization lock structure,
global resource serialization received an unexpected event, violating
the rebuild protocol. Global resource serialization is not able to
continue.
When this wait state occurs, message ISG309W is issued
to the console.
- 0E0
- During a rebuild of the global resource serialization lock structure,
global resource serialization stopped for an unknown reason. Global
resource serialization is not able to continue processing.
When
this wait state occurs, message ISG309W is issued to the console.
- 0E4
- During migration from a global resource serialization ring to
a star complex, a structure error occurred. Global resource serialization
is not able to continue processing.
When this wait state occurs,
message ISG309W is issued to the console.
- 0E8
- During migration from a global resource serialization ring to
a star complex, global resource serialization queue damage was detected.
Global resource serialization is not able to continue processing.
When
this wait state occurs, message ISG332I is issued to the console.
- 0EA
- The system attempted to IPL while global resource serialization
was migrating from a global resource serialization ring to a star
complex. The system cannot join the complex during this processing.
When
this wait state occurs, message ISG301W is issued to the console.
- 0EC
- During migration from a global resource serialization ring to
a star complex, an unexpected error occurred.
When this wait state
occurs, message ISG304W is issued to the console.
- 0EE
- During migration from GRSRNL=EXCLUDE to standard RNLs, an unexpected
error occurred.
When this wait state occurs, message ISG373W is
issued to the console.
System actionThe system enters a non-restartable wait state.
For reason codes X'026', X'058', and X'05C',
the system writes a logrec error record and issues an SVC dump.
For
reason codes X'064' through X'070', the system issues
message ISG015I. The system may also issue message ISG183W.
System programmer responseDo one of the following: - To IPL a system without global resource serialization, IPL with
COUPLE=00,GRS=NONE. The system will IPL in XCF-local mode. Do not
start any jobs that access shared sysplex resources.
- To IPL a system into the sysplex and the global resource serialization
complex,
- If you want to IPL a global resource serialization ring complex,
correct the GRS= specification (in IEASYSxx parmlib member or in response
to message IEA101A) to be one of the following:
- If you want to IPL a global resource serialization star complex,
check the following:
- The global resource serialization record was formatted on the
sysplex couple data set via the IXCL1DSU formatting utility.
- The sysplex couple data set with the global resource serialization
record is the current primary sysplex couple data set.
- To resolve the problem preventing the system from joining global
resource serialization, do the following:
- See the explanations for accompanying messages for information
about the problem.
- Obtain the SVC dump, if one was issued, and format it with the
IPCS VERBEXIT MTRACE command to find the last message global resource
serialization issued. See the explanation for any message found.
- For reason codes 64, 68, 6C, and 70, obtain a stand-alone dump;
in a sysplex, a SDUMP will be taken on the 'assisting system'. This
dump should also be provided to the IBM Support
Center.
- If you cannot find the problem, or the problem persists, search
problem reporting databases for a fix for the problem. If no fix exists,
contact the IBM Support Center.
Provide the logrec error record and the SVC dump if they were issued.
SourceGlobal resource serialization
|