Timeout Error Messages

Recall that a timeout for Node Manager commands can be configured in the Node Manager software runstring using the NMtimeout parameter (default is 5 seconds). If a command is entered and accepted, but for some reason the NMGR module does not respond to the NM module within the designated timeout period, the NM module will return the following error message:

NM> RC,08-00-09-00-02-0B,2<RETURN>

 

Read

802.3

Link Config from node

08-00-09-00-02-0B... [failed]

-- >

times

out - no response from target node

NM>

Typical causes of command timeouts include:

Dtransmission to an unknown Station Address,

Dexcessive NMGR module loading, or

Dexcessive network traffic.

Command Execution

Command execution errors are returned by the NMGR module. They can result even though command entries were accepted and passed by the User Interface modules. An example of a command execution error message returned to the user is shown below:

NM>

SC,08-00-09-00-02-5A,3<RETURN>

 

Set

802.3

Link Config on node

08-00-09-00-02-5A.... [failed]

ERROR: NM003

REPORTING NODE ADR:08000900025A SAP: F8

Parameter

not

supported

 

NM>

Note the error contains an •error code", and the Station Address and program SAP of the node from which the error is generated.

The error codes are described in Chapter 4 (see •NMGR Module"), and provided in Appendix A. These codes consist of two letters reflecting the type of error, followed by three hexadecimal digits that specify the particular error (see Appendix A). In the example above, NM003 indicates a Node Manager error resulting from an unsupported parameter specified in the command. The unsupported parameter, in this case, is the •3" immediately before the <RETURN> key.

From the same example above, the Station Address of the node reporting the error is 08000900025A hexadecimal. The program at that node reporting the failure has its class number posted to SAP F8 (hex).

5%6 Using Node Manager