TS/MP 2.5 System Management Manual

2059
*2059* DEFINE PROCEDURE ERROR (DEFINE-errnum)
Cause. An error occurred, identified by the error number, in a procedure call to the DEFINE
procedure library.
Effect. The operation fails.
Recovery. For information concerning the specified DEFINE error, see the Guardian Procedure
Errors and Messages Manual.
2060
*2060* SAVED DEFINE LENGTH EXCEEDS PATHCOM LIMIT
Cause. The size of the DEFINE definition being added to a server class exceeds the PATHMON
process internal limit.
Effect. The DEFINE definition is not added.
Recovery. Correct the size of the DEFINE.
2061
*2061* DEFINE PARSING AND DISPLAY DISABLED
Cause. PATHCOM is not able to parse or display the DEFINE definitions. This error can occur, for
example, if one or more of the required DEFINE procedures, such as DEFINESAVE and
DEFINERESTORE, are not available.
Effect. The DEFINE operation fails.
Recovery. Contact your Global Customer Support Center (GCSC).
Before contacting the GCSC, have the following information available:
• Log files and dump files
• Your PATHMON configuration file and PATHMON process version
• A description of the application task that was in progress when the error was encountered
This information is invaluable for the support staff to be able to understand the problem and help
fix the problem.
2063
*2063* SAVED CONFIGURATION IN PATHCTL FILE IS VALID FOR COOL
START. DO YOU WISH TO OVERWRITE IT?
Cause. The START PATHWAY COLD command (without the ! option) was issued, the PATHCTL
file exists, and the stored configuration is valid.
Effect. The PATHMON environment can be cool started from the existing PATHCTL file.
Recovery. If you choose to continue the command, the current PATHCTL file is overwritten.
PATHCOM Messages 265