NBT Manual Abstract This manual describes the installation and use of the Compaq NBT product. NBT provides NetBIOS services to users of Compaq NonStop TCP/IP 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 424773-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.
NBT 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 NBT 2.
3. NBT Commands (continued) Contents 3.
3. NBT Commands (continued) Contents 3. NBT Commands (continued) RSCMGR^DEPTH 3-42 SECURITY 3-43 SHUTDOWN 3-44 SOCKET^KA 3-45 START WINDOW 3-46 3-47 STATUS DOMAIN STATUS LOGON STATUS NAME 3-48 3-49 STATUS NCB 3-50 STATUS SESSION 3-51 STATUS WINDOW 3-52 STOP SESSION 3-53 STOP WINDOW TRACE 3-54 3-55 VERSION 3-57 4.
A. NBT Event Messages (continued) Contents A.
B. Support Commands Contents B. Support Commands ABEND B-1 BUP^TRACE B-1 CPUSWITCH B-1 DEBUG B-1 Glossary Index Figures Figure 1-1. NBT Connectivity 1-2 Tables Table i. Summary of Contents ix Table 2-1. NBT Files 2-2 Table 3-1.
Contents NBT Manual—424773-001 vi
What’s New in This Manual Manual Information NBT Manual Abstract This manual describes the installation and use of the Compaq NBT product. NBT provides NetBIOS services to users of Compaq NonStop TCP/IP 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 • • • • • • RESET DOMAIN on page 3-40 Using the NBTEST / RML Utility program on page 4-4 Additional NBTEST Help on page 4-7 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 NBT Manual—424773-001 viii
About This Manual The NBT Manual contains instructions for using the Compaq NBT system. NBT provides access to Compaq NetBIOS applications on G-series systems and is an alternative to MULTILAN software and hardware for Compaq NetBIOS applications on D-series systems. Who Should Read This Manual The NBT Manual is intended for Compaq computer-system managers and application programmers sho configure and run NetBIOS applications on NSK servers that connect to Compaq NonStop TCP/IP and NetBIOS.
Other Manuals About This Manual 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 TCP/IP Configuration and Management Manual TCP/IP Management Programming 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 NBT Manual—424773-001 xvi
1 Introducing NBT NBT provides access to Compaq NetBIOS applications on G-series systems and is a replacement to MULTILAN software and hardware for Compaq NetBIOS applications on D-series systems. NBT enables plug-compatible support for WSPTP and 6530 WINDOW application programming interfaces (APIs) as well as the resource manager and file server functions. Note. For G-series systems: MULTILAN software and hardware is not supported. The MLSRV file server is replaced by the SMB file server.
Introducing NBT Figure 1-1. NBT Connectivity Himalaya S-Series Server NonStop TS/MP Terminal Emulator TACL Compaq NBT NetBIOS Compaq NonStop TCP/IP TCP/IP Client TCP/IP Ethernet or Token-Ring LAN NetBIOS Name Server CDT 104.
2 Installation and Configuration This section provides the following information: • • • • • • • • Required Software NBT Software Installation NBT Files SMB File Server (G-series) and MLSRV (D-series) Configuration Remote Node NetBIOS Configuration NBT Domains Local Lookup Table for Internet Name Resolution NetBIOS Scopes Required Software NBT requires the following software to run on D-series and G-series systems: • Compaq NonStop TCP/IP software: • • Sockets library (included in NBT object file) T
NBT Files Installation and Configuration NBT Files Table 2-1 describes the NBT files and shows where they are placed by DSM/SCM. Table 2-1. NBT Files File Name Location Type Description NBTGTRED $SYSTEM.SYSTEM 100 Trace editor/formatter NBT * $SYSTEM.SYSTEM 700 NBT program object file NBTCHELP $SYSTEM.SYSTEM 101 NBT help text file NBTCOM $SYSTEM.
SMB File Server (G-series) and MLSRV (D-series) Configuration Installation and Configuration SMB File Server (G-series) and MLSRV (D-series) Configuration NBT 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 NBT.
NBT Domains 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.
NetBIOS Scopes Installation and Configuration Thus a name request can be resolved via the lookup table, by a remote node responding to a local broadcast, or remain unresolved. If unresolved, the NCB CALL or SEND DATAGRAM is rejected with an indication that the remote name could not be found. If resolved, NBT uses the resulting Internet address in the TCP CONNECT (for NCB CALL) request. Compaq NonStop TCP/IP software handles the routing to local and remote Internet networks.
NetBIOS Scopes Installation and Configuration NBT Manual—424773-001 2 -6
3 NBT Commands This section provides the following information: Running NBT on page 3-2 LOOKUP on page 3-32 Running NBTCOM on page 3-4 NODE^ALIAS on page 3-33 ABORT SESSION on page 3-6 OBEY on page 3-34 ABORT WINDOW on page 3-7 OPEN on page 3-35 ADD DOMAIN on page 3-8 OS2^RCV^NSR on page 3-36 ADD LOOKUP on page 3-10 OS2^SEND^NSR on page 3-37 ADD WINDOW on page 3-11 POOL on page 3-38 AUTO^ADD^WIN on page 3-13 RECV^SIZE on page 3-39 BACKUP / BACKUPCPU on page 3-14 RESET DOMAIN on page 3-40
Running NBT NBT Commands Running NBT To start NBT, use the standard TACL RUN command. 1> 2> 3> 4> LOGON SUPER.XXX,password CLEAR ALL PARAM ... RUN NBT / NAME $NBT , NOWAIT / NBT must be run using a SUPER group user ID or the object file must have the program identity (PROGID) bit set and be owned by a SUPER group user ID. This is due to the TCP/IP restriction on users of well-known Internet port addresses; TCP/IP requires that the SUPER group be used. The NBT object file must be licensed.
Running NBT NBT Commands PARAM SECURITY letter defines security access required for sensitive NBTCOM 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 NBTCOM NBT Commands Running NBTCOM NBTCOM is the system operator interface to NBT. NBTCOM provides for configuration, status, and maintenance requests. You can store your NBTCOM 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.
NBTCOM Command Summary NBT Commands Table 3-1.
ABORT SESSION NBT 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 NBT 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 NBT files (for example, $NBT.#WIN1). * aborts all configured windows.
ADD DOMAIN NBT Commands ADD DOMAIN ADD DOMAIN defines a logical LAN. One ADD DOMAIN is required to operate NBT. Do not use more than one DOMAIN. Note. Only one ADD DOMAIN should be used per NBT process. If the NODE^ALIAS command is used, it must precede any ADD DOMAIN commands. You do not need to start the TCP/IP process and define the subnet before using the ADD DOMAIN command.
ADD DOMAIN NBT Commands SCOPE scope-id defines the NetBIOS scope. scope-id can be *NONE* (the asterisks are required) to specify a null scope, or it can specify a name in Internet Domain Name format. Examples: SCOPE *NONE* SCOPE ABC.COM The default is *NONE*. scope-id when specified to NBT must match the corresponding parameter on all remote nodes. NBT will ignore any messages referring to a different NetBIOS scope.
ADD LOOKUP NBT Commands ADD LOOKUP ADD LOOKUP creates an entry in the local lookup table. The new lookup entry is available for use immediately after completion of this command. ADD LOOKUP netname internet-address netname specifies a NetBIOS name. Presently, the name is restricted to 1 through 16 letters and digits, with trailing spaces assumed. (The name can begin with a digit.) internet-address specifies an internet address in dotted form (for example, 128.1.2.
ADD WINDOW NBT Commands ADD WINDOW ADD WINDOW creates a static 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 NBT files (for example, $NBT.#WIN1).
ADD WINDOW NBT 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 NBT 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 $NBT with a qualifier which does not correspond to a defined window, NBT attempts to perform the following command: ADD WIN #name where #name was specified in the application open.
BACKUP / BACKUPCPU NBT 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.
COMMENT NBT Commands COMMENT COMMENT allows insertion of commentary text into NBTCOM input files. COMMENT text text specifies the comments to be inserted into NBTCOM input files. The text can include anything except a semicolon.
CONTROL^11 NBT Commands CONTROL^11 CONTROL^11 emulates ATP6100 instead of MULTILAN WS6530. Note. MULTILAN is not supported on G-series systems. NBT 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 NBT 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 NBT 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 LOOKUP NBT Commands DELETE LOOKUP DELETE LOOKUP removes an entry from the local lookup table. DELETE LOOKUP netname netname specifies the name, previously defined by ADD LOOKUP, to be deleted.
DELETE WINDOW NBT 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 NBT 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 NBT 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 NBT Commands EXIT EXIT stops NBTCOM. This is the normal method of terminating an NBTCOM session. NBT 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 NBTCOM.
FC NBT 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, NBTCOM 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 NBT Commands HELP HELP provides online documentation to NBTCOM users. The HELP file, named NBTCHELP, is located in the same volume and subvolume as the NBTCOM 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 NBTCHELP 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 NBT Commands INFO DOMAIN INFO DOMAIN displays static configuration information about a specified domain or all domains. This information includes: • • • • • • The domain name The TCP/IP driver process name and subnet name The node type and the IP address of the NBNS An indication that this is the present DEFAULT domain The configured NetBIOS scope ID The configured CASE setting INFO DOMAIN domain-name | * domain-name specifies the domain of interest. * specifies all configured domains.
INFO LOOKUP NBT Commands INFO LOOKUP INFO LOOKUP displays static configuration information about a specified local lookup name or the entire local lookup table. This information includes: • • The lookup name The associated Internet address INFO LOOKUP netname | * netname specifies the local lookup name of interest. * specifies all configured lookup names.
INFO PROCESS NBT Commands INFO PROCESS INFO PROCESS displays the setting of global parameters. INFO PROCESS INFO PROCESS shows the current settings for: AUTO^ADD^WIN CONTROL^11 DEFAULT DOMAIN DEFAULT SERVICE DYNAMIC^PRI KILL^PROC LOG^MON^INT NODE^ALIAS OS2^RCV^NSR OS2^SEND^NSR RECV^SIZE RFC1001^KA RSCMGR^DEPTH SOCKET^KA also displays the following information: NODE NAME This is the actual Expand node name where the NBT process is running.
INFO WINDOW NBT 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.
KILL^PROC NBT 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 NBT Commands LISTOPENS LISTOPENS displays all applications that have NBT 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 NBT Commands LOG^MON^INT LOG^MON^INT controls monitoring of logged-on workstations. When a remote workstation logs onto the NBT Resource Manager via the RMPCCOM LOGON command, NBT 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.
LOOKUP NBT Commands LOOKUP LOOKUP directs the order of name resolution using the local lookup table and local network broadcasts. LOOKUP BEFORE | AFTER | ONLY The default is LOOKUP BEFORE. This command specifies that the local lookup table is to be searched before, after, or instead of local network broadcast searches. Refer to Local Lookup Table for Internet Name Resolution on page 2-4 for further details.
NODE^ALIAS NBT 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, NBT uses the actual NonStop Expand node name of the system where NBT is running. When NODE^ALIAS is used, NBT uses the alias node name instead.
OBEY NBT Commands OBEY OBEY processes NBTCOM 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 NBT Commands OPEN OPEN opens the specified NBT process for subsequent commands. OPEN NBT-process-name NBT-process-name specifies the process to be opened. If another process is already open, that process is closed. If the OPEN fails, all NBTCOM commands requiring an application are rejected until a successful OPEN is completed. The version command is automatically performed after every OPEN command. Examples: OPEN $NBT OPEN \THERE.
OS2^RCV^NSR NBT Commands OS2^RCV^NSR OS2^RCV^NSR allows operation with OS/2 workstations. OS2^RCV^NSR Y | N The default is OS2^RCV^NSR N with most RFC1001 implementations. When set to OS2^RCV^NSR Y, incoming Node Status Requests are interpreted as Name Query Requests to resolve local (to NBT) NetBIOS name queries from remote workstations. This allows operation with OS/2 workstations which do not fully comply with RFC1001.
OS2^SEND^NSR NBT Commands OS2^SEND^NSR OS2^SEND^NSR allows operation with OS/2 workstations. OS2^SEND^NSR Y | N The default is OS2^SEND^NSR N with most RFC1001 implementations. When set to OS2^SEND^NSR Y, a Node Status Request, instead of a Name Query Request, is transmitted by NBT to resolve local (to NBT) queries for remote NetBIOS names. This allows operation with OS/2 workstations which do not fully comply with RFC1001.
POOL NBT 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.
RECV^SIZE NBT Commands RECV^SIZE RECV^SIZE specifies the input buffer size used when NBT accepts inbound data from TCP/IP during active sessions. RECV^SIZE n n specifies the new size in bytes. The default value is 1000, and the range is 100 to 4095. The present value of this parameter may be displayed by the INFO PROCESS command.
RESET DOMAIN NBT Commands RESET DOMAIN RESET DOMAIN clears counters displayed by STATUS DOMAIN, and will close and reopen the Session Server and Name Server sockets on ports 137 and 139. Type P and M nodes will display the next scheduled name refresh. RESET DOMAIN domain-name | * domain-name specifies the domain to be reset. * specifies that all configured domains be reset.
RFC1001^KA NBT Commands RFC1001^KA RFC1001^KA controls keep-alive messages as defined by the RFC1001 specification. When a NetBIOS session is active (6530 window, WSPTP CALL, or LISTEN), NBT periodically sends a special null message, which is discarded by the remote workstation NetBIOS driver. This message forces the TCP Transport Layer to verify that the session is still fully functional.
RSCMGR^DEPTH NBT 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 NBT 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 NBT Commands SHUTDOWN SHUTDOWN initiates an immediate NBT process termination. All active sessions are terminated. There are no parameters. SHUTDOWN You can also use the TACL STOP $process command.
SOCKET^KA NBT Commands SOCKET^KA SOCKET^KA controls keep-alive messages sent by the TCP Transport Layer. When a NetBIOS session is active (6530 window, or WSPTP CALL or LISTEN), the TCP Transport Layer periodically sends a special null message that is discarded by the remote workstation TCP transport driver. This message verifies that the session is still fully functional. If the message cannot be delivered, TCP eventually (in several minutes) notifies NBT that the session has failed.
START WINDOW NBT 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 NBT files (for example, $NBT.#WIN1).
STATUS DOMAIN NBT Commands STATUS DOMAIN STATUS DOMAIN displays the current operational status of a specified domain or for all configured domains.
STATUS LOGON NBT Commands STATUS LOGON STATUS LOGON displays the status of all logged-on users.
STATUS NAME NBT 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 NBT 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 $NBT.#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 NBT Commands STATUS SESSION STATUS SESSION displays the status of all active NetBIOS sessions for a specified domain or for all configured domains.
STATUS WINDOW NBT Commands STATUS WINDOW STATUS WINDOW displays the status of a specified window or for all configured windows.
STOP SESSION NBT 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 NBT 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 NBT files (for example, $NBT.#WIN1). * terminates all active windows.
TRACE NBT Commands TRACE TRACE controls program tracing. The NBT trace is implemented via an extended data segment (edseg) that is associated with a user-specified disk file. NBT creates trace entries by direct memory access to the edseg. When the trace is stopped, or if NBT 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 NBT 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 NBT application was started are used, not the defaults from the NBTCOM 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 NBT Commands VERSION VERSION displays the name, revision number, and revision date of NBT. There are no parameters.
VERSION NBT Commands NBT Manual—424773-001 3- 58
4 NBT Usage This section provides the following information and recommendations on using NBT with other applications: • • • • The NBT Backup Takeover Using NBT With Pathway Using WSPTP NCB Applications • • Commands Not Supported by NBT Presentation Interface Troubleshooting • • Using NBTGTRED Using the NBTEST / RML Utility program The NBT Backup Takeover If the NBT primary process fails, or the processor running the primary NBT process fails, the NBT backup process will continue operation.
Using WSPTP NCB Applications NBT Usage In PATHCOM, add sufficient TERM entries to support the peak simultaneous session load, and use any convenient window name in the ADD TERM FILE field, for example. SET TERM FILE $NBT.#PW01 ($NBT.#PW02 ...) When using the DEFAULT SERVICE feature, all workstations can share the identical configuration file. Using WSPTP NCB Applications The NBT WSPTP operation is almost identical to MULTILAN. Below are the differences: Note.
Troubleshooting NBT Usage • • NCB^POOL^KEY is not used. 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, NBT 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.
Using NBTGTRED NBT Usage Using NBTGTRED NBTGTRED formats a trace file created by the TRACE command. You can run NBTGTRED after a trace file is closed. RUN NBTGTRED / IN trace-file , OUT out-file / [ 80COL ] IN trace-file specifies the trace file named on the TRACE ON command. 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.
Using the NBTEST / RML Utility program NBT Usage 2. Run the NBTEST program from a TACL prompt, as follows: RUN NBTEST DOMAIN=$NBT.#DOM1 LISTEN where $NBT refers to the NBT process name and #DOM1 refers to the domain added to the NBT process.
Using the NBTEST / RML Utility program NBT Usage Some common responses after response NB13 are: NB14 CALL cannot complete. This indicates either that Compaq NBTEST is not running in LISTEN mode, or that there is no connectivity between the PC and the Compaq host. NB15 Call completed.
Using the NBTEST / RML Utility program NBT Usage If NBTEST does complete properly, then a baseline of connectivity is established. The next step is to run the actual applications, such as OV, SMB (on G-series systems), or MLSRV (on D-series systems), and so on. If the problem still persists, include the results of NBTEST when reporting the problem to your Compaq representative.
Using the NBTEST / RML Utility program NBT Usage The default names are usually adequate, but in rare cases, it may be required to use different NetBIOS names for NBTEST. NBTEST assigns default NetBIOS names, depending on the CALL-LISTEN mode, as follows: CALL MODE LISTEN MODE LOCALNAME NBTESTCALL NBTESTLISTEN REMOTENAME NBTESTLISTEN not used The REMOTENAME at the NBTEST CALL node must match the LOCALNAME at the NBTEST LISTEN node.
Using the NBTEST / RML Utility program NBT Usage The NBTEST RML function syntax to perform an RMPCCOM LOGON is NBTEST LOGON=group.user,password MACHINE=machine HOST=host [ ADAPTER=adapter ] group.user,password is the NSK userid and password. machine specifies the NetBIOS machine name. The machine name must match the Computer Name displayed on the Network Control Panel Identification screen. NBTEST will not perform any checks on this value. host is the Expand Node name of the NSK system.
Using the NBTEST / RML Utility program NBT Usage 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. Typically, Windows 95/98/NT uses adapter 0 for RFC1001 TCP/IP (used with NBT), adapter 6 for Netbeui, and adapter 7 for IPX (used with NBX).
A NBT Event Messages This appendix lists event messages that describe all the significant events that occur during NBT startup and operation. NBT uses the Event Management Service (EMS) to report these events. NBT reports events that have global effects on all NBT users. Events that only affect a single user or session are not reported. One exception is event znbt-evt-logon-suspended which could indicate a potential security violation.
znbt-evt-auto-add-fail NBT Event Messages znbt-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 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.
znbt-evt-backup-stopped NBT Event Messages znbt-evt-backup-stopped pname Backup stopped Cause. The NBT backup process stopped as a result of an NBTCOM BACKUP command, processor failure, or backup process failure. Effect. NBT will recreate the backup process when a backup processor is available, unless the backup process was stopped by the NBTCOM command. Recovery. No action is required. znbt-evt-checkalloc pname Checkallocatesegment err status Cause.
znbt-evt-cpuswitch NBT Event Messages znbt-evt-cpuswitch pname Primary process stopping - CPUSWITCH command 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. znbt-evt-domain-down pname Domain domain down on subnet subnet Cause. NBT has lost contact with the TCP/IP subnet, and all activity on the domain is stopped. Effect.
znbt-evt-exit-debug NBT Event Messages znbt-evt-exit-debug pname Process exiting debug 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. znbt-evt-gftcom-start-err pname Error status1 status2 starting GFTCOM^OBJECT fname Cause. NBT could not start the NBTCOM process from object file fname. Effect.
znbt-evt-misc NBT Event Messages znbt-evt-misc pname text Cause. This event is used for compatibility with previous releases of NBT. Effect. Message text is given. Recovery. text is generally self-explanatory. znbt-evt-nbns-contact pname Domain domain NetBIOS Name Server ip-addr contacted Cause. NBT has received its first message from the NetBIOS Name Server configured as IP address ip-addr for domain domain.
znbt-evt-parm-error NBT Event Messages znbt-evt-parm-error pname Error in PARAM param-name param-value 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.
znbt-evt-subnet-not-found NBT Event Messages znbt-evt-subnet-not-found pname Domain domain Subnet subnet-name not defined 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.
znbt-evt-trace-segment NBT Event Messages znbt-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 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.
znbt-evt-trace-stop NBT Event Messages znbt-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 NBTCOM TRACE ON command is used. This event is logged in addition to the text response returned to NBTCOM. Recovery. No action is required.
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 NBT operation, they should only be used when directed by support personnel. ABEND This command forces the NBT process to immediately terminate using the NonStop ABEND procedure. All active sessions are immediately stopped.
DEBUG Support Commands NBT Manual—424773-001 B- 2
Glossary This glossary defines terms used both in this manual and in other Compaq manuals that describe TCP/IP. Both industry-standard terms and Compaq terms are included. Because this glossary is for Compaq NonStop TCP/IP as a whole, not all of the terms listed here appear in this manual. address mask. A bit mask used to select bits from an Internet address for subnet addressing. The mask is 32 bits long and selects the network portion of the Internet address and one or more bits from the local portion.
autonomous system Glossary autonomous system. A collection of gateways and networks that fall under one administrative entity and cooperate closely to propagate network reachability (and routing) information among themselves using an interior gateway protocol of their choice. Gateways within an autonomous system have a high degree of trust. At least one gateway in an autonomous system must advertise networks in that system to a core gateway using EGP. baseband.
Class D Glossary Class D. A Class D address is a 4-octet multicast group address. The four high-order bits of the address are always 1110; therefore, the first octet is a number in the range 224 through 239 (%HE0 through %HEF). This means that an Internet can have a total of 268,435,456 multicast groups. collector. An EMS process that accepts event messages from subsystems and logs them in the event log. See also Event Management Service (EMS). Compare distributor. command message.
critical event Glossary critical event. A DSM event that is considered to be crucial to the operation of the system or network. Each subsystem determines which of its events are critical, designating them as such by setting the value of the emphasis token to TRUE. Compare noncritical event. CSMA (Carrier Sense Multiple Access). A characteristic of network hardware that operates by allowing multiple stations to contend for access to a transmission medium by listening to see if it is idle.
Distributed Systems Management Glossary Distributed Systems Management. A set of tools used to manage NonStop systems and EXPAND networks. These tools include the VIEWPOINT console application, the Subsystem Control Facility (SCF) for data communications subsystems, the Subsystem Programmatic Interface (SPI), the Event Management Service (EMS), the Distributed Name Service (DNS), and token-oriented programmatic interfaces to the management processes for various Compaq subsystems. distributor.
error Glossary error. In DSM interfaces, a condition that causes a command or other operation to fail. Contrast Warning. error list. In DSM programmatic interfaces, a group of tokens used within a response record to provide error and warning information. An error list consists of a list token that denotes an error list (different from the token that starts a data list or a generic list), followed by an error token, other tokens explaining the error (optional), and an end-list token.
Event Management Service (EMS) Glossary Event Management Service (EMS). A part of DSM used to provide event collection, event logging, and event distribution facilities. It provides for different event descriptions for interactive and programmatic interfaces, lets an operator or application select specific event-message data, and allows for the flexible distribution of event messages within a system or network. EMS has an SPI-based programmatic interface for both reporting and retrieving events.
filter Glossary filter. In 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 (for Himalaya S-series systems), filters are logical entities which allow frames received from the LAN to be sorted and delivered to a client.
header token Glossary header token. In an SPI message, a token that provides information pertaining to the message as a whole. Header tokens differ from other tokens in several ways: they exist in the buffer at initialization and their values are usually set by SSINIT, they can occur only once in a buffer, they are never enclosed in a list, they cannot be moved to another buffer with SSMOVE, and programs cannot position to them or retrieve their values using the NEXTCODE or NEXTTOKEN operation.
interactive command Glossary interactive command. In DSM, a command entered by a human operator rather than by a program. See also programmatic command. International Organization for Standardization (ISO). A United Nations organization, established to promote the development of standards to facilitate the international exchange of goods and services and to develop mutual cooperation in areas of intellectual, scientific, technological, and economic activity.
ISO Glossary ISO. See International Organization for Standardization (ISO). ITU-T. See International Telecommunications Union Telecommunications (ITU-T). IXF. See Information Xchange Facility (IXF). LAN (local area network). Any physical network technology that operates at high speed (usually tens of megabits per second through several gigabits per second) over short distances (up to a few thousand meters). LANMAN. See LAN manager (LANMAN) process. LAN. See local area network (LAN).
local area network (LAN) Glossary local area network (LAN). A network that is located in a small geographical area and whose communications technology provides a high-bandwidth, low-cost medium to which low-cost nodes can be connected. One or more LANs can be connected to the system such that the LAN users can access the system as if their workstations were connected directly to it. logical interface (LIF).
multicast Glossary multicast. A technique that allows copies of a single packet to be passed to a selected subset of all possible destinations. Some hardware (for example, Ethernet) supports multicast by allowing a network interface to belong to one or more multicast groups. Broadcast is a special form of multicast in which the subset of machines selected to receive a copy of a packet consists of the entire set. multifunction I/O board (MFIOB).
noncritical event Glossary noncritical event. A DSM event not too crucial to system or network operations. Each subsystem determines which of its events are noncritical by setting the value of the emphasis token to FALSE. Compare critical event. nonsensitive command. A DSM command that can be issued by any user or program allowed access to the target subsystem—that is, a command on which the subsystem imposes no further security restrictions.
packet Glossary packet. The unit of data sent across a packet switching network. While some Internet literature uses it to refer specifically to data sent across a physical network, other literature views the Internet as a packet switching network and describes IP datagrams as packets. Packet Internet Groper (PING). The name of a program used in the Internet to test the reachability of destinations by sending them an ICMP echo request and waiting for a reply.
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).
ServerNet adapter Glossary ServerNet adapter. A customer-replaceable unit (CRU) that connects peripheral devices to the rest of the system through a ServerNet bus interface (SBI). A ServerNet adapter is similar in function to an I/O controller logic board (LB) and backplane interconnect card (BIC) in Himalaya K-series servers. ServerNet addressable controller (SAC).
SPI message Glossary SPI message. In DSM programmatic interfaces, a message specially formatted by the SPI procedures for communication between a management application and a subsystem or between one subsystem and another. An SPI message consists of a collection of tokens. Note that an SPI message is a single block of information sent at one time, as one interprocess message.
Subsystem Control Point (SCP) Glossary Subsystem Control Point (SCP). .n DSM, the management process for all Compaq data communications subsystems. There can be several instances of this process. Applications using SPI send all commands for data communications subsystems to an instance of this process, which in turn sends the commands on to the manager processes of the target subsystems. SCP also processes a few commands itself.
Tandem LAN Access Method (TLAM). Glossary Tandem LAN Access Method (TLAM). The TLAM software provides an industry-standard interface for accessing LANs from the Compaq system. Based on the IEEE 802.2 Logical Link Control standard, TLAM supports 802.2 Type 1 connectionless service as well as the MULTILAN/NetBIOS protocol. With TLAM, you do not need to write applications for a specific type of LAN. TCP (Transmission Control Protocol).
Trivial File Transfer Protocol (TFTP) Glossary Trivial File Transfer Protocol (TFTP). The Internet standard protocol for file transfer with minimal capability and minimal overhead. TFTP depends only on the unreliable, connectionless datagram delivery service (UDP), so it can be used on machines like diskless workstations that keep such software in ROM and use it to bootstrap themselves. UDP. See User Datagram Protocol (UDP). User Datagram Protocol (UDP).
wild-card character Glossary wild-card character. A character that stands for any possible character(s) in a search string or in a name applying to multiple objects. In DSM object-name templates, two wild-card characters can appear: ? for a single character and * for zero, one, or more consecutive characters. See also object-name template. WSPTP. See MULTILAN WSPTP X.25. The CCITT standard protocol for transport-level network service. Originally designed to connect terminals to computers, X.
Index A Access methods 3-16 Applications 6530 Windows 1-1 custom 1-1 File Server 1-1 IXF 1-1 NetBIOS ix, 1-1 Outside View 1-1 Pathway 1-1, 3-13, 4-1 Resource Manager 1-1 TACL 1-1, 3-13 TEDIT 1-1 WSPTP 4-2 ATP6100 3-16 B Backup takeover 4-1 Buffer pool See Pool Bytes, counts of 3-47 C Commands ABORT SESSION 3-6 ABORT WINDOW 3-7 ADD DOMAIN 2-4, 3-8 ADD LOOKUP 3-10 ADD WINDOW 3-11 AUTO^ADD 4-1 AUTO^ADD^WIN 3-13 BACKUP 3-14 BACKUPCPU 3-14 COMMENT 3-15 CONTROL^11 3-16 DEFAULT DOMAIN 3-8, 3-17 Commands (contin
D Index Commands (continued) STOP SESSION 3-53 STOP WINDOW 3-54 storing in EDIT file 3-4 summary of 3-4 TRACE 3-55, 4-4 VERSION 3-57 WINDOW_NAME 2-4 Configuration 6530 windows 3-2 adjusting parameters 3-2 domains 3-2 PCT 2-3 Remote Node NetBIOS 2-3 scope 4-3 simplification of 4-1 Counters, clearing of 3-40 K Keep-alive messages 3-41, 3-45 L LAN Spooler (LANSPOOL) 1-1 Licensing, required for object file 3-2 Local Lookup Table 1-1 Logon, status of 3-48 Lookup tables 2-4, 3-10, 3-19 M Domains 2-4 default
O Index P Nodes NBNS 3-8 remote 2-5 type B 1-1, 2-4, 3-8 type M 1-1, 2-4, 3-8 type P 1-1, 2-4, 3-8 Null messages 3-41 O Options adding a window name 3-11, 3-28, 3-46, 3-52, 3-54 adding services to windows 3-11 defining default domain 3-17 defining NetBIOS scope 3-9 determining backup CPU number 3-14 gets specifying buffer allocations 3-38 identifying a SUBNET 3-8 identifying nodes 3-8 internet address for lookup 3-10 netname for lookup 3-19 number of backup CPUs 3-14 puts specifying buffer releases 3-38
S Index RMPCCOM LOGOFF 4-8 using the NBTEST RML Function 4-9 RMPCCOM LOGON 4-8 using the NBTEST RML Function 4-8 S SCOPE field 2-5, 4-3 Scopes, messages received for 3-47 Security precautions 3-31 setting 3-43 Services specifying a name 3-18 Sessions, status of 3-51 Socket Library interface of TCP/IP 1-1 Software, required 2-1 Software, TCP/IP 2-1 Status requests 3-4 System operator interface 3-4 W Windows deleting 3-20 dynamic 1-1, 4-1 service 3-12 static 1-1, 2-3, 3-11 status 3-52 Workstations remote
