NBX Manual Abstract This manual describes the installation and use of the Compaq NBX product. NBX provides NetBIOS services to users of IPX/SPX software. Product Version N/A Supported Releases This manual supports D43.02 and all subsequent D4x releases and G06.07 and all subsequent G-series releases until otherwise indicated in a new edition.
Document History Part Number Product Version Published 424774-001 N/A December 1999 Ordering Information For manual ordering information: domestic U.S. customers, call 1-800-243-6886; international customers, contact your local sales representative. Document Disclaimer Information contained in a manual is subject to change without notice. Please check with your authorized representative to make sure you have the most recent information.
NBX Manual Glossary Index Figures Tables What’s New in This Manual vii Manual Information vii New and Changed Information vii About This Manual ix Who Should Read This Manual ix How This Manual Is Organized ix Where to Get More Information ix Your Comments Invited x Notation Conventions xi 1. Introducing NBX 2.
3. NBX Commands (continued) Contents 3.
3. NBX Commands (continued) Contents 3. NBX Commands (continued) START WINDOW 3-42 STATUS DOMAIN 3-43 3-44 STATUS LOGON STATUS NAME 3-45 STATUS NCB 3-46 STATUS SESSION 3-47 STATUS WINDOW 3-48 STOP SESSION 3-49 STOP WINDOW TRACE 3-50 3-51 VERSION 3-53 4. NBX Usage Using NBX With Pathway 4-1 Using WSPTP NCB Applications 4-2 Commands Not Supported by NBX 4-2 4-2 Presentation Interface Troubleshooting 4-3 Using NBXGTRED 4-3 Using the NBTEST / RML Utility program 4-4 A.
A. NBX Event Messages (continued) Contents A.
Tables Contents Tables Table i. Summary of Contents ix Table 2-1. NBX Files 2-2 Table 3-1.
Contents NBX Manual—424774-001 vi
What’s New in This Manual Manual Information NBX Manual Abstract This manual describes the installation and use of the Compaq NBX product. NBX provides NetBIOS services to users of IPX/SPX software. Product Version N/A Supported Releases This manual supports D43.02 and all subsequent D4x releases and G06.07 and all subsequent G-series releases until otherwise indicated in a new edition.
New and Changed Information What’s New in This Manual • • • Additional NBTEST Parameters on page 4-7 RMPCCOM LOGON using the NBTEST RML Function on page 4-8 RMPCCOM LOGOFF using the NBTEST RML Function on page 4-9 NBX Manual—424774-001 viii
About This Manual The NBX Manual contains instructions for using the Compaq NBX system. NBX provides access to Compaq NetBIOS applications connected to workstations that use Novell ® IPX 1 and NetBIOS on G-series systems and is an alternative to MULTILAN software and hardware for Compaq NetBIOS applications connected to workstations that use Novell ® IPX 2 and NetBIOS on D-series systems.
Other Manuals About This Manual Manuals describing the Himalaya K-series servers are organized into several sets of manuals, which are fully described in the NonStop Himalaya K10000/K20000 Planning and Configuration Guide. Other Manuals Depending on the tasks you are performing, you might also need one of the following manuals: • • • • • • • • • • • • • • TCP/IP and IPX/SPX Programming Manual IPX/SPX Configuration and Management Manual Remote Server Call (RSC) R5.1.
Notation Conventions About This Manual Many of the improvements you see in manuals are a result of suggestions from our customers. Please take this opportunity to help us improve future manuals. Notation Conventions Hypertext Links Blue underline indicates a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described. For example: This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 3-2.
General Syntax Notation About This Manual | Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: INSPECT { OFF | ON | SAVEABEND } … Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: M address-1 [ , new-value ]... [ - ] {0|1|2|3|4|5|6|7|8|9}...
Notation for Messages About This Manual !i,o. In procedure calls, the !i,o notation follows an input/output parameter (one that both passes data to the called procedure and returns data to the calling program). For example: error := COMPRESSEDIT ( filenum ) ; !i,o !i:i. In procedure calls, the !i:i notation follows an input string parameter that has a corresponding parameter specifying the length of the string in bytes.
Notation for Management Programming Interfaces About This Manual arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: proc-name trapped [ in SQL | in SQL file system ] { } Braces. A group of items enclosed in braces is a list of all possible items that can be displayed, of which one is actually displayed.
Change Bar Notation About This Manual Change Bar Notation Change bars are used to indicate substantive differences between this edition of the manual and the preceding edition. Change bars are vertical rules placed in the right margin of changed portions of text, figures, tables, examples, and so on. Change bars highlight new or revised information. For example: The message types specified in the REPORT clause are different in the COBOL85 environment and the Common Run-Time Environment (CRE).
Change Bar Notation About This Manual NBX Manual—424774-001 xvi
1 Introducing NBX NBX provides access to Compaq NetBIOS applications connected to workstations that use Novell ® IPX 1 and NetBIOS on G-series systems and is a replacement to MULTILAN software and hardware for Compaq NetBIOS applications connected to workstations that use Novell ® IPX 2 and NetBIOS on D-series systems. NBX supports WSPTP and 6530 WINDOW application programming interfaces (APIs) as well as the resource-manager and file-server functions. Note.
Introducing NBX Figure 1-1. NBX Connectivity Himalaya S-Series Server NonStop TS/MP Terminal Emulator SMB File Server Compaq NBX NetBIOS NetWare Client IPX/SPX Compaq NonStop IPX/SPX Ethernet LAN or Token-Ring LAN NetWare Server CDT 105.
2 Installation and Configuration This section provides the following information: • • • • • • • Required Hardware and Software NBX Software Installation NBX Files SMB File Server (G-series) and MLSRV (D-series) Configuration Remote Node NetBIOS Configuration Remote Node NetWare Configuration NBX Domains Required Hardware and Software NBX requires the following software to run on D-series and G-series systems: • Compaq NonStop IPX/SPX software For information about Compaq NonStop IPX/SPX on D-series
NBX Files Installation and Configuration NBX Files Table 2-1 describes the NBX files and shows where they are placed by DSM/SCM. Table 2-1. NBX Files File Name Location Type Description NBXGTRED $SYSTEM.SYSTEM 100 Trace editor/formatter NBX * $SYSTEM.SYSTEM 700 NBX program object file NBXCHELP $SYSTEM.SYSTEM 101 NBX help text file NBXCOM $SYSTEM.
SMB File Server (G-series) and MLSRV (D-series) Configuration Installation and Configuration SMB File Server (G-series) and MLSRV (D-series) Configuration NBX only supports DOMAIN objects. This means that the following command must be used for SMBCOM, on G-series systems, and MLSRVCOM, on D-series systems: LAN DOMAIN $NBT.#DOM1 LAN ADAPTER and LAN POOL commands will not function with NBX.
Remote Node NetWare Configuration Installation and Configuration When using the NODE^ALIAS command, all workstation references to the Expand Node name should specify the NODE^ALIAS instead of the actual node name. In the PCT.INI file, these are the HOST_NAME and WINDOW_NAME commands. In RMPCCOM, this is the SET HOST command. When using Compaq Outside View or similar 3rd party emulator, specify the NODE^ALIAS node-name in the HOST_NAME or NODE_NAME field of the MULTILAN configuration screen.
3 NBX Commands This section provides the following information: Running NBX on page 3-2 IPX^RESEND on page 3-29 Running NBXCOM on page 3-4 IPX^SESS^TO on page 3-30 ABORT SESSION on page 3-6 KILL^PROC on page 3-31 ABORT WINDOW on page 3-7 LISTOPENS on page 3-32 ADD DOMAIN on page 3-8 LOG^MON^INT on page 3-33 ADD WINDOW on page 3-9 NODE^ALIAS on page 3-34 AUTO^ADD^WIN on page 3-11 OBEY on page 3-35 BACKUP / BACKUPCPU on page 3-12 OPEN on page 3-36 CALL^RETRY on page 3-13 POOL on page 3-37
Running NBX NBX Commands Running NBX To start NBX, use the standard TACL RUN command. 1> CLEAR ALL 2> PARAM ... 3> RUN NBX / NAME $NBX , NOWAIT , PRI 180 / NBX can be run from any user ID. The NBX object file must be licensed. Licensing is required due to a privileged procedure used for user ID verification and dynamic session process management. Since NBX performs network protocol functions, it must operate at a relatively high priority to avoid timeouts and other network problems.
Running NBX NBX Commands PARAM SECURITY letter defines security access required for sensitive NBXCOM commands. Sensitive commands are commands that alter the application environment. Nonsensitive commands are those that only report status information without changing anything in the application. The default is O (Owner). Values are from the set NAGCOU.
Running NBXCOM NBX Commands Running NBXCOM NBXCOM is the system operator interface to NBX. NBXCOM provides for configuration, status, and maintenance requests. You can store your NBXCOM commands in an EDIT format disk file or enter them conversationally. You can direct your output to a terminal, printer, disk file, or spooler. Standard OBEY and FC commands are provided.
NBXCOM Command Summary NBX Commands Table 3-1.
ABORT SESSION NBX Commands ABORT SESSION ABORT SESSION immediately terminates a session. ABORT SESSION session-lsn | * session-lsn refers to a local session number that can be displayed by the STATUS SESSION command. The specified session is aborted. * aborts all configured sessions.
ABORT WINDOW NBX Commands ABORT WINDOW ABORT WINDOW immediately terminates a 6530 window session. ABORT WIN[DOW] window-name | * ABORT WIN[DOW] WIN and WINDOW are equivalent. window-name specifies a window to be aborted. The window name must be a pound sign (#) followed by a letter, then 0 to 6 letters or digits. The window name qualifies the file name used in Compaq applications to open NBX files (for example, $NBX.#WIN1). * aborts all configured windows.
ADD DOMAIN NBX Commands ADD DOMAIN ADD DOMAIN defines a logical LAN. One ADD DOMAIN is required to operate NBX.Do not use more than one DOMAIN. Note. Only one ADD DOMAIN should be used per NBX process. If the NODE^ALIAS command is used, it must precede any ADD DOMAIN commands. You do not need to start the NonStop IPX process before using the ADD DOMAIN command.
ADD WINDOW NBX Commands ADD WINDOW ADD WINDOW creates a 6530 window and associates it with a domain. ADD WIN[DOW] window-name domain-name [ ,SERVICE service-name ] ADD WIN[DOW] WIN and WINDOW are equivalent. window-name specifies a window to be added. The window name must be a pound sign (#) followed by a letter, then 0 to 6 letters or digits. The window name qualifies the file name used in Compaq applications to open NBX files (for example, $NBX.#WIN1).
ADD WINDOW NBX Commands Advantage of Service Windows: • • • All remote workstations have the same PCT.INI file. No RMPCCOM LOGON is required, and there is no security problem of having a BAT file containing a Compaq password. PCT startup is faster because there is no NEWPROCESS or other dynamic session overhead. Applications for service windows, like standard static windows, are previously started.
AUTO^ADD^WIN NBX Commands AUTO^ADD^WIN AUTO^ADD^WIN controls the automatic creation of windows. This can greatly simplify configuration files in Pathway and TACL. To display the current setting of this parameter, use the INFO PROCESS command. AUTO^ADD^WIN Y | N Y | N defaults to Y. When set to Y, if an application opens $NBX with a qualifier which does not correspond to a defined window, NBX attempts to perform the following command: ADD WIN #name where #name was specified in the application open.
BACKUP / BACKUPCPU NBX Commands BACKUP / BACKUPCPU BACKUPCPU controls the application backup process. BACKUP is a synonym for BACKUPCPU. BACKUPCPU cpu cpu can be one of the following: ? displays the current setting, along with the current backup status. NONE stops a backup process if one is already running. No new backup processes will be created. number specifies a number in the range 0 through 15 inclusive. The application will use the specified processor for its backup process.
CALL^RETRY NBX Commands CALL^RETRY CALL^RETRY specifies the number of retry attempts when attempting to establish a session to a remote node as a result of a WSPTP NCB CALL command. To display the current setting of this parameter, use the INFO PROCESS command. CALL^RETRY n n specifies the number of retry attempts. The default is 4. The Range is 2 to 19. Increase this value for very busy networks or if slow routers or bridges are used.
CALL^TO NBX Commands CALL^TO CALL^TO specifies the timeout, in seconds, between retries when attempting to establish a session to a remote node as a result of a WSPTP NCB CALL command. To display the current setting of this parameter, use the INFO PROCESS command. CALL^TO n n specifies the number of seconds. The default is 2 (seconds). The range is 1 to 5. Increase this value if slow routers or bridges are used.
COMMENT NBX Commands COMMENT COMMENT allows insertion of commentary text into NBXCOM input files. COMMENT text text specifies the comments to be inserted into NBXCOM input files. The text can include anything except a semicolon.
CONTROL^11 NBX Commands CONTROL^11 CONTROL^11 emulates ATP6100 instead of MULTILAN WS6530. Note. MULTILAN is not supported on G-series systems. NBX provides the same MULTILAN APIs on D- and G-series systems, and continues to support NSK applications and remote workstation NetBIOS applications using these APIs. Most Compaq access methods, such as ATP6100, use certain conventions with respect to inactive sessions. MULTILAN WS6530 uses a different convention.
DEFAULT DOMAIN NBX Commands DEFAULT DOMAIN DEFAULT DOMAIN specifies a domain to be used as a default for ADD WINDOW commands and for WSPTP NCB type 1 requests. To display the current setting of this parameter, use the INFO PROCESS command. DEFAULT DOMAIN domain-name | *NONE* | FIRST^ADDED domain-name refers to a previously defined domain to be used as a default. *NONE* disables the default. ADD WINDOW commands must specify a domain name, and WSPTP NCB type 1 requests are rejected.
DEFAULT SERVICE NBX Commands DEFAULT SERVICE DEFAULT SERVICE specifies a service name to be used as a default for ADD WINDOW commands. DEFAULT SERVICE does not apply to windows automatically added during a dynamic window session. To display the current setting of this parameter, use the INFO PROCESS command. DEFAULT SERVICE service-name | *NONE* service-name specifies the service name to be used for subsequent ADD WINDOW commands that do not specify a service field.
DELETE WINDOW NBX Commands DELETE WINDOW DELETE WINDOW removes a previously added 6530 window from the configuration. Dynamic windows are automatically deleted upon session termination. Windows created by AUTO^ADD^WIN Y are automatically deleted when all applications using the window terminate or close the window. DELETE WIN[DOW] window-name DELETE WIN[DOW] WIN and WINDOW are equivalent. window-name specifies a window to be deleted.
DYNAMIC^PRI NBX Commands DYNAMIC^PRI DYNAMIC^PRI defines a default priority for new process requests performed during dynamic window initiation. This is to allow the priority of the created processes to be independent of the NBX process priority. The remote workstation can override this priority by using the PCT.INI file command SPS / PRI pri /. To display the current setting of this parameter, use the INFO PROCESS command. DYNAMIC^PRI pri pri specifies an integer in the range 1 to 199.
EXIT NBX Commands EXIT EXIT stops NBXCOM. This is the normal method of terminating an NBXCOM session. NBX is not affected. There are several forms of the EXIT command: EXIT E control Y eof on disc or process IN file eof in an OBEY file, returns to the previous OBEY file or IN file, and does not terminate NBXCOM.
FC NBX Commands FC FC provides a typical FC facility; refer to Compaq TACL or EDIT documentation for a full description. Like the EDIT product’s implementation, NBXCOM allows FC to be combined with other commands on a line. When an FC command is combined in this manner, it takes effect after all other commands on the line are processed; then the FC applies to the entire line, including the FC itself. FC commands are not allowed in OBEY files, or when the IN file is not the same as the OUT file.
HELP NBX Commands HELP HELP provides online documentation to NBXCOM users. The HELP file, named NBXCHELP, is located in the same volume and subvolume as the NBXCOM program object file. The file is in standard Compaq EDIT file format, with lines of text formatted according to certain rules. These rules are explained in comment lines within the NBXCHELP file itself; list this file with EDIT or FUP for more documentation. HELP [ALL] [command] HELP displays a summary of the HELP file.
INFO DOMAIN NBX Commands INFO DOMAIN INFO DOMAIN displays static configuration information about a specified domain or all domains. This information includes: • • • The domain name The NonStop IPX protocol process An indication that this is the present DEFAULT domain INFO DOMAIN domain-name | * domain-name specifies the domain of interest. * specifies all configured domains.
INFO PROCESS NBX Commands INFO PROCESS INFO PROCESS displays the setting of global parameters. INFO PROCESS INFO PROCESS shows the current settings for: AUTO^ADD^WIN CALL^RETRY CALL^TO CONTROL^11 DEFAULT DOMAIN DEFAULT SERVICE DYNAMIC^PRI IPX^FRAME IPX^KA IPX^RESEND IPX^SESS^TO KILL^PROC LOG^MON^INT NODE^ALIAS RSCMGR^DEPTH also displays the following information: NODE NAME This is the actual Expand node name where the NBX process is running.
INFO WINDOW NBX Commands INFO WINDOW INFO WINDOW displays static configuration information about a specified 6530 window or all configured 6530 windows. This information includes: • • The 6530 window name The domain name INFO WIN[DOW] window-name | * INFO WIN[DOW] WIN and WINDOW are equivalent. window-name specifies the 6530 window name of interest. The window name must be a pound sign (#) followed by a letter, then 0 to 6 letters or digits.
IPX^FRAME NBX Commands IPX^FRAME IPX^FRAME limits the size of outbound Ethernet frames sent by NBX. To display the current setting of this parameter, use the INFO PROCESS command. IPX^FRAME n n specifies the maximum frame size in bytes, in the range of 100 to 528. The default is 528.
IPX^KA NBX Commands IPX^KA IPX^KA controls the time interval between periodic keep-alive messages sent by NBX to detect session failure. Lowering this parameter increases overhead but more quickly detects a failed session (usually caused by workstation power-off or network errors). Refer to IPX^SESS^TO on page 3-30 for additional information. Note that Novell ® NetBIOS usually sends a keep-alive message from the workstation once every 5 seconds. This parameter is not normally changed by the user.
IPX^RESEND NBX Commands IPX^RESEND IPX^RESEND controls the timeout interval, after a session message is sent and no acknowledgment is received from the remote, before retransmitting the message. This parameter is not normally changed by the user. To display the current setting of this parameter, use the INFO PROCESS command. IPX^RESEND n n specifies a timeout interval in the range of 1 through 30, in 0.1 second units (0.1 to 3.0 seconds). The default is 2 (0.2 seconds).
IPX^SESS^TO NBX Commands IPX^SESS^TO IPX^SESS^TO controls the time interval for NBX to wait for any session messages from the remote before terminating the session. NBX expects to receive session messages as a result of normal inbound traffic, acknowledgments to normal outbound traffic or keep-alive messages, or normal inbound keep-alive messages. If nothing is received for this time period, the session is terminated.
KILL^PROC NBX Commands KILL^PROC KILL^PROC controls automatic termination of processes associated with a dynamic window when the window session terminates. To display the current setting of this parameter, use the INFO PROCESS command. KILL^PROC Y | N Y | N Y, the default, stops all processes that have a home terminal equal to the terminated window when a dynamic window session terminates.
LISTOPENS NBX Commands LISTOPENS LISTOPENS displays all applications that have NBX open. LISTOPENS LISTOPENS displays one line for each OPEN of the application by another process. Examples The following three sample output lines are folded due to printer limitations: 1. G083I process.term [cpu,pin] fnum userid programfile home [backup] 2. $TCP1.#W742 1,47 fn=6 id=20,33 $SYSTEM.SYSTEM.PATHTCP $TERM4 bak=2,52 fn=6 3. \CENTDIV.01,050.#COMMAND.COMMAND fn=3 id=255,255 $SYSTEM.SYSTEM.
LOG^MON^INT NBX Commands LOG^MON^INT LOG^MON^INT controls monitoring of logged-on workstations. When a remote workstation logs onto the NBX Resource Manager via the RMPCCOM LOGON command, NBX verifies that the workstation has not been powered off or rebooted. This prevents a security problem where another person can power up the workstation and obtain security privileges of the previously logged-on user.
NODE^ALIAS NBX Commands NODE^ALIAS NODE^ALIAS changes the Expand node name used in forming the NetBIOS names for the resource manager and 6530 windows. Remote workstations specify node names in the RMPCCOM SET HOST, the PCT.INI HOST_NAME, and the WINDOW_NAME commands. Without NODE^ALIAS, NBX uses the actual NonStop Expand node name of the system where NBX is running. When NODE^ALIAS is used, NBX uses the alias node name instead.
OBEY NBX Commands OBEY OBEY processes NBXCOM commands from an EDIT format file. OBEY edit-file-name edit-file-name specifies the EDIT file in which the commands are listed. Commands can be nested up to six levels deep.
OPEN NBX Commands OPEN OPEN opens the specified NBX process for subsequent commands. OPEN NBX-process-name NBX-process-name specifies the process to be opened. If another process is already open, that process is closed. If the OPEN fails, all NBXCOM commands requiring an application are rejected until a successful OPEN is completed. The version command is automatically performed after every OPEN command. Examples: OPEN $NBX OPEN \THERE.
POOL NBX Commands POOL POOL verifies the integrity of the entire buffer pool and provides useful information for tuning PARAM POOL^SIZE. POOL TOTAL SIZE shows word size of pool. IN USE shows words currently in use in the user buffer area. HIGH shows the highest value of IN USE since process startup or the most recent backup takeover. GETS shows total number of buffer allocation requests. PUTS shows total number of buffer releases.
RESET DOMAIN NBX Commands RESET DOMAIN RESET DOMAIN clears counters displayed by STATUS DOMAIN. RESET DOMAIN domain-name | * domain-name specifies the domain to be reset. * specifies that all configured domains be reset.
RSCMGR^DEPTH NBX Commands RSCMGR^DEPTH RSCMGR^DEPTH controls the number of resource manager threads created by subsequent ADD DOMAIN commands. When a domain is added, the then current value of RSCMGR^DEPTH is used for the lifetime of the domain. Changing RSCMGR^DEPTH after the domain is added will have no effect on that domain. The resource manager handles the RMPCCOM LOGON and LOGOFF commands and dynamic windows (PCT and IXF).
SECURITY NBX Commands SECURITY SECURITY displays and modifies the application’s security setting. This setting is initially established by the PARAM SECURITY command, with a default of O. SECURITY no-parameters letter no-parameters displays the current setting. The value O is the default. letter sets the security to the specified letter, which must be from the set NACGUO with standard Compaq file security interpretation.
SHUTDOWN NBX Commands SHUTDOWN SHUTDOWN initiates an immediate NBX process termination. All active sessions are terminated. There are no parameters. SHUTDOWN You can also use the TACL STOP $process command.
START WINDOW NBX Commands START WINDOW START WINDOW activates a 6530 window. START WINDOW is only needed after a STOP WINDOW or ABORT WINDOW. START WIN[DOW] window-name | * START WIN[DOW] WIN and WINDOW are equivalent. window-name specifies the window to be started. The window name must be a pound sign (#) followed by a letter, then 0 to 6 letters or digits. The window name qualifies the file name used in Compaq applications to open NBX files (for example, $NBX.#WIN1).
STATUS DOMAIN NBX Commands STATUS DOMAIN STATUS DOMAIN displays the current operational status of a specified domain or for all configured domains. This status information includes: • • • The NonStop IPX protocol process name in use The last file error code from NonStop IPX The number of messages sent and received through NonStop IPX STATUS DOMAIN domain-name | * domain-name displays the status of the specified domain. * displays the status for all configured domains.
STATUS LOGON NBX Commands STATUS LOGON STATUS LOGON displays the status of all logged-on users.
STATUS NAME NBX Commands STATUS NAME STATUS NAME displays the status of all names created by WSPTP ADD NAME, ADD WINDOW, and the internal resource manager name.
STATUS NCB NBX Commands STATUS NCB STATUS NCB displays the status of all NetBIOS control blocks active for a specified domain or for all configured domains. The display includes: • NCB type: • • • • • • • • • • WSPTP—an application using the $NBX.#WSPTP interface. The application process ID is also displayed. RSCMGR—the integrated resource manager WIN-M / WIN-R—two NCBs associated with each 6530 window. The window name is also displayed.
STATUS SESSION NBX Commands STATUS SESSION STATUS SESSION displays the status of all active NetBIOS sessions for a specified domain or for all configured domains.
STATUS WINDOW NBX Commands STATUS WINDOW STATUS WINDOW displays the status of a specified window or for all configured windows.
STOP SESSION NBX Commands STOP SESSION STOP SESSION immediately terminates the specified session or all active sessions. The sessions can be associated with a 6530 window, a WSPTP CALL or LISTEN, or a resource manager thread. STOP SESSION lsn | * lsn refers to a local session number that can be displayed by the STATUS SESSION command. The specified session is terminated. * terminates all active sessions.
STOP WINDOW NBX Commands STOP WINDOW STOP WINDOW immediately terminates the specified window or all active windows. STOP WIN[DOW] window-name | * STOP WIN[DOW] WIN and WINDOW are equivalent. window-name specifies the name of the window to be stopped. The window name must be a pound sign (#) followed by a letter, then 0 to 6 letters or digits. The window name qualifies the file name used in Compaq applications to open NBX files (for example, $NBX.#WIN1). * terminates all active windows.
TRACE NBX Commands TRACE TRACE controls program tracing. The NBX trace is implemented via an extended data segment (edseg) that is associated with a user-specified disk file. NBX creates trace entries by direct memory access to the edseg. When the trace is stopped, or if NBX stops for any reason, the Compaq NonStop system flushes all remaining information from the edseg to the disk file. You can control the trace file size.
TRACE NBX Commands ON filename [ , size ] starts a trace on the specified unstructured disk file. The file name should be fully qualified; if it is not qualified, the default volume and subvolume in effect at the time the NBX application was started are used, not the defaults from the NBXCOM startup. If the file name does NOT begin with $ or \, the keyword ON is required. A file of the specified size will be created. If a trace is already open, it is first closed.
VERSION NBX Commands VERSION VERSION displays the name, revision number, and revision date of NBX. There are no parameters.
VERSION NBX Commands NBX Manual—424774-001 3- 54
4 NBX Usage This section provides the following information and recommendations on using NBX with other applications: • • • Using NBX With Pathway Using WSPTP NCB Applications • • Commands Not Supported by NBX Presentation Interface Troubleshooting • • Using NBXGTRED Using the NBTEST / RML Utility program Using NBX With Pathway When preconfiguring terminals, you should use both of the following: PATHCOM - SET TERM AUTORESTART 10 NBXCOM - CONTROL^11 Y If the SCOBOL application captures errors, or
Using WSPTP NCB Applications NBX Usage Using WSPTP NCB Applications The NBX WSPTP operation is almost identical to MULTILAN. Below are the differences: Note. MULTILAN is not supported on G-series systems. NBX provides the same MULTILAN APIs on D- and G-series systems, and continues to support NSK applications and remote workstation NetBIOS applications using these APIs.
Troubleshooting NBX Usage • For NCB^LSN, NCB^LSN^EXT, NCB^NUM, and NCB^NUM^EXT, values are assigned differently from MULTILAN. To be compatible with standard NetBIOS rules, NBX will never assign the values 0 or 255 to the NCB^LSN field. Other than skipping these values, the NCB^LSN^EXT is used as the high-order byte of the NCB^LSN field and the sessions are assigned the lowest available LSN. Likewise, NCB^NUM^EXT is used as a high-order byte to NCB^NUM, and the lowest available name index is used.
Using the NBTEST / RML Utility program NBX Usage OUT out-file specifies any line-oriented output file, like a spooler, a printer, and so on. The output lines are 90 to 100 characters long, unless the 80COL (80-column) option is used. 80COL indicates that timestamps are to be edited on a separate line to keep output in 80 columns. This is useful for displaying to a CRT.
Using the NBTEST / RML Utility program NBX Usage NB10 Another Compaq NBTEST is already running in LISTEN mode NB09 Another PC NBTEST is already running in LISTEN mode NB20 Normal operation. NBTEST is ready to accept a session from a remote NBTEST running in CALL mode When the NB20 message appears, the Compaq NBTEST waits for the PC NBTEST. To abort the NBTEST LISTEN, use BREAK and the TACL STOP command.
Using the NBTEST / RML Utility program NBX Usage Running PC NBTEST in LISTEN Mode and Compaq NBTEST in CALL Mode Some NBX applications, such as LANSPOOL, FASTPSMB, and user WSPTP programs, have the Compaq host running in CALL mode and the remote PC in LISTEN mode. To test this direction of connectivity, first run PC NBTEST in LISTEN mode: 1. Bring up the NetBIOS protocol stack driver according to the vendor’s instructions. 2.
Using the NBTEST / RML Utility program NBX Usage Additional NBTEST Help Running the NBTEST programs without any parameters will display a brief help screen describing all parameters. For the NSK version, enter the following command at a TACL prompt: RUN NBTEST For the MS-DOS version, enter the following command at a DOS or Command window prompt: NBTEST Additional NBTEST Parameters NBTEST supports several parameters in addition to DOMAIN, CALL, and LISTEN, described above.
Using the NBTEST / RML Utility program NBX Usage The REMOTENAME at the NBTEST CALL node must match the LOCALNAME at the NBTEST LISTEN node. The LOCALNAME of the CALL node is not important per se, but it must be different from the LOCALNAME of the LISTEN node. NBTEST allows names of 1 to 16 letters and numbers. All alphabetic characters are converted to upper case. DELAY=number The DELAY parameter slows down NBTEST PC by delaying before sending each test message to the Compaq host.
Using the NBTEST / RML Utility program NBX Usage machine specifies the NetBIOS machine name. The machine name must match the Computer Name displayed on the Network Control Panel Identification screen. NBTEST will perform any checks on this value. host is the Expand Node name of the NSK system. adapter is the specified NetBIOS stack or adapter for NBTEST on PC’s running multiple NetBIOS stacks. The default is 0, and values from 0 to 9 are allowed.
Using the NBTEST / RML Utility program NBX Usage NBX Manual—424774-001 4- 10
A NBX Event Messages This appendix lists event messages that describe all the significant events that occur during NBX startup and operation. NBX uses the Event Management Service (EMS) to report these events. NBX reports events that have global effects on all NBX users. Events that only affect a single user or session are not reported. One exception is event znbx-evt-logon-suspended which could indicate a potential security violation.
znbx-evt-auto-add-fail NBX Event Messages znbx-evt-auto-add-fail pname Automatic ADD WIN failure window 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.
znbx-evt-backup-stopped NBX Event Messages znbx-evt-backup-stopped pname Backup stopped Cause. The NBX backup process stopped as a result of an NBXCOM BACKUP command, processor failure, or backup process failure. Effect. NBX will recreate the backup process when a backup processor is available, unless the backup process was stopped by the NBXCOM command. Recovery. No action is required. znbx-evt-checkalloc pname Checkallocatesegment err status Cause.
znbx-evt-cpuswitch NBX Event Messages znbx-evt-cpuswitch pname Primary process stopping - CPUSWITCH command 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. znbx-evt-domain-down pname Domain domain down on subnet subnet Cause. NBX has lost contact with NonStop IPX/SPX, and all activity on the domain is stopped. Effect.
znbx-evt-exit-debug NBX Event Messages znbx-evt-exit-debug pname Process exiting debug 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. znbx-evt-gftcom-start-err pname Error status1 status2 starting GFTCOM^OBJECT fname Cause. NBX could not start the NBXCOM process from object file fname. Effect.
znbx-evt-not-super-group NBX Event Messages znbx-evt-not-super-group pname Must be run from SUPER group 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. znbx-evt-parm-error pname Error in PARAM param-name param-value Cause. Either param-name is an invalid PARAM for NBX, or param-value is syntactically incorrect or out of range. Effect.
znbx-evt-stopping NBX Event Messages znbx-evt-stopping pname Process stopping - SHUTDOWN command 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.
znbx-evt-trace-segment NBX Event Messages znbx-evt-trace-segment pname Trace not started to fname size size allocatesegment error status 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.
znbx-evt-trace-stop NBX Event Messages znbx-evt-trace-stop pname Trace stopped 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.
znbx-evt-trace-stop NBX Event Messages NBX Manual—424774-001 A -10
B Support Commands This appendix describes the support commands ABEND, BUP^TRACE, CPUSWITCH, and DEBUG. These commands are intended for use by support and development personnel to facilitate testing and problem analysis. Since they cause severe interruption of NBX operation, they should only be used when directed by support personnel. ABEND This command forces the NBX process to immediately terminate using the NonStop ABEND procedure. All active sessions are immediately stopped.
DEBUG Support Commands NBX Manual—424774-001 B- 2
Glossary This glossary defines terms used both in this manual and in other Compaq manuals that describe NonStop IPX/SPX. Because this glossary is for Compaq NonStop IPX/SPX as a whole, not all of the terms listed here appear in this manual. ABORT. A sensitive command that terminates the operation of a NonStop IPX/SPX object abruptly without regard for interruption of data transfer. ABORTING. The state of an object, indicating that it is responding to an ABORT command or some type of malfunction.
application program interface (API) Glossary application program interface (API). A general term for a software interface that allows an application program to talk to or control another service-providing program so that the application program can use the services provided. For example, an application program in the form of a client might use an API to talk to a server program. ARP. See Address Resolution Protocol (ARP). attribute. In Distributed Systems Management (DSM), a characteristic of an entity.
DELETE Glossary DELETE. A sensitive command that removes a process from the NonStop IPX/SPX subsystem. Distributed Systems Management (DSM). A set of tools used to manage Compaq NonStop systems and networks. DSM tools include the ViewPoint console application, Subsystem Control Facility (SCF), and Event Management Service (EMS) interfaces to the management processes for various Compaq subsystems. distributor.
FASTP Glossary FASTP. Net Spool print process. filter. In Event Management Service (EMS), a file containing a list of criteria against which incoming event messages can be compared. The messages are allowed to pass (all criteria met) or not pass (one or more criteria failed). In the ServerNet LAN systems access (SLSA) subsystem, a filter provides a logical mechanism where frames received from the local area network (LAN) can be sorted and then delivered to a particular client. forwarding distributor.
LANMAN Glossary LANMAN. See LAN Manager (LANMAN) process. LAN Manager (LANMAN) process. LANMAN is provided as part of the ServerNet LAN systems access (SLSA) subsystem. The NonStop Kernel subsystem starts LANMAN, and the Subsystem Control Facility (SCF) product module manages it. LANMAN is started as a generic process and runs as a NonStop process pair in the host system processors. LANMAN starts and manages the SLSA subsystem objects and starts the LAN Monitor (LANMON) process.
Media Access Control (MAC) address Glossary Media Access Control (MAC) address. A value in the Medium Access Control sublayer of the IEEE/ISO/ANSI LAN architecture that uniquely identifies an individual station that implements a single point of physical attachment to a local area network (LAN). MFIOB. See multifunction I/O board (MFIOB). MLAD. See MULTILAN Attachment Device (MLAD). MLSRV. See MULTILAN File Server (MLSRV). multicast.
NetWare Core Protocol (NCP) Glossary NetWare Core Protocol (NCP). A Novell protocol for request-response access to NetWare services, such as printing and filing. NetWare Loadable Module (NLM). A software module that conforms to a standard that allows the module to function with and communicate with other NLMs and with NetWare software. NetWare server. A system that runs NetWare network operating system (NOS) software.
object Glossary object. In general Compaq usage, one or more of the devices, lines, processes, and files in a Compaq subsystem; any entity subject to independent reference or control by one or more subsystems. In Distributed Systems Management (DSM) usage, an entity subject to independent reference and control by a subsystem: for example, the IPXMGR process $ZMGR or the IPXPROTO process $ZN0. object-name template. In Distributed Systems Management (DSM), a name that stands for more than one object.
Pathway/TS Glossary Pathway/TS. A transaction processing (TP) product that supports requester programs that run in the Guardian environment and communicate with terminals and intelligent devices. It requires the services of NonStop Transaction Services/MP (NonStop TS/MP). PC6530 Terminal Emulator (PCT). A Compaq program that runs on an IBM-compatible PC with the MS-DOS operating system and emulates a 6530 terminal. PCONSOLE.
protocol Glossary protocol. A formal description of message formats and the rules two or more machines must follow to exchange those messages. Protocols can describe low-level details of machineto-machine interfaces (for example, the order in which the bits from a byte are sent across a wire) or high-level exchanges between application programs (for example, the way in which two programs transfer a file across the Internet).
sensitive command Glossary sensitive command. A Subsystem Control Facility (SCF) command that can be issued only by a restricted set of users, such as the owner of a subsystem process. For Compaq data communications subsystems, the sensitive commands are those that can change the state or configuration of objects, start or stop tracing, or change the values of statistics counters. Contrast nonsensitive command. Sequenced Packet Exchange (SPX).
socket number Glossary socket number. For NonStop IPX/SPX, the unique port identifier portion of the network address, node address, and port identifier combination that makes up an IPX address. A Berkeley Software Distribution (BSD) Internet port is the equivalent of a NonStop IPX/SPX socket number. SPX. See Sequenced Packet Exchange (SPX). SQL. See Structured Query Language (SQL). SSID. See subsystem ID (SSID). START. A sensitive command that starts a NonStop IPX/SPX object. STARTED.
subsystem Glossary subsystem. In general terms, the software and/or hardware facilities that give users access to a set of communications services. In Distributed Systems Management (DSM), a program or set of processes that manages a cohesive set of objects. Each subsystem has a process through which applications can request services by issuing commands defined by that subsystem; in some cases, this process is the entire subsystem. Many subsystems also have interactive interfaces.
Tandem Failure Data System (TFDS) Glossary Tandem Failure Data System (TFDS). A diagnostic tool that is a component of the Compaq NonStop Kernel operating system. TFDS isolates software problems and provides automatic processor failure data collection, diagnosis, and recovery services. TFDS monitors processors and automatically initiates a processor dump if a processor fails. The failed processor is reloaded automatically, and the processor is analyzed along with the incident.
token map Glossary token map. In Distributed Systems Management (DSM) programmatic interfaces, a structure that contains decoding information for a DSM extensible structured token. Also, a variable name used to reference an extensible structured token. The token map includes a token code and a description of the token value: its fields, the null values of those fields, and the versions of the fields.
ViewPoint console application Glossary ViewPoint console application. An extensible interactive application for operators, provided as part of Distributed Systems Management (DSM). ViewPoint allows a system or a network to be controlled from a single terminal.
Index A Access methods 3-16 Applications 6530 Windows 1-1 custom 1-1 EDIT XVS 1-1 File Server 1-1 IXF 1-1 NetBIOS ix, 1-1 Outside View 1-1 Pathway 1-1, 3-11, 4-1 Resource Manager 1-1 TACL 1-1, 3-11 WSPTP 1-1, 4-2 ATP6100 3-16 B Buffer pool See Pool C Commands ABORT SESSION 3-6 ABORT WINDOW 3-7 ADD DOMAIN 2-4, 3-8 ADD WINDOW 3-9 AUTO^ADD 4-1 AUTO^ADD^WIN 3-11 BACKUP 3-12 BACKUPCPU 3-12 CALL^RETRY 3-13 CALL^TO 3-14 COMMENT 3-15 CONTROL^11 3-16 DEFAULT DOMAIN 3-8, 3-17 DEFAULT SERVICE 3-18, 4-1 Commands (co
D Index Configuration 6530 windows 3-2 adjusting parameters 3-2 domains 3-2 PCT 2-3 Remote Node NetBIOS 2-3 Remote Node NetWare 2-4 simplification of 4-1 Tandem MLSRV MULTILAN File Server 2-3 Counters, clearing of 3-38 D Domains 2-4 default 3-8, 3-17 E L LAN Spooler (LANSPOOL) 1-1 Licensing, required for object file 3-2 Logon, status of 3-44 M Maintenance requests 3-4 Messages, counts of 3-43 MLSRV See MULTILAN File Server MULTILAN 1-1, 4-2 MULTILAN File Server (MLSRV) 1-1, 2-3 MULTILAN WS6530 3-16 N
P Index Options (continued) defining default domain 3-17 determining backup CPU number 3-12 gets specifying buffer allocations 3-37 identifying a SUBNET 3-8 number of backup CPUs 3-12 puts specifying buffer releases 3-37 specifying a domain 3-8 specifying a service name 3-18 specifying a session 3-6 specifying a window 3-7, 3-9, 3-19, 3-26, 3-42 specifying words in user buffer 3-37 Output examples of open applications 3-32 Output, direction of 3-4 Outside View 2-3 P PARAM statements 3-2 Parameters BACKUP
T Index T TACL 1-1, 3-11 Timeout intervals 3-29 Traces files 3-3, 4-3 hardware 4-3 NBTGTRED 4-3 using the TRACE command 3-51 W Windows 6530 3-9 deleting 3-19 dynamic 1-1 service 3-10 static 1-1, 2-3 status 3-48 Workstations remote 3-20, 3-33 specifying nodes 3-34 WSPTP 1-1, 4-2 NBX Manual—424774-001 Index- 4
