Download Print this page

HP 9000 Manual page 77

Dtc device file access utilities and telnet port identification
Hide thumbs Also See for 9000:

Advertisement

(217) ERROR: Unable to obtain binary negotiation from network:
system error <system_error>: <system_message>
CAUSE: There was no binary negotiation to receive from the network due to the
system error given.
NOTE: This message is followed by message (296), (297), and (299).
ACTION: Determine if the terminal server and device are operational and restart the
application if they are.
(218) ERROR: No binary negotiation to obtain from network within time interval allowed
CAUSE: There was no data and thus no binary negotiation to receive from the
network during the time to wait for such negotiations (most likely
because of the load on the terminal server, network, or system).
NOTE: This message is followed by message (296), (297), and (299).
ACTION: Determine if the terminal server and device are operational and restart
the application if they are.
(219) ERROR: Binary negotiation not completed on time
CAUSE: There was no binary negotiation in the data received from the remote
terminal server.
NOTE: This message is followed by message (296), (297), and (299).
(220) ERROR: Received SIGUSR2 signal
(221) ERROR: Give up trying to obtain connection at request of user
CAUSE: Ocd or ocdebug received a SIGUSR2 signal and any more tries to open
a connection to the device on the remote terminal server were stopped.
ACTION: Determine if the terminal server and device are operational and
restart the application if they are.
Appendix B: ocd Logging Messages
B-11

Advertisement

loading