GRS INITIALIZATION ERROR. UNABLE TO ALLOCATE THE GRS LOCK
STRUCTURE (ISGLOCK) reason
Explanation
GRS was unable to allocate the global resource
serialization lock structure.
In the message text
reason is
one of the following:
- IXLCONN FAILED WITH RC=rc, RSN=rsn.
- LOCK STRUCTURE (ISGLOCK) CONTAINS xxxxx LOCKS. A MINIMUM OF 32767
IS REQUIRED.
System action
The system enters a non-restartable X'0A3' wait
state.
Operator response
Inform the system programmer of the error.
After the error condition has been relieved, reIPL the system.
System programmer response
- If IXLCONN failed with RC=C RSN=0C08, make sure that
you do the system IPL with a CFRM policy that defines the global resource
serialization lock structure with sufficient connectivity to coupling
facilities. See messages IXL013I and IXL015I for details on connect
failures and on coupling facility status that prevents the use of
GRS from allocating the lock structure. See IXC518I for details on
coupling facility that is not connected to the system. A CFRM policy
must be started to allow the use of coupling facilities and the global
resource serialization lock structure. To start a CFRM policy, either
use the SETXCF START,POLICY,TYPE=CFRM,POLNAME=polname operator
command or specify CFRMPOL(polname) in the COUPLExx
parmlib member to do sysplex IPL.
This problem might occur during
a sysplex-wide IPL after a hardware upgrade when a coupling facility
cannot be used. The SETXCF command cannot be used because this is
occurring during a sysplex-wide IPL. The CFRMPOL keyword in the COUPLExx
parmlib member is ineffective because a CFRM policy is already active
in the CFRM couple data sets. To recover from this problem, perform
the following steps:
- Specify GRS=TRYJOIN in IEASYS or as a response to IEA101A. This
allows the system to come up in the GRS ring mode.
- Start a new CFRM policy, bring a new coupling facility online
, or correct the size of the ISGLOCK structure to correct the problem
that is keeping GRS from allocating the ISGLOCK structure.
For
example, this problem can occur on a z/990 machine when the partition
number of a coupling facility definition in the CFRM policy does not
match the LPAR identifier of the coupling facility definition in the
HMC Image Profile. In this case, correcting the CFRM policy (and starting
that corrected policy) should correct the problem and allow the coupling
facility to be brought into use.
- Either re-IPL with the corrections, or issue SETGRS MODE=STAR
to avoid the IPL.
- Start the remaining systems in GRS=STAR mode.
- Make sure that the SIZE or INITSIZE specified in the CFRM policy
for the global resource lock structure is sufficient for use by global
resource serialization. If it is not, increase the size specified
in the policy. If it is, update the CFRM policy preference list to
select a coupling facility that has sufficient storage. After updating
the CFRM policy, start the updated policy.
- If IXLCONN failed with RC=C RSN=0C27, use the D XCF,STR,STRNAME=ISGLOCK
operator command to display detailed information about the ISGLOCK
structure and its connectors. Additionally, you can use D XCF,STR,
SSTRNAME=ISGLOCK, CONNAME=xconname for details about each connector.
Source
Global resource serialization
Module
Routing code
Descriptor code