![](dblue_rule.gif) |
- ,CONTEXIT=contexit
- Use this input parameter to identify the contention exit for the
requestor.
The contention exit is used to resolve resource contention
based on user-defined protocols.
To Code: Specify the
RS-type name or address (using a register from 2 to 12) of the contention
exit for the requestor.
- ,LOCKENTRIES=lockentries
- Use this input parameter to specify the number of lock entries
to be allocated for the coupling facility lock structure. If the value
for LOCKENTRIES is not a power of 2, it is rounded upward to the nearest
power of 2. If a lock structure contains record data (RECORD=YES),
you must specify a nonzero value for LOCKENTRIES. If a lock structure
does not contain record data (RECORD=NO) and the value for LOCKENTRIES
is zero, the system attempts to allocate the structure with as many
lock entries as possible within the given structure size.
To
Code: Specify the RS-type name or address (using a register from
2 to 12) of the fullword field that contains the number of lock entries
to be allocated for the lock structure. If the lock structure supports
record data, a value of zero for LOCKENTRIES is not valid. If the
lock structure does not support record data, a value of zero indicates
that the system should obtain the largest possible number of lock
entries given the structure's allocated size.
,MAXCONN=maxconn ![End of change](./deltaend.gif)
,NUMUSERS=numusers ![End of change](./deltaend.gif)
- Use this input parameter to specify the maximum number of users
that can connect and use the lock structure. You must use either NUMUSER
or MAXCONN. The actual number of connections that the structure supports
is returned in the Connect Answer Area field
CONALOCKNUMUSERS . For
NUMUSERS=numusers, specify a value in the
range of 1 to 32. If NUMUSERS specifies a value over 32, the structure
will only allow 32 connections, causing the actual number of supported
connections to be 32.
To allocate a structure that can support
more than 32 connectors, use the MAXCONN keyword.
For NUMUSERS
if the user limit for the allocated structure (returned in CONACFACILITYUSERLIMIT ![End of change](./deltaend.gif) ) is greater than 32, the
system rejects the connect request for the following reasons: - The requested NUMUSERS attribute value of the connector is lower
than the number of in-use connections to the specified structure.
- The available connection identifier is greater than the smallest
NUMUSERS or MAXCONN value that existing connections have specified.
- The available connection identifier is greater than 32.
If you have specified NUMUSERS on a connect request,
XCF rejects the request for the following reasons: - If the requested MAXCONN attribute value of the connector is lower
than the highest in-use connection identifier to the specified structure.
- If the available connection identifier is greater than the smallest
NUMUSERS or MAXCONN value that existing connections have specified.
- The available connection identifier is greater than 32.
XCF rejects a rebuild connect request for the following
reasons: - If the requested NUMUSERS attribute of the connector is lower
than the number of in-use connections to the old structure instance.
- If the initial connect request specified the MAXCONN keyword.
Use either MAXCONN or NUMUSERS to specify the maximum number of users
that can connect to the lock structure.
To allocate a lock structure that can support more than
32 connectors, use the MAXCONN= maxconn ![End of change](./deltaend.gif) keyword
as follows: - Ensure that the MAXCONN keyword is used by all connectors to the
structure.
- Ensure that the structure is allocated in a coupling facility
with CFLEVEL=17 or higher.
Specifying the MAXCONN keyword with any value indicates
that the connection can support a user-id limit change that results
from a system-managed process (for example, rebuild). XCF communicates
the user-id limit change through the structure state change event.
Specifying the MAXCONN keyword with a value greater than 32 indicates
that the connector can understand events for subject connections with
connection identifiers up to the value specified (for example, EeplExistingConnection or EeplNewConnection).
XCF
rejects a MAXCONN connect request for the following reasons: - If the requested MAXCONN attribute value of the connector is lower
than the highest in-use connection id of an existing connector to
the specified structure.
- If the available connection identifier of the connector is greater
than the smallest NUMUSERS or MAXCONN value that existing connections
have specified
XCF rejects a rebuild MAXCONN connect request for the
following reasons: - If the requested MAXCONN attribute value of the connector is lower
than the number of in-use connections to the old structure instance.
- If the initial connect request specified the NUMUSERS keyword.
To Code: Specify the RS-type name or address (using
a register from 2 to 12) of the 1-byte field that contains the maximum
number of users of the coupling facility lock structure.
- ,MONITORSTORAGE=0
- ,MONITORSTORAGE=monitorstorage
- Use this input parameter to indicate whether monitoring of storage
is desired. Valid values are 0 (or
IXLCONNMONITORSTORAGENO )
and 1 (or IXLCONNMONITORSTORAGEYES ). A value
of 0 ( IXLCONNMONITORSTORAGENO ) specifies not
to monitor storage usage. When storage is exceeded, the XES storage
manager issues an abend of X'026'.
A value of 1 ( IXLCONNMONITORSTORAGEYES ) specifies to monitor
storage usage. When the amount of in-use storage reaches a preestablished
threshold, incoming requests will be rejected with a return code of
IXLRETCODEENVERROR and a reason code of ISLRSNCODERESOURCESCONSTRAINED.
Any
other specified value will have the same behavior as specifying a
value of 0 ( IXLCONNMONITORSTORAGENO ).
- ,NOTIFYEXIT=notifyexit
- Use this input parameter to specify the name of the notify exit
for the requestor.
The notify exit is used to notify resource
owners that contention for the resource exists.
To Code: Specify
the RS-type name or address (using a register from 2 to 12) of the
name of the notify exit for the requestor.
- Use this input parameter to specify the maximum number of users
that can connect and use the lock structure. The actual number of
connections that the structure supports is returned in the Connect
Answer Area field ConaLockNumUsers.
To Code: Specify
the RS-type name or address (using a register from 2 to 12) of the
fullword field that contains the number of lock entries for the coupling
facility list structure.
- ,NUMUSERS=numusers or ,MAXCONN=maxconns
- Use this input parameter to specify the maximum number of users
that can connect and use the lock structure. You must use either NUMUSER
or MAXCONN. The actual number of connections that the structure supports
is returned in the Connect Answer Area field ConaLockNumUsers.
For NUMUSERS=numusers,
specify a value in the range of 1 to 32. If NUMUSERS specifies a value
over 32, the structure will only allow 32 connections, causing the
actual number of supported connections to be 32.
To allocate
a structure that can support more than 32 connectors, use the MAXCONN
keyword.
For NUMUSERS if the user limit for the allocated
structure (returned in ConaCFacilityUserLimit) is
greater than 32, the system rejects the connect request for the following
reasons: - The requested NUMUSERS attribute value of the connector is lower
than the number of in-use connections to the specified structure.
- The available connection identifier is greater than the smallest
NUMUSERS or MAXCONN value that existing connections have specified.
- The available connection identifier is greater than 32.
If you have specified NUMUSERS
on a connect request, XCF rejects the request for the following reasons: - If the requested MAXCONN attribute value of the connector is lower
than the highest in-use connection identifier to the specified structure.
- If the available connection identifier is greater than the smallest
NUMUSERS or MAXCONN value that existing connections have specified.
- The available connection identifier is greater than 32.
XCF rejects a rebuild connect request for the following
reasons: - If the requested NUMUSERS attribute of the connector is lower
than the number of in-use connections to the old structure instance.
- If the initial connect request specified the MAXCONN keyword.
Use either MAXCONN or NUMUSERS to specify the maximum number of users
that can connect to the lock structure.
To allocate a lock structure that can support more than
32 connectors, use the MAXCONN= maxconns keyword
as follows: - Ensure that the MAXCONN keyword is used by all connectors to the
structure.
- Ensure that the structure is allocated in a coupling facility
with CFLEVEL=17 or higher.
Specifying the MAXCONN keyword with any value indicates that
the connection can support a user-id limit change that results from
a system-managed process (for example, rebuild). XCF communicates
the user-id limit change through the structure state change event.
Specifying the MAXCONN keyword with a value greater than 32 indicates
that the connector can understand events for subject connections
with connection identifiers up to the value specified (for example, EeplExistingConnection or EeplNewConnection).
XCF
rejects a MAXCONN connect request for the following reasons: - If the requested MAXCONN attribute value of the connector is lower
than the highest in-use connection id of an existing connector to
the specified structure.
- If the available connection identifier of the connector is greater
than the smallest NUMUSERS or MAXCONN value that existing connections
have specified
XCF rejects a rebuild MAXCONN connect request
for the following reasons: - If the requested MAXCONN attribute value of the connector is lower
than the number of in-use connections to the old structure instance.
- If the initial connect request specified the NUMUSERS keyword.
When you migrate applications to use greater-than-32
connectors support in a rolling fashion, the application or installation
can take the following steps to avoid failed connection attempts: - Ensure that applications have internal structures coded to accept
events for connection identifiers up to the planned value that is
to be used on the MAXCONN keyword.
- Ensure that all instances of the application are updated to use
the MAXCONN keyword. When all instances of the application have been
upgraded to a level that specifies MAXCONN, the structure is eligible
to accommodate more than 32 instances of the application.
- Ensure that the structure is reallocated in order to take advantage
of greater-than-32 connectors in a CFLEVEL 17 coupling facility. You
can accomplish this through the rebuild process.
To Code: Specify the RS-type name or address (using
a register from 2 to 12) of the 1-byte field that contains the maximum
number of users of the coupling facility lock structure.
- ,RECORD=NO
- ,RECORD=YES
- Use this input parameter to specify whether the lock user wants
to do recording of data about the lock:
- NO
- Indicates the system does not record data.
- YES
- Indicates the system records data.
- ,RNAMELEN=FIXED64
- ,RNAMELEN=VAR300
- Use this input parameter to indicate the length attribute of the
resource names (either fixed length or variable length). All connectors
to the structure must specify the same attribute when they connect
to the structure. The system rejects a connect request if the connector's
requested RNAMELEN value does not match the attribute in effect for
a currently-allocated instance of the structure, as determined by
the IXLCONN RNAMELEN specification of the first connector to the structure.
The system also rejects a rebuild connect request if RNAMELEN is specified
and its value is not consistent with the value specified for the original
structure.
- RNAMELEN=FIXED64
- Specifies that the resource names for the structure will have
a fixed length of 64 bytes.
- RNAMELEN=VAR300
- Specifies that the resource names for the structure will have
a variable length between 1 and 300 bytes.
|