When a response is saved independently of the message/response entity, it becomes an independent message. The message notify user routine will not be able to use the IXCMSGIX service to access the response data after it has been saved independently of the message/response entity. Note, however, that it is only the response data that becomes unavailable to the message notify user routine. Information about the response, such as the message control information and who sent the response, is still available to the instance of the message notify user routine that saved the response as well as to any new instances of the message notify user routine that might be called at a later time to process the saved message/response entity.

The message token for an individual response (MNPLTRMSGITOKEN) that is passed in the MNPL is invalidated when the response is saved or discarded, or if the XCF Message In service delivers all the message data. The message tokens for all the associated responses are also invalidated if the message/response entity is saved or discarded.

When saving a response independently of the message/response entity, the undelivered portion of the response is saved along with whatever data is needed to create a new MEPL. A saved response can be processed by invoking the IXCMSGC Call Exit service to call a message user routine.