Cross-memory considerations when the RPL is not posted complete

This section documents special responsibilities for the application running in cross-memory mode.

An application executing in its home address space, or HASN, terminates and a request is pending under its primary ASID.
VTAM® drives LOSTERM exit with RPL. The application is responsible for doing incomplete RPL processing of CSM.
If the application is executing in the initiator-attached task and that task terminates, CSM memory termination or jobstep TCB RTM locates and releases any CSM owned by the terminating application.
Subtask of initiator-attached task in Primary ASID abends.
If the application requires unprocessed CSM storage in pending RPLs to be automatically freed, the application must task associate the CSM as follows:
- For TCB mode RPL requests on a send macroinstruction, use CSM services to ensure that CSM is associated with the ACB task.
- For TCB mode RPL requests on a receive macroinstruction, specify to VTAM the application task that is the ACB task so that VTAM can ensure that CSM is associated with that task.
- For SRB mode RPL requests, associate CSM storage to the same TCB that the SRB is associated with.
If the application does not require unprocessed CSM storage in pending RPLs to be automatically freed, task association is not used. RPLs could be active until the abending task has completed task termination. The application must wait for the RPL request to quiesce. Therefore, the application must locate and process incomplete RPLs at the attaching task level after task term completes.