Chapter 56 NBX (NetBIOS Over IPX) Messages

Cause  NBX is terminating because of an internally detected error, or via the NBXCOM 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 the Global NonStop Solution Center (GNSC) for analysis. If a backup is present, a backup takeover occurs. If no backup is present, then NBX must be restarted.

Cause  NBX 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  NBX was not started.

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

Cause  This message is displayed at NBX startup time. program-name includes the full NBX 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 NBX, or param-value is syntactically incorrect or out of range.

Effect  The PARAM is ignored and NBX 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 NBX.

Cause  NBX could not start the NBXCOM process from object file fname.

Effect   status1 and status2 are the results from NEWPROCESS.

Recovery  Correct PARAM GFTCOM^OBJECT and restart NBX.

Cause  NBX started a backup process in CPU cpunum.

Effect  This message is given for your information only.

Recovery  No action is required.

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

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

Recovery  No action is required.

Cause  NBX could not create a backup process.

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

Recovery  No action is required.

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

Effect  Message text is given.

Recovery  text is generally self-explanatory.

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

Effect  The NBX backup process was not started.

Recovery  See event znbx-evt-alloc. Correct the problem, then restart the backup process with the NBXCOM BACKUPCPU command.

Cause  Attempts to create the backup process repeatedly failed.

Effect  NBX will set BACKUPCPU to NONE.

Recovery  If the failure is due to a specific CPU being unavailable, use the NBXCOM BACKUPCPU command to specify another backup CPU number. For other failure reasons, contact the Global Mission Critical Solution Center (GMCSC).

Cause  NBX 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 the Global Mission Critical Solution Center (GMCSC).

Cause  NBX 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 the Global Mission Critical Solution Center (GMCSC).

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 NBXCOM TRACE ON command is used. This event is logged in addition to the text response returned to NBXCOM.

Recovery  Turn off the trace with the NBXCOM 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 NBXCOM TRACE ON command is used. This event is logged in addition to the text response returned to NBXCOM.

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 NBXCOM TRACE ON command is used, in addition to the text response returned to NBXCOM.

Recovery  If a trace is required, use the NBXCOM 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 NBX.

Cause  A trace file could not be opened because of a problem reading the NBX 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 NBXGTRED.

Recovery  Verify that the object file is secured to allow read access to the user ID of the NBX process. If the problem persists, contact the Global Mission Critical Solution Center (GMCSC).

Cause  The NBX 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 NBX failure. NBX 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 NBX variables.

Effect  The trace was not started.

Recovery  Report this problem to the Global Mission Critical Solution Center (GMCSC).

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 NBXCOM TRACE ON command.

Cause  NBX 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 NBXCOM SHUTDOWN command was received.

Effect  NBX 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 znbx-evt-event-backup-stopped event is generated. The TACL STOP process-name command can equivalently be used to stop NBX.

Recovery  No action is required.

Cause  An NBXCOM CPUSWITCH command was received.

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

Recovery  No action is required.

Cause  An NBXCOM DEBUG command was received. This command is normally used only by NBX developers.

Effect  The NBX 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 NBX into debug mode, but no event will be generated in that case.

Recovery  No action is required.

Cause  NBX is resuming operation after an NBXCOM DEBUG command.

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

Recovery  No action is required.

Cause  NBX has contacted NonStop IPX/SPX and is ready for sessions. This appears after ADD DOMAIN, after a backup takeover, or after NonStop IPX/SPX became available again after an outage.

Effect  NBX is available for use.

Recovery  No action is required.

Cause  NBX has lost contact with NonStop IPX/SPX, and all activity on the domain is stopped.

Effect  The NBXCOM STATUS DOMAIN command will provide some additional information. This usually indicates a problem with the NonStop IPX/SPX subsystem.

Recovery  No action is required in NBX, as NBX will automatically retry connection to NonStop IPX/SPX 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  NBX 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 NBX 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 NBX 6530 users.

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

Cause  $NBX 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 NBX.