TSMWatch messages

During normal operations, the probe generates ProbeWatch messages and sends them to the ObjectServer. These messages tell the ObjectServer how the probe is running.

The following table describes the raw TSMWatch error messages that the probe generates. For information about generic TSMWatch messages, see the IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide, (SC14-7530).

Table 1. TSMWatch messages
ProbeWatch message	Description	Triggers/causes
`Connection attempted`	The TSM is trying to establish a connection to the host.	The TSM is trying to establish a connection to the host.
`Connection failed`	The TSM has failed to establish a connection to the host.	The TSM has failed to establish a connection to the host.
`Connection Going Down`	The TSM is disconnecting from the host.	Either the TSM has received a bounce command from the command port, or the TSM is having problems reading from the socket.
`Connection lost`	The TSM has lost the connection to the host.	The device has dropped the connection to the TSM.
`Connection succeeded`	The TSM has successfully established a connection to the host.	The TSM has successfully established a connection to the host.
`Deleted inactive device device_name`	The TSM has deleted an inactive device.	The TSM received a response that ends with a prompt (>) after sending out the deldevice command to delete inactive devices.
`Disconnection Attempted`	The TSM is trying to disconnect from the host.	The TSM is shutting down or has lost the connection.
`Disconnection Failed`	The TSM has failed to disconnect cleanly from the host.	There has been a corruption of the memory location storing the connection details.
`Disconnection Successful`	The TSM has disconnected from the host.	The TSM is shutting down or has lost the connection.
`Event Flushed`	Events have been flushed to the ObjectServer from the TSM's buffer.	After a valid HeaderLine or Warning line has been received but before the terminator line has been received, a time interval exceeding that defined in FlushTime property has passed without anything having been read.
`Failed to change password`	Under automatic login, the TSM is unable to change the password to the alternative password.	The TSM's attempt to change the password used for logging in has been rejected by the host.
`Failed to delete inactive devices - logging out`	The TSM is unable to delete inactive devices.	There are too many log devices in use but none of the devices is inactive and therefore cannot be deleted.
`Failed to issue the addclass command - logging out`	The TSM is unable to execute the addclass command.	The TSM received an Invalid parameters response to the addclass command.
`Failed to issue the addrep command - logging out`	The TSM is unable to execute the addrep command.	The TSM received a `Log <log report> not found` response to the addrep command.
`Failed to issue the deldevice command - logging out`	The TSM is unable to execute the deldevice command.	Either the TSM received a response other than .`nknown.` or .`*>` after sending this command, or it timed out while waiting for a response.
`Failed to issue the deldevice command`	The TSM is unable to execute the deldevice command when attempting to remove inactive devices.	Either the TSM received a response other than .`nknown.` or .`*>` after sending this command, or it timed out while waiting for a response.
`Failed to issue the delrep command - logging out`	The TSM is unable to execute the delrep command.	The TSM received a `Log <log report> not found` response to the delrep command.
`Failed to issue the listdevs command - logging out`	The TSM is unable to execute the listdevs command.	Either the TSM received a response other than `known.` or .`Rerouted.` after sending this command, or it timed out while waiting for a response.
`Failed to issue the logutil command - logging out`	The TSM is unable to execute the logutil command.	Either the TSM received a response other than `Unknown.` or .`LOGUTIL.*` after sending this command, or it timed out while waiting for a response.
`Failed to issue the start command - logging out`	The TSM is unable to execute the start command.	Either the TSM received a response other than `Unknown.` or .`o many log devices in u.` or .`break.*` after sending this command, or it timed out while waiting for a response.
`Failed to issue the stop command - logging out`	The TSM is unable to execute the stop command.	Either the TSM received a response other than `Unknown.` or .`his device.` or .`TELNSVR.*` after sending this command, or it timed out while waiting for a response.
`Failed to retrieve device ID after stop command attempt - logging out`	The TSM is unable to extract the device ID from the response received after sending out the stop command.	Either the device ID in the response does not start with TELNSVR or the response does not contain the device ID.
`Going Down`	The TSM is shutting down.	The TSM is shutting down after performing the shutdown routine.
`Heartbeat response received`	A heartbeat response has been received within the period specified by the HeartbeatTimeout property.	A response matching the HeartbeatResponse property in the properties or hosts file has been received.
`Heartbeat response timed out`	A response to the heartbeat string has not been received for the period specified by the HeartbeatTimeout property.	The TSM has not received the expected response or an event and is disconnecting from and reconnecting to the host.
`Heartbeat sent`	A heartbeat string has been sent from the TSM to the host.	The TSM has not received an event from the device for the period specified by HeartbeatInterval.
`Invalid User ID or password.`	Under automatic login, the TSM is unable to log in to the host.	There was a problem logging in; for example, the login properties (UserName, `Password` and `AltPassword`) are not specified correctly.
`Login attempted`	The TSM is trying to log in to the host.	The TSM is trying to log in to the host.
`Login failed`	The TSM has failed to log in to the host.	The TSM has encountered a problem while logging in. Check that the ChatinString property is specified correctly.
`Login succeeded`	The TSM has logged in to the host.	The TSM has logged in to the host.
`Logout attempted`	The TSM is trying to log out from the host.	The TSM has received a command to shut down or has received the bounce command from the command port.
`Logout failed`	The TSM has failed to log out from the host.	The TSM has encountered a problem while logging out. Check that the ChatoutString property is specified correctly.
`Logout succeeded`	The TSM has logged out from the host.	The TSM has logged out from the host.
`Running`	The TSM is running normally.	The TSM has just been started.
`Switch is being rebooted`	The DMS switch is being rebooted.	The TSM received an SOS response during login.
`Temporary password may be in use`	Under automatic login, the TSM is attempting to log in to the host using `AltPassword`. T	he TSM was unable to log in using the password specified in `Password`.
`Too many log devices in use: deleting inactive devices`	The TSM is trying to delete inactive TELNSVR devices.	The TSM received a Too many log devices in use response to the start command that was sent.
`Unable to get events`	A problem occurred while receiving events.	There was a problem initializing the connection due to insufficient memory.
`Unable to save process ID to file pid_file`	The TSM is unable to save its process ID into the file.	General problem saving the PID file; for example, the TSM does not have the permission to save the file.
`User does not have permission to use the command command`	The TSM is unable to execute the command specified (this will be either logutil, listdev, start, addclass, deldevice, or stop).	The TSM received an Unknown response to the command that was sent.
`User logged in on another device`	The username and password combination used by the TSM is already in use in the DMS switch.	The username and password combination used by the TSM is already in use in the DMS switch.