 |
» |
|
|
|
This section lists the intrinsic return codes that may be
returned to a TP by control operator intrinsics. The return codes
are returned in the ReturnCode parameter of the intrinsics. MESSAGE: Successful completion | CAUSE: The intrinsic completed successfully, and there
are no error or warning messages. ACTION: No action necessary. |
MESSAGE: Missing required parameter | CAUSE: A required parameter was omitted from the intrinsic
call. ACTION: See Chapter 3 “Control Operator Intrinsics” of this manual for
the syntax of control operator intrinsics. Check the syntax of the intrinsic
call in your TP. |
MESSAGE: Parameter error | CAUSE: Incorrect command or parameter specified. ACTION: See Chapter 3 “Control Operator Intrinsics” of this manual for
the syntax of control operator intrinsics. Check the syntax of the intrinsic
call in your TP. |
MESSAGE: Parameter string length too
long | CAUSE: Parameter string exceeded specified length. ACTION: See Chapter 3 “Control Operator Intrinsics” of this manual for
the syntax of control operator intrinsics. Check the syntax of the intrinsic
call in your TP. |
MESSAGE: Too many parameters specified | CAUSE: Too many parameters were specified in a control
operator intrinsic call ACTION: See Chapter 3 “Control Operator Intrinsics” of this manual for
the syntax of control operator intrinsics. Check the syntax of the intrinsic
call in your TP. |
MESSAGE: Syntax error | CAUSE: A syntax error was encountered in a control operator
intrinsic call. ACTION: See Chapter 3 “Control Operator Intrinsics” of this manual for
the syntax of control operator intrinsics. Check the syntax of the intrinsic
call in your TP. |
MESSAGE: Redundant parameter | CAUSE: A parameter was used more than once in a control
operator intrinsic call. ACTION: Change the intrinsic call, leaving out the duplicated parameter. |
MESSAGE: Missing parameter after equal
sign | CAUSE: A parameter was specified with no value assigned
to it, or there was a syntax error in the intrinsic call. ACTION: See Chapter 3 “Control Operator Intrinsics” of this manual for
the syntax of control operator intrinsics. Check the syntax of the intrinsic
call in your TP. |
MESSAGE: Missing or invalid delimiter | CAUSE: Incorrect syntax for intrinsic call. ACTION: See Chapter 3 “Control Operator Intrinsics” of this manual for
the syntax of control operator intrinsics. Check the syntax of the intrinsic
call in your TP. |
MESSAGE: Parameter out of bounds | CAUSE: A parameter value outside the allowable range
was specified. ACTION: See Chapter 3 “Control Operator Intrinsics” of this manual for
the syntax of control operator intrinsics. Check the syntax of the intrinsic
call in your TP. |
MESSAGE: User missing NM capability | CAUSE: A user without NM capability called a control
operator intrinsic. ACTION: Control operator intrinsics require NM (Node Manager) capability. |
MESSAGE: Invalid value for Erropt parameter | CAUSE: The Erropt parameter of the APPCStart intrinsic is not a valid value. ACTION: Check the APPCStart intrinsic call and make sure the Erropt parameter is either 1 or 2. See Chapter 3 “Control Operator Intrinsics” |
MESSAGE: Invalid value for TraceOn
parameter | CAUSE: The TraceOn parameter of the APPCStart intrinsic is not a valid value. ACTION: Check the APPCStart intrinsic call and make sure the TraceOn parameter is either 0 or 1. See Chapter 3 “Control Operator Intrinsics” |
MESSAGE: Invalid value for TFileSize
parameter | CAUSE: The TFileSize APPCStart intrinsic is not a valid value. ACTION: Check the APPCStart intrinsic call and make sure the TFileSize parameter is from 0 through 32767. See Chapter 3 “Control Operator Intrinsics” |
MESSAGE: Invalid value for PerformanceOn
parameter | CAUSE: The parameter of the APPCStart intrinsic is not a valid value. ACTION: Check the APPCStart intrinsic call and make sure the PerformanceOn parameter is either 0 or 1. See Chapter 3 “Control Operator Intrinsics” |
MESSAGE: Invalid SessionTypeName parm
value | CAUSE: Session type name specified in the SessionType parameter of the APPCSessions intrinsic 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. |
MESSAGE: Invalid SessionLimit parm
value | CAUSE: Session limit specified in the NewLimit parameter of the APPCSessions intrinsic 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 maximum 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. |
MESSAGE: Invalid StopType parm value | CAUSE: The StopType parameter of the APPCStop intrinsic is not a valid value. ACTION: Check the APPCStop intrinsic call and make sure the StopType parameter is 1, 2, or 3. See Chapter 3 “Control Operator Intrinsics” |
MESSAGE: APPC module versions mismatch | CAUSE: Version mismatch detected between the modules. ACTION: Type APPCCONTROL VERSION to verify the mismatch. Call your HP representative. |
MESSAGE: Missing required module | 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. |
MESSAGE: Invalid module ID in version
check | CAUSE: The APPC subsystem detected NM return code 105
during version checking. ACTION: Issue the APPCCONTROL VERSION command and save the output to a file. Contact your HP
representative. |
MESSAGE: Invalid APPC configuration | CAUSE: The APPC subsystem detected an error trying to
validate the configuration file during subsystem startup. ACTION: Check the configuration of the APPC subsystem.
If the problem persists, contact your HP representative. |
MESSAGE: Unable to open NMCONFIG file | 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. |
MESSAGE: Unable to close NMCONFIG file | CAUSE: The APPC subsystem is unable to close the NMCONFIG.PUB.SYS file. ACTION: Restart the APPC subsystem. If the same message
is returned, call your HP representative. |
MESSAGE: Configuration error | 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. |
MESSAGE: Unable to open CATAPPC.APPC.SYS | 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. |
MESSAGE: Unable to close CATAPPC.APPC.SYS | 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. |
MESSAGE: Unable to open NM log file | CAUSE: The APPC subsystem is unable to open the Node
Management Log File. ACTION: Check the logging class configuration in NMMGR. |
MESSAGE: Unable to close NM log file | CAUSE: The APPC subsystem is unable to close the Node
Management Log File. ACTION: Check the logging class configuration in NMMGR. |
MESSAGE: Unable to open internal trace
file | CAUSE: The APPC subsystem is unable to create the internal
trace file. ACTION: Restart the APPC subsystem. If the problem still
exists, call your HP representative. |
MESSAGE: Unable to close internal trace
file | CAUSE: The APPC subsystem is unable to close the internal
trace file. ACTION: Restart the APPC subsystem. If the problem still
exists, call your HP representative. |
MESSAGE: Unable to create Resource
Manager at subsystem start-up | CAUSE: Internal error in APPC subsystem. ACTION: Contact your HP representative. |
MESSAGE: Unable to create control operator
TP at subsystem start-up | CAUSE: Internal error in APPC subsystem. ACTION: Contact your HP representative. |
MESSAGE: Unable to create CNOS TP at
subsystem start-up | CAUSE: Internal error in APPC subsystem. ACTION: Contact your HP representative. |
MESSAGE: Resource Manager detected
error during subsystem start-up | CAUSE: Internal error in APPC subsystem. ACTION: Contact your HP representative. |
MESSAGE: COPR TP detected error during
subsystem start-up | CAUSE: Internal error in APPC subsystem. ACTION: Contact your HP representative. |
MESSAGE: CNOS TP detected error during
subsystem start-up | CAUSE: Internal error in APPC subsystem. ACTION: Contact your HP representative. |
MESSAGE: Resource Manager error — CHANGE_SESSIONS_FAILED | CAUSE: The APPC subsystem detected an internal error. ACTION: Call your HP representative. |
MESSAGE: Resource Manager error — subsystem
shutdown failed | CAUSE: Internal error in APPC subsystem. ACTION: Call your HP representative. |
MESSAGE: Control operator internal
error | CAUSE: Internal error in APPC subsystem. ACTION: No action required. |
MESSAGE: APPC object access error | CAUSE: The Control Operator TP was unable to access the
APPC KSO. ACTION: Call your HP representative. |
MESSAGE: APPC subsystem not active | CAUSE: The intrinsic called cannot be executed because
the APPC subsystem was not started. ACTION: Start the APPC subsystem with the APPCCONTROL START command before running your program, or code your program
to call the APPCStart intrinsic before calling any other APPC intrinsics. |
MESSAGE: APPC subsystem pending active | CAUSE: The intrinsic called cannot be executed because
the APPC subsystem startup is in progress. ACTION: Check the status of the APPC subsystem and restart
your program when the subsystem is active. If problems still exist,
call your HP representative. |
MESSAGE: APPC subsystem already active | CAUSE: The APPCStart intrinsic was called after the APPC subsystem had
already been activated. ACTION: No action necessary. |
MESSAGE: APPC subsystem shutting down | CAUSE: A control operator intrinsic was called after
initiation of subsystem shutdown. ACTION: Check the status of the subsystem and wait until
the subsystem has completed shutdown. Then, restart your program. |
MESSAGE: Session limit exceeded | CAUSE: The session limit for the APPC subsystem was reached
before the end of the configuration file. Remaining session types
are initialized in the APPC object with a session limit of 0. ACTION: No action is necessary if you don't use
the session types that are not initialized. Use the APPCCONTROL SESSIONS command or the APPCSessions intrinsic to reapportion sessions among the session types.
If necessary, shut down the APPC subsystem and update the configuration
file. |
MESSAGE: CATREAD failed | CAUSE: A non-zero result code was returned from a call
to CATREAD. ACTION: Restart the APPC subsystem. If the problem still
exists, contact your HP representative. |
|
