Difference between revisions of "NCP DECnet/VAX V1.3"
From Computer History Wiki
(First Draft) |
|||
| Line 1: | Line 1: | ||
'''A VERY ROUGH DRAFT!''' | '''A VERY ROUGH DRAFT!''' | ||
| − | ==Remarks== | + | == What is NCP?== |
| + | Citation from "DECnet-VAX, Version 1.3 Software Product Description": | ||
| + | |||
| + | ''Network Control Program'' | ||
| + | |||
| + | ''The Network Control Program (NCP) performs three primary functions: displaying statistics, controlling network components, and testing network components.'' | ||
| + | |||
| + | ''Using the DECnet-VAX NCP utility, an operator can display the status of DECnet activity at the local node.'' | ||
| + | ''The user can choose to display statistics related to the local node, other DECnet-VAX nodes, and communication lines, including information on traffic and errors.'' | ||
| + | ''Using the DECnet-VAX NCP utility, the local operator can also perform many network control functions such as reconfiguring the local node’s network parameters, starting and stopping lines, activating the local node, and down-line loading DECnet-11S systems.'' | ||
| + | |||
| + | ''NCP allows the user to perform a series of tests that aid in isolating problems. NCP can be used to send and receive test messages over individual lines either between nodes or through other controlled loopback arrangements. The messages can then be compared.'' | ||
| + | |||
| + | ==NCP Remarks== | ||
| + | * '''NCP''' is started with: | ||
| + | ** '''MC NCP''' (the oldfashioned RSX-11-way), or: | ||
| + | ** '''RUN SYS$SYSTEM:NCP''' (the VMS-way) | ||
| + | * You can either: | ||
| + | ** enter complete NCP commands, or: | ||
| + | ** start with only the beginning of an NCP command and after pressing '''[Enter]''' NCP will show you how you can continue | ||
* '''LOCAL''' is what '''EXECUTOR''' is in newer NCP versions | * '''LOCAL''' is what '''EXECUTOR''' is in newer NCP versions | ||
* '''KNOWN''' means "all" (kind of a wildcard) | * '''KNOWN''' means "all" (kind of a wildcard) | ||
| − | * Use '''[ESC]''' to abort commands | + | * Use '''[ESC]''' to abort NCP commands |
==NCP "Elements"== | ==NCP "Elements"== | ||
| + | |||
| + | ===NODE=== | ||
| + | ---- | ||
| + | A '''NODE''' is a computer participating in a [[DECnet]] network. | ||
| + | |||
| + | NODEs have got DECnet numbers (= DECnet adresses) in the range 1 to 31 ([[DECnet#Phase II (1976)|DECnet Phase II]]). | ||
| + | |||
| + | NODEs have got names up to 6 characters long. | ||
===LOCAL=== | ===LOCAL=== | ||
| + | ---- | ||
| + | '''LOCAL''' is the DECnet NODE where '''NCP''' is executed. | ||
| + | |||
| + | ===REMOTE=== | ||
| + | ---- | ||
| + | '''REMOTE''' are other DECnet NODEs connected via DECnet. | ||
===LINE=== | ===LINE=== | ||
| + | ---- | ||
| + | A '''LINE''' is the physical connection between two DECnet NODEs. | ||
| − | + | A NODE can have more than one LINE (restrictions apply). | |
| − | + | A LINE is named after the interface on the local end; i.e. '''DMC11_0''' is the line of the first [[DMC11]] on the local node, '''DMC11_1''' is the second, and so on. | |
===LINK=== | ===LINK=== | ||
| + | ---- | ||
| + | A '''LINK''' is an active data connection over a LINE. | ||
| + | |||
| + | A LINK has got a unique number. | ||
| + | |||
| + | A LINE can carry serveral LINKs at a time in parallel (restrictions apply). | ||
===COUNT=== | ===COUNT=== | ||
| + | ---- | ||
| + | '''COUNT''' is a collection of statistical numbers, e.g. for LOCAL, a LINE, or a LINK. | ||
| + | |||
| + | ===OBJECT=== | ||
| + | ---- | ||
| + | An '''OBJECT''' is a program that works on behalf of a DECnet function. | ||
| + | |||
| + | OBJECTs have got names up to 8 characters long and a unique number. | ||
| + | |||
==NCP Command Syntax== | ==NCP Command Syntax== | ||
| Line 36: | Line 86: | ||
DEVICE_LOOPBACK | DEVICE_LOOPBACK | ||
<TEMPORARY REMOTE NAME TO USE FOR LOOPBACK(6 CHARS):> | <TEMPORARY REMOTE NAME TO USE FOR LOOPBACK(6 CHARS):> | ||
| + | </PRE> | ||
| + | <PRE> | ||
ZERO | ZERO | ||
LOCAL (complete) | LOCAL (complete) | ||
| Line 42: | Line 94: | ||
<LINE IDENTIFIER(DEV_#_#_# OR "STRING")> (complete) | <LINE IDENTIFIER(DEV_#_#_# OR "STRING")> (complete) | ||
KNOWN LINES (complete) | KNOWN LINES (complete) | ||
| + | </PRE> | ||
| + | <PRE> | ||
LOAD | LOAD | ||
<REMOTE NODE NAME(1-6 CHARS):> | <REMOTE NODE NAME(1-6 CHARS):> | ||
| + | </PRE> | ||
| + | <PRE> | ||
PURGE | PURGE | ||
LOCAL | LOCAL | ||
| Line 52: | Line 108: | ||
LINE | LINE | ||
KNOWN | KNOWN | ||
| + | </PRE> | ||
| + | <PRE> | ||
LIST | LIST | ||
LOCAL (complete) | LOCAL (complete) | ||
| Line 65: | Line 123: | ||
REMOTES (complete) | REMOTES (complete) | ||
OBJECTS (complete) | OBJECTS (complete) | ||
| + | </PRE> | ||
| + | <PRE> | ||
DEFINE | DEFINE | ||
LOCAL | LOCAL | ||
| Line 75: | Line 135: | ||
LINE | LINE | ||
<LINE NAME(1-16 CHARS):> | <LINE NAME(1-16 CHARS):> | ||
| + | </PRE> | ||
| + | <PRE> | ||
DISCONNECT | DISCONNECT | ||
<LOGICAL LINK NUMBER:> | <LOGICAL LINK NUMBER:> | ||
| + | </PRE> | ||
| + | <PRE> | ||
LOOP | LOOP | ||
REMOTE | REMOTE | ||
| Line 88: | Line 152: | ||
MIXED | MIXED | ||
<LENGTH IN BYTES OF BLOCK BEING LOOPED(1-255):> | <LENGTH IN BYTES OF BLOCK BEING LOOPED(1-255):> | ||
| + | </PRE> | ||
| + | <PRE> | ||
SHOW | SHOW | ||
LINKS (complete) | LINKS (complete) | ||
| Line 101: | Line 167: | ||
<LINE IDENTIFIER(DEV_#_#_# OR "STRING")> (complete) | <LINE IDENTIFIER(DEV_#_#_# OR "STRING")> (complete) | ||
KNOWN LINES (complete) | KNOWN LINES (complete) | ||
| + | </PRE> | ||
| + | <PRE> | ||
MODIFY | MODIFY | ||
LOCAL | LOCAL | ||
| Line 145: | Line 213: | ||
REMOTE | REMOTE | ||
TIMEOUT | TIMEOUT | ||
| + | </PRE> | ||
| + | <PRE> | ||
EXIT (complete) | EXIT (complete) | ||
</PRE> | </PRE> | ||
===NCP Command Examples=== | ===NCP Command Examples=== | ||
| + | The examples are taken on a NODE with two DMC11 interfaces. | ||
| + | |||
====SHOW==== | ====SHOW==== | ||
<PRE> | <PRE> | ||
| Line 156: | Line 228: | ||
NODE=VAX1 | NODE=VAX1 | ||
376/0002002A 375/00050029 | 376/0002002A 375/00050029 | ||
| + | </PRE> | ||
| + | <PRE> | ||
NCP>SHOW COUNTS LOCAL | NCP>SHOW COUNTS LOCAL | ||
COUNTS OF LOCAL, AS OF 7-DEC-1980 13:30:46.24 | COUNTS OF LOCAL, AS OF 7-DEC-1980 13:30:46.24 | ||
| Line 176: | Line 250: | ||
CONNECTS INITIATED 3 | CONNECTS INITIATED 3 | ||
CONNECTS RECEIVED 3 | CONNECTS RECEIVED 3 | ||
| + | </PRE> | ||
| + | <PRE> | ||
NCP>SHOW COUNT LINE DMC11_1 | NCP>SHOW COUNT LINE DMC11_1 | ||
COUNTS OF LINE, AS OF 7-DEC-1980 13:32:34.27 | COUNTS OF LINE, AS OF 7-DEC-1980 13:32:34.27 | ||
| Line 190: | Line 266: | ||
BLOCKS RECEIVED 0 | BLOCKS RECEIVED 0 | ||
BLOCKS SENT 1 | BLOCKS SENT 1 | ||
| + | </PRE> | ||
| + | <PRE> | ||
NCP>SHOW COUNT KNOWN LINES | NCP>SHOW COUNT KNOWN LINES | ||
COUNTS OF KNOWN LINES, AS OF 7-DEC-1980 13:33:49.49 | COUNTS OF KNOWN LINES, AS OF 7-DEC-1980 13:33:49.49 | ||
| Line 214: | Line 292: | ||
BLOCKS RECEIVED 0 | BLOCKS RECEIVED 0 | ||
BLOCKS SENT 1 | BLOCKS SENT 1 | ||
| + | </PRE> | ||
| + | <PRE> | ||
NCP>SHOW STATUS LOCAL | NCP>SHOW STATUS LOCAL | ||
STATUS OF LOCAL, AS OF 7-DEC-1980 13:35:35.82 | STATUS OF LOCAL, AS OF 7-DEC-1980 13:35:35.82 | ||
| Line 222: | Line 302: | ||
STATE=ON | STATE=ON | ||
DEFAULT HOST=VAX1 | DEFAULT HOST=VAX1 | ||
| + | </PRE> | ||
| + | <PRE> | ||
NCP>SHOW STATUS LINE DMC11_1 | NCP>SHOW STATUS LINE DMC11_1 | ||
STATUS OF LINE, AS OF 7-DEC-1980 13:36:33.95 | STATUS OF LINE, AS OF 7-DEC-1980 13:36:33.95 | ||
| Line 228: | Line 310: | ||
LINE-ID STATE REMOTE | LINE-ID STATE REMOTE | ||
DMC11_1 OFF VAX3 | DMC11_1 OFF VAX3 | ||
| + | </PRE> | ||
| + | <PRE> | ||
NCP>SHOW STATUS KNOWN LINES | NCP>SHOW STATUS KNOWN LINES | ||
STATUS OF KNOWN LINES, AS OF 7-DEC-1980 13:37:51.22 | STATUS OF KNOWN LINES, AS OF 7-DEC-1980 13:37:51.22 | ||
| Line 245: | Line 329: | ||
MAXIMUM NUMBER OF LOGICAL LINKS: 128 | MAXIMUM NUMBER OF LOGICAL LINKS: 128 | ||
MAXIMUM NUMBER OF REMOTE NODES: 10 | MAXIMUM NUMBER OF REMOTE NODES: 10 | ||
| + | </PRE> | ||
| + | <PRE> | ||
NCP>LIST REMOTE VAX2 | NCP>LIST REMOTE VAX2 | ||
CONFIGURATION DATABASE NODE VAX2 | CONFIGURATION DATABASE NODE VAX2 | ||
| Line 263: | Line 349: | ||
SERVERS LINE TO REMOTE: | SERVERS LINE TO REMOTE: | ||
REMOTES HOST NODE: | REMOTES HOST NODE: | ||
| + | </PRE> | ||
| + | <PRE> | ||
NCP>LIST KNOWN OBJECTS | NCP>LIST KNOWN OBJECTS | ||
CONFIGURATION DATABASE OBJECT NICE | CONFIGURATION DATABASE OBJECT NICE | ||
| Line 307: | Line 395: | ||
ACCESS PRIVILEGES: | ACCESS PRIVILEGES: | ||
NONE | NONE | ||
| + | </PRE> | ||
| + | <PRE> | ||
NCP>LIST KNOWN LINES | NCP>LIST KNOWN LINES | ||
CONFIGURATION DATABASE LINE XMA0 | CONFIGURATION DATABASE LINE XMA0 | ||
| Line 501: | Line 591: | ||
===OPCOM DECnet Messages=== | ===OPCOM DECnet Messages=== | ||
| − | Opcom, DECnet line XMA0: went down | + | <PRE>Opcom, DECnet line XMA0: went down</PRE> |
| − | Opcom, DECnet line XMA0: received a valid node init from address: 2, name: VAX1 | + | <PRE>Opcom, DECnet line XMA0: received a valid node init from address: 2, name: VAX1</PRE> |
| − | Opcom, DECnet line XMA0: shutting down | + | <PRE>Opcom, DECnet line XMA0: shutting down</PRE> |
| − | Opcom, DECnet shutting down | + | <PRE>Opcom, DECnet shutting down</PRE> |
| − | Opcom, DECnet starting | + | <PRE>Opcom, DECnet starting</PRE> |
| − | Opcom, DECnet line XMA0: starting | + | <PRE>Opcom, DECnet line XMA0: starting</PRE> |
| − | Opcom, DECnet line XMA0: had a DSR on-to-off transition | + | <PRE>Opcom, DECnet line XMA0: had a DSR on-to-off transition</PRE> |
| − | Opcom, DECnet line XMA0: node password incorrect from address: 2, name: VAX1 | + | <PRE>Opcom, DECnet line XMA0: node password incorrect from address: 2, name: VAX1</PRE> |
===NCP Messages=== | ===NCP Messages=== | ||
| Line 534: | Line 624: | ||
</PRE> | </PRE> | ||
| + | <PRE> | ||
BADFIL, badly formatted file 'file-spec' | BADFIL, badly formatted file 'file-spec' | ||
Facility: NCP | Facility: NCP | ||
Explanation: The file was corrupted. | Explanation: The file was corrupted. | ||
User Action: Recreate the file. | User Action: Recreate the file. | ||
| + | </PRE> | ||
| + | <PRE> | ||
BADOPEN, cannot open file 'file-spec' | BADOPEN, cannot open file 'file-spec' | ||
Facility: NCP | Facility: NCP | ||
Explanation: There is a problem in reading from disk. | Explanation: There is a problem in reading from disk. | ||
User Action: Ensure that the disk drive is operational and that no hardware problems exist. | User Action: Ensure that the disk drive is operational and that no hardware problems exist. | ||
| + | </PRE> | ||
| + | <PRE> | ||
BADPARS, unrecognized parameter 'parameter' | BADPARS, unrecognized parameter 'parameter' | ||
Facility: NCP | Facility: NCP | ||
Explanation: A syntax error was detected in the command input. | Explanation: A syntax error was detected in the command input. | ||
User Action: Reenter the command correctly. | User Action: Reenter the command correctly. | ||
| + | </PRE> | ||
| + | <PRE> | ||
BADRSP, received wrong size nice message | BADRSP, received wrong size nice message | ||
Facility: NCP | Facility: NCP | ||
Explanation: NICE protocol incompatibility. | Explanation: NICE protocol incompatibility. | ||
User Action: Run against compatible NICE object or equivalent. | User Action: Run against compatible NICE object or equivalent. | ||
| + | </PRE> | ||
| + | <PRE> | ||
CINREJ, unable to complete network $assign | CINREJ, unable to complete network $assign | ||
Facility: NCP | Facility: NCP | ||
Explanation: Logical link to NICE object failed. | Explanation: Logical link to NICE object failed. | ||
User Action: Ensure that the configuration database is consistent with the User Authorization File and that .LOG files can be written to the default directory. Also, check that enough processes can be created. | User Action: Ensure that the configuration database is consistent with the User Authorization File and that .LOG files can be written to the default directory. Also, check that enough processes can be created. | ||
| + | </PRE> | ||
| + | <PRE> | ||
DELERR, error deleting file 'file-spec' | DELERR, error deleting file 'file-spec' | ||
Facility: NCP | Facility: NCP | ||
Explanation: PURGE KNOWN attempted to nonexistent database. | Explanation: PURGE KNOWN attempted to nonexistent database. | ||
User Action: None. | User Action: None. | ||
| + | </PRE> | ||
| + | <PRE> | ||
INVCOD, invalid line device code received | INVCOD, invalid line device code received | ||
Facility: NCP | Facility: NCP | ||
Explanation: NICE protocol incompatibility. | Explanation: NICE protocol incompatibility. | ||
User Action: None. | User Action: None. | ||
| + | </PRE> | ||
| + | <PRE> | ||
INVDBK, improper dialogue message received | INVDBK, improper dialogue message received | ||
Facility: NCP | Facility: NCP | ||
Explanation: NICE protocol incompatibility. | Explanation: NICE protocol incompatibility. | ||
User Action: None. | User Action: None. | ||
| + | </PRE> | ||
| + | <PRE> | ||
INVLID, improper line-id received from nice object | INVLID, improper line-id received from nice object | ||
Facility: NCP | Facility: NCP | ||
Explanation: Incompatible NICE object at target. | Explanation: Incompatible NICE object at target. | ||
User Action: None. | User Action: None. | ||
| + | </PRE> | ||
| + | <PRE> | ||
INVSTA, invalid state received from nice object | INVSTA, invalid state received from nice object | ||
Facility: NCP | Facility: NCP | ||
Explanation: NICE protocol incompatibility. | Explanation: NICE protocol incompatibility. | ||
User Action: None. | User Action: None. | ||
| + | </PRE> | ||
| + | <PRE> | ||
IOERR, ncp/nice io error | IOERR, ncp/nice io error | ||
Facility: NCP | Facility: NCP | ||
Explanation: A communications error occurred. | Explanation: A communications error occurred. | ||
User Action: Check the quality of the line. | User Action: Check the quality of the line. | ||
| + | </PRE> | ||
| + | <PRE> | ||
LINETYP, invalid line type | LINETYP, invalid line type | ||
Facility: NCP | Facility: NCP | ||
Explanation: The line type referred to is not supported. | Explanation: The line type referred to is not supported. | ||
User Action: Enter a valid line type. | User Action: Enter a valid line type. | ||
| + | </PRE> | ||
| + | <PRE> | ||
NOPRIV, diagnostic and operator privileges required | NOPRIV, diagnostic and operator privileges required | ||
Facility: NCP | Facility: NCP | ||
Explanation: DIAGNOSE and OPER privileges required. | Explanation: DIAGNOSE and OPER privileges required. | ||
User Action: Run NCP under account with DIAGNOSE and OPER privileges. | User Action: Run NCP under account with DIAGNOSE and OPER privileges. | ||
| + | </PRE> | ||
| + | <PRE> | ||
NOREC, no entry in database | NOREC, no entry in database | ||
Facility: NCP | Facility: NCP | ||
Explanation: A reference was made to nonexistent data. | Explanation: A reference was made to nonexistent data. | ||
User Action: Refer to data properly. | User Action: Refer to data properly. | ||
| + | </PRE> | ||
| + | <PRE> | ||
RANGE, numeric not within required range | RANGE, numeric not within required range | ||
Facility: NCP | Facility: NCP | ||
Explanation: A syntax error was detected. | Explanation: A syntax error was detected. | ||
User Action: Reenter the information correctly. | User Action: Reenter the information correctly. | ||
| + | </PRE> | ||
| + | <PRE> | ||
RECADD, new database record added | RECADD, new database record added | ||
Facility: NCP | Facility: NCP | ||
Explanation: The addition was completed successfully. | Explanation: The addition was completed successfully. | ||
User Action: None. | User Action: None. | ||
| + | </PRE> | ||
| + | <PRE> | ||
RECUPD, current database record updated | RECUPD, current database record updated | ||
Facility: NCP | Facility: NCP | ||
Explanation: The update operation completed successfully. | Explanation: The update operation completed successfully. | ||
User Action: None. | User Action: None. | ||
| + | </PRE> | ||
| + | <PRE> | ||
RMSERR, record io error on file 'file-spec' | RMSERR, record io error on file 'file-spec' | ||
Facility: NCP | Facility: NCP | ||
Explanation: A read or a write to file failed. | Explanation: A read or a write to file failed. | ||
User Action: Ensure that the disk drive is functioning properly. | User Action: Ensure that the disk drive is functioning properly. | ||
| + | </PRE> | ||
| + | <PRE> | ||
TOOLONG, text wrong length | TOOLONG, text wrong length | ||
Facility: NCP | Facility: NCP | ||
Explanation: The input did not meet syntactic requirements. | Explanation: The input did not meet syntactic requirements. | ||
User Action: Reenter with the correct input. | User Action: Reenter with the correct input. | ||
| + | </PRE> | ||
| + | <PRE> | ||
XMTERR, loop failed, nnn messages not sent | XMTERR, loop failed, nnn messages not sent | ||
Facility: NCP | Facility: NCP | ||
Explanation: An error occurred during the loopback test. | Explanation: An error occurred during the loopback test. | ||
User Action: Check the quality of the communications line. | User Action: Check the quality of the communications line. | ||
| + | </PRE> | ||
===DTSEND Messages=== | ===DTSEND Messages=== | ||
| + | <PRE> | ||
BADDATDAT, data echoed invalid | BADDATDAT, data echoed invalid | ||
Facility: DTSEND | Facility: DTSEND | ||
Explanation: Test error. | Explanation: Test error. | ||
User Action: Retry the test. | User Action: Retry the test. | ||
| + | </PRE> | ||
| + | <PRE> | ||
BADDATLEN, not enough data sent/received | BADDATLEN, not enough data sent/received | ||
Facility: DTSEND | Facility: DTSEND | ||
Explanation: Test error. | Explanation: Test error. | ||
User Action: Retry the test. | User Action: Retry the test. | ||
| + | </PRE> | ||
| + | <PRE> | ||
BADFUNC, invalid function type received | BADFUNC, invalid function type received | ||
Facility: DTSEND | Facility: DTSEND | ||
Explanation: DECnet test program protocol incompatibility. | Explanation: DECnet test program protocol incompatibility. | ||
User Action: Run against compatible version of DTRECV or equivalent. | User Action: Run against compatible version of DTRECV or equivalent. | ||
| + | </PRE> | ||
| + | <PRE> | ||
BADMAIL, unexpected mail received, type is 'mail-type' | BADMAIL, unexpected mail received, type is 'mail-type' | ||
Facility: DTSEND | Facility: DTSEND | ||
Explanation: The logical link was broken. | Explanation: The logical link was broken. | ||
User Action: Retry the operation. | User Action: Retry the operation. | ||
| + | </PRE> | ||
| + | <PRE> | ||
BADPAT, invalid data pattern received | BADPAT, invalid data pattern received | ||
Facility: DTSEND | Facility: DTSEND | ||
Explanation: Test error. | Explanation: Test error. | ||
User Action: Retry the test. | User Action: Retry the test. | ||
| + | </PRE> | ||
| + | <PRE> | ||
BADSEQNUM, invalid data sequence received | BADSEQNUM, invalid data sequence received | ||
Facility: DTSEND | Facility: DTSEND | ||
Explanation: Test error. | Explanation: Test error. | ||
User Action: Retry the test. | User Action: Retry the test. | ||
| + | </PRE> | ||
| + | <PRE> | ||
BADSUBFCN, invalid subfunction received | BADSUBFCN, invalid subfunction received | ||
Facility: DTSEND | Facility: DTSEND | ||
Explanation: DECnet test program protocol incompatibility. | Explanation: DECnet test program protocol incompatibility. | ||
User Action: Run against a compatible version of DTRECV or equivalent. | User Action: Run against a compatible version of DTRECV or equivalent. | ||
| + | </PRE> | ||
| + | <PRE> | ||
BADUSRDAT, connect/disconnect userdata invalid | BADUSRDAT, connect/disconnect userdata invalid | ||
Facility: DTSEND | Facility: DTSEND | ||
Explanation: Test error. | Explanation: Test error. | ||
User Action: Retry the test. | User Action: Retry the test. | ||
| + | </PRE> | ||
| + | <PRE> | ||
BADUSRLEN, connect/disconnect userdata is wrong length | BADUSRLEN, connect/disconnect userdata is wrong length | ||
Facility: DTSEND | Facility: DTSEND | ||
Explanation: Test error. | Explanation: Test error. | ||
User Action: Retry the test. | User Action: Retry the test. | ||
| + | </PRE> | ||
| + | <PRE> | ||
CINBAD, connect not accepted/rejected as expected | CINBAD, connect not accepted/rejected as expected | ||
Facility: DTSEND | Facility: DTSEND | ||
Explanation: Test error. | Explanation: Test error. | ||
User Action: Ensure that the correct DTRECV or equivalent is available at target node. | User Action: Ensure that the correct DTRECV or equivalent is available at target node. | ||
| + | </PRE> | ||
| + | <PRE> | ||
CINREJ, connect aborted, nsp reason is 'number' | CINREJ, connect aborted, nsp reason is 'number' | ||
Facility: DTSEND | Facility: DTSEND | ||
Explanation: Logical link to DTRECV could not be established. | Explanation: Logical link to DTRECV could not be established. | ||
User Action: Interpret NSP reason. | User Action: Interpret NSP reason. | ||
| + | </PRE> | ||
| + | <PRE> | ||
INVOPTION, non-supported flow control parameter received | INVOPTION, non-supported flow control parameter received | ||
Facility: DTSEND | Facility: DTSEND | ||
Explanation: DECnet test program protocol incompatibility. | Explanation: DECnet test program protocol incompatibility. | ||
User Action: Run with compatible version of DTRECV orequivalent. | User Action: Run with compatible version of DTRECV orequivalent. | ||
| + | </PRE> | ||
===NIC Messages=== | ===NIC Messages=== | ||
| + | <PRE> | ||
BADPARVAL, invalid parameter value | BADPARVAL, invalid parameter value | ||
Facility: NIC | Facility: NIC | ||
Explanation: One of the downline load parameters stored in the RSX-11 file image of the system to be loaded was unacceptable. | Explanation: One of the downline load parameters stored in the RSX-11 file image of the system to be loaded was unacceptable. | ||
User Action: Use VNP to modify the RSX-11 system image. | User Action: Use VNP to modify the RSX-11 system image. | ||
| + | </PRE> | ||
| + | <PRE> | ||
CONDATBAS, configuration database error | CONDATBAS, configuration database error | ||
Facility: NIC | Facility: NIC | ||
Explanation: An error was detected during an attempt to access the configuration database files. | Explanation: An error was detected during an attempt to access the configuration database files. | ||
User Action: Determine that the configuration database files exist and that their protection allows access by the default privileged DECnet account. | User Action: Determine that the configuration database files exist and that their protection allows access by the default privileged DECnet account. | ||
| + | </PRE> | ||
| + | <PRE> | ||
ILLFUNC, invalid function or option | ILLFUNC, invalid function or option | ||
Facility: NIC | Facility: NIC | ||
Explanation: Function not supported by target node. | Explanation: Function not supported by target node. | ||
User Action: None. | User Action: None. | ||
| + | </PRE> | ||
| + | <PRE> | ||
INVERRCOD, invalid error code | INVERRCOD, invalid error code | ||
Facility: NIC | Facility: NIC | ||
Explanation: NICE protocol incompatibility. | Explanation: NICE protocol incompatibility. | ||
User Action: None. | User Action: None. | ||
| + | </PRE> | ||
| + | <PRE> | ||
INVFILE, invalid file | INVFILE, invalid file | ||
Facility: NIC | Facility: NIC | ||
Explanation: This message originates in a NICE object on a non-VMS node. | Explanation: This message originates in a NICE object on a non-VMS node. | ||
User Action: Consult the remote node's documentation. | User Action: Consult the remote node's documentation. | ||
| + | </PRE> | ||
| + | <PRE> | ||
INVMSGFMT, invalid message format | INVMSGFMT, invalid message format | ||
Facility: NIC | Facility: NIC | ||
Explanation: Incompatible NICE object at target. | Explanation: Incompatible NICE object at target. | ||
User Action: None. | User Action: None. | ||
| + | </PRE> | ||
| + | <PRE> | ||
INVNODNAM, invalid node identification | INVNODNAM, invalid node identification | ||
Facility: NIC | Facility: NIC | ||
Explanation: The specified node name either exceeded 6 characters or contained a non-alphanumeric character. | Explanation: The specified node name either exceeded 6 characters or contained a non-alphanumeric character. | ||
User Action: Correct the node name specification. | User Action: Correct the node name specification. | ||
| + | </PRE> | ||
| + | <PRE> | ||
INVSRVNAM, invalid server identification | INVSRVNAM, invalid server identification | ||
Facility: NIC | Facility: NIC | ||
Explanation: The server node designated to downline load the target node is inaccessible. | Explanation: The server node designated to downline load the target node is inaccessible. | ||
User Action: Bring the server node online or modify the configuration database to specify a different server. | User Action: Bring the server node online or modify the configuration database to specify a different server. | ||
| + | </PRE> | ||
| + | <PRE> | ||
LIN_COMM, line communications error | LIN_COMM, line communications error | ||
Facility: NIC | Facility: NIC | ||
Explanation: Line protocol error. | Explanation: Line protocol error. | ||
User Action: Check the line and all associated hardware for validity. | User Action: Check the line and all associated hardware for validity. | ||
| + | </PRE> | ||
| + | <PRE> | ||
LIN_PROT, line protocol error | LIN_PROT, line protocol error | ||
Facility: NIC | Facility: NIC | ||
Explanation: A down-line load device caused an error(s). | Explanation: A down-line load device caused an error(s). | ||
User Action: Check the device for proper functioning. | User Action: Check the device for proper functioning. | ||
| + | </PRE> | ||
| + | <PRE> | ||
LINWNGSTA, line in wrong state | LINWNGSTA, line in wrong state | ||
Facility: NIC | Facility: NIC | ||
Explanation: SET STATE operation not valid. | Explanation: SET STATE operation not valid. | ||
User Action: Perform a valid operation. | User Action: Perform a valid operation. | ||
| + | </PRE> | ||
| + | <PRE> | ||
MSGSEQERR, dialogue message out of order | MSGSEQERR, dialogue message out of order | ||
Facility: NIC | Facility: NIC | ||
Explanation: Incompatible NICE object at target node. | Explanation: Incompatible NICE object at target node. | ||
User Action: None. | User Action: None. | ||
| + | </PRE> | ||
| + | <PRE> | ||
NOPRIV, insufficient status | NOPRIV, insufficient status | ||
Facility: NIC | Facility: NIC | ||
Explanation: A NICE object is running under an account that does not have DIAGNOSE or OPER privilege. | Explanation: A NICE object is running under an account that does not have DIAGNOSE or OPER privilege. | ||
User Action: Modify privileges of the default privileged account on the node where the operation failed. | User Action: Modify privileges of the default privileged account on the node where the operation failed. | ||
| + | </PRE> | ||
| + | <PRE> | ||
NO_REMOTE, remote NICE process not available | NO_REMOTE, remote NICE process not available | ||
Facility: NIC | Facility: NIC | ||
Explanation: Attempt at loopback failed. | Explanation: Attempt at loopback failed. | ||
User Action: Ensure that the NICE object can run at remote node. | User Action: Ensure that the NICE object can run at remote node. | ||
| + | </PRE> | ||
| + | <PRE> | ||
NORESOURCE, resource error | NORESOURCE, resource error | ||
Facility: NIC | Facility: NIC | ||
Explanation: A resource error, such as a system service failure, occurred during an attempt to complete the specified command. | Explanation: A resource error, such as a system service failure, occurred during an attempt to complete the specified command. | ||
User Action: Repeat the command. If the error persists, ensure that the system pool is adequate and that the configuration data base is consistent. | User Action: Repeat the command. If the error persists, ensure that the system pool is adequate and that the configuration data base is consistent. | ||
| + | </PRE> | ||
| + | <PRE> | ||
NO_ROOM, no room for new entry | NO_ROOM, no room for new entry | ||
Facility: NIC | Facility: NIC | ||
Explanation: No room for new entry in database. | Explanation: No room for new entry in database. | ||
User Action: Delete unwanted items from database. | User Action: Delete unwanted items from database. | ||
| + | </PRE> | ||
| + | <PRE> | ||
PRGERR, NICE process program error | PRGERR, NICE process program error | ||
Facility: NIC | Facility: NIC | ||
Explanation: A software error occurred, | Explanation: A software error occurred, | ||
User Action: Collect as much information as possible and submit an SPR. | User Action: Collect as much information as possible and submit an SPR. | ||
| + | </PRE> | ||
===DLE Messages=== | ===DLE Messages=== | ||
| + | <PRE> | ||
LOADFAIL, DECnet line 'line': downline load failure | LOADFAIL, DECnet line 'line': downline load failure | ||
Facility: DLE | Facility: DLE | ||
Explanation: Down-line load failed. | Explanation: Down-line load failed. | ||
User Action: Refer to the accompanying message. | User Action: Refer to the accompanying message. | ||
| + | </PRE> | ||
| + | <PRE> | ||
STARTING, DECnet line 'line-number' starting downline load | STARTING, DECnet line 'line-number' starting downline load | ||
Facility: DLE | Facility: DLE | ||
Explanation: A boot request was initiated by the satellite system. | Explanation: A boot request was initiated by the satellite system. | ||
User Action: None. | User Action: None. | ||
| + | </PRE> | ||
===Miscellaneous Messages=== | ===Miscellaneous Messages=== | ||
| + | <PRE> | ||
ABORT, abort | ABORT, abort | ||
Facility: VAX/VMS System Services | Facility: VAX/VMS System Services | ||
| Line 799: | Line 992: | ||
2. Following a network request, this status indicates that a logical link was disconnected. | 2. Following a network request, this status indicates that a logical link was disconnected. | ||
User Action: The operating system does not normally display this message; user programs should be coded to detect and respond to the status return. | User Action: The operating system does not normally display this message; user programs should be coded to detect and respond to the status return. | ||
| + | </PRE> | ||
| + | <PRE> | ||
ACCQUOTA, ACCOUNT had inadequate quota at remote node | ACCQUOTA, ACCOUNT had inadequate quota at remote node | ||
Facility: VAX/VMS System Services | Facility: VAX/VMS System Services | ||
Explanation: This severe error message is associated with a Status code returned from a system service request. An attempt was made to initiate a DECnet logical link connection. The target object is already using its quota of logical links or some other resource. | Explanation: This severe error message is associated with a Status code returned from a system service request. An attempt was made to initiate a DECnet logical link connection. The target object is already using its quota of logical links or some other resource. | ||
User Action: This condition is not usually permanent. Try to initiate the connection later. Consult the DECnet-VAX User's Guide for additional information. | User Action: This condition is not usually permanent. Try to initiate the connection later. Consult the DECnet-VAX User's Guide for additional information. | ||
| + | </PRE> | ||
| + | <PRE> | ||
BADPARAM, bad parameter value | BADPARAM, bad parameter value | ||
Facility: VAX/VMS System Services | Facility: VAX/VMS System Services | ||
| Line 814: | Line 1,011: | ||
5. If this message is associated with a status code returned by a request to a DR11-W interface, an odd transfer count was specified. | 5. If this message is associated with a status code returned by a request to a DR11-W interface, an odd transfer count was specified. | ||
User Action: Determine the system service call that returned the error, using the debugger if necessary. Verify that the call to the service was coded correctly. See the VAX/VMS System Services Reference Manual for coding specifications. | User Action: Determine the system service call that returned the error, using the debugger if necessary. Verify that the call to the service was coded correctly. See the VAX/VMS System Services Reference Manual for coding specifications. | ||
| + | </PRE> | ||
| + | <PRE> | ||
BUG_DAP, internal network error condition detected; DAP code=xxxxxx | BUG_DAP, internal network error condition detected; DAP code=xxxxxx | ||
Facility: VAX-11 RMS | Facility: VAX-11 RMS | ||
Explanation: A Data Access Protocol violation was detected by VAX-11 RMS while attempting to communicate with the Remote Access Listener. | Explanation: A Data Access Protocol violation was detected by VAX-11 RMS while attempting to communicate with the Remote Access Listener. | ||
User Action: Collect as much information as possible and submit an SPR. The status value (STV) field of the FAB or RAB contains the DAP status code. Consult the DECnet-VAX User's Guide to interpret the status code. Note, however, that the explanation is intended for users who are familiar with DAP. | User Action: Collect as much information as possible and submit an SPR. The status value (STV) field of the FAB or RAB contains the DAP status code. Consult the DECnet-VAX User's Guide to interpret the status code. Note, however, that the explanation is intended for users who are familiar with DAP. | ||
| + | </PRE> | ||
| + | <PRE> | ||
CRC, network DAP level CRC check failed | CRC, network DAP level CRC check failed | ||
Facility: VAX-11 RMS | Facility: VAX-11 RMS | ||
Explanation: CRC checksums computed by VAX-11 RMS and the File Access Listener (FAL) program did not match when compared during an RMS close operation. | Explanation: CRC checksums computed by VAX-11 RMS and the File Access Listener (FAL) program did not match when compared during an RMS close operation. | ||
User Action: The file that was created or modified may be corrupted. Repeat the file access. If the CRC error on close persists, the communication hardware is malfunctioning. | User Action: The file that was created or modified may be corrupted. Repeat the file access. If the CRC error on close persists, the communication hardware is malfunctioning. | ||
| + | </PRE> | ||
| + | <PRE> | ||
DIRFULL, directory is full | DIRFULL, directory is full | ||
Facility: VAX/VMS System Services | Facility: VAX/VMS System Services | ||
| Line 830: | Line 1,033: | ||
If associated with a DECnet operation, this message indicates that the directory of declared network names is full. | If associated with a DECnet operation, this message indicates that the directory of declared network names is full. | ||
User Action: Delete or purge unwanted files from the directory and repeat the request; specify a different directory for the output file; or, organize the directory into subdirectory levels to obtain more cataloging space. | User Action: Delete or purge unwanted files from the directory and repeat the request; specify a different directory for the output file; or, organize the directory into subdirectory levels to obtain more cataloging space. | ||
| + | </PRE> | ||
| + | <PRE> | ||
FILALRACC, file already accessed on channel | FILALRACC, file already accessed on channel | ||
Facility: VAX/VMS System Services | Facility: VAX/VMS System Services | ||
Explanation: This message is associated with a DECnet operation. A logical link already exists or is pending. | Explanation: This message is associated with a DECnet operation. A logical link already exists or is pending. | ||
User Action: Check for a programming error. | User Action: Check for a programming error. | ||
| + | </PRE> | ||
Revision as of 09:21, 5 June 2022
A VERY ROUGH DRAFT!
Contents
What is NCP?
Citation from "DECnet-VAX, Version 1.3 Software Product Description":
Network Control Program
The Network Control Program (NCP) performs three primary functions: displaying statistics, controlling network components, and testing network components.
Using the DECnet-VAX NCP utility, an operator can display the status of DECnet activity at the local node. The user can choose to display statistics related to the local node, other DECnet-VAX nodes, and communication lines, including information on traffic and errors. Using the DECnet-VAX NCP utility, the local operator can also perform many network control functions such as reconfiguring the local node’s network parameters, starting and stopping lines, activating the local node, and down-line loading DECnet-11S systems.
NCP allows the user to perform a series of tests that aid in isolating problems. NCP can be used to send and receive test messages over individual lines either between nodes or through other controlled loopback arrangements. The messages can then be compared.
NCP Remarks
- NCP is started with:
- MC NCP (the oldfashioned RSX-11-way), or:
- RUN SYS$SYSTEM:NCP (the VMS-way)
- You can either:
- enter complete NCP commands, or:
- start with only the beginning of an NCP command and after pressing [Enter] NCP will show you how you can continue
- LOCAL is what EXECUTOR is in newer NCP versions
- KNOWN means "all" (kind of a wildcard)
- Use [ESC] to abort NCP commands
NCP "Elements"
NODE
A NODE is a computer participating in a DECnet network.
NODEs have got DECnet numbers (= DECnet adresses) in the range 1 to 31 (DECnet Phase II).
NODEs have got names up to 6 characters long.
LOCAL
LOCAL is the DECnet NODE where NCP is executed.
REMOTE
REMOTE are other DECnet NODEs connected via DECnet.
LINE
A LINE is the physical connection between two DECnet NODEs.
A NODE can have more than one LINE (restrictions apply).
A LINE is named after the interface on the local end; i.e. DMC11_0 is the line of the first DMC11 on the local node, DMC11_1 is the second, and so on.
LINK
A LINK is an active data connection over a LINE.
A LINK has got a unique number.
A LINE can carry serveral LINKs at a time in parallel (restrictions apply).
COUNT
COUNT is a collection of statistical numbers, e.g. for LOCAL, a LINE, or a LINK.
OBJECT
An OBJECT is a program that works on behalf of a DECnet function.
OBJECTs have got names up to 8 characters long and a unique number.
NCP Command Syntax
(complete) means: no more data required
SET
LOCAL
ON
OFF
SHUT
LINE
<LINE IDENTIFIER(DEV_#_#_# OR "STRING")>
ON
OFF
LOOPBACK
DEVICE_LOOPBACK
<TEMPORARY REMOTE NAME TO USE FOR LOOPBACK(6 CHARS):>
ZERO
LOCAL (complete)
LINE
<LINE IDENTIFIER(DEV_#_#_# OR "STRING")> (complete)
KNOWN LINES (complete)
LOAD <REMOTE NODE NAME(1-6 CHARS):>
PURGE LOCAL REMOTE OBJECT LINE KNOWN
LIST
LOCAL (complete)
REMOTE
<REMOTE NODE NAME(1-6 CHARS):>
OBJECT
<OBJECT NAME(1-8 CHARS):>
LINE
<LINE IDENTIFIER(DEV_#_#_# OR "STRING"):>
KNOWN
LINES (complete)
REMOTES (complete)
OBJECTS (complete)
DEFINE
LOCAL
<ENTER NAME OF LOCAL NODE(1-6 CHARS):>
REMOTE
<REMOTE NODE NAME(1-6 CHARS):>
OBJECT
<OBJECT NAME(1-8 CHARS):>
LINE
<LINE NAME(1-16 CHARS):>
DISCONNECT <LOGICAL LINK NUMBER:>
LOOP
REMOTE
<REMOTE NODE NAME(1-6 CHARS):>
LOCAL
<NUMBER OF TIMES TO LOOP(1-65535):>
ONES
ZEROS
MIXED
<LENGTH IN BYTES OF BLOCK BEING LOOPED(1-255):>
SHOW
LINKS (complete)
COUNTS
LOCAL (complete)
LINE
<LINE IDENTIFIER(DEV_#_#_# OR "STRING")> (complete)
KNOWN LINES (complete)
STATUS
LOCAL (complete)
LINE
<LINE IDENTIFIER(DEV_#_#_# OR "STRING")> (complete)
KNOWN LINES (complete)
MODIFY
LOCAL
NAME
NUMBER
MAXLINKS
MAXNODES
REMOTE
<REMOTE NODE NAME(1-6 CHARS):>
BOOTPW
CONNECT_TIMER
DLLFILE
HOST
NAME
NONPRVACC
NONPRVID
NONPRVPSW
NUMBER
PRVA
CC
PRVID
PRVPSW
RCVPW
SECLDR
SERVER
SERVER_LINE
TERLDR
XMTPW
OBJECT
<OBJECT NAME(1-8 CHARS):>
NAME/NUMBER/FILE/PRIVILEGES
LINE
<LINE NAME(1-16 CHARS):>
ADDRESS
BUFFERSIZE
CHARACTERISTICS
DEVICE_TYPE
<LINE IS <DMC11/DQ11/...>
LINE
NAME
NUMBER
NUMBERBUFFERS
REMOTE
TIMEOUT
EXIT (complete)
NCP Command Examples
The examples are taken on a NODE with two DMC11 interfaces.
SHOW
NCP>SHOW LINKS
LINKS FOR LOCAL AS OF 7-DEC-1980 13:26:50.69
NODE=VAX1
376/0002002A 375/00050029
NCP>SHOW COUNTS LOCAL COUNTS OF LOCAL, AS OF 7-DEC-1980 13:30:46.24 NODE=VAX1 SECONDS SINCE LAST ZEROED 2229 USER MESSAGES SENT 1128 USER MESSAGES RECEIVED 1128 EXTRANEOUS MESSAGES RECEIVED 0 FORMAT ERRORS IN ROUTING DATA 0 FORMAT ERRORS OTHER THAN ROUTING 0 RESOURCE ERRORS 0 SUCCESSFUL NEIGHBOR INITIALIZATIONS 0 UNSUCCESSFUL NEIGHBOR INITIALIZATIONS 0 CURRENTLY ACTIVE LOGICAL LINKS 2 MAXIMUM LOGICAL LINKS ACTIVE 4 CONNECTS INITIATED 3 CONNECTS RECEIVED 3
NCP>SHOW COUNT LINE DMC11_1 COUNTS OF LINE, AS OF 7-DEC-1980 13:32:34.27 LINE=DMC11_1 SECONDS SINCE LAST ZEROED 190 RETRANSMISSIONS, LINE ERRORS 0 RECEIVED LINE ERRORS 0 RETRANMISSIONS, OTHER THAN LINE ERRORS AND PARITY 0 RECEIVE TIMEOUTS 0 RESOURCE ERRORS 0 BLOCKS RECEIVED 0 BLOCKS SENT 1
NCP>SHOW COUNT KNOWN LINES COUNTS OF KNOWN LINES, AS OF 7-DEC-1980 13:33:49.49 LINE=DMC11_0 SECONDS SINCE LAST ZEROED 7 RETRANSMISSIONS, LINE ERRORS 0 RECEIVED LINE ERRORS 0 RETRANMISSIONS, OTHER THAN LINE ERRORS AND PARITY 0 RECEIVE TIMEOUTS 0 RESOURCE ERRORS 0 BLOCKS RECEIVED 0 BLOCKS SENT 1 LINE=DMC11_1 SECONDS SINCE LAST ZEROED 7 RETRANSMISSIONS, LINE ERRORS 0 RECEIVED LINE ERRORS 0 RETRANMISSIONS, OTHER THAN LINE ERRORS AND PARITY 0 RECEIVE TIMEOUTS 0 RESOURCE ERRORS 0 BLOCKS RECEIVED 0 BLOCKS SENT 1
NCP>SHOW STATUS LOCAL STATUS OF LOCAL, AS OF 7-DEC-1980 13:35:35.82 NODE=VAX1(2),SYSTEM=VAX/VMS Version V2.0 ROUTING VERSION=3.1.0 COMMUNICATION VERSION=3.1.0 STATE=ON DEFAULT HOST=VAX1
NCP>SHOW STATUS LINE DMC11_1
STATUS OF LINE, AS OF 7-DEC-1980 13:36:33.95
LINE-ID STATE REMOTE
DMC11_1 OFF VAX3
NCP>SHOW STATUS KNOWN LINES
STATUS OF KNOWN LINES, AS OF 7-DEC-1980 13:37:51.22
LINE-ID STATE REMOTE
DMC11_0 OFF VAX2
DMC11_1 OFF VAX3
LIST
NCP>LIST LOCAL CONFIGURATION DATABASE LOCAL NODE LOCAL NODE NAME: VAX1 LOCAL NODE NUMBER: 2 MAXIMUM NUMBER OF LOGICAL LINKS: 128 MAXIMUM NUMBER OF REMOTE NODES: 10
NCP>LIST REMOTE VAX2 CONFIGURATION DATABASE NODE VAX2 NODE NUMBER: 3 PASSWORD REMOTE RECEIVES DURING INITIALIZATION: HELLOVAX PASSWORD REMOTE SENDS DURING INITIALIZATION: HELLOVAX SECONDARY LOADER FILE: TERTIARY LOADER FILE: DOWNLINE LOAD FILE: DEFAULT NON-PRIVILEGED USERID: GUEST DEFAULT NON-PRIVILEGED ACCOUNT NAME: DEFAULT PRIVILEGED USERID: SYSTEM DEFAULT PRIVILEGED ACCOUNT NAME: NSP CONNECT TIMEOUT CONSTANT 0 SECONDS REMOTES SERVER NODE: SERVERS LINE TO REMOTE: REMOTES HOST NODE:
NCP>LIST KNOWN OBJECTS
CONFIGURATION DATABASE OBJECT NICE
NETWORK WIDE NUMBER: 19
ASSOCIATED FILE NAME: NICE
ACCESS PRIVILEGES:
DIAGNOSE
OPER
CONFIGURATION DATABASE OBJECT TASK
NETWORK WIDE NUMBER: 0
ASSOCIATED FILE NAME: TASK
ACCESS PRIVILEGES:
NONE
CONFIGURATION DATABASE OBJECT FAL
NETWORK WIDE NUMBER: 17
ASSOCIATED FILE NAME: FAL
ACCESS PRIVILEGES:
NONE
CONFIGURATION DATABASE OBJECT DTR
NETWORK WIDE NUMBER: 63
ASSOCIATED FILE NAME: DTR
ACCESS PRIVILEGES:
NONE
CONFIGURATION DATABASE OBJECT MAIL
NETWORK WIDE NUMBER: 27
ASSOCIATED FILE NAME: MAIL
ACCESS PRIVILEGES:
NONE
CONFIGURATION DATABASE OBJECT REMACP
NETWORK WIDE NUMBER: 23
ASSOCIATED FILE NAME: REMACP
ACCESS PRIVILEGES:
NONE
NCP>LIST KNOWN LINES CONFIGURATION DATABASE LINE XMA0 DEVICE TYPE: DMC11 CONTROLLER NUMBER: 0 LINE NUMBER:0 LINE ADDRESS:0 ASSOCIATED NODE: VAX2 ASSOCIATED BUFFER SIZE: 192 NUMBER OF BUFFERS TO ALLOCATE: 6 CHARACTERISTICS: FULLDUPLEX MOP TIMEOUT CONSTANT: 10 SECONDS CONFIGURATION DATABASE LINE XMB0 DEVICE TYPE: DMC11 CONTROLLER NUMBER: 1 LINE NUMBER:0 LINE ADDRESS:0 ASSOCIATED NODE: VAX3 ASSOCIATED BUFFER SIZE: 192 NUMBER OF BUFFERS TO ALLOCATE: 6 CHARACTERISTICS: FULLDUPLEX MOP TIMEOUT CONSTANT: 10 SECONDS
Example NCP Command File (CONFIGNET.COM)
$ @CONFIGNET
!
!PURGE EVERYTHING
!
PURGE LOCAL
!
!LOCAL NODE DEFINITIONS
!
DEFINE LOCAL -
NAME VAX1 -
NUMBER 2 -
MAXLINKS 128 -
MAXNODES 10
!
!NODE DEFINITIONS FOR THE LOCAL
!
DEFINE REMOTE -
NAME VAX1 -
NUMBER 2 -
SECLDR _NA -
TERLDR _NA -
DLLFILE _NA -
BOOTPW _NA -
RCVPW HELLOVAX -
XMTPW HELLOVAX -
NONPRVID GUEST -
NONPRVPSW GUEST -
NONPRVACC _NA -
PRVID SYSTEM -
PRVPSW MANAGER -
PRVACC _NA -
CONNECT_TIMER _NA -
SERVER _NA -
SERVERLINE _NA -
HOST _NA
!
!REMOTE VAX2
!
DEFINE REMOTE -
NAME VAX2 -
NUMBER 3 -
SECLDR _NA -
TERLDR _NA -
DLLFILE _NA -
BOOTPW _NA -
RCVPW HELLOVAX -
XMTPW HELLOVAX -
NONPRVID GUEST -
NONPRVPSW GUEST -
NONPRVACC _NA -
PRVID SYSTEM -
PRVPSW MANAGER -
PRVACC _NA -
CONNECT_TIMER _NA -
SERVER _NA -
SERVERLINE _NA -
HOST _NA
!
!A REMOTE, DOWN-LINE LOADABLE RSX11S SYSTEM
!
DEFINE REMOTE -
NAME NOD11S -
NUMBER 5 -
SECLDR SECDMC.SYS -
TERLDR TERDMC.SYS -
DLLFILE NOD11S.SYS -
BOOTPW DUMP -
RCVPW HELLOALL -
XMTPW HELLOYES -
NONPRVID GUEST -
NONPRVPSW GUEST -
NONPRVACC _NA -
PRVID SYSTEM -
PRVPSW MANAGER -
PRVACC _NA -
CONNECT_TIMER _NA -
SERVER VAX1 -
SERVERLINE DMC11_1 -
HOST VAX1
!
!DEFINE CONNECTING LINES
!
DEFINE LINE -
NAME XMA0 -
DEVICE_TYPE DMC11 -
NUMBER 0 -
LINE _NA -
ADDRESS _NA -
REMOTE VAX2 -
BUFFERSIZE 192 -
NUMBERBUFFERS 6 -
CHARACTERISTICS FULLDUPLEX -
TIMEOUT 10
DEFINE LINE -
NAME XMB0 -
DEVICE_TYPE DMC11 -
NUMBER 1 -
LINE _NA -
ADDRESS _NA -
REMOTE NOD11S -
BUFFERSIZE 192 -
NUMBERBUFFERS 4 -
CHARACTERISTICS FULLDUPLEX -
TIMEOUT 10
!
!DEFINE NECESSARY OBJECTS
!
DEFINE OBJECT -
NAME NICE -
NUMBER 19 -
FILE NICE -
PRIVILEGES DIAGNOSE OPER
DEFINE OBJECT -
NAME TASK -
NUMBER 0 -
FILE TASK -
PRIVILEGES _NA
DEFINE OBJECT -
NAME FAL -
NUMBER 17 -
FILE FAL -
PRIVILEGES _NA
DEFINE OBJECT -
NAME DTR -
NUMBER 63 -
FILE DTR -
PRIVILEGES _NA
DEFINE OBJECT -
NAME MAIL -
NUMBER 27 -
FILE MAIL -
PRIVILEGES _NA
DEFINE OBJECT -
NAME REMACP -
NUMBER 23 -
FILE REMACP -
PRIVILEGES _NA
!
!TURN EVERYTHING ON
!
SET STATE LOCAL ON
SET STATE LINE DMC11_0 ON
SET STATE LINE DMC11_1 ON
DECnet Messages
OPCOM DECnet Messages
Opcom, DECnet line XMA0: went down
Opcom, DECnet line XMA0: received a valid node init from address: 2, name: VAX1
Opcom, DECnet line XMA0: shutting down
Opcom, DECnet shutting down
Opcom, DECnet starting
Opcom, DECnet line XMA0: starting
Opcom, DECnet line XMA0: had a DSR on-to-off transition
Opcom, DECnet line XMA0: node password incorrect from address: 2, name: VAX1
NCP Messages
from: [link | AA-D017B-TE VAX-VMS System Messages and Recovery Procedures Manual]
AMBIG, ambiguous parameter 'parameter' Facility: NCP Explanation: The command has a non unique input. User Action: Reenter the command with a unique parameter.
BADACP, unable to start network acp Facility: NCP Explanation: NCP could not create a process or could not find CCP.EXE. User Action: Ensure that enough processes can be created and that DECnet has been properly installed.
BADCON, cannot connect to file 'file-spec' Facility: NCP Explanation: Possible disk drive error. User Action: Check the drive for proper functioning.
BADFIL, badly formatted file 'file-spec' Facility: NCP Explanation: The file was corrupted. User Action: Recreate the file.
BADOPEN, cannot open file 'file-spec' Facility: NCP Explanation: There is a problem in reading from disk. User Action: Ensure that the disk drive is operational and that no hardware problems exist.
BADPARS, unrecognized parameter 'parameter' Facility: NCP Explanation: A syntax error was detected in the command input. User Action: Reenter the command correctly.
BADRSP, received wrong size nice message Facility: NCP Explanation: NICE protocol incompatibility. User Action: Run against compatible NICE object or equivalent.
CINREJ, unable to complete network $assign Facility: NCP Explanation: Logical link to NICE object failed. User Action: Ensure that the configuration database is consistent with the User Authorization File and that .LOG files can be written to the default directory. Also, check that enough processes can be created.
DELERR, error deleting file 'file-spec' Facility: NCP Explanation: PURGE KNOWN attempted to nonexistent database. User Action: None.
INVCOD, invalid line device code received Facility: NCP Explanation: NICE protocol incompatibility. User Action: None.
INVDBK, improper dialogue message received Facility: NCP Explanation: NICE protocol incompatibility. User Action: None.
INVLID, improper line-id received from nice object Facility: NCP Explanation: Incompatible NICE object at target. User Action: None.
INVSTA, invalid state received from nice object Facility: NCP Explanation: NICE protocol incompatibility. User Action: None.
IOERR, ncp/nice io error Facility: NCP Explanation: A communications error occurred. User Action: Check the quality of the line.
LINETYP, invalid line type Facility: NCP Explanation: The line type referred to is not supported. User Action: Enter a valid line type.
NOPRIV, diagnostic and operator privileges required Facility: NCP Explanation: DIAGNOSE and OPER privileges required. User Action: Run NCP under account with DIAGNOSE and OPER privileges.
NOREC, no entry in database Facility: NCP Explanation: A reference was made to nonexistent data. User Action: Refer to data properly.
RANGE, numeric not within required range Facility: NCP Explanation: A syntax error was detected. User Action: Reenter the information correctly.
RECADD, new database record added Facility: NCP Explanation: The addition was completed successfully. User Action: None.
RECUPD, current database record updated Facility: NCP Explanation: The update operation completed successfully. User Action: None.
RMSERR, record io error on file 'file-spec' Facility: NCP Explanation: A read or a write to file failed. User Action: Ensure that the disk drive is functioning properly.
TOOLONG, text wrong length Facility: NCP Explanation: The input did not meet syntactic requirements. User Action: Reenter with the correct input.
XMTERR, loop failed, nnn messages not sent Facility: NCP Explanation: An error occurred during the loopback test. User Action: Check the quality of the communications line.
DTSEND Messages
BADDATDAT, data echoed invalid Facility: DTSEND Explanation: Test error. User Action: Retry the test.
BADDATLEN, not enough data sent/received Facility: DTSEND Explanation: Test error. User Action: Retry the test.
BADFUNC, invalid function type received Facility: DTSEND Explanation: DECnet test program protocol incompatibility. User Action: Run against compatible version of DTRECV or equivalent.
BADMAIL, unexpected mail received, type is 'mail-type' Facility: DTSEND Explanation: The logical link was broken. User Action: Retry the operation.
BADPAT, invalid data pattern received Facility: DTSEND Explanation: Test error. User Action: Retry the test.
BADSEQNUM, invalid data sequence received Facility: DTSEND Explanation: Test error. User Action: Retry the test.
BADSUBFCN, invalid subfunction received Facility: DTSEND Explanation: DECnet test program protocol incompatibility. User Action: Run against a compatible version of DTRECV or equivalent.
BADUSRDAT, connect/disconnect userdata invalid Facility: DTSEND Explanation: Test error. User Action: Retry the test.
BADUSRLEN, connect/disconnect userdata is wrong length Facility: DTSEND Explanation: Test error. User Action: Retry the test.
CINBAD, connect not accepted/rejected as expected Facility: DTSEND Explanation: Test error. User Action: Ensure that the correct DTRECV or equivalent is available at target node.
CINREJ, connect aborted, nsp reason is 'number' Facility: DTSEND Explanation: Logical link to DTRECV could not be established. User Action: Interpret NSP reason.
INVOPTION, non-supported flow control parameter received Facility: DTSEND Explanation: DECnet test program protocol incompatibility. User Action: Run with compatible version of DTRECV orequivalent.
NIC Messages
BADPARVAL, invalid parameter value Facility: NIC Explanation: One of the downline load parameters stored in the RSX-11 file image of the system to be loaded was unacceptable. User Action: Use VNP to modify the RSX-11 system image.
CONDATBAS, configuration database error Facility: NIC Explanation: An error was detected during an attempt to access the configuration database files. User Action: Determine that the configuration database files exist and that their protection allows access by the default privileged DECnet account.
ILLFUNC, invalid function or option Facility: NIC Explanation: Function not supported by target node. User Action: None.
INVERRCOD, invalid error code Facility: NIC Explanation: NICE protocol incompatibility. User Action: None.
INVFILE, invalid file Facility: NIC Explanation: This message originates in a NICE object on a non-VMS node. User Action: Consult the remote node's documentation.
INVMSGFMT, invalid message format Facility: NIC Explanation: Incompatible NICE object at target. User Action: None.
INVNODNAM, invalid node identification Facility: NIC Explanation: The specified node name either exceeded 6 characters or contained a non-alphanumeric character. User Action: Correct the node name specification.
INVSRVNAM, invalid server identification Facility: NIC Explanation: The server node designated to downline load the target node is inaccessible. User Action: Bring the server node online or modify the configuration database to specify a different server.
LIN_COMM, line communications error Facility: NIC Explanation: Line protocol error. User Action: Check the line and all associated hardware for validity.
LIN_PROT, line protocol error Facility: NIC Explanation: A down-line load device caused an error(s). User Action: Check the device for proper functioning.
LINWNGSTA, line in wrong state Facility: NIC Explanation: SET STATE operation not valid. User Action: Perform a valid operation.
MSGSEQERR, dialogue message out of order Facility: NIC Explanation: Incompatible NICE object at target node. User Action: None.
NOPRIV, insufficient status Facility: NIC Explanation: A NICE object is running under an account that does not have DIAGNOSE or OPER privilege. User Action: Modify privileges of the default privileged account on the node where the operation failed.
NO_REMOTE, remote NICE process not available Facility: NIC Explanation: Attempt at loopback failed. User Action: Ensure that the NICE object can run at remote node.
NORESOURCE, resource error Facility: NIC Explanation: A resource error, such as a system service failure, occurred during an attempt to complete the specified command. User Action: Repeat the command. If the error persists, ensure that the system pool is adequate and that the configuration data base is consistent.
NO_ROOM, no room for new entry Facility: NIC Explanation: No room for new entry in database. User Action: Delete unwanted items from database.
PRGERR, NICE process program error Facility: NIC Explanation: A software error occurred, User Action: Collect as much information as possible and submit an SPR.
DLE Messages
LOADFAIL, DECnet line 'line': downline load failure Facility: DLE Explanation: Down-line load failed. User Action: Refer to the accompanying message.
STARTING, DECnet line 'line-number' starting downline load Facility: DLE Explanation: A boot request was initiated by the satellite system. User Action: None.
Miscellaneous Messages
ABORT, abort Facility: VAX/VMS System Services Explanation: An attempted operation was aborted: 1. The system returns this status for an I/O request that was canceled before it was completed. 2. Following a network request, this status indicates that a logical link was disconnected. User Action: The operating system does not normally display this message; user programs should be coded to detect and respond to the status return.
ACCQUOTA, ACCOUNT had inadequate quota at remote node Facility: VAX/VMS System Services Explanation: This severe error message is associated with a Status code returned from a system service request. An attempt was made to initiate a DECnet logical link connection. The target object is already using its quota of logical links or some other resource. User Action: This condition is not usually permanent. Try to initiate the connection later. Consult the DECnet-VAX User's Guide for additional information.
BADPARAM, bad parameter value Facility: VAX/VMS System Services Explanation: A value specified for a system function is not valid. Several conditions can cause this error: 1. If this message occurs as a result of a call to a file system ACP function, it indicates that parameter listoptions are not valid. 2. If this message occurs as a result of a call to the Formatted ASCII Output (SFAO) system service, it indicates that a control string contained an unknown directive. 3. If this message occurs as a result of a call to a network ACP control function, it indicates that one of the function parameters is out of range or has a bad format. 4. If this message is associated with a status code returned by a request to a DR32 interface, an attempt was made to set the data rate higher than the rate allowed by the SYSGEN parameter /XFMAXRATE. 5. If this message is associated with a status code returned by a request to a DR11-W interface, an odd transfer count was specified. User Action: Determine the system service call that returned the error, using the debugger if necessary. Verify that the call to the service was coded correctly. See the VAX/VMS System Services Reference Manual for coding specifications.
BUG_DAP, internal network error condition detected; DAP code=xxxxxx Facility: VAX-11 RMS Explanation: A Data Access Protocol violation was detected by VAX-11 RMS while attempting to communicate with the Remote Access Listener. User Action: Collect as much information as possible and submit an SPR. The status value (STV) field of the FAB or RAB contains the DAP status code. Consult the DECnet-VAX User's Guide to interpret the status code. Note, however, that the explanation is intended for users who are familiar with DAP.
CRC, network DAP level CRC check failed Facility: VAX-11 RMS Explanation: CRC checksums computed by VAX-11 RMS and the File Access Listener (FAL) program did not match when compared during an RMS close operation. User Action: The file that was created or modified may be corrupted. Repeat the file access. If the CRC error on close persists, the communication hardware is malfunctioning.
DIRFULL, directory is full Facility: VAX/VMS System Services Explanation: This message is associated with a status code returned from a file system ACP QIO request. The message indicates that an error occurred while a disk file was being created because the directory specified is full and cannot catalog any more entries. The maximum size of a directory file is 1024 blocks. If associated with a DECnet operation, this message indicates that the directory of declared network names is full. User Action: Delete or purge unwanted files from the directory and repeat the request; specify a different directory for the output file; or, organize the directory into subdirectory levels to obtain more cataloging space.
FILALRACC, file already accessed on channel Facility: VAX/VMS System Services Explanation: This message is associated with a DECnet operation. A logical link already exists or is pending. User Action: Check for a programming error.
