View source for NCP DECnet/VAX V1.3

'''A VERY ROUGH DRAFT!'''

== 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 (1976)|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

<PRE>
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):>
</PRE>

<PRE>
ZERO
   LOCAL (complete)
   LINE
      <LINE IDENTIFIER(DEV_#_#_# OR "STRING")> (complete)
   KNOWN LINES (complete)
</PRE>

<PRE>
LOAD
   <REMOTE NODE NAME(1-6 CHARS):>
</PRE>

<PRE>
PURGE
   LOCAL
   REMOTE
   OBJECT
   LINE
   KNOWN
</PRE>

<PRE>
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)
</PRE>

<PRE>
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):>
</PRE>

<PRE>
DISCONNECT
   <LOGICAL LINK NUMBER:>
</PRE>

<PRE>
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):>
</PRE>

<PRE>
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)
</PRE>

<PRE>
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
</PRE>

<PRE>
EXIT (complete)
</PRE>

===NCP Command Examples===
The examples are taken on a NODE with two DMC11 interfaces.

====SHOW====
<PRE>
NCP>SHOW LINKS
LINKS FOR LOCAL AS OF  7-DEC-1980 13:26:50.69
NODE=VAX1
                376/0002002A    375/00050029
</PRE>

<PRE>
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
</PRE>

<PRE>
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
</PRE>

<PRE>
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
</PRE>

<PRE>
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
</PRE>

<PRE>
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
</PRE>

<PRE>
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
</PRE>

====LIST====
<PRE>
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
</PRE>

<PRE>
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: 
</PRE>

<PRE>
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
</PRE>

<PRE>
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
</PRE>

==DECnet/VAX V1.3 Peculiarities==

Some DECnet/VAX V1.3 Peculiarities I found out while configuring resp. using it.

=== No DECnet CIRCUITS ===

At the time of DECnet/VAX V1.3 (DECnet Phase II) there were no DECnet '''CIRCUIT'''s.

The term '''CIRCUIT''' only came into being when DECnet PHASE III was introduced where certain types of '''LINE''' could have multiple '''CIRCUITS''' (logical connections that carry information between two nodes).

=== Definition of the LOCAL (EXECUTOR) Node in Two Places ===

The '''LOCAL''' node in DECnet/VAX V1.3 (called '''EXECUTOR''' in later versions) needs two definitions:
* The <code>'''DEFINE LOCAL'''</code> definition, and
* additionally a <code>'''DEFINE REMOTE'''</code> definition.
 
See the sample DECnet V1.3 [[NCP DECnet/VAX V1.3#Example NCP Command File (CONFIGNET.COM)|configuration file]] for details.

=== Required Receive Password ===

While in newer DECnet versions a receive password for nodes is optional, it is mandatory in DECnet/VAX V1.3:

 NCP>'''DEFINE REMOTE'''
 REMOTE NODE NAME(1-6 CHARS):'''TEST'''
 REMOTE NODE NUMBER(2-240):'''99'''
 FILENAME FOR SECONDARY LOADER(1-13 CHARS,OPTIONAL):
 FILE USED FOR TERTIARY LOADER(1-13 CHARS,OPTIONAL):
 DOWN-LINE LOAD FILE(1-13 CHARS,OPTIONAL):
 BOOTSTRAP PASSWORD(EXACTLY 4 CHARS,OPTIONAL):
 PASSWORD REMOTE SENDS DURING INIT SEQUENCE(1-8 CHARS):'''MUSTBE'''
 PASSWORD REMOTE EXPECTS DURING INIT SEQUENCE(1-8 CHARS,OPTIONAL):
 NON-PRIVILEGED DEFAULT USER IDENTIFICATION( 1-16 CHARS,OPTIONAL):
 NON-PRIVILEGED DEFAULT PASSWORD( 1-8 CHARS,OPTIONAL):
 NON-PRIVILEGED DEFAULT ACCOUNT NAME ( 1-16 CHARS,OPTIONAL):
 PRIVILEGED DEFAULT USER ID( 1-16 CHARS,OPTIONAL):
 PRIVILEGED DEFAULT PASSWORD( 1-8 CHARS,OPTIONAL):
 PRIVILEGED DEFAULT ACCOUNT NAME( 1-16 CHARS,OPTIONAL):
 TIMEOUT CONSTANT FOR NSP CONNECT SEQUENCES IN SECONDS(1-120,OPTIONAL):
 NAME OF REMOTES SERVER NODE(1-6 CHARS,OPTIONAL):
 SERVERS LINE TO REMOTE(DEV_#_#_#,OPTIONAL):
 REMOTES HOST NODE(1-6 CHARS,OPTIONAL):
 %NCP-S-RECADD, new database record added
 NCP>

=== Privileged Default User ID and Password ===

The:
* <code>'''PRIVILEGED DEFAULT USER ID'''</code> (paramter name: <code>'''PRVID'''</code>) and the 
* <code>'''PRIVILEGED DEFAULT PASSWORD'''</code> (paramter name: <code>'''PRVPSW'''</code>) 
must be set to the VMS SYSTEM Account and Password (or maybe another sufficient privileged account values (not yet tested)) of the local node; otherwise the local node will not be able to connect to other nodes.

=== Line Status Change === 

If a DECnet line goes off:

 Opcom, DECnet line XMA0: had a DSR on-to-off transition

and comes up again, DECnet V1.3/VAX does not recognize this automatically and you have to intervene manually: 

 NCP>'''SET STATE LOCAL OFF'''
    Opcom, 08:57:35.33, NETACP       Accnt=        
    Opcom, DECnet line XMA0: shutting down
 
 NCP>
    Opcom, 08:57:35.36, NETACP       Accnt=        
    Opcom, DECnet shutting down
 
 NCP>'''SET STATE LOCAL ON'''
    Opcom, 08:57:48.42, NETACP       Accnt=        
    Opcom, DECnet starting
 
 NCP>'''SET STATE LINE DMC11_0 ON'''
    Opcom, 08:58:12.55, NETACP       Accnt=        
    Opcom, DECnet line XMA0: starting
 
 NCP>
    Opcom, 08:58:26.86, NETACP       Accnt=        
    Opcom, DECnet line XMA0: received a valid node init from address: 3, name: VAX2
 
 NCP>

Maybe there's a more elegant way, but I don't know it yet.

==Example NCP Command File (CONFIGNET.COM)==

<PRE>
$ @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
</PRE>

==DECnet Messages==

===OPCOM DECnet Messages===
<PRE>Opcom, DECnet line XMA0: went down</PRE>
<PRE>Opcom, DECnet line XMA0: received a valid node init from address: 2, name: VAX1</PRE>
<PRE>Opcom, DECnet line XMA0: shutting down</PRE>
<PRE>Opcom, DECnet shutting down</PRE>
<PRE>Opcom, DECnet starting</PRE>
<PRE>Opcom, DECnet line XMA0: starting</PRE>
<PRE>Opcom, DECnet line XMA0: had a DSR on-to-off transition</PRE>
<PRE>Opcom, DECnet line XMA0: node password incorrect from address: 2, name: VAX1</PRE>

===NCP Messages===
from: [link | AA-D017B-TE VAX-VMS System Messages and Recovery Procedures Manual]

<PRE>
AMBIG, ambiguous parameter 'parameter'
Facility: NCP
Explanation: The command has a non unique input.
User Action: Reenter the command with a unique parameter.
</PRE>

<PRE>
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.
</PRE>

<PRE>
BADCON, cannot connect to file 'file-spec'
Facility: NCP
Explanation: Possible disk drive error.
User Action: Check the drive for proper functioning.
</PRE>

<PRE>
BADFIL, badly formatted file 'file-spec'
Facility: NCP
Explanation: The file was corrupted.
User Action: Recreate the file.
</PRE>

<PRE>
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.
</PRE>

<PRE>
BADPARS, unrecognized parameter 'parameter'
Facility: NCP
Explanation: A syntax error was detected in the command input.
User Action: Reenter the command correctly.
</PRE>

<PRE>
BADRSP, received wrong size nice message
Facility: NCP
Explanation: NICE protocol incompatibility.
User Action: Run against compatible NICE object or equivalent.
</PRE>

<PRE>
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.
</PRE>

<PRE>
DELERR, error deleting file 'file-spec'
Facility: NCP
Explanation: PURGE KNOWN attempted to nonexistent database.
User Action: None.
</PRE>

<PRE>
INVCOD, invalid line device code received
Facility: NCP
Explanation: NICE protocol incompatibility.
User Action: None.
</PRE>

<PRE>
INVDBK, improper dialogue message received
Facility: NCP
Explanation: NICE protocol incompatibility.
User Action: None.
</PRE>

<PRE>
INVLID, improper line-id received from nice object
Facility: NCP
Explanation: Incompatible NICE object at target.
User Action: None.
</PRE>

<PRE>
INVSTA, invalid state received from nice object
Facility: NCP
Explanation: NICE protocol incompatibility.
User Action: None.
</PRE>

<PRE>
IOERR, ncp/nice io error
Facility: NCP
Explanation: A communications error occurred.
User Action: Check the quality of the line.
</PRE>

<PRE>
LINETYP, invalid line type
Facility: NCP
Explanation: The line type referred to is not supported.
User Action: Enter a valid line type.
</PRE>

<PRE>
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.
</PRE>

<PRE>
NOREC, no entry in database
Facility: NCP
Explanation: A reference was made to nonexistent data.
User Action: Refer to data properly.
</PRE>

<PRE>
RANGE, numeric not within required range
Facility: NCP
Explanation: A syntax error was detected.
User Action: Reenter the information correctly.
</PRE>

<PRE>
RECADD, new database record added
Facility: NCP
Explanation: The addition was completed successfully.
User Action: None.
</PRE>

<PRE>
RECUPD, current database record updated
Facility: NCP
Explanation: The update operation completed successfully.
User Action: None.
</PRE>

<PRE>
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.
</PRE>

<PRE>
TOOLONG, text wrong length
Facility: NCP
Explanation: The input did not meet syntactic requirements.
User Action: Reenter with the correct input.
</PRE>

<PRE>
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.
</PRE>

===DTSEND Messages===
<PRE>
BADDATDAT, data echoed invalid
Facility: DTSEND
Explanation: Test error.
User Action: Retry the test.
</PRE>

<PRE>
BADDATLEN, not enough data sent/received
Facility: DTSEND
Explanation: Test error.
User Action: Retry the test.
</PRE>

<PRE>
BADFUNC, invalid function type received
Facility: DTSEND
Explanation: DECnet test program protocol incompatibility.
User Action: Run against compatible version of DTRECV or equivalent.
</PRE>

<PRE>
BADMAIL, unexpected mail received, type is 'mail-type'
Facility: DTSEND
Explanation: The logical link was broken.
User Action: Retry the operation.
</PRE>

<PRE>
BADPAT, invalid data pattern received
Facility: DTSEND
Explanation: Test error.
User Action: Retry the test.
</PRE>

<PRE>
BADSEQNUM, invalid data sequence received
Facility: DTSEND
Explanation: Test error.
User Action: Retry the test.
</PRE>

<PRE>
BADSUBFCN, invalid subfunction received
Facility: DTSEND
Explanation: DECnet test program protocol incompatibility.
User Action: Run against a compatible version of DTRECV or equivalent.
</PRE>

<PRE>
BADUSRDAT, connect/disconnect userdata invalid
Facility: DTSEND
Explanation: Test error.
User Action: Retry the test.
</PRE>

<PRE>
BADUSRLEN, connect/disconnect userdata is wrong length
Facility: DTSEND
Explanation: Test error.
User Action: Retry the test.
</PRE>

<PRE>
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.
</PRE>

<PRE>
CINREJ, connect aborted, nsp reason is 'number'
Facility: DTSEND
Explanation: Logical link to DTRECV could not be established.
User Action: Interpret NSP reason.
</PRE>

<PRE>
INVOPTION, non-supported flow control parameter received
Facility: DTSEND
Explanation: DECnet test program protocol incompatibility.
User Action: Run with compatible version of DTRECV orequivalent.
</PRE>

===NIC Messages===
<PRE>
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.
</PRE>

<PRE>
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.
</PRE>

<PRE>
ILLFUNC, invalid function or option
Facility: NIC
Explanation: Function not supported by target node.
User Action: None.
</PRE>

<PRE>
INVERRCOD, invalid error code
Facility: NIC
Explanation: NICE protocol incompatibility.
User Action: None.
</PRE>

<PRE>
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.
</PRE>

<PRE>
INVMSGFMT, invalid message format
Facility: NIC
Explanation: Incompatible NICE object at target.
User Action: None.
</PRE>

<PRE>
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.
</PRE>

<PRE>
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.
</PRE>

<PRE>
LIN_COMM, line communications error
Facility: NIC
Explanation: Line protocol error.
User Action: Check the line and all associated hardware for validity.
</PRE>

<PRE>
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.
</PRE>

<PRE>
LINWNGSTA, line in wrong state
Facility: NIC
Explanation: SET STATE operation not valid.
User Action: Perform a valid operation.
</PRE>

<PRE>
MSGSEQERR, dialogue message out of order
Facility: NIC
Explanation: Incompatible NICE object at target node.
User Action: None.
</PRE>

<PRE>
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.
</PRE>

<PRE>
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.
</PRE>

<PRE>
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.
</PRE>

<PRE>
NO_ROOM, no room for new entry
Facility: NIC
Explanation: No room for new entry in database.
User Action: Delete unwanted items from database.
</PRE>

<PRE>
PRGERR, NICE process program error
Facility: NIC
Explanation: A software error occurred,
User Action: Collect as much information as possible and submit an SPR.
</PRE>

===DLE Messages===
<PRE>
LOADFAIL, DECnet line 'line': downline load failure
Facility: DLE
Explanation: Down-line load failed.
User Action: Refer to the accompanying message.
</PRE>

<PRE>
STARTING, DECnet line 'line-number' starting downline load
Facility: DLE
Explanation: A boot request was initiated by the satellite system.
User Action: None.
</PRE>

===Miscellaneous Messages===
<PRE>
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.
</PRE>

<PRE>
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.
</PRE>

<PRE>
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.
</PRE>

<PRE>
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.
</PRE>

<PRE>
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.
</PRE>

<PRE>
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.
</PRE>

<PRE>
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.
</PRE>

[[Category: DECnet]]
[[Category: VAX Software]]