Chapter 55 NBT (NetBIOS Over TCP/IP) Messages

Cause  NBT is terminating because of an internally detected error, or via the NBTCOM ABEND command. reason is an internal code for the error detected.

Effect  A saveabend dump file will be created.

Recovery  Forward the dump file to your service provider for analysis. If a backup is present, a backup takeover occurs. If no backup is present, then NBT must be restarted.

Cause  NBT could not allocate an extended segment for its buffer pool at startup time. status is the result of the NonStop ALLOCATESEGMENT procedure. size is the number of words requested.

Effect  NBT was not started.

Recovery  Check the value for PARAM POOL^SIZE, and determine that adequate space exists on the disk volume containing the NBT object file.

Cause  This message is displayed at NBT startup time. program-name includes the full NBT version and release date.

Effect  This message is given for your information only.

Recovery  No action is required.

Cause  Either param-name is an invalid PARAM for NBT, or param-value is syntactically incorrect or out of range.

Effect  The PARAM is ignored and NBT starts up with default values for the particular PARAM. If param-name is GFTCOM^XXX, then one or two, but not all three, of the GFTCOM^OBJECT, GFTCOM^IN, and GFTCOM^OUT PARAMs were specified.

Recovery  Correct param-name and param-value, then stop and restart NBT.

Cause  NBT could not start the NBTCOM process from object file fname.

Effect   status1 and status2 are the results from NEWPROCESS.

Recovery  Correct PARAM GFTCOM^OBJECT and restart NBT.

Cause  NBT started a backup process in CPU cpunum.

Effect  This message is given for your information only.

Recovery  No action is required.

Cause  The NBT backup process stopped as a result of an NBTCOM BACKUP command, CPU failure, or backup process failure.

Effect  NBT will recreate the backup process when a backup CPU is available, unless the backup process was stopped by the NBTCOM command.

Recovery  No action is required.

Cause  NBT could not create a backup process.

Effect  status1 and status2 are the results of NEWPROCESS. NBT will retry the request.

Recovery  No action is required.

Cause  This event is used for compatibility with previous releases of NBT.

Effect  Message text is given.

Recovery  text is generally self-explanatory.

Cause  During backup creation, NBT could not allocate an extended segment for the buffer pool in the backup process.

Effect  The NBT backup process was not started.

Recovery  See NBT operator message 0002. Correct the problem, then restart the backup process with the NBTCOM BACKUPCPU command.

Cause  Attempts to create the backup process repeatedly failed.

Effect  NBT will set BACKUPCPU to NONE.

Recovery  If the failure is due to a specific CPU being unavailable, use the NBTCOM BACKUPCPU command to specify another backup CPU number. For other failure reasons, contact your service provider.

Cause  NBT encountered an error while checkpointing data to the backup process. fecode is the result of the NonStop procedure CHECKPOINT.

Effect  The backup is stopped.

Recovery  Recovery is usually automatic. If the error persists, contact your service provider.

Cause  NBT encountered an error while checkpointing a file open to the backup process. fecode is the result of the NonStop procedure CHECKPOINT.

Effect  The backup is stopped.

Recovery  Recovery is usually automatic. If the error persists, contact your service provider.

Cause  A trace file of size bytes has been opened on disk file fname.

Effect  This event is logged when the PARAM TRACE^FILE is used and when the NBTCOM TRACE ON command is used. This event is logged in addition to the text response returned to NBTCOM.

Recovery  Turn off the trace with the NBTCOM TRACE OFF command after you have captured the desired information.

Cause  The trace file has been closed.

Effect  This event is logged when the PARAM TRACE^FILE is used and when the NBTCOM TRACE ON command is used. This event is logged in addition to the text response returned to NBTCOM.

Recovery  No action is required.

Cause  A trace of size bytes could not be opened to disk file file. status is the result from NonStop ALLOCATESEGMENT.

Effect  This is mainly useful when PARAM TRACE^FILE is used, but it also occurs when the NBTCOM TRACE ON command is used, in addition to the text response returned to NBTCOM.

Recovery  If a trace is required, use the NBTCOM TRACE ON command. Check that the space size is available on the device at fname. Check that if fname already exists, it can be deleted by a user with the user ID of NBT.

Cause  A trace file could not be opened because of a problem reading the NBT object file.

Effect  The trace mechanism needs to copy finite-state machine transition tables from the object files to the trace file, which are used later by NBTGTRED.

Recovery  Verify that the object file is secured to allow read access to the user ID of the NBT process. If the problem persists, contact your service provider.

Cause  The NBT backup process became the primary process.

Effect  reason explains the manner in which the primary process stopped.

Recovery  If the failure is due to a primary process failure, check for other events that would indicate an NBT failure. NBT will automatically restart a new backup whenever the appropriate CPU is available.

Cause  The trace file was not opened to disk file fname. status1 and status2 are internal NBT variables.

Effect  The trace was not started.

Recovery  Report this problem to your service provider.

Cause  This occurs when PARAM TRACE^FILE is defined before PARAM TRACE^SIZE.

Effect  The trace is opened at the default size of 500k (bytes), and the PARAM TRACE^FILE is ignored.

Recovery  Correct the order of the PARAM statements. If the default size is inappropriate, restart the trace with the appropriate size using the NBTCOM TRACE ON command.

Cause  NBT received a NonStop file system error fecode when replying to an application request.

Effect  This message provides additional information useful when other errors are detected.

Recovery  No action is required. If other problems are detected, include this information in a trouble report.

Cause  An NBTCOM SHUTDOWN command was received.

Effect  NBT stops immediately, returning error code 201 to any outstanding application file system requests, and terminating any active sessions with remote nodes. If the backup was running, a separate znbt-evt-event-backup-stopped event (NBT operator message 0007) is generated. The TACL STOP process-name command can equivalently be used to stop NBT.

Recovery  No action is required.

Cause  An NBTCOM CPUSWITCH command was received.

Effect  This is normally used only for NBT backup testing. The NBT primary process stops, and the backup process will take over automatically.

Recovery  No action is required.

Cause  An NBTCOM DEBUG command was received. This command is normally used only by NBT developers.

Effect  The NBT process is suspended while in debug mode, so applications will not get any responses to file system requests, and remote sessions may timeout. Note that the TACL DEBUG command can also be used to place NBT into debug mode, but no event will be generated in that case.

Recovery  No action is required.

Cause  NBT is resuming operation after an NBTCOM DEBUG command.

Effect  Various application timeouts or remote session timeouts can be expected while NBT is in debug mode, or just after debug mode is exited.

Recovery  No action is required.

Cause  NBT has contacted the TCP/IP subnet on both the Name Server and Session Server ports and is ready for sessions. This appears after ADD DOMAIN, after a backup takeover, or after the TCP/IP subnet became available again after an outage.

Effect  NBT is available for use.

Recovery  No action is required.

Cause  NBT has lost contact with the TCP/IP subnet, and all activity on the domain is stopped.

Effect  The NBTCOM STATUS DOMAIN command will provide some additional information. This usually indicates a problem with the TCP/IP subsystem.

Recovery  No action is required in NBT, as NBT will automatically retry connection to TCP/IP every minute.

Cause  wsname is the NetBIOS machine name of the remote workstation that has failed three consecutive RMPCCOM logon attempts, and it suspends for one minute from further logon attempts.

Effect  This may signify an attempt to defeat security.

Recovery  NBT will automatically allow further logon attempts from the workstation after one minute.

Cause  An attempt to automatically add a 6530 window has failed. This occurs when AUTO^ADD is set to Y and an application, such as TACL or Pathway, opens NBT using an undefined window name. This almost always is the result of a buffer pool shortage.

Effect  The window is not added, so the application window will not be available for remote NBT 6530 users.

Recovery  Use the NBTCOM POOL command to check buffer pool utilization. If required, change PARAM POOL^SIZE and restart NBT.

Cause  NBT has received its first message from the NetBIOS Name Server configured as IP address ip-addr for domain domain. This appears after ADD DOMAIN, after a backup takeover, and after a previous event znbt-evt-nbns-no-response (NBT operator message 1005).

Effect  This message is given for your information only.

Recovery  No action is required.

Cause  NBT is not able to contact the NetBIOS Name Server configured as IP address ip-addr for domain domain.

Effect  For Type M nodes, NBT will attempt to resolve names via local broadcast. For Type P nodes, NBT cannot resolve names, and new sessions are not allowed.

Recovery  Verify that the NetBIOS Name Server node is operational and has a network connection to the Tandem system. NBT will automatically reconnect when the name server resumes operation.

Cause  $NBT was started by a user ID not in the SUPER group.

Effect  The process stops.

Recovery  Log on to a SUPER group user ID and restart NBT.

Cause  Subnet subnet-name is not defined under the TCP/IP subsystem.

Effect  NBT was unable to connect to the subnet.

Recovery  If the spelling on the ADD DOMAIN statement is wrong, correct it and then stop and restart NBT. If it is correct, check the TCP/IP system. NBT will recover automatically when the TCP/IP subnet is properly configured.

Cause  An unusual error occurred while trying to communicate with the TCP/IP process to retrieve the TCP/IP subnet configuration.

Effect  NBT was unable to communicate with the TCP/IP process.

Recovery  Try the SCF command INFO SUBNET subnet-name. If there is a problem, correct it and NBT should automatically recover within one minute. If the problem persists, contact your service provider.

Cause  An error occurred communicating to the TCP/IP process for NBT DOMAIN domain. error is the file system of socket error code. object may see Name-Server for UDP port 137 activity, Session-Server for TCP port 139 activity, or LSN n for TCP activity for active and pending sessions. operation is the socket function which encountered the error.

Effect  Errors for a session (object, specifies LSN n) terminate the session. Other errors perform RESET DOMAIN.

Recovery  No action is required. If the error persists, the message is useful to your service provider.