z/OS MVS Programming: Sysplex Services Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Passing the List of Entries to be Moved

z/OS MVS Programming: Sysplex Services Guide
SA23-1400-00

An array of elements in the BUFFER or BUFLIST storage areas contains the information about the list entries to be moved. Each array element identifies the entry to be moved and may also designate version number comparison and key assignment information. The array elements are mapped by the IXLYMELI macro and are indexed with the first element starting at offset zero in the BUFFER or BUFLIST area. Identify the index of the first element to be processed with FIRSTELEM and the index of the last element with LASTELEM.

IXLYMELI, Move Entrylist Input, contains three mappings:
  • Each element in the array is mapped by MELI1 when:
    • The structure does not support keyed entries and VERSCOMPARE=YES or NO is specified.
    • The structure does support keyed entries and entry keys and secondary keys are not to be updated (MOVETOKEY=UNCHANGED), (MOVETOSKEY=UNCHANGED) with VERSIONCOMPARE=NO, or VERSIONCOMPARE=YES is specified.
    • The structure does not support keyed entries and entry keys are to be updated with the list key value (MOVETOKEY=LISTKEY), MOVETOSKEY=UNCHANGED with VERSIONCOMPARE=NO, or VERSIONCOMPARE=YES is specified.
  • Each element in the array is mapped by MELI2 when VERSCOMPARE=BYENTRY or entry key update (MOVETOKEY=TARGETKEY) is specified with MOVETOSKEY=UNCHANGED (secondary key not changed).
  • Each element in the array is mapped by MELI3 when the secondary key is to be updated (MOVETOSKEY=TARGETKEY is specified).

Each IXLYMELI element also contains the target list to which the list entry is to be moved, the direction in which the entry is to be positioned on the list or sublist, and whether the list limit set for the target list should be enforced or ignored.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014