NONE

No additional action is to be performed.

WRITE

In addition to moving the list entry, write the contents of the storage area(s) specified by BUFFER or BUFLIST and/or BUFLIST to the list entry, if the storage areas exist.

READ

In addition to moving the list entry, read the entry data and/or adjunct data into the storage areas specified by BUFFER or BUFLIST and/or ADJAREA.

At least one of BUFFER, BUFLIST, or ADJAREA must be specified when ACTION=READ is specified with REQUEST=MOVE.

Specify ADJAREA only for structures that support adjunct data. (Adjunct areas for a structure are established through the IXLCONN macro.)

If the structure was allocated to use secondary keys, and the IXLLSTE request results in a new list entry being created, the first 32 bytes of the list entry adjunct data will be used to store the secondary key of the list entry. This allows only the last 32 bytes of list entry adjunct data to be written.

If the structure was allocated to use secondary keys and the IXLLSTE request results in the list entry being moved or updated, the first 32 bytes of the ADJAREA are ignored, allowing only the last 32 bytes of data to be written to the list entry adjunct area. The secondary key of the list entry can only be updated by an IXLLSTM REQUEST=MOVE_ENTRYLIST request.

To Code: Specify the RS-type name or address (using a register from 2 to 12) of a 64-byte area that contains or will contain the adjunct data.

Not all fields in the answer area are applicable to all request types. Request type descriptions indicate which answer area fields are applicable for successful request completion cases. Return and reason code descriptions indicate which answer area fields are applicable for non-successful completing requests.

To Code: Specify the RS-type name or address (using a register from 2 to 12) of an area (with a length of ANSLEN) that will contain the information returned by the request.

Check the prologue of the IXLYLAA mapping macro for the minimum required size of the answer area, or use the length field (LAA_LEN) in the LAA.

To Code: Specify the RS-type name or address (using a register from 2 to 12) of a 2-byte field that contains the size, in bytes, of the answer area.

If the list entry is moved or created, use this parameter to assign a TARGETKEY, ENTRYKEY, or list key value.

ASSIGN also allows key comparison to be specified for keyed list entries.

NONE

No assignment is to be explicitly made.

If the list entry is created, the following applies:

• If the structure was allocated to use keyed entries, the entry key (and therefore, the target list keyed position) is assigned as follows:
  • If DIRECTION=HEADTOTAIL is specified (explicitly or by default), the list entry is assigned an entry key value of all binary zeros.
  • If DIRECTION=TAILTOHEAD is specified, the list entry is assigned an entry key value of all binary ones.
• If the structure was allocated to use secondary keys, the list entry is assigned a secondary key value of all binary zeros.

If the list entry is moved, the entry key and the secondary key remain unchanged.

NAME

The entry name specified by ENTRYNAME is to be assigned to the list entry if it is created as a result of the IXLLSTE request.

If a list entry already exists with the specified ENTRYNAME, a new list entry is not created and the IXLLSTE request is ended.

ASSIGN=ENTRYNAME may only be specified when the structure was allocated to use named entries.

KEY

The entry key (and therefore the target list keyed position) specified for ENTRYKEY is to be assigned to the newly created or moved list entry.

If the list entry is created and the structure was allocated to use secondary keys, the secondary key value specified by SECONDARYKEY will be assigned to the list entry. The secondary key will be stored in the first 32 bytes of the list entry adjunct area. If the user supplies ADJAREA, the first 32 bytes will be ignored. If the user does not supply SECONDARYKEY, the secondary key will be set to all binary zeros.

For keyed list entries, when ENTRYTYPE=NEW is specified, a new list entry is created regardless of whether a list entry already exists with the same ENTRYKEY value or the same SECONDARYKEY value.

LISTKEY

The current list key value is to be assigned to the newly created list entry.

The list key and maximum list key values may be set with an IXLLSTC REQUEST=WRITE_LCONTROLS request.

The current list key value can be assigned to a list entry only on structures allocated in a coupling facility of CFLEVEL=1 or higher.

If the request is attempting to create a list entry and either a list entry already exists with the specified ENTRYID, or ASSIGNENTRYID was not specified, a new list entry is not created and the IXLLSTE request is ended.

If the request is not creating a new list entry, the value specified for ASSIGNENTRYID will be ignored.

ASSIGNENTRYID is valid only when the structure is allocated in a coupling facility of CFLEVEL=8 or higher.

To Code: Specify the RS-type name or address (using a register from 2 to 12) of a 12-byte field that contains the ENTRYID to be assigned.

The ASSIGNLISTKEY specification in conjunction with the TARGETKEY and ENTRYKEY specifications are used to assign the entry key. Note especially that the ENTRYKEY specified for KEYCOMPARE may be used as the entry key assignment for a newly created list entry depending on the ASSIGNLISTKEY specification.

The list key value and maximum list key values may be set with an IXLLSTC WRITE_LCONTROLS request.

The current list key value can be assigned to a list entry only on structures allocated in a coupling facility of CFLEVEL=1 or higher.

NO

The list key value is not to be assigned to the list entry, regardless of whether the list entry is moved or created as a result of this request. Instead, the entry key is assigned as follows:

• If the entry is created as a result of this request:
  • The list entry is assigned the TARGETKEY, if specified.
  • If TARGETKEY is not specified, the list entry is assigned the ENTRYKEY, if specified.
  • If neither TARGETKEY nor ENTRYKEY is specified, the entry key is assigned as follows:
    • If DIRECTIONHEADTOTAIL is specified (explicitly or by default), the entry key is assigned all binary zeros.
    • If DIRECTIONTAILTOHEAD is specified, the entry key is assigned all binary ones.
• If the entry is moved as a result of this request:
  • The list entry is assigned the TARGETKEY, if specified.
  • If TARGETKEY is not specified, the entry key remains unchanged.

CREATE

The list key value of the target list (and therefore, the target list keyed position) is to be assigned to the list entry if it is created as a result of this request.

If the list entry is moved as a result of this request, the entry key is assigned as follows:

• The list entry is assigned the TARGETKEY, if specified.
• If TARGETKEY is not specified, the list entry is assigned the ENTRYKEY, if specified.
• If neither TARGETKEY nor ENTRYKEY is specified, the entry key remains unchanged.

MOVE

The list key value of the target list (and therefore, the target list keyed position) is to be assigned to the list entry if it is moved as a result of this request.

If a new list entry is created as a result of this request, the entry key is assigned as follows:

• The list entry is assigned the TARGETKEY, if specified.
• If TARGETKEY is not specified, the list entry is assigned the ENTRYKEY, if specified.
• If neither TARGETKEY nor ENTRYKEY is specified, the entry key is assigned as follows:
  • If DIRECTION=HEADTOTAIL is specified (explicitly or by default), the entry key is assigned all binary zeros.
  • If DIRECTION=TAILTOHEAD is specified, the entry key is assigned all binary ones.

ANY

The list key value of the target list is to be assigned to the list entry whether the list entry is moved or created as a result of this request.

To Code: Specify the RS-type name or address (using a register from 2 to 12) of the 16-byte field that contains the list authority value.

The AUTHCOMPARE keyword is only meaningful for list structures allocated in a coupling facility of CFLEVEL=1 or higher.

NO

No list authority comparison is to be performed to determine whether the entry is to be created or processed.

YES

List authority comparison is to be performed to determine whether the entry is to be created or processed.

EQUAL

The list authority for the list specified by LISTNUM must be equal to the value specified for AUTHCOMP.

LESSOREQUAL

The list authority for the list specified by LISTNUM must be less than or equal to the value specified for AUTHCOMP.

31

The entry in BUFLIST is 31 bits in size.

64

The entry in BUFLIST is 64 bits in size.

VIRTUAL

The buffer addresses are virtual storage addresses. The virtual storage can be pageable or nonpageable. See the PAGEABLE parameter for information about managing storage binds when specifying virtual storage addresses.

REAL

The buffer addresses are real storage addresses.

It is the caller's responsibility to manage the binds between the data buffer virtual storage and the real storage addresses provided. The caller must ensure that the data buffer virtual storage remains bound to the real storage addresses provided until the request completes.

To Code: Specify the RS-type name or address (using a register from 2 to 12) of a 4-byte field that contains the ALET.

If BUFFER or BUFLIST is not specified, entry data is not read or written, as appropriate.

BUFFER is only functional for structures that support entry data. If the structure does not support entry data, the contents of BUFFER will not affect this request.

See the BUFSIZE parameter description for defining the size of the buffer.

To Code: Specify the RS-type name or address (using a register from 2 to 12) of an area (with a length of BUFSIZE) that contains the entry data.

Valid BUFINCRNUM values are 1,2,4,8, or 16, which correspond to BUFLIST buffer sizes of 256, 512, 1024, 2048, and 4096 bytes respectively.

To Code: Specify the RS-type name or address (using a register from 2 to 12) of a 1-byte field that contains 1,2,4,8, or 16.

Either 31-bit addressable (below 2GB) or 64-bit addressable (above 2GB) real or virtual storage areas are supported for the BUFLIST specification, depending on the specifications for the BUFADDRTYPE and BUFADDRSIZE keywords. However, pageable high shared virtual storage areas (above 2GB) may not be used.

If BUFFER or BUFLIST is not specified, entry data is not to be read or written.

BUFLIST is only functional for structures that support entry data. If the structure does not support entry data, the contents of BUFLIST will not affect this request.

See the BUFNUM and BUFINCRNUM parameter descriptions for defining the number and size of buffers.

To Code: Specify the RS-type name or address (using a register from 2 to 12) of a 128-byte area that contains the list of buffer addresses.

To Code: Specify the RS-type name or address (using a register from 2 to 12) of a 1-byte field that contains the number of buffers in the buffer list.

To Code: Specify the RS-type name or address (using a register from 2 to 12) of a fullword field that contains the size of the buffer (BUFFER) in bytes.

If you do not specify BUFSTGKEY, or if you specify BUFSTGKEY=CALLERS_KEY, all references to the buffer(s) are performed using the caller's PSW key.

To Code: Specify the RS-type name or address (using a register from 2 to 12) of an 8-bit field that contains the storage key in the format B'kkkkxxxx', where kkkk is the key and xxxx is ignored.

To Code: Specify the RS-type name or address (using a register from 2 to 12) of a 16-byte field that contains the connect token.

NEXT

Set the list cursor as follows:

• If the list entry is created, the cursor for the list specified by MOVETOLIST or LISTNUM is updated and the direction of the cursor update depends on the value specified for MOVETODIRECTION or DIRECTION.
• For an existing list entry, the cursor for the list on which the designated entry resides before the request is processed is updated and the direction of the cursor update depends on the value specified for DIRECTION.
• When MOVETODIRECTION or DIRECTION=HEADTOTAIL is specified (explicitly or by default), the cursor is set to point to the list entry following the created or processed list entry, except when it is the tail entry of the list, in which case the cursor is set to all binary zeros.
• When MOVETODIRECTION or DIRECTION=TAILTOHEAD is specified, the cursor is set to point to the list entry preceding the created or processed list entry, except when it is the head entry of the list, in which case the cursor is set to all binary zeros.

NEXTCOND

Set the list cursor as follows:

• If the list cursor points to the list entry processed for the request, and the list entry is deleted or moved to another list, set the cursor to point to the preceding or following list entry, depending on the DIRECTION specified. If the deleted or moved list entry was the last entry on the list and DIRECTION=HEADTOTAIL, or the deleted or moved list entry was the first entry on the list and DIRECTION=TAILTOHEAD, set the list cursor to binary zeros.
• If the list cursor points to the list entry processed for the request, and the list entry is moved to the same list, the cursor will remain pointing to the moved list entry.

The list cursor direction may be set by specifying SETCURSOR on an IXLLSTC WRITE_LCONTROLS request.

CURRENT

Set the list cursor as follows:

• If the list entry is created, set the list cursor to point to the created list entry.
• If the list entry is deleted or moved to another list, set the list cursor to binary zeros.
• If the list entry is moved to the same list, leave the list cursor to remain pointing to the moved list entry.
• For all other cases where the list entry is processed and remains on the same list, set the list cursor to point to the processed list entry.

CURRENTCOND

Set the list cursor as follows:

• If the list entry is created, and if the list cursor does not point to a list entry, set the list entry to point to the created list entry.
• If the list entry for the list specified for LISTNUM does not point to a list entry, and the list entry is moved to another list, the list cursor will remain binary zeros.
• If the list cursor does not point to a list entry, and the list entry is moved from and to the same list, set the cursor to point to the moved list entry.
• For all other cases where the list cursor does not point to a list entry, and the list entry is processed and remains on this same list, set the list cursor to point to the processed list entry.

If the list entry is deleted or moved to another list, then the list cursor will remain binary zeros.

• To place the newly created list entry,
• To designate a list entry to be processed, or
• To specify the direction relative to the current entry in which the cursor is to be updated to point to the next entry on the list when CURSORUPDTYPE=NEXT is specified with UPDATECURSOR=YES.

KEEP

The list entry is to remain on the list after the read is performed.

DELETE

The list entry is to be deleted after the read is performed.

To Code: Specify the RS-type name or address (using a register from 2 to 12) of a 1-byte field that contains the number of elements.

• An entry identifier to be used to identify an existing list entry to be processed.
• An entry identifier to be assigned to a newly created list entry.

To Code: Specify the RS-type name or address (using a register from 2 to 12) of a 12-byte field that contains the entry identifier.

• Specify an entry key to be used in conjunction with LISTNUM, DIRECTION, and KEYREQTYPE to locate the entry to be processed.
• Specifies an entry key to be assigned to the list entry if it is created. If there exists a sublist of one or more entries with a matching key on the list, the target position is at the head or tail of the sublist, as specified by DIRECTION. If all existing list entries have a key greater that that specified by ENTRYKEY, the target position is at the head of the list. Similarly, if the specified ENTRYKEY exceeds all of the entry keys, the target position is at the tail of the list. If none of the list entries has a matching key, and ENTRYKEY is neither the greatest nor least among the entry keys, the target position is determined according to key sequence for the list.
• For structures allocated in a coupling facility of CFLEVEL=9 or higher, when the request specifies KEYCOMPARE=YES, specifies the entry key to be compared to the entry key of the designated entry.

To Code: Specify the RS-type name or address (using a register from 2 to 12) of a 16-byte field that contains the entry key.

• Assign an entry name to a new entry to be created.
• Designate an existing entry to be processed.

Specify ENTRYNAME only for structures that support named entries. Each entry name is unique within the structure.

To Code: Specify the RS-type name or address (using a register from 2 to 12) of a 16-byte field that contains the entry name.

NEW

Write to a new list entry the contents of either the storage area specified by BUFFER or the buffers specified by BUFLIST, and the storage area specified by ADJAREA. LISTNUM designates the list number on which the created entry is to reside. The value of ASSIGN specifies whether to assign an ENTRYNAME, ENTRYKEY, or list key value to the newly created list entry. If the structure was allocated to use secondary keys, a secondary key value may be assigned to the newly created list entry.

• If the structure supports entry data and BUFFER and BUFLIST are not specified, the created entry will not contain any entry data.
• If the structure supports adjunct data and ADJAREA is not specified, the created entry will contain binary zeros for adjunct data.

When the amount of space indicated by ELEMNUM is greater than the amount of data specified for BUFFER or BUFLIST, the entry will be padded with zeros. When the amount of space indicated by ELEMNUM is less than the amount of data specified for BUFFER or BUFLIST, the input data will be truncated.

Specifying AUTHCOMPARE in conjunction with AUTHCOMP causes the list authority for the list designated by LISTNUM to precede processing. If the list authority comparison ciriterion is not met, the IXLLSTE request is terminated.

If LOCKINDEX is specified, the lock entry designated by LOCKINDEX will be operated on a specified by the LOCKOPER keyword.

The new list entry will be created as follows:

• If the structure was not allocated to use named entries or keyed entries, the newly created entry will be placed on the list specified by LISTNUM at the head or tail as specified by DIRECTION.
• If the structure was allocated to use named entries, the entry name specified for ENTRYNAME is assigned to the newly created list entry, provided a list entry does not already exist with the same entry name. The newly created entry will be placed on the list specified by LISTNUM at the head or tail as specified by DIRECTION.
• If the structure was allocated to use keyed entries, an entry key (and therefore, the target list keyed position) is assigned to the newly created list entry as follows:
  • If ASSIGN=NONE is specified, then:
    • If DIRECTION=HEADTOTAIL is specified (explicitly or by default), the newly created list entry is assigned an entry key value of all binary zeros.
    • If DIRECTION=TAILTOHEAD is specified, the newly created list entry is assigned an entry key value of all binary ones.
  • If ASSIGN=KEY is specified, the newly created list entry is assigned the value specified for ENTRYKEY.
  • If ASSIGN=LISTKEY is specified, the newly created list entry is assigned the list key value.
  • If the assigned entry key is zero, the newly created list entry is placed at the head of the list specified by LISTNUM.
  • If the assigned entry key is non-zero, the newly created list entry is placed on the list specified by LISTNUM at the head or tail of the sublist composed of list entries whose entry keys are equal to the assigned entry key. The newly created list entry is placed at the head or tail of this sublist as specified by DIRECTION. If a sublist of entries with entry keys equal to the assigned entry key does not yet exist, the newly created list entry is placed on the list in key sequence.
• If the structure was allocated to use user-provided ENTRYIDs, the newly created list entry is assigned the ENTRYID specified by ASSIGNENTRYID, provided a list entry does not already exist with the same ENTRYID.
• If the structure supports secondary keys, the secondary key specified by SECONDARYKEY will be assigned to the newly created list entry. If the user does not supply SECONDARYKEY, the newly created list entry is assigned a secondary key of all binary zeros.
  • The newly created list entry is placed on the list specified by LISTNUM at the head or tail, relative to secondary key ordering, of the sublist composed of list entries whose secondary keys are equal to the assigned secondary key. The newly created list entry is placed at the head or tail of this sublist as specified by SKEYTARGETDIR. If a sublist of entries with secondary keys equal to the assigned secondary key does not yet exist, the target position relative to secondary key ordering is determined according to secondary key sequence for the list.

When the request completes successfully, the list entry controls, the number of entries or elements residing on the list, and the total number of allocated entries in the structure are returned in the answer area specified by ANSAREA.

OLD

Perform a read, write, move, or delete operation on an existing entry designated by the LOCATOR keyword. If the entry is not found, the requested operation is not performed and no change is made to the list structure.

Specifying AUTHCOMPARE in conjunction with AUTHCOMP causes the list authority for the list designated by LISTNUM to precede processing. If the list authority comparison ciriterion is not met, the IXLLSTE request is terminated.

If LOCKINDEX is specified, the lock entry designated by LOCKINDEX will be operated on as specified by the LOCKOPER keyword.

If the lock comparison criterion is not met, the IXLLSTE request is terminated.

In order for the request to be performed, any and all requested comparison criteria must be met. Namely, authority comparison, list number comparison, version number comparison, lock comparison, and key comparison must each succeed if requested.

ANY

Perform the specified operation on the designated entry if it exists. If the designated entry does not exist, a new entry will be created.

Specifying AUTHCOMPARE in conjunction with AUTHCOMP causes the list authority for the list designated by LISTNUM to precede processing. If the list authority comparison ciriterion is not met, the IXLLSTE request is terminated.

If LOCKINDEX is specified, the lock entry designated by LOCKINDEX will be operated on as specified by the LOCKOPER keyword.

In order for the request to be performed on an existing list entry, any and all requested comparison criteria must be met. Namely, list number comparison, version number comparison, lock comparison, and key comparison must each succeed if requested.

NO

No key comparison should be performed to determine whether the list entry should be processed.

YES

Key comparison should be performed to determine whether the list entry should be processed. If the designated list entry exists but the requested key comparison criterion is not met, the IXLLSTE request is terminated.

KEYCOMPARE=YES is only meaningful when the structure is allocated in a coupling facility of CFLEVEL=9 or higher. KEYCOMPARE=YES will be ignored if the target structure was not allocated with keyed list entries.

The KEYPOSITION keyword is only meaningful for list structures allocated in a coupling facility of CFLEVEL=9 or higher.

UPDATE

The list entry should be moved from its current position on the sublist to a position on the sublist as specified by MOVETODIRECTION and MOVETOKEY.

KEEP

The list entry should keep its current position based on entry key ordering on the sublist if and only if the list number specified by MOVETOLIST matches the current list number that contains the list entry, and the list entry is not changed by the move operation when MOVETOKEY=UNCHANGED is specified (explicitly or by default).

EQUAL

• The designated list entry must have a key equal to the value specified for ENTRYKEY. If the entry key is not equal to the value specified for ENTRYKEY, the IXLLSTE request is terminated.
• When LOCATOR=KEYPOS, specifies that if a list entry exists with an entry key equal to the value specified for ENTRYKEY, that list entry is to be processed. If more than one such entry exists, the list entry at either the head or tail of the sublist as specified by DIRECTION is designated for processing. If no such entry exists, the IXLLSTE request is terminated.

LESSOREQUAL

• The designated list entry must have an entry key that is equal to or less than the value specified for ENTRYKEY. If the entry key is not equal to or less than the value specified for ENTRYKEY, the IXLLSTE request is terminated.
• When LOCATOR=KEYPOS, specifies that:
  • If a list entry exists with an entry key equal to the value specified for ENTRYKEY, that entry is designated for processing. If more than one such entry exists, the list entry at the head or tail of the sublist as specified by DIRECTION is designated for processing.
  • If no list entries exist with an equal entry key, the list entry with the highest entry key less than the value specified for ENTRYKEY is designated for processing. If more than one such entry exists, the list entry at the head or tail of the sublist as specified by DIRECTION is designated for processing.
  • If no list entries exist with an entry key equal to or less than the value specified for ENTRYKEY, the IXLLSTE request is terminated.

GREATEROREQUAL

• The designated list entry must have an entry key that is equal to or greater than the value specified for ENTRYKEY. If the entry key is not equal to or greater than the value specified for ENTRYKEY, the IXLLSTE request is terminated.
• When LOCATOR=KEYPOS, specifies that:
  • If a list entry exists with an entry key equal to the value specified for ENTRYKEY, that entry is designated for processing. If more than one such entry exists, the list entry at the head or tail of the sublist as specified by DIRECTION is designated for processing.
  • If no list entries exist with an equal entry key, the list entry with the lowest entry key greater than the value specified for ENTRYKEY is designated for processing. If more than one such entry exists, the list entry at the head or tail of the sublist as specified by DIRECTION is designated for processing.
  • If no list entries exist with an entry key equal to or greater than the value specified for ENTRYKEY, the IXLLSTE request is terminated.

ENTRY

The list entry will be located by list entry key.

SECONDARY

The list entry will be located by secondary key.

KEYTYPE=SECONDARY is valid only when the structure is allocated in a coupling facility of CFLEVEL=9 or higher.

NO

No list number comparison whould be performed to determine whether the list entry should be processed.

YES

List number comparison should be performed to determine whether the list entry should be processed.

The list number value specified for LISTNUM is compared with the list number on which the designated list entry resides. If the designated list entry exists but does not reside on the list specified by LISTNUM, the IXLLSTE request is terminated.

To Code: Specify the RS-type name or address (using a register from 2 to 12) of the fullword field that contains the value to be added to the list key after the entry key is set to the list key value.

ENFORCE

The move request will be failed if the list-entry count would exceed the current list-entry count limit of the target list or the list-element count would exceed the list-element count limit of the target list as a result of the move request.

IGNORE

The move request will proceed even if the list-entry count would exceed the current list-entry count limit of the target list or the list-element count would exceed the list-element count of the target list as a result of this move request.

• Designate the list number (when ENTRYTYPE=NEW) on which the newly created list entry should be placed.
• Check if the entry exists on the list (when ENTRYTYPE=ANY) before proceeding with the request.
• Confirm that the entry exists on the list (when ENTRYTYPE=OLD) before proceeding with the request.

To Code: Specify the RS-type name or address (using a 2 register from 2 to 12) of a 4-byte field that contains the number of the list.

CURSOR

The list cursor should be used to designate the list entry to be processed.

ENTRYID

The ENTRYID is to be used to designate the list entry to be processed.

ENTRYNAME

The entry name specified by ENTRYNAME is to be used to designate the list entry to be processed.

LOCATOR=ENTRYNAME may only be specified when the structure was allocated to use named entries.

UNKEYPOS

LISTNUM and DIRECTION are to be used to designate the list entry at the head or tail of the list to be processed.

KEYPOS

LISTNUM, DIRECTION, and the key specified by KEYTYPE are to be used to designate the list entry to be processed.

When LOCKCOMP is specified, the completion of the request is conditional on there being no contention for the lock. If contention exists, the request will fail.

The connection identifier is available from the IXLCONN answer area, mapped by IXLYCONA, in field CONACONID.

The effect of LOCKCOMP is based on the LOCKOPER value specified. See the description under LOCKOPER to see how each request is affected by this parameter.

To Code: Specify the RS-type name or address (using a register from 2 to 12) of a 1-byte field that contains the connection identifier.

• LOCKOPER=SET
• LOCKOPER=NOTHELD with LOCKMODE=UNCOND

To Code: Specify the RS-type name or address (using a register from 2 to 12) of an 8-byte field that contains the user-defined information.

UNCOND

If the specified lock is held by another user, your request is either:

• Suspended until the lock becomes available (if MODE=SYNCSUSPEND is specified).
• Performed asynchronously with notification to you when the request completes (if any MODE value other than SYNCSUSPEND is specified).

COND

The lock operation will be performed conditionally; that is, only if there is no contention for the lock. If the specified lock is held by another user, the request will be terminated with no change to the structure, and return and reason codes describing the termination are returned to the caller.

SET

Set the lock.

• When LOCKCOMP is not specified, your connection gets the lock, providing no other connection holds the lock. If another connection holds the lock, the request either continues once the lock is released or fails, depending on the LOCKMODE value you specify.
• When LOCKCOMP is specified, if the connection specified by LOCKCOMP holds the lock, the lock will be transferred to your connection.

RESET

Reset the lock.

• When LOCKCOMP is not specified, the lock will be released if it is held by your connection.
• When LOCKCOMP is specified, the lock will be released if it is held by the connection specified by LOCKCOMP.

NOTHELD

The request is performed only if the lock is not held by any connection. This option also ensures that the lock remains free for the duration of the request. If another connection holds the lock, your task is suspended until the lock is released or your request fails, depending on the LOCKMODE value you specify. See the LOCKMODE description for how to handle possible lock contention.

HELDBY

Processing is determined by which connector is holding the lock.

• When LOCKCOMP is not specified, the request is performed only if your connection holds the lock.
• When LOCKCOMP is specified, the request is performed only if the lock is held by the connection specified by LOCKCOMP.

Use MF=L to specify the list form of the macro. Use the list form together with the execute form of the macro for applications that require reentrant code. The list form defines an area of storage that the execute form uses to store the parameters. Only the PLISTVER parameter can be coded with the list form of the macro.

SYNCSUSPEND

The request will be performed synchronously. Control is not returned to the caller until request processing is complete and the final disposition determined.

If necessary, the caller will be suspended until the request completes. The caller must be executing in an enabled state to use this option.

SYNCECB

The request will be attempted synchronously. If the request cannot be completed synchronously, control is returned to the caller prior to completion of the request, and the ECB specified by REQECB is posted when the request has completed.

If the request does not complete synchronously, latent XES binds to the storage locations specified by BUFFER, BUFLIST, MOSVECTOR, and ANSAREA persist until the REQECB ECB is posted.

SYNCEXIT

The request will be attempted synchronously. If the request cannot be completed synchronously, control is returned to the caller prior to completion of the request. When the request completes, the connection's Complete Exit will be called.

If the request does not complete synchronously, latent XES binds to the storage locations specified by BUFFER, BUFLIST, MOSVECTOR, and ANSAREA persist until the connection's Complete Exit is called.

SYNCTOKEN

The request will be attempted synchronously. If the request cannot be completed synchronously, control is returned to the caller prior to completion of the request and a token that uniquely identifies the request is returned. This token must be specified on a subsequent invocation of IXLFCOMP to force completion of the request and determine its final disposition.

If the request does not complete synchronously, latent XES binds to the storage locations specified by BUFFER, BUFLIST, MOSVECTOR, and ANSAREA persist until a subsequent corresponding IXLFCOMP request indicates completion of the original request.

SYNCECB

The request is to be initiated and control is to be returned to the caller prior to completion of the request. When the request completes, the ECB specified by REQECB will be posted.

Latent XES binds to the storage locations specified by BUFFER, BUFLIST, MOSVECTOR, and ANSAREA persist until the REQECB ECB is posted.

ASYNCEXIT

The request is to be initiated and control is to be returned to the caller prior to completion of the request. When the request completes, the connection's Complete Exit will be called.

Latent XES binds to the storage locations specified by BUFFER, BUFLIST, MOSVECTOR, and ANSAREA persist until the connection's Complete Exit is called.

ASYNCTOKEN

The request is to be initiated, a token generated that uniquely identifies the request on this system, and control returned to the caller prior to completion of the requested operation. The token must be specified on a subsequent invocation of IXLFCOMP to force completion of the request and determine its final disposition.

Latent XES binds to the storage locations specified by BUFFER, BUFLIST, MOSVECTOR, and ANSAREA persist until a subsequent corresponding IXLFCOMP request indicates completion of the original request.

ASYNCNORESPONSE

The request is to be initiated and control returned to the caller prior to completion of the requested operation. No asynchronous request token is returned, hence no external mechanism exists to force completion of the request.

MODE=ASYNCNORESPONSE is mutually exclusive with LOCKINDEX, BUFFER, and BUFLIST. Any request which does not perform a locking operation and does not use a BUFFER area or BUFLIST buffers may specify MODE=ASYNCNORESPONSE.

HEADTOTAIL

One of the following:

• If the list entry is moved or created as a result of this request, and the structure was not allocated to use keyed entries, the list entry will be placed at the head of the list designated by MOVETOLIST.
• If the list entry is moved or created as a result of this request, and the structure was allocated to use keyed entries, the entry will be placed at the head of the sublist designated by MOVETOLIST and the assigned entry key.

TAILTOHEAD

One of the following:

• If the list entry is moved or created as a result of this request, and the structure was not allocated to use keyed entries, the list entry will be placed at the tail of the list designated by MOVETOLIST.
• If the list entry is moved or created as a result of this request, and the structure was allocated to use keyed entries, the entry will be placed at the tail of the sublist designated by MOVETOLIST and the assigned entry key.

To Code: Specify the RS-type name or address (using a register from 2 to 12) of a 16-byte field that contains the key.

To Code: Specify the RS-type name or address (using a register from 2 to 12) of a 4-byte field that contains the number of the target list.

When the structure is allocated, the authority value for each list is initialized to binary zeros.

To Code: Specify the RS-type name or address (using a register from 2 to 12) of the 16-byte field that contains the list authority value.

To Code: Specify the RS-type name or address (using a register from 2 to 12) of an 8-byte field that contains the entry version number.

YES

Specify this option to indicate that the BUFFER or BUFLIST buffers reside in pageable virtual storage.

This includes disabled reference (DREF) storage, and may include storage that has the potential to become pageable during the processing of a request. (An example is address space storage owned by any swappable address space, for which a PGSER FIX has been successfully processed, but for which the owning address space gets swapped during processing of a cache or list request.) It does not include implicitly non-pageable storage (such as is obtained from non-pageable subpools).

The system takes responsibility for managing binds to central storage for the duration of the list request, regardless of what address space owns the storage or whether the storage-owning address space is swappable or nonswappable. The storage can be owned by any address space.

NO

Specify this option to indicate that the BUFFER or BUFLIST buffers reside in non-pageable virtual storage.

This includes implicitly non-pageable storage areas. If the virtual storage may potentially become pageable, the invoker is responsible for ensuring the virtual storage remains non-pageable for the duration of the request. (An example is address space storage owned by any swappable address space, for which a PGSER FIX has been successfully processed, but for which the owning address space gets swapped-out during processing of a list request.)

If MODE=ASYNCTOKEN is specified or MODE=SYNCTOKEN is specified and the request does not complete synchronously, the storage must remain non-pageable until completion of the corresponding IXLFCOMP request. If MODE=ASYNCEXIT is specified or MODE=SYNCEXIT is specified and the request does not complete synchronously, the storage must remain non-pageable until the complete exit is driven for the request. If MODE=ASYNCECB is specified or MODE=SYNCECB is specified and the request does not complete synchronously, the storage must remain non-pageable until the specified ECB is posted for the request.

The system takes responsibility for managing binds to central storage for the duration of the list request, if and only if the non-pageable storage is owned by either the requestor's address space or the connector's address space. If the storage is owned by any other address space, then the invoker is responsible for ensuring that the virtual storage remains non-pageable for the duration of the request (including the case in which the storage is owned by a swappable address space that is swapped during processing of a list request). Subject to this consideration, the storage can be owned by any address space. See z/OS MVS Programming: Sysplex Services Guide.

To Code: Specify the RS-type name or address (using a register from 2 to 12) of an 8-byte field that contains the data to be passed to the complete exit.

To Code: Specify the RS-type name or address (using a register from 2 to 12) of a 4-byte field that contains the address of the ECB to be posted when the request completes. The ECB must be aligned on a fullword boundary.

To Code: Specify the RS-type name or address (using a register from 2 to 12) of an 8-byte field that contains the user-defined request identifier.

To Code: Specify the RS-type name or address (using a register from 2 to 12) of a 16-byte field where the system will put the request token.

READ

The entry data and adjunct data and list entry controls for the designated entry are to be read.

Entry data is to be read into the storage area specified by BUFFER or the buffers specified by BUFLIST. Adjunct data is to be read into the storage area specified by ADJAREA. The absence of BUFFER, BUFLIST, and ADJAREA specifies the request is only interested in obtaining the list entry controls in the answer area specified by ANSAREA.

When the request completes successfully, the list entry controls, the number of entries or elements residing on the list, and the total number of allocated entries in the structure are returned in the answer area specified by ANSAREA.

WRITE

• For requests that specify either ENTRYTYPE=OLD or ENTRYTYPE=ANY and the designated entry already exists:

  The contents of the storage area specified by BUFFER or the buffers specified by BUFLIST, and the storage area specified by ADJAREA are to be written to the designated list entry.

  The size of list entry may be altered by specifying an ELEMNUM value that is different than the ELEMNUM value used when the entry was created. When the amount of space indicated by ELEMNUM is greater than the amount of data specified for BUFFER or BUFLIST, the entry will be padded with zeros. When the amount of spece indicated by ELEMNUM is less than the amount of data specified for BUFFER or BUFLIST, the input data will be truncated.

  When the request completes successfully, the list entry controls, the number of entries or elements residing on the list, and the total number of allocated entries in the structure are returned in the answer area specified by ANSAREA.

• For requests that specify ENTRYTYPE=ANY and the designated list entry does not exist, a new list entry will be created as follows:
  • If the structure was not allocated to use named entries or keyed entries, the newly created entry will be placed on the list specified by LISTNUM at the head or tail as specified by DIRECTION.
  • If the structure was allocated to use named entries, the entry name specified for ENTRYNAME is assigned to the newly created list entry, provided a list entry does not already exist with the same entry name. The newly created entry will be placed on the list specified by LISTNUM at the head or tail as specified by DIRECTION.
  • If the structure was allocated to use keyed entries, an entry key (and therefore, the target list keyed position) is assigned to the newly created list entry as follows:
    • If ASSIGN=NONE is specified, then:
      • If DIRECTION=HEADTOTAIL is specified (explicitly or by default), the newly created list entry is assigned an entry key value of all binary zeros.
      • If DIRECTION=TAILTOHEAD is specified, the newly created list entry is assigned an entry key value of all binary ones.
    • If ASSIGN=KEY is specified, the newly created list entry is assigned the value specified for ENTRYKEY.
    • If ASSIGN=LISTKEY is specified, the newly created list entry is assigned the list key value.
    • If the assigned entry key is zero, the newly created list entry is placed at the head of the list specified by LISTNUM.
    • If the assigned entry key is non-zero, the newly created list entry is placed on the list specified by LISTNUM at the head or tail of the sublist composed of list entries whose entry keys are equal to the assigned entry key. The newly created list entry is placed at the head or tail of this sublist as specified by DIRECTION. If a sublist of entries with entry keys equal to the assigned entry key does not yet exist, the newly created list entry is placed on the list in key sequence.
  • If the structure was allocated to use user-provided ENTRYIDs, the newly created list entry is assigned the ENTRYID specified by ASSIGNENTRYID, provided a list entry does not already exist with the same ENTRYID.
  • If the structure supports entry data and BUFFER and BUFLIST are not specified, the newly created list entry will not contain any entry data.
  • If the structure supports adjunct data and ADJAREA is not specified, the newly created list entry will contain binary zeros for adjunct data.
  • If the structure supports secondary keys, the secondary key specified by SECONDARYKEY will be assigned to the newly created list entry. If the user does not supply SECONDARYKEY, the newly created list entry is assigned a secondary key of all binary zeros.
    • The newly created list entry is placed on the list specified by LISTNUM at the head or tail, relative to secondary key ordering, of the sublist composed of list entries whose secondary keys are equal to the assigned secondary key. The newly created list entry is placed at the head or tail of this sublist as specified by SKEYTARGETDIR. If a sublist of entries with secondary keys equal to the assigned secondary key does not yet exist, the target position relative to secondary key ordering is determined according to secondary key sequence for the list.

MOVE

• When the request specifies ENTRYTYPE=OLD:
  • The designated list entry is to be moved from its current location and placed at the position specified by MOVETOLIST, MOVETODIRECTION, and if keyed entries are being used, the entry key specified by MOVETOKEY.

    When ACTION=READ and ACTION=WRITE, in addition to moving the list entry, the entry data and/or adjunct data is read into the storage areas specified by BUFFER or BUFLIST and, if applicable, ADJAREA.

    When the request completes successfully, the list entry controls, the number of entries or elements residing on the target list, and the total number of allocated entries in the structure are returned in the answer specified by ANSAREA.

  • If the structure was allocated to use keyed entries, an entry key is assigned to the moved list entry as follows:
    • If TARGETKEY is specified with MOVETOKEY=TARGETKEY, the list entry is assigned the entry key specified by TARGETKEY.
    • If MOVETOKEY=LISTKEY, the list entry is assigned the current list key value of the target list.
    • If MOVETOKEY=UNCHANGED, the entry key of the list entry remains unchanged.
• When the request specifies ENTRYTYPE=ANY and ACTION=WRITE, and the designated list entry exists:
  • In addition to moving the list entry, the data in the storage area(s) specified by BUFFER or BUFLIST and, if applicable ADJAREA, is written to the list entry. If BUFFER or BUFLIST is not specified, entry data is not to be written. If ADJAREA is not specified, structure adjunct data will not be written.
  • The size of an existing list entry may be altered by specifying an ELEMNUM value that is different from the ELEMNUM value used when the entry was created. When the amount of space indicated by ELEMNUM is greater than the amount of data specified for BUFFER or BUFLIST, the entry will be padded with zeros. When the amount of space indicated by ELEMNUM is less than the amount of data specified for BUFFER or BUFLIST, the input data will be truncated.
  • The designated list entry will be moved as follows:
    • If the structure was not allocated to use keyed entries, the list entry will be placed on the list specified by MOVETOLIST at the head or tail as specified by MOVETODIRECTION.
    • The moved list entry is placed on the list specified by MOVETOLIST at the head or tail of the sublist composed of list entries whose entry keys are equal to the assigned entry key. The moved list entry is placed at the head or tail of this sublist as specified by MOVETODIRECTION. If a sublist of entries with entry keys equal to the assigned entry key does not yet exist, the moved list entry is placed on the list in key sequence.
    • The moved list entry is placed on the list specified by MOVETOLIST at the head or tail of the sublist composed of list entries whose secondary keys are equal to the assigned secondary key. The moved list entry is placed at the head or tail of this sublist as specified by SKEYTARGETDIR. If a sublist of entries with secondary keys equal to the assigned secondary key does not yet exist, the moved list entry is placed on the list in secondary key sequence.
  • If the structure was allocated to use keyed entries, an entry key (and therefore, the target list keyed position) is assigned to the list entry as follows:
    • If TARGETKEY=NO_TARGETKEY is specified (explicitly or by default) with ASSIGNLISTKEY=NO or with ASSIGNLISTKEY=CREATE, the entry key remains unchanged.
    • If TARGETKEY is specified with ASSIGNLISTKEY=NO or with ASSIGNLISTKEY=CREATE, the entry key is assigned the value specified for TARGETKEY.
    • If ASSIGNLISTKEY=MOVE or ASSIGNLISTKEY=ANY is specified, the entry key is assigned the list key value of the target list.
  • When the request specifies ENTRYTYPE=ANY and the designated list entry does not exist, a new list entry will be created as follows:
    • If the structure was not allocated to use named entries or keyed entries, the newly created entry will be placed on the list specified by MOVETOLIST at the head or tail as specified by MOVETODIRECTION.
    • If the structure was allocated to use named entries, the entry name specified for ENTRYNAME is assigned to the newly created list entry, provided a list entry does not already exist with the same entry name. The newly created entry will be placed on the list specified by MOVETOLIST at the head or tail as specified by MOVETODIRECTION.
    • If the structure was allocated to use keyed entries, an entry key (and therefore, the target list keyed position) is assigned to the newly created list entry as follows:
      • If ENTRYKEY is not specified, and TARGETKEY=NO_TARGETKEY is specified (explicitly or by default) with ASSIGNLISTKEY=NO or with ASSIGNLISTKEY=MOVE, then:
        • If MOVETODIRECTION=HEADTOTAIL is specified (explicitly or by default), the newly created list entry is assigned an entry key value of all binary zeros.
        • If MOVETODIRECTION=TAILTOHEAD is specified, the newly created list entry is assigned an entry key value of all binary ones.
      • If ENTRYKEY is specified, and TARGETKEY=NO_TARGETKEY is specified (explicitly or by default) with ASSIGNLISTKEY=NO or with ASSIGNLISTKEY=MOVE, the newly created list entry is assigned the value specified by ENTRYKEY.
      • If TARGETKEY is specified with ASSIGNLISTKEY=NO or with ASSIGNLISTKEY=MOVE, the newly created list entry is assigned the value specified for TARGETKEY.
      • If ASSIGNLISTKEY=CREATE or ASSIGNLISTKEY=ANY is specified, the newly created list entry is assigned the list key value of the target list.
      • The newly created list entry is placed on the list specified by MOVETOLIST at the head or tail of the sublist composed of list entries whose entry keys are equal to the assigned entry key. The newly created list entry is placed at the head or tail of this sublist as specified by MOVETODIRECTION. If a sublist of entries with entry keys equal to the assigned entry key does not yet exist, the newly created list entry is placed on the list in key sequence.
      • The newly created list entry is placed on the list specified by MOVETOLIST at the head or tail of the sublist composed of list entries whose secondary keys are equal to the secondary key of the moved entry. The newly created list entry is placed at the head or tail of this sublist as specified by SKEYTARGETDIR. If a sublist of entries with secondary keys equal to the assigned secondary key does not yet exist, the newly created list entry is placed on the list in secondary key sequence.
    • If the structure was allocated to use user provided ENTRYIDs, the newly created list entry is assigned the ENTRYID specified by ASSIGNENTRYID, provided a list entry does not already exist with the same ENTRYID.
    • If the structure supports entry data and BUFFER and BUFLIST are not specified, the newly created list entry will not contain any entry data.
    • If the structure supports adjunct data and ADJAREA is not specified, the newly created list entry will contain binary zeros for adjunct data. If the structure was allocated to use secondary keys, then the first 32 bytes of the adjunct data will be occupied by the secondary key which may or may not be zeros.

DELETE

The designated list entry is to be removed from the list on which it resides and returned to the pool of free entries for reuse.

When the request completes successfully, the list entry controls for the deleted entry, the remaining number of entries or elements residing on the list, and the remaining total number of allocated entries in the structure are returned in the answer area specified by ANSAREA.

To Code: Specify the RS-type name or address (using a register from 2 to 12) of a 4-byte field that will contain the return code when the request has completed.

To Code: Specify the RS-type name or address (using a register from 2 to 12) of a 4-byte field that will contain the reason code (if any) when the request has completed.

• Specify a secondary key to be used in conjunction with LISTNUM, DIRECTION, and SKEYREQTYPE to locate the list entry to be processed.
• Specify a secondary key to be assigned to the list entry if it is created. SKEYTARGETDIR is used to specify the position relative to secondary key ordering on the sublist at which to place the newly created list entry. If there exists a sublist of one or more entries with a matching secondary key on the list, the target position is at the head or tail of the sublist, as specified by SKEYTARGETDIR. If all existing list entries have a secondary key greater than that specified by SECONDARYKEY, the target position relative to secondary key ordering is at the head of the list. Similarly, if the specified SECONDARYKEY exceeds all of the secondary keys, the target position relative to secondary key ordering is at the tail of the list. If none of the list entries has a matching secondary key, and SECONDARYKEY is neither the greatest nor least among the secondary keys, the target position relative to secondary key ordering is determined according to secondary key sequence for the list.
• For structures allocated in a coupling facility of CFLEVEL=9 or higher, when the request specifies SKEYCOMPARE=YES, specifies the secondary key to be compared to the secondary key of the designated entry.

If the user does not supply SECONDARYKEY, the secondary key will be set to all binary zeros.

To Code: Specify the RS-type name or address (using a register from 2 to 12) of the 32-byte field that contains the secondary key to be assigned to the list entry.

NO

No secondary key comparison should be performed to determine whether the list entry should be processed.

YES

Secondary key comparison should be performed to determine whether the list entry should be processed. if the designated list entry exists but the requested key comparison criterion is not met, the IXLLSTE request is terminated.

SKEYCOMPARE=YES is only meaningful when the structure is allocated in a coupling facility of CFLEVEL=9 or higher.

SKEYCOMPARE=YES will be ignored if the target structure was not allocated with secondary keys.

The SKEYPOSITION keyword is only meaningful for list structures allocated in a coupling facility of CFLEVEL=9 or higher.

UPDATE

The list entry should be moved from its current position on the secondary sublist to a position on the secondary sublist as specified by SKEYTARGETDIR.

KEEP

The list entry should keep its current position based on secondary key ordering on the secondary sublist if and only if the list number specified by MOVETOLIST matches the current list number that contains the list entry.

EQUAL

• The designated list entry must have a secondary key equal to the value specified for SECONDARYKEY. If the secondary key of the entry is not equal to the value specified for SECONDARYKEY, the IXLLSTE request is terminated.
• When LOCATOR=KEYPOS, specifies that if a list entry exists with a secondary key equal to the value specified for SECONDARYKEY, that entry is designated for processing. If more than one such entry exists, the list entry at either the head or tail of the sublist as specified by DIRECTION is designated for processing. If no such entry exists, the IXLLSTE request is terminated.

LESSOREQUAL

• The designated list entry msut have a secondary key equal to or less than the value specified for SECONDARYKEY. If the secondary key of the entry is not equal to or less than the value specified for SECONDARYKEY, the IXLLSTE request is terminated.
• When LOCATOR=KEYPOS, specifies that:
  • If a list entry exists with a secondary key equal to or less than the value specified for SECONDARY key, that entry is designated for processing. If more than one such entry exists, the list entry at the head or tail of the sublist as specified by DIRECTION is designated for processing.
  • If no list entries exist with an equal secondary key, the list entry with the highest secondary key less than the value specified for SECONDARYKEY is designated for processing. If more than one such entry exists, the list entry at the head or tail of the sublist as specified by DIRECTION is designated for processing.
  • If no list entries exist with a secondary key equal to or less than the value specified for SECONDARYKEY, the IXLLSTE request is terminated.

GREATEROREQUAL

• The designated list entry must have a secondary key equal to or greater than the value specified for SECONDARYKEY. If the secondary key of the entry is not equal to or greater than the value specified for SECONDARYKEY, the IXLLSTE request is terminated.
• When LOCATOR=KEYPOS, specifies that:
  • If a list entry exists with a secondary key equal to the value specified for SECONDARYKEY, that entry is designated for processing. If more than one such entry exists, the list entry at the head or tail of the sublist as specified by DIRECTION is designated for processing.
  • If no list entries exist with an equal secondary key, the list entry with the lowest secondary key greater than the value specified for SECONARYKEY is designated for processing. If more than one such entry exists, the list entry at the head or tail of the sublist as specified by DIRECTION is designated for processing.
  • If no list entries exist with a secondary key equal to or greater than the value specified for SECONDARYKEY, the IXLLSTE request is terminated.

SKEYTARGETDIR is only valid when the structure is allocated in a coupling facility of CFLEVEL=9 or higher.

HEADTOTAIL

The designated position is at the head of the sublist designated by the secondary key value.

TAILTOHEAD

The designated position is at the tail of the sublist designated by the secondary key value.

This keyword is only applicable to a structure that was allocated to used keyed entries, and is otherwise ignored.

To Code: Specify the RS-type name or address (using a register from 2 to 12) of a 16-byte area that contains the entry key to be assigned to the list entry.

If the structure was allocated with keyed entries, the entry key order is always used to determine the next or previous list entry. Note that the secondary key order is not relevant in determining the next or previous list entry.

NO

The cursor should not be updated.

Note that the list cursor will be set to binary zeros if it points to an entry that is deleted or moved to another list as a result of this request regardless of how UPDATECURSOR is specified.

YES

The cursor should be updated.

If the list entry specified on the request exists, the list cursor for the list on which the entry resides is updated before the list entry is processed for the request.

The CURSORUPDTYPE values of NEXTCOND, CURRENT, and CURRENTCOND are only meaningful for list structures allocated in a coupling facility of CFLEVEL=1 or higher.

The existing entry is moved only if its version number meets the condition specified by the VERSCOMPTYPE parameter. If the entry does not have the specified version number, the request is terminated with no change to the structure.

To Code: Specify the RS-type name or address (using a register from 2 to 12) of an 8-byte field that contains the version number.

NO

No version number comparison should be performed to determine whether the list entry should be processed.

YES

Version number comparison should be performed to determine whether the list entry should be processed.

VERSCOMPTYPE=EQUAL

The version number for the list entry must be equal to the value specified for VERSCOMP.

VERSCOMPTYPE=LESSOREQUAL

The version number for the list entry must be less than or equal to the value specified for VERSCOMP.

NONE

The existing entry's version number is not updated. The new entry's version number is set to binary zeros.

INC

The existing entry's version number is increased by one. The new entry's version number is set to binary zeros, except for the low-order bit, which is set to one.

DEC

The existing entry's version number is decreased by one. The new entry's version number is set to all binary ones.

SET

Both the existing and the new entry's version number is set to the value specified by NEWVERS.