TS/MP 2.5 System Management Manual

1010
*1010* PATHWAY NOT CONFIGURED
Cause. An attempt was made to run a command while the PATHMON process was not in the
RUNNING state. Only the SET PATHMON and SET PATHWAY commands can be run while the
PATHMON process is not running.
Effect. The command fails.
Recovery. Configure the PATHMON environment.
1011
*1011* link manager-name, DELINK FAILURE : < nested-message >
Cause. An error occurred while a TCP or LINKMON process was trying to return a link to a server
class. The nested message indicates the reason for the failure.
Effect. The effect depends on the reason for the failure.
Recovery. For additional information, see the description associated with the nested message.
1012
*1012* object-name, ENTRY ALREADY EXISTS
Cause. Either the PATHMON process tried to add an object having a name that already exists, or
the PATHMON process tried to start a TCP or server process using a process name that is already
active within this PATHMON environment.
This message usually indicates an attempt to use an object name or a process name twice. For
example, if this is a nested message in a CAN’T GRANT LINK error (for more information, see the
description of error 1007), then the process name for a dynamic server already exists in the list
of active server processes and TCPs for the PATHMON process.
Effect. The object is not added, or the TCP or server process is not started.
Recovery. Check the object name or the process name associated with the specified object. Change
the name, as needed.
1013
*1013* object-name, EMPTY ENTRY
Cause. An entry that was supposed to contain the description of an object (for example, a server)
is empty. This is an internal error.
Effect. The operation that needed to use the entry cannot complete.
Recovery. Contact your HP representative and provide all relevant information as follows:
• Descriptions of the problem and accompanying symptoms
• Details from the messages generated
• Your PATHMON configuration file and the PATHMON process version
• A description of the application task that was in progress when the error was encountered
• Supporting documentation such as Event Management Service (EMS) logs, trace files, and
dump files, if applicable
PATHMON Messages 215