LU 6.2 API Application Programmer's Reference Guide (30294-90008)

154 AppendixA
Status Info
CAUSE: An unavailable remote TP. The remote LU rejected the
allocation request because the remote TP could not be started.
ACTION: Determine why the remote TP could not be started. Do not try
to restart the TP until the problem has been resolved.
-51 MESSAGE: Resource Failure: No retry possible.
CAUSE: A conversation failure has occurred and the APPC subsystem is
unable to reactivate the conversation.
Possible reasons include the following:
LU 6.2 API detected a violation of mapped conversation protocol.
A session failure has occurred.
The APPC subsystem has been stopped by the node manager.
The partner LU has deallocated the conversation, indicating a protocol
error.
ACTION: Do not attempt the transaction again until the condition has
been identified and corrected.
Verify that the APPC subsystem is active.
Verify that the partner LU is transmitting data that does not violate
the LU 6.2 protocol.
-52 MESSAGE: Resource Failure: Retry possible.
CAUSE: The conversation has been prematurely terminated, probably
due to a session failure because of a power outage or modem failure.
ACTION: The conversation is now in Deallocate state and must be
deallocated. The program may be designed to reallocate the
conversation and continue processing. The TP does not have to be
restarted.
-56 MESSAGE: Program Error: No data truncation has occurred.
CAUSE: The remote TP has discovered an error. It flushed its send
buffer, issued the equivalent of the MCSendError intrinsic, and is now
in Send state. No truncation of received data has occurred at the
mapped conversation protocol boundary.
ACTION: The required action depends on the error recovery procedure
for the local program.
-60 MESSAGE: Program Error: Data may have been purged.
CAUSE: While in Receive or Confirm state, the remote TP discovered an
error and issued the equivalent of the MCSendError intrinsic. Any data
sent to the local TP may have been purged.
ACTION: The required action depends on the error recovery procedure
for the local program.