Appendix A Status Info

CAUSE: Intrinsic executed successfully.

ACTION: None.

CAUSE: (MPE V only) The address of a parameter is outside of the DL to S stack boundary. (That is, it is either less than DL or greater than S).

ACTION: Verify that the stack data has not been corrupted by overwriting.

Verify that parameters are being passed to the intrinsic as specified in Chapter 7 “Debugging”

CAUSE: (MPE V only) Intrinsic called in split stack mode.

ACTION: Change your program so that it does not call an intrinsic in split stack mode.

CAUSE: (MPE XL only) The address of a parameter is outside the process data area.

ACTION: Verify that the data has not been corrupted.

CAUSE: (MPE XL or V) The value of the Length parameter is greater than the length of the Data array specified in the intrinsic call.

ACTION: Verify that the value of the Length parameter is less than or equal to the length of the Data array.

CAUSE: A ResourceID has been specified that does not correspond to any value returned by the MCAllocate intrinsic for an active conversation.

ACTION: Verify that the value specified in the intrinsic call is the same value returned by the MCAllocate or MCGetAllocate intrinsic for an active conversation.

CAUSE: (MPE V only) The ReturnControl parameter has been set to a value other than 0.

ACTION: Because this parameter is not currently implemented, the value must always be 0. The parameter can be explicitly set to 0 in the intrinsic call, or it can be omitted from the intrinsic call and allowed to default to 0.

CAUSE: (MPE XL only) The ReturnControl parameter has been set to a value other than 0 or 1.

ACTION: The ReturnControl parameter of the MCAllocate intrinsic can be either 0 (IMMEDIATE) or 1 (WHEN_SESSION_ALLOCATED). Check to see that it is set to a valid value.

CAUSE: The value of the Synclevel parameter is not valid.

ACTION: Verify that Synclevel is either 0 or 2.

CAUSE: The length of an individual PIP is out of range.

ACTION: Verify that the length of each PIP is greater than or equal to 0 bytes and less than or equal to 1980 bytes.

CAUSE: The value for the Timer parameter is not within its valid range.

ACTION: Verify that the Timer parameter is a value from 0 through 28800 seconds.

CAUSE: The DeallocateType parameter is not a valid value.

ACTION: Verify that the DeallocateType parameter is 0, 1, 2, 5 or 6.

CAUSE: The DeallocateType parameter is not a valid value.

ACTION: Verify that the DeallocateType parameter is 0, 1, 2, 5 or 6.

CAUSE: The value of the Length parameter is out of its valid range.

ACTION: Verify that the Length parameter is a value from 0 through 4092 bytes (or from 0 through 32763 bytes for the MCRcvAndWait intrinsic on MPE XL).

CAUSE: The value of the Length parameter is greater than the length of the Data array specified in the intrinsic call.

ACTION: Verify that the value of the Length parameter is less than or equal to the length of the Data array.

CAUSE: The Length parameter may be corrupted.

ACTION: Verify that addresses are not being corrupted.

CAUSE: The address of the Data array in the MCRcvAndWait, MCRcvNoWait, MCPostOnRcpt, or MCSendData intrinsic is invalid or corrupted.

ACTION: Verify that the Data array address is not being modified accidentally before it is passed to the intrinsic.

CAUSE: The TPID value specified in the intrinsic call does not correspond to the value returned by the TPStarted intrinsic.

ACTION: Verify that the TPID specified in the intrinsic call contains the value that was returned by TPStarted.

CAUSE: The catalog files for LU 6.2 API do not exist.

ACTION: Verify that the files CATAPI.PUB.SYS and CATAPPC.APPC.SYS exist.

CAUSE: The catalog files for LU 6.2 API have not been released for system use.

ACTION: Verify that the files CATAPI.PUB.SYS and CATAPPC.APPC.SYS have been released for general system use.

CAUSE: GENMESSAGE file is corrupted.

ACTION: Verify that GENMESSAGE file is not corrupted.

CAUSE: The MPE GENMESSAGE intrinsic did not execute properly.

ACTION: Notify your HP representative.

CAUSE: CATREAD file is corrupted.

ACTION: Verify that CATREAD file is not corrupted.

CAUSE: The MPE CATREAD intrinsic did not execute properly.

ACTION: Notify your HP representative.

CAUSE: The APPC subsystem has not been started or is no longer active.

ACTION: Request that the node manager start the APPC subsystem.

CAUSE: The minimum amount of stack space required to call and execute an intrinsic is not available.

ACTION: (MPE V only) Increase the maximum stack size using the Stack parameter of the MPE RUN command. Increase the maximum stack size using the Stack or MaxData parameter of the MPE PREP command. For information on the RUN and PREP commands, refer to the MPE V Command Reference Manual or the online help facility.

ACTION: (MPE XL only) Increase the maximum stack size using the NMStack parameter of the MPE RUN command. Increase the maximum stack size using the NMStack parameter of the MPE LINK command. For information on the RUN and LINK commands, refer to the MPE XL Command Reference Manual or the online help facility.

CAUSE: Not enough space for the TP process to allocate an Available File Table (AFT) entry for the conversation.

ACTION: (MPE V only) Allocate more space for the process using the MPE PREP command (DL=DLsize) or the MPE RUN command (DL=DLsize). For information on the RUN and PREP commands, refer to the MPE V Command Reference Manual or the online help facility.

ACTION: (MPE XL only) Allocate more space for the process using the MPE RUN command (DL=DLsize). For information on the RUN command, refer to the MPE XL Command Reference Manual or the online help facility.

CAUSE: Presentation Services was unable to build the InterProcess Communication (IPC) port.

ACTION: Notify your HP representative.

CAUSE: The SessionType specified in the intrinsic call was not found in the APPC subsystem configuration.

ACTION: Verify that the correct SessionType is specified in the intrinsic call.

Verify that the specified SessionType has been configured in the NMCONFIG file for the APPC subsystem. For information on APPC subsystem configuration, see the LU 6.2 API/V Node Manager's Guide or the APPC Subsystem on MPE XL Node Manager's Guide.

CAUSE: No conversations are available because the maximum number of conversations has been allocated.

ACTION: Run programs at a time when resources are not in heavy demand.

CAUSE: All sessions for the specified session type are busy or unavailable.

ACTION: Have the node manager increase the number of active sessions using the APPCCONTROL SESSIONS command. See the APPC Subsystem on MPE V Node Manager's Guide or the APPC Subsystem on MPE XL Node Manager's Guide for information on APPCCONTROL commands.

Run programs at a time when resources are not in heavy demand.

Request that more sessions be configured for the specified session type. (The maximum number of sessions is 8 on MPE V, or 256 on MPE XL.)

CAUSE: LU 6.2 API was not able to find a request to start a conversation with the local TP.

ACTION: Check the stream file in the APPC.SYS account to make sure that the jobname in the MPE JOB command matches the file name of the stream file.

Make sure that MCGetAllocate is not being called by a locally initiated TP.

CAUSE: The value of the PrepToRcvType parameter is not within its valid range.

ACTION: Verify that the PrepToRcvType value is 0, 1 or 2.

CAUSE: The value of the Locks parameter is not within its valid range.

ACTION: Verify that the Locks value is 0 or 1.

CAUSE: The OldStatus parameter specified in the MCErrMsg intrinsic call is undefined or was corrupted.

ACTION: Verify that the OldStatus value is a valid status info value and that it has not been corrupted.

CAUSE: The configured Time-out value for the remotely initiated transaction program expired before an allocate request arrived from a remote TP.

ACTION: If this message indicates a problem, verify that the remote TP is sending the correct TP name in the allocate request. Verify that the remotely initiated TP is configured correctly through NMMGR. If necessary, raise the configured Time-out value.

CAUSE: A confirmation was requested and the synchronization level for the conversation was not set to CONFIRM.

ACTION: Set the SyncLevel parameter to CONFIRM in the MCAllocate or MCGetAllocate intrinsic if confirmation will be used during this conversation. This status info value can be returned when you call MCConfirm, MCPrepToRcv with PrepToRcvType = CONFIRM, or MCDeallocate with DeallocateType = CONFIRM.

CAUSE: The value of the NumResources parameter is not within its valid range.

ACTION: Verify that the NumResources parameter is a value from 1 through 8 on MPE V, or from 1 through 256 on MPE XL.

CAUSE: The value of the Test parameter is not within its valid range.

ACTION: Verify that the Test value is 0 or 1.

CAUSE: This status info value is returned to the MCTest intrinsic (Test = REQUEST_TO_SEND_RECEIVED) when a RequestToSend has not been received.

ACTION: Informational message. No action necessary.

CAUSE: This status info value is returned to the MCTest (Test = POSTED) or MCWait intrinsic when posting is not active (MCPostOnRcpt has not been called) for the specified mapped conversation.

ACTION: Before calling MCTest or MCWait, verify that the MCPostOnRcpt intrinsic has executed successfully for the specified conversation.

CAUSE: No data or conversation status information has been received for the specified conversation.

ACTION: Informational message. No action necessary.

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.

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.

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.

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.

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.

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.

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.

CAUSE: The APPC subsystem rejected the remote TP's request to start a conversation, because it was invalid.

The APPC subsystem could not receive the PIP data successfully.

ACTION: Have remote programmer verify the parameters used to allocate the conversation.

PIP data length must be specified correctly by the remote TP.

CAUSE: No data or status information was received from the remote TP in the time limit specified in the Timer parameter of the MCAllocate intrinsic.

ACTION: This message is an event indicator. Any required action is program dependent.

CAUSE:

ACTION: Note the circumstances and report them to your HP representative.

CAUSE:

ACTION: Note the circumstances and report them to your HP representative.

CAUSE: Presentation Services was unable to build the InterProcess Communication (IPC) port for the transaction program.

ACTION: Notify your HP representative.

CAUSE: The conversation has been deallocated by the remote TP, without any errors.

ACTION: Deallocate the local TP using the MCDeallocate intrinsic (DeallocateType = LOCAL).

CAUSE: The conversation has been deallocated by the remote TP, without any errors.

ACTION: Note the circumstances and report them to your HP representative.

CAUSE: A required parameter was not included in the call to an LU 6.2 API intrinsic.

ACTION: Verify that all the required parameters are included in the intrinsic call.

CAUSE: The size of the DL to DB area was insufficient for the MCAllocate intrinsic to start a conversation.

ACTION: Increase the maximum stack size using the Stack parameter of the MPE RUN parameter of the MPE PREP command. For information on the RUN and PREP commands, refer to the MPE V Command Reference Manual or the online help facility.

CAUSE: The RemoteTPLen parameter is not within its valid range.

ACTION: Verify that the RemoteTPLen parameter is a value from 1 through 64, indicating the number of characters in the RemoteTPName.

CAUSE: The value of the NumPIPs parameter is not within its valid range.

ACTION: Verify that the NumPIPs parameter is a value from 0 through 16.

CAUSE: 1. The LocalTPName parameter of the MCGetAllocate intrinsic is coded as an output parameter when it should be passed as an input parameter

2. The LocalTPName parameter of the MCGetAllocate intrinsic does not match the LocalTPName parameter of the TPStarted intrinsic.

3. The LocalTPName is not configured as a remotely initiated TP.

ACTION: Verify that the LocalTPName parameter is being passed as an input parameter to the MCGetAllocate intrinsic. Verify that the LocalTPName parameter is the same in both the MCGetAllocate and TPStarted intrinsic calls. Verify that the LocalTPName is configured through NMMGR as a remotely initiated TP.

CAUSE: The combined length of PIP1 through PIP16 is greater than 1980 bytes.

ACTION: Reduce the lengths of the PIPs until their combined length is less than or equal to 1980 bytes.

CAUSE: The remote TP has sent more PIPs than the number specified in the NumPIPs parameter of the MCGetAllocate intrinsic.

ACTION: Consult with the remote programmer to make sure the number of PIPs sent matches the value in the NumPIPs parameter.

CAUSE: The remote TP issued the equivalent of the MCDeallocate intrinsic, specifying the deallocate type ABEND.

ACTION: All buffers have been flushed. If the local TP was in Receive state, data may been lost. After receiving this status info value, the local TP is in Deallocate state and must issue the MCDeallocate intrinsic with DeallocateType = LOCAL.

CAUSE: The TPStarted intrinsic did not execute successfully because the maximum number of concurrently active TPs has been reached.

ACTION: Attempt program execution at a time when resources are not in heavy demand. The maximum number of TPs allowed to be executing at one time is 8 on MPE V, or 256 on MPE XL.

CAUSE: Invalid TraceFile parameter specified in intrinsic call. The disc file name specified in the TraceFile parameter is not a valid name, is not terminated with a blank, or specifies an unknown file name, lockword, group name, or account name.

ACTION: Verify that the disc file name specified in the TraceFile parameter is valid, is terminated with a blank, and specifies a valid file name, lockword, group name, and account name.

CAUSE: If two TP processes try to open the same trace file, the first process will be successful, and the second process will receive this status info value.

ACTION: Verify that different TPs specify different trace file names. If more than one instance of the same TP will be executing at the same time, allow the trace file name to default.

CAUSE: The TraceSize parameter is not within its valid range.

ACTION: Verify that the TraceSize parameter is a value from 1 through 32767.

CAUSE: The value of the TraceOn parameter is not within its valid range.

ACTION: Verify that the TraceOn parameter is a value from 0 through 3.

CAUSE: One or more conversations were not deallocated before the TPEnded intrinsic was called.

ACTION: Verify that the MCDeallocate intrinsic was executed for any active conversations before calling TPEnded.

CAUSE: The program attempted to call the TPStarted intrinsic more than once during program execution.

ACTION: Verify that TPStarted intrinsic is called only once.

CAUSE: The Data parameter specified in the MCRcvAndWait, MCRcvNoWait, or MCPostOnRcpt intrinsic does not match the Data parameter specified in a previous call to MCPostOnRcpt.

ACTION: Verify that the MCRcvAndWait or MCRcvNoWait intrinsic and the MCPostOnRcpt intrinsic are using the same variable in their Data parameters.

CAUSE:

ACTION: Contact your HP representative.