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


Information Passed to the Notify Exit

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

When the notify exit gains control, it receives the following information:
  • The lock index for which there is contention
  • The LOCKDATA information you specified when you obtained the lock. This information can help your notify exit decide how to handle the lock contention. For instance, you might be able to determine why you obtained the lock and whether you can release it.
  • Whether the lock is a persistent lock, which is indicated by a LOCKDATA field of zero.
  • The connection ID (CONID) and connection name (CONNAME) associated with the request causing the contention
  • The type of lock request (LOCKOPER=SET or LOCKOPER=NOTHELD) causing the contention.
This information is passed to the notify exit in the notify exit parameter list (NEPL), mapped by the IXLYNEPL macro:
NEPLCONTOKEN
Your connection token.
NEPLCONNAME
Your connection name.
NEPLCONDATA
Connect-time data you specified when you issued the IXLCONN macro to connect to the list structure. The use of this optional field is user defined. One possibility is to store the address and ALET of an area containing information used by your connection.
NEPLLIST
Indicates that the notify exit received control as a result of an IXLLIST request.
NEPLREBUILD
Indicates whether the target list structure was being rebuilt. When a list structure is being rebuilt, there is an interval in which the new structure and the old structure can both be the target of an IXLLIST request.
0
The target list structure was not being rebuilt or, if so, the target list structure was the original structure.
1
The target list structure was being rebuilt, and the target list structure was the new list structure.
NEPLLOCKINDEX
The lock table index for the lock for which there is contention.
NEPLOWNERLOCKDATA
The lock data specified with the LOCKDATA parameter when the lock was obtained
NEPLOWNERPERSISTENTLOCK
The lock was previously a persistent lock and the LOCKDATA field is now set to zero. See Recovering Persistent Locks and Reconnecting with Persistent Locks for more information about persistent locks.
NEPLPENDINGCONID
The connection ID associated with the pending request
NEPLPENDINGREQUESTTYPE
The pending request type
0
The pending request is LOCKOPER=NOTHELD
1
The pending request is LOCKOPER=SET
NEPLPENDINGCONNAME
The connection name of the pending request

See z/OS® MVS™ Data Areas in the z/OS Internet library for a listing of the IXLYNEPL macro.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014