Home

HP NSARPA/1000 User's Manual

1. 372 NSINIT Gateway line connect call failed XLUEX LU is lu 373 NSINIT Gateway line internal error errorno 380 NSINIT WARNING Error clearing class number with LAN 1000 381 NSINIT Warning Cannot clean up IEEE 802 3 tables of NS kk 383 NSINIT Invalid Driver Type for NS LU Cleaning up The NS ARPA 1000 LAN code reported an error while reading multicast addresses from the card This error indicates that NSINIT encountered a problem while accessing an IEEE 802 3 communication link card The NS ARPA 1000 LAN code reported an error while storing multicast addresses to the card NSINIT will not pursue communication with the LAN 1000 software No IEEE 802 3 messages will be delivered to NS ARPA 1000 although initialization may complete successfully SAM may fill up with these messages because the LAN 1000 driver will still be receiving messages from NS ARPA 1000 An error occurred in an internal routine May be caused by an invalid LU or an internal error An internal error occurred in NSINIT The value returned in errorno is for HP use only The NS ARPA 1000 LAN code reported a problem during shutdown The NS ARPA 1000 LAN code could not return resources allocated The driver type for the LU described in previous messages is not the proper type NS ARPA initialization was aborted Program Specific Error Messages Refer to accompanying error messages f
2. Not enough characters have Use HELP on the command been entered for a parameter to Check syntax and try again differentiate it from another parameter A TELNET command was entered that requires an open connection Use the OPEN command to connect to the remote system first Then try the command again A node name was entered with more than 50 characters A node name cannot be greater than 50 characters Use HELP on the OPEN command Check syntax and try again Program Specific Error Messages 4 3 FTP User Error Messages The following error messages are returned to the current list device when an error is encountered by the FTP user program After a message is printed the user may again be presented with the FTP prompt In some cases after the FTP error is printed a NetIPC error will also be printed NetIPC errors give more detailed information for specific errors and are listed in Section 2 of this manual Message FTP internal error encountered FTP ERR 1 Unable to connect to specified computer FTP ERR 2 Illegal option found Valid ones are G I L N 0 sT U V 5 FTP ERR 3 Two nodenames in runstring ignoring second one FTP ERR 4 Ambiguous command FTP ERR 5 Invalid command FTP ERR 6 FTP login failed FTP ERR 7 Illegal reply code FTP ERR 8 Unexpected reply code from server Expected reply code code FTP ERR 9 FTP User Error Messages A
3. If you have a network map including it will help HP determine if the problem is related to your network configuration Document your interim or workaround solution The cause of the problem can sometimes gt be found by comparing the circumstances in which it occurs with the circumstances in which it does not occur Introduction 1 3 Numeric Error Codes The following NS ARPA 1000 errors are categorized according to the program call or parameter that returns them The following is a summary of the errors described in this section APLDR Error Codes These error codes may be returned when the LO command is issued in REMAT They may also be returned in the err parameter of the FLOAD call The LO command is described in the REMAT section and FLOAD is described in the Utilities section of the NS ARPA 1000 DS 1000 IV Compatible Services Reference Manual DLGON DLGOF DLGNS Error Codes These error codes are returned in the err parameter of DLGON DLGOF and DLGNS calls These calls are described in the Utilities section of the NS ARPA 1000 DS 1000 IV Compatible Services Reference Manual ERR Error Codes These error codes are returned to the err parameter of PTOP RFA and certain utility calls They may also be returned in the A and B registers after a DEXEC or utility call and to the current log device through REMAT The PTOP RFA utility calls REMAT and DEXEC are described in their respective sections of
4. Invalid Destination Network An invalid subnet mask was specified in the IP DCN GT section of NSINIT The link LU was not specified or was specified incorrectly A duplicate 802 link LU was entered The 802 station address specified is not in the correct format The proper format is H H H H H H where His one hexadecimal digit More than three IEEE 802 3 LUs were entered A group station address was entered for the individual station address of this node The destination network s IP address was not specified The destination network specified is not in the form of a valid IP address The IP Address format is n n n n where n is a number from 0 to 255 Program Specific Error Messages In the subnet mask bits are set to 1 for the network address and subnet number and to 0 for the node number Refer to Subnet Masks in the NS ARPA 1000 Generation and Initialization Manual Correct the subnet mask and rerun NSINIT If you are using NSINIT interactively enter an LU in the range of 1 to 255 If you are using NSINIT with an answer file correct the LU in the answer file as described above and rerun NSINIT If you are using NSINIT interactively enter a non duplicate LU If you are using NSINIT with an answer file correct the LU in the answer file and rerun NSINIT If you are using NSINIT interactively enter a valid station address If you are using NSINIT with an answer file correct the
5. Program Specific Error Messages Rerun NSINIT If the error persists reboot your system and try again If rebooting does not solve the problem this error requires HP notification Refer to the appropriate RTE reference manual for more information on the RTE error code Correct the link problem and rerun NSINIT This is an informational message only No action is required However if DS 1000 IV services are desired rerun NSINIT The following monitor names are valid for DS 1000 IV services CNSLM DLIST EXECM EXECW OPERM PROGL PTOPM RDBAM RFAM TRFAS and VCPMN This is an informational message only No action is required Rerun NSINIT with a correct LU This is an informational message only No action is required However if DS 1000 IV services are desired rerun NSINIT This is an informational message only No action is required However if you need the LU fix the card and rerun NSINIT If you are using NSINIT interactively enter a valid address to subsequent prompts If not correct your answer file and try again If you are using NSINIT interactively enter a valid address to subsequent prompts If not correct your answer file and try again 358 NSINIT Error Getting Multicast Address Cleaning up Error is errornum 359 NSINIT Error Saving Multicast Addresses Cleaning up Error is errornum 360 NS allocating RN GetSignalRN Terminating Error
6. RTE FILE ERROR nnn The reported FMP error See the appropriate FMP error occurred during a file access code for an explanation TIMEOUT NO REPLY FROM The HP 3000 did not respond to If timeouts occur often the REMOTE the last command try again master timeout value needs to be increased See your Network Manager TR STACK OVERFLOW The transfer stack is more than Shorten the transfer stack seven levels deep 4 60 Program Specific Error Messages UNINITIALIZED READ Local and or remote ID Reinitialize NS ARPA or use sequences do not match the DSMOD to change them HP 3000 WARNING ILLEGAL OPTION _ Printed only if severity 0 sP The option is ignored and specified with input from RTE LU processing continues or an RTE file in non spooled format WARNING RMOTE BUFFER Printed only if severity 0 Size up RMOTE and establish a TOO SMALL RMOTE has insufficient buffer new virtual session space at the end of the partition to hold some of the messages from the HP 3000 Program Specific Error Messages 4 61 Tracing Error Messages The error messages listed in this section are returned by the NS ARPA trace utilities NSTRC FMTRC and BRTRC These utilities are documented in the NS ARPA 1000 Maintenance and Principles of Operation Manual NSTRC Error Messages The following error messages are returned by the NS ARPA trace program NSTRC NSTRC Error Messages An error occurred in an EXEC Refer to the acco
7. An LU was specified for a remote node but the remote node is not part of the local network and is not connected via a Router 1000 link Level 0 was specified but DS 1000 services are not enabled A non NS ARPA LU 1u was specified for the Router 1000 LU table The master timeout is less than the result of the Message Accounting retry limit multiplied by the Message Accounting timeout Multiple neighbors have been assigned to the same LU number An IP address has been entered that is the duplicate of another IP address on a directly connected network Program Specific Error Messages If you are using NSINIT interactively verify that the IP address is correct If it is correct do not enter an LU number if it is not correct enter a valid IP address If you are using NSINIT with an answer file NSINIT has aborted Correct the answer file as described above and rerun NSINIT If you are using NSINIT interactively do not enter level number 0 if the node has NS ARPA 1000 or DS 1000 IV software If you are using NSINIT with an answer file NSINIT has aborted Correct the answer file as described above and rerun NSINIT If you are using NSINIT interactively enter a valid NS ARPA LU If you are using NSINIT with an answer file NSINIT has aborted Correct the LU in the answer file and rerun NSINIT If you are using NSINIT interactively enter a smaller Message Accounting timeout value for this node or a
8. Fileman flags not initialized This error message is persists reboot your system initialized returned when an error is and try again If rebooting does Terminating detected in the NS ARPA not solve the problem this error software NSINIT has requires HP notification terminated 42 NS Internal NSINIT encountered an error Rebooting your system may error Invalid smb when attempting to manipulate solve this problem If it does address Cleaning up the System Memory Block table not this error requires HP area and then terminated It notification attempted to clean up any allocated resources before terminating This error message is returned when an error is detected in the NS ARPA software 43 NS Warning The default log device LU 1 This is an informational Opened default file was opened instead of the log message No action is required name device specified 44 NS Internal NSINIT was informed that the Refer to the accompanying error error Hit Pascal Error Pascal error catcher was string for more information and Catcher Terminating entered This error message is rerun NSINIT If the error returned when an unexpected persists reboot your system Pascal error occurs for and try again If rebooting does example writing to the output not solve the problem this error file NSINIT has terminated requires HP notification 4 30 Program Specific Error Messages 45 NSINIT In
9. Link Error errornum accessing LU lu XLUEX 350 NS Warning No DS 1000 IV services specified 351 NSINIT Monitor Name Invalid 352 NSINIT Duplicate LU Entry ignored 353 NS Error Wrong type or can t read device type for LU lu kk 354 NS WARNING No DS 1000 IV 1000 3000 links were specified 355 NS Error errornum initializing Bisync LU lunum 356 NS Invalid 802 mcast addr LSB of the lst octet must be set 357 NS Invalid ITEEE 802 address Format is HH HH HH HH HH HH kk 4 46 Internal consistency check failed on the Nodal Routing Vector An RTE error errornum occurred when NSINIT attempted to determine the status of a link link LU 1u The user requested DS 1000 IV services but then did not instruct NSINIT to initialize either DS 1000 IV to DS 1000 IV or DS 1000 IV to DS 3000 services An invalid monitor name was entered for DS 1000 IV services The LU entered was previously entered as a BISYNC LU The DS 1000 IV to DS 3000 driver type is invalid or NSINIT could not read the driver type from the specified LU 1u DS 1000 IV to DS 3000 services were requested but no pool LUs or BISYNC LUs were specified NSINIT could not initialize LU lunum errornum is an EXEC error code The least significant bit LSB of the first octet must be set for multicast addresses An invalid IEEE 802 3 address was entered
10. NSINIT will not pursue communication with the LAN 1000 software No IEEE 802 3 messages will be delivered to NS ARPA 1000 although initialization may complete successfully SAM Refer to accompanying error messages for more information and try again Refer to accompanying error messages for more information and try again Make sure that no one else is running NSINIT and that subordinate program is dormant Rerun NSINIT Use the LAN 1000 NM program to check that the card and driver are communicating Check the table extension size for ID 67 Increase it if necessary and re generate the system Use the LAN 1000 NM program to check that the card and driver are communicating Check the table extension size for ID 67 Increase it if necessary and re generate the system may fill up with these messages because the LAN 1000 driver will still be receiving messages from NS ARPA 1000 The table extension for ID 67 may be too small in the system generation 4 54 Program Specific Error Messages 4104 NSINIT Error storing class number Driver reports errornum LU is lu 4105 NSINIT Error reading receive pkt filter LU lu 4106 NSINIT Error writing receive pkt filter LU lu 9000 NS Error input is not valid for this question NSINIT has encountered a Use the LAN 1000 NM program problem with the interface card to check that the card and driver associated with LU lu This
11. command file edit the file and rerun FMTRC If you are running FMTRC interactively correct the time and try again If you are using a command file edit the file and rerun FMTRC If you are running FMTRC interactively correct the trace level and try again If you are using a command file edit the file and rerun FMTRC If you are running FMTRC interactively specify three or fewer ids and try again If you are using a command file edit the the file to contain three or fewer ids and rerun FMTRC If you are running FMTRC interactively specify three or fewer sockets and try again If you are using a command file edit the file to contain three or fewer sockets and rerun FMTRC Rerun NSTRC and try again Rerun NSTRC and try again Specify a unique file name for the trace file FMTRCERR 22 VM size of FMTRC was linked with the VM Relink FMTRC with the VM FMTRC does not match VMA option NSTRC was also linked option so that the number of file xxxxx pages with the VM option but a pages matches the value filename different maximum page number returned in xxx and try again was specified The filename parameter contains the name of the VMA file FMTRCERR 23 Trace file The file name specified Make sure filename is the file is not a VMA Type 2 filename is not the name of a you intended to specify file filename VMA file FMTRCERR 24 FMTRC FMTRC encountered a message This error requires HP
12. from server FTP ERR 23 Network is not up FTP ERR 24 Required network resource is not available FTP ERR 25 Connection aborted Remote host unreachable FTP ERR 26 Illegal nodename Possible syntax error FTP ERR 27 A timeout has occurred Try request later FTP ERR 28 Break acknowledged Terminating transfer FTP ERR 29 FTP Connection lost to peer node Connection reset FTP ERR 30 Unexpected network error encountered FTP ERR 31 Input line too long FTP ERR 32 APPEND is not allowed in BINARY mode FTP ERR 33 4 6 FTP encountered an error when receiving reply code from the server The network is currently down See NetIPC error 4 and 107 in Section 2 A required resource such as DSAM resource number or sockets is not currently available Connection to be remote host was aborted because 1 remote host has been shutdown 2 some network links are malfunctioning 3 the network is extremely congested An invalid remote host was specified An internal timeout occurred while running FTP A break was issued by the user and accepted by FTP The connection to the peer node was aborted so the connection has been reset An internal NetIPC error has occurred The input line was greater than 256 characters APPEND is not supported for binary file transfers Program Specific Error Messages Refer to the NetIPC error in Section 2 of
13. is a member of a LAN No registry response A name look up query was sent to the remote registry referenced in an IPCLookUp Call but the registry never responded The node upon which the registry resides might be down or might be unreachable Could not interpret path The path report referenced by the specified path report descriptor contained uninterpretable information When this error occurs it may be indicative of a system software error It may also indicate that the path report was somehow corrupted between the time it was generated and the time it was interpreted Bad length The data length specified was either too long or too short Not a path report descriptor The descriptor specified in the parameter reserved for path report descriptors was not a path report descriptor One or more of the following actions can be taken 1 Verify that the name specified was the intended one 2 verify that an entry for the referenced socket registry was entered into the nodal registry by the system manager or 3 check to see if the node is down if the referenced registry is known to be supported by a LAN based node If the node crashed or is temporarily unreachable the caller may wait and try again later It is also possible that the entry entered into the local nodal registry is incorrect If this is the case the look up query may have been incorrectly addressed to a node other than the intended one Assum
14. or the file is being copied locally Indicates that an internal error has occurred This error requires HP notification The source file has fixed length records but the VARIABLE option was not given or the target computer requested that the target file should have fixed length records Padding cannot be stripped if the target records are to be fixed length An unexpected file system error occurred in accessing the target file Specify the VARIABLE option in conjunction with the STRIP option or remove the STRIP option Verify that the target file is accessible reset any previously given file equation or specify attributes that do not conflict with the file equation Also refer to the qualifying file system error string The source file name is invalid Check the source file name on the source computer syntax and try again The source file name contained Verify that the source file one or more wildcard specification is correct and try characters or was a directory again but no files or directories were matched by it The APPEND option is not supported on the target computer Remove the APPEND option and use REPLACE Or OVERWRITE whichever is appropriate or specify a nonexistent target file name and try again Program Specific Error Messages 4 15 OVERWRITE option is not supported NS NFTERR 52 Unable to create directory NS NFTERR 53 Error creating or accessing scratch file on so
15. passed option 20000 is greater than 256 bytes or is a negative value The length of one of the options is invalid Invalid node name The nodename specified in the RPM call is not valid or is unknown to NetIPC same as NetIPC error code 40 Logging Codes and Messages Correct the option or request code This error message is not used in NS ARPA 1000 RPM Check the RPMCreate or RPMControl call and make sure that the option array is constructed correctly Refer to NetIPC error code 40 in the Numeric Error Codes section of this manual 6 35 18020 XX XX XX 18021 XX XX XX 18022 XX XX XX No RPM parameter string The RPMGetString call has been invoked by the child program to retrieve the parameter string passed to it by the parent program but no parameter string exists possibly because all parameter strings have already been retrieved in previous RPMGet String Calls OR The program issuing the RPMGet String call is nota child program scheduled by the RPM Monitor Illegal string length The length of the parameter string for the pass string option 20000 in RPMCreate is negative The child program terminated abnormally Either a memory protect error occurred or the child was accidentally terminated by someone by RTE OF command Check the child and parent programs to make sure that the number of RPMGet String Calls matches the number of strings in the parent s RPMCreat
16. program monname that is already running NSINIT has aborted See error 210 above An invalid node name was entered NSINIT was unable to RP a subordinate program named progname Program Specific Error Messages Refer to the RTE error codes returned in aregister and bregister for more information Also refer to accompanying NSINIT error messages Refer to the RTE status status for more information Also refer to accompanying NSINIT error messages Refer to the RTE errors returned in aregisterand bregister for more information Reboot to deallocate the resource number if desired Refer to the RTE status returned in status for more information Deallocate the resource number or reboot if desired Refer to the RTE error codes returned in aregister and bregister for more information Also refer to accompanying NSINIT error messages Stop the program monname and rerun NSINIT Refer to accompanying error messages for more information Enter a valid node name Refer to the accompanying RTE error ierr for more information 4 41 301 NRV Specified LU is not a router 1000 LU k 302 NRV 1000 1000 services are not enabled kk 303 Link Specified LU is not a Driver 66 LU LU is lu 304 NRV MA retry limit times MA T O is greater than master T O k 305 NRV Multiple neighbors assigned to a single LU 306 NRV Duplicate IP address 4 42
17. socket with IPCCreate 300 XX XX XX The PRDC1 helper program This error requires HP received a fatal internal error notification 400 XX XX XX XX The consumer CONSM received This error requires HP a fatal internal error notification 0 401 xx ipcerror 0 The consumer received a fatal Refer to the NetIPC error code NetIPC error ipcerror while for more information attempting to send a message xx ipcerror 0 0 The consumer received a fatal Refer to the NetIPC error code NetIPC error pcerror while for more information attempting to receive a message 403 xx xx 0 0 The consumer received an This error requires HP incorrect message from the notification producer This error code indicates that a coding error exists in the NFT software 404 XX XX XX X The consumer received a This error requires HP message of the wrong length notification This error code indicates that a coding error exists in the NFT software or in the lower layers of NS ARPA 405 x xx muerror 0 0 The consumer was unable to This error will occur if the attach to a session No logon session in which DSCOPY is was given for the target file and running is prematurely the target node is local terminated Refer to the accompanying multiuser error code muerror for additional information Logging Codes and Messages 6 13 500 ipcerror 0 0 ipcerror 0 0 503 xx 0 0 504 muerror 0 0 505 muerror 0 0 506 ipcerror 0 0 507 ipcerror muerr
18. the intended value and that it was not negative or zero Verify that the value passed was the intended value and that it was not negative or zero Verify that the value passed was the intended value and that it was not greater than the socket s maximum receive size specified when the socket was created One or both of the following actions may be taken 1 Wait until some sockets have been aborted thus freeing some resources or 2 ask the System Manager to configure more resources for the protocols in the system One or both of the following actions may be taken 1 Retry the request again later after PXP has recovered some of its path records or 2 ask the System Manager to configure more PXP path records into the system One or both of the following actions may be taken 1 Retry the request later after some NetIPC connections have been aborted and some IP path records have been released or 2 ask the System Manager to configure more IP path records into the system No 802 path records The request could not be satisfied because IEEE 802 3 did not have an available path record Such path records are used to hold protocol context and addressing information No TCP path records The request could not be satisfied because TCP did not have an available path record Such path records are used to hold protocol addressing and context information Bad upper bound A bad upper descriptor bound was
19. 1024 bytes RPM at the child s node encountered an FMP error while either executing the FmpRunProgram option 23110 or the Restore Program option 23010 in RPMCreate The FMP error is contained in the FMPerror field of the log record header Too many child programs are executing at the child s node RPM cannot allocate another child program Insufficient memory to create a child program 1 There is not enough DSAM to create a new child program There are no more ID segments for another program to run The RPM child table is full and another child program cannot be created Unknown internal error An unexpected error was returned to RPM from another internal NS ARPA routine Bad RPM packet structure RPM received an internal packet 1 Make sure that RPM software installed at the child s and parent s nodes is compatible Check the FMP error and the option in RPMCreate Wait for resources to be deallocated and try the RPM call later 3 Increase DSAM on the child s node Increase the number of ID segments on the child s node Or wait until ID segments are released and try the RPM call later Wait until child programs have terminated and try the RPM call later Check the log file for other errors possibly from IPC and refer to the documentation on those errors The structure of the RPM message packet is incorrect which is not formatted according This error r
20. Another program is Try again WAITING ON SOURCE CLASS waiting on the source class number and requeueing is not allowed I012 2 LU NOT DEFINED EXECM The session you are Either log on to an account with FOR THIS SESSION executing under at the remote the necessary resources or have node does not have the them added to the default specified LU defined This may account definition be the result of a logon failure or inadequate resources of the default session account Alphanumeric Error Messages 3 9 RSxx Error Messages These error messages include the subsystem prefix RS to indicate Remote Session An RSxx error occurs when a program encounters a problem accessing session monitor at a remote node RS01 0 SLAVE MONITOR ATTACH FAILED SLAVE FAILED MONITOR SLAVE FAILED MONITOR SLAVE FAILED MONITOR SLAVE FAILED MONITOR RSO2 ERROR LOGON CLASS I O ON RESPONSE FROM RSO3 EXCEEDED LOCAL LIMIT ON NUMBER OF REMOTE SESSIONS RS03 1 NO AVAILABLE SESSION IDENTIFIERS AT DESTINATION NODE RS04 0 REMOTE SESSION ENVIRONMENT NOT INITIALIZED RSO05 0 WRONG PASSWORD FOR NON SESSION ACCESS TO A REMOTE NODE RSXX Error Messages MAST The session at the remote node is no longer accessible to this master Programs running under this session have been aborted RFAM Same as RSO1 0 above but reported by RFAM EXECM
21. Consult your Network Manager system has not been initialized for networked operation or it has been shut down by the system manager 5 Illegal socket type The calling process attempted to create a kind of socket that the system does not support Illegal protocol The protocol referenced is not supported by the system 7 Illegal flags A flags bit was set that is not supported Illegal option An illegal option was specified in the opt parameter 10 Protocol type mismatch A protocol and a socket kind type were specified that are not supported together 2 10 Numeric Error Codes Check the socketkind parameter to make sure it matches one of the socket types supported by the system One or more of the following actions may be taken 1 Check the protocol parameter to make sure it matches one of the protocol types supported by the system 2 make sure the system supports the referenced protocol 3 consider defaulting the protocol argument to zero thus letting the system decide which protocols are best Check the flags parameter to make sure that the correct bits are set Some calls may return information through the flags parameter and the bits returned may not be valid input on subsequent calls Check the opt parameter to make sure that it was correctly initialized with InitOpt and that all options added with Addopt are defined for the system One or both of the following actions may be taken
22. ERROR Monitor to be scheduled not dormant Cleaning up kk 517 NSINIT RTE error errornum on XLUEX call LU is lu 601 NSINIT DCN Invalid Input String 602 NSINIT DCN Invalid IP Address Format is n n n n 603 NSINIT DCN Invalid Lower Level Protocol ID Enter 802 or RTR 604 NSINIT DCN Invalid segment size 4 48 The NFT error message file nserrs msg is not on system All NFT error messages will be numeric not alphanumeric NSINIT could not deallocate a resource number allocated to NS ARPA NSINIT received a not dormant error from EXEC NSINIT has terminated and is cleaning up An RTE error was encountered during an XLUEX call User input omitted some required parameters An invalid IP address was specified The IP address format is n n n n where nisa number from 0 to 255 An invalid protocol ID was entered The segmentation size specified for the lower level protocol is an illegal size Program Specific Error Messages If error messages are desired put the file on system shut down NS ARPA and rerun NSINIT If numeric error codes are acceptable no action is required No action is necessary However you may reboot your system to recover the resource number Refer to accompanying error messages for more information Stop execution of monitor and rerun NSINIT Refer to the RTE manuals for an explanation of errornum NSINIT may continue
23. Error Messages BRTRC Error Messages The following error messages are returned by the NSTRC halt program BRTRC Message 7501 NSTRC is not running rteerror Failed Sending Stop Message to NSTRC ABReg areg breg Tracing is not enabled Access to DSAM not allowed mmgrerror 5 2 Tracing Error Messages BRTRC Error Messages NSTRC is dormant or no ID segment was found NSTRC must be running before BRTRC can be used to terminate tracing An RTE error rteerror was encountered when BSTRC attempted to set NSTRC s break flag An RTE error areg breg occurred while sending a message after the break flag was set No class number could be found for tracing in LC or DSAM This is a disastrous error The storage area in DSAM has been cleared mmgrerror is a Memory Manager error code A code of 1007 indicates that DSAM is corrupt a code of 1008 indicates that DSAM is corrupt because of a parity error This is an informational message only No action is required Refer to the appropriate RTE reference manual for more information Refer to the appropriate RTE reference manual for more information Use NSINIT to shut down and reinitialize NS ARPA If the error persists reboot your system If rebooting does not solve the problem notify your HP field office This error requires HP notification FMTRC Error Messages The following error messages are printed to the current log file or device
24. Memory Manager An MACCT reference did not reference a valid MACCT This could be caused if the reference did not point to an MACCT or if the MACCT was free This is an NS ARPA internal error Memory Manager The MBUF chain contained less than the number of bytes the operation required This is an NS ARPA internal error Memory Manager The capacity of the area is not large enough to hold all the data in the MBUF chain This is an NS ARPA internal error Logging Codes and Messages Reinitialize NS ARPA 1000 moving DSAM to unaffected memory or replace the defective memory This error requires HP notification If this error occurred in the event log and the system is busy no action is necessary However if throughput is significantly affected or if connections are lost then the size of DSAM should be increased If this error occurred in the event log and the system is busy no action is necessary However if throughput is significantly affected or if connections cannot be established then the size of DSAM should be increased This error requires HP notification This error requires HP notification This error requires HP notification This error requires HP notification This error requires HP notification 6 17 1017 1018 1019 1020 1021 1022 1023 1024 6 18 Memory Manager Resources still active in socket buffer Buffers are still in use This is an NS ARPA in
25. NS ARPA Shut down NS ARPA and check the NSINIT answer file Make corrections to the file and reinitialize NS ARPA 16011 Internal data structure error This error requires HP notification Program Specific Error Messages 4 29 NSINIT Error Messages The following error messages are returned to the current log device when an error is encountered by the NS ARPA initialization program NSINIT If the message catalog NSINIT MSG is missing from the directory from which NSINIT is running the following error message will be returned This error message will also be returned if the error number cannot be found in NSINIT MSG NSINIT message number number moreinfo An NSINIT error code is returned in number If additional information about the message is available it is returned in moreinfo NSINIT Error Messages 39 NS Internal An error has been detected in Rerun NSINIT If the error error Intinput range the NS ARPA software causing persists reboot your system invalid Terminating NSINIT to terminate and try again If rebooting does not solve the problem this error requires HP notification 40 NS End of file NSINIT encountered an Make sure the input file is occurred reading from end of file while reading from the complete and then rerun NSINIT file Terminating input device causing it to terminate 41 NS Internal File manipulation flags were not Rerun NSINIT If the error error
26. One or both of the following actions may be taken 1 Verify that the descriptor specified was the one that the calling process intended to specify 2 verify that the original call to create the VC socket succeeded Expect no more data from the remote process on this socket Do one of the following 1 Wait and try again some of the descriptors may have been gotten by this time 2 consider that the program s that were supposed to retrieve the previously given descriptors may not have run properly One or both of the following actions may be taken 1 Verify that the request code specified was the intended one 2 verify that the request code is supported on the local system see Network Interprocess Communication of NS ARPA 1000 User Programmer Reference Manual One or both of the following actions may be taken 1 Verify that the timeout value specified was the intended value 2 see Network Interprocess Communication of NS ARPA 1000 User Programmer Reference Manual to make sure the value is acceptable Recheck the initialization of the data vector Numeric Error Codes 2 17 Bad vector address The calling One or both of the following process specified a data vector actions may be taken 1 Verify argument that contained an that the data vector was address outside of the caller s initialized as intended or 2 accessible range verify that the byte addresses are being p
27. RPed but before RPM can schedule it Logoff failed The RPM Monitor failed to logoff the child session A Multiuser error is logged Group 3 option error An error occurred when executing a Group 3 option in an RPMCreate Call Wait until a parent program completes and RPM deallocates resources Try again later Refer to the Multiuser Log Message Codes subsection in Logging Codes and Messages section The xx and yy fields of the log header record contain the values of the A and B registers Refer to the RTE manuals for an explanation of the EXEC error Make sure that the child program exists and has an ID segment Then try again Refer to the Multiuser Log Message Codes subsection in the Logging Codes and Messages section Check the Group 3 option in the RPMCreate Call Alphanumeric Error Messages The NS ARPA 1000 error messages described in this section are categorized as follows e Subsystem Error Messages These error messages consist of four fields of information a subsystem prefix a numeric error code a numeric error qualifier code and an ASCII message For example the error message DS 1 0 PROGRAM NOT FOUND contains the subsystem prefix DS the error code 1 the error qualifier code 0 and the ASCII message PROGRAM NOT FOUND Subsystem errors may be returned to the current log device through REMAT or in the err parameter of PTOP RFA and certain utility calls They ma
28. Seah eessd hee ieeasgees 5 5 Chapter 6 Logging Codes and Messages OQVEIVIEW ie vice da aid aN R RNR A REMAN Kade REND A RMR bee eA eee ele 6 1 PY MON Error M ssages cis a0 le saedhie ites bbe mas aaam imaia ted Cota i 6 1 LOGCHG Error Messa eS 6655 65 6662 tb bi eho thos aasawa OOSEELAE REDEEM 6 1 Log Pile Codes and Messages 1 4 0 1h saacteiviie ever ad eee eee a ees 6 1 L g Mess ge C d s nit ens thei Ghee ele A eee en Fa 6 2 Location Codes pereos oe th thai e ew haan a oak AA Ei 6 2 ASCH Log Messages mri rere tio mupe enw Mids See oe seein wee ee 6 2 L g Records and Messages lt serorea oeeaaeaii ooh re GE E Oh EEA STEN 6 2 Eyent Class sxe i535 eves Sexo netong d TESE NEKEEN OENES TAKE PENE ENE ESNE TES 6 3 EOU oaea r ra S N E et O E E EAN 6 3 Location oreina aa E Pe E ee a 6 5 Xand yy Fields uo vice a get Honea sE NETE RRE NDEDER ERAGE 6 5 Lo Maske ricresce rrote tet irie SG Pane ead amp E EEA FAE REE 6 5 Process NANG iigoseitsudsiais sadak ipi anaa EA s ia GE FOE eee E S 6 5 SESSION deik aa aeai aa E ara cca acai a ware wa EAE arcu P E AEE NAE aoe 6 5 L g Message CodeS rie ca tears aEAE EEG Wate a wane aco aioe Sacer age 6 6 EVMOW Ernor Messages ics oscoi5 docu serai iiaa sel aA AA E E E ang ATE wee 6 7 LOGCHG Error Messages cco dc 6 N ake ee Gale bas CONS DEMON SEE Ra Caw 6 9 Log Message CodeS occ cdin Gis neds saree iba Gee cebend sae cre ets certain keeeeds 6 10 Generic Log Message Codes 0 999 cccccticevcenesavvnewvaenw
29. This error requires HP notification Verify that the scheduler and the subordinate program are the proper programs and rerun NSINIT If the error persists reboot your system and try again If rebooting does not solve the problem this error requires HP notification 4 53 810 NSINIT Encountered Pascal Error in prognum 811 NSINIT Internal Pascal in prognum Errors 812 NSINIT Subordinate not EXEC Program prognum Error dormant is 4101 NSINIT Error storing station addr Driver reports errornum LU is lu 4102 NSINIT Error storing MCAST address Driver Reports errornum LU is lu NSINIT subordinate program prognum returned a Pascal error indication to NSINIT Subordinate program numbers 1 through 3 refer to NSPR1 through NSPR3 program number 4 refers to NSPARS Same as 810 except more than one Pascal error has occurred NSINIT subordinate program prognum was not dormant when NSINIT attempted to schedule it Subordinate program numbers 1 through 3 refer to NSPR1 through NSPR3 program number 4 refers to NSPARS NSINIT has encountered a problem with the interface card associated with LU lu The table extension for ID 67 may be too small in the system generation NSINIT has encountered a problem with the interface card associated with LU lu This error indicates that NSINIT encountered a problem while accessing an IEEE 802 3 communication link card
30. by the trace formatting utility FMTRC Errors that occur because a message could not be formatted are also printed in the formatted trace file above the unformatted message If you receive an FMTRC error that requires HP notification you should create copies of the formatted trace file and the raw trace file from which it was produced for your HP representative to analyze FMTRC Error Messages FMTRCERR 1 Error internal to FMTRC errorno FMTRCERR 2 Error internal to FMTRC input FMTRCERR 3 FMP error errorcode opening format file filename FMTRCERR 4 VMA error errorcode opening trace file filename FMTRCERR 5 Trace file contents are not decipherable by FMTRC filename FMTRCERR 6 FMP error errorcode writing to format file filename FMTRCERR 7 Address specified is not valid address FMTRCERR 8 Protocol specified is not valid protocol An error has been detected in the NS ARPA software An errorno Of 1 indicates that a bad stream number has been detected an errorno of 2 indicates that a bad service monitor type has been detected Command file input input was unexpected This error requires HP notification This error requires HP notification The format file that you specified Refer to the accompanying FMP filename could not be error code errorcode for opened more information The trace file that you specified filename could not be opened FMTRC could not forma
31. call in the result parameter DSCOPY is covered in the NS ARPA 1000 User Programmer Reference Manual DSLIN Errors These ASCII error messages are returned to the current log device when an error is encountered by the program DSLIN DSLIN is explained in the NS ARPA 1000 Generation and Initialization Manual DSMOD Errors These ASCII error messages are returned to the current log device when an error is encountered by the program DSMOD DSMOD is explained in the NS ARPA 1000 Generation and Initialization Manual MVCP3 Error Messages These ASCII error messages are returned to the current log device if an error is encountered by the program MVCP3 MVCP3 is described in the NS ARPA 1000 Generation and Initialization Manual Nodal Registry Error Messages These ASCII error messages are returned by the Nodal Registry utility programs NRINIT and NRLIST NRINIT is described in the NS ARPA 1000 Generation and Initialization Manual NRLIST is described in the NS ARPA 1000 Maintenance and Principles of Operation Manual NSINF Errors These ASCII error messages are returned to the current log device when an error is encountered by the information utility program NSINE NSINF is explained in the NS ARPA 1000 Maintenance and Principles of Operation Manual NSINIT Errors These ASCII error messages are returned to the current log device when an error is encountered by the NS ARPA initialization program NSINIT NSINIT is explained in the NS ARPA 1000 Generat
32. disk space on the referenced disk allocated to the created file Break was entered during an No action is necessary FCOPY file transfer 26 28 29 33 Non NS ARPA error May be an Check parameters If all IO or RN error parameters are correct consult your Network Manager Do not call DSERR it will return invalid information 2 8 Numeric Error Codes HELLO BYE Error Codes These error codes are returned in the err parameter of the utility subroutines HELLO and BYE HELLO BYE Error Codes No error No action is necessary 1 HELLO failure or line Try again or report error to the disconnected Network Manager 4 Invalid LU The LU specified is Check parameters and try not a communications line to an again HP 3000 or the NS 3000 modules are not initialized Illegal rejected request Check syntax and try again Request is not recognized 7 Transaction Table access error See NSINF and DSMOD in the not enough Transaction Control NS ARPA 1000 Generation and Blocks for HELLO Initialization Manual Non NS ARPA error for Check syntax If OK consult example input only device your Network Manager specified as list LU Numeric Error Codes 2 9 NetIPC Error Codes These error codes are returned to the result parameter of Network Interprocess Communication NetIPC calls NetIPC Error Codes The call was successful No action is necessary 4 The network is down Either the
33. encountered an unknown that it could not format notification message FMTRC First Return Parameter Values The following values are returned in the first return parameter First Return Parameter Values EC i ee Invalid command file input was Refer to the log file or device for detected accompanying error messages Refer to FMTRCERR 3 for more E Refer to FMTRCERR 4 for more E Refer to FMTRCERR 22 for more Poa Refer to FMTRCERR 23 for more ented Refer to FMTRCERR 19 for more oa Tracing Error Messages 5 5 Logging Codes and Messages Overview The following codes and messages may be returned when logging is used They are divided into three categories e EVMON Error Messages e LOGCHG Error Messages e Log File Codes and Messages EVMON Error Messages The EVMON Error Messages are messages that are generated by the EVMON program and are returned to the scheduling terminal and or the log file LOGCHG Error Messages The LOGCHG Error Messages are messages that are generated by the LOGCHG program and are returned to the scheduling terminal Log File Codes and Messages The Log File Codes and Messages are divided into the following subcategories e Log Message Codes e Location Codes e ASCII Log Messages Logging Codes and Messages_ 6 1 Log Message Codes These codes are printed to the log message They are sent to the log file by certain software modules procedures processes
34. gateway indicated by the redirect message To shorten the path a message takes to the host configure the local node to send messages directly to the host This is an informational message only No action is required This message is not currently supported by NS ARPA 1000 If it was sent by another NS ARPA 1000 machine an internal error may be indicated If so this error requires HP notification This message is not currently supported by NS ARPA 1000 If it was sent by another NS ARPA 1000 machine an internal error may be indicated If so this error requires HP notification 3168 3169 IP An ICMP message of Such unknown messages are unknown type was received not supported IP An ICMP redirect message This message indicates a was received but the route to configuration error either at the the specified gateway is gateway doing the redirection or unknown at the host that received the redirect Check that the gateway and the host are properly configured on the pertinent networks The IP address of the new gateway is contained in the the xx and yy fields of the log record header Logging Codes and Messages 6 25 HP IEEE 802 ETHERNET Log Message Codes 4000 4999 HP IEEE 802 ETHERNET Log Message Codes 4000 4999 4001 4002 4003 4004 4005 4006 4007 4008 4009 4010 IEEE 802 Ethernet Tried to send on a link which was down May also occur if the link was not enab
35. has been found to be in error Security violation EXEC Calls 9 10 12 23 24 Illegal buffer address or length EXEC Calls 6 8 9 10 11 12 14 23 24 28 Program or segment name not EXEC Calls 8 9 10 12 23 24 found 28 DEXEC DEXEC has found the Correct the program name in caller s program name the schedule call If a clone is specification to be in error requested in a DEXEC 9 or DEXEC 23 call or RW from REMAT this error can occur if the type 6 file if applicable could not be opened or if there are no blank ID segments or if there are already 26 clones for this program name 3 12 Alphanumeric Error Messages SC05 2 PROGRAM NOT EXECM The NS ARPA monitor Load or RP the target program LOADED EXECM has issued the schedule or correct the program name in request and found the target the schedule call program to be non existent SC05 3 PROGRAM NOT EXECW The NS ARPA monitor Load or RP the target program LOADED EXECW has issued the schedule or correct the program name in request and found the target the schedule call program to be non existent Program is too large Never enough SAM to pass the EXEC Calls 9 10 14 23 24 desired string Not enough SAM to pass the EXEC Calls 9 10 14 22 23 24 desired string Alphanumeric Error Messages 3 13 SMxx Error Messages These error codes include the subsystem prefix SM to indicate Session Monitor They are
36. header and log message are illustrated below current Time EventClass Entity Location xx yy LogMask ProcessName Session LogMessage The log record header may include the current Time which is the current system time The current Time is not printed if there is less than one second difference between it and the last current Time printed 6 2 Logging Codes and Messages The log record header format is the same for all records however a field s meaning may vary according to the protocol or service that logs the record The format of the log message may also vary according to the protocol or service that logs the message The following subsections describe fields of the log record header Event Class The event class indicates the type of log record There are seven event classes e LogStat Class 0 e Prolog Class 1 protocol specific information e Event Class 2 event messages e Warning Class 3 warnings e Error Class 4 severe errors e Disaster Class 5 disasters e RsrceLim Class 6 resource limitations The codes and messages listed in this section correspond to Class 3 Class 4 Class 5 and Class 6 event classes only These classes are described in the NS ARPA 1000 Maintenance and Principles of Operation Manual Entity The Entity indicates the software module procedure process or protocol handler that reports the log record and or message A protocol handler is a set of software procedures that implement
37. if the problem is not severe However you should refer to accompanying error messages for more information If you are using NSINIT interactively enter a valid string in response If you are using NSINIT with an answer file correct the string in the answer file and rerun NSINIT If you are using NSINIT interactively enter a valid IP address If you are using NSINIT with an answer file correct the IP address in the answer file and rerun NSINIT If you are using NSINIT interactively enter a valid protocol enter one of the valid protocol IDs listed in the NSINIT question If you are using NSINIT with an answer file correct the protocol ID in the answer file as described above and rerun NSINIT If you are using NSINIT interactively enter a size which is in the range specified in the NSINIT question If you are using NSINIT with an answer file correct the segmentation size in the answer file as described above and rerun NSINIT 605 NSINIT IP Invalid subnet mask form Format 1 s followed by 0 s 615 NSINIT 802 Invalid Link LU Range 1 255 616 NSINIT 802 Duplicate Link LU 617 NSINIT 802 Invalid Station Address Format is H H H H H H k 618 NSINIT 802 many IEEE 802 3 LUs entered Terminating Too 619 NSINIT 802 IEEE 802 Group Station address not allowed 620 NSINIT GT Destination Network not specified 621 NSINIT GT
38. is an informational message only No action is required If you are using NSINIT interactively enter a valid action Valid actions are 1 through 4 If you are using NSINIT with an answer file correct the action in the answer file and rerun NSINIT Enter a valid action and try again If you are using NSINIT with an answer file correct the action in the answer file and rerun NSINIT Specify a new input device and rerun NSINIT Rerun NSINIT If the problem persists this error requires HP notification Reload or rerun NSINIT This is an informational message No action is required Shut down NS ARPA and rerun NSINIT Check your system for memory problems and or this error requires HP notification 4 35 135 NSINIT MMInit Bad Minimum Cluster Count Terminating 136 NSINIT MMInit Bad Tablesize Terminating 137 NSINIT MMInit Bad Globals Terminating Min buffer value 138 NSINIT SHEMA needed is table space of 139 NSINIT Internal return parameter Invalid Terminating 140 NSINIT MMInit SHEMA size error MMInit Terminating 4 36 MMINIT calculates an internal value for the minimum cluster count this count was invalid This error message is returned when an error is detected in the NS ARPA software NSINIT passed a table size that was less than zero to MMINIT causing NSINIT to terminate This error message may be returned
39. mark TELNET ERR 4 Illegal command TELNET ERR 5 Unknown command TELNET ERR 6 This error may be returned for one of the following reasons 1 TELNET was unable to acquire sufficient system resources such as sockets or 2 an error occurred in accessing Distributed System Available Memory DSAM or tables in DSAM 3 user s terminal is not connected to a D MUX or A400 Unable to initialize TELNET TELNE T ERR 8 MUX or is not a remote TELNET session An illegal escape character was entered Illegal escape character TELNET ERR 9 4 2 Program Specific Error Messages An internal TELNET error has This error requires HP occurred notification 1 Verify that the target computer name is correct 2 the target computer is connected to the network 3 that there are sufficient system resources to establish a connection or 4 that TELNET has been initialized on the target computer Shorten the length of the command input line to less than 80 characters Check syntax and try again Use HELP if necessary Check syntax and try again A TELNET command was Use HELP if necessary Check entered incorrectly syntax and try again Input command is too big You typed in a command with Shorten the command check TELNET ERR 7 more than 256 characters syntax and try again An additional error may follow this message which will offer further explanation Use HELP on the ESC
40. message No action is required Illegal access Same as SMO5 Enter correct password No such user Same as SM04 Enter a valid account name Session limit exceeded Same Wait for someone to logoff as SM03 Required class number not Possible generation error available Same as SMO2 LOGON requires a class number for its own use FMP error xxxxx on Account Consult your System Manager File access Same as SM01 Remote session was lost or After an error of this type future ATTACH failed Same as requests will cause a new RSO1 session to be established Ifa specific session is required rather than the default session you must issue a specific attach from REMAT or logon request Numeric Error Codes 2 3 Class I O error on response Try again and if the error from LOGON Same as RSO2 persists consult your System Manager Limit exceeded on of remote The local limit may have been nodes Same as RSO3 reached on the number of remote nodes accessed by this program limit is 16 If this is not the case you may need a larger value for NSINIT s ACTIVE TRANSActionS NOTE PNLs for remote 1000 3000 sessions and master TCBs for remote requests are taken from the same block of SAM 4 Remote session environment When session is shut down at a not initialized Same as RS04 remote node it looks to NS ARPA as though the node has been generated without Session Monitor or Sessi
41. not enable the LU or omit the enable indicator to use the default If you are using NSINIT with an answer file NSINIT has aborted Correct your response in the answer file as described above and rerun NSINIT 4 43 314 Link Improper rerouting option Enter RR or NR 315 Link cost value Invalid 316 NRV Invalid node number 317 NRV address Invalid IP 318 NRV Invalid LU number 4 44 An invalid rerouting option was entered The value entered for the cost of a link is out of range A Router 1000 address entered is out of range An IP address entered is either invalid no information was provided about that network in the IP section of NSINIT or is not in the proper format An LU number was entered that is out of range Program Specific Error Messages If you are using NSINIT interactively type either RR use dynamic rerouting on this LU or NR do not use rerouting on this LU If you are using NSINIT with an answer file NSINIT has aborted Correct your response in the answer file as described above and rerun NSINIT If you are using NSINIT interactively enter a value in the range 1 to 99 or omit the value to indicate the default If you are using NSINIT with an answer file NSINIT has aborted Correct your response in the answer file as described above and rerun NSINIT If you are using NSINIT interactively enter a Router 1000 addre
42. notification retransmission effort This is an NS ARPA internal error Logging Codes and Messages 6 53 1001 Could not reset the timer This error requires HP needed for a Probe name notification request transmission This is an NS ARPA internal error 1100 Indicates a configuration This error requires HP problem Could not find an notification entry for the local node in the local node s Nodal Registry database This is an NS ARPA internal error 1101 Could not read the local node s__ This error requires HP entry out of the local node s notification Nodal Registry database This is an NS ARPA internal error 1102 Unable to write an unsolicited This error requires HP Probe reply message in a DSAM notification mbuf prior to transmission This is an NS ARPA internal error 1103 Unable to set the timer used for This error requires HP unsolicited Probe reply notification messages This is an NS ARPA internal error 1200 Had trouble writing a Virtual This error requires HP Address Probe request notification message into DSAM prior to transmission This is an NS ARPA internal error 1201 Could not set a timer needed to This error requires HP time the retransmission interval notification for a Virtual Address Probe transaction This is an NS ARPA internal error 1300 Had trouble writing a Probe This error requires HP Virtual Address request retry notification message into a DSAM mbuf This is an NS ARPA i
43. of entries system This can be done by in the RTE multiuser table using the RTAGN us command 2003 System is not multiuser This is an informational code only No action is required 2004 No such user Correct the supplied user name and try again 2007 2010 2012 2014 Errors greater than 2100 RTE reports no more available sessions Duplicate program name An attempt was made to attach to a session The request was rejected since there was already a program by the same name in the specified session Corrupt key An NS ARPA session key has been determined to be corrupt This indicates either an internal error in the NS ARPA code or corrupt tables in DSAM No such session An attempt was made to attach to a non existent session The session may have been logged off Bad logon password RTE reports an incorrect password was supplied in a logon attempt Errors greater than 2100 are actually FMP errors To calculate the FMP error code subtract 2100 from the error code 6 20 Logging Codes and Messages See error 2002 for more information Delete the duplicate program s ID segment for example OF prog ID If the problem persists you may need to reinitialize NS This is an informational code only No action is required Correct the password and try again Refer to the RTE Programmer s Reference Manual for descriptions of FMP errors HP IP Log Message Codes 3000 3999 H
44. or 3 the network is extremely congested If the timeout occurs frequently you may consider modifying the socket s associated timeout interval Refer to the discussion of IPCCont rol in the Network Interprocess Communication section of the NS ARPA 1000 User Programmer Reference Manual Call IPCRecv to verify that the connection referenced by the VC socket came up before trying to send again No recovery is possible IPCShutDown should be invoked to release the VC socket Consult your Network Manager for assistance in diagnosing the problem Not a VC socket The descriptor specified in the parameter reserved for VC socket descriptors did not describe a VC socket This error on TPCRecv indicates that all the data sent by the remote process has been delivered to the user and that the remote process has gracefully released this socket Cannot give The calling process attempted to give away one too many descriptors This problem may occur only after a calling process has given away several descriptors but those descriptors have not yet been gotten by other processes Illegal request The request code passed in an IPCControl request was not valid Illegal timeout The IPCControl or IPCSelect request invoked by the calling process specified a timeout value that was invalid Bad vector data length The calling process specified a data vector argument that contained a negative length field
45. or protocol handlers They are sent to the log file when the event class printed in the EventClass field of the log record header is Warning Class 3 Error Class 4 Disaster Class 5 or RsrceLim Class 6 Refer to the NS ARPA 1000 Maintenance and Principles of Operation Manual for a description of the different event classes The log record header and log message are explained below in Log Records and Messages Location Codes These codes are returned in the Location field of the log record header They are also sent to the log file by certain software modules procedures processes or protocol handlers when the event class printed in the EventClass field of the log record header is Warning Class 3 Error Class 4 Disaster Class 5 or RsrceLim Class 6 These codes are listed in this section according to the Entity printed in the Entity field of the log record header when they occur ASCII Log Messages These are ASCII messages that are printed to the log file Like the codes described above these messages are produced by certain software modules procedures processes or protocol handlers The ASCII Log Messages are listed in this section according to the Entity printed in the Entity field of the log record header when they occur Log Records and Messages The log file contains log records Log records consist of two parts e the first part is the log record header e the second part is the log message The log record
46. parameter was initialized with InitOpt The entry number referenced was either less than zero or was larger than the number of the last entry that the opt parameter had been initialized to accommodate Bad option data length The data length specified in the AddoOpt or ReadOpt call was invalid Bad option total InitOpt was invoked specifying that the number of eventual entries to be placed into the opt parameter would be either fewer than zero or greater than the maximum possible number of opt entries One or both of the following actions may be taken 1 Wait for a NetIPC process to terminate When a NetIPC process terminates its user record is released or 2 ask the System Manager to configure more user records into the system One or both of the following actions may be taken 1 Wait for one of the NetIPC processes to terminate when a NetIPC process terminates its resource number is released back to the operating system or 2 ask the System Manager to configure more resource numbers into the system so that more NetIPC processes can be accommodated One or both of the following actions may be taken 1 Verify that the opt parameter has been initialized with the intended bounds 2 verify that the intended entry number is the one being referenced Verify that the value passed was the intended value One or both of the following actions may be taken 1 Verify that the value passed for the event
47. purging it This is an NS ARPA internal error Had trouble overwriting the This error requires HP next pointer field of a stored notification Nodal Registry database entry This is an NS ARPA internal error Deleting the local node s entry This is a warning only from the Nodal Registry is not allowed Could not read in from DSAM This error requires HP the header of a Socket Registry notification reply message This is an NS ARPA internal error 6 60 Logging Codes and Messages 1401 Had trouble appending a This error requires HP preamble record to a notification connect site path report in DSAM This is an NS ARPA internal error 1402 The Memory Manager would not This error requires HP allow the space to be used for notification storing a connect site path report to be charged against the Socket Registry s special socket This is an NS ARPA internal error 1403 Could not read in a Socket This error requires HP Registry reply message from notification DSAM that PXP had tried to deliver This is an NS ARPA internal error 1404 Could not deallocate the mbuf This error requires HP that contained a Socket Registry notification reply message This is an NS ARPA internal error 1405 A Socket Registry reply This error requires HP message was received from the notification remote peer but could not be interpreted The message may have been corrupted in transit This is an NS ARPA internal err
48. reports 6 57 eee Sea eee 4000 A problem was encountered This error requires HP while trying to read the notification preamble portion of a path report from DSAM This is an NS ARPA internal error 4001 A problem was encountered This error requires HP while trying to dispose of a path notification reported stored in DSAM This is an NS ARPA internal error 4200 An attempt to put an event This error requires HP message into DSAM failed This notification is an NS ARPA internal error 4201 An attempt to append an event This error requires HP message to a root socket failed notification This is an NS ARPA internal error 4202 An attempt to read in an event This error requires HP message that was queued ona notification root socket failed This is an NS ARPA internal error 4401 An attempt to put an event This error requires HP message into DSAM failed This notification is an NS ARPA internal error 4402 An attempt to append an event This error requires HP message to a root socket s notification inbound sbuf failed This is an NS ARPA internal error 4403 Encountered a root socket in an This error requires HP unknown state This is an notification NS ARPA internal error 4500 Encountered a root socket in an This error requires HP unknown state while trying to notification deallocate it This is an NS ARPA internal error 4501 Encountered a call socket ina This error requires HP unknown state
49. returned in the result parameter of Remote Process Management RPM calls These codes are also printed to the log file when the Entity is HP RPM Refer to the HP RPM Log Message Codes subsection in the Logging Codes and Messages section of this manual Many errors are invalid parameter errors Refer to the Remote Process Management section of the NS ARPA 1000 User Programmer Reference Manual to check the parameters RPM Error Codes The call was successful No action is necessary 2 3 1 2 26 Numeric Error Codes Network is down NS ARPA is either down going down or not completely up Illegal name length The length in one of the following parameters is either too short or too long nodelen must be between 0 and 50 bytes characters namelen must be between 1 and 64 bytes characters in RTE loginlen must be between 0 and 16 bytes characters in RTE passwdlen must be between 0 and 14 bytes characters in RTE Illegal flags An unimplemented flag is specified in either RPMCreate or RPMControl For RPMCreate valid flag bits are bits 1 30 and 31 For RPMControl flags must be set to zero Illegal option or request code An illegal option code was specified in an RPMCreate call or an illegal request code was specified in an RPMControl call Bring up NS ARPA Correct the length parameter in the RPM call RPMCreate RPMControl or RPMKil1 Correct the flags parameter in the R
50. returned to the origin node This error occurs when a reply Try again possibly an error reply cannot be delivered back to the origin node XXXXxX name of program Try again reporting the error yyyyy stream code zzzzz sequence number of the request or reply being processed when the error occurred pppppp P register address where the program detected the error you will need listings aaaaaa contents of the A register when the error occurred bbbbbb contents of the B register when the error occurred Rerouting has found the Check the communications link communications link status has changed too frequently It has disabled the link to increase communications stability Alphanumeric Error Messages 3 19 DS 3000 Request Rejected System Console Messages DS 3000 Request Rejected System Console Messages DS 3000 request rejected class I O error aabb DS 3000 reques cont reques after timeout rejected rec d DS 3000 request error sending aabb rejected reply DS 3000 request holding class missing rejected data DS 3000 request illegal class stream rejected and DS 3000 request rejected illegal DS 1000 stream number in reply DS 3000 request rejected local node is quiescent DS 3000 request rejected monitor unavailable or not enabled DS 3000 request rejected no available class numbers DS 3000 request rejected no available TST entr
51. seii ded wes 3 17 DS 3000 Request Rejected System Console Messages 02sec eee 3 20 Miscellaneous System Console Messages io io i sceie dco aca swine cin Ved 4 ees oes 3 22 Miscellaneous Alphanumeric Error Messages 00 0 0 c cece cece ee eee ees 3 24 11 Chapter 4 Program Specific Error Messages TELNET User Etror Messages q2iecscie iaer pasians ana Peech Gers sees 4 2 FIP User Error Messages scence actin ieee ieee re CN oes chee 4 4 DSCOPY amp NET Error Messages cereiro riirii Bese s eee wate sie e 4 8 IDSLIN Bion Messages o srs oss nee see a RE ts E AE E E EEA R ede swig 4 17 DSMOD Error Messages crecsisreraces rira eae he EE INE E E E EEA 4 19 MVCP3 Error Messages ossi cussrescids esere tese reto wee ees ea bea CE eee EY 4 21 Nodal Registry Error Messages lt irerirss crostate tut Tuan eee co i ENESE R E SENATA 4 22 NSINF Error Messages purini nr eaa a E hee A E E EEE EE 4 27 NSINIT Error Messages suc t eriee mines ee heen e a a a e a e a 4 30 REMAL Efrof Messages 2cc6t es cadens eee ed etna ieee ene eee eres eae 4 58 RMOTE Error Mes ag s 5 056 0 nad ys rerin g HV RGN MER ee MARES ade R Re ERE NE Oe ae 4 59 Chapter 5 Tracing Error Messages INS TING Error Messages nigarria ey a Gases es eee ed Gn DE we 5 1 BRTRC Error Messages 25 ocene cee eaoeeeoeeuiees aE S EEEE E SEE ees 5 2 EMTRC Error Messages lt 1 c lt s ed eecege ew reai niun i aaa cee dose Aa 5 3 FMTRC First Return Parameter Values 5 60 06 tie ebb
52. sequence DEXEC An illegal request code was detected EXECW An illegal request code was detected Alphanumeric Error Messages See the explanation of DS05 0 for more information This should rarely occur unless all routes to the node are down However if it does occur increasing the number of retries in the NSINIT answer file may solve the problem The Message Accounting retry count is specified with the response to Enter MA retry limit during NS ARPA initialization If this error occurs frequently increase the timeout values and retry count Note that this error differs from the DSO5 0 error in that Message Accounting has signalled the timeout 1 Load monitor online use DSMOD s S command to schedule it and retry 2 icode parameter value not defined for remote EXEC calls Check this parameter and try again 3 Programs must restart sessions on the HP 3000 by calling HELLO 4 A dummy call to D3KMS in the main will cause this collection of routines to be appended to the main and eliminate the problem of overwritten process numbers Examine the CALL statement and make appropriate corrections EXECM Examine the CALL statement and make appropriate corrections Examine the CALL statement and make appropriate corrections 3 5 DS07 0 ERROR SYSTEM TABLE DSO7 1 INPUT OUTPUT CONVERTERS INCNV OTCNV REQUIRED BUT NOT SCHEDULED DSO7 2 INCONSISTENT LEVEL NUMBE
53. station address in the answer file as described above and rerun NSINIT Rerun NSINIT Enter less than four IEEE 802 3 LUs for this node If you are using NSINIT interactively enter an individual station address If you are using NSINIT interactively correct the station address in the answer file as described above and rerun NSINIT If you are using NSINIT interactively enter the IP address of any node on the destination network If you are using NSINIT with an answer file correct the IP address in the answer file as described above and rerun NSINIT If you are using NSINIT interactively enter a valid IP address If you are using NSINIT with an answer file correct the IP address in the answer file and rerun NSINIT 4 49 622 NSINIT GT Gateway IP Address not specified 623 NSINIT GT Invalid Gateway Address Format is n n n n 624 NSINIT GT Invalid Maximum Hop count 625 NSINIT GT Hops count out of range Range is 1 100 627 NSINIT LIPAD Duplicate Local IP Address 628 NSINIT GT Duplicate Destination Network 629 NSINIT Set Elements EnterCritical Failed 630 NSINIT DCN Duplicate Network or Node address 4 50 The IP address of the gateway to be used for all traffic to the destination network was not specified A node on one of the directly connected networks DCN must be specified as the gateway to be used Th
54. stopped while active NSINIT subordinate program prognum received an invalid routine index Subordinate program numbers 1 through 3 refer to NSPR1 through NSPR3 program number 4 refers to NSPARS NSINIT subordinate program prognum received an improper runstring This error may be returned if a program other than NSINIT scheduled the subordinate program Subordinate program numbers 1 through 3 refer to NSPR1 through NSPR3 program number 4 refers to NSPARS Program Specific Error Messages Rerun NSINIT If the error persists reboot your system and try again If rebooting does not solve the problem this error requires HP notification Rerun NSINIT If the error persists reboot your system and try again If rebooting does not solve the problem this error requires HP notification Refer to the accompanying RTE error code for more information and rerun NSINIT If the error persists reboot your system and try again If rebooting does not solve the problem this error requires HP notification Make sure the subordinate program is the correct program and rerun NSINIT If the error persists reboot your system and try again If rebooting does not solve the problem this error requires HP notification Refer to the accompanying RTE error code for more information and rerun NSINIT If the error persists reboot your system and try again If rebooting does not solve the problem this error requires HP notification
55. string Verify that the source computer name is correct that the source computer is connected to the network that the source node has its own entry in the Nodal Registry that there are sufficient resources to establish a connection or that NFT has been initialized on the source computer Also refer to the qualifying error string Verify that the target computer name is correct that the target computer is connected to the network that there are sufficient resources to establish a connection or that NFT has been initialized on the target computer Also refer to the qualifying error string Verify that there are sufficient resources on the source computer and try again 4 11 Insufficient resources at target computer NS NFTERR 8 Source file not found NS NFTERR 9 Target file not found NS NFTERR 10 Transfer terminated by user NS NFTERR 11 Requested data type refused NS NFTERR 14 Requested record type refused NS NFTERR 15 Requested record size refused NS NFTERR 17 Requested file size refused NS NFTERR 18 Conflicting attributes or options NS NFTERR 19 4 12 There are insufficient resources at the target computer to copy the file or files Refer to the qualifying error string The source file does not exist or the name was misspelled The target file does not exist or the name was misspelled Acknowledges the user s abort or cancel request The us
56. terminated DS_DeallocDsam returned an error when it attempted to deallocate Distributed System Available Memory DSAM DSAM was not deallocated The value of the Distributed System Available Memory DSAM state word is undefined The value is returned in value The value of the NS ARPA state word in Distributed System Available Memory DSAM is undefined The value is returned in value The value of the protocol segment word of the NS ARPA state word in Distributed System Available Memory DSAM is invalid This value is returned in value NSINIT received a parity error in Distributed System Available Memory DSAM when it called DeallocateDsam to deallocate DSAM DSAM was deallocated NSINIT received an error during startup shutdown An NSINIT error code is provided in errornum Program Specific Error Messages This is an informational message No action is required The following actions may be taken 1 Disregard the message and start up NS If problems are encountered this error requires HP notification 2 Reboot your system and rerun NSINIT Rerun NSINIT If the error persists reboot your system and try again If rebooting does not solve the problem this error requires HP notification Shut down NS ARPA or reboot Shut down NS ARPA After shut down some resources may still be allocated because there may be a problem with Distributed System Available Memory DSAM If this is the case re
57. that the producer program is on the PROGRAMS directory or in the FMGR file domain Refer to the accompanying multiuser error muerror for additional information Refer to the NetIPC error code for more information Refer to the NetIPC error code for more information Refer to the accompanying multiuser error muerror for additional information 509 xx XK Xx The NFT monitor NFTMN This error requires HP received a fatal internal error notification 6 14 Logging Codes and Messages 510 ipcerror 0 0 The NFT monitor NFTMN Refer to the NetIPC error for received a NetIPC error more information ipcerror when it attempted to create a call socket with IPCCreate and was therefore unable to initialize properly 511 ipcerror The NFT monitor NFTMN Refer to the NetIPC error code received a fatal NetIPC error for more information ipcerror when it called TPCSelect 512 muerror The NFT monitor NFTMN was Refer to the accompanying unable to attach to a session multiuser error muerror for additional information Logging Codes and Messages 6 15 Memory Manager Log Message Codes 1000 1999 Memory Manager Log Message Codes 1000 1999 1001 1002 1003 1004 1005 1006 1007 Memory Manager When this error occurs at initialization time it indicates that the configured size of DSAM is too small for the tables described in the NSINIT answer file When this error occurs at any other time it indica
58. the error occurred Program Download Console Messages Error messages may also be printed to system LU 1 when an error occurs during a program download These errors are printed in the following format DOWNLOAD OF FILE file name lu type AM AT DAY nnn hr min sec ASCII message PM The following table lists the error messages that are returned to the ASCII message parameter described above Alphanumeric Error Messages 3 15 Program Download Console Messages FAILED CKSM ERR FAILED CLASS ER FAILED LINE ERR WAS ABORTED PROGL calculates a checksum on each record read before sending it to the remote A class l O error occurred on the attempt to transmit a record not a transmission error An error occurred in trying to re queue a record back onto the transmission line after a transmission error has occurred PROGL simply delays transmission on all lines for 200 ms if an error occurs on any line A new download request arrived before completing the previous one This may occur if the operator restarts the CBL sequence or if the remote program load feature is enabled a power failure occurs during a download RPL restarts on power recovery If the file is not absolute binary or has been corrupted the check will fail and this message will be printed This would be a catastrophic error most likely an indication of corrupted tables in RES or the RTE class table This would be a catastrophic erro
59. to shutdown is an internal error NS ARPA If the error persists reboot your system If rebooting does not solve the problem this error requires HP notification Logging Codes and Messages 6 27 HP ROUTER Log Message Codes 8000 8999 HP ROUTER Log Message Codes 8000 8999 8100 8101 8103 HP ROUTER All routes to the node are down HP ROUTER Link was not a ROUTER link HP ROUTER Path no longer exists HP ROUTER A bad NRV index was supplied by the ULP HP ROUTER No path exists to that node 6 28 Logging Codes and Messages Check your cables use NSINF to make sure the LU is enabled and check that NS ARPA is up on the remote nodes This error requires HP notification Check your cables and make sure NS ARPA is up on the remote nodes This error requires HP notification Make sure your initialization file has a router address for the node in the NRV Also make sure the IP address is correct HP TCP Log Message Codes 14000 14999 HP TCP Log Message Codes 14000 14999 teswessae Meaning Mim 14001 TCP No connection resource This is an informational code only The protocol will recover 14002 TCP Remote reject connection This is an informational error attempt only The protocol will recover 14003 TCP Connection was reset by This is an informational code remote only The protocol will recover 14004 TCP Keep alive timer expired This is an informat
60. too short or RPMControl or RPMKil1 too long nodelen must be between 0 and 50 bytes characters namelen must be between 1 and 64 bytes characters in RTE loginlen must be between 0 and 16 bytes characters in RTE passwdlen must be between 0 and 14 bytes characters in RTE 18003 xx xx XxX Illegal flags specified in either Correct the flags parameter in RPMCreate or RPMControl the RPMCreate or RPMControl For RPMCreate valid flag bits call are bits 1 30 and 31 For RPMControl flags must be set to zero 18004 xx XX xx Illegal option or request code Correct the option code in An illegal option code was RPMCreate or the request code specified in an RPMCreate Call in RPMControl or an illegal request code was specified in an RPMControl call 6 32 Logging Codes and Messages Illegal option format One of the Check the option format in the 18005 xx XX XX 18006 muerror xx XX 18007 XX XX XX 18008 XX XX XX following errors has occurred 1 The option code in the RPMCreate call is not in the correct order For example a Group 3 option code has been specified before a Group 2 option code The format of one of the options in the RPMCreate call is incorrect Invalid or missing login or password specified by the parent program A session could not be created for the child node Child program not found on child node The name of the child program specified in the RPMCreate Call is not found
61. updates that are included Periodi cally update packages are distributed which contain replacement pages to be merged into the manual including an updated copy of this printing history page Also the update may contain write in instructions Each reprinting of this manual will incorporate all past updates however no new information will be added Thus the reprinted copy will be identical in content to prior printings of the same edition with its user in serted update information New editions of this manual will contain new information as well as all updates To determine what manual edition and update is compatible with your current software revision code refer to the Manual Numbering File or the Computer User s Documentation Index The Manual Numbering File is included with your software It consists of an M followed by a five digit product number First Edition Feb 1986 oi ct beak dike daneg See oem ean Rev 2608 Update 1 ee eee eee May 1986 ic ceed cde ecceiat ad wae daa dom Rev 2626 Update 2 Oct 1986 a nane cgi aa EEA Rev 4 1 4010 Update 3 nananana Aug 1987 seccrirdiererirerat enii is Rev 5 0 5000 Second Edition Oct 1989 i ides thee ewes Rev 5 16 5016 Third Edition Aug 1991 erreme ai ieuainc eee Rev 5 24 5240 Fourth Edition DOC 1992 iiid anii ikae ee tata on Rev 6 0 6000 Fifth Edition NOV 1993 s cccc geet
62. when an error is detected in the NS ARPA software or it may be caused by an RTE scheduling error i e the correct copy of MMINIT was not scheduled The value for the size of the global table area is a constant This error message is returned when an error is detected in the NS ARPA software NSINIT has terminated value indicates the minimum DSAM Shareable Extended Memory Access SHEMA size for tables only You will receive this error message if MMINIT returns an invalid value to NSINIT This can occur for the following reasons 1 the wrong version of MMINIT was scheduled 2 there is a problem in MMINIT or 3 an error has been detected in the NS ARPA software NSINIT has terminated DS_SetupDsam found an error with the Shareable Extended Memory Access SHEMA partition The partition size returned is less than the size requested Palc did not detect the error NSINIT deallocated the SHEMA before terminating This error message is returned when an error is detected in the NS ARPA software Program Specific Error Messages Rerun NSINIT If the error persists reboot your system and try again If rebooting does not solve the problem this error requires HP notification Check that the correct version of MMINIT was scheduled and rerun NSINIT If the error persists reboot your system If rebooting does not solve the problem this error requires HP notification This error requires HP notification Th
63. 0 1 RPMCreate request message too long Bad parameter in opt array parameter One of the following problems has occurred in an RPMControl Call 1 The request code is not valid 2 The readdata Or wrtdata length is not correct One of the following problems has occurred in an RPMCreate call 1 The options are not specified in the correct order 2 More than one Group 2 option is specified 3 More than one Group 4 option is specified 4 The string specified in the FmpSetWorkingDir option is not a valid directory or has an illegal length must be 1 63 bytes 5 The option array has an illegal structure 6 The length of the string being passed option 20000 is greater than 256 bytes or is a negative value 7 The length of one of the options is invalid Invalid node name The nodename specified in the RPM call is not valid or is unknown to NetIPC same as NetIPC error code 40 No RPM parameter string The RPMGet String Call has been invoked by the child program to retrieve the parameter string passed to it by the parent program but no parameter string exists possibly because all parameter strings have already been retrieved in previous RPMGet String Calls The program issuing the RPMGetString call is nota child program scheduled by the RPM Monitor Illegal string length The length of the parameter string for the pass string option 20000 in RPMCreate s negative This error message is not us
64. 000 moving DSAM to unaffected memory or replace the defective memory This error requires HP notification This error requires HP notification If this error occurred in the event log and the system is busy no action is necessary However if throughput is significantly affected or if connections are lost then the size of DSAM should be increased If this error occurred in the event log and the system is busy no action is necessary However if throughput is significantly affected or if connections are lost then the size of DSAM should be increased This error requires HP notification 1025 1026 1027 1028 1029 1030 1031 1032 1033 Memory Manager A table scan failed to find the requested element This is an NS ARPA internal error Memory Manager A linked list scan exceed the maximum list length This is an NS ARPA internal error Memory Manager During initialization NSINIT passed a bad MinC1Num parameter to DSSetUpDSAM This is an NS ARPA internal error Memory Manager The size of the table area in DSAM requested by the NSINIT answer file is larger than can be provided This is an NS ARPA internal error Memory Manager The statically mapped area requested by the NSINIT answer file is larger than can be implemented Memory Manager The total size of DSAM requested by the NSINIT answer file is larger than can be provided greater than 2 Mbytes Memory Manager A p
65. 000 IV Compatible Services calls these include PTOP calls RFA calls and certain utility subroutines The err error codes may also be returned to the A and B registers after a DEXEC call or to the current log device through REMAT You should also refer to this section for NetIPC error codes Remote I O Mapping errors codes received through the program IOMAP and Remote Process Management RPM error codes Alphanumeric Error Messages Alphanumeric error messages are described in Section 3 These errors are categorized as Subsystem Errors Messages System Console Error Messages and Miscellaneous Error Messages You should refer to this section whenever an alphanumeric message is printed to the current log device Program Specific Error Messages The program specific error messages are described in Section 4 Although these messages are also alphanumeric unlike those described in Section 3 each set of messages listed in this section is used exclusively by a certain program As a result these errors are organized according to the name of the program that generates them Many of these errors are returned by programs described in the NS ARPA 1000 Generation and Initialization Manual You should refer to this Introduction 1 1 section whenever you receive an error while running DSCOPY DSLIN DSMOD MDFCL D FCL MVCP3 NRINIT NRLIST NSINIT NSINEK REMAT RMOTE TELNET and FTP Tracing Error Messages Error messages returned by the NS AR
66. 0306 xx 0 0 TELNET user program received An internal TELNET error has a Driver Rejects Call error from occurred This error requires HP the terminal interface notification 20307 xx 0 0 TELNET user program received The LU of the terminal being an LU is locked error from the accessed is already locked and terminal interface in use by another program Wait for the LU to be released Then run TELNET again 20308 xx 0 0 TELNET user program received The LU of the terminal being an LU is down error from the accessed is down Use the UP terminal interface lu command Then run TELNET again Logging Codes and Messages 6 39 HP TN Log Message Codes for TELNET Server 20000 20999 20501 0 xx yy 20502 xx 0 0 20503 xx 0 0 20504 0 xx yy 20505 0 xx yy ipcerr cd 0 20507 0 0 0 20508 0 0 0 TELNET server program ran out of internal FIFO buffer space 20509 xx 0 0 20510 xx 0 0 6 40 TELNET server program received an illegal I O request from the pseudo terminal driver not read write control or abort TELNET server program has encountered an error from an internal NetIPC InitOpt call TELNET server program has encountered an error from an internal NetIPC Addopt call TELNET server program received a new I O request before it could complete the previous request TELNET server program has received an I O control request with a subfunction that is not recognized by TNSRV TELNET server p
67. 1 Check the socketkind and protocol parameters for the correct values 2 default the protocol value to zero thus letting the system decide which protocols best support the referenced socket kind No memory The system does not have enough memory available to support the request This error can occur when you attempt to create a new call socket Call sockets require that a certain amount of memory be allocated from DSAM Messages queued option error An error was detected in the messages queued option of the opt parameter Illegal TCP address A TCP address was specified that was out of range This error can occur when using the IPCCreate Or IPCDest call Socket limit exceeded The calling process attempted to gain access to a new socket descriptor or path report descriptor even though it already owned the maximum permissible number of descriptors No path records The calling process tried to obtain a destination descriptor via IPCLookUp but the system didn t have enough storage space in which to save the addressing information that would have been bound to the path report descriptor The addressing information is stored in DSAM in the form of path records One or more of the following actions may be taken 1 Ask your System Manager to configure a larger DSAM memory allocation 2 release some of the sockets or path report descriptors that are not currently being used 3 if applicable reduce the s
68. 10 IP The Virtual Network Address Use only the HP DSN domain Domain is not known to IP 3111 IP Requested PID was not Such protocol stacks are not found While parsing a path supported report a protocol unknown to IP was encountered by the IP routines Logging Codes and Messages 6 21 3112 3113 3114 3115 3117 3121 3122 3123 3124 6 22 IP Event Message received is unknown to this IP event handler Another protocol has passed a message to IP that IP does not understand IP Referenced path record is on the free list This is an internal error indicating inconsistent data structures Cleanup is done by NS ARPA to remove the inconsistency IP Referenced ANH record is on the free list This is an internal error indicating inconsistent data structures Cleanup is done by NS ARPA to remove the inconsistency IP ANH record could not be allocated IP IP Header referenced in event message could not be retrieved from DSAM IP Retrieval of GT Gateway Table record by reference failed IP Outbound protocol event handler can not handle the inbound event message received This error indicates that internal inconsistences exist IP Inbound protocol event handler can not handle the outbound event message received This error indicates that internal inconsistences exist IP The Virtual Network Address supplied is of the wrong domain This error indicates that internal in
69. 1000 May represent data corruption in SAM or mismatched version of INPRO and one of the drivers INPRO dropped the affected message The xx field of the log record header contains the link type code from the message The log message contains the event message that INPRO would have sent to the link interface The first word is meaningless Logging Codes and Messages No action is necessary because the HP protocols can retransmit lost messages However if enough messages are dropped in this way so that network functioning is impaired a shutdown and restart of NS ARPA or a reboot of the system may be necessary to clear the condition If these actions do not solve the problem notify your HP field Office If too many messages are lost in this way more space should be allocated for DSAM at initialization time If this problem repeats shutting down tracing with BRTRC and then restarting NSTRC may correct it If not this error requires HP notification Verify that all software is of the same revision Especially check revisions of datacomm drivers and the NS ARPA 1000 code appended to INPRO check load map You may check the update time stamps on nssys_cds 1ib nslib_cds lib inpro rel and the relocatable for the driver affected If all software is same revision the problem may be corruption in SAM or in the driver Reboot If versions match and rebooting does not solve the problem this log is an internal error
70. 105 2300 2306 The Memory Manager rejected an attempt to write a node name string into DSAM The string would have been stored in an mbuf where it could have been later retrieved by Probe This is an NS ARPA internal error Could not write context information for an IPCDest transaction into an mbuf in DSAM where it was to be saved This is an NS ARPA internal error Could not construct a connect site path report to describe one of the local node s call sockets This is an NS ARPA internal error Unable to put a Socket Registry reply message into DSAM prior to asking PXP to transmit it This is an NS ARPA internal error Encountered an unexpected problem obtaining domain information while constructing a connect site path report template This is an NS ARPA internal error TCP had trouble adding its part to a connect site path report template This is an NS ARPA internal error IP had trouble adding its part to a connect site path report template This is an NS ARPA internal error IEEE 802 had trouble adding its part to a connect site path report template This is an NS ARPA internal error Ethernet had trouble adding its part to a connect site path report template This is an NS ARPA internal error A reference to an unknown protocol was encountered while constructing a connect site path report template This is an NS ARPA internal error Logging Codes and Messages This error requires HP notif
71. 1OXX Error Messages a a L RTE 10xx Errors for description I000 INVALID CLASS RQUE Source class Correct call parameters and try Ae Tcie ION ee is zero or greater again than maximum class number IO01 1 IMPROPER DEXEC A parameter error has Correct your DEXEC call MISSING OR TOO MANY been detected by the DEXEC parameters and try again PARAMETERS intrinsic I001 2 IMPROPER OR EXECM A parameter error has Correct your DEXEC call MISSING PARAMETERS been detected by EXECM parameters and try again I001 4 PARAMETER RQUE Call parameters are Correct call parameters and try MISSING INVALID OR missing or invalid or the search again CLASS SEARCH FAILED for the class header failed RQUE Illegal logical unit Correct LU and try again number I004 1 IMPROPER DEXEC a User buffer length Correct call parameters and try BUFFER SPECIFICATION specification gt 512 words b In again a write read request the write length is greater than the read length I004 4 INVALID BUFFER RQUE An illegal buffer was Correct call parameters and try SPECIFICATION specified Extends beyond again or check SAM usage RT BG area or not enough SAM to buffer the request I007 2 DRIVER EXECM A request issued by Correct call parameters and try REJECTED REQUEST EXECM in response to a user again call to the DEXEC intrinsic has resulted in a rejection by the driver IO10 4 PROGRAM RQUE
72. 2 ipcerr xx xx FTP encountered a Network Refer to the NetIPC error later in error this section for more information 21004 xx XX XX A binary file transfer with Make sure the source file is a destination file other than file disk image of RTE file If the file type 1 2 or 6 failed because the is not an RTE file transfer it to data did not match the disk type 1 file image of an RTE file HP ARM Log Message Codes 24000 24999 HP ARM Log Message Codes 24000 24999 24016 An ARM transaction has been Configure more ARM PCB initiated either by IP or by the records using NSINIT Socket Registry while all of ARM s path records were in use 24111 This is an NS ARPA internal This error requires HP error notification 24201 The ARM protocol handler This error requires HP received an unexpected type of notification event message This is an NS ARPA internal error 6 42 Logging Codes and Messages HP ARP Log Message Codes 25000 25999 HP ARP Log Message Codes 25000 25999 TogMessage Meaning Action 25001 This error indicates that the This error requires HP Memory Manager has returned notification an error The Memory Manager error and the location in the code are in the accompanying fields This is an NS ARPA internal error 25002 The length of an ARP message This is a warning If the error received from the network is an persists this error requires HP invalid length notification 25003 The ARP mes
73. APE command Check syntax and try again y is the interrupt character TELNET ERR 10 Illegal interrupt character TELNET ERR 11 I is the escape character TELNET ERR 12 Mode change unavailable TELNET ERR 13 Already character TELNET ERR 15 Unknown parameter TELNET ERR 16 Ambiguous parameter TELNET ERR 17 No connection open TELNET ERR 18 Node name is too long TELNET ERR 19 Use HELP on the ESCAPE command Check syntax and try again The interrupt character was specified in the ESCAPE command instead of an escape character Use HELP on the INTERRUPT command Check syntax and try again An illegal character was specified for the interrupt character in the INTERRUPT command The escape character was Use HELP on the INTERRUPT specified in the INTERRUPT command Check syntax and command instead of an interrupt try again character A MODE command was entered Use the OPEN command to when there is no remote connect to the remote system connection open first Use HELP on the MODE command Check syntax and try again Use HELP on the MODE command Check syntax and try again A line MODE command was entered and the transmission mode is already in line mode A character MODE command was entered and the transmission mode is already in character mode The parameter entered is Use HELP on the command unknown for the command Check syntax and try again
74. EVICE The RTE system error message LUO1 LUO2 LUO3 may appear in the xxxx field above NRV POSSIBLY CORRUPT Nodal Routing Vector contains Use DSMOD to correct the NRV erroneous information or shut down NS ARPA 1000 using NSINIT and reinitialize REROUTING TABLE POSSIBLY Table containing the link vector Shut down NS ARPA 1000 using CORRUPT information has become corrupt NSINIT and reinitialize RQ 4 REQUEST CODE IS RQUE The code parameter Check code value INVALID does not equal 17 18 19 or 20 or the no abort bit is not set and the request code is an inappropriate negative value 3 24 Alphanumeric Error Messages Program Specific Error Messages The following NS ARPA 1000 errors are categorized according to the program that returns them These program specific errors include TELNET Error Messages These ASCII error messages are returned to the current list device when an error is encountered by TELNET TELNET is covered in the NS ARPA 1000 User Programmer Reference Manual FTP Error Messages These ASCII error messages are returned to the current list device when an error is encountered by FTP FTP is covered in the NS ARPA 1000 User Programmer Reference Manual DSCOPY amp NFT Errors These error and warning messages are returned to the current list file or device when DSCOPY is used interactively The numeric error codes not the warning codes associated with these messages are returned to the DSCOPY
75. EXCEEDED DSO5 0 TIMEOUT HOP COUNT REQUEST NRV at node reporting error does not contain an entry for the destination node Possible causes 1 If local processing request NRV did not contain an entry for local node 2 NRV built improperly either at local node or intervening node 3 Remote file is open or a slave program is scheduled without proper initialization 4 Programming error The rerouting software has determined that all routes to the destination node are down and the message cannot be transmitted Note that if 12665 DVA65 links are included in the network they are not automatically restored to service Message has exceeded the maximum number of store and forwards specified at NS ARPA 1000 initialization time or as modified by the DSMOD T command MAST This error can occur for a number of reasons 1 A slave monitor may be tied up for too long and there is no message accounting in the system message accounting will cause a DS05 1 2 The master timeout may be too small or the destination node may be loaded heavily or generated improperly 3 The reply could not be sent back due to an irrecoverable transmission error in the reply 4 The response may fail to be returned due to an error in the NRV in some node involved in the reply path 3 4 Alphanumeric Error Messages Possible solutions are 1 Shut down edit the answer file and re initialize 2 Use DSMOD a
76. HP not be allocated for the number notification of IP Appropriate Next Hop ANH records required Internal error Table space could This error requires HP not be allocated for the number notification of LAN table records required A response other than E NE or the default was entered for this parameter If you are using NSINIT interactively enter E NE or default the parameter If you are using NSINIT with an answer file correct the answer file as described above and rerun NSINIT Rerun NSINIT and enter at least one local IP address An IP address was not entered for the local node Rerun NSINIT and refer to an IEEE 802 3 link The driver type for the specified IEEE 802 3 link is not 67 An error occurred while reading Refer to accompanying error the driver type from IEEE 802 3 messages for more information LU 1u Correct the problem with the LU NSINIT or a subordinate program received an error on CLRQ when communicating and rerun NSINIT If the error between subordinate programs persists reboot your system An RTE error code is returned in and try again If rebooting does aregister and bregister not solve the problem this error requires HP notification Refer to the accompanying RTE error code for more information NSINIT or a subordinate program encountered a class I O error An RTE error code is returned in errornum Refer to the accompanying RTE error code for more infor
77. LA eackann NS ARPA 1000 Error Message and Recovery Manual Software Technology Division 11000 Wolfe Road Cupertino CA 95014 9804 Manual Part No 91790 90045 Printed in U S A November 1993 E1193 Fifth Edition NOTICE The information contained in this document is subject to change without notice HEWLETT PACKARD MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THE MATERIAL INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE Hewlett Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing performance or use of this material Hewlett Packard assumes no responsibility for the use or reliability of its software on equipment that is not furnished by Hewlett Packard This document contains proprietary information which is protected by copyright All rights are reserved No part of this document may be photocopied reproduced or translated to another language without the prior written consent of Hewlett P ackard Company RESTRICTED RIGHTS LEGEND Use duplication or disclosure by the Government is subject to restrictions as set forth in subparagraph c 1 ii of the Rights in Technical Data and Computer Software clause at DFARs 252 227 7013 Copyright 1986 1987 1989 1991 1993 by Hewlett Packard Company Printing History The Printing History below identifies the edition of this manual and any
78. LE COPY3K ICOPY3K IS FILE TYPE type NOT TYPE 1 FMP ERROR errorno COPY3 FMP ERROR errorno OPENING COPY3 sc cr RROR errorno NG COPY3K PUB SYS RROR errorno NG COPY3K PUB SYS IPE ERROR errorno WRITING COPY3K PUB SYS A record in the COPY3 file specified in the MVCP3 runstring is not 128 words long The COPY3 file specified in the MVCP3 runstring is not an FMP type 1 file MVCP3 encountered the FMP error errorno while trying the read COPY3 MVCP3 encountered the FMP error errorno while trying to open COPY3 MVCP3 encountered the MPE error errorno while trying to close COPY3K PUB SYS MVCP3 encountered the MPE error errorno while trying to open COPY3K PUB SYS MVCP3 encountered the MPE error errorno while trying to write COPY3K PUB SYS Program Specific Error Messages The COPY3 file included in the NS ARPA 1000 product has records that are all 128 words long Check to make sure the correct file is available on a FMGR cartridge The COPYS3 file included with the NS ARPA 1000 product is a type 1 file Check to make sure the correct file is available on a FMGR cartridge Refer to the appropriate FMP error code for an explanation of this error Refer to the appropriate FMP error code for an explanation of this error See the appropriate FS 3000 error code for an explanation of this error See the appropriate FS 3000 error code for an explanation of this erro
79. Let DSCOPY choose the data type by not specifying a data type option and try again Let DSCOPY choose the record type by not specifying a record type option and try again Let DSCOPY choose the record size by not specifying the RSIZE option and try again Let DSCOPY choose the file size by not specifying the FSIZE option and try again Specify FIXED to make the records fixed length reset the file equation or specify attributes that agree with the file equation Target record size is invalid NS NFTERR 20 Target file size is invalid NS NFTERR 21 Target file already exists NS NFTERR 22 Need password to access source file NS NFTERR 23 Need password to access target file NS NFTERR 24 Out of disk space NS NFTERR 25 Connection to source computer went down NS NFTERR 26 Connection to target computer went down NS NFTERR 27 Unable to purge target file NS NFTERR 28 Invalid target file name NS NFTERR 29 The user defined record size RSIZE value is out of the acceptable range The user defined file size FSIZE value is out of the acceptable range The target file exists and neither APPEND REPLACE or OVERWRITE was specified The source file could not be accessed without the proper password The target file could not be accessed without the proper password The target computer is out of disk space An error was detected on the connection to the c
80. MP Log Message Codes 26000 26999 ICMP Log Message Codes 26000 26999 26001 ICMP received an error from This error requires HP Memory Manager while trying to notification append data in DSAM The Memory Manager error is in the xx field This is an NS ARPA internal error 26002 A bad checksum of an ICMP If the error persists this error packet occurred requires HP notification 26003 ICMP attempted to clean up This error requires HP after it received an error from notification Memory Manager but failed This might indicate that DSAM or SAM is corrupt 26004 ICMP cannot satisfy a Verify that the host is in the connection request to a given Nodal Registry If the host is host from PING program there this error requires HP notification 26005 A packet has arrived fora PING This error requires no further program that has already action terminated 26006 ICMP cannot read the header of This error requires HP an ICMP packet The error notification returned by Memory Manager is in the xx field This is an NS ARPA internal error 26007 While trying to update the This error requires HP checksum of an ICMP packet notification ICMP received an error from Memory Manager The Memory Manager error is in the xx field This is an NS ARPA internal error 26008 Memory Manager returned an This error requires HP error when ICMP attempted to notification move data from DSAM to PING data space The Memory Manager error is in the x
81. N TIME DSO05 2 TOO MANY RETRIES BY MESSAGE ACCOUNTING DS05 3 TIMEOUT SIGNALED BY MESSAGE ACCOUNTING DS06 0 ILLEGAL REQUEST OR MONITOR NOT ACTIVE DS06 1 THE APPENDED ROUTINE DEXEC HAS DETECTED AN ILLEGAL OR MISSING PARAMETER IN THE CALLING SEQUENCE DS06 2 ILLEGAL REQUEST CODE OR FUNCTION NOT SUPPORTED DS06 3 ILLEGAL REQUEST CODE OR FUNCTION NOT SUPPORTED The Message Accounting software confirmed delivery of the request at the destination node but the reply had not arrived by the time the Master Timeout expired The maximum number of Message Accounting retries have been attempted and the message has not been successfully received by the destination node An acknowledge has not arrived in time and Message Accounting has declared a timeout error This error is reported by programs in the destination node Causes may include 1 Either the NS ARPA monitor which services the request is not active or the request has been found illegal 2 Unacceptable DEXEC call 3 An HP 3000 link has gone down and come up again Programs using the previously valid process numbers receive the DS06 error because the process number is now invalid 4 If D3KMS is appended to a segment rather than the main the process number will be overlaid when the segments swap causing the use of an invalid process number DEXEC An illegal or missing parameter was detected in the calling
82. N will reschedule INPRO after performing all possible cleanup The invalid class number is printed in the xx field of the log record header This is an NS ARPA internal error Logging Codes and Messages If this condition persists NS ARPA must be shutdown and reinitialized If shutdown and reinitialization do not solve the problem this error requires HP notification 6 47 6 48 INPRO received an error indication in the DVT status word returned along with the write completion of a Class I O request The xx field of the log record header contains the error code field from the DVT status word and the yy field contains the entire DVT status word This is an NS ARPA internal error INPRO was unable to allocate space in DSAM for an incoming message If the transport is TCP HP PXP or the DS 1000 IV Compatible Services transport with Message Accounting the message will be retransmitted and will probably be accepted A Memory Manager error code is printed in xx field of the log record header INPRO tried to requeue a message to the message tracing program NSTRC or to the interface protocol monitor IFPM but the class number used was rejected by the Class 1 O system The xx field of the log record header contains the class number and the yy field contains the error indication from REQUE This is an NS ARPA internal error INPRO received a message which appeared to be from a link type not supported by NS ARPA
83. NK __ Improper initialization of labeled common during initialization or QUEX was improperly loaded QUEX TCB NOT FOUND POSSIBLE TIMEOUT CLASS XXXX STREAM xxxx FROM ID xx TO ID QUEX has received a reply for which there is no outstanding master TCB The reply was discarded XX QUEX TRACING ERROR aaaa QUEX Got the indicated ASCII error message aaaa when an attempt to write a trace record was made The status of tracing is set to down See LOG3K gt gt QUEZ EXPECTS PSI LINK Improper initialization of labeled common during initialization or QUEZ was improperly loaded 3 22 Alphanumeric Error Messages See specific error code Contact your Network Manager Increase the master timeout specified at NS ARPA initialization See specific error code Contact your Network Manager RECV D LEVEL yy MSG FROM NODE XXXXX ROCNV BAD BUFFER MSG FLUSHED ROCNV NO ROOM IN 3K LU TABLE FOR X 25 VC INCNV Node received message of higher format level than level of the node RQCNV The driver passed RQCNV a bad message The Contact Network Manager message was flushed Increase the number of X 25 pool LUs specified during NS ARPA initialization An incoming X 25 connection arrived from the HP 3000 but there was not enough room in the HP 3000 LU table for the new entry Alphanumeric Error Messages 3 23 Miscellaneous Alphanumeric Error Messages The followi
84. NS ARPA internal error Unable to store a Probe gateway reply message into a DSAM mbuf prior to transmission This is an NS ARPA internal error Could not read in from a DSAM mbuf the name part of a Probe name request message This is an NS ARPA internal error The name length specified in a received Probe name request message was invalid This is an NS ARPA internal error The name found in a received Probe name request message had an illegal syntax This is an NS ARPA internal error Had trouble reading in a nodal path report that should have been present in the local node s nodal registry This is an NS ARPA internal error Logging Codes and Messages This error requires HP notification Configure more Probe PCB records This error requires HP notification This error requires HP notification This error requires HP notification This error requires HP notification This error requires HP notification This error requires HP notification This error requires HP notification Encountered a problem in This error requires HP preparing a response message _ notification for a Probe name request This is an NS ARPA internal error Could not read in from DSAM This error requires HP the entire contents of an notification unsolicited Probe reply message This is an NS ARPA internal error The name length specified in an This error requires HP unsolicited Probe reply message notif
85. NSINIT has terminated errornum is an FMP error code An invalid Network Security code was entered An EXEC error errornum occurred when NSINIT attempted to schedule MMINIT You must log on to an account with superuser capability in order to run NSINIT Program Specific Error Messages Refer to the appropriate RTE manual for a description of the RTE error code and rerun NSINIT If the error persists reboot your system and try again If rebooting does not solve the problem this error requires HP notification Check resource number refer to accompanying error messages for more information and rerun NSINIT If the error persists reboot your system and try again If rebooting does not solve the problem this error requires HP notification If this error was returned during startup refer to accompanying error messages for more information and then rerun NSINIT If the error persists reboot your system and try again If rebooting does not solve the problem this error requires HP notification If the error occurred during shutdown the problem should have been corrected during cleanup and no action is required Refer to accompanying error messages for more information If a specific link is needed but not initialized correct the problem and rerun NSINIT Make sure MMINIT exists Refer to the RTE A manuals for information on the accompanying FMP error code Enter the correct Network Security code Ref
86. Network Manager Initialize session environment at remote node or if session is not desired do not attempt to attach to a specific account Enter the correct password RS06 0 ANOTHER PROGRAM OWNS A SESSION RS06 1 ANOTHER PROGRAM OWNS A SESSION RSO7 0 LOGON OR LOGOFF ATTEMPTED TO LOCAL NODE RSO09 0 RSM RECEIVED AN ILLEGAL REQUEST DLGOF The session that the calling program is using was created by another program DLGON DLGNS A session which the calling program is willing to share as specified by the oride parameter exists at the requested node A session which the calling program is willing to share exists at the requested node and the remote node s sub level is 0 No REMAT logons are permitted to the local node Check the oride parameter in your DLGON or DLGNS call for the proper value Refer to the Utilities section in the NS ARPA 1000 DS 1000 IV Compatible Services Reference Manual for a detailed discussion of session sharing Check the oride parameter of your DLGON or DLGNS call for the proper value Refer to the Utilities section in the NS ARPA 1000 DS 1000 IV Compatible Services Reference Manual for a detailed discussion of session sharing Use the SW command to switch to the correct node Remote Session Monitor Contact your Network Manager received an unknown request Alphanumeric Error Messages 3 11 SCxx Error Messages These errors i
87. OAD and SWAP Regenerate the memory based are generated in The APLDR system without the modules DS program and the LOAD and LOAD and SWAP SWAP RTE A modules are trying to manage memory 2 2 Numeric Error Codes iS Partition does not exist Check partition number and try again 56 23 19 14 15 53 54 56 57 58 59 62 63 DLGON DLGOF DLGNS Error Codes These error codes are returned in the err parameter of DLGON DLGOF and DLGNS calls See their ASCII equivalents for more information DLGON DLGOF DLGNS Error Codes a e E Session shutdown Same as Try again later When session is SM13 shut down only the system console is available for operator control Account file corrupt Same as Consult your System Manager SM12 FMP error xxxx on disk mount See SM11 for more information attempt Same as SM11 No free ID segments or FMGR Consult your System Manager not found Same as SM10 SST overflow Same as SM09 Consult your System Manager Duplicate session identifier See SMo8 for more information Same as SMO8 No room for session control Receiving this error indicates block Same as SMO7 this SAM block is filled and the maximum number of sessions are now active Some other session must terminate before a successful access of the remote session node can be accomplished Conflict i E definition of session This is an informational error LU xx Same as SMO6
88. OPY is described in the Network File Transfer section of the NS ARPA 1000 User Programmer Reference Manual Numeric Error Codes 2 1 APLDR Error Codes APLDR errors may be returned to the current log device when the LO command is issued in REMAT They may also appear in the err parameter of the FLOAD command APLDR Error Codes a a LO command not available To use LO search DSLDR before searching CMDLB when loading APLDR RTE A Duplicate program name Change program name Program is not linked for this Re link program system No ID segments are available Remove existing program or modify generation answer file to include more ID segments Successful installation of ID No action is necessary segment into system Illegal name Check program name and try again Shared EMA partition does not Check partition number and try exist again Shared EMA partition is too Check partition number and try small again Reserved partition conflict Check partition number and try again Too many programs sharing Refer to the appropriate RTE EMA programmer s reference manual for information on shared EMA Partition is too small Use a larger partition and try again ASCII PTN No free partition Inform System Manager No partition large enough RTE A ASCII PTSZ Partition Check partition number label specified not large enough or and try again shared EMA label not found RTE A ASCII DISK L
89. P GRPM class no notification IFPM IFPM Detected bad IFPM class number is 0 This error requires HP IFPM class no notification Sie k invalid IFPM socket ID is 0 This error requires HP notification DS SBPut error Could not transfer the message _ This error requires HP to DSAM notification IFPM DS MAppendHead Could not add IFP header to This error requires HP error message in DSAM notification IFPM DS SBAppend error Could not append the message _ This error requires HP to IFP socket notification INPRO ASCII Log Messages The following ASCII log message is printed to the log file and may accompany the location codes listed in Location Codes in this section INPRO ASCII Log Messages Bad Class Number in DSAM See INPRO log message code See page 6 47 302 for more information Logging Codes and Messages 6 65 OUTPRO ASCII Log Messages The following ASCII log messages are printed to the log file and may accompany the location codes listed in Location Codes in this section OUTPRO ASCII Log Messages teswessage Meaig Mion DS_SBDequeue problem See OUTPRO location code 1 See page 6 49 for more information DispatchCall See OUTPRO location code 2 See page 6 49 aa state for more information error DispatchCall See OUTPRO location code 3 See page 6 49 EXCEPTIONAL state error for more information DispatchCall bad The xxxxx xxxxxx fields See page 6 49 Signal XXXXX
90. P IP Log Message Codes 3000 3999 teomessase Meaning Aon 3002 IP Reassembly is not yet This is an informational complete message only No action is required 3006 IP Frag not needed for This is an informational reassembly message only No action is required 3101 IP Message received with bad Check the line transmission checksum quality 3102 IP Message being forwarded Set hop counts at source to and time to live field has gone to include all IP gateways that 0 messages may take 3103 IP Requested path record This error requires HP could not be found This error notification indicates that internal inconsistencies exist 3105 IP No free paths available for Increase the number of IP path allocation records during NS ARPA initialization 3106 IP Requested ANH record No further action is necessary could not be found This error indicates that internal inconsistences exist Cleanup is done by NS ARPA to remove the inconsistency 3107 IP The destination network is The remote network s IP unknown address must be entered in the GT Gateway Table during NS ARPA initialization The unknown network s IP address is contained in the the xx and yy fields of the log record header Put this address into the GT using NSINIT 3108 IP The destination protocol is Such communication is not unknown A message arrived supported destined for the local node but addressed to a protocol unknown to IP 31
91. PA 1000 tracing utilities are described in Section 5 You should refer to this section when you are running NSTRC FMTRC and BRTRC Logging Error Codes and Messages Error codes and messages produced by the NS ARPA 1000 logging utility EVMON and the log mask utility LOGCHG are listed in Section 6 You should refer to this section when attempting to interpret the contents of log files produced by EVMON Using DSERR Many of the numeric error codes described in this manual are returned in the err parameter of PTOP RFA and certain utility calls Because the same numeric error code may have different meanings HP suggests that you call the utility subroutine DSERR whenever an error is returned to a program that utilizes one of these calls Note Do not use DSERR if your PTOP slave program resides on an HP 3000 node if you are using HP 3000 RFA calls or if you are calling HELLO BYE or PRCNM it will produce erroneous results DSERR returns extended error information in the following format DS ERROR SSEE QQ REPORTING NODE NNNNN The DSERR parameters have the following meanings SS subsystem prefix such as SC for scheduling IO for input output and FM for FMGR EE numeric error code QQ numeric error code qualifier NNNNN number of the node reporting the error Refer to Section 7 Utilities of the NS ARPA 1000 DS 1000 IV Compatible Services Reference Manual for a detailed description of DSERR 1 2 Introduction Inter
92. PMCreate or RPMControl call Correct the option code in RPMCreate or the request code in RPMControl Illegal option format One of the following errors has occurred 1 The options code in the RPMCreate Call is not in the correct order For example a Group 3 option code has been specified before a Group 2 option code 2 The format of one of the options in the RPMCreate Call is incorrect Invalid login or password The login name or password specified by the parent program is not valid or was not specified A session could not be created for the child node Child program not found on child node The name of the child program specified in the RPMCreate Call is not found on the child node so the child program cannot be scheduled One of the following problems has occurred 1 The child program cannot be found at the child s node Either the name is incorrect an RTE type 6 file executable program file does not exist or the file could not be found in the search path 2 The child program name specified in the FmpRun option 23110 does not match the name specified in progname of the RPMCreate Call 3 The length of the child program name is incorrect in namelen of the RPMCreate call Invalid program descriptor The pd parameter was not specified correctly in either a RPMControl Of RPMKil1 call Check the option format in the RPMCreate Call Check the login and password parameters in RPMCreate Che
93. R BETWEEN LOCAL AND REMOTE NODES DS07 3 ERROR TCB LIST IN DS07 4 EXPECTED POOL OF REMOTE SESSION IDENTIFIERS POOL NOT EXIST DOES DS08 0 REMOTE BUSY OR RESOURCE UNAVAILABLE Possible malfunction in some software which caused NS ARPA 1000 tables to be corrupted or destroyed MAST An attempt has been made to access a node of a different NS ARPA software upgrade level but the proper input and output message converters are not present in the system to perform the necessary message conversion Your NRV indicates another node in the network is of a different software upgrade level than it actually is RSAX NS ARPA internal tables located in System Available Memory have become corrupt This error is reported by RSAX the Resident Table Access routine This error can happen if DINIT is linked with the library DSNSM no session monitor node anywhere in the network and other modules are relocated with DSSM or DSLSM These other modules include REMAT user programs and slave monitors Returned to master program if 1 Insufficient SAM at the destination node 2 QUEUE is busy 3 Remote system is quiescent 4 No available TCBs in destination node 5 A monitor is in unavailable memory suspend or not available 6 Interrupt Table entry at remote node is incorrect 7 The LU in a DEXEC call is down 8 The LU ina DEXEC call has been locked 9 The error is i
94. RINIT is being run does not have superuser capability This error is returned if 1 NSINIT was not used to set up DSAM prior to running the nodal registry utility 2 NSINIT terminated abnormally before completing NS ARPA initialization or 3 NS ARPA is or is in the process of being shut down NSINIT allocates storage space for the Nodal Registry entries and NRINIT fills these entries This error message is returned when the registry is full again If this error persists you may need to regenerate your system with more resource numbers Run the utility from an account with superuser capability Make sure NS ARPA is initialized before running the nodal registry utility Delete some registry entries or rerun the utility specifying more table space for the Nodal Registry This is an NS ARPA internal This error requires HP error NRINIT has terminated notification Program Specific Error Messages 6008 NRERR IP subfield not in range O42 2255 NR 6009 NRERR Path report is too long 6010 NRERR Incorrect format address for LAN 6011 NRERR environment name kk Illegal format 6012 NRERR Unknown protocol ID 6013 NRERR required but was supplied 6014 NRERR Illegal format for IP address 6015 NRERR IP address is missing An IP subfield was entered that is not in the range O to 255 The specified path as converted t
95. Refer the FMP error codes listed in your operating system reference manual for more information Refer to the FMP error codes listed in your operating system reference manual for more information EVMON will clean up queue and socket if possible otherwise it will terminate If EVMON terminates restart If it persists this error requires HP notification Refer to the NetIPC error codes listed in this manual for more information Refer to the NetIPC error codes listed in this manual for more information LOGCHG Error Messages The following table lists error messages that are returned by the log mask utility LOGCHG LOGCHG Error Messages Message Meaning tion LOGCHG New log mask is The log mask has been set to This is an informational nnnB nnnB message No action is required LOGCHG New log mask is The log mask has been set to This is an informational nnnB Bit 0 must always nnnB This value is the same as message No action is required be set the one requested with the addition of Bit 0 LOGCHG Access to DSAM NS ARPA 1000 is not currently No action is required When not allowed Error code initialized NS ARPA 1000 is initialized nnnn re execute the LOGCHG command LOGCHG nnnnnnn is not a The log mask nnnnnnn Correct the log mask and legal logmask specified in the LOGCHG reexecute the LOGCHG command is not a legal log command This message will mask be followed by the usage message described b
96. Remote program not open No remote system room to initiate Communication 40 4 42 44 45 A PWRIT PREAD Or PCONT call has been issued to a slave program which is dormant 2 22 Numeric Error Codes correctly PCB was destroyed Not enough parameters Check parameters If a clone of the slave is requested in the POPEN call this error can occur if the type 6 file if applicable could not be opened or there are no blank ID segments or there are already 26 clones A thru Z for this program name There is room for up to 20 PTOP slave programs to be active ina single node at the same time May also occur if no class number is available for sending data to the slave Indicates a programming error May occur if a REMAT So slave off command has been given or PTOPM was aborted and restarted POPEN call gets this error if the slave program is not dormant and has not been scheduled by PTOPM in the slave node This may be due to the slave program being scheduled by other means than POPEN This indicates the slave program has been abnormally terminated i e not by PCLOS or FINIS calls or not by the so command A user should fix the code in the slave program which caused it to abort or should re issue another POPEN call in the master program Sequence error May occur in PTOP slave subroutine calls when a communications line error a system table validity check failure or a request ti
97. Request 05 5 ieee ones eae ess bees ees wanes s Deaes cose es 1 3 Chapter 2 Numeric Error Codes APLDR Error COd6S oss c0ices euwa tienen acer wees Ese ee EN ETENEE EEN es eh ex 2 2 DLGON DLGOE DUGNS Error Codes de ririeeris iae nE raa becker GRRE GA 2 3 ERR Error CodeS unner eaa EA E E N S E r E SA t 2 6 HELLOBYE Error Codes ei serotipe a vee EE AE E E A E EE EE dane 2 9 NetIPC Error CodeS wi ccdvines o sti Truro ed KERERE TORNET ERRA TERTRE TORE TAS 2 10 PTOP Erro Cod s 2st ode eenc sepaeunnted Hees SEET CRETE TERA RERET ERRER tee 2 22 Remote T O Mapping Error Codes s sccrssisirirer icta td tape EDEA PRGA DATERE ETA 2 25 RPM Err f Cod s ici tr aks cca sane awed teks itana ORG eR akd EA we Se Ee aS wok 2 26 Chapter 3 Alphanumeric Error Messages DSX Error Messages 44 ccu dans cease thence eeaee eae VAR See SSeS SSeS ERE S SESS ES 3 2 Ox Error Messages vr 04s fess bye POWs een bgewe bh re Eek oe eet Rees b4e eee Ken Ex 3 9 Rox Error Messages eraci oeren taan en trees toutes E EEE ANE E eee 3 10 SCI Error Messages o ariaa beer a ra abe ENE ae eae AN SSR E aN 3 12 SM3 Error Messa ES rniii a EAA EE EE aE EE REENE E te EE E AE AE E ak 3 14 System Consol Errof Messages sesrcsessres onsi rotu on ea sad ERE EREE ead ound 3 15 Unexpected Console Messag S iccnidctaere eye a8 epiti Ten Renee s Ea ah 3 15 Program Download Console Messages ssuuuuunuunrererrrrrrrrrrrnn vas 3 15 DS Error system Console Messages soceri aging ates wee eee sao katin
98. SINIT to shutdown NS ARPA If the error persists reboot your system If rebooting does not solve the problem this error requires HP notification 14018 TCP IPATH already existed This is an informational code only The protocol will recover 14021 TCP Unknown event message _ Run NSINIT to shutdown received NS ARPA If the error persists reboot your system If rebooting does not solve the problem this error requires HP notification TIMER Log Message Codes 15000 15999 TIMER Log Message Codes 15000 15999 tegiessaze Meaning Action 15002 TIMER Internal error The timer This error requires HP list is corrupt notification 15003 TIMER Internal error An This error requires HP invalid time was passed onto notification internal NS ARPA routines 15004 TIMER Timer was canceled This is a warning message only and reset with an invalid timer No action is required ID This is a common occurrence in busy systems It usually occurs because of race conditions between INPRO and OUTPRO 15005 TIMER No available timer If it persists this error requires entries HP notification 6 30 Logging Codes and Messages UPLIN Log Message Codes 17000 17999 UPLIN Log Message Codes 17000 17999 teawessaze Meaning Miom 17001 UPLIN INPRO was dormant This is an informational UPLIN will attempt to reschedule message only No action is INPRO required 17002 UPLIN OUTPRO was dormant This is a
99. Same as RS01 0 above but reported by EXECM EXECW Same as RS01 0 above but reported by EXECW PTOPM Same as RSO1 0 above but reported by PTOPM An error occurred during class I O communication with the LOGON program a No room in local table to catalog a remote session b Local limit reached on number of remote nodes accessed by this program Destination node has reached its limit on number of sessions created from other nodes When session is shut down at a remote node it appears to NS ARPA as though the node has been generated without Session Monitor or Session Monitor has not been initialized Any attempt to attach to specific accounts at the node result in the RS04 error reply An incorrect password was entered Also non session access is not permitted at the local node when operating under control of REMAT or by a call to DLGONS 3 10 Alphanumeric Error Messages After an error of this type future requests will cause a new session to be established specific session is required rather than the default session you must issue a specific attach from REMAT or logon request Ifa Try again and if the error persists consult your System Manager a The local node may need a larger number of sessions NOTE PNLs for remote HP 1000 HP 3000 requests are taken from the same block of SAM b Limit is 16 The destination node might need a larger number of sessions Notify your
100. TE and assign it are available for the PTOP file more pages move buffer used with the Mo command NO SLAVE AT 3000 The slave program which The MO command will not work performs the slave side until the program is installed processing for the MO command with MVCP3 does not exist as COPY3K PUB SYS NO SUCH PROGRAM RTE returned an Sco5 See Sco5 for an explanation scheduling error for a RU ON or RW command NOT ENOUGH SAM RTE returned an Sc10 See SC10 for an explanation scheduling error for an RU ON or RW command NOT LOCAL COMMAND HELLO or BYE under the Use sw to go remote prompt from RMOTE OLD COPY3K VERSION ON Slave program on HP 3000 for Install the new version using 3000 MOVE FAILED LOAD MO command is not most recent MVCP3 NEW VERSION version OLD RMOTE VERSION ON Version of RMOTE is Have your system manager load 1000 MOVE FAILED LOAD incompatible with slave program the latest version of RMOTE on NEW VERSION on HP 3000 for RMOTE mo your system command OVERWRITE Asked when the to file in a file Respond YES to overwrite the move already exists data PROGRAM BUSY An RU or ON command specified Try again when program is a non dormant program dormant REQUEST FAILED The HP 3000 rejected the last Try again request RMOTE IOxx RTE reported O errors See appropriate RTE I O error for an explanation RMOTE SCxx Indicates bad parameters See RTE reported errors earlier in this section
101. TERS IN MAST CALL DS09 2 NEGATIVE WRITE DATA LENGTH IN MAST CALL DSO09 3 NEGATIVE READ DATA LENGTH IN MAST CALL The maximum number of unacknowledged messages has been exceeded EXECM Possibilities are 1 Class I O error or insufficient SAM for class I O Read Write or Control request 2 Class I O error or insufficient EXECM s internal usage 3 Attempted I O request to a disk LU EXECW Possibilities are 1 String could not be passed to scheduled program 2 APLDR could not be scheduled RQUE Possibilities are 1 The number of requests queued on a slave program s class has exceeded the limit of 10 2 The LU onto which the class 1 O request is to be requeued is down 3 The EQT onto which the class I O request is to be requeued is down 4 The destination class queue cannot contain another outstanding request 5 RTE rejected the Rethread request MAST All class numbers are in use Retry the request Check resources or inform your System Manager Check resources or inform your System Manager 1 In the case where a slave simultaneously serves a number of masters which exceeds the queue limit try to reduce the time a slave takes to process and reply to each request 2 Up the LU 3 Up the EQT 4 Check resources and try again 5 Try again NS ARPA monitors use class numbers which may require more class numbers to be allocated at generation Indica
102. The reported numeric NS ARPA 1000 error occurred during a file move operation The reported numeric DS 3000 error occurred during a file move operation The HELLO command was not correct or could not be transmitted due to a line error RTE returned an SCco3 scheduling error for an RU ON or RW command Wrong or missing parameter or wrong prompt on transfer file input From SW command Either the LU is not in the 3000 LU table built when NSINIT was executed or it is not the LU of the currently active session opened on the 3000 The link to the HP 3000 is not functioning physically disconnected or an electrically open circuit The reported FS 3000 error occurred during a file move operation Attempt to send a command to the HP 3000 before issuing HELLO Check NS ARPA error code for action See appropriate numeric error for explanation Check syntax and try again or check to see if the HP 3000 line is down See SCo3 for an explanation Check parameters or transfer file Check LU and try again Check link and try again See the appropriate FS 3000 error code for an explanation of this error Issue a HELLO Program Specific Error Messages 4 59 NEED TO RUN DINIT Attempt to switch to remote Run NSINIT and specify 1K 3K node before the local node has services been initialized for communications to the HP 3000 NO BUFFER SPACE Less than 256 words of memory Terminate RMO
103. X TELNET user program received An internal TELNET error has a fatal internal error occurred This error requires HP notification 20101 xx 0 0 TELNET user program was This error requires HP unable to initialize notification 20102 a b 0 TELNET user program was not a and b represent the A and able to get a class number B registers in integer format Wait for a class number and try again 20103 ipcerror 0 0 TELNET user program received Refer to the NetIPC error code in a NetIPC error from an internal the Numeric Error Codes IPCSelect call section of this manual for more information 20104 xx 0 0 TELNET user program received An internal TELNET error has a bad event from an internal occurred This error requires HP IPCSelect call notification 20200 ipcerror 0 0 TELNET user program received Refer to the NetIPC error code in a NetIPC error ipcerror on the Numeric Error Codes the terminal connection section of this manual for more information 20201 ipcerror 0 0 TELNET user program received With HP Modem running at the an exceptional signal on the target node when a user exits TELNET server connection the session the TELNET user program will log this message This is a normal condition not an error 20204 ipcerror 0 0 TELNET user program received Refer to the NetIPC error code in a NetIPC error sending data to the Numeric Error Codes the TELNET server section of this manual for more inf
104. X XXXXKXX contain the signal record for the socket in octal See OUTPRO location code 4 for more information DispatchRoot See OUTPRO location code 5 See page 6 50 CTRL READABLE state for more information error DispatchRoot bad The xxxxxx xxxxxx fields See page 6 50 Signal XXXXXX XXXXXX contain the signal record for the socket in octal See OUTPRO location code 6 for more information DispatchEvent Illegal See OUTPRO location code 7 See page 6 50 Socket Kind for more information DispatchVC EXCEPTIONAL See OUTPRO location code 8 See page 6 50 state error for more information DispatchvVC See OUTPRO location code 9 See page 6 51 DATAREADABLE state for more information error Dispatchvc bad signal The xxxxxx xxxxxx fields See page 6 51 XXXXXXX XXXXXXX contain the signal record for the socket in octal See OUTPRO location code 10 for more information DequeueAndPass problem See OUTPRO location code 11 See page 6 51 for more information 6 66 Logging Codes and Messages HP ROUTER ASCII Log Messages The following ASCII messages are printed to the log file when the Entity is HP ROUTER HP ROUTER ASCII Log Messages Message Meaning Aon RROB DS_MDispose error Error encountered when This error requires HP disposing the message notification RROB NRV error Could not find the path This error requires HP reference in the NRV notification RROB OutStub detected It i
105. Y CONNECT SECONDARY CONNECT AWAITING REPLY DISCONNECT vvvvv LINE FAILURE TIMEOUT OVERRUN REMOTE BUSY UNINITIALIZE WRONG MODE ILLEGAL REQUEST CARD FAILURE There were users on the PSI BISYNC line when you tried to close it so DSLIN terminated without closing the line You entered a carriage return in response to the question HP 3000 TO INITIALIZE A was read as a request to terminate the program DSLIN was terminated DSLIN attempt to lock the lu for primary connection failed Program Specific Error Messages No action is necessary Check the board type and firmware See specific error code Try running DSLIN again later Enter the LU of the PSI BISYNC line that you want to initialize No action is necessary Attempt to lock fails when someone else is running DSLIN at the same instant or if you have incompatible software Wait a minute and try again If the problem persists contact your Network Manager 4 17 CONNECTING AS A SECONDARY STATION ON LU XXX DS 1000 HAS NOT BEEN INITIALIZED HP 1000 is awaiting a call from the HP 3000 to establish the communication link NS ARPA 1000 software has not been initialized No action is necessary Run NSINIT specifying links to an HP 3000 and try again ERROR OPENING aaaaa DSLIN could not open the Check syntax command file aaaaa LINE IS UP BUT HP3000 IS NOT REPLYING The PSI card was initialized but Check stat
106. a protocol The procedures that constitute a protocol handler may reside in different processes The Entity printed in the Entity field is not necessarily the same as the Entity that encountered the error The entities are as follows ARM Address Resolution Module ARP Address Resolution Protocol ETHERNET Ethernet protocol handler HP FTP File Transfer Protocol HP IFP Interface Protocol handler used for DS 1000 IV Compatible Services over IEEE 802 3 links HP IP Internet Protocol handler HP NFT Network File Transfer subsystem Logging Codes and Messages 6 3 HP PROBE Probe protocol handler HP PXP HP Packet Exchange Protocol handler HP ROUTER Router 1000 protocol handler HP RPM Remote Process Management HP TCP Transmission Control Protocol HP TN TELNET virtual terminal service e ICMP Internet Control Message Protocol used for PING IEEE 802 IEEE 802 3 protocol handler INPRO Inbound message handler e OUTPRO Outbound message handler PROSW NS ARPA module that delivers event messages between the protocol and event handlers in INPRO and OUTPRO RUNTIME These are Pascal detected runtime errors SIGMOD Signal module used by NetIPC and contains some NetIPC routines SREG Socket Registry modules TIMER Timer monitor subsystem e UPLIN UPLIN module Note The Entity RunTime is printed in the Entity field of the log record header w
107. ady familiar with the concepts and syntax presented in those two manuals The NS ARPA 1000 Quick Reference Guide also contains abbreviated syntax for certain programs and utilities described in the NS ARPA 1000 Generation and Initialization Manual and the NS ARPA 1000 Maintenance and Principles of Operation Manual For your convenience the NS ARPA 1000 Quick Reference Guide also contains a master index of NS ARPA 1000 manuals This is a combined index from the NS ARPA 1000 manuals to help you find information that may be in more than one manual 91790 90045 NS ARPA 1000 Error Message and Recovery Manual Lists and explains in tabular form all of the error codes and messages that can be generated by NS ARPA 1000 This manual should be consulted by programmers and users who will be writing or maintaining programs for NS ARPA 1000 systems Because it contains error messages generated by the NS ARPA 1000 initialization program NSINIT and other network management programs it should be consulted by Network Managers 91790 90050 NS ARPA 1000 DS 1000 IV Compatible Services Reference Manual Describes the user level services provided by the DS 1000 IV backward compatible services These services are Remote File Access RFA DEXEC REMAT RMOTE program to program communication PTOP utility subroutines remote I O mapping remote system download to memory based DS 1000 IV nodes only and remote virtual control panel 91790 90060 NS ARPA 1000 BSD IPC Re
108. age No action is necessary This is an informational message No action is necessary Target logon or node The target logon or node name _ This is an informational name overrides previous _ given in the copy descriptor will message No action is setting override the default setting for necessary NFT 1000 WARN 9 the current copy descriptor Subsequent copy descriptors will not be affected Input line too long The input line was greater than Shorten the length of the input NFT 1000 ERR 10 80 characters line to less than 80 characters and place the continuation character amp at the end of the line Continue input on the next line Cannot find closing An opening quotation mark was Check syntax and try again quotation mark given in the command but the NFT 1000 ERR 13 closing quotation mark could not be found No source file was given No source file was specified in Check syntax and try again NFT 1000 ERR 14 the copy descriptor Cannot find last square A logon string must be Check syntax and try again bracket for logon string terminated by a square bracket NFT 1000 ERR 15 Logon string is too long A logon string must not be Check syntax and try again NFT 1000 ERR 16 greater than 60 characters Node name is too long A node name must not be Check syntax and try again NFT 1000 ERR 17 greater than 50 characters File name is too long A file name must not be greater Check syntax and t
109. ain from BEGIN or terminate and rerun NRINIT If you are using NRINIT with a text file correct the name in the text file and rerun NRINIT If you are using NRINIT interactively you may start again from BEGIN or terminate and rerun NRINIT If you are using NRINIT with a text file correct the IP address in the text file and rerun NRINIT If you are using NRINIT interactively you may start again from BEGIN or terminate and rerun NRINIT If you are using NRINIT with a text file correct the address in the text file and rerun NRINIT 6029 NRERR Conflicting environment names in same record 6030 NRERR Zero valued network number illegal 6031 NRERR Zero valued node address illegal 6032 NRERR Address is in the reserved class kk 6033 NRERR Only LAN link protocol id is allowed here 6034 NRERR Internal DSAM error reported 6035 NRERR Total entry length exceeds maximum size 6036 NRERR Node name length larger than maximum size An END was not encountered before the second entry causing the second entry to be interpreted as a continuation of the previous entry This error was returned because the environment name in the second entry was different from that in the first entry A Class A IP address with a network number of zero was specified Zero is reserved and may not be used A Class A B or C IP address with a node address of zer
110. and requires HP notification Entity OUTPRO The following codes are printed to the Location field of the log record header when the event class is Warning Class 3 Error Class 4 Disaster Class 5 or RsrceLim Class 6 and the Entity printed to the Entity field is OUTPRO OUTPRO was unable to dequeue an outgoing message from its socket in order to pass it on the transport protocol handler concerned The xx field of the log record header contains the global socket descriptor of the socket that encountered the problem and the yy field contains the error number indicating the problem that prevented dequeueing of the message This is an NS ARPA internal error 2 OUTPRO received a signal indicating that a call socket had a control message on it and yet the socket was not in a state that permitted these messages The xx field of the log record header contains the global socket descriptor of the socket that encountered the problem and the yy field contains the state so_b state the socket was in This is an NS ARPA internal error OUTPRO received a signal indicating that a call socket had an exception message on it and yet the socket was not in a state that permitted these messages The xx field of the log record header contains the global socket descriptor of the socket that encountered the problem and the yy field contains the state so_b state the socket was in This is an NS ARPA internal error OUTPRO re
111. are communicating error indicates that NSINIT encountered a problem while accessing an IEEE 802 3 communication link card NSINIT will not pursue communication with the LAN 1000 software No IEEE 802 3 messages will be delivered to NS ARPA 1000 although initialization may complete successfully SAM may fill up with these messages because the LAN 1000 driver will still be receiving messages from NS ARPA 1000 NSINIT has encountered a Use the LAN 1000 NM program problem with the interface card to check that the card and driver associated with LU lu This are communicating error indicates that NSINIT encountered a problem while accessing an IEEE 802 3 communication link card NSINIT will not pursue communication with the LAN 1000 software No IEEE 802 3 messages will be delivered to NS ARPA 1000 although initialization may complete successfully SAM may fill up with these messages because the LAN 1000 driver will still be receiving messages from NS ARPA 1000 NSINIT has encountered an RTE Refer to the RTE manuals for error This error indicates that more information NSINIT encountered a problem while accessing an IEEE 802 3 communication link card NSINIT will not pursue communication with the LAN 1000 software No IEEE 802 3 messages will be delivered to NS ARPA 1000 although initialization may complete successfully SAM may fill up with these messages because the LAN 1000 driv
112. assed in the vector s address fields under RTE A byte addresses are different from word addresses Byte addresses can be generated by invoking the special NetIPC call Adrof Address in use The caller One or both of the following process requested that its call actions may be taken 1 Verify socket descriptor be bound to a that the address specified was particular protocol address but the intended one or 2 verify the address was already bound that the address falls within the to another call socket descriptor range accessible to users certain addresses are reserved for use by HP services May be caused by one of the Release all NS ARPA resources following 1 NS ARPA is not held and save any context initialized 2 NS ARPA is going information necessary for up or down or 3 the NS ARPA successful restart memory area is corrupt This error indicates that the user Do not continue to do IPCRecv has been informed that the once the remote has gracefully remote process has gracefully released the socket There can released this socket via an error never be any more data 68 on an IPCRecv available on it Subsequent IPCRecv Calls will get this error An NS ARPA internal software This error requires HP error has been encountered notification No useable paths The local Obtain a new path report node s protocol software cannot descriptor using IPCLookUp If connect to the remote node this is
113. be released via IPCShutDown A later attempt to re establish a failed connection may work if the underlying problem is corrected e g if a crashed node is rebooted if the links of a partitioned network are repaired or if a heavily congested network has become less congested The calling process must assign fewer names to the referenced socket Release some of the names that are bound to sockets This may be done using either IPCNamErase Or IPCGet Because name records are system wide resources shared by all NS ARPA programs the name records released by one program may be allocated for use by another One or both of the following actions may be taken 1 Make sure that the name specified in the TPCLookUp call was the one that was intended 2 consider that the failure could have been due to a race condition the IPCLookUp caller could have executed its call before the IPCName caller executed its call Check that the name specified is the one the caller intended to use Verify that the name passed was the intended one or verify that the length specified for the passed name was correct Numeric Error Codes 2 13 2 14 Numeric Error Codes Unknown registry The caller invoked IPCLookUp with the name of a registry that was unknown to the local node A local node may resolve a registry name in one of two ways 1 either it can consult its local nodal database or 2 it can use the PROBE protocol if it
114. boot your system and try again See error 145 Check your system for memory problems Refer to accompanying error codes for more information and rerun NSINIT If the error persists reboot your system and try again If rebooting does not solve the problem this error requires HP notification 4 37 149 NSINIT Network Management Security Code is 0 Cleaning up 150 NSINIT Internal segment error Attempting cleanup Segment is segment 151 Terminating because of EnterCritical Error 152 NSINIT Attempting deallocation of dsam for cleanup 153 NSINIT MMInit internal error DSAM not allocated Terminating kk 154 NSINIT Invalid state in DSAM state word Terminating 155 NSINIT Invalid state in DSAM state word UNINIT Terminating kk 156 NSINIT Error opening output file Terminating 4 38 NSINIT found that the Network Management Security Code was zero The security code could have been set to zero during a previous clean up attempt when NSINIT aborted NSINIT will attempt to clean up again NSINIT encountered an error while initializing or shutting down a protocol segment The segment number returned in segment is for HP use NSINIT received an enter critical error from Memory Manager NS ARPA is in an abnormal state NSINIT has terminated NSINIT is not sure if DSAM was allocated and is attempting to deallocate it Refe
115. booting does not solve the problem this error requires HP notification Rerun NSINIT Ifthe error persists reboot your system and try again If rebooting does not solve the problem this error requires HP notification Rerun NSINIT If the problem persists this error requires HP notification 4 31 54 NSINIT Terminating program because of input error kk 55 NSINIT Sreg error Cleaning up Error is errornum 56 NSINIT WARNING Cannot access DSAM Segment reporting problem is segnum 100 NS Parity Error in MBuf in DSAM kk 101 NS Corrupt MBuf in DSAM 102 NS Parity Error in Table Area in DSAM 103 NS Parity Error in Global Area of DSAM 104 NS DSAM State Word indicates Partial initialization of DSAM 105 NS State Word indicates an aborted startup of NS Occurred kk 106 NS State word indicates an aborted shutdown of NS occurred kk 4 32 NSINIT found invalid user input in an answer file NSINIT has terminated NSINIT received an error when it called SRegIpcTemplates NSINIT has aborted A NetIPC error code is returned in errornum NSINIT cannot gain access to DSAM The value returned in segnum is for HP use only This error usually occurs at shutdown NSINIT was notified of a parity error in the message buffers in Distributed System Available Memory DSAM when it requested the state of DSAM NSINIT was n
116. bort and rerun NSINIT with a 1 larger master timeout or 2 a smaller Message Accounting retry limit If you are using NSINIT with an answer file NSINIT has aborted Correct the answer file as described above and rerun NSINIT If you are using NSINIT interactively correct and reenter your NRV responses If you are using NSINIT with an answer file NSINIT has aborted Correct your NRV responses in the answer file as described above and rerun NSINIT If you are using NSINIT interactively enter a non duplicate IP address If you are using NSINIT with an answer file NSINIT has aborted Correct the IP address in the answer file as described above and rerun NSINIT 307 NRV Duplicate router address 308 Link Duplicate LU number 309 Link Bad non rerouting LU 311 NSINIT Error enabling RTR link Driver Reports errornum 312 Link LU number Invalid 313 Link Improper enable indicator Enter E or NE A router address has been entered that is the duplicate of a previously entered router address A link LU has been entered that is the duplicate of a previously entered link LU An attempt has been made to enable a Router 1000 LU as non rerouting but there is no reference to this LU in the NRV NSINIT will not enable a non rerouting LU if it is not referenced in the NRV section of NSINIT An RTE error errornum occurred when NSINIT attempted to enabl
117. ceived a signal indicating that a call socket had some undefined message on it The xx field of the log record header contains the global socket descriptor of the socket that encountered the problem This is an NS ARPA internal error Logging Codes and Messages No action is necessary unless enough messages are dropped in this way to impact system functions If this is the case a shutdown and restart of NS ARPA may clear the problem If it does not this error requires HP notification This error requires HP notification This error requires HP notification This error requires HP notification 6 49 OUTPRO received a signal indicating that a root socket had a control message on it and yet the socket was not in a state that permitted these messages The xx field of the log record header contains the global socket descriptor of the socket that encountered the problem and the yy field contains the state so_b state the socket was in This is an NS ARPA internal error OUTPRO received a signal indicating that a root socket had some undefined message on it The xx field of the log record header contains the global socket descriptor of the socket that encountered the error This is an NS ARPA internal error 7 OUTPRO received a signal indicating that a socket had some message on it but the socket is of an undefined kind The xx field of the log record header contains the global socket descriptor of the sock
118. ck the child program name and length parameters in RPMCreate Make sure that an executable program file exists at the child s node Make sure that the program descriptor is the one returned by the RPMCreate Call Also make sure that the node name specified is the same as the one in the RPMCreate Call Numeric Error Codes 2 27 Remote process limit exceeded One of the following problems has occurred 1 The remote node cannot handle RPM messages greater than 1024 bytes and it received a message that is greater than 1024 bytes 2 RPM at the child s node encountered an FMP error while either executing the FmpRunProgram option 23110 or the Restore Program option 23010 in RPMCreate The FMP error is contained in the xx field of the log record header 3 Too many child programs are executing at the child s node RPM cannot allocate another child program 1 Make sure that RPM software installed at the child s and parent s nodes is compatible 2 Check the FMP error and the option in RPMCreate 8 Wait for resources to be deallocated and try the RPM call later 1 Increase DSAM on the child s node 2 Increase the number of ID segments on the child s node Or wait until ID segments are released and try the RPM call later 3 Wait until child programs have terminated and try the RPM call later 1 Security violation or device error This error message is not used in NS ARPA RPM Unknown int
119. consistencies exist IP The message length passed with the event message disagrees with IP s header IP Fragmentation is required for this message but is not allowed Logging Codes and Messages If other errors occur with this error note these problems and notify HP If this problem persists this error requires HP notification If the problem persists this error requires HP notification Allocate more IP Path records in NSINIT to avoid running out of room for ANH records If the problem persists this error requires HP notification This error requires HP notification This error requires HP notification This error requires HP notification This error requires HP notification This error requires HP notification This is an informational message only However if this message is frequently received it requires HP notification Send smaller messages that do not require fragmentation tostiessaze Meaning aon 3125 IP Fragmentation failed This error requires HP notification 3126 IP The current route is bad If it persists this error requires HP notification 3127 IP The requested RCB was not This error requires HP found notification 3130 IP An Unknown Timer expired If it persists this error requires and IP processed the signal HP notification 3131 IP The IP header is of an NS ARPA 1000 only supports IP unsupported version header version four 3133 IP ICMP m
120. d System Available Memory DSAM during shut down NSINIT attempted to finish clean up some resources may remain allocated however An attempt was made to shut down NS ARPA when NS ARPA was not initialized An attempt was made to start up NS ARPA when NS ARPA was already initialized The NS ARPA state word indicated that NS ARPA is only partially initialized The input and output files specified are the same file NSINIT requires that the input file and output file be different files Program Specific Error Messages Build a larger Shareable Extended Memory Access SHEMA partition or examine your table structure and reduce amount of Distributed System Available Memory DSAM Make sure the DSAM SHEMA load file is correct and rerun NSINIT Refer to accompanying error messages for more information and rerun NSINIT If the error persists reboot your system and try again If rebooting does not solve the problem this error requires HP notification Reload NSINIT using the load file provided Rerun NSINIT to make sure that the shut down was successful This is an informational message No action is required This is an informational message No action is required Shut down NS ARPA before attempting another start up Change the input or output file name 126 NSINIT Output file not opened 127 NSINIT Action is invalid Try again 128 NSINIT Action is invalid NSINIT Ab
121. d in six groups of two hexadecimal digits Groups are separated by dashes Check to make sure that current software is being used If it is not upgrade the software to the current release If the software is current the Nodal Registry is corrupted notify your HP field office Check syntax and try again Check syntax and try again Check syntax and try again This is an NS ARPA internal This error requires HP error notification Program Specific Error Messages NSINF Error Messages The following error messages may be returned when NSINF is scheduled They occur when NSINF checks the state of DSAM before continuing NSINF Error Messages NSINFERR 1 Warning Parity error detected in DSAM clusters mbufs NSINFERR 2 Parity error Globals Area Warning detected in k NSINFERR 3 Parity error Tables Area Warning detected in kk kk NSINFERR 4 NS ARPA is not initialized Warning kk NSINFERR 5 Disaster State is inconsistent of DSAM kk NSINFERR 6 NSINF access to DSAM permitted No NSINFERR 7 Warning Inconsistency detected Try running NSINF again NSINFERR 8 NSINF will be denied access to some information NSINFERR 9 NSINIT stateword is invalid stateword is stateword NSINFERR 10 NSINIT aborted during shutdown NSINFERR 11 NSINIT aborted during startup A parity error occurred in a cluster of mbuf Memory was unlin
122. d to terminate execution of FCOPY D3KMS This error is returned Run NSINIT to initialize the when a program tries to node generate no wait call traffic out of a node that is not initialized 3 2 Alphanumeric Error Messages DS00 1 LOCAL NODE NOT INITIALIZED TO TALK TO HP 1000 GRPM 0 DS00 2 LOCAL NODE IS NOT INITIALIZED QRN IS LOCKED GLOBALLY DS00 3 LOCAL SYSTEM IS NOT INITIALIZED DS01 0 COMMUNICATION LINE PARITY PROTOCOL FAILURE STOP RECEIVED CABLE DISCONNECTED OR OTHER HARDWARE ERROR DS03 0 ILLEGAL RECORD DS03 1 INBOUND DATA LENGTH TOO LARGE FOR INPUT CONVERTER DS03 5 INBOUND DATA LENGTH TOO LARGE FOR USER BUFFER MAST This error can occur when only an HP 1000 HP 3000 link has been defined and REMAT or any other master routine intended for HP 1000 HP 1000 communication is called to attempt access to another HP 1000 MAST This error is returned when a program tries to generate traffic out of the local node while the local node is not initialized MAST Returned when a program tries to generate no wait call traffic out of a node that is not initialized DVA66 This error means that the link is not connected Indicates programming error INCNV INCNV is loaded with a fixed buffer size module This buffer must be capable of receiving the entire incoming message MAST The message header mus
123. de to NSINIT after setting up Distributed System Available Memory DSAM NSINIT has terminated NSINIT attempted to scheduled MMINIT but the name that was returned to the scheduling call was not MMINIT NSINIT terminated before starting up NS ARPA NSINIT attempted to deallocate Distributed System Available Memory DSAM but DSAM was not allocated This error may be returned if an error is detected in the NS ARPA software NSINIT has terminated DS_DeallocDSAM reported that NSINIT passed an invalid security code This error message is returned when an error is detected in the NS ARPA software The Shareable Extended Memory Access SHEMA size needed is too large causing NSINIT to terminate NSINIT deallocated Distributed System Available Memory DSAM Program Specific Error Messages Shut down NS ARPA and initialize again Rerun NSINIT If the error persists reboot your system and try again If rebooting does not solve the problem this error requires HP notification Make sure that the correct MMINIT program is being scheduled and rerun NSINIT Make sure that the correct MMINIT program is being scheduled and rerun NSINIT Rerun NSINIT and or run WHZAT to see if the Shareable Extended Memory Access SHEMA partition is there If the SHEMA exists reboot your system and try again Rerun NSINIT and attempt another shut down If the problem persists this error requires HP notification Examine y
124. e Call The RPMGet String call can only be used by a child program scheduled by RPM It must have been created previously by RPMCreate Check the string length in the RPMCreate call Check the child program 18023 xx XX XX Unsupported RPM call This RPM call is not used on NS ARPA 1000 RPM 18302 XX XX XX 18304 muerror XxX XX 18305 aa bb xx 18306 CS XX XX 6 36 Table is full There is no free entry in the local RPM Parent Process Table to accommodate this RPMCreate call RPM attach failed The RPM Monitor failed to attach to either the parent or child session A Multiuser error is logged Schedule error The RPM Monitor cannot schedule the child because the EXEC call failed The values of the A and B registers which were returned by the EXEC call are logged in the log file Cannot find child program s ID segment The child program does not exist anymore This can occur if the RTE oF command is used on the child program after it is RPed but before RPM can schedule it cs indicates the child program status Logging Codes and Messages Wait until a parent program completes and RPM deallocates resources Try again later Refer to the Multiuser Log Message Codes subsection earlier in this section aa and bb are fields of the log header record and contain the values of the A and B registers Refer to the RTE manuals for an explanation of the EXEC error Make sure that the child program exis
125. e DS04 for an explanation See DS05 for an explanation See DS06 for an explanation At this point rebooting or shutdown restart are probably the only viable solutions See DS08 for an explanation Correct program calling parameters and re run Numeric Error Codes 2 5 ERR Error Codes The ERR errors are returned to the err parameter of PTOP RFA and certain utility calls They may also be returned in the A and B registers after a DEXEC call or to the current log device through REMAT REMAT displays all numeric error codes that it receives by using the utility subroutine DSERR DSERR is explained in the Utilities section of the NS ARPA 1000 D S 1000 IV Compatible Services Reference Manual If the no abort option is set when an error occurs in programs calling DEXEC or certain utilities ASCII error codes are also returned in the A and B registers If the no abort option is not set the message will be printed on the initiating terminal and the program will abort NS ARPA 1000 system programs receiving these error codes generally display them on the initiator s terminal or log device ERR Error Codes lllegal parameter type Check parameters Missing parameter Check parameters 45 Input device must be interactive Check input device for REMAT FL command 13 REMAT transfer file stack Correct transfer file and try overflow again Input error illegal REMAT Check command syntax command etc FCOPY Duplica
126. e allocated resources before terminating NSINIT encountered an error while allocating System Memory Block SMB NSINIT attempted to deallocate Distributed System Available Memory DSAM before terminating This error may indicate that DS 1000 IV is currently initialized An error was detected in the NS ARPA software when PrintPrompt reported an internal error This caused NSINIT to terminate NSINIT detected an invalid socket count during the TCP portion initialization NSINIT attempted to deallocate all allocated resources before terminating Program Specific Error Messages Rerun NSINIT Ifthe error persists reboot your system and try again If rebooting does not solve the problem this error requires HP notification Rerun NSINIT Ifthe error persists reboot your system and try again If rebooting does not solve the problem this error requires HP notification Rerun NSINIT Ifthe error persists reboot your system and try again If rebooting does not solve the problem this error requires HP notification Rerun NSINIT Ifthe error persists reboot your system and try again If rebooting does not solve the problem this error requires HP notification Check LU 1 and rerun NSINIT Rerun NSINIT Ifthe error persists reboot your system and try again If rebooting does not solve the problem this error requires HP notification Rerun NSINIT Ifthe error persists reboot your system and try again If re
127. e an LU An LU number was entered that is out of range An invalid enable indicator was entered Program Specific Error Messages If you are using NSINIT interactively enter a non duplicate router address If you are using NSINIT with an answer file NSINIT has aborted Correct the router addresses in the answer file as described above and rerun NSINIT If you are using NSINIT interactively enter a non duplicate LU If you are using NSINIT with an answer file NSINIT has aborted Correct the link LU in the answer file as described above and rerun NSINIT If you are using NSINIT interactively either 1 enable the LU with the rerouting option or 2 abort NSINIT and rerun it using the LU number in response to the NRV prompt If you are using NSINIT with an answer file NSINIT has aborted Correct the answer file as described above and rerun NSINIT This is an informational message only no action is required NSINIT will continue to startup NS ARPA If the link associated with the LU is desired refer to the appropriate RTE reference manual for more information about the RTE error code and rerun NSINIT to enable the LU If you are using NSINIT interactively enter an LU number in the range 1 to 255 If you are using NSINIT with an answer file NSINIT has aborted Correct the LU in the answer file as described above and rerun NSINIT If you are using NSINIT interactively type E enable the LU NE do
128. e contents of PCB are not overwritten 53 54 55 56 57 58 59 2 24 Numeric Error Codes Remote I O Mapping Error Codes The following are serious Remote I O Mapping error codes When these errors occur they are returned to IOMAP in the first return parameter the second and third parameters will be meaningless These error codes are obtained when IOMAP is run with a 2 parameter For additional IOMAP error codes refer to the NS ARPA 1000 Generation and Initialization Manual REMOTE I O Mapping Error Codes NS ARPA quiescent resource User software has a number is corrupt illegally accessed labeled common Consult your System Manager 5 Source node is not completely Wait until source node is initialized initialized Class number set up for LUMAP User software has probably has been corrupted illegally accessed labeled common Consult your System Manager Program LUMAP is not present Load or RP LUMAP in system Destination node number is not Check node number and NRV in the NRV If node number is missing from NRV consult your System Manager P10 NS ARPA not initialized not initialized Run Run NSINIT E C E E on class number Aon a error requires HP allocation notification No class numbers available Try again later If the problem persists regeneration of the system may be necessary to add class numbers Numeric Error Codes 2 25 RPM Error Codes These error codes are
129. e gateway IP address specified is not in the form of a valid IP address The IP address format is n n n n where n is a number from 0 to 255 The hop count specified to the remote network is invalid The hop count specified to the remote network is out of range The IP address entered for a local IP address is the duplicate of one already entered The destination network entered is a duplicate of one already entered An error was detected when attempting to enter critical while setting up the protocol table elements The specified node or network address is a duplicate of one already entered at the DCN prompt Program Specific Error Messages If you are using NSINIT interactively specify an IP address for the gateway If you are using NSINIT with an answer file correct the answer file and rerun NSINIT If you are using NSINIT interactively enter the IP address of any node on one of the directly connected networks as the gateway to the given destination If you are using NSINIT with an answer file correct the IP address as described above and rerun NSINIT If you are using NSINIT interactively enter a hop count between 1 and 100 If you are using NSINIT with an answer file correct the hop count in the answer file as described above and rerun NSINIT If you are using NSINIT interactively enter a hop count between 1 and 100 If you are using NSINIT with an answer file correct the hop count in the an
130. e of the following resources memory for storing nodal path reports or memory for storing connect site path reports The Socket Registry charges the space for nodal path reports against Probe s special path memory socket Space for connect site path reports is charged against the Socket Registry s special path memory socket You may configure the amount of memory initially allocated to each of these sockets by running NSINIT SREG Location Codes Could not purge an entry from This error requires HP the Nodal Registry database notification This is an NS ARPA internal The Socket Registry could not Configure more space for the obtain enough space to store a__ storage of Nodal Path Reports nodal path report Adding the local node s entry This is a warning only into the Nodal Registry is not allowed Had trouble reading the This error requires HP preamble part of an entry stored notification in the Nodal Registry database This is an NS ARPA internal error Had trouble reading the next This error requires HP pointer of an entry stored in the notification Nodal Registry database This is an NS ARPA internal error Had trouble reading the This error requires HP preamble part of a Nodal notification Registry database entry prior to purging it This is an NS ARPA internal error Had trouble reading the next This error requires HP pointer part of a Nodal Registry notification database entry prior to
131. ectionless data for transmission The message affected was lost However if the message was for a DS 1000 IV Compatible Service Message Accounting will probably retransmit it The xx field of the log record header contains the global socket descriptor of the socket that encountered the problem and the yy field contains the socket_b state field of the socket This is an NS ARPA internal error This error requires HP notification This error requires HP notification This error requires HP notification Logging Codes and Messages 6 51 Entity HP PROBE The following codes are printed to the Location field of the log record header The following codes are printed when the event class is Warning Class 3 Error Class 4 Disaster Class 5 or RsrceLim Class 6 and the Entity printed in the Entity field is HP PROBE HP PROBE Location Codes 6 52 An attempt to store a Probe message into a DSAM mbuf prior to transmission failed This is an NS ARPA internal error A Probe transaction was initiated either by IP or the Socket Registry while all of Probe s path records were in use Could not read in the virtual network addresses from the mbuf containing the newly arrived gateway request message This is an NS ARPA internal error Indicates a configuration problem The IEEE 802 software did not have the station address for the local node on the network in which it is supposed to be a member This is an
132. ectory or 2 the source file name specifies an unsupported device A connection could not be established to the computer where the source file resides Either the source computer name is incorrect the source computer is not connected to the network there are insufficient resources or NFT has not been initialized on the source computer A connection could not be established to the computer where the target file resides Often means Probe failed on the LAN or the target computer was not in the local Nodal Registry Either the target computer name is incorrect the target computer is not connected to the network there are insufficient resources or NFT has not been initialized on the target computer There are insufficient resources at the source computer to copy the file or files Refer to the qualifying error string Program Specific Error Messages This error may require one of the following actions 1 If an additional error message is returned refer to it for further information 2 check the logon string and try again or 3 provide a different logon string and try again This error may require one of the following actions 1 If an additional error message is returned refer to it for further information 2 check the logon string and try again or 3 provide a different logon string and try again Verify that the source file exists and is accessible Also refer to the qualifying file system error
133. ed in NS ARPA RPM Check the RPMCreate or RPMControl call and make sure that the option array is constructed correctly Refer to NetIPC error code 40 in the Numeric Error Codes section of this manual Check the child and parent programs to make sure that the number of RPMGet String Calls matches the number of strings in the parents RPMCreate call The RPMGet String call can only be used by a child program scheduled by RPM It must have been created previously by RPMCreate Check the string length in the RPMCreate Call Numeric Error Codes 2 29 302 2 30 Numeric Error Codes The child program terminated abnormally Either a memory protect error occurred or the child was accidentally terminated by someone by RTE OF command Check the child program Unsupported RPM call This RPM call is not used on NS ARPA RPM Table is full There is no free entry in the local RPM Parent Process Table to accommodate this RPMCreate call RPM attach failed The RPM Monitor failed to attach to either the parent or child session A Multiuser error is logged Schedule error The RPM Monitor cannot schedule the child because the EXEC call failed The values of the A and B registers which were returned by the EXEC call are logged in the log file Cannot find child program s ID segment The child program does not exist anymore This can occur if the RTE oF command is used on the child program after it is
134. ed filename The Pascal error errornum occurred when NSINIT attempted to open LU 1 to print informational messages NSINIT has aborted The Pascal error errornum occurred when NSINIT attempted to open the file named filename as a log file The default log device LU 1 was opened as the log device instead NSINIT encountered the end of file in an input file NSINIT encountered invalid user input while building an answer file Invalid responses were placed in the answer file Program Specific Error Messages Refer to accompanying error messages for more information If you are using NSINIT interactively enter valid input If you are using NSINIT with an answer file correct the input in the answer file and rerun NSINIT If you are using NSINIT interactively enter valid user input to subsequent prompts If not correct your answer file and try again If you are using NSINIT interactively enter valid user input to subsequent prompts If not correct your answer file and try again Refer to accompanying error messages for more information Rerun NSINIT If the error persists reboot your system and try again If rebooting does not solve the problem this error requires HP notification This is an informational message only No action is required Refer to accompanying error messages for more information You must delete the invalid input before using the answer file to initialize NS ARPA NS E
135. eeneneewenwe 6 10 HP NET Lop Message Codes 100 599 oc cccsyoweewss tees besaedee seen be und 6 12 Memory Manager Log Message Codes 1000 1999 0 2 eee ee ee eee 6 16 Multiuser Log Message Codes 2000 2999 2 ccceccsseedestssebeseeeeseeees 6 20 HP IP Lop Message Codes 3000 3999 ioe id os pate nus geal eenpeaeheedes eae oe 6 21 HP IEEE 802 ETHERNET Log Message Codes 4000 4999 0 6 26 HP PAP Log Message Codes 5000 5999 cco scduckgws dave sgevekneesiuydeedes 6 27 HP ROUTER Log Message Codes 8000 8999 0 eee eee eee eee eee 6 28 HP TCP Log Message Codes 14000 14999 1 2 eee eee eee 6 29 12 TIMER Log Message Codes 15000 15999 cscccsei ast cagaack Gasset oh earededs 6 30 UPLIN Log Message Codes 17000 17999 5 cccicveebices Hiae edhe bed eee es 6 31 HP RPM Log Message Codes 18000 18099 oo ic ieeii sense ee ecae beteeewires 6 32 HP TN Log Message Codes 20000 20999 oo ic cess oab besa eae eee e eae eed ole 6 38 HP FIP Log Message Codes 21000 21999 34 oyeeecaaie tao ete ceseeeaeeeeoees 6 42 HP ARM Log Message Codes 24000 24999 1 0 0 cece eee e eee eee eens 6 42 HP ARP Log Message Codes 25000 25999 es 35ho ab eens deed 25 Ssesens 6 43 ICMP Log Message Codes 26000 26999 oc ct nws tone ssGdeceeeavaenewehGeewee 6 44 Location Codes 4 cus yesh ocak y renn tat p Rhee Geese hee Cee eeee rend ase 6 47 Entity INERO serasa tE e ren wens eee sedeuse weews ieee sede eee ese meets 6 47 Enti
136. efers to the state of memory May be 1007 DSAM corrupt or 1008 DSAM corrupt because of a parity error Both codes may also indicate that NS ARPA is not initialized This error message is displayed when an attempt to acquire a user record fails errorcode is a NetIPC error code This message is displayed when an attempt to open the log file fails errorcode is an FMP error code This error message is displayed when an attempt to post a log message to the log file fails errorcode is an FMP error code This error message is displayed when an attempt to post a log message to the log file fails errorcode is an FMP error code A message received by EVMON is too long This error message is displayed when EVMON attempts to truncate the message errorcodeisa Memory Manager error code This error message is displayed when EVMON encounters an error while waiting for a signal on the Event Logging Root Socket errorcode is a NetIPC error code This error message is displayed when EVMON encounters an error while attempting to create the Event Logging Root Socket Logging Codes and Messages This error requires HP notification If NS ARPA is not initialized run NSINIT If NSINIT is initialized this error requires HP notification Refer to the NetIPC error codes listed in this manual for more information Refer to the FMP error codes listed in your operating system reference manual for more information
137. elow Usage LOGCHG Either no log mask was Supply a correct log mask lt logmask gt specified or the log mask specified is illegal in some way Logging Codes and Messages 6 9 Log Message Codes The following numeric codes are printed to the log message Refer to Log Message Codes in the Overview subsection for a list of entities The entity that encountered the error is indicated in parentheses in the table s Meaning column Generic Log Message Codes 0 999 Generic Log Message Codes 0 999 This message appears together Make sure that the node name with log message code 90 points to the correct IP address PROBE attempted to resolve a Do this by running NRLIST If virtual address request and the name to address mapping is couldn t therefore IP notifies correct but there are still TCP that the address cannot be problems then check the status resolved of the remote node 30 Generic General EXEC call This error requires HP errors notification 31 Generic The path record is This error requires HP bad notification 32 Generic There is no path for This error requires HP this reference notification Generic Link LU is down If this error persists check the link interface Generic No path having This error requires HP specified field notification Generic Event message not This error requires HP supported notification Generic Header invalid This error requires HP
138. encountered an unknown z buffer length Message was not formatted FMTRCERR 18 FMTRC found an unrecognized link type Message was not formatted FMTRCERR 19 Formatted filename cannot be the same as trace filename filename 5 4 Tracing Error Messages The monitor or service id id that you specified is not correct This may be due toa typographical error The socket socket that you specified is not correct This may be due to a typographical error The time time that you specified is not correct This may be due to a typographical error The trace level 1eve1 that you specified is not correct This may be due to a typographical error You may specify a maximum of three ids You may specify a maximum of three sockets This error message may be returned if the raw trace file is corrupt or if NSTRC and FMTRC are not compatible The formatter will continue to format any remaining trace messages This error message may be returned if the raw trace file is corrupt or if NSTRC and FMTRC are not compatible The formatter will continue to format any remaining trace messages The same file name was specified for the trace file as was specified for the formatted file If you are running FMTRC interactively correct the id and try again If you are using a command file edit the file and rerun FMTRC If you are running FMTRC interactively correct the socket and try again If you are using a
139. equires HP to RPM protocol or the length of the packet is too long Network transport error RPM received a NetIPC error ipcerror when it tried to send or receive an RPM packet Incompatible version number ID The RPM version number in the RPM message packet is not the same as the version number for RPM installed at the local node Logging Codes and Messages notification Refer to the NetIPC error codes in the Numeric Error Codes section of this manual for more information Make sure that the RPM versions are compatible If not update the older system LogMessage 18016 XX XX XX 18017 XX XX XX 18018 XX XX XX 18019 ipcerror xx XX a E RPM option or request The option specified in the RPMCreate Call or the request specified in the RPMControl Call is unsupported RPMCreate ca message too ca Bad parameter in opt array parameter One of the following problems has occurred in an RPMControl Call 1 Invalid request code 2 Incorrect readdata or wrtdata length OR One of the following problems has occurred in an RPMCreate call The options are not specified in the correct order More than one Group 2 option is specified More than one Group 4 option is specified The string specified in the FmpSetWorkingDir option is not a valid directory or has an illegal length must be 1 63 bytes The option array has an illegal structure The length of the string being
140. er defined data type ASCII or BINARY was refused Either APPEND or OVERWRITE was specified for an existing target file with a data type different from that requested or the target computer does not support files of this data type The user defined record type FIXED or VARIABLE was refused Either APPEND or OVERWRITE was specified for an existing target file with a record type different from that requested or the target computer does not support files of that record type The user defined record size value RSIZE was refused APPEND Or OVERWRITE was specified for an existing target file with a record size different from that requested The user defined file size value FSIZE was refused OVERWRITE was specified for an existing target file and the target computer could not change the file size An attempt was made to send a sparse file with variable length records to a target computer that does not support this file type or if the target computer is an HP 3000 a previous file equation may have been given that contains attributes which conflict with the user defined file attributes Program Specific Error Messages Verify that there are sufficient resources on the target computer and try again Verify that the file exists and that the name is correct and try again Verify that the file exists and that the name is correct and try again This is an informational message only No action is necessary
141. er to the accompanying RTE error code for more information Log on to an account with superuser capabilities 4 39 166 NSINIT Error opening output file Error is errornum 167 NSINIT WARNING Problem with Memory Manager RN 168 NSINIT No RN available for Memory Manager Aborting 200 NS WARNING required monitor not found 201 NSINIT ERROR necessary monitor not found Aborting 202 NS Error No ID Segment for monitor PGMAD 203 NS Error aregister bregister allocating class number CLRQ 204 NS Error aregister bregister deallocating class number number CLRQ 4 40 NSINIT could not open an output file A Pascal error is returned in errornum This is an informational message that occurs at shutdown One resource number may still be allocated This message may also indicate other Memory Manager problems MMINIT reported a resource number error during DSAM initialization DSAM is not allocated This error may also indicate a Memory Manager problem NSINIT could not schedule a required monitor NSINIT will complete successfully but the service provided by the unscheduled monitor will not be available NSINIT could not schedule a monitor that is necessary for the successful operation of NS ARPA NSINIT has deallocated resources and terminated NS ARPA is not initialized NSINIT could not find the ID segment for
142. er will still be receiving messages from NS ARPA 1000 User input was entered in Enter a valid response response to an NSINIT prompt for which it was not valid Program Specific Error Messages 4 55 9001 NS INPUT ERROR Prompt and response from input file are NSINITprompt useresponse Error is NSINITerror 9002 NS Input not within Range Input must be between xx and yy 9003 kk Invalid Input 9004 NS Invalid Input Enter one of r1 r2 r3 r4 r5 9005 NS ERROR errornum opening filename 9006 NS Error errornum Opening the input device for writing Aborting 9007 NS ERROR errornum opening filename Opened LU 1 as log file 9008 NS End of file encountered Aborting 9009 NS ERROR Edit OUTPUT file before using it to initialize NS 4 56 The user input entered useresponse is invalid for the NSINIT prompt NSINITprompt Invalid integer input was entered The user input entered is invalid for the NSINIT prompt If you are using NSINIT interactively NSINIT will reprompt If not NSINIT will print more messages and then abort The user input entered is invalid for the NSINIT prompt r through r5 are valid responses If you are using NSINIT interactively NSINIT will reprompt If not NSINIT will print more messages and then abort A Pascal error occurred when NSINIT attempted to open the file nam
143. eric Error Codes section of this manual for more information Refer to the NetIPC error code in the Numeric Error Codes section of this manual for more information Refer to the NetIPC error code in the Numeric Error Codes section of this manual for more information xx and yy are fields of the log record header xx will be one of the following WILL WONT DO or DONT yy is the unknown option that was received This error requires HP notification xx is a field of the log record header xx is the unknown TELNET command This error requires HP notification 6 41 HP FTP Log Message Codes 21000 21999 The following codes are printed to the log file logDevice specified when running EVMON when the Entity is for FTP Some of the log message codes are followed by error codes returned by NetIPC Refer to the NetIPC error codes for more information Fields that are indicated by xx contain values that are for HP internal use only These errors and the xx values should be reported to HP There may be other undocumented messages in the log file These are diagnostic messages for HP internal use only As long as there are no problems with the ARPA services then ignore these messages If there are problems your HP representative will analyze and interpret those messages HP FTP Log Message Codes 21000 21999 21001 xx xx xx FTP internal error This error requires HP notification 2100
144. ernal error An unexpected error was returned to RPM from another internal NS ARPA routine Bad RPM packet structure RPM received an internal packet Check the log file for other errors possibly from NetIPC and refer to the documentation on those errors The structure of the RPM message packet is incorrect which is not formatted according Retry the call If the problem to RPM protocol or the length of the packet is too long Network transport error RPM received a NetIPC error when it tried to send or receive an RPM packet Incompatible version number ID The RPM version number in the RPM message packet is not the same as the version number for RPM installed at the local node Unsupported RPM option or request The option specified in the RPMCreate Call is not supported or the request specified in the RPMControl call is not supported 10 Insufficient memory to create a child program 1 There is not enough DSAM to create a new child program 2 There are no more ID segments for another program to run 3 The RPM child table is full and another child program cannot be created 2 28 Numeric Error Codes persists call your HP representative Check the log file for NetIPC errors Refer to the NetIPC error codes in this section for more information Make sure that the RPM versions are compatible If not update the older system Correct the option or request code ee E 17 18 19 2
145. ervice requirements for the socket being created e g by requesting smaller message sizes 4 determine if some of the other programs running on the system can release some of their NS ARPA resources Check the opt parameter to make sure that the Addopt call used to insert the option request contained the intended values Check that the TCP address is within the legal range The process must release one of the socket descriptors or destination descriptors that it owns and then retry the request One or more of the following actions may be taken 1 The calling process may release one or more of the path report descriptors that it owns thereby freeing up some path record storage space and then try the request again 2 the calling process may also request that some other process running in the system release some of its destination descriptors or 3 the System Manager may be asked to configure the system with more memory allocated for path record storage Numeric Error Codes 2 11 2 12 Numeric Error Codes Message size option error An illegal value was specified in the opt parameter for either the maximum send or maximum receive size option The value specified was probably less than or equal to zero Data offset error An illegal value was found in the offset option in the opt parameter Duplicate option At least one of the options in the opt parameter was specified twice Connection queued opt
146. essage type was This error requires HP known but the code was not notification 3134 IP Could not get a path for this Increase the number of IP path ICMP message records during NS ARPA initialization IP The IP address is not an This error requires HP address of the local machine notification This error indicates that internal inconsistencies exist 3137 IP The local node has no local This error requires HP IP address on the given DCN notification This error indicates that internal inconsistencies exist 3138 IP The down PID Path This is an informational associated with a remote node message only However if it on a DCN has changed due to persists this error requires HP processing a path report or an notification inbound message This mapping was supposed to be static 3139 IP An ABORT_DPATH event The IP gateway or destination message was received on the DCN does not respond or is unknown Ensure that the node is in the gateway table or that it is on a LAN and is communicating with other nodes 3148 IP A Transit Time to Live Lengthen the hop count to the exceeded ICMP message was destination or correct the routing received to the destination 3149 IP Reassembly timer expired Lengthen the hop count to the destination 3150 IP A Destination Net Correct the routing at each IP Unreachable ICMP message hop along the route Ensure was received that the GT Gateway Table is correct at eac
147. et that encountered the error and the yy field contains the socket_kind field of the socket This is an NS ARPA internal error OUTPRO received a signal indicating that a VC socket had an exception on it but the socket was not in a state that permitted that kind of signal The xx field of the log record header contains the global socket descriptor of the socket that encountered the error and the yy field contains the socket_b state field of the socket This is an NS ARPA internal error 6 50 Logging Codes and Messages This error requires HP notification This error requires HP notification This error requires HP notification This error requires HP notification OUTPRO received a signal indicating that a VC socket had data on it but the socket was not in a state that permitted that kind of signal The signal was ignored The xx field of the log record header contains the global socket descriptor of the socket that encountered the problem and the yy field contains the socket_b state field of the socket This is an NS ARPA internal error OUTPRO received a signal indicating that a VC socket had an undefined signal on it The signal was ignored The xx field of the log record header contains the global socket descriptor of the socket that encountered the error and the yy field contains the socket_b state field of the socket This is an NS ARPA internal error OUTPRO was unable to dequeue outbound conn
148. etIPC or the NS ARPA multiuser software Fields that are indicated by xx contain values that are for HP use only Errors that include these fields usually require HP notification the values contained in these fields should be reported to HP The NS ARPA multiuser errors are listed in a separate table in a later subsection Multiuser Log Message Codes 2000 2999 HP NFT Log Message Codes 100 599 O Message Meaning ation 100 xx XX XX DSCOPY received a fatal internal This error requires HP error notification 101 ipcerror muerror 0 DSCOPY was unable to initialize Refer to the accompanying This error probably occurred NetIPC error code ipcerror because of a lack of user and multiuser error code records or multiuser session muerror for additional table entries information DSCOPY received an incorrect This error requires HP message while waiting for an notification ANFT message This error indicates that a coding error exists in the NFT software DSCOPY received an incorrect This error requires HP message while waiting for an notification AINIT message This error indicates that a coding error exists in the NFT software DSCOPY received a message of This error requires HP the wrong length This error notification code indicates that a coding error exists in the NFT software or in the lower layers of NS ARPA ipcerror 0 DSCOPY received a NetIPC Refer to the NetIPC error code error ipcerror on the
149. eway information in your answer file as described above and rerun NSINIT Edit the answer file and correct the error This error requires HP notification This error requires HP notification This error requires HP notification This error requires HP notification 4 51 kk 641 NSINIT IP PIDLIST table allocation error kk 642 NSINIT IP LIPADLIST table allocation error kk 643 NSINIT IP Enter Critical failed kk 644 NSINIT IP Proto Domain Rec init error kk 646 NSINIT LAN LAN Table Initialization error kk 650 NSINIT 802 Bad Value E or NE expected kk 652 local address terminating NSINIT IP No NSINIT 653 NSINIT Error Driver type is not 67 for IEEE 802 3 link LU is lu 654 NSINIT RTE error on XLUEX call is lu LU kk 801 NSINIT CLRQ error A and B registers are aregister bregister kk 802 NSINIT Class Write Error Error is errornum 4 52 Internal error Table space could This error requires HP not be allocated for the number notification of IP Appropriate Next Hop ANH records required Internal error Table space could This error requires HP not be allocated for the number notification of local IP addresses specified Internal error An error was This error requires HP detected while entering critical notification Internal error Table space could This error requires
150. fer to the appropriate operating system manual to determine the meaning 15 Illegal file name This error is reported by the file system at the reporting node Refer to the appropriate operating system manual to determine the meaning Illegal type or size 0 This error code is reported by the file system at the reporting node Refer to the appropriate operating system manual to determine the meaning Illegal read write on type 0 file This error is reported by the file system at the reporting node Refer to the appropriate operating system manual to determine the meaning Bad entry number in RFAM Check your program code to Indicates that the file was never make sure that the file access opened correctly or the calls are used correctly pseudo DCB in the user program has been destroyed or the specified pseudo DCB is incorrect due to a programming error or the DCB for this file access call was released when the same file was opened to another DCB within the program No internal table space in RFAM Close some files before opening An attempt was made to open any more files more files than the version of RFAM used at the destination node can handle Internal RFAM tables invalid Contact your HP representative On DcRET the specified file size The remote file create is negative subroutine does not allow a negative file size because a communication line error may occur which would leave all available
151. ference Manual Numeric Error Codes 2 15 Numeric Error Codes Timed out The calling process s request timed out The request was either an IPCSelect call or a NetIPC call issued against a socket that was in synchronous mode the default mode for NetIPC sockets Timeout errors that occur on calls issued against VC sockets do not concern the protocol or connection they reference protocols use their own timers to determine if a connection is not functioning reasonably IPCRecv expected An attempt was made to manipulate a VC socket whose corresponding connection had been initiated with IPCConnect but whose successful establishment had not been verified via IPCRecv A user cannot send on a VC socket that was created with IPCcConnect without first having called IPCRecv to complete the establishment sequence Aborted by peer The connection referenced by a VC socket has been aborted by the protocol handler on the node at the other end of the connection The remote protocol handler may have initiated the abort because the user of the connection told it to or because the remote process aborted Connection aborted The connection underlying a VC socket has been aborted by the protocol handler running on the local node because it was unable to contact its peer protocol handler at the remote end of the connection This error may be returned when 1 the remote node is down 2 some network links are malfunctioning
152. ference Manual Describes the 4 3 Berkeley Software Distribution Interprocess Communication BSD IPC facility on the HP 1000 BSD IPC is a set of programming development tools originally developed by the University of California at Berkeley UCB BSD IPC on the HP 1000 offers a programmatic interface for multi vendor connectivity to other systems with BSD IPC 4 3 5958 8523 NS Message Formats Reference Manual Describes data communication messages and headers passed between computer systems communicating over Distributed System DS and Network Services NS links 5958 8563 NS Cross System NFT Reference Manual Provides cross system NFT information It is a generic manual that is a secondary reference source for programmers and operators who will be using NFT on NS ARPA 1000 NS3000 V NS3000 XL NS 9000 NS for the DEC VAX computer and PC PC NFT on HP OfficeShare Network Information provided in this manual includes file name and login syntax at all of the systems on which NS NFT is implemented a brief description of the file systems used by each of these computers and end to end mapping information for each supported source target configuration DEC and VAX are U S registered trademarks of Digital Equipment Corporation Conventions Used in this Manual NOTATION nonitalics italics DESCRIPTION Words in syntax statements that are not in italics must be entered exactly as shown Punctuation characters other than brackets b
153. for more information producer connection xx ipcerror The producer PRODC received Refer to the NetIPC error code a NetIPC error ipcerror on for more information the initiator connection xx ipcerror The producer received a NetIPC Refer to the NetIPC error code error ipcerror on the for more information consumer connection 202 XX XK XK XX The producer received a fatal This error requires HP internal error notification 203 xx ipcerror 0 0 The producer noted a NetIPC Refer to the NetIPC error code error ipcerror while performing an IPCSelect call 6 12 Logging Codes and Messages 204 XX XX XX XX The producer received a This error requires HP message of the wrong length notification This error code indicates that a coding error exists in the NFT software or in the lower layers of NS ARPA 205 xx xx 0 0 The producer received an This error requires HP incorrect message This error notification code indicates that a coding error exists in the NFT software 206 xx 0 0 0 The producer was unable to This error will occur if the attach to a session No logon session in which DSCOPY is was given for the source file and running is prematurely the source node is local terminated If the session was not prematurely terminated this error requires HP notification 207 xx ipcerror 0 0 The producer received a NetIPC Refer to the NetIPC error code error ipcerror while for more information attempting to create a call
154. g Codes and Messages persists notify your HP representative 20511 xx yy 0 20512 0 xx yy ipcerr xXx yy ipcerr 0 0 ipcerr 0 0 ipcerr xXx yy 20517 0 xx yy 20518 0 IAC xx TELNET server program failed to find its context information TELNET server program failed to set up the pseudo terminal driver connection TELNET server program received a NetIPC error from an internal ITPCSelect call TELNET server program received a NetIPC error from an internal IPCShutDown call for a network socket TELNET server program received a NetIPC error from an internal IPCShutDown call ona socket for a pseudo terminal LU TELNET server program received a NetIPC error from an internal IPCSend call ona network socket TELNET server program received an unknown TELNET option from the network TELNET server program received an unknown TELNET command from the network Logging Codes and Messages The yy field of the log record header contains the server s ID segment address This is an internal TELNET server error This error requires HP notification xx and yy are fields of the log record header xx contains the pseudo terminal LU number and yy contains the socket ID for the pseudo terminal driver Reset the pseudo LU using control request and try again Refer to the NetIPC error code in the Numeric Error Codes section of this manual for more information Refer to the NetIPC error code in the Num
155. g log file errorcode EVMON Error writing to log file errorcode EVMON Unexpected error cleaning up message queue errorcode EVMON Error log terminating errorcode EVMON Unexpected error creating a socket errorcode This message is displayed after a signal is set on a socket and an attempt to read the data appended to that socket fails errorcode is a Memory Manager error code errorcode is a Memory Manager error code A code of 1007 indicates that DSAM is corrupt a code of 1008 indicates that DSAM is corrupt because of a parity error Both codes may also indicate that NS ARPA is not initialized This error message is displayed when an attempt to acquire a user record fails errorcode is a NetIPC error code This message is displayed when an attempt to open the log file fails errorcode is an FMP error code This error message is displayed when an attempt to post a log message to the log file fails errorcode is an FMP error code A message received by EVMON is too long This error message is displayed when EVMON attempts to truncate the message errorcodeisa Memory Manager error code This error message is displayed when EVMON encounters an error while waiting for a signal on the Event Logging Root Socket errorcode is a NetIPC error code This error message is displayed when EVMON encounters an error while attempting to create the Event Logging Root Socket Logging Codes and Messages T
156. gentaewed pet de ws Rev 6 1 6100 3 4 Preface Hewlett Packard Network Services for the HP 1000 NS ARPA 1000 provides the networking software that allows HP computer systems to communicate with each other The NS ARPA 1000 Error Message and Recovery Manual lists and explains in a tabular form all of the error codes and messages that can be generated by NS ARPA 1000 This manual should be consulted by programmers and users who will be writing or maintaining programs for NS ARPA 1000 systems Because it contains error messages generated by the NS ARPA 1000 initialization program NSINIT and other network management programs it should also be consulted by Network Managers The Introduction to this manual presents an overview of the NS ARPA 1000 error messages described in this manual This section also suggests that the utility subroutine DSERR be utilized after using certain NS ARPA 1000 calls to provide extended error information You are encouraged to read the Introduction before using the other sections Organization Section 1 Introduction presents an overview of the NS ARPA 1000 error messages described in this manual Section 2 Numeric Error Codes lists NS ARPA 1000 errors that are categorized according to the program call or parameter that returns them The error codes listed are APLDR Error Codes DLGON DLGOF DLGNS Error Codes DSCOPY Error Codes ERR Error Codes HELLO BYE Error Codes NetIPC Error Codes PTOP E
157. h gateway 3151 IP A Destination Host Correct the routing at the final IP Unreachable ICMP message gateway was received Logging Codes and Messages 6 23 3152 3153 3157 3158 3159 3162 3164 3166 6 24 IP A Destination Protocol Unreachable ICMP message was received IP A Destination Port Unreachable ICMP message was received This error indicates that internal inconsistencies exist IP A source quench ICMP message was received A remote destination or gateway dropped a message because of congestion IP An ICMP redirect message was received for a remote IP network The gateway being used for the remote network had to use another gateway on the directly connected network IP An ICMP redirect message was received for a host The destination host is on the same network as the local node but the local node routed traffic through an IP gateway IP An ICMP echo request message was received An echo reply will be sent IP An ICMP time stamp request message was received A remote node requested a time stamp reply IP An ICMP information request message was received Logging Codes and Messages This error requires HP notification This error requires HP notification If this error persists route traffic in such a way that the congested nodes are relieved To shorten the path a message takes to the remote network use the
158. he action to be taken Contact the Network Manager for the source computer or try again later Contact the Network Manager for the target computer or try again later This error is logged to a log file and is informational only No action is necessary The file or files will be copied but the source files will not be purged DSLIN Error Messages The following error messages are returned to the current log device when an error is encountered by the program DSLIN Some errors are returned during the DSLIN dialogue others are returned when DSLIN attempts to satisfy the buffer size requested in response to the prompt COMMUNICATIONS BLOCK SIZE 1024 after the dialogue has ended DSLIN will continue to initialize the link after these errors occur however errors of this type represent conditions that may make the link impossible to use without encountering further errors DSLIN Error Messages During a request for initialization No action is necessary BREAK FLAG SET LU nn HAS BEEN INITIALIZED WITH BUFFER SIZE XXXX THE BOARD ON LU nn DOES NOT CONTAIN BISYNC FIRMWARE BOARD TYPE X STATUS vvvvv SESSIONS STILL OPEN ON LU xxx THE LU WAS NOT CLOSED PLEASE ENTER THE LU A COMMAND READ CANNOT LOCK LU xxx DSLIN has received a break request The link is up Board contains wrong firmware Status returned from the driver indicates an error INITIALIZE BOARD GET PARAMETERS PRIMAR
159. he error persists this error record This might indicate that requires HP notification DSAM is corrupt 6 46 Logging Codes and Messages Location Codes The following codes are returned in the Location field of the log record header These codes are listed according to the Entity that is printed in the Entity field of the log record header when they occur Entity INPRO The following codes are printed to the Location field of the log record header when the event class is Warning Class 3 Error Class 4 Disaster Class 5 or RsrceLim Class 6 and the Entity printed in the Entity field is INPRO INPRO Location Codes INPRO has encountered a No If this condition persists Abort return from its Class I O NS ARPA must be shutdown GET call If the No Abort return and reinitialized If shutdown indicates that INPRO s class and reinitialization do not solve number is no longer valid or if the problem notify your HP field two successive Class I O GET office calls encounter a No Abort return the event class is logged as Disaster and INPRO is aborted UPLIN will reschedule INPRO after performing all possible cleanup A and B register information is returned in the xx and yy fields of the log record header This is an NS ARPA internal error While starting up INPRO was unable to find a valid class number for its use in the DSAM storage area After logging this message INPRO will abort UPLI
160. hen the NS ARPA software encounters a Pascal detected runtime error These errors require HP notification 6 4 Logging Codes and Messages Location The location field is a one word integer that indicates the section procedure module or process of the Entity s software that logged the event Some Entities use the location code when the event class indicates a warning Class 3 error Class 4 disaster Class 5 or resource limit condition Class 6 The Entities that use the location code in this way are INPRO OUTPRO HP PROBE PROSW SIGMOD SREG xx and yy Fields The xx and yy fields are for HP internal use only However some of the error messages meanings do explain the values of these fields when appropriate LAN driver error codes are printed to the yy field These errors are explained in the HP 12076A LAN 1000 Link Node Manager s Manual Log Mask The log mask is the octal value of EVMON s log mask at the time the log record was sent Process Name The process name is the five character name stored in the ID segment of the process that sent the log message such as INPRO or OUTPRO the inbound and outbound message handlers Session The session field is the session ID the scheduling terminal s LU of the session that scheduled the process in the previous field For NS ARPA subsystem processes INPRO OUTPR TIMER and the NS ARPA monitors this is the system session ID For NetIPC proces
161. his error requires HP notification If NS ARPA is not initialized run NSINIT If NS ARPA is initialized this error requires HP notification Refer to the NetIPC error codes are listed in this manual for more information Refer to the FMP error codes listed in your operating system reference manual for more information Refer to the FMP error codes listed in your operating system reference manual for more information EVMON will clean up queue and socket if possible otherwise it will terminate If EVMON terminates restart If it persists this error requires HP notification Refer to the NetIPC error codes listed in this manual for more information Refer to the NetIPC error codes listed in this manual for more information 6 7 The next table lists the EVMON error messages that are printed to the log file These errors correspond in meaning to those listed in the previous table EVMON Errors Printed to the Log File EVMON DS SBGet errorcode EVMON Enter critical errorcode EVMON FindUserRec errorcode EVMON Fmp Open errorcode EVMON FMPPost errorcode EVMON FMP Write errorcode EVMON SBDrop errorcode EVMON SoAwaitSig errorcode EVMON SoCreate errorcode 6 8 This message is displayed after a signal is set on a socket and an attempt to read the data appended to that socket fails errorcode is a Memory Manager error code errorcode is a Memory Manager error code that r
162. ication This error requires HP notification This error requires HP notification This error requires HP notification This error requires HP notification This error requires HP notification This error requires HP notification This error requires HP notification This error requires HP notification This error requires HP notification 6 63 ASCII Log Messages The following ASCII messages are printed to the log file by certain software modules procedures processes and protocol handlers They are listed according to the Entity that is printed in the Entity field of the log record header when they occur Entity HP IFP The following codes and or messages are printed to the log file when the Entity is HP IFP IFPOB Outstub received _ This procedure should not be This error requires HP spurious emsg called It would only be called notification by a faulty protocol handler IFPOB GetRouterAdr Could not read the IFP header This error requires HP err msg lost field from DSAM notification IFPOB NRV error msg Could not get the NRV entry for Reinitialize your node to add the lost source destination node router address If the router address is already in the NRV this error requires HP notification IFPOB IP path error No IP path reference on which Make sure that your have as msg lost to send the message many IP path records as sockets If you do and the system is heavily used this err
163. ication was invalid This is an NS ARPA internal error Could not purge the nodal path This error requires HP report part of an entry in the notification Nodal Registry database This is an NS ARPA internal error Had trouble inserting a nodal This error requires HP path report into a Nodal Registry notification database entry This is an NS ARPA internal error Could not update the length This error requires HP fields of a Nodal Registry notification database entry This is an NS ARPA internal error The amount of data received as This error requires HP part of a Virtual Address request notification was incorrect This is an NS ARPA internal error Could not read in from DSAM a_ This error requires HP Virtual Address requested notification passed to Probe by the LAN This is an NS ARPA internal error Had unexpected trouble trying This error requires HP to write a Probe Virtual address notification reply message into DSAM prior to transmission This is an NS ARPA internal error Had trouble setting up a Probe This error requires HP name request message and had notification to terminate a node name look up transaction This is an NS ARPA internal error Request to start a timer for a This error requires HP Probe name request transaction notification failed This is an NS ARPA internal error Could not set up a Probe name This error requires HP request message as part of a
164. ies DS 3000 request rejected no TCBs available DS 3000 request rejected operator command is too long Error occurred on class I O EXEC call The ASCII error code from the A and B registers is displayed A continuation request was received from DS 3000 after the original request had timed out An error occurred while replying to a DS 3000 request The last part of a request with continuations arrived and the data from previous portions of the request was missing A DS 3000 request was received with a class and stream number that was unknown to DS 1000 RPCNV received a reply from a DS 1000 monitor which contained an invalid DS 1000 stream number A DS 3000 request was received while the local node was quiescent The monitor required to process the request was not enabled or was unavailable Same as DS08 5 except not from MAST All of the transaction status table TST entries are in use No transaction control block TCB s were available for use An operator command request from DS 3000 was too long 3 20 Alphanumeric Error Messages See specific error code Try increasing the slave timeout See specific error code Contact HP Contact network manager DS internal error Report to your network manager Run DINIT or use the DSMOD R restart command to re initialize the node Check to see if the monitor is RP ed Then use DSMOD s s command to schedule and enab
165. ing the problem is due to corruption of the path report and not a system software error try shutting down the referenced destination descriptor and then performing another IPCLookUp If the same error is returned when the new path report descriptor is used this error requires HP notification One or both of the following actions may be taken 1 Verify that the data length specified was the data length intended 2 verify that the size specified was not larger than the maximum permissible send or receive size of the socket One or both of the following actions may be taken 1 Verify that the descriptor specified was the intended one 2 verify that the call used to create the path report descriptor actually succeeded Protocol mismatch The call socket referenced in an IPCCreate Call is not bound to any of the protocols that the destination descriptor references i e there is no way to use the protocol referenced by the call socket to access the socket referenced by the path report descriptor Socket type mismatch The path report descriptor specified in an IPCConnect call does not reference a remote call socket This error occurs when the remote socket is supported by a system that supports socket kinds other than call and VC sockets Not a call socket The descriptor specified in the field reserved for socket descriptors was not a socket descriptor No sockets available The calling process reque
166. ion Run NSINIT to shutdown NS ARPA Make sure LAN LUs are correct Reinitialize NS ARPA Check the RTE error description in the RTE manuals Check the error code in Appendix A of the HP 12076A LAN 1000 Link Node Manager s Manual 12076 9002 HP PXP Log Message Codes 5000 5999 HP PXP Log Message Codes 5000 5999 teatessage Meaning aimn 5001 HP PXP PXP path exhausted This is an informational code only The protocol will recover 5002 HP PXP No IPATH record Run NSINIT to shutdown NS If found This is an NS ARPA the error persists reboot your internal error system If rebooting does not solve the problem this error is internal and requires HP notification 5003 HP PXP Bad packet length This is an informational code only The protocol will recover 5004 HP PXP Service class not This is an informational code supported only The protocol will recover 5005 HP PXP Path port already This is an informational code existed only The protocol will recover 5006 HP PXP Server s queue is full This is an informational code only The protocol will recover However if this error persists you could reinitialize the node increasing the number of NS ARPA programs 5007 HP PXP Internal error Run NSINIT to shutdown NS ARPA If the error persists reboot your system If rebooting does not solve the problem this error requires HP notification 5008 HP PXP Unknown e_msg This Run NSINIT
167. ion and Initialization Manual REMAT Error Messages These ASCII error messages are returned to the current log device when an error is encountered by REMAT REMAT is described in the NS ARPA 1000 DS 1000 IV Compatible Services Reference Manual RMOTE Error Messages These ASCII error messages are returned to the current log device when an error is encountered by RMOTE RMOTE is described in the NS ARPA 1000 D S 1000 IV Compatible Services Reference Manual Program Specific Error Messages 4 1 TELNET User Error Messages The following error messages are returned to the current list device when an error is encountered by the TELNET user program After a message is printed the user may again be presented with the TELNET prompt TELNET User Error Messages Internal TELNET error TELNET ERR 1 A connection could not be established to the target computer because of one of the following problems 1 the target computer name is incorrect 2 the target computer is not connected to the network 3 there are not enough system resources or 4 TELNET has not been initialized at the target computer Unable to connect to target computer TELNET ERR 2 The input line was greater than 80 characters Input line too long TELNET ERR 3 An opening quotation mark was found but not the closing quotation mark A TELNET command was entered incorrectly with the wrong syntax or parameter s Cannot find closing quotation
168. ion error An error was detected in the arguments regarding the maximum number of connections queued option in the opt parameter Illegal name length The name length was either too large or too small Illegal descriptor The referenced descriptor is outside of the acceptable range for descriptors Cannot name VC socket The calling process tried to name a VC socket using IPCName Duplicate name The name that IPCName tried to assign to a socket was already in use Check the Addopt call used to insert the option request to make sure it contained the intended value Check the length and offset values that were input to the opt parameter with Addopt Check arguments input to AddOpt when initializing the opt parameter Check the Addopt call that was used to put the option arguments in the opt parameter Compare the name length to the acceptable range for this parameter Determine why the value was not within the acceptable range One possible reason is that the call to allocate the descriptor failed IPCName cannot be invoked against VC sockets One of the following actions may be taken 1 Pick another name 2 wait and try again 3 if several copies of the same process are running make sure that each process has some way of generating a unique name IPCName has a random name generation facility that could be used or the calling process could wait and try again later Aborted locally The
169. ional code only The protocol will recover 14006 TCP Cannot get DSAM buffers This is an informational code only The protocol will recover 14007 TCP No listener This is an informational code only The protocol will recover 14008 TCP Retransmit retry This is an informational code exceeded only The protocol will recover 14009 TCP Memory accounting Increase memory If this does problem not solve the problem this may be an NS ARPA internal error and requires HP notification 14010 TCP Incoming segment has This is an informational code bad offset only The protocol will recover 14011 TCP Bad checksum This is an informational code only The protocol will recover 14013 TCP TCP connection has been This is an informational code dropped only The protocol will recover TCP Bad TCP path reference Run NSINIT to shutdown NS ARPA If the error persists reboot your system If rebooting does not solve the problem this error requires HP notification TCP Bad upper level protocol Run NSINIT to shutdown reference NS ARPA If the error persists reboot your system If rebooting does not solve the problem this error requires HP notification TCP Bad TCP send queue Run NSINIT to shutdown NS ARPA If the error persists reboot your system If rebooting does not solve the problem this error requires HP notification Logging Codes and Messages 6 29 14017 TCP Irrecoverable error Run N
170. ious record type setting NFT 1000 WARN 6 REPLACE overrides APPEND or OVERWRITE NFT 1000 WARN 7 Source logon or node name overrides previous setting NFT 1000 WARN 8 4 8 DSCOPY Error Messages Only APPEND OVERWRITE or REPLACE can be in effect at one time APPEND was given while REPLACE Or OVERWRITE was in effect Only ASCII or BINARY may be in effect at one time One of these options was given while the other was in effect Only APPEND OVERWRITE or REPLACE may be in effect at one time OVERWRITE was given while APPEND or REPLACE was in effect An option option was given a value while a previous value was in effect Only FIXED or VARIABLE may be in effect at one time One of these options was given while the other was in effect Only REPLACE APPEND or OVERWRITE may be in effect at one time REPLACE was given while APPEND or OVERWRITE was in effect The source logon or node name given in the copy descriptor will override the default setting for the current copy descriptor Subsequent copy descriptors will not be affected Program Specific Error Messages This is an informational message No action is necessary This is an informational message No action is necessary This is an informational message No action is necessary This is an informational message No action is necessary This is an informational message No action is necessary This is an informational mess
171. is intended for interactive users as well as programmers It should also be read by Network Managers before designing an NS ARPA 1000 network so that they will have a clear understanding of the full implications of various NS ARPA 1000 functions and features 91790 90030 NS ARPA 1000 Generation and Initialization Manual Describes the tasks required to install generate and initialize NS ARPA 1000 This manual is intended for the Network Manager Before reading this manual the Network Manager should read the NS ARPA 1000 User Programmer Reference Manual to gain an understanding of the NS ARPA 1000 user level services The Network Manager should also be familiar with the RTE A Operating System and system generation procedure 91790 90031 NS ARPA 1000 Maintenance and Principles of Operation Manual Describes the NS ARPA 1000 network maintenance utilities troubleshooting techniques and the internal operation of NS ARPA 1000 The Network Manager should use this manual in conjunction with the NS ARPA 1000 Generation and Initialization Manual This manual may also be used by advanced users to troubleshoot their applications 91790 90040 NS ARPA 1000 Quick Reference Guide Lists and briefly describes the interactive and programmatic services described in the NS ARPA 1000 User Programmer Reference Manual and the NS ARPA 1000 DS 1000 IV Compatible Services Reference Manual The purpose of this guide is to provide a quick reference for users who are alre
172. is is an informational message Although no action is necessary you may want to reload Distributed System Available Memory DSAM to use less memory Check to make sure that the correct version of MMINIT was scheduled and rerun NSINIT If the problem persists this error requires HP notification Rerun NSINIT If the error persists reboot your system and try again If rebooting does not solve the problem this error requires HP notification 141 NSINIT Overwriting of output file declined 142 NSINIT DSAM not initialized cannot deallocate it Terminating 143 NSINIT Problem DeAllocating DSAM DSAM not Deallocated DSAM State Value is xx 144 NS Word Invalid value 145 NS 1 Invalid value 146 NS 2 Invalid value 147 NS Parity Error DSAM Warning Detected in 148 NSINIT encountered error during startup shutdown Error is errornum An output file was specified that already exists A prompt was issued to inquire if the file should be overwritten and a negative response was received the file was not overwritten NS ARPA attempted to deallocate Distributed System Available Memory DSAM and DS_DeallocDSAM returned an error stating that DSAM had not been allocated This error message may be returned if 1 a problem is encountered regarding the NS ARPA state words or 2 an error is detected in the NS ARPA software NSINIT has
173. is printed to the Location field of the log record header when the event class is Warning Class 3 Error Class 4 Disaster Class 5 or RsrceLim Class 6 and the Entity printed to the Entity field is PROSW PROSW Location Codes An event message was sent to an undefined event handler port The xx field of the log record This error requires HP notification header contains the source event handler port identifier and the yy field contains the address of the call to PROSW This is an NS ARPA internal error Logging Codes and Messages 6 55 Entity SIGMOD The following codes are printed to the Location field of the log record header when the event class is Warning Class 3 Error Class 4 Disaster Class 5 or RsrceLim Class 6 and the Entity printed in the Entity field is SIGMOD Routines in SIGMOD manage several configurable and or depletable NS ARPA resources Whenever a SIGMOD routine detects that a resource needed to service the caller is depleted a resource limit notice is logged SIGMOD Location Codes An internal error was encountered while trying to lock a resource number RNRQ This is an NS ARPA internal error The system has no more UserRecords This means that no new user processes will be permitted to use any NS ARPA services until some active NS user process terminates The system has no more NameRecords Such records are needed whenever a user tries to use IPCName to name a socket NameRec
174. ize manual to determine the meaning Invalid security code This error code is reported by the file system at the reporting node Refer to the appropriate operating system manual to determine the meaning File currently open exclusively or Try again open to more than 7 programs Attempt to open type 0 file as This error code is reported by type 1 or to use DPOSN on type the file system at the reporting 0 file node Refer to the appropriate operating system manual to determine the meaning 10 Not enough or error in This error code is reported by parameters the file system at the reporting node Refer to the appropriate operating system manual to determine the meaning DCB not open on FL If this error was returned in command or attempt to replace response to the FL command a memory resident program no action is required If it was remote loading returned during a remote load attempt you have issued an illegal request you may not replace a memory resident program EOF or SOF read This error code is reported by the file system at the reporting node Refer to the appropriate operating system manual to determine the meaning Cartridge locked This error is reported by the file system at the reporting node Refer to the appropriate operating system manual to determine the meaning Numeric Error Codes 2 7 14 Directory full This error code is reported by the file system at the reporting node Re
175. ked NS ARPA is proceeding at reduced capacity Refer to accompanying error messages for more information A parity error occurred in the globals area Refer to accompanying error messages for more information A parity error has occurred in the tables area Refer to accompanying error messages for more information NS ARPA is not initialized Refer to accompanying error messages for more information An unexpected error has occurred in the NS ARPA software NSINF cannot report reliable information NSINF has been denied access to DSAM because it would be unable to report reliable information The error may be caused by a timing or state problem NSINF has been denied access to DSAM because it would be unable to report reliable information An invalid state occurred during initialization This is an informational message only No action is necessary Normal NS ARPA traffic may continue although some of the buffer area is no longer available Do not initiate any new NS ARPA traffic NS ARPA should be shut down and reinitialized Do not initiate any new NS ARPA traffic NS ARPA should be shut down and reinitialized NSINIT must be run to initialize NS ARPA NS ARPA should be shutdown and reinitialized NS ARPA should be shutdown and reinitialized Rerun NSINIT If the problem persists contact your Network Manager NS ARPA should be shutdown and reinitialized NS ARPA should be shutdown and
176. le is of inappropriate Either the TR or LL command Verify that the specified file type was given a file which is of an name is correct if the file exists NFT 1000 ERR 34 unacceptable type or use a new type 3 or type 4 file Read from input file An unknown error occurred in Verify that the input file is correct failed reading from the input file The and the file is not corrupt NFT 1000 ERR 35 file may be corrupt or the record read was too long Transfer succeeded The file copy process was This is an informational NS NFTERR 0 successful message No action is necessary 4 10 Program Specific Error Messages An internal NFT error has This error requires HP occurred notification Internal NFT error NS NFTERR 1 Unable to logon to source computer NS NFTERR 2 Unable to logon to target computer NS NFTERR 3 Unable to open or access source file or device NS NFTERR 4 Unable to connect to source computer NS NFTERR 5 Unable to connect to target computer NS NFTERR 6 Insufficient resources at source computer NS NFTERR 7 An error occurred in logging on to the source computer or no logon string was given when one was required An error occurred in logging on to the target computer or no logon string was given when one was required A file system error occurred in opening or accessing the source file Either 1 a protection violation occurred in accessing the source file or its dir
177. le it Same as DS08 5 Shut down and re initialize Increase the response to the DINIT question MAX CONCURRENT HP 3000 USERS or the NSINIT question Enter the maximum number of concurrent DS 3000 users to access this node Re initialize and increase the number of active transactions allowed Remote operator commands to DS 1000 should not be over 40 characters DS 3000 request rejected remote session monitor is not enabled DS 3000 request rejected request timeout DS 3000 request rejected slave TCB not found on cont DS 3000 request rejected system table error A HELLO BYE or KILL request from DS 3000 was rejected because Remote Session Monitor RSM was not enabled Slave timeout expired on a request from DS 3000 A slave monitor or program took too long to reply A continuation request was received from DS 3000 for which the original TCB was not found Possible malfunction in some software which caused DS 1000 IV tables to be corrupted or destroyed If your node is an RTE 6 system with session monitor RSM can be enabled at initialization These requests are not valid to nodes without RSM Check the state of the monitor or PTOP slave and retry the request If this error occurs regularly you should increase the slave timeout Contact your Network Manager Shut down and restart DS DS 3000 request rejected Same as DS07 3 Same as DS07 3 TCB list in err
178. led IEEE 802 Ethernet Path reference or IP address in question is not currently in the LAN tables IEEE 802 Ethernet LAN could not create a path record No more space in the LRT IEEE 802 Ethernet A path cannot be built within the build path routines IEEE 802 Ethernet Some internal error in calculating pathref IEEE 802 only LAN received a send request with dlen longer than the maximum packet length IEEE 802 only LAN received a data packet inconsistent length field IEEE 802 Ethernet A message came in on an unknown LU IEEE 802 Ethernet RTE EXEC call error Error codes from the A and B registers are in the xx and yy fields of the log record header IEEE 802 Ethernet The LAN driver reported an error ona write request The xx field of the log record header contains the error code field from the DVT status word The yy field of the log record header contains the entire DVT status word 6 26 Logging Codes and Messages Determine if the link is down If it is not enable the link in the NSINIT answer file and reinitialize NS ARPA This error requires HP notification If this error occurs frequently allocate more IP path records LRT size is derived from the number of IP path records If it persists this error requires HP notification This error requires HP notification If it persists this error requires HP notification If it persists this error requires HP notificat
179. line re enable command L cannot be used to re enable an X 25 pool LU DSMOD LU ERROR L NOT VALID FOR X 25 POOL LUS USE DSMOD DI TO DISABLE THE LU Abort DSMOD using the A command and then use RTE operator commands to change the status DSMOD FILE ERROR Improper response to INPUT Retry OF FILES DSMOD INVALID NAME Monitor name is not recognized Retry by DSMOD INVALID Operator entry error Retry nee You must use the DI command to disable the LU and return it to the pool DSMOD NODE SPEC ERROR Improper nodal reference value Correct initialization answers DSMOD aborted and restart DSMOD End of file or FMGR error has been detected on the input device file DSMOD READ ERROR Program Specific Error Messages The question is repeated on the error LU device The user may supply the required response from this device 4 19 DSMOD RN ERROR A required resource number Re generation with a large cannot be allocated DSMOD is allotment of resource numbers aborted may be required DSMOD TR FILE ERROR The file manager cannot Correct the file problem and process the file which was re schedule DSMOD specified in the scheduling parameters 4 20 Program Specific Error Messages MVCP3 Error Messages The following error messages are printed to the current log device when an error is encountered by the program MVCP3 MVCP3 Error Messages BAD LENGTH IN FI
180. lt If you are using NSINIT with an answer file NSINIT has aborted Correct the timeout value in the answer file as described above and rerun NSINIT If you are using NSINIT interactively enter a message level of either O or 1 or omit the message level to indicate the default If you are using NSINIT with an answer file NSINIT has aborted Correct the message level in the answer file as described above and rerun NSINIT If you are using NSINIT interactively enter N to indicate that the node is a neighbor there is a direct link to this node If you are using rerouting this field may be blank If you are using NSINIT with an answer file NSINIT has aborted Correct the response in the answer file as described above and rerun NSINIT If you are using NSINIT interactively enter MA to indicate that Message Accounting should be used in transactions to this node or omit this value to indicate the default If you are using NSINIT with an answer file NSINIT has aborted Correct your response in the answer file as described above and rerun NSINIT If you are using NSINIT interactively enter a Message Accounting timeout in the range 0 to 32767 or omit the timeout value to indicate the default If you are using NSINIT with an answer file NSINIT has aborted Correct the timeout value in the answer file as described above and rerun NSINIT 4 45 324 NSINIT NRV Table Corrupt Aborting Startup 325
181. manual for information on SAM utilization If necessary regenerate the system with more SAM An error occurred deallocating a Consult your System Manager class number Program Specific Error Messages DSMOD Error Messages The following error messages are returned to the current log device when an error is encountered by the program DSMOD DSMOD Error Messages DSMOD CLASS I O ERROR A required class number cannot be allocated DSMOD is aborted A command entered or irrecoverable error occurred DSMOD DSMOD ABORTED DSMOD END DSMOD Normal completion message The ten characters comprising the message are also returned in the 5 word temporary storage area of a scheduler s ID segment They may be recovered through the use of RMPAR If DSMOD has been aborted the five words returned are 100000B ER D SM OD This error may require regeneration with a larger allotment of class numbers Explanation will have been printed prior to this message If input from a file line number of last error also printed No action is necessary DSMOD ERROR MON The specified monitor xxxxx is Load the monitor then use XXXXX not in the system DSMOD to schedule it The monitor s status is not dormant and therefore it cannot be scheduled DSMOD ERROR XXXXX STAT OD LU ERROR Improper LU number specified or LU number does not point to the communication driver The
182. mation and rerun NSINIT If the error persists reboot your system and try again If rebooting does not solve the problem this error requires HP notification Program Specific Error Messages 803 NSINIT Length Error on Class Get NSINIT Program is prognum 804 NSINIT Exec Wait error errornum 805 NSINIT Error starting up subordinate program Error is errornum 806 NSINIT Invalid subordinate security code Program is prognum 807 NS Error on Class Get A and B registers are aregister bregister 808 NSINIT Subordinate invalid routine index Program is prognum 809 NSINIT Invalid subordinate runstring Program is prognum NSINIT subordinate program prognun received a class O message which had an improper length Subordinate program numbers 1 through 3 refer to NSPR1 through NSPR3 program number 4 refers to NSPARS NSINIT or a subordinate program received an error on an EXEC wait call NSINIT encountered an RTE error errornum starting up a subordinate program Subordinate program prognum returned an improper security code to NSINIT immediately after it was scheduled Subordinate program numbers 1 through 3 refer to NSPR1 through NSPR3 program number 4 refers to NSPARS NSINIT or a subordinate program received a class O error on a class GET An RTE error code is provided in aregister and bregister This error may be returned if NSINIT is
183. meout error occurs May also occur if GRPWM s class is found to be Indicates a programming error Slave programs must call the GET routine first then either ACEPT or REJCT then call GET again An exception to this would be after an error is returned on the GET call the slave goes back to the GET call again The master program must be the one to attempt any retries This error will occur if the NRV does not provide a path back to the master program To rectify this correct the NRV and re initialize the node Since master programs are responsible for retries it is bad if the NRV does not provide suggested that the error code a path back to the master program if a request s Transaction Control Block does not exist when the slave calls ACEPT or REJCT All RTE reported error messages IOxx RNxx SCxx etc are converted to 47 Abortive error indicates something is seriously wrong A PCLOS terminated a shared slave program while one or more requests were pending from other master programs Local node not initialized or for requests made to itself local node is quiescent Same as DSOO Communications line parity or other line error same as DSO1 Communications line timeout error Same as DS02 program name and some description of the transaction on which the error occurred be returned by the slave program The master will receive a more descriptive error code and can determine the retry
184. monitor This monitor was not present in the system when NSINIT checked its ID segment NS ARPA could not allocate a class number The RTE error codes aregister and bregister were returned NSINIT could not deallocate the class number number The class number will remain allocated after NSINIT terminates Program Specific Error Messages If you are using NSINIT interactively NSINIT will repeat the prompt If you are using NSINIT with an an answer file NSINIT will have aborted rerun NSINIT This is an informational message No action is required NSINIT will attempt to clean up Make sure there are enough resource numbers in the system Try again If the problem persists reboot your system If rebooting does not solve the problem this error requires HP notification Refer to accompanying error messages to determine the name of the monitor that was not scheduled Use DSMOD to schedule the monitor if desired Refer to accompanying error messages for the name of the monitor that was not scheduled and the scheduling error Use the RTE RP command to restore the monitor program and rerun NSINIT Refer to accompanying error messages for more information If the monitor was necessary for NS ARPA operation NSINIT will abort If the monitor was not required for NS ARPA operation NSINIT will print a warning message and then continue Refer to the appropriate RTE manual for more information on the RTE error c
185. mpanying RTE call error code for more information The name in NSTRC s ID segment must be NSTRC NSTRC Error in exec call errorcode NSTRC Name must be NSTRC not progname If cloned reload as a system utility If RP ed with a different name rename to NSTRC PLOG is not supported with Abort PLOG NS ARPA NSTRC Trace file name Trace file already exists Rename or purge old trace file filename exists or specify a unique file name NSTRC VM error errorno An RTE VM error has occurred Refer to RTE error codes for more information NSTRC PLOG must be dormant NSTRC VMA open file Create a name that is less than 64 characters long or shorten the path The file name specified is not Purge or rename the file Create the name of a VMA file a new trace file The file was not loaded as a Reload the program specifying VMA program the VM option in the load command file Reload NSTRC Note be sure to purge the old NSTRC before linking Relink the program specifying VM where is a multiple of 32 5 1 descriptor may be only 64 characters NSTRC Trace file filename not a VMA file NSTRC Program not loaded as a VMA program NSTRC Unexpected program type NSTRC Program not loaded with correct VM size VMA routines can handle only 64 characters The program was not the correct type This file was not loaded with a VM size that is a multiple of 32 pages Tracing
186. n an intervening node 10 The number of retries given by the Remote Busy Retries parameter has been tried 3 6 Alphanumeric Error Messages At this point rebooting or shutdown restart are probably the only viable solutions This error occurs when the NRV is corrected online to indicate the presence of different upgrade level nodes in the network If no nodes of other upgrade levels existed during NS ARPA initialization the level converters are not scheduled To get them scheduled correct the NSINIT answer file shut down NS ARPA and reinitialize or reboot Check NRVs and eliminate the inconsistency Rebooting or shutdown reinitialization are probably the only solutions This error requires HP notification If seen infrequently may indicate a temporary overload If seen frequently may indicate an error in system generation System Manager should check 1 Too few swap tracks 2 Too little SAM 3 QUEUE made disk resident in node with heavy data traffic 4 Too few TCBs 5 The number of requests queued on a slave program s class has exceeded the limit of 10 DS08 1 TOO MANY UNACKNOWLEDGED MESSAGES BETWEEN SOURCE AND DESTINATION NODE FOR MESSAGE ACCOUNTING DS08 2 INSUFFICIENT RESOURCES DS08 3 INSUFFICIENT RESOURCES DS08 4 INSUFFICIENT RESOURCES DS08 5 NO AVAILABLE CLASS NUMBERS IN SYSTEM DSO9 0 ILLEGAL OR MISSING PARAMETERS DSO9 1 NOT ENOUGH PARAME
187. n informational UPLIN will attempt to reschedule message only No action is OUTPRO required 17003 UPLIN A program has aborted This error requires HP while executing a critical section notification of an NS ARPA routine The xx field contains the program s ID segment address The next message will print the program name The name will be valid only if the ID segment was not temporary Logging Codes and Messages 6 31 HP RPM Log Message Codes 18000 18999 The following codes are printed to the log file when the Entity is HP RPM for the Remote Process Management RPM service There are two types of RPM log message codes standard RPM and RTE A specific codes Many errors are invalid parameter errors Refer to the Remote Process Management section of the NS ARPA 1000 User Programmer Reference Manual to check the parameters Some of the log message codes are followed by error codes returned by NetIPC Refer to the NetIPC error codes for more information Fields that are indicated by xx contain values that are for HP use only When notifying HP the values contained in these fields should be reported to HP HP RPM Log Message Codes 18000 18999 18001 xx xx xx Network is down NS ARPA is Bring up NS ARPA with NSINIT either down going down or not completely up 18002 xx XX XX Illegal name length The length Correct the length parameter in in one of the following the RPM call RPMCreate parameters is either
188. n internal FTP error has occurred This error requires HP notification Verify that 1 the remote host name is correct 2 the remote host is connected to the network 3 that there are sufficient system resources to establish a connection or 4 that FTP is running on the remote host A connection could not be established to the remote host because of one of the following problems 1 the remote computer name is incorrect 2 the remote computer is not connected to the network 3 there are not enough system resources 4 FTP has not been initialized at the remote host An FTP runstring was entered incorrectly with an invalid option Check syntax and try again Verify that you have specified the right remote host An FTP runstring containing more than one host parameter was entered FTP will use the first host parameter Use HELP if necessary Check syntax and try again An FTP command was entered incorrectly without enough characters to make it a legal FTP command An invalid FTP command was Use HELP if necessary Check entered syntax and try again FTP server did not recognize the Check the syntax of the user user name or password that was name or verify that the password is correct and try again Try request again If problem persists exit FTP and restart FTP again An illegal reply code was received from the FTP server Legal reply codes begin with 1 2 3 4 or 5 An i
189. n type was received by the NetIPC inbound protocol handler This is an NS ARPA internal error An event message of an unexpected or unknown type was received by the NetIPC inbound protocol handler running in OUTPRO This is an NS ARPA internal error A problem was encountered trying to place an IPATH ABORTED event message into DSAM This is an NS ARPA internal error A problem was encountered trying to append an mbuf containing an IPATH ABORTED event message to a user s Call socket This is an NS ARPA internal error The DSAM state word has an unexpected value This is an NS ARPA internal error A name record that should have been linked to a socket was discovered not to be linked This is an NS ARPA internal error No space is available for the storage of connect site path reports Calls such as IPCLookUp will not complete successfully until some storage space has been released This storage space is charged against the Socket Registry s special path memory socket Logging Codes and Messages This error requires HP notification This error requires HP notification This error requires HP notification This error requires HP notification This error requires HP notification This error requires HP notification This error requires HP notification This error requires HP notification This error requires HP notification Configure more space for the storage of connect site path
190. nal Errors Some of the error messages listed in this manual are classified as internal errors These errors usually require HP notification If you receive an error of this type take the appropriate action according to the terms of your HP support contract Submitting a Service Request When submitting a Service Request to HP you should include the following information where applicable to help HP determine the cause of the error A characterization of the problem Describe the events leading up to and including the problem Attempt to describe the source of the problem Describe the symptoms of the problem Your characterization should include any RTE commands NS ARPA 1000 subsystem commands and application program source code that can reproduce the problem Obtain the version update and fix information for all software This allows HP to determine if the problem is already known and if the correct software is installed at your site Obtain screen copies of all error codes and messages that appear at the user terminal and the system console Prepare a listing of the system generation answer file the NSINIT answer file the NRINIT answer file the boot and welcome files and any additional link initialization files DSN X 25 1000 LAN etc Create copies of any trace or log files that were active when the problem occurred for your HP representative to further analyze Obtain the NSINF LU information for the LU being used
191. nclude the subsystem prefix SC to indicate that a scheduling error has occurred SC01 1 MISSING SCHEDULING PARAMETER SC0O1 2 MISSING SCHEDULING PARAMETER SC0O1 3 MISSING SCHEDULING PARAMETER SC02 0 SC02 2 ILLEGAL SCHEDULING PARAMETER SC02 3 ILLEGAL SCHEDULING PARAMETER PROGRAM NOT SCXX Error Messages ode caning ation SCXX 0 Summary of RTE scheduling Refer to the RTE SC xXx error errors descriptions SCO1 0 1 Not enough parameters EXEC Calls 11 14 DEXEC Not enough Provide additional parameters scheduling parameters have and try again been provided in the DEXEC call EXECM The scheduling EXEC Provide additional parameters call has made it to the NS ARPA and try again monitor EXECM where an error has been detected EXECW The scheduling EXEC Provide additional parameters call has made it to the NS ARPA and try again monitor EXECW where an error has been detected Illegal parameter value EXEC Calls 12 14 EXECM The scheduling EXEC Correct the parameter and try call has made it to the NS ARPA again The improper parameter monitor EXECW where one of is related to the STRING buffer the provided parameters has specification been found to be in error EXECW The scheduling EXEC Correct the parameter and try call has made it to the NS ARPA again The request length is monitor where one of the incorrect provided parameters
192. ncorrect reply code was received from the FTP server The command sequence between FTP and FTP server can be out of sequence Try request again If problem persists exit FTP and restart FTP again 4 4 Program Specific Error Messages Unable to retrieve information on local host FTP ERR 10 Not connected Please use the OPEN command first FTP ERR 11 Already connected to host Please use USER or CLOSE first FTP ERR 12 Not a valid type Only ASCII and BINARY are supported FTP ERR 13 Unimplemented command FTP ERR 14 Unimplemented option FTP ERR 15 No transfer file specified Ignoring option T FTP ERR 16 Two log files in runstring Ignoring second one FTP ERR 17 Two transfer files in runstring Ignoring second one FTP ERR 18 Same name given for log and transfer files Ignoring both FTP ERR 19 Unknown nodename No such node exists FTP ERR 20 No username or password specified Ignoring option u FTP ERR 21 Error encountered sending command to the server FTP ERR 22 FTP unable to obtain IP and port Try request again If problem address information on local persists exit FTP and restart node for sending the port FTP again command to FTP server You are currently not connected Use the OPEN command to to a remote host connect to a remote host first Use the USER command or CLOSE command first You are already connected to a rem
193. nds that will cause the remainder of the files to be copied If the source or target node is an NS for the DEC VAX system make sure the NFT buffer size is not greater than 1423 bytes Refer to the qualifying file system error string to determine action to be taken The target file name is not valid Check the target file name for the target computer syntax and try again Program Specific Error Messages 4 13 Unable to purge source file NS NFTWARN 30 Read from source file failed NS NFTERR 31 Write to target file failed NS NFTERR 32 Unable to create or open target file NS NFTERR 33 Invalid or unsupported source device NS NFTERR 34 Invalid or unsupported target device NS NFTERR 35 Unable to close target file NS NFTERR 36 Incorrect source file password NS NFTERR 38 Incorrect target file password NS NFTERR 39 Removed invalid characters in target file name NS NFTWARN 41 Target file name was truncated NS NFTWARN 42 4 14 The source file could not be purged for some reason after the file copy succeeded the MOVE option was given An unexpected source file system error occurred when reading from the source file An unexpected file system error occurred when writing data to the target file An unexpected file system error occurred in creating or opening the target file A request was made to copy a file from a non disk device This is no
194. nfigured in the DCN section An error was detected when parsing an answer file If NSINIT were being used interactively recovery would have been possible Internal error Table space could not be allocated for the required Gateway Table GT entries Internal error Table space could not be allocated for the number of IP path records specified in the startup answer file Internal error Table space could not be allocated for the number of IP Appropriate Next Hop ANH records required Internal error Table space could not be allocated for the IP global table Program Specific Error Messages If you are using NSINIT interactively enter a size that is in the range specified in the NSINIT question If you are using NSINIT with an answer file correct the segmentation size in the answer file as described above and rerun NSINIT This error requires HP notification If you are using NSINIT interactively enter each destination only once If you are using NSINIT with an answer file delete the duplicate destination network from the answer file and rerun NSINIT If you are using NSINIT interactively enter a gateway that is a member of one of the directly connected networks configured in the DCN section If the gateway was not configured in either the DCN section and it should have been you must abort NSINIT and rerun it with the correct responses If you are using NSINIT with an answer file correct the gat
195. ng ASCII error messages are returned by various NS ARPA 1000 programs Miscellaneous Alphanumeric Error Messages Message EDITR WAITING FOR LIST EDITR attempts to lock the This message is for for DEVICE lineprinter to prevent other information only no action is programs from printing at the required same time If this lock is denied because the device is in use EDITR prints this message and then suspends FM xx 0 SEE FMGR xxx _ Refer to the appropriate FMGR FOR DESCRIPTION error LU03 4 LOGICAL UNIT RQUE Via EXECM and Check password and or try LOCKED OR INVALID DEXEC the specified LU is again later PASSWORD locked to another program and or the password is incorrect or not specified the I O operation cannot be performed LU ERROR 4 character RTE Occurs if an LU which does not Specify an LU which is error code LU exist or is not a NS ARPA 1000 associated with the correct driver but has the same device NS ARPA 1000 driver This may type code is specified during also occur if NRV or the initialization Rerouting Tables are corrupt Check NRV and make the corrections with DSMOD or shut down NS ARPA using NSINIT and reinitialize LU LOCK ERROR xxxx EDITR This message may be The most likely cause of this printed when a lock is error is insufficient resource attempted on the local systems numbers assigned at system lineprinter see the error generation time message EDITR WAITING FOR LIST D
196. not successful ask the described by the path report System Manager to verify that referenced by a passed path the local node s IP address has report descriptor This could been given sufficient information occur because the local node to send messages to the remote does not know where the node Also determine which remote node s network is or protocols are supported by the because the remote node does remote node not support the same protocols as the local node 2 18 Numeric Error Codes Too many users There are not enough resources available in the system to support any new NetIPC processes Every NetIPC program requires the use of a user record User records are structures that NS ARPA uses to keep track of the sockets resource numbers and other resources allocated to its users The number of user records can be set when you respond to the Enter the maximum number of active NS programs prompt in the NSINIT program No resource numbers There are no RTE resource numbers available to allocate to the calling process Every process that uses NetIPC requires the exclusive use of one resource number The resource numbers provide the means for coordinating synchronization between user processes and the processes that implement the system s protocols Bad entry number in option parameter The calling process referenced an entry in the opt array that lies outside the bounds that were defined when the opt
197. notification Generic DSAM error in send This error requires HP routine notification corresponding card 3 internal error requires HP notification error Generic No SAM on send Retry If this error persists increase the amount of SAM allocated Generic Bad class number on_ This error requires HP send routine notification Generic Receive routine This error requires HP general DSAM error notification routine 51 Generic The LI was unable to Actions corresponding to the requeue the request to the causes are 1 wait and retry driver Possible causes are 1 this is done by the protocol TCP insufficient SAM heavy traffic or PXP 2 provide a card or 2 the device is down because change the NSINIT file to use it is an LU without a LUs that do have cards 8 this 6 10 Logging Codes and Messages ae R Receive routine can This error requires HP ie ieee DSAM notification This message appears with log Make sure that the node name message code 8 See log points to the correct IP address message code 8 for more Do this by running NRLIST If information the name to address mapping is correct but there are still problems then check the status of the remote node Logging Codes and Messages 6 11 HP NFT Log Message Codes 100 599 The following codes are printed to the log file when the Entity is HP NFT Some of the log message codes are followed by error codes returned by N
198. nternal error 1301 Had trouble resetting a timer for This error requires HP a Probe Virtual Address request notification that was being retransmitted This is an NS ARPA internal error 2500 The Probe inbound protocol This error requires HP handler received an unexpected notification kind of event message i e not a DATA INDICATION This is an NS ARPA internal error 2501 The Probe inbound protocol This error requires HP handler received a message that notification was too short to be a legitimate Probe message This is an NS ARPA internal error 6 54 Logging Codes and Messages 2701 Entity PROSW Could not read in from DSAM the preamble part of an inbound Probe message This is an NS ARPA internal error A kind of Probe message arrived that the local node does not know how to handle This is an NS ARPA internal error This error requires HP notification This error requires HP notification The outbound Probe protocol handler received an unexpected This error requires HP notification kind of timer signal This is an NS ARPA internal error The outbound Probe protocol handler received an unexpected kind of event message This is an NS ARPA internal error The stub inbound PROBE protocol handler in OUTPRO received an unexpected kind of event message This is an NS ARPA internal error This error requires HP notification This error requires HP notification The following code
199. o internal format is longer than the maximum allowed path of 559 bytes An invalid LAN address was entered after the keyword TEEE802 LAN ETHERNET A LAN address must be specified in six groups of two hexadecimal digits Groups are separated by dashes An invalid node name was entered Node names consist of three subfields Each subfield may be up to 16 alphanumeric characters long and the first character must be alphanumeric NRINIT detected an unknown protocol ID Either END or IP must appear at the end of an IP address The IP keyword did not appear after the IP address specified An invalid IP address was entered An IP address has the format ddd ddd ddd ddd Each subfield must be in the range 0 to 255 An IP address did not follow the node name Program Specific Error Messages If you are using NRINIT interactively you may start again from BEGIN or terminate and rerun NRINIT If you are using NRINIT with a text file correct the IP address in the text file and rerun NRINIT Use shorter node names node domain and or organization fields change your configuration or use different node names for the same node If you are using NRINIT interactively you may start again from BEGIN or terminate and rerun NRINIT If you are using NRINIT with a text file correct the address in the text file and rerun NRINIT If you are using NRINIT interactively you may start again from BEGIN or terminate and rer
200. o was specified Zero is reserved and may not be used An IP address was specified with a value between 224 and 255 in the first field this is neither Class A B or C You must specify a Class A B or C address A protocol ID other than 802 ETHERNET or LAN was entered after the IP keyword One of the low level DSAM handling routines has returned an error The total length of the entry is larger than the maximum allowed size This error indicates an error in the Nodal Registry table The length of the node name is larger than the maximum allowed size This error indicates an error in the Nodal Registry table Program Specific Error Messages If you are using NRINIT interactively you may start again from BEGIN or terminate and rerun NRINIT If you are using NRINIT with a text file correct the entry in the text file and rerun NRINIT If you are using NRINIT interactively you may start again from BEGIN or terminate and rerun NRINIT If you are using NRINIT with a text file change the network number to a non zero value in the text file and rerun NRINIT If you are using NRINIT interactively you may start again from BEGIN or terminate and rerun NRINIT If you are using NRINIT with a text file change the node address to a non zero value in the text file and rerun NRINIT If you are using NRINIT interactively you may start again from BEGIN or terminate and rerun NRINIT If you are using NRINIT with a
201. odes returned Also refer to accompanying error messages if any for more information Refer the RTE error codes returned in aregister and bregister for more information You must reboot in order to regain access to the class number 205 NS Error aregister bregister allocating resource number RNRQ 206 NS locking rn returned was RNRQ Error Status status 207 NS Error aregister bregister deallocating resource number number RNRQ 208 NS Error Dealloc res number Status returned was status RNRQ 209 NS Error aregister bregister scheduling monitor EXEC 210 NS ERROR monname not dormant EXEC 211 NSINIT ERROR Desired monitor already active Aborting 212 Invalid local node name Format name domain organization kk 222 NSINIT Error ierr Rping progname Terminating FMPRPPROGRAM NSINIT could not allocate a resource number NSINIT could not lock a resource number when it attempted an RNRQ call NSINIT could not deallocate the resource number number NSINIT will continue to shut down NS ARPA but the resource number will remain allocated after shutdown NSINIT could not deallocate a resource number NSINIT will continue to shut down NS ARPA but the resource number will remain allocated after shutdown NSINIT could not schedule the monitor monitor NSINIT attempted to schedule a
202. omputer where the source file or files reside If the file producer program is still active on the source computer then it will attempt to carry out the remainder of the user file copy command perhaps causing several files to be copied if wildcards were given If the file producer is no longer active the remaining files that were to be copied will not be copied An error was detected on the connection to the computer where the target file or files are to be created If this error occurs while the file producer is copying several files the current file may not have been copied successfully and an attempt will not be made to copy the remainder of the files This error will also occur when a file is copied to an NS for the DEC VAX system and the NFT buffer size is too large The existing target file could not be purged for some reason Specify an acceptable record size and try again Specify an acceptable file size and try again Verify that the target file name is correct or specify APPEND OVERWRITE Or REPLACE whichever is appropriate Specify the password along with the source file name and try again Specify the password along with the target file name and try again Free up enough disk space on the target computer for the target file and try again Determine which if any of the file or files were not copied Cause them to be copied by specifying the proper commands Specify a command or comma
203. on Monitor has not been initialized 50 51 Wrong password for Enter the correct password non session access Same as RSO5 Another program owns or has a DLGOF The session that the session Same as RS06 calling program is using was created by another program DLGON DLGNS A session which the calling program is willing to share as specified in the oride parameter exists at the requested node Log on or log off to local node No REMAT logons are permitted Same as RSO7 to the local node Local node is quiescent Same This temporary condition will be as DSOO corrected with the restart command R is issued using NSINIT Communication line parity See DSO1 for an explanation protocol failure STOP received cable disconnected or other hardware error Same as DSO1 Communication line timeout See DS02 for an explanation 53 Illegal record size Same as Indicates programming error DSO3 The inbound data buffer size must not exceed the maximum space allocated for the user buffer 2 4 Numeric Error Codes bods Wearing ation J Illegal nodal address node address not in nodal routing vector NRV table Same as DS04 Request timeout Same as DS05 System table error Same as DS07 Remote busy or resource unavailable Same as DS08 56 Illegal request or monitor not active Same as DS06 59 Illegal or missing parameters Same as DSO9 Se
204. on the child node so the child program cannot be scheduled One of the following problems has occurred 1 The child program does not exist at the child s node Either the name is incorrect or an RTE type 6 file executable program file does not exist The child program name specified in the FmpRun option 23110 does not match the name specified in progname of the RPMCreate call The length of the child program name is incorrect in namelen of the RPMCreate call Invalid program descriptor The pd parameter was not specified correctly in either a RPMControl Of RPMKil1 call Logging Codes and Messages RPMCreate Call Check the login and password parameters in RPMCreate Check the child program name and length parameters in RPMCreate Make sure that an executable program file exists at the child s node Make sure that the program descriptor is the one returned by the RPMCreate Call Also make sure that the node name specified is the same as the one in the RPMCreate Call 6 33 18009 FMPerror xx XX 18010 XX XX XX 18011 xx XX xx Security violation or device error This error message is not used in NS ARPA 1000 RPM 18012 XX XX XX 18013 XX XX XX 18014 ipcerror xx XX 18015 vn xx xx 6 34 Remote process limit exceeded One of the following problems has occurred 1 The remote node cannot handle RPM messages greater than 1024 bytes and it received a message that is greater than
205. ons of inconsistent or missing for this the NSINIT answer file Make node This error code indicates corrections to the file and that RTR information is reinitialize NS ARPA inconsistent missing 16003 Same as 16001 but LAN link Same as 16001 interface information is inconsistent missing 16004 A station address is configured Shut down NS ARPA and check but a multicast address is not the NSINIT answer file Make Probe will be disabled for this corrections to the file and LU reinitialize NS ARPA 16005 A local IP address was not Shut down NS ARPA and check configured for this node the NSINIT answer file Make corrections to the file and reinitialize NS ARPA 16006 IP path records were not Shut down NS ARPA and check configured for this node the NSINIT answer file Make corrections to the file and reinitialize NS ARPA 4 28 Program Specific Error Messages 16007 16008 16009 16010 User records were not configured for this node Sockets were not configured for this node Name records were not configured for this node Address resolution modules Probe ARP were not configured for this node Shut down NS ARPA and check the NSINIT answer file Make corrections to the file and reinitialize NS ARPA Shut down NS ARPA and check the NSINIT answer file Make corrections to the file and reinitialize NS ARPA Shut down NS ARPA and check the NSINIT answer file Make corrections to the file and reinitialize
206. or 1407 The inbound Socket Registry This error requires HP protocol handler has received notification an event message that it cannot interpret This is an NS ARPA internal error 1408 The Socket Registry could not Configure more space for the obtain enough memory to store storage of connect site path a connect site path report reports 1501 The inbound Socket Registry This error requires HP protocol handler in OUTPRO notification received an event message of an unexpected type This is an NS ARPA internal error 1502 The inbound Socket Registry This error requires HP protocol handler in OUTPRO notification received a QUERY _CONFIRM event message but could not interpret its meaning This is an NS ARPA internal error 1601 Could not read in from DSAM This error requires HP the context record for an notification IPCLookUp transaction This is an NS ARPA internal error Logging Codes and Messages 6 61 1602 Could not deallocate the mbuf This error requires HP containing the context record for notification an IPCLookUp transaction This is an NS ARPA internal error 1603 Unable to read in from DSAM a This error requires HP Nodal Path Report that Probe notification tried to locate for the Socket Registry This is an NS ARPA internal error 1604 Unable to read in from DSAM a This error requires HP nodal path report the first time notification but not the second time This is an NS ARPA internal error 1800 Had tr
207. or Alphanumeric Error Messages 3 21 Miscellaneous System Console Messages Miscellaneous System Console Messages NS 1000 LU Ju CAME UP Rerouting has just been time informed that this link LU is now functioning NS 1000 DOWN time LU lu WENT Rerouting has determined that this link LU is no longer functioning This node does not have Message Accounting or it is not initialized DS MSG MESSAGE ACCOUNTING REMOVED FROM NODE XXXXX gt gt HP 3000 INCOMING BAD BUFFER QUEX received an incorrectly formatted or corrupt message from the HP 3000 Reported by ID 66 when QUEUE is absent from the system ILLEGAL INTERRUPT FROM SC xx OCTAL No action is necessary This is an informational message appearing on the system console This is an informational message appearing on the system console This node has been declared to have Message Accounting at NS ARPA initialization and it does not have the proper Message Accounting software generated in Regenerate with MA software or do not indicate this node as an MA node at initialization Contact your Network Manager Can be corrected by either loading QUEUE or using the RP command to restore it if it was not purged I O ERROR AT xxx STATUS SeeDS ERROR COMM READ YYYYY for description QUEX CLASS ERROR aaaa_ QUEX Got the indicated ASCII error message aaaa whena class I O operation was performed gt gt QUEX EXPECTS PSI LI
208. or requires HP notification IFPOB Detected invalid Message had an invalid event This error requires HP emsg ID notification IFPIB DS Mread error Could not read the IFP This error requires HP header message from DSAM notification IFPIB DS 1000 services IFPM class number was invalid Reinitialize your node to enable not present the DS 1000 IV Compatible Services IFPIB Detected DS MAdj Could not strip the DS 1000 This error requires HP error header from the DSAM notification message IFPIB Could not Could not allocate SAM for the Check the amount of SAM allocate SAM message usage on your node If no other programs make heavy use of SAM this error requires HP notification IFPIB DS IntoSAM error Could not move the message This error requires HP from DSAM to SAM notification IFPIB Class requeue Could not requeue the message This error requires HP error from IFPM class to GRPM class notification IFPIB Detected invalid Message had invalid event ID This error requires HP emsg notification 6 64 Logging Codes and Messages IFPM Class I O error Error returned for class Refer to the appropriate RTE TOxx Requeue reference manual for information on class I O errors IFPM Detected Class I O Error returned from class Refer to the appropriate RTE error Requeue bad length reference manual for information on Class I O errors IFPM IFPM Detected bad GRPM class number is 0 This error requires H
209. or 0O 0 The NFT monitor NFTMN received a NetIPC error ipcerror while attempting to accept an incoming connection request with TPCRecvCn The NFT monitor NFTMN received a NetIPC error ipcerror when it called IPCRecv The NFT monitor NFTMN received a message of the wrong length This error code indicates that a coding error exists in the NFT software or in the lower layers of NS ARPA The NFT monitor NFTMN received an incorrect message This error code indicates that a coding error exists in the NFT software The NFT monitor NFTMN was unable to clone a consumer program The NFT monitor NFTMN was unable to clone a producer program The NFT monitor received a NetIPC error ipcerror while manipulating user record structures The NFT monitor NFTMN received a NetIPC error ipcerror when it called IPCSend The NFT monitor NFTMN received an error while logging on a session A Multi User error code is returned in muerror This error is usually caused by an invalid logon or password in the DSCOPY copy descriptor Refer to the NetIPC error code for more information Refer to the NetIPC error code for more information This error requires HP notification If it persists this error requires HP notification Verify that the consumer program is on the PROGRAMS directory or in the FMGR file domain Refer to the accompanying multiuser error muerror for additional information Verify
210. or more information Attempt to correct the LAN 1000 problem if any Try again If the error persists reboot your system If rebooting does not solve the problem this error requires HP notification Refer to accompanying error for more information Attempt to correct the LAN 1000 problem if any Try again If the error persists reboot your system If rebooting does not solve the problem this error requires HP notification Check resource number availability and rerun NSINIT If the error persists reboot your system and try again If rebooting does not solve the problem this error requires HP notification Check LUs and rerun NSINIT If the error persists reboot your system and try again If rebooting does not solve the problem this error requires HP notification Rerun NSINIT If the error persists reboot your system and try again If rebooting does not solve the problem this error requires HP notification LAN 1000 may continue handing messages to NS ARPA If it does not rebooting the system should solve the problem LAN 1000 may continue handing messages to NS ARPA If it does not rebooting the system should solve the problem Refer to accompanying error messages for more information Correct the LU and try again 4 47 400 NSINIT Warning Cannot open message file system nserrs msg 503 NSINIT WARNING May not have deallocated problem resource number 508 NSINIT
211. ords are also needed whenever a user tries to use IPCGive to give a socket to another process The system has no more SocketRecords This means that NetIPC users won t be able to create any new sockets The system has no more memory that it can allocate to newly created sockets Every socket when created is allocated some amount of memory for its exclusive use An attempt was made to create a socket of an undefined type This is an NS ARPA internal error A call socket was discovered in an undefined state This is an NS ARPA internal error A VC socket was discovered with a bad reference count This is an NS ARPA internal error 6 56 Logging Codes and Messages This error requires HP notification Configure more UserRecords Configure more NameRecords Configure more sockets Increase the amount of DSAM space allocated This error requires HP notification This error requires HP notification This error requires HP notification 1702 1703 1800 2202 2300 2400 2401 2700 3200 3700 AVC socket received an ABORT CONFIRMATION event message when it was not expecting it This is an NS ARPA internal error An attempt was made to manipulate a socket of an undefined type This is an NS ARPA internal error An ABORT INDICATION event message that referenced a call socket was received by NetIPC This is an NS ARPA internal error An event message of an unexpected or unknow
212. ormation 20205 ipcerror 0 0 TELNET user program received Refer to the NetIPC error code in a NetIPC error receiving data the Numeric Error Codes from the TELNET server section of this manual for more information 6 38 Logging Codes and Messages tostiessaze Meaning Amon 20301 xx 0 0 TELNET user program received An internal TELNET error has an Unknown Error from the occurred This error requires HP terminal interface notification 20302 xx 0 0 TELNET user program received An internal TELNET error has a No Class Number error from occurred This error requires HP the terminal interface notification 20303 xx 0 0 TELNET user program received SAM is a resource used by a Not Enough SAM error from many other programs You can the terminal interface wait for another program to release its use of SAM and then try using TELNET again If the problem persists increase the amount of SAM needed in your system 20304 xx 0 0 TELNET user program received SAM is a resource used by a Not Enough SAM Ever error many other programs There is from the terminal interface not enough SAM allocated to use TELNET Increase the amount of SAM needed in your system by regeneration or using the SAM command in BOOTEX 20305 xx 0 0 TELNET user program received An internal TELNET error has an Illegal Class Number error occurred This error requires HP from the terminal interface notification 2
213. orted 129 NSINIT Cannot open Input Device Terminating 130 Error NSINIT State Terminating 131 NSINIT must not cloned Terminating 132 NSINIT User entered ABORT sequence Terminating 133 NSINIT DSAM Already initialized Terminating 134 NSINIT Error at DSAM Initialization Terminating Parity NSINIT did not open the output file An invalid action was entered An invalid action was entered NSINIT has aborted NSINIT encountered an error when it attempted to open the input device This caused NSINIT to terminate NSINIT has an invalid value for the state word it keeps in either CheckStartConditions or CheckShutConditions This error message may be returned when an error is detected in the NS ARPA software NSINIT must be called NSINIT One of the acceptable abort sequences a or ab was entered in response to an NSINIT question causing NSINIT to terminate Although NSINIT checked the state of Distributed System Available Memory DSAM immediately prior to scheduling MMINIT to make sure that DSAM was not initialized MMINIT returned a DSAM initialized error The two state words do not agree causing NSINIT to terminate MMINIT reported a parity error in Distributed System Available Memory DSAM NSINIT attempted to deallocate DSAM and clean up any allocated resources before terminating Program Specific Error Messages This
214. ote host Use the ASCII or BINARY transfer type An invalid transfer type was specified A command not implemented on NS ARPA 1000 was specified An option not implemented on Use HELP if necessary Check NS ARPA 1000 was specified syntax and try again No file name was specified with Retry the command with a the T option in the FTP filename for the T option runstring Remember there must be no space between T and filename Check the syntax and verify that the first log file name is the correct one Use HELP if necessary Check command list and try again Two log files were specified in the FTP runstring The second log file was ignored Two transfer files were specified in the FTP runstring The second file was ignored Check the syntax and verify that the first transfer file name is the correct one The same file name was used for log and transfer file Try again using different file names for the log and transfer files An unknown remote host was specified Verify that the name specified was the correct name Use the A command of NETINF to see what nodes are connected to the network Try again specifying the login parameters The username and password were not specified for the u option Refer to the NetIPC error in Section 2 of this manual for more information FTP received a NetIPC error Program Specific Error Messages 4 5 Error encountered receiving reply code
215. otified of a corrupt message buffer in Distributed System Available Memory DSAM when it requested the state of DSAM NSINIT was notified of a parity error in the table area of Distributed System Available Memory DSAM when it requested the state of DSAM NSINIT was notified of a parity error in the global structures of Distributed System Available Memory DSAM when it requested the state of DSAM NSINIT discovered that Distributed System Available Memory DSAM was only partially initialized when it requested the state of DSAM The NS ARPA state word in Distributed System Available Memory DSAM indicated an aborted start up of NS ARPA The NS ARPA state word in Distributed System Available Memory DSAM indicated that NSINIT was aborted while it was attempting to shut down NS ARPA Program Specific Error Messages Correct the answer file and rerun NSINIT Make sure there are two E responses after the DCN section The second E is a required placeholder Refer to the NetIPC errors for a description of errornum Rerun NSINIT If the error persists reboot your system and try again If rebooting does not solve the problem this error requires HP notification Some resources may not be deallocated Refer to accompanying error messages for more information Shut down NS ARPA Check your system for memory problems Shut down NS ARPA Check your system for memory problems Shut down NS ARPA Check yo
216. ouble reading the This error requires HP preamble part of a connect site notification path report This is an NS ARPA internal error 1801 Could not read in a connect site This error requires HP path report that was stored in notification DSAM This is an NS ARPA internal error 1802 The memory manager rejected This error requires HP an attempt to purge or overwrite notification a nodal path report in DSAM This is an NS ARPA internal error 1900 This error indicates a This error requires HP configuration problem The notification information that the Socket Registry needs to construct connect site path reports cannot be found This is an NS ARPA internal error 1901 Could not store the template for This error requires HP connect site path reports into notification DSAM This is an NS ARPA internal error 2001 The Socket Registry s outbound This error requires HP protocol handler received an notification event message of an unexpected kind This is an NS ARPA internal error 2100 Unable to read a nodal path This error requires HP report from DSAM This is an notification NS ARPA internal error 2101 The Socket Registry could not This error requires HP read in either a socket name or __ notification a node name passed to it inside an mbuf The names were to have been resolved as part of an IPCLookUp transaction This is an NS ARPA internal error 6 62 Logging Codes and Messages 2102 2103 2104 2
217. our table structure and request less DSAM Your request exceeded the maximum amount allowed 4 33 117 NSINIT DSAM SHEMA too small Terminating 118 NSINIT PALC returned SHEMA Error to MMInit Terminating 119 NSINIT Error on EnterCriticalCall Error is errornum 120 NSINIT must be a SYSTEM UTILITY to Initialize or Shut Down NS 121 NSINIT State word access error Attempting partial cleanup NSINIT NS is initialized Cannot down 122 not shut 123 NSINIT NS already up Cannot start up NS in this node 124 NSINIT Partially initialized Cannot start up NS in this node 125 NSINIT Output file is the same as the Input file 4 34 The Shareable Extended Memory Access SHEMA partition size of Distributed System Available Memory DSAM is not large enough to accommodate the amount of DSAM required for this run of NSINIT This caused NSINIT to deallocate DSAM and then terminate The Distributed System Available Memory DSAM allocation routine Palc returned an error to MMINIT when attempting to set up the Shareable Extended Memory Access SHEMA partition NSINIT could not access DSAM A Memory Manager error is returned in errornum NSINIT is not loaded as a system utility An error was encountered when NSINIT attempted to retrieve the segment number from the NS ARPA state word in Distribute
218. procedure if any The slave program should go back to the GET call when any error occurs This error may occur if a class number in PTOPM s table is found to be bad or 255 requests the maximum allowed in class I O have occurred this may occur if a monitor was locked out of execution for an extremely long time for example if swap tracks were unavailable or a program locked itself into the only available partition This error will be returned to each master which had a request pending on the slave program when it was terminated This temporary condition will be corrected when the restart command R is issued using NSINIT See DS01 for an explanation See DS02 for an explanation Numeric Error Codes 2 23 0d ean ton Illegal record size same as Indicates a programming error DS03 The inbound data buffer size must not exceed the maximum space allocated by the user buffer Illegal nodal address same as See DS04 for an explanation DS04 a Request timeout same as See DSO5 for an explanation DS05 Illegal request Same as DS06 See DSO6 for an explanation System table error same as At this point rebooting or DS07 shutdown restart are probably the only viable solutions Remote busy same as DS08 See DS08 for an explanation Illegal or missing parameters Correct program calling same as DS09 parameters and re run 103 Illegal PCB PTOP Indicates a programming error Make sur
219. protocol referenced by the socket specified has indicated that the socket can no longer be supported This error will be returned only after the protocol has determined that the remote node can no longer be reached either because it has crashed or the network connecting the local node to it has become partitioned Under certain conditions this error may be reported if the network becomes heavily congested Name limit The caller attempted to assign too many names to the referenced socket with IPCName Name table full A process attempted to bind a name to a socket via IPCGive or IPCName when the system had no free name records A name record must be allocated for each name that is bound to a socket When the system runs out of name records all succeeding IPCGive and IPCName requests are rejected Name not found A process attempted to obtain a path report descriptor using IPCLookUp but the name specified in the call was not registered in the referenced socket registry No ownership The caller invoked IPCNamErase specifying a valid name but one bound to a socket that it does not own Only the owner of a call socket may purge its name Illegal registry name The caller invoked IPCLookUp passing it a node name having an illegal syntax for example too many levels of hierarchy or too many characters in one of the name parts The socket through which the error has been reported cannot be recovered and should
220. pted to Check program name or load run does not exist or is not program and try again loaded DEXEC This error is the result The program may exist as a of the special DEXEC request type 6 file but it does not code 99 used to acquire possess an ID segment Use program status If the request is the RP command to restore the directed at the local node program DEXEC will process the request locally and return this error if necessary EXECM This error occurs when EXECM The program may the program issues the DEXEC exist as a type 6 file but it does call with request code 99 to not possess an ID segment acquire program status If the Use the FMGR RP command to request is directed to a remote restore the program node EXECM processes the request and returns this error if necessary FCOPY The named file and the Specify a unique name for the attempted retry name both file at the destination node exist at the destination node FCOPY Record size too large Check record size and try again FCOPY The destination file size Correct file size and try again is negative RFMST Remote File Access Correct parameters and try Intrinsics again RFAM All the DCBs allocated Close files not needed are currently in use programmatically or by using the REMAT FL command Reloading RFAM and sizing it up will provide 6 DCBs per added page FCOPY The RTE command BR No action is required was use
221. quires HP notification This error requires HP notification This error requires HP notification This error requires HP notification This error requires HP notification If NS ARPA 1000 was not up then no action is necessary If the cause was a parity error reinitialize NS ARPA 1000 moving DSAM to unaffected memory or replace the defective memory Check if DSQ is generated into the system If not it must be 1008 1009 1010 1011 1012 1013 1014 1015 1016 Memory Manager DSAM is corrupt because of a parity error The error was discovered during initialization or shut down Memory Manager A parameter value was out of range in some Memory Manager call made by NS ARPA 1000 code This is an NS ARPA internal error Memory Manager Insufficient memory credits are currently available to charge against This error was returned to an NS ARPA 1000 protocol handler In most cases the protocol will have to dispose of the memory Memory Manager Too many memory credits would have been allocated to this socket or queueing limits were exceeded This error was returned to an NS ARPA 1000 protocol handler Memory Manager An NS ARPA 1000 protocol handler made a Memory Manager call referencing an invalid buffer ID undefined or currently free This is an NS ARPA internal error Memory Manager A request to allocate an MACCT could not be satisfied This is an NS ARPA internal error
222. r See the appropriate FS 3000 error code for an explanation of this error 4 21 Nodal Registry Error Messages The following error messages are printed to the scheduling terminal when an error is encountered by the nodal registry utilities NRINIT and NRLIST NRINIT messages are printed in the following format Line number xx column number xx error number XX lt The input that caused the error to occur is printed here gt lt The error message string is printed here gt The error number is also returned in RETURNI1 Nodal Registry Error Messages Another user is running NSINIT Rerun the utility once NSINIT to shut down NS ARPA has been restarted kk 6001 NRERR State of DSAM changed kk 6002 NRERR Nodal Registry is corrupt kk 6003 NRERR Attempt to lock tables failed 6004 NRERR You must be a superuser 6005 NRERR You must run NSINIT to set up DSAM first kk 6006 NRERR Insufficient Nodal Registry space for name kk kk 6007 NRERR NregAdd error errornum 4 22 NRINIT attempted to count the number of entries in the Nodal Registry but discovered that the NR is corrupt This is an NS ARPA internal error This error requires HP notification NRLIST or NRINIT could not lock Rerun NRLIST or NRINIT and try the Nodal Registry tables probably because no resource numbers are available from RTE The account under which N
223. r This error message is to notify the operator that a re start has occurred No operator action is required The message of a new download prints immediately afterward In addition to the program download messages listed above the following messages may be printed to system LU 1 if a file open or file read error occurs during a program download OPEN PROGL FILE ERROR nnnnn READ AM DOWNLOAD OF FILE namr AT DAY nnn hr min HAS FAILED PM The nnnnn parameter contains a FMGR error code 3 16 Alphanumeric Error Messages DS Error System Console Messages DS Error System Console Messages Message DS ERROR From Driver I O STATUS BITS yyyy are LU xxx STATUS yyyy bits 13 8 device type drv drivertype err octal 65 or 66 ZZZ bits 7 4 error type bit 3 0 for DS bit 3 1 for non DS system download or remote VCP bit 2 1 for read request bit 2 0 fora write request bit 1 1 if an error occurred bit 0 0 always NOTE PSI BISYNC link status is displayed in bits 0 3 all other bits are 0O Error codes zzz in octal are no error line failure timeout local busy message aborted remote busy o not initialized 11 wrong mode 12 illegal request 13 card failure 17 bad interrupt ID 66 The receive LU does not ID 66 Read process errors follow the transmit LU or GRPM could be caused by a timeout detected an error in the read waiting for incoming frame an process a
224. r messages if any for more information and rerun NSINIT If the error persists reboot your system and try again If rebooting does not solve the problem this error requires HP notification Check the output file and rerun NSINIT 157 NSINIT Problem scheduling MMInit Error returned is errornum 158 NSINIT Startup aborted Cleaning up 159 NSINIT Cleaning up Protocol segment reporting the error is segment 160 NSINIT ERROR NS up link initialization errors were detected 161 NSINIT Error RPing MMInit FmpRpProgram Terminating Error is errornum 163 NSINIT Invalid Network Security Code Terminating 164 NSINIT Error Scheduling MMInit Terminating Error is errornum 165 NS You must be a SUPERUSER to run NSINIT Terminating NSINIT encountered an error when it attempted to schedule MMINIT An RTE scheduling error code is returned in errornum NSINIT encountered an error while attempting to unlock the initialization resource number NS ARPA startup was aborted NSINIT attempted to deallocate NS ARPA resources before terminating A protocol segment segment returned an error to NSINIT during startup or shutdown The segment number returned in segment is for HP use only A protocol segment returned link initialization errors Not all links may be initialized NSINIT continued with startup NSINIT could not schedule MMINIT
225. r to accompanying messages if any for more information After scheduling MMINIT NSINIT was informed that MMINIT hit the Pascal error catcher This error message is returned when an unexpected Pascal error occurs DSAM was not allocated and NSINIT has terminated DSAM was found to be in an invalid state immediately after allocation NSINIT attempted to deallocate DSAM and then terminated DSAM was not initialized NSINIT encountered an error while attempting to open the output file and then aborted Program Specific Error Messages If necessary rerun NSINIT until it has completely cleaned up Rerun NSINIT If the error persists reboot your system and try again If rebooting does not solve the problem this error requires HP notification Rerun NSINIT If the error persists reboot your system and try again If rebooting does not solve the problem this error requires HP notification This is an informational message only No action is required Make sure that the correct MMINIT program is being scheduled and rerun NSINIT If the error persists reboot your system and try again If rebooting does not solve the problem this error requires HP notification Refer to accompanying error messages if any for more information and rerun NSINIT If the error persists reboot your system and try again If rebooting does not solve the problem this error requires HP notification Refer to accompanying erro
226. races and ellipses must also be entered exactly as shown For example EXIT Words in syntax statements that are in italics denote a parameter that must be replaced by a user supplied variable For example CLOSE filename An element inside brackets in a syntax statement is optional Several elements stacked inside brackets means the user may select any one or none of these elements For example B User may select A or B or neither When several elements are stacked within braces in a syntax statement the user must select one of those elements For example A fel User must select A or B or C A horizontal ellipsis in a syntax statement indicates that a previous element may be repeated For example itemname In addition vertical and horizontal ellipses may be used in examples to indicate that portions of the example have been omitted A shaded delimiter preceding a parameter in a syntax statement indicates that the delimiter must be supplied whenever a that parameter is included or b that parameter is omitted and any other parameter that follows is included For example itema itemb itemc means that the following are allowed itema itema itemb itema itemb itemc itema itemc underlining char When necessary for clarity the symbol A may be used in a syntax statement to indicate a required blank or an exact number of blanks For example SET modifier A variable When nece
227. reinitialized NS ARPA should be shutdown and reinitialized NSINIT was unable to complete NSINIT should be rerun to the shutdown of NS ARPA shutdown NS ARPA NSINIT was unable to complete the startup of NS ARPA Program Specific Error Messages NSINIT should be rerun to shutdown and reinitialize NS ARPA 4 27 NSINFERR 12 NSINIT Same as NSINIF 11 aborted during startup NSINFERR 13 NSINF An internal error occurred in the This error requires HP Internal Error NSINF software notification NSINFERR 14 NSINIT was unable to complete NS ARPA should be shutdown Warning NS ARPA is not the startup of NS ARPA Refer and reinitialized fully initialized to accompanying error messages for more information NSINFERR 15 An unexpected state of DSAM NS ARPA should be shutdown Disaster State of DSAM was reported and reinitialized is undefined Value is value The following error message may be also be received when NSINF checks the state of DSAM If this error is returned NS ARPA should be shut down and reinitialized NSINF No access to DSAM permitted Error code mmgrerror The error codes listed in the following table are returned in the errorno field of the following NSINF error string NSINF Internal configuration error encountered errorno Errorno Error Codes 16001 Link interface address routing Shut down NS ARPA and check configuration information is the NRV and DCN secti
228. returned when a Session Monitor error occurs at the local node SMXX Error Messages code arin ation MO1 FMP ERROR ON Account file bad or file not Contact System Manager CCOUN ca FILE ACCESS found M02 REQUIRED CLASS Possible generation error LOGON requires a class number UNCER NOT AVAILABLE for its own use M03 0 SESSION LIMIT Allocated SAM block for Session Wait for someone to logoff XCEEDED Control Blocks is full MO SM04 0 NO SUCH USER SUCH USER Invalid USER GROUP name Enter a valid account name 0 Se08 0 80 Secs oes 0 ILLEGAL ACCESS Invalid password supplied Enter correct password PASSWORD SM CONFLICT IN The terminal being logged onto The user s account file definition Sarit GOR OF SESSION LU has aconfiguration table entry is used This is an informational X which is a duplicate of an entry error message No action is in the user s account file necessary i ae e ae SMO07 0 NO ROOM FOR The SAM block allocated to Some other Session must SESSION CONTROL BLOCK contain all Session Control terminate before a successful Blocks is full The maximum access of the Remote Session number of Sessions are now Node can be accomplished active SM08 0 DUPLICATE Logon attempted for an existing Log on to a new session SESSION IDENTIFIER session SM09 0 SESSION SWITCH The user account was defined Contact the System Manager TABLE OVERFLOW with the total number of req
229. roblem was detected in allocating the SHEMA DSAM This is an NS ARPA internal error Memory Manager A Memory Manager table call was made on an undefined table This is an NS ARPA internal error Memory Manager The system is generated with a different version of NS ARPA 1000 than was used to load MMINIT Logging Codes and Messages This error requires HP notification This error requires HP notification This error requires HP notification This error requires HP notification Reduce the number of sockets or the number of active NS ARPA programs Reduce the above or the number of nodes or networks requested This error requires HP notification This error requires HP notification Regenerate your system or reload your programs to the new version 6 19 Multiuser Log Message Codes 2000 2999 The following table lists the multiuser error codes that may be returned in the muerror field of the HP NFT log messages described previously in HP NFT Log Message Codes Multiuser Log Message Codes 2000 2999 2001 2002 Unknown error The multiuser software has received an unknown error from one of the following RTE routines ATTACH GETSN CLGON NS ARPA has run out of table space for session keys The amount of space allocated is This error requires HP notification You must increase the size of the RTE multiuser table by generating more users into your taken from the number
230. rogram received a NetIPC error from an internal IPCRecv call when trying to receive data from the network TELNET server program ran out of internal buffer space for data to be echoed remotely This error requires HP notification A possible internal error in TELNET or NetIPC has occurred This error requires HP notification A possible internal error in TELNET or NetIPC has occurred This error requires HP notification A possible internal error in TELNET has occurred This can occur in a busy system where the server is locked out by high priority programs for an extended period of time This error requires HP notification Check to see if the control request subfunction is valid for a TELNET pseudo terminal lu interface driver IDZ00 See the RTE A Driver Reference Manual Refer to the NetIPC error code in the Numeric Error Codes section of this manual for more information This error is caused by the network socket not being writeable for a duration of time This error requires HP notification Too many characters at one time were typed ahead Re enter the characters TELNET server program failed to No free NS ARPA socket get the protocol socket available Try using TELNET again or increase the number of sockets configured in the system TELNET server program failed to Reinitialize NS If the problem find the VC socket created by the internet services network daemon INETD Loggin
231. rrent version of system nserr msg on your system in order to get proper FTP errors If not you will only get FTP error numbers without the accompanying error messages If you are not getting the correct FTP errors contact your System Manager to make sure file system nserr msg was present on the system when NS ARPA was initialized Program Specific Error Messages 4 7 DSCOPY amp NFT Error Messages The following error messages are returned to the current list device when DSCOPY is run interactively The numeric codes associated with these messages are returned in the result parameter of the DSCOPY call For example if DSCOPY encounters the error Cannot find closing quotation mark NFT 1000 ERR 13 the numeric error code 13 will be returned to the result parameter Only the numeric codes associated with error messages are returned to the DSCOPY call numeric codes associated with warning messages are not returned The negative error and warning codes NFT 1000 1 through 35 are HP 1000 specific and are returned by DSCOPY The error code zero NS NFTERR 0 and all of the positive error and warning codes NS NFTERR 1 through 58 are generated by the NFT protocol APPEND overrides REPLACE or OVERWRITE NFT 1000 WARN 1 option overrides previous data type setting NFT 1000 WARN 2 OVERWRITE overrides APPEND or REPLACE NFT 1000 WARN 4 option overrides previous setting NFT 1000 WARN 5 option overrides prev
232. rror ile filename k NS Error All files exist k Enter YES Kk 9013 NS Pascal error errornum of type errortype at line linenum progname 9014 NS File Name is name NSINIT could not open the message file filename A default file was requested but all 99 default files nsout1 through nsout 99 exist Input other than YES or NO was entered Only these two responses are valid for this NSINIT prompt If you are using NSINIT interactively NSINIT will reprompt If not NSINIT will print more messages and then abort A Pascal error occurred in the program progname A Pascal error occurred with the file named name This error message is for HP internal use only Program Specific Error Messages Put message file on the directory specified Purge some of the existing default files or use a non default file name If you are using NSINIT interactively enter either either YES or NO when NSINIT reprompts If not correct your answer file and try again Refer to the Pascal error errornum of type errortype for more information and rerun NSINIT If the error persists reboot your system and try again If rebooting does not solve the problem this error requires HP notification This is an informational message only No action is required 4 57 REMAT Error Messages The following error messages are returned to the current list device when an error is encoun
233. rror Codes Remote I O Error Codes and RPM Error Codes Section 3 Alphanumeric Error Messages provides the Subsystem Error Messages System Console Error Messages and Miscellaneous Alphanumeric Error Messages Section 4 Program Specific Error Messages lists program specific errors which include TELNET User Error Messages FTP User Error Messages DSCOPY and NFT Errors DSLIN Errors DSMOD Errors MVCP3 Error Messages Nodal Registry Error Messages NSINF Errors NSINIT Errors REMAT Errors and RMOTE Errors Section 5 Tracing Error Messages lists the error messages returned by the NS ARPA trace utilities NSTRC FMTRC and BRTRC Section 6 Logging Codes and Messages lists the error messages returned by the NS ARPA logging utilities EVMON and LOGCHG It also lists log message codes returned by the following entities HP IFP HP IP HP NFT HP PROBE HP PXP HP ROUTER HP RPM HP TCP HP IN IEEE 802 INPRO OUTPRO PROSW RUNTIME SIGMOD SREG TIMER and UPLIN Guide to ARPA 1000 Manuals The following are brief descriptions of the manuals included with the NS ARPA 1000 product 91790 90020 NS ARPA 1000 User Programmer Reference Manual Describes the user level services provided by NS ARPA 1000 The NS services are network file transfer NFT network interprocess communication NetIPC and remote program management RPM The ARPA services are TELNET and FTP Because these are interactive and programmatic services this manual
234. ry again NFT 1000 ERR 18 than 256 characters Illegal command The command issued is illegally Check syntax and try again NFT 1000 ERR 19 formed Unknown command DSCOPY does not recognize the Check syntax and try again NFT 1000 ERR 20 command option is an unknown DSCOPY does not recognize the Check syntax and try again copy descriptor option copy descriptor option NFT 1000 ERR 21 Error in option value The value associated with Check syntax and try again for option option option is invalid NFT 1000 ERR 22 File names cannot be An attempt was made to default Check syntax and try again defaulted a file name NFT 1000 ERR 23 Input command is too big The input command is greater Shorten the command and try NFT 1000 ERR 24 than 256 characters again Cannot open file DSCOPY was unable to open Verify that the file name is filename the given file due to an unknown correct and that the file is NFT 1000 ERR 25 error accessible and try again Program Specific Error Messages 4 9 Unable to initialize This error may be returned for An additional error string may DSCOPY the following reasons 1 follow this message which will NFT 1000 ERR 26 DSCOPY was unable to acquire offer further explanation sufficient resources Such as sockets or 2 an error occurred in accessing Distributed System Available Memory DSAM or tables in DSAM Cannot create a The target computer does no
235. s illegal to call this procedure This error requires HP bad message notification RROB invalid emsg Message had invalid event ID This error requires HP notification RRIB DS MDispose error Could not dispose the message This error requires HP notification RRIB InStub received Message had invalid event ID This error requires HP spurious emsg notification RRIB DS MRead error Could not read the message This error requires HP from DSAM notification PRIB DS MAdj error Could not strip the header from __ This error requires HP the message notification PRIB NRV node not found The router address was not Add the router address during error found NS ARPA initialization PRIB Invalid emsg Message had invalid event ID This error requires HP notification Logging Codes and Messages 6 67
236. s is an NS ARPA internal error 26517 PING encountered an invalid If the error persists this error path report The Nodal Registry requires HP notification might be corrupt 26518 Memory Manager returned an This error requires HP error when PING tried to put its notification event message in DSAM The Memory Manage error is in the xx field This is an NS ARPA internal error Memory Manager returned an This error requires HP error when PING tried to reada notification path report from DSAM The Memory Manager error is in the xx field This is an NS ARPA internal error Memory Manager returned an This error requires HP error when PING tried to retrieve notification its data from DSAM The Memory Manager error is in the xx field This is an NS ARPA internal error 26521 PING was unable to set the If the error persists this error timer requires HP notification Logging Codes and Messages 6 45 26522 PING was unable to wait for a This error requires HP reply from ICMP The Memory notification Manager error returned is in the xx field This is an NS ARPA internal error 26523 The timer expired unexpectedly If the error persists this error requires HP notification 26524 PING was unable to create its If the error persists when the user record This might happen network traffic is low this error if the network traffic is heavy requires HP notification 26525 PING was unable to find its user If t
237. sage received from This is a warning If the error the network is not in the correct persists this error requires HP format notification 25004 An error was encountered while This error requires HP trying to find out the local node s notification LAN station address This is an NS ARPA internal error 25005 An error was encountered while This error requires HP trying to send an ARP message notification out to the network The exact nature of the error depends upon the accompanying location and error fields This is an NS ARPA internal error 25006 An error was encountered while This error requires HP setting a timer The exact nature notification of the error depends upon the accompanying location and error fields This is an NS ARPA internal error 25007 The ARP protocol handler This error requires HP received an unexpected type of notification event message This is an NS ARPA internal error 25008 The ARP message received from This is a warning If the error the network has an unknown persists this error requires HP message type field notification 25009 The ARP protocol handler This error requires HP received an unknown type of notification timer signal from the timer facility This is an NS ARPA internal error 25016 An ARP transaction has been Configure more ARP PCB initiated by IP while all of ARP s records using NSINIT path records were in use Logging Codes and Messages 6 43 IC
238. ses this is the user s session ID Logging Codes and Messages 6 5 Log Message Codes Log Message Codes and ASCII Log Messages are sent to the log file by certain software modules procedures processes or protocol handlers Some Entities use the Log Message Codes when the event class indicates a warning Class 3 error Class 4 disaster Class 5 or resource limit condition Class 6 The following Entities print their Log Message Codes in the following numeric ranges e 0 999 generic includes codes 100 599 for HP NFT 1000 1999 Memory Manager e 2000 2999 Multiuser e 3000 3999 HP IP e 4000 4999 IEEE 802 ETHERNET e 5000 5999 HP PXP e 8000 8999 HP ROUTER e 14000 14999 HP TCP e 15000 15999 TIMER e 17000 17999 UPLIN e 18000 18999 HP RPM e 20000 20999 HP TN e 21000 21999 HP FTP e 24000 24999 ARM e 25000 25999 ARP e 26000 26999 ICMP The following Entities have ASCII Log Messages HP IFP HP ROUTER INPRO OUTPRO 6 6 Logging Codes and Messages EVMON Error Messages The following table lists error messages that are returned by the logging utility EVMON The first table lists the error messages that are printed to the scheduling terminal EVMON Errors Printed to the Terminal EVMON Unexpected error getting a message errorcode EVMON Access to DSAM not allowed errorcode EVMON Unexpected error getting a user record errorcode EVMON Error openin
239. specified while invoking IPCSelect Cannot read select on the socket now One or both of the following actions may be taken 1 Retry the request later after some NetIPC connections have been aborted and some IEEE 802 3 path records have been released or 2 ask the System Manager to configure more IEEE 802 3 path records into the system One or both of the following actions may be taken 1 Retry the request later after some NetIPC connections or call sockets have been aborted or 2 ask the System Manager to configure more TCP path records into the system Check the value of the descriptor bound parameter to verify that its value was the intended one The socket has been gracefully released by the remote and the user has been informed about it Hence there will be no more data on that socket Numeric Error Codes 2 21 PTOP Error Codes The following error codes are returned in the err parameter of PTOP master or PTOP slave calls If an error code is returned to the slave program the slave program must pass this information to the master program slave programs cannot initiate recovery procedures Error codes 50 through 59 are returned to PTOP master calls in lieu of DS errors 00 through 09 This simplifies your code when error recovery is desired All other messages IOxx SCxx for example are converted to 47 in PTOP slave calls PTOP Error Codes ade caning ation Remote program not defined
240. ss in the range 1 to 32767 If you are using NSINIT with an answer file NSINIT has aborted Correct your response in the answer file as described above and rerun NSINIT If you are using NSINIT interactively and the IP address was not in the proper format reenter the corrected address If the IP address was invalid abort and rerun NSINIT this time providing information about the IP address in the IP section If you are using NSINIT with an answer file NSINIT has aborted Correct the IP address in the answer file as described above and rerun NSINIT If you are using NSINIT interactively enter an LU number in the range 1 to 255 or omit the LU number to indicate the default If you are using NSINIT with an answer file NSINIT has aborted Correct the LU in the answer file as described above and rerun NSINIT 319 NRV Invalid LU timeout 320 NRV Invalid message level 321 NRV Improper neighbor indicator 322 NRV indicator Improper MA 323 NRV timeout Invalid MA An LU timeout entered is out of range An invalid message level was entered An invalid neighbor indicator was entered An invalid Message Accounting indicator was entered A Message Accounting timeout entered is out of range Program Specific Error Messages If you are using NSINIT interactively enter an LU timeout in the range 1 to 255 or omit the timeout value to indicate the defau
241. ssary for clarity in an example user input may be underlined For example NEW NAME ALPHA Brackets braces or ellipses appearing in syntax or format statements that must be entered as shown will be underlined For example LET var subscript value Output and input output parameters are underlined A notation in the description of each parameter distinguishes input output from output parameters For example CREATE parm1 parm2 flags error The symbol ____ may be used to indicate a key on the terminal s keyboard For example indicates the carriage return key Control characters are indicated by followed by the character For example CONTROLJY means the user presses the control key and the character Y simultaneously Table of Contents Chapter 1 Introduction OVEIVIOW 0d 5s kee tide cerid tE eee e shia CeSR eee NCES E Ree cawe CeO 1 1 Numeric Error Codes sis eseunsy ssketauds yip dees woes ess eho wees aoh es 1 1 Alphanumeric Error Messages ovvcisatvekseae teeta tebedeeehyertteetesad 1 1 Program Specific Error Messages wisn ivca dod even th dadeeat erie ee teed 1 1 Tracing Error M ssabeS carry res miri aai di oat puree heed EE TE 1 2 Logging Error Codes and Messages uh cdvvis ei dae tee ehaueesvede4ene shea ton 1 2 Using DSERR a4 lt cxcs oes esd ERARA shee Kote TEE ER shee Cone SARE Reseed eos 1 2 Internal Biro 4c basa eeeesee sco eews soci eines oe Bene ee Sb Riess oo ewe eee eee 1 3 Submitting a Service
242. st was rejected because the system did not have any free socket records Every socket in the system must have a corresponding socket record The number of socket records contained in a system is determined by the System Manager when a node is brought up Would block error The calling process issued a request that could not be immediately satisfied against a socket that was in asynchronous mode One of the following actions may be taken 1 Do not specify a particular protocol when creating the call socket Instead use the default protocol value of zero in IPCCreate s protocol parameter 2 Create a new call socket and bind it to a different protocol and try again None unless the remote application that the calling process wants to connect to can be modified to use call sockets One or both of the following actions may be taken 1 Verify that the descriptor value specified was the one intended 2 verify that the call to create the call socket succeeded One or both of the following actions may be taken 1 The calling process or some other process can shut down some sockets in order to release some socket records 2 the System Manager can be asked to configure more socket records into the system This is an informational message so no action is necessary For more information on asynchronous I O refer to the Network Interprocess Communication section of the NS ARPA 1000 User Programmer Re
243. swer file as described above and rerun NSINIT If you are using NSINIT interactively enter a non duplicate IP address for the local address If you are using NSINIT with an answer file correct the IP address in the answer file as described above and rerun NSINIT The gateway to this destination has already been fixed due to a response to a previous NSINIT question Proceed to the next destination network This error requires HP notification Try again and enter another non duplicate node or network address 631 NSINIT DCN Segment size out of range 632 NSINIT DCN Internal error Invalid Down Protocol ID 634 NSINIT GT Destination Network entered previously 635 NSINIT GT Gateway DCN information not found 636 NS Input Error Input device not interactive Aborting 637 NSINIT IP GT space allocation error 638 NSINIT IP PATH Record table allocation error 639 NSINIT IP ANH Record table allocation error 640 NSINIT IP GLOBAL BLOCK allocation error The segmentation size specified for the lower level protocol was an illegal size Internal error An invalid protocol identifier is being used for the link interface The destination network has already been entered The gateway entered is not on one of the previously entered directly connected networks Gateways must be members of one of the directly connected networks co
244. t each node to display the NRVs and compare this to your network topology Correct the NSINIT initialization files nodal addresses and re initialize bring to quiescent state shut down and restart or reboot all nodes that had incorrect NRVs 3 Call DOPEN or POPEN and open the file 4 Correct the node number It may be possible to restore links with the L command and change the NRV with the cn command of DSMOD DVA66 links are automatically enabled when the link problem is corrected or goes away This error can occur when the links at a store and forward 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 This may indicate that the NRV at this node or other nodes is specified incorrectly Check NRVs and use DSMOD cN or T to correct this error Retry on a DSO5 error is not always a good practice for the following two reasons 1 The request may have been correctly delivered to the destination node and have been executed but the destination node may have a problem in sending back the reply or the reply just takes too long to reach the origin node 2 ADSO5 0 error can occur if Message Accounting does not exist at this node Another solution to avoid DS05 0 error may be to increase the master timeout value DS05 1 REQUEST WAS RECEIVED AT TH DESTINATION NODE BUT THE REPLY WAS NOT RECEIVED I
245. t Specify the FIXED option and sparse variable length support sparse files with variable try again record file length records NFT 1000 ERR 27 Cannot schedule PRDC1 PRDC1 could not be scheduled Ask the source computer s helper program Either it could not be found or Network Manager to make the NFT 1000 ERR 28 there are insufficient resources PRDC1 program accessible Cannot schedule DSCOPY The DSCOPY call could not Make sure the DSCOPY program schedule the DSCOPY program program is accessible on your NFT 1000 ERR 29 computer DSCOPY aborted The DSCOPY call noticed that the Try again NFT 1000 ERR 30 DSCOPY program was terminated for some reason Cannot schedule Producer The Producer program could not Ask the source computer s program on source be scheduled Network Manager to make the computer Producer program accessible NFT 1000 ERR 31 Cannot schedule Consumer The Consumer program could Ask the target computer s program on target not be scheduled Network Manager to make the computer Consumer program accessible NFT 1000 ERR 32 Record size is too large The source computer or the Specify an RSIZE of less than NFT 1000 ERR 33 target computer could not 2200 words accept the interchange file copy request because of buffer space limitations Either one of the records in the source file is larger than 2200 words or the user defined RSIZE value is larger than 2200 words Fi
246. t be at least 13 words long MAST The request header must not be larger than 63 words GET Request header must be greater than or equal to 13 words and not greater than 63 words GET The data received is larger than the user buffer provided to receive the reply Alphanumeric Error Messages If other HP 1000s exist in your network shut down NS ARPA and reinitialize with a correct network description Run NSINIT to initialize the node Run NSINIT to initialize the node Check the communication link The inbound data buffer must not exceed the maximum space allocated by the user buffer If a larger buffer is required consult the NS ARPA 1000 Generation and Initialization Manual for information on expanding this buffer This error indicates a NS ARPA internal error has occurred Consult your Network Manager If this error occurs it indicates a NS ARPA internal error Consult your Network Manager This error indicates a NS ARPA internal error Consult your Network Manager This happens when a record from a file is read that turns out to be larger than the buffer provided to read the record or when in Program to Program Communication the incoming buffer is larger than the buffer space allocated by the user 3 3 DS04 0 ADDRESS ILLEGAL NODAL NODE ADDRESS NOT IN NODAL ROUTING VECTOR DS04 1 THIS NOD NRV TABLE ALL ROUTES TO E ARE DOWN REROUTING DS04 2
247. t file is printed to the list file This is an informational message No action is necessary The name chosen for the target file is printed in the list file Source and target file attributes differ NS NFTWARN 43 Records were truncated to fit in target file NS NFTWARN 44 Not compressing for this transfer NS NFTWARN 45 Unable to turn on tracing NS NFTWARN 46 Cannot strip padding from fixed length records NS NFTWARN 47 Unable to access target file or device NS NFTERR 48 Invalid source file name NS NFTERR 49 No files matched source specification NS NFTERR 50 APPEND option is not supported NS NFTERR 51 The source file attributes had to This is an informational be modified so that the file could message No action is be copied to the target necessary computer Either APPEND or OVERWRITE was given and the existing target file had attributes different from the source file or the target computer requested that the file attributes be modified before that file could be acceptable This is an informational message No action is necessary The user defined record size value RSIZE was smaller than the size of the largest record in the source file and one or more records in the source file were truncated This is an informational message No action is necessary Either the source and or the target computer does not support data compression the COMPRESS option
248. t supported A request was made to copy a file to a non disk device This is not supported An unexpected file system error occurred in closing the target file The given source file password was incorrect The given target file password was incorrect The target file name contained some characters which were invalid for the target computer and they were removed from the target file name before it was created The target file name was too large for the target computer and was truncated Program Specific Error Messages Refer to the qualifying file system error string to determine action to be taken Refer to the qualifying file system error string to determine the action to be taken Refer to the qualifying file system error string to determine the action to be taken Refer to the qualifying file system error string to determine the action to be taken Copy the non disk device file to a disk file using a system utility program and then use DSCOPY to copy the file to the target computer Copy the file to disk on the target computer using DSCOPY and then to the non disk device using a system utility program Refer to the qualifying file system error string to determine the action to be taken Specify the correct source file password and try again Specify the correct target file password and try again This is an informational message only No action is necessary The name chosen from the targe
249. t the contents of the trace file filename that you specified This error is returned 1 if you are using incompatible versions of FMTRC and NSTRC or 2 if your trace file is corrupt Refer to the accompanying VMA error code errorcode for more information Make sure you have compatible versions of FMTRC and NSTRC If the programs are compatible rerun NSTRC to produce a new trace file and try again An error occurred when writing to the format file filename Refer to the accompanying FMP error code errorcode for more information The address that you specified address is not correct This may be due to a typographical error If you are running FMTRC interactively correct the address and try again If you are using a command file edit the file and rerun FMTRC If you are running FMTRC interactively correct the protocol and try again If you are using a command file edit the file and rerun FMTRC The protocol protocol that you specified is not correct This may be due toa typographical error Tracing Error Messages 5 3 FMTRCERR 9 Monitor Service id specified is not valid id FMTRCERR 10 Socket specified is not valid socket FMTRCERR 11 Time string specified is not valid time FMTRCERR 12 Trace level specified is not valid level FMTRCERR 13 Too many Monitor Service ids were specified ids FMTRCERR 14 Too many sockets were specified sockets FMTRCERR 17 FMTRC
250. te file name No action is necessary the first two characters have been replaced by warning only or PTOP RJECT received No error or PTOP ACEPT No action is necessary received RFA Disk down or DEXEC 99 The RFA Disk down error is Program Status Request reported by the file system at non existent program the reporting node Refer to the appropriate operating system manual to determine the meaning Duplicate file name Reported by the file system at the reporting node Refer to the appropriate operating system manual Illegal backspace This error code is reported by the file system at the reporting node Refer to the appropriate operating system manual to determine the meaning 2 6 Numeric Error Codes File too long or record size error This error code is reported by the file system at the reporting node Refer to the appropriate operating system manual to determine the meaning Attempt to read or position a This error code is reported by record not written or on update the file system at the reporting to write to an illegal record node Refer to the appropriate length operating system manual to determine the meaning File not found or On DCRET or The file not found error is FCOPY the specified file size is reported by the file system at negative The remote file create the reporting node Refer to the subroutine does not allow a appropriate operating system negative file s
251. tem must be either BEGIN or END An END keyword was encountered before the last raw Nodal Path Report NPR was complete or a e or end of file was encountered before the END keyword was entered The first item encountered was not BEGIN The first item after an END must be BEGIN A node name subfield was entered that is too long Node name subfields may be a maximum of 16 characters long An IP address has the format ddd ddd ddd ddd An IP address was entered that did not contain four subfields An IP address has the format ddd ddd ddd ddd Program Specific Error Messages If you are using NRINIT interactively you may start again from BEGIN or terminate and rerun NRINIT If you are using NRINIT with a text file correct the entry in the text file and rerun NRINIT If you are using NRINIT interactively you may start again from BEGIN or terminate and rerun NRINIT If you are using NRINIT with a text file correct the entry in the text file and rerun NRINIT If you are using NRINIT interactively you may start again from BEGIN or terminate and rerun NRINIT If you are using NRINIT with a text file correct the entry in the text file and rerun NRINIT If you are using NRINIT interactively you may start again from BEGIN or terminate and rerun NRINIT If you are using NRINIT with a text file correct the entry in the text file and rerun NRINIT If you are using NRINIT interactively you may start ag
252. ter has already timed out or was aborted by the operator If Message Accounting is in the system and a reply was slow in returning this might occur due to MA s retransmission sequence 3 18 Alphanumeric Error Messages ID 66 Read process errors could be caused by a timeout waiting for incoming frame an attempt to read data when link is not logically connected message type and frame size do not agree message length and read length do not agree line fails during read process One of the Message Accounting modules has determined that there is an internal system failure It has disabled itself This should never occur Consult your Network Manager and reboot One of the rerouting modules XXXXX has determined that there is an internal system failure It has disabled itself This should never occur Consult your Network Manager and reboot The slave monitor or PTOP slave may have taken too much time processing this reply If this error occurs frequently increase the master timeout value DS ERROR ttuu v REPORTING NODE Wwwww REPLY FLUSHED STREAM xXxxxx ORG NODE yyyyy DEST NODE 2222Z DS ERROR ttuu v REPORTING NODE wwwww REPLY FLUSHED STREAM xXxxxx ORG NODE yyyyy LU 22222Z DS ERROR PROG xXxxxx STREAM yyyyy SEQ 22222 P ppppp A aaaaa B bbbbb DS ERROR UP DOWN COUNTER EXCEEDED LINK LU xxx IS DISABLED This error occurs when a reply Try again possibly an error reply cannot be
253. tered by the program REMAT REMAT Error Messages LOGOFF DSERR SSEE QQ This message can appear if the Check under error code EE for REPORTING NODE NNNNN node being accessed by REMAT specific subsystem SS is a Session Monitor node LOGON DSERR SSEE QQ This message can appear if the Check under error code EE for REPORTING NODE NNNNN node being accessed by REMAT specific subsystem SS is a Session Monitor node REMAT ae SSEE QQ See error code EE in specific REPORTIN DE NNNNN subsystem SS REMAT xxx Numerical error message See appropriate FMGR error for equivalent to FMGR errors an explanation 4 58 Program Specific Error Messages RMOTE Error Messages The following error messages are returned to the current log device when an error is encountered by the program RMOTE RMOTE Error Messages AUTO BYE FAILED The BYE generated automatically when the EX command is entered with a HELLO outstanding has failed May occur if the link has been disconnected since the HELLO was entered This error is for the operator s information only the session at the HP 3000 is closed automatically BAD LU A negative LU number was Correct the LU and try again specified in a MO command DS 1000 ERROR nnn DS 3000 ERROR nnn HELLO FAILED OR LINE DOWN ILLEGAL STATUS INVALID INPUT INVALID REMOTE LU DISCONNECTED MPE FILE ERROR nnn NEED HELLO
254. ternal error on SoCreate call Cleaning up IPC error is errornum 46 NSINIT Internal error on program count Cleaning up IPC error ig errornum 47 NSINIT error accessing initialization RN Terminating Internal 48 NS Internal error in IntInput Terminating 49 NS Error opening LU 1 Terminating 50 NSINIT Internal error No smb left Cleaning up 51 NSINIT Error in SMB Allocation Cleaning up kk 52 NS Internal error in PrintPrompt Terminating 53 NSINIT Internal error on socket count Cleaning up An error occurred on the SoCreate call during the NetIPC portion of initialization NSINIT attempted to return all allocated resources before terminating This error message may be returned when an error is detected in the NS ARPA software NSINIT encountered an invalid value for the program count during the PXP portion of initialization NSINIT tries to cleanup resources before terminating There may be an error in the NS ARPA software RTE returned an error to NSINIT while accessing the initialization resource number at start up NSINIT tries to cleanup resources before terminating IntInput did not return the proper value There may be an error in the NS ARPA software NSINIT encountered an error when attempting to open LU 1 NS ARPA requested less System Memory Block SMB than it requires NSINIT attempted to return th
255. ternal error Memory Manager There is enough memory between the user s SBUF and the pool to satisfy the request but it is currently being used This is an NS ARPA internal error Memory Manager A parity error was discovered in a buffer on the MBUF chain Memory Manager The SBUF reference did not reference a valid SBUF This may occur if the reference did not point toa valid SBUF or the SBUF was not initialized or the SBUF was disposing or the SBUF was a pool SBUF This is an NS ARPA internal error Memory Manager The SBUF is already initialized This is an NS ARPA internal error Memory Manager Either no data is currently available or it may be possible to get that many memory credits from the individual SBUF not using the pools but currently they are in use This error was returned to an NS ARPA 1000 protocol handler In most cases the protocol handler will have to dispose of the memory Memory Manager The number of memory credits required will never be available This error was returned to an NS ARPA 1000 protocol handler In most cases the protocol handler will have to dispose of the memory Memory Manager The MBUF chain contains an illegal account given the operation requested This is an NS ARPA internal error Logging Codes and Messages This error requires HP notification This error requires HP notification If communications are severely affected reinitialize NS ARPA 1
256. tes programming error Correct program calling parameters and re run MAST This is a NS ARPA internal error One of the NS ARPA intrinsics has called with insufficient parameters MAST MAST requires positive word length specifications DEXEC does not support negative character length specifications MAST MAST requires positive word length specifications DEXEC does not support negative character length specifications Alphanumeric Error Messages Consult your Network Manager Correct call parameters and try again Correct call parameters and try again 3 7 DS09 4 NEGATIVE MAXIMUM EXPECTED REPLY LENGTH DS09 5 NEGATIVE PARAMETER IN GET CALL DS09 6 MISSING PARAMETER IN GET CALL MAST On a read request the Change to positive word length maximum expected reply length and try again can t be specified as a negative character length GET This error is a NS ARPA_ Inform your Network Manager internal error One of the NS intrinsics is calling GET with negative parameter values GET This error is a NS ARPA Inform your Network Manager internal error One of the NS intrinsics is calling GET without all the necessary parameters 3 8 Alphanumeric Error Messages lOxx Error Messages The following error codes are I O errors and thus have the subsystem prefix of IO All of the IOxx errors with error qualifier 0 are equivalent to the RTE IOxx errors
257. tes that a parity error has occurred in the DSAM buffer area and the capacity of the system is reduced Memory Manager A problem occurred on DSAM allocation during NS ARPA initialization This is an NS ARPA internal error Memory Manager A problem occurred on DSAM deallocation during NS ARPA shut down This is an NS ARPA internal error Memory Manager MMINIT was run by a program other than NSINIT This is an NS ARPA internal error Memory Manager DSAM is not initialized NSINIT attempted to shut down NS ARPA 1000 when it was not up This is an NS ARPA internal error Memory Manager DSAM is already initialized NSINIT attempted to initialize NS ARPA 1000 when it was already initialized This is an NS ARPA internal error Memory Manager Access to DSAM denied Some program attempted to access DSAM when DSAM access was not permitted This could be because NS ARPA 1000 was not up or because of a parity error in the tables or globals 6 16 Logging Codes and Messages If the error occurred at initialization increase the size of DSAM and rerun NSINIT Ifa parity error is indicated no action is necessary unless the problem is so severe that NS ARPA 1000 communication is seriously affected If this is the case shut down and reinitialize NS ARPA moving DSAM to an unaffected region of memory or replace the defective memory You may also cross check a parity error with the NSINF B display This error re
258. text file correct the entry in the text file and rerun NRINIT If you are using NRINIT interactively you may start again from BEGIN or terminate and rerun NRINIT If you are using NRINIT with a text file correct the entry in the text file and rerun NRINIT Reboot your system If rebooting does not solve the problem notify your HP field office Reboot your system If rebooting does not solve the problem notify your HP field office Reboot your system If rebooting does not solve the problem notify your HP field office 4 25 kk 6037 NRERR Version domain unknown Skipping record kk 6038 NRERR Illegal subfield syntax kk 6042 NRERR Illegal environment name syntax kk kk 6047 NRERR Illegal LAN address syntax kk 6048 NRERR NRegFind error 4 26 Either the version of the node name or its domain code is not that of the current release software If the software is current an error has occurred in the Nodal Registry table An invalid domain or organization field for a node name was entered Domain and organization fields may be up to 16 alphanumeric characters long and the first character must be alphabetic An invalid node name was entered Node names consist of three subfields Each subfield may be up to 16 alphanumeric characters and the first character must be alphabetic An invalid LAN station address was entered The LAN address must be specifie
259. the NS ARPA 1000 DS 1000 IV Compatible Services Reference Manual HELLO BYE Error Codes These error codes are returned to the HELLO and BYE utility subroutines HELLO and BYE are described in the Utilities section of the NS ARPA 1000 DS 1000 IV Compatible Services Reference Manual NetIPC Error Codes These error codes are returned in the result parameter of Network Interprocess Communication NetIPC calls NetIPC is described in its own section of the NS ARPA 1000 User Programmer Reference Manual PTOP Error Codes These error codes are returned in the err parameter of PTOP master and slave calls PTOP is described in its own section of the NS ARPA 1000 DS 1000 IV Compatible Services Reference Manual Remote I O Mapping Error Codes These error codes are returned to the program IOMAP in the first return parameter Remote I O Mapping is described in the NS ARPA 1000 Generation and Initialization Manual RPM Error Codes These error codes are returned in the result parameter of Remote Process Management RPM calls RPM is described in its own section of the NS ARPA 1000 User Programmer Reference Manual The numeric codes associated with the DSCOPY error messages are returned in the result parameter of the DSCOPY call The error codes are equivalent to those returned in the list file or device when DSCOPY is used interactively Refer to DSCOPY and NFT Error Messages in Section 4 of this manual for a description of these errors DSC
260. this manual for more information Verify with your Node Manager about the status of your network Refer to the NetIPC error in Section 2 of this manual for more information Try request again Verify that the remote host is up and running and that FTP is running on the remote host Refer to the NetIPC error in Section 2 of this manual for more information Verify the node name of the remote host Use the A command of NSINF to see what nodes are connected to the network Refer to the NS ARPA 1000 Generation and Initialization Manual for details Refer to the NetIPC error in Section 2 of this manual for more information No action required Since connection has been reset you need to restart the FTP session Refer to the NetIPC error in Section 2 of this manual for more information Shorten the length of the input line to less than 256 characters and try again If file contains ASCII data set file transfer type to ASCII and try again Note however that APPEND does not support ASCII file transfers involving file types 1 2 and 6 Message FTP internal error An internal FTP error has This error requires HP encountered occurred notification FTP ERR 34 Unable to use CMNDO An error was returned from Refer to the Relocatable Library editing HpStartCmndo HpStartCmndo Reference Manual for an error explanation of error codes FTP ERR 35 returned by HpStartCmndo Note You must have the cu
261. ts and has an ID segment cs indicates the child program status Then try again If the problem persists this error requires HP notification LogMessage 18307 muerror xx Xx Logoff failed The RPM Monitor Refer to the Multiuser Log failed to logoff the child session Message Codes subsection A Multiuser error is logged earlier in this section 18308 xx XX xXx Group 3 option error An error Check the Group 3 option in the occurred when executing a RPMCreate call Group 3 option in an RPMCreate Call Logging Codes and Messages 6 37 HP TN Log Message Codes 20000 20999 The following codes are printed to the log file when the Entity is HP TN for the TELNET virtual terminal service The parts of TELNET that return log message codes are the TELNET user program and the TELNET remote server program The TELNET user program runs on the local node and communicates with the TELNET remote server The TELNET remote server program runs on the remote node and handles the virtual terminal session Some of the log message codes are followed by error codes returned by NetIPC Refer to the NetIPC error codes for more information Fields that are indicated by xx contain values that are for HP use only Errors that include these fields usually require HP notification the values contained in these fields should be reported to HP HP TN Log Message Codes for TELNET User Program 20000 20999 tesmessase Meaning Ation 20100 XX XX X
262. ttempt to read data when link is not logically connected message type and frame size do not agree message length and read length do not agree line fails during read process Alphanumeric Error Messages 3 17 DS ERROR 1K 3K From Driver LU xxx write drv 66 err 222 DS ERROR SELF CHECK ERROR IN MESSAGE ACCOUNTING DS ERROR SELF CHECK ERROR IN Xxxxx P ppppp A aaaaa B bbbbb REROUTING IS DISABLED FROM THIS NODE DS ERROR SLAVE TCB NOT FOUND POSSIBLE TIMEOUT STREAM xXxxxx ORG NODE yyyyy DEST NODE 2222Z DS ERROR TCB NOT FOUND POSSIBLE TIMEOUT STREAM xXxxxx ORG NODE yyyyy LU ZZZZZ Error codes zzz in octal are no error line failure timeout local busy message aborted remote busy o not initialized 11 wrong mode 12 illegal request 13 card failure 17 bad interrupt 0 1 2 3 4 5 1 ID 66 The receive LU does not follow the transmit LU or GRPM detected an error in the read process Message is returned in the form nnnnn XXXXX VYYYY ZZZZZ where nnnnn Node number The other numbers are special flags for HP internal use Where xxxxx name of rerouting module pppppp octal contents of the P register aaaaaa octal contents of the A register bbbbbb octal contents of the B register A reply was being sent for which there was no associated request A reply arrived which could not be matched to any master TCB Most probable reason is that the mas
263. ty OQUTPRO oc ngvcegess thease cnet ease de one herrea taese aE k 6 49 Entity HP PROBE 23 o500 6 ba iis pee Adee Rie ecm ere tab subsets mae nae RA 6 52 Entity PROSW gcd cdedenkndeeet saree ile sans Peas pane deay ase a E enemas 6 55 Entity SUG MOD seess nereis tienaa E ike we Oe eed Baia ee ee es 6 56 Entity SREG ae haces eh eee ead Oe he MO Ae eae One beers ae 6 60 ASCI Log MESS ABCs ascris ee san aes gas Bihan aU u a Rees aid Seo ROMO wees ck 6 64 Entity TPE saa aces oc ches oe ba eek eae ea ee oa Eek nae Bete ee ey 6 64 INPRO ASCII Log Messages 0 06 spi w w sd acpineace eRe Wp eaw ie Habre ace ewan eay ak eS 6 65 OUTPRO ASCII Log Messages eei5e 0e Febawnd ege NS aay ie abe sede ey a8 n 6 66 HP ROUTER ASCII Log Messages ici oid dade ented eeu wage de de aw a biw ae eects 6 67 13 Introduction Overview NS ARPA 1000 is a Hewlett Packard data communications product which enables HP computer systems to exchange information and share resources The NS ARPA 1000 Error Message and Recovery Manual lists and explains all of the error codes and messages that may be generated by NS ARPA 1000 The error codes and messages explained in this manual are organized into five major groups Numeric Error Codes Numeric error codes are described in Section 2 They are listed in alphabetical order by the name of the program call or parameter that returns them This section contains the error codes that are returned to the err parameter of many DS 1
264. ual number of entries argument was the intended value 2 recalculate the number of entries that will actually be needed Numeric Error Codes 2 19 2 20 Numeric Error Codes Cannot read option The opt entry specified in the ReadOpt call was not initialized Illegal read threshold The caller attempted to set an illegal read threshold for the referenced socket with an IPCControl call Illegal write threshold The caller attempted to set an illegal write threshold for the referenced socket with an IPCControl call Write threshold too big The caller attempted to set a write threshold value that was too large with an IPCControli call Resource error The request via IPCCreate or IPCConnect to create a new socket could not be supported because the protocols would not have had enough resources to support the socket No PXP path records The request could not be satisfied because PXP did not have an available path record This error will most often be returned by IPCLookUp when a process specifies the name of a remote node No IP path records The request could not be satisfied because IP did not have an available path record IP needs such records to hold addressing information One or both of the following actions may be taken 1 Verify that the opt parameter was properly initialized with InitOpt 2 verify that the referenced entry was set up properly with Addopt Verify that the value passed was
265. uired SST entries greater than 70 SM10 0 NO FREE ID There are not enough free ID Consult your System Manager SEGMENTS OR FMGR NOT segments to create and FOUND schedule a copy of file manager for this session SM11 0 FMP ERROR ON An attempt to mount a private or Check the appropriate FMP DISK MOUNT ATTEMPT group cartridge belonging to error for more information this session failed SM12 0 ACCOUNT FILE Internal structure of account file Contact your System Manager CORRUPT is incorrect SM13 0 SESSION The system is not ready for use Try again later When session is SHUTDOWN shut down only the system console is available for operator control 3 14 Alphanumeric Error Messages System Console Error Messages The tables in this subsection lists miscellaneous ASCII messages that may be printed to the system console system LU 1 Unexpected Console Messages Certain system console messages are considered unexpected They are printed in the following format DS ERROR PROG xxxxx STREAM yyyyyy SEQ ddddd P pppppp A aaaaaa B bbbbbb where xXxxxx name of program reporting the error yyyyyy stream code ddddd sequence number of the request or reply being processed when the error occurred Pppppp P register address where the program detected the error you ll need listings aaaaaa contents of the A register when the error occurred and bbbbbb contents of the B register when
266. un NRINIT If you are using NRINIT with a text file correct the node name in the text file and rerun NRINIT If you are using NRINIT interactively you may start again from BEGIN or terminate and rerun NRINIT If you are using NRINIT with a text file correct the entry in the text file and rerun NRINIT If you are using NRINIT interactively you may start again from BEGIN or terminate and rerun NRINIT If you are using NRINIT with a text file correct the entry in the text file and rerun NRINIT If you are using NRINIT interactively you may start again from BEGIN or terminate and rerun NRINIT If you are using NRINIT with a text file correct the address in the text file and rerun NRINIT If you are using NRINIT interactively you may start again from BEGIN or terminate and rerun NRINIT If you are using NRINIT with a text file add the address to the text file and rerun NRINIT 4 23 6016 NRERR Expected protocol ID BEGIN or END 6017 NRERR Expected BEGIN or END 6018 NRERR Last path not complete 6019 Begin NRERR Missing 6020 NRERR Subfield in name is greater than 16 characters 6021 NRERR IP subfields not separated by periods 6022 NRERR IP address does not have 4 subfields 4 24 An invalid entry was detected after the IP address The next item following the IP keyword must be 802 ETHERNET LAN BEGIN or END The next i
267. ur system for memory problems Shut down NS ARPA Check your system for memory problems Shut down NS ARPA Refer to accompanying error messages for additional information Shut down NS ARPA Refer to the accompanying error messages from additional information Shut down NS ARPA NSINIT will attempt to deallocate all remaining resources 107 NS Discrepancy The Distributed System between DSAM State Word and NSINIT State Word kk 110 NS Invalid State Cannot Startup NSINIT ABORTING 112 NSINIT MMInit Wrong Security Return Terminating 113 NSINIT MMInit Schedule Error Name not MMInit Terminating 114 NSINIT Improper State of NS Terminating 115 NSINIT Invalid Internal Security Code kkk 116 NSINIT DSAM requested is more than 2 MBytes Terminating Available Memory DSAM state word indicates that DSAM is allocated but the NS ARPA state word indicates that NS ARPA is not initialized This error may be returned if a problem was encountered during a previous start up or shut down of NS ARPA When NSINIT called the resource allocating subroutine to allocate Distributed System Available Memory DSAM it found that the state word kept by NSINIT indicated that NS ARPA was not uninitialized This error message may be returned if an error is detected in the NS ARPA software NSINIT has aborted MMINIT returned an invalid security co
268. urce node NS NFTERR 54 Unable to start NFT service on the source node NS NFTERR 55 Unable to start NFT service on the target node NS NFTERR 56 Incoming connection has gone down NS NFTERR 57 MOVE option is not supported NS NFTWARN 58 4 16 The OVERWRITE option is not supported on the target computer An unexpected file system error occurred in creating a directory on the target node An unexpected file system error occurred in reference to a scratch file on the source computer An NFT server program could not be initialized on the source computer Either the server program could not be scheduled or the server could not enter the proper session This may be due to a lack of resources on the source node An NFT server program could not be initialized on the target computer Either the server program could not be scheduled or the server could not enter the proper session This may be due to a lack of resources on the target node An incoming connection to an NFT server program has gone down for an unknown reason The source computer does not support the MOVE option Program Specific Error Messages Remove the OVERWRITE option and use APPEND or REPLACE whichever is appropriate or specify a nonexistent target file name and try again Refer to the file system error qualifying string to determine the action to be taken Refer to the file system error qualifying string to determine t
269. us of the HP 3000 the HP 3000 is not replying HP 1000 is forced to secondary mode LINE IS UP WITH BUFFER The link to the HP 3000 has Proceed as usual SIZE XXX been established LU xxx IS LOCKED LU xxx IS NOT IN THE 3000 LU TABLE DSLIN attempts to lock the LU for primary connections The LU is already locked if another user is also running DSLIN NSINIT did not set up table space for this HP 3000 LU Try again later Shut down NS ARPA and bring it back up specifying LU xxx for HP 3000 communication PRIMARY CONNECT TIMED The connect timer expired Respond YES to overwrite the OUT before the HP 3000 replied data DSLIN WARNING CAN T CHECK S A M NO AVAILABLE CLASS NUMBERS DSLIN WARNING CAN T ALLOCATE xx WORDS OF S A M EVER DSLIN WARNING CAN T ALLOCATE xx WORDS OF S A M NOW DSLIN WARNING ERROR xxyy RELEASING CLASS NUMBER 4 18 No class numbers are available Check class number usage Regenerate the system with more class numbers if necessary Specified buffer size will never be available in System Available Memory Specify a smaller buffer size or regenerate the system with more System Available Memory Specified buffer size not currently available This condition may be due to fragmentation of System Available Memory SAM If SAM fragmentation occurs while the link is in use messages may be lost Refer to the NS ARPA 1000 Generation and Initialization
270. while trying to notification deallocate it This is an NS ARPA internal error 4502 Received a request to deallocate This error requires HP a socket of unknown kind This notification is an NS ARPA internal error 4800 An attempt to read in the This error requires HP preamble part of a path report notification stored in DSAM failed This is an NS ARPA internal error 4801 An attempt to read in the This error requires HP preamble part of a path report notification stored in DSAM failed This is an NS ARPA internal error 6 58 Logging Codes and Messages 4802 An attempt the overwrite the This error requires HP preamble part of a path reported notification stored in DSAM failed This is an NS ARPA internal error 5000 A graceful release indication This error requires HP from a remote system is notification received on a non VC socket This is an NS ARPA internal error 5001 A graceful release indication This error requires HP from a remote system is notification received on a VC socket which is not in an expected state This is an NS ARPA internal error Logging Codes and Messages 6 59 Entity SREG The following codes are printed to the Location field of the log record header when the event class is Warning Class 3 Error Class 4 Disaster Class 5 or RsrceLim Class 6 and the Entity printed in the Entity field is SREG The resource limit codes indicate that the Socket Registry is unable to acquire on
271. x field This is an NS ARPA internal error 26010 Memory Manager returned an This error requires HP error when ICMP attempted to notification copy data from DSAM The Memory Manager error is in the xx field This is an NS ARPA internal error 6 44 Logging Codes and Messages 26011 Memory Manager returned an This error requires HP error when ICMP attempted to notification move data from PING s data space to DSAM The Memory Manager error is in the xx field This is an NS ARPA internal error Memory Manager returned an This error requires HP error when PING attempted to notification append its data in DSAM The Memory Manager error is in the xx field This is an NS ARPA internal error 26502 PING was unable to cancel the __ If the error persists this error timer requires HP notification PING was unable to create its If the error persists when the own socket This might happen _ network has low traffic this error if there is heavy traffic on the requires HP notification network 26505 PING received an unknown If the error persists this error event message from ICMP requires HP notification 26506 PING encountered an invalid If the error persists this error domain report length The requires HP notification Nodal Registry might be corrupt 26515 Memory Manager returned an This error requires HP error when PING attempted to notification move data into DSAM The Memory Manager error is in the xx field Thi
272. y also be returned in the A and B registers after a DEXEC or utility call When a subsystem error is encountered by REMAT it is returned in its full alphanumeric form to the current log device When such an error is encountered by a PTOP RFA or a utility call only the error code is returned in the err parameter The A and B registers return the subsystem prefix in the A register and the error code in the B register e System Console Error Messages These error messages are returned to system LU 1 and are the result of unexpected as well as program download errors o Miscellaneous Alphanumeric Error Messages These error messages are also returned to the current log device They have no numeric equivalent and thus are not returned to any NS ARPA 1000 call Alphanumeric Error Messages 3 1 DSxx Error Messages The following errors are returned by the DS 1000 IV Compatible Services software and thus have the subsystem prefix DS They also include an error code an error qualifier in parentheses and an ASCII message DS 1 0 PROGRAM NOT FOUND DS 1 1 PROGRAM DOESN T EXIST DS 1 2 PROGRAM DOESN T EXIST DS 2 0 DUPLICATE FILE NAME DS 4 0 RECORD SIZE ERROR DS 6 0 ILLEGAL RECORD SIZE DS 10 0 NOT ENOUGH OR ERROR IN PARAMETERS DS 28 0 NO DCBS AVAILABLE DS 100 0 BREAK ENTERED DS00 0 LOCAL NODE IS NOT INITIALIZED DSXX Error Messages The program you attem

HP NSARPA/1000 User's Manual

Contents

Download Pdf Manuals

Related Search

Related Contents