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

Appendix A 153
Status Info
ACTION: Before calling MCTest or MCWait, verify that the
MCPostOnRcpt intrinsic has executed successfully for the specified
conversation.
+38 MESSAGE: Not Posted.
CAUSE: No data or conversation status information has been received
for the specified conversation.
ACTION: Informational message. No action necessary.
-40 MESSAGE: Intrinsic called in invalid state.
CAUSE: The program called an intrinsic from a state in which the
intrinsic is not allowed.
ACTION: Refer to Appendix C , “State Transition Tables,” or Chapter 5 ,
“Intrinsic Descriptions,” to verify that the conversation is in the
appropriate state for this intrinsic call.
-50 MESSAGE: Allocation Error.
CAUSE: Allocation could not be completed. Reasons may include the
following:
CAUSE: The conversation is now in Deallocate state and can be
deallocated.
CAUSE: A conversation type mismatch. The remote LU does not support
mapped conversations, so it rejected an allocation request from the local
TP.
ACTION: Verify that the remote LU supports mapped conversations.
CAUSE: An unrecognized
RemoteTPName . The remote LU rejected the
allocation request from the local TP because the TP name specified in
the
RemoteTPName parameter of the MCAllocate intrinsic was not
recognized.
ACTION: Verify that the RemoteTPName matches the name of the correct
program on the remote system.
Verify that the RemoteTPName has been converted from ASCII to
EBCDIC correctly.
CAUSE: PIP data is not allowed. The remote TP does not support PIP
data.
ACTION: Verify that the remote system accepts PIP data. If it does not,
your program will have to be redesigned.
CAUSE: The remote system will not accept the PIP data as it has been
specified.
ACTION: Verify that the PIP data is in the form that the remote system
can accept.