Code | Meaning | Action |
|
|
|
DS04(0) – ILLEGAL NODAL | NRV at node reporting error | Possible solutions are: (1) Shut |
ADDRESS, NODE ADDRESS | does not contain an entry for the | down, edit the answer file, and |
NOT IN NODAL ROUTING | destination node. Possible | reinitialize; (2) Use DSMOD at |
VECTOR (NRV) TABLE | causes: (1) If local processing | each node to display the NRVs, |
| request, NRV did not contain an | and compare this to your |
| entry for local node; (2) NRV | network topology. Correct the |
| built improperly either at local | NSINIT initialization files (nodal |
| node or intervening node; (3) | addresses) and reinitialize |
| Remote file is open or a slave | (bring to quiescent state, shut |
| program is scheduled without | down, and restart or reboot) all |
| proper initialization; (4) | nodes that had incorrect NRVs; |
| Programming error. | (3) Call DOPEN or POPEN and |
|
| open the file; (4) Correct the |
|
| node number. |
|
|
|
DS04(1) – ALL ROUTES TO | The rerouting software has | It may be possible to restore |
THIS NODE ARE DOWN | determined that all routes to the | links with the /L command and |
(REROUTING) | destination node are down and | change the NRV with the CN |
| the message cannot be | command of DSMOD. DVA66 |
| transmitted. (Note that if 12665 | links are automatically enabled |
| (DVA65) links are included in the | when the link problem is |
| network they are not | corrected or goes away. This |
| automatically restored to | error can occur when the links |
| service.) | at a storeandforward node are |
|
| down, not necessarily just links |
|
| at the local node. The reporting |
|
| node number can be used to |
|
| determine how far into the |
|
| network the message traveled. |
|
|
|
DS04(2) – HOP COUNT | Message has exceeded the | This may indicate that the NRV |
EXCEEDED | maximum number of | at this node or other nodes is |
| storeandforwards specified at | specified incorrectly. Check |
| NSARPA/1000 initialization time | NRVs and use DSMOD CN or /T |
| (or as modified by the DSMOD | to correct this error. |
| /T command). |
|
|
|
|
DS05(0) – REQUEST | (#MAST) This error can occur | Retry on a DS05 error is not |
TIMEOUT | for a number of reasons: (1) A | always a good practice for the |
| slave monitor may be •tied up" | following two reasons: (1) The |
| for too long and there is no | request may have been correctly |
| message accounting in the | delivered to the destination node |
| system (message accounting | and have been executed, but |
| will cause a DS05(1)); (2) The | the destination node may have a |
| master timeout may be too small | problem in sending back the |
| or the destination node may be | reply or the reply just takes too |
| loaded heavily or generated | long to reach the origin node. |
| improperly; (3) The reply could | (2) A DS05(0) error can occur if |
| not be sent back due to an | Message Accounting does not |
| irrecoverable transmission error | exist at this node. Another |
| in the reply; (4) The response | solution to avoid DS05(0) error |
| may fail to be returned due to an | may be to increase the master |
| error in the NRV in some node | timeout value. |
| involved in the reply path. |
|
|
|
|
34 Alphanumeric Error Messages