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


Determining Buffer Storage Ownership

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

XES always assumes that the storage for the data buffers is owned by the home address space (the “requestor's” or “client's” address space) at the time of the IXLLIST request. However, XES also allows the buffers to be owned by the primary address space (the “connector's” or “server's address space”) at the time of the request when the following conditions both exist:
  • The connector's space is not equal to the requestor's home space
  • The connector's space is non-swappable
Thus, the possible address space environments for your application are:
  • Requestor (Home) equals Connector (Primary)
  • Requestor (Home) does not equal Connector (Primary) with buffer storage owned by Connector's address space
  • Requestor (Home) does not equal Connector (Primary) with buffer storage owned by Requestor's address space

In general, the IXLLIST service allows you to designate your data buffer storage using real or virtual storage addresses. However, it is of the utmost importance that XES is aware of the specific location of the data buffer storage and that the location remains so until all data transfer is complete.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014