Error Messages

CAUSE:

ACTION:

CAUSE: An invalid character has been selected when choosing a trace type or a control block index. The APPC subsystem trace formatter reprompts for a valid selection.

ACTION: When selecting a trace type, enter an integer of 1 (internal trace) or 2 (user trace). When selecting a control block index, enter an integer from 0 through 99999.

CAUSE: An invalid trace formatting type has been selected. The APPC subsystem trace formatter reprompts for a valid selection.

ACTION: Select either 1 (internal trace) or 2 (user trace).

CAUSE: The APPC trace formatter failed to write to the $STDLIST file passed to it from NMDUMP.

ACTION: Check that $STDLIST, if redirected when running NMDUMP, is equated properly to an existing MPE file or that the NEW option is specified in the RUN command. See the MPE XL Intrinsics Reference Manual for the exact meaning of the FWRITE error indicated by errornum.

CAUSE: The APPC trace formatter failed to read from the $STDIN file passed to it from NMDUMP.

ACTION: Check that $STDIN, if redirected when running NMDUMP, is equated properly to an existing MPE text file. See the MPE XL Intrinsics Reference Manual for the exact meaning of the FREAD error indicated by errornum.

CAUSE: The APPC subsystem failed to read the specified message in the specified set of NMCAT.PUB.SYS.

ACTION: The intrinsic error number indicates the CATREAD intrinsic return code for failure to read the catalog. See the MPE XL Intrinsics Reference Manual to determine the meaning of the CATREAD failure.

CAUSE: A TCB index bigger than the allowable maximum value has been selected. A TCB index cannot be greater than a five-digit integer. The APPC subsystem trace formatter reprompts for a new value.

ACTION: Select a TCB index from 0 through 99999.

CAUSE: An RCB index bigger than the allowable maximum value has been selected. An RCB index cannot be greater than a five-digit integer. The APPC subsystem trace formatter reprompts for a new value.

ACTION: Select an RCB index from 0 through 99999.

CAUSE: An SCB index bigger than the allowable maximum value has been selected. An SCB index cannot be greater than a five-digit integer. The APPC subsystem trace formatter reprompts for a new value.

ACTION: Select an SCB index from 0 through 99999.

CAUSE: The APPCCONTROL command you typed is missing a necessary parameter.

ACTION: Check the syntax of this command by typing APPCCONTROL HELP or by looking in Chapter 2 “Interactive Control Operator Commands” of this manual.

CAUSE: Incorrect command or parameter specified.

ACTION: Check the syntax of this command by typing APPCCONTROL HELP or by looking in Chapter 2 “Interactive Control Operator Commands” of this manual.

CAUSE: Parameter string exceeded specified length.

ACTION: Check the syntax of this command by typing APPCCONTROL HELP or by looking in Chapter 2 “Interactive Control Operator Commands” of this manual.

CAUSE: An APPCCONTROL command was issued with too many parameters.

ACTION: Check the syntax of this command by typing APPCCONTROL HELP or by looking in Chapter 2 “Interactive Control Operator Commands” of this manual.

CAUSE: Incorrect syntax of command.

ACTION: Check the syntax of this command by typing APPCCONTROL HELP or by looking in Chapter 2 “Interactive Control Operator Commands” of this manual.

CAUSE: A parameter has been used more than once.

ACTION: Retype the command, leaving out the duplicated parameter.

CAUSE: A parameter was specified, but no value was assigned to it, or there was a syntax error in the command line.

ACTION: Retype the command with the assigned value, or check the syntax by typing APPCCONTROL HELP.

CAUSE: Incorrect syntax of command.

ACTION: Check the syntax of this command by typing APPCCONTROL HELP> or by looking in Chapter 2 “Interactive Control Operator Commands” of this manual.

CAUSE: Programmatic interface detected a parameter out of bounds.

ACTION: Call your HP representative.

CAUSE: A user without NM capability issued a command that requires NM capability.

ACTION: Assign NM capability to the user, or log on to another user that has NM capability

CAUSE: Incorrect value assigned to the ERROPT parameter of the APPCCONTROL START command.

ACTION: Retype the command with the correct ERROPT value. If you need help, check the syntax of this command by typing APPCCONTROL HELP, or refer to Chapter 2 “Interactive Control Operator Commands” of this manual.

CAUSE: An invalid value was specified in the TRACEON parameter of the APPCCONTROL START command.

ACTION: Type APPCCONTROL HELP for information about APPCCONTROL commands, or see Chapter 2 “Interactive Control Operator Commands” of this manual.

CAUSE: Incorrect value assigned to the TFILESIZE parameter of the APPCCONTROL START command.

ACTION: Retype the command with a valid TFILESIZE value. If you need help, check the syntax of this command by typing APPCCONTROL HELP, or refer to Chapter 2 “Interactive Control Operator Commands” of this manual.

CAUSE: An incorrect value was specified in the PERFORMANCEON parameter of the APPCCONTROL START command.

ACTION: Specify YES or NO. Check the syntax of this command by typing APPCCONTROL HELP, or see Chapter 2 “Interactive Control Operator Commands” of this manual.

CAUSE: Session type name specified in the STYPE parameter of the APPCCONTROL SESSIONS, APPCCONTROL PERFORMANCE, or APPCCONTROL STATUS command is not configured or is not recognized.

ACTION: Determine which session types are configured by issuing the APPCCONTROL STATUS command. If necessary, shut down the APPC subsystem to update the configuration file.

CAUSE: Session limit specified in the LIMIT parameter of the APPCCONTROL SESSIONS command is greater than the number currently allowed.

ACTION: You could receive this message because you tried to exceed the maximum number of sessions that the APPC subsystem can support, or because you exceeded the number of sessions configured for this session type. Check the number of active sessions and the configured session limit for the session type by issuing the APPCCONTROL STATUS command.

CAUSE: Incorrect value assigned to the TYPE parameter of the APPCCONTROL STOP command.

ACTION: Check the syntax of this command by typing APPCCONTROL HELP or by looking in Chapter 2 “Interactive Control Operator Commands” of this manual.

CAUSE: Type APPCCONTROL VERSION to verify the version mismatch. Call your HP representative.

ACTION: Version mismatch detected between the modules.

CAUSE: A required file has not been installed on the subsystem.

ACTION: Issue the APPCCONTROL VERSION command to determine which software modules are installed on the system, and save the output to a file. Call your HP representative.

CAUSE: APPC subsystem detected NM return code 105 during version checking.

ACTION: Issue the APPCCONTROL VERSION command, and save the output to a file. Call your HP representative.

CAUSE: The APPC subsystem detected an error trying to validate the configuration file during subsystem startup.

ACTION: Run NMMGR and validate the APPC subsystem. Note and correct any errors. If the problem persists, contact your HP representative.

CAUSE: The APPC subsystem is unable to open the NMCONFIG.PUB.SYS file.

ACTION: Restart the APPC subsystem. If the same message is returned, call your HP representative.

CAUSE: The APPC subsystem is unable to close the NMCONFIG.PUB.SYS file.

ACTION: Restart the APPC subsystem. If the problem still exists, call your HP representative.

CAUSE: The APPC subsystem detected an error return code from the NMCONF call of Node Management Services.

ACTION: Check the configuration of the APPC subsystem.

CAUSE: The APPC subsystem is unable to open the catalog file CATAPPC.APPC.SYS.

ACTION: Type LISTF CATAPPC.APPC.SYS to see if the file exists. Call your HP representative.

CAUSE: The APPC subsystem is unable to close the catalog file CATAPPC.APPC.SYS.

ACTION: Type LISTF CATAPPC.APPC.SYS to see if the file exists. Call your HP representative.

CAUSE: The APPC subsystem is unable to open the Node Management Log File.

ACTION: Check the logging class configuration in NMMGR.

CAUSE: The APPC subsystem is unable to close the Node Management Log File.

ACTION: Check the logging class configuration in NMMGR.

CAUSE: The APPC subsystem is unable to create the APPC internal trace file.

ACTION: Restart the APPC subsystem. If the problem still exists, call your HP representative.

CAUSE: The APPC subsystem is unable to close the APPC internal trace file.

ACTION: Restart the APPC subsystem. If the problem still exists, call your HP representative.

CAUSE: A file could not be created to dump the APPC data structures.

ACTION: Verify that there is enough disk space to build the dump file, and then retry the command. If the problem still exists, call your HP representative.

CAUSE: The APPC dump file could not be opened.

ACTION: Verify that the capabilities for the APPC.SYS group and account are correct and that there is enough disk space on the system. Then retry the command. If the problem still exists, call your HP representative.

CAUSE: The APPC subsystem detected an error trying to create the Resource Manager process during subsystem startup.

ACTION: Verify that the program file RM.APPC.SYS exists and that the capabilities and access privileges for the APPC.SYS group and account are correct. If the problem still exists, contact your HP representative.

CAUSE: The APPC subsystem detected an error trying to create the Control Operator TP process during subsystem startup.

ACTION: Verify that the program file COPRTP.APPC.SYS exists and that the capabilities and access privileges for the APPC.SYS group and account are correct. If the problem still exists, contact your HP representative.

CAUSE: The APPC subsystem detected an error trying to create the Change Number of Sessions (CNOS) TP process during subsystem startup.

ACTION: Verify that the program file CNOSTP.APPC.SYS exists and that the capabilities and access privileges for the APPC.SYS group and account are correct. If the problem still exists, contact your HP representative.

CAUSE: The Resource Manager detected an error during subsystem startup.

ACTION: Restart the subsystem. If the error still exists, call your HP representative.

CAUSE: The Control Operator TP detected an error during subsystem startup.

ACTION: Restart the subsystem. If the error still exists, call your HP representative.

CAUSE: The Change Number of Sessions (CNOS) TP detected an error during subsystem startup.

ACTION: Restart the subsystem. If the error still exists, call your HP representative.

CAUSE: The APPC subsystem detected an error while trying to deactivate a session after the APPCCONTROL SESSIONS command was issued or the APPCSessions intrinsic was called.

ACTION: Call your HP representative.

CAUSE: The APPCCONTROL DUMP command did not execute.

ACTION: Retry the command. If the problem still exists, call your HP representative.

CAUSE: The APPC subsystem detected an internal error.

ACTION: Call your HP representative.

CAUSE: The APPC subsystem detected an internal error while trying to shut down the APPC subsystem after the APPCCONTROL STOP command was issued.

ACTION: Call your HP representative.

CAUSE: The COPR TP detected a run-time error.

ACTION: Call your HP representative.

CAUSE: The Control Operator was unable to access the APPC KSO.

ACTION: Call your HP representative.

CAUSE: The Control Operator was unable to open $STDIN to read from the terminal.

ACTION: Call your HP representative.

CAUSE: The Control Operator was unable to open $STDLIST to write output to the terminal.

ACTION: Call your HP representative.

CAUSE: The APPCCONTROL PERFORMANCE command was issued when APPC performance tracing was not active.

ACTION: Issue the APPCCONTROL PERFORMANCEON command to enable the gathering of performance statistics before issuing the APPCCONTROL PERFORMANCE command.

CAUSE: The command issued cannot be executed because the APPC subsystem was not started.

ACTION: If you wish to execute the command, do so after starting up the APPC subsystem with the APPCCONTROL START command.

CAUSE: The command issued cannot be executed because the APPC subsystem is in the progress of starting up.

ACTION: Check the status of the APPC subsystem and reenter your command when the subsystem is active. If problems still exist, call your HP representative.

CAUSE: The APPCCONTROL START command was issued (or the APPCStart intrinsic was called) after the APPC subsystem had already been activated.

ACTION: No action necessary.

CAUSE: An APPCCONTROL START or an APPCCONTROL SESSIONS command was issued after initiation of subsystemn shutdown.

ACTION: Check the status of the subsystem and wait until the subsystem has shut down completely. If the command entered was APPCCONTROL START, re-enter the command. If the command entered was APPCCONTROL SESSIONS, restart the subsystem with APPCCONTROL START, and then reissue the APPCCONTROL SESSIONS command.

CAUSE: The command issued cannot be executed because the requested session type is not in ACTIVE state.

ACTION: Use the APPCCONTROL STATUS command to verify the state of the session type. Use APPCCONTROL SESSIONS to activate the session type if it is in a NO SESS state.