NETBAsE for MPE Reference Guide
610 Newport Center Drive, Suite 1400, Newport Beach, CA 92660
This manual contains proprietary information which is protected by copyright. The information in this manual is subject to change without notice and does not represent a commitment on the part of Quest Software. The software described in this manual is furnished under a license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of this agreement.
T A B L E O F C O N T E N T S NetBase Reference Guide Introduction - Welcome to NetBase ....................................................................................................................... i NetBase Functionality............................................................................................................................. iii NetBase Performance................................................................................................................................
NetBase for MPE Reference Guide STOP...............................................................................................................................................2-43 TRACE ...........................................................................................................................................2-46 UNDEFER.......................................................................................................................................2-48 Chapter 3 - Using CONFIG......
Table of Contents REBUILD........................................................................................................................................4-50 RESET ............................................................................................................................................4-51 SHADOW........................................................................................................................................4-53 SQLIN ..........................................
NetBase for MPE Reference Guide Chapter 6 - NetBase NFA..................................................................................................................................... 6-1 NFA Overview ......................................................................................................................................6-2 Buffering ...........................................................................................................................................
Table of Contents Chapter 9 - NetBase Statistics ............................................................................................................................9-1 Collecting Statistics ...............................................................................................................................9-2 Reporting Statistics................................................................................................................................9-4 Running NBLGDUMP.............
NetBase for MPE Reference Guide Additional Utilities............................................................................................................................13-11 QUARK+ ......................................................................................................................................13-11 NBCOPY.......................................................................................................................................
I N T R O D U C T I O N Welcome to NetBase NetBase is comprehensive networking software consisting of five major services. The NetBase services allow a network of Hewlett-Packard commercial computers to work together acting as one large system.
Introduction In This Guide In this guide, you will find the following chapters: Chapter 1 explains the NetBase components. Chapter 2 describes the NBCTRL commands. Chapter 3 describes the CONFIG commands. Chapter 4 describes the NBDIR commands. Chapter 5 explains NetBase Shadowing. Chapter 6 explains Network File Access. Chapter 7 explains NetBase Spooling. Chapter 8 explains NetBase AutoRPM. Chapter 9 explains NetBase Statistics. Chapter 10 discusses NetBase and third party products.
Welcome to NetBase NetBase Functionality NetBase brings functionality and performance to HP systems that previously was not possible. Customers faced with expensive upgrades have found that adding a machine and using NetBase to distribute the computing load is less costly and provides better performance. Companies that own multiple systems may use NetBase to correct an imbalance in processor loading.
Introduction Transporting Spooling Output Efficiently One desirable feature of networked computers is the ability to share printing resources. NetBase minimizes both networking and spooling overhead by efficiently transporting the output to the desired computer and spooling the output on the destination computer only. NetBase Spooling can be as fast as local spooling.
Welcome to NetBase NetBase Performance NetBase is fast! Of all the features that NetBase offers, performance is perhaps the most valuable. Networking a transaction is more costly in terms of elapsed time and machine resources than performing the same transaction locally. The key to enhanced performance is that NetBase minimizes the number of network transactions. Minimizing Network Transactions When NetBase was developed, great care was taken to ensure that the code was written as efficiently as possible.
Introduction Improving Data Access Application programs usually access data in a very predictable manner. Generally speaking, a DBFIND to an IMAGE dataset is followed by one or more mode 5 or 6 DBGETs. This predictability is true for a variety of other calls. NetBase makes use of these facts when servicing calls to remote files and databases.
Welcome to NetBase How Does NetBase Work? NetBase works by intercepting and looking at all calls and file requests to the file system. Requests to local files are passed directly to MPE to be executed locally, while requests to remote files are passed by NetBase to the appropriate computer where the file resides. To determine where a particular file exists, NetBase uses its own directory. The directory is the key to the simplicity of NetBase implementation.
Introduction A Different Approach NetBase approaches shadowing differently from other shadowing products in several ways. First, since NetBase does not use IMAGE logging, all types of disk files are shadowed, not just databases. One product can now be used to maintain a complete copy of all application files. NetBase Shadowing also guarantees that updates occur to the shadow copy in the exact order that they occurred against the master.
Welcome to NetBase NetBase NFA The NetBase product is built around Network File Access (NFA). NFA allows programs running on one computer to access files in the domain of another computer. With NetBase NFA, a file can be placed anywhere in the network without having to change programs, file equations or UDCs. Additionally, NetBase does not require any type of remote sessions or virtual terminals, and it does not count against the OS user license limit on the remote system.
Introduction NetBase Spooling Network spooling is a standard NetBase feature. NetBase Spooling provides several transparent methods for defining the printing environment and uses a minimal amount of overhead. NetBase Spooling allows users to move or copy selected spool files from one computer to another. Users are provided with flexible syntax for specifying spool files to move, making a simple task of directing an output file to the appropriate device.
Welcome to NetBase Creating a Local Copy Another NetBase feature is that any spooled device can be configured to create a local copy of the output automatically. This extra copy can be used as a backup copy, or it can be deleted by NetBase once the entire spool file has been transmitted. If a network failure should occur while a process is outputting, and the remote spooler is defined with the COPY option, NetBase will allow the process to continue using the local spool copy.
Introduction AutoRPM AutoRPM is the NetBase interface to Remote Process Management (RPM), a feature of HewlettPackard’s Network Services. AutoRPM provides the ability to run an interactive program on a remote computer. NetBase AutoRPM is completely transparent to the user. The user is not aware that the program is actually running on another machine. AutoRPM provides two major financial values. As an option for load balancing and reduced processing costs, NetBase AutoRPM saves you money.
Welcome to NetBase NetBase Statistics Using NetBase Statistics, application systems can be easily profiled, monitored and tuned. NetBase provides a method of capturing statistics on file access as well as measuring process overhead. NetBase also provides reports that clearly illustrate the captured information. The accumulation of data is a by-product of running applications through NetBase. The collection of statistics can be enabled or disabled at any time for any subset of data required.
Introduction Other NetBase Services Two other NetBase services are available: NetBase SQL Shadowing and NetBase Client. These services are briefly described below but are not referenced in this guide. For reference information, see the NetBase SQL Shadowing Handbook and the NetBase Client Reference Guide. NetBase SQL Shadowing In addition to the NetBase Shadowing service designed for IMAGE databases and KSAM files, NetBase provides shadowing of ALLBASE DBEs.
Welcome to NetBase NetBase Client NetBase Client allows MS-DOS, Windows, and UNIX based applications to access MPE files and IMAGE databases on HP 3000 MPE/iX systems. To offer this access, NetBase Client uses libraries of APIs that have the same calling sequences as the MPE/iX intrinsics. Code that is written and compiled on an HP 3000 may, with minor modifications, be compiled and run on a PC or a UNIX system.
C H A P T E R 1 The NetBase Components Four NetBase components exist that support the NetBase services. These components are: the NetBase background job to facilitate communication between systems; the NetBase shell to intercept file and database activity; the NetBase directory to define the files for NetBase services; and the NetBase control program to monitor and configure NetBase.
Chapter 1 NetBase Background Job The NetBase background job is used to establish communication between all nodes configured within NetBase. The main purpose of the job is for transportation of data and communication between nodes. The NetBase job must be up and running at all times on the system after NetBase is installed. Local System NetBase Job NBCOM NBEXPORT Remote System NetBase Job NBCOM NBIMPORT NBPOST Start the NetBase job as part of the normal system startup procedures. The NETBASE.JOB.
The NetBase Components The NBLOG.DATA logfile contains all of the messages from the previous run of the NetBase job. To view the messages from the logfile, use the NBLOG.PUB.NETBASE utility program. To view logfile messages: 1. View logfile messages by typing: :RUN NBLOG.PUB.NETBASE 2. Enter the start date: Enter Start Date for all: 12/13/96 12/20/96 12/20/96 12/20/96 12/20/96 12/20/96 12/20/96 12/20/96 15:14:22.9 15:14:23.0 15:14:25.5 15:14:26.6 15:14:26.6 15:14:26.6 15:14:28.
Chapter 1 NetBase Shell The NetBase shell is a set of procedures that install into the system libraries. These procedures intercept TurboIMAGE and file system intrinsic calls. In fact, the NetBase shell procedures have the same name as the MPE/iX procedures. This allows NetBase to trap the activity to files or databases without having to make any changes to application programs. The NetBase shell traps programmatic activity to files or databases.
The NetBase Components When the NetBase shell is installed in the system libraries, new error codes may occur. These new error codes are greater than 1000, and constitute some type of NetBase error. For example, if you were running an application program that passes a DBOPEN on a database that is to be accessed remotely via NFA but the local NetBase background job was not running, the DBOPEN would fail with 1001 - LOCAL NETBASE SERVICES ARE DOWN.
Chapter 1 Other Intrinsics ACTIVATE GENMESSAGE PRINTFILEINFO COMMAND HPCICOMMAND SUSPEND CREATE IODONTWAIT VPRINTFORM CREATEPROCESS IOWAIT For more information about which system libraries the NetBase shell is installed into and how to install it, see the Installation Section in this manual.
The NetBase Components NetBase Directory The NetBase directory is used to define the NetBase environment. Entries in the directory tell NetBase which files are on remote systems and which files are to be shadowed. The directory itself is a hash file similar to an IMAGE master set. In fact, NetBase makes use of the IMAGE hashing algorithm. This type of file is used because of its fast keyed access.
Chapter 1 NetBase Control Program The NetBase control program, NBCTRL.PUB.NETBASE, is used to stop and start NetBase services and to also monitor NetBase activity on a system. NBCTRL is used to stop and start the NetBase background job. It is also used to stop and start individual NetBase services such as remote file access, the exporting of transactions for shadowing and remote spooling. Only one person on the system can run NBCTRL at any given time.
C H A P T E R 2 Using NBCTRL NBCTRL is an interactive program for controlling and monitoring NetBase operations. The NBCTRL program is used for configuring and starting or stopping NetBase. It displays current NetBase users and their status. The NBCTRL program is the operator’s interface for controlling the NetBase process.
Chapter 2 NBCTRL Command Summary The following table lists the NBCTRL commands. 2-2 Command Function ∗> ABORT Immediately terminates some or all NetBase features. ∗> CHGDIR Changes the current default NetBase directory. ∗> CONFIG Invokes the NetBase configuration subsystem. ∗> DEFER Defers posting of selected filesets. ∗> DIR Invokes the NetBase directory subsystem. ∗> DISABLE Turns off one of the NetBase features. ∗> ENABLE Turns on one of the NetBase features.
Using NBCTRL Running NBCTRL NBCTRL is run from MPE using the following command: :RUN NBCTRL.PUB.NETBASE Since NBCTRL communicates directly with NetBase’s controlling process, only one person may execute it at a time. Any additional users attempting to run it will receive the message NBCTRL is currently running elsewhere and the program will terminate. When NBCTRL has been successfully started, it displays the following prompt: NetBase Control Program ∗> [x.
Chapter 2 Special Command Features NBCTRL supports a help facility. When you type HELP, a list of valid commands display. NBCTRL also has some special features that provide MPE functionality within NetBase. Any MPE command that is executable in break may be issued from NBCTRL. To enter an MPE command, type the command prefixed by a colon (:). The REDO command allows the last command entered to be modified and then executed.
Using NBCTRL Accessing NetBase Subsystems The configuration, directory, and security subsystems can be accessed through NBCTRL. Each of these subsystems has its own prompt. This helps the user determine what subsystem is running.
Chapter 2 Using the NBDISABLE JCW Many of the NetBase features that are enabled through NBCTRL can be disabled for a particular job or session. This is done with a job control word called NBDISABLE. The NetBase shell checks NBDISABLE the first time a user calls FOPEN or DBOPEN for a file or database. If any of the flags are set that disable a service, NetBase disables those services for that user only. NBDISABLE cannot be used to enable a service.
Using NBCTRL NBCTRL Commands The following sections describe the NBCTRL commands in detail. ABORT This command immediately terminates NetBase services to a user or node. It also aborts a server, or aborts the NetBase control process. This command requires NODE MANAGER (NM) capability. Stop! Aborting NetBase may cause synchronization problems with shadowing. Do not abort NetBase while the shadow transport is active.
Chapter 2 Parameters 2-8 Parameter Description CLIENT Aborts the processes which allow NetBase Client to access data on an HP 3000. You can either enter a client number, or @ to abort all clients. Active as well as inactive clients are aborted. EXPORT Aborts the process responsible for exporting shadow records. IMPORT node-id Aborts the process responsible for importing shadow records from the node specified. NETBASE Terminates all NetBase services and stops the background job.
Using NBCTRL Examples To abort a remote user, first obtain the server number: ∗> SHOW REMOTE NODE JOBNUM SRVR PIN JOB NAME PROGRAM NAME ACCT DIST ACCT #J102 #S507 #S202 1 3 4 47 122 132 GLPOST,JOB.ACCT JILL.DIST JACK.PURCHASE GLPOST.PUB.PROD SOENTER.PUB.PROD POENTER.PUB.PROD NODE JOBNUM SRVR PIN JOB NAME PROGRAM NAME ACCT ACCT #J102 #S202 47 132 GLPOST,JOB.ACCT JACK.PURCHASE GLPOST.PUB.PROD POENTER.PUB.
Chapter 2 Issue the following command to shutdown the entire NetBase job, ignoring active services: ∗> ABORT NETBASE Stop! Aborting NetBase may cause synchronization problems with shadowing if aborted while the shadow transport is active. Note that the ABORT command immediately terminates services to the process specified. This command will cause programs currently executing to terminate with a NetBase error upon their next NetBase file request.
Using NBCTRL CHGDIR This command changes the active NetBase directory. The new directory will effect new processes only. Existing processes will continue to use the directory that was active when the process was started. This command requires NODE MANAGER(NM) or SYSTEM SUPERVISOR(OP) capability. Syntax ∗> CHGDIR filename Parameters Parameter Description filename The fully-qualified name of a valid NetBase directory. Examples To change the active NetBase directory to NBDIR.TEST.
Chapter 2 CONFIG This command invokes the NetBase configuration subsystem. The user must be logged into the NETBASE account to access this subsystem. This command requires ACCOUNT MANAGER(AM) or SYSTEM MANAGER(SM) capability. Changes made to the configuration parameters while NetBase is running may not take effect immediately. Turn to Chapter 3 “CONFIG” for a description of parameters and when changes to each parameter takes effect. Syntax ∗> CONFIG Parameters This command does not have parameters.
Using NBCTRL DEFER This command defers the posting of shadowed transactions from the specified node for the listed file sets, queuing those updates instead. This allows a specific shadow file or set of shadowed files to be taken off-line, without interrupting the posting for any remaining shadowed files. Reference the UNDEFER command for information on re-initiating the posting of the pending transactions. This command requires SYSTEM MANAGER(SM) or SYSTEM SUPERVISOR(OP) capability.
Chapter 2 DIR This command gives the user access to the NetBase directory subsystem. Turn to Chapter 4 “NBDIR” chapter for more information on the directory subsystem. This command requires NODE MANAGER(NM) or SYSTEM MANAGER(SM) capability. Syntax ∗> DIR Parameters This command does not have parameters. Examples :RUN NBCTRL NetBase Control Program [x.x] Update n (C) QUEST Software 1987 ∗> DIR D> BUILD NBTEST.DATA,500 D> EXIT Note.
Using NBCTRL DISABLE The DISABLE command is used to turn off one or more of the NetBase functions. The function remains disabled until it is re-enabled using the ENABLE command. This command should be issued before NetBase is started. If issued while NetBase is running, it will only take effect on some of NetBase processes. This command requires SYSTEM MANAGER(SM) capability. Warning! While the DISABLE command may be used to completely disable the shadowing module of NetBase, it is not recommended.
Chapter 2 Parameters The parameters can be abbreviated to the first three characters. Parameter Description AUTORPM Disables automatic remote process management. BUFFERING Disables the buffering feature of NFA. CRITICAL Makes it possible for a shadowed file or database transaction to be interrupted, enabling the file update to happen while the shadow write may not.
Using NBCTRL ENABLE Turns on various NetBase features that operate on and from the local node. This command is used to enable various NetBase services that have been disabled with the DISABLE command. It should be issued before NetBase is started. If issued while NetBase is running, it will only take effect on some NetBase processes. This command requires SYSTEM MANAGER(SM) capability. Note.
Chapter 2 Parameters Description PENDLOCK Couples an unconditional database lock with the next call to that database into a single network transaction. A DBLOCK followed by a DBUNLOCK of the same database without any other activity will not be sent to the remote machine. Do not use if DBLOCKS are being used to synchronize external data structures, or if any remote system is an MPE/V system. Otherwise, this option further reduces networking overhead. Note that these changes are dynamic.
Using NBCTRL ROLL FORWARD This command causes the posting process to roll forward transactions from the posting queue files into their shadow files. This command requires SYSTEM MANAGER(SM) capability. If the posting process encounters an error while opening a shadowed file, the transactions are preserved in a post queue file. POST reports the exceptional condition encountered during the file open to the system console, as well as the NetBase job $STDLIST.
Chapter 2 SECURITY This command gives the user access to the NetBase security subsystem. Turn to the “NFA Security” section in Chapter 6 for more information on the security subsystem. This command requires SYSTEM MANAGER(SM) and NODE MANAGER(NM) capability. Note. Since NBCTRL communicates directly with the NetBase controlling process, only one person may execute it at a time. This should be considered when invoking the security subsystem through NBCTRL.
Using NBCTRL SERVER The SERVER command is used to allow or abort access to files. This command requires NODE MANAGER (NM) or SYSTEM SUPERVISOR (OP) capability. ∗> HELP SERVER Controls Server Processes Syntax ∗> SERVER {ABORT=fileset[,fileset[,...]]} {ALLOW=fileset[,fileset[,...]]} Parameters Parameter Description ABORT Eliminates access to specified file set(s) for all remote users on the system.
Chapter 2 SET This command dynamically changes the limit or the priority queue for NetBase processes. The SET command allows current NetBase limits to be changed while NetBase is running. The number of local users, remote users and the number of servers available can be changed up to their maximum allowable values. This command will also re-schedule the priority of the shadowing export and posting processes. This command requires NODE MANAGER(NM) or SYSTEM SUPERVISOR(OP) capability.
Using NBCTRL Examples If during a heavy period of user updating, it was discovered that the shadowing posting process for node 2 was using too much of the processor, you can issue the following command to lower the posting priority: ∗> SET POST 2=DS The SHOW STATUS command can be used to display current limits. The current limits are listed under LOCAL in the display.
Chapter 2 The STATUS command can be used to verify the new limits: ∗> STATUS STATUS FOR NODE 1: SYSA NODE STATUS 2 SYSB 3 SYSC LOCAL: REMOTE USERS: LOCAL USERS: SERVERS: CLIENTS: ROLL FORWARD: UP UP ------- NFA ------ACCESS LOCAL REMOTE -- SPOOLING -EXPORT IMPORT ---- SHADOWING --EXPORT IMPORT POST IN/OUT IN/OUT ACTIVE DOWN DOWN 0 0 70 0 0 SERVICES: NFA CACHING: ACTIVE STATISTICS: INACTIVE SQL SHADOW: ACTIVE 2-24 LIMIT = LIMIT = ALLOC = 0 0 0 0 100 80 0 ACTIVE INACT STOP ACTIVE STOP
Using NBCTRL SHOW The SHOW command is used to display the status of all the NetBase processes. The STATUS command is an abbreviation for the SHOW command with the STATUS option. The listing for any SHOW command can be terminated by entering .
Chapter 2 Parameter Description CLIENT [n] Displays the status of incoming client systems. The information for a client system includes a list of the files that the system is accessing and the access mode for each file. If the client number is not specified, a list of all client systems is displayed. EXPORT Displays the number of shadow transactions sent to each node, as well as the number queued for export.
Using NBCTRL The shadowing processes may be in one of seven states. Following is a list of the valid states with an explanation of their meaning: State Description ACTIVE This indicates that the shadow process is configured and is running and that its co-process is also up and running on the other system. DOWN This indicates that the shadow process is configured but that the process has not been started or has been stopped.
Chapter 2 LOCAL: REMOTE USERS: LOCAL USERS: SERVERS: CLIENTS: ROLL FORWARD: 0 0 0 0 0 LIMIT LIMIT ALLOC ALLOC = = = = 64 500 0 0 SERVICES: STATISTICS: INACTIVE CLIENT ACC: ACTIVE In the above example, the status of all processes importing from or exporting to other nodes is displayed. The local user counts describe the number of local user processes that are using NFA to access remote systems or are being tracked locally by NetBase statistics.
Using NBCTRL The ROLL FORWARD statistic is the number of roll forward processes that are executing. A roll forward process is started by the ROLL FORWARD command. It is used to roll transactions forward from a post queue into the actual file for which that post had been queuing. SHOW POST Command The SHOW POST command displays a list of all shadow files that the posting process has open, including the status of the posting to each file.
Chapter 2 SHOW POST Example To display the status of all files being updated by the posting process for node 8: ∗> SHOW POST 8 File Type Updates Time Stamp of Last Record Processed GL.DATA.ACCT GLCUSTL.DATA.ACCT FINDB.DATA.ACCT IMAGE MPE ??? 3721962 95 0 04/19/91 13:47:32 04/19/91 11:53:17 04/19/91 13:45:38 S Q D Y U I N E S - - S - D - Q - In the example above, the file GL.DATA.ACCT is an IMAGE database. It has had 3,721,962 updates since the posting process was last started.
Using NBCTRL For information about remote users, enter the SHOW REMOTE command: ∗> SHOW REMOTE NODE JOBNUM SRVR SPIN JOB NAME PROGRAM NAME DAFFY FOX DAFFY #J102 #S507 #S202 GLPOST,JOB.ACCT JILL.DIST JACK.PURCHASE GLPOST.PUB.PROD SOENTER.PUB.PROD POENTER.PUB.PROD 1 3 4 105 79 121 Note. The SPIN that is displayed here is the PIN of the server process allocated to the remote process.
Chapter 2 To display the number of shadow transactions sent to each node, as well as the number queued for export, enter the SHOW EXPORT command: ∗> SHOW EXPORT No Backlog at this time. Priority is CS, shifted 1 times.
Using NBCTRL In the previous example, the posting process for node 2 is actively posting to eighteen shadowed files. The asterisk indicates that the backlog is greater than the amount shown by one or more import queue files. This usually is a result of the posting process for this node having been shutdown for some period of time, such as for a system backup. The posting process for node 8 is also running, but there is no activity from the master node.
Chapter 2 To display the status of NetBase processes in descriptive MPE/iX variables, use the SHOW VARSTATUS command. In this way, batch job streams can be built to automate a number of operational tasks related to monitoring the state of the NetBase processes.
Using NBCTRL You can also use SHOW VARSTATUS to check to see if a NetBase job is running. See the following description of SHOW VARSTATUS: :showvar NBCTRL - 0 - indicates NBCTRL ran successfully 1 - indicates NBCTRL crashed 2 - indicates Netbase is down.
Chapter 2 START The START command is used to start up NetBase services. These services can be started to specific nodes or to all nodes currently up on the network. START also has the ability to initiate the background job that runs NetBase controlling programs. Typically NetBase is configured so that all of the services are available when NetBase is started.
Using NBCTRL Parameters Parameter Description CLIENT Starts the processes necessary for NetBase Client to access data on an HP 3000. EXPORT [node] Starts the exporting of shadowed transactions. When EXPORT is initially started, exporting to all nodes is enabled regardless of whether a node is specified. If exporting to an individual node had been stopped, it can be restarted by specifying the remote node with the START command. ILOG [file] Starts IMAGE log file shadowing for the file specified.
Chapter 2 Parameter Description SPOOL IN [node] Starts the process that receives spooling output from the node specified. If the node is not specified, the reception of spooling output from all nodes is enabled. SPOOL OUT [node] Starts the process that transmits spooling output to the node specified. If the node is not specified, the transmission of spooling output to all nodes is enabled. SPOOL UNIX Starts the process that receives spooling output from UNIX nodes.
Using NBCTRL STATS The STATS command enables and disables NetBase statistical logging for the local system. The current log file can also be displayed and changed using this command. Statistics can be enabled for either remote or local files and data bases. This command requires SYSTEM MANAGER(SM) or NODE MANAGER(NM) capability. If NetBase is unable to gain exclusive access to the current statistics log file, statistics will be suspended.
Chapter 2 Parameters 2-40 Parameter Description START Enables statistical tracking of user processes. If entered without an option, this command starts the process that gathers statistics. The STATS SHOW command displays the activities that are being tracked. If entered with one or more options, this command starts statistical tracking of the activity or activities specified. STOP Disables statistical tracking of user processes.
Using NBCTRL Examples To show the status of the current log file: ∗> STATS SHOW LOGGING STATUS: CURRENT FILE: RECORDS LOGGED: PERCENT FULL: ACTIVE NBLG0004 1534 47% LOGGING OPTIONS: IMAGE FILES PROCESS OFF OFF LOCAL The only option currently active is the tracking of terminal response time.
Chapter 2 To instruct NetBase to close the current log file and open the next: ∗> STATS SWITCH Since NetBase requires exclusive access to statistic log files, this command is used when the current log file needs to be freed up to produce statistics reports. Note that STATS STOP will not close the current log file since processes currently collecting statistics will be posting statistics as the data becomes available.
Using NBCTRL STOP The STOP command turns off a particular service or all services to new users requesting that service, and can stop services to a specific node or all nodes. Users that have been granted access to a service before it is stopped are allowed to complete. This command requires NODE MANAGER(NM) or SYSTEM SUPERVISOR(OP) capability.
Chapter 2 Parameter Description ALL Stops all processes but does not terminate the NetBase background job. CLIENT Stops the processes necessary for NetBase Client to access data on an HP 3000. SPOOLING Stops all spooling into and out of the local node. SPOOL IN [node] Stops the process that receives spooling output from the node specified. If the node is not specified, the reception of spooling output from all nodes is disabled.
Using NBCTRL Examples To stop services to and from a node, first obtain the node number by executing the SHOW STATUS command.
Chapter 2 TRACE The TRACE command displays the server activity as it occurs. TRACE displays on the terminal all IMAGE and File System intrinsic calls that a server is executing.
Using NBCTRL Examples To display the activity of server 1: :RUN NBCTRL NetBase Control Program [x.x] Update n (C) QUEST Software 1987 ∗> SHOW REMOTE NODE JOBNUM SRVR SPIN VIXEN #S216 1 BANMAIN.PUB.NETBASE 78 JOB NAME PROGRAM NAME TEST,OPERATOR.SYS ∗> TRACE SERVER 1 TRACING HAS BEEN ENABLED 09:19:32.3 09:19:32.5 09:19:32.5 09:19:32.6 09:19:32.6 09:19:33.8 09:19:37.0 09:19:37.0 09:19:45.0 09:19:46.4 09:19:46.5 09:19:46.5 09:19:46.6 09:19:53.5 09:19:53.5 09:20:03.4 09:20:05.9 09:20:06.0 09:20:06.
Chapter 2 UNDEFER This command posts all deferred updates to shadowed files. UNDEFER starts the posting of shadowed transactions from the specified node into shadowed files previously deferred with the DEFER command. Once all deferred transactions have been applied, new transactions will post directly for those files. This command requires SYSTEM SUPERVISOR(OP) or SYSTEM MANAGER(SM) capability.
C H A P T E R 3 Using CONFIG Since all network environments are not the same, NetBase allows for the entry and modification of NetBase operating parameters. NBCTRL has a subsystem dedicated to installing and maintaining the configuration and operating environment of NetBase. In this chapter, the CONFIG subsystem commands and their use with configuration parameters are described. The configuration parameters are stored in files in the NETBASE account.
Chapter 3 CONFIG Command Summary The following table lists the CONFIG commands. 3-2 Command Function C> ADD Adds a node to the configuration. C> DELETE Deletes a node from the configuration. C> EXIT Exits from the configuration subsystem, and returns to NBCTRL. C> HELP Displays a list of the CONFIG subsystem commands and the syntax for each command. C> LIST Lists the configuration information. C> MODIFY Changes the configuration parameters.
Using CONFIG Configuring NetBase Configuring NetBase consists of two parts, configuring the operational parameters and defining the network nodes for NetBase. The configuration subsystem can only be entered through NBCTRL. Configuration changes may require the creation of files that must reside in the NETBASE account. Access to CONFIG is denied if the user is not logged into the NETBASE account or does not have SM capability. Use the following steps to configure NetBase.
Chapter 3 To define the network nodes: 1. To define the nodes in your network for NetBase, use the ADD command, specifying the number of the node you wish to define. Remember to define the current node. You are prompted for details concerning each node. C> ADD n 2. Tell NetBase which node is the local node: C> MODIFY GLOBAL 3. Exit CONFIG: C> EXIT ∗> EXIT 4. Repeat steps 1 to 3 on each node. Note. As an alternative, you can run NBCTRL with an INFO parameter.
Using CONFIG Special Command Features The subsystem command processor has some special features that provide MPE functionality within NetBase. Any MPE command that is executable in break may be issued from the subsystem. To enter an MPE command, type the command prefixed by a colon (:). This subsystem requires NODE MANAGER(NM) and SYSTEM MANAGER(SM) capabilities. The user must be logged into the NETBASE account. The REDO command allows the last command entered to be modified and then executed.
Chapter 3 NetBase Parameter Definitions The following section describes the parameters used by NetBase to function, as well as various tuning options. To guarantee a successful implementation of NetBase, it is recommended that you study this section and become familiar with these parameters. There are two sets of parameters. The largest set of parameters defines the operational environment for NetBase on the local node.
Using CONFIG Operational Parameters The following parameters define general information regarding the operation of NetBase: GLOBAL - Local Node Number An arbitrary number between 1 and 255 designating the number of this node. Each node in the NetBase network must be assigned a different node number. This value is used to determine which files are local and which are remote. This parameter takes effect when NetBase is started.
Chapter 3 GLOBAL - Maximum Local Users The maximum number of concurrent local user processes that may access NetBase at any one time. Each user process accessing at least one remote file or for who statistics are being collected is considered a local user. The maximum is 2048 user processes. Local users do not include processes that are using the SHADOWING subsystem only. This parameter takes effect when NetBase is started.
Using CONFIG NFA - Server Allocation Time-out This is the number of seconds that NetBase will wait for a remote server to be allocated to a user process. The default is 60 seconds. If the system is heavily loaded, and server allocation time-outs are being experienced, this limit should be increased. This number must be between 20 and 600 seconds. This parameter takes effect when new server processes are started.
Chapter 3 NFA - Client Lock Held Time-out This parameter sets the maximum time a server will wait for any activity before it terminates the connection. Unlike the Client Inactivity Time-out, this parameter takes effect only when the client holds a lock. When all locks are released, the Client Inactivity Time-out parameter takes effect. If this parameter is set to 0, and the Client Inactivity Time-out parameter is non-zero, then the later parameter will be used.
Using CONFIG SPOOL - Remote Transfer Time-out This parameter specifies the number of seconds that the NetBase Spooling transfer program will wait to establish communication with its remote spooling process. The minimum value is 10 with a maximum of 3276. This parameter takes effect when the START SPOOLING command is issued in NBCTRL. Default = 120 SPOOL - Transfer Server Allocation This parameter determines the number of spool file transfer servers to pre-allocate.
Chapter 3 SPOOL - Use S' and J' on incoming This parameter tells NetBase to set the job/session id numbers on incoming spool files to J'nnn or S'nnn. This convention reduces ambiguity between local and remote spool files. This parameter takes effect when the START SPOOLING command is issued in NBCTRL. Default = Y SPOOL - Change user on incoming Setting this parameter to Y preserves the user information from the originating computer.
Using CONFIG SPOOL - Spooling Import Priority This parameter sets the execution priority of all Spooling Import processes. The default is linear queue 152. Any numeric value or BS, CS, DS, or ES is valid. This parameter takes effect when a Spooling Import process starts. Default = 152 Minimum = 50 Maximum = 255 SPOOL - Enable HP-UX Receiving If this parameter is set to Y , NetBase Spooling from HP-UX will be available. This parameter does not effect spooling to HP-UX.
Chapter 3 STATS - Max File Allocation This parameter sets the maximum number of files accessed by a local process that can be monitored for statistics. This includes local and remote files and databases. Valid values are 1 to 145. This command takes effect when the STATS START command is issued in NBCTRL. Default = 64 Maximum = 145 STATS - Init File Allocation This parameter is used to compute the initial size of the statistics data segment.
Using CONFIG STATS - Read-Read Filter (ms) This parameter is the threshold above which read-read transaction time statistics are captured. If a read-read response time is less than this value, that particular transaction is ignored for statistics gathering. The measurement is in milliseconds. A value of 0 disables the filtering. The maximum is 2,147,483,647. This command takes effect when the STATS START command is issued in NBCTRL.
Chapter 3 DIR - Default Directory Filename The name of the file that will be used as the NetBase directory for all processes on this node. This parameter takes effect as new user processes are started or the START POST command is issued in NBCTRL. Default = NBD.DATA.NETBASE DIR - Allow File Equates If set to Y , the NetBase directory may be redirected from the default directory with a file equation. Recommended value is N. This parameter takes effect as new user processes are started.
Using CONFIG SHADOW - Close Log file on suspend This parameter should be set to Y if a very large (greater than 384) number of processes are updating shadowed files. This flag will cause the shadow transaction queue file to be closed if a process suspends, thus allowing more user processes to access the input queue file. This parameter takes effect as new user processes are started.
Chapter 3 SHADOW - Check KSAM record counts This parameter enables a further sync check on KSAM files to ensure that no records are missing when writing new records to a KSAM file. This parameter should only be set to N if a master system has a version of NetBase earlier than 9.5. Existing users have this option off by default. It cannot be enabled until all master systems have been installed with the 9.5 NetBase shell. This parameter takes effect when the START POST command is issued in NBCTRL.
Using CONFIG SHADOW - Export User Exits When this parameter is set to Y , the user-defined Export User Exit procedure will be called for each shadow record processed. This procedure can be used to filter exported records and to change the destination of each record. This parameter takes effect when EXPORT is started. Default = N SHADOW - Export Bridge Exits When this parameter is set to Y , the Export Bridge Exit procedure will be called for each shadow record processed.
Chapter 3 SHADOW - Export Buffer Max BF This parameter defines the maximum number of blocks that the export process can send to a node at one time. The optimal setting for the NS LAN Link is 5 blocks. This parameter takes effect when the START EXPORT command is issued in NBCTRL. Default = 5 Minimum = 1 Maximum = 16 SHADOW - Export Buffer Time-out This parameter is the number of seconds that the export process will wait before sending the buffered shadow transaction to the shadow node.
Using CONFIG SHADOW - Export Upshift Priority This parameter is the MPE process priority that the export process will shift into should exporting fall behind. The export process determines it has fallen behind when the number of records in the export queue exceeds the upshift trigger. This parameter takes effect when the START EXPORT command is issued in NBCTRL.
Chapter 3 SHADOW - Enable Export Logging This flag enables the transaction logging feature of shadowing. When enabled, all shadow transactions will be logged to a series of files in the LOG group. These files can be used for roll forward recovery on any subset of the shadowed files. This parameter takes effect when the START EXPORT command is issued in NBCTRL. Default = N SHADOW - Export Log File Size Determines the size of the shadow log files, in blocks.
Using CONFIG SHADOW - Export Inactivity Time-out This parameter is the number of seconds that the export process will wait before flushing the queued shadow updates to disk and updating the queue files EOF. This parameter takes effect when the START EXPORT command is issued in NBCTRL. Default = 5 Maximum = 120 SHADOW - Import Inactivity Time-out This parameter is the number of seconds that the import process will wait before flushing any queued shadowed updates to disk and updating the queue files EOF.
Chapter 3 SHADOW - Post on startup If this parameter is set to Y , the posting process will be started when NetBase is started. This parameter takes effect when NetBase is started. Default = Y SHADOW - Use IMAGE Log Files This flag activates the IMAGE log file transporter. This creates additional processes used solely for the shadowing of IMAGE log files. Do not set this to Y unless at least one IMAGE log file is enabled for shadowing. This parameter takes effect when NetBase is started.
Using CONFIG PASSWORD - Group Password This parameter is used by the START NETBASE command in NBCTRL to substitute the group password in the JOB file before it streams the NETBASE job. A password can be removed by typing NONE. Default = NONE PASSWORD - Account Password This parameter is used by the START NETBASE command in NBCTRL to substitute the account password in the JOB file before it streams the NETBASE job. A password can be removed by typing NONE.
Chapter 3 Node Level Parameters The following parameters define specific information regarding each node in the network: System Name This is a node level parameter that is used to describe the node in NetBase displays, reports and commands. The name can be up to eight characters long. For operational simplicity, it is recommended that this be the same as the NS node name.
Using CONFIG Node Name This is the NS node name of the specified node. It should be fully qualified if its domain and organization differ from the local node. Default = none Required Parameter Node Connection Time-out When a communication line is down, NetBase will check periodically to see if the line has come up. Once the link between two nodes has been established, NetBase will further check the link if the link has not been used for a set period.
Chapter 3 SPOOL - Enable Export Flow Control Normally, the Spooling Export process sends data as quickly as the network can receive the data. If a network link is not a LAN link, or if the destination node is a slower computer, this option may be necessary to prevent the link from experiencing load related failures. This parameter takes effect when Spooling Exporting is started. Default = N SHADOW - Direction (N/E/I/B) This parameter describes the direction that files are shadowed relative to this node.
Using CONFIG SHADOW - Post queue size This parameter is used to set the limit of the posting queue files built by NetBase in 16K blocks. Default = 3172 SHADOW - Initial Post Priority This is the MPE process priority under which the posting process will initially run. Valid options are BS, CS, DS or ES. Default = CS SHADOW - Post Inactivity Timeout This parameter specifies how long a file will remain open by the post process after the last update is processed.
Chapter 3 SHADOW - Save Process Info on Post This flag is used in conjunction with Post User Exits to pass process info from the originating process to the user exit procedure. The originating node must also have turned on the Export Process Info parameter. Do not enable this feature unless Post User Exits are being used. This parameter takes effect when a post process is started.
Using CONFIG SHADOW - Transfer Single Queues This parameter causes shadow EXPORT to transfer queued shadow data a queue file at a time. This is useful for transferring queued shadow information across network links that are likely to experience failures. This parameter takes effect when Exporting is started. Default = N SHADOW - Transfer ACK Frequency This parameter enables acknowledgments during a shadow transfer.
Chapter 3 CONFIG Commands The following sections describe the CONFIG commands. ADD The ADD command adds a node to NetBase's configuration file. All node specific parameters such as the node name and NetBase shadowing options are specified here. NetBase should be stopped before adding a node. This command may be abbreviated to A . Syntax C> ADD node# Parameters 3-32 Parameter Description node# The number of the node to be added to the configuration file.
Using CONFIG Example To add node 1 to NetBase's configuration: C> A 1 System Name........................ Startup Access (S/I/O/A/W)......... Node Name.......................... Node Connection Timeout............ SPOOL - Direction (N/E/I/B)........ SPOOL - Allow incoming job streams. SPOOL - Enable Export Flow Control. SHADOW - Direction (N/E/I/B)....... SHADOW - Export queue size......... SHADOW - Import queue size......... SHADOW - Post queue size........... SHADOW - Initial Post Priority.....
Chapter 3 DELETE The DELETE command removes a node from the NetBase configuration file. When a node is deleted from the configuration, files located on that node are no longer accessible by local users of NetBase. NetBase should be stopped before deleting a node. This command may be abbreviated to D. Note. Deleting a node from the configuration does not remove the references to this node from the directory. Those references become invalid until changed, or until the node is added back.
Using CONFIG LIST The LIST command displays the configuration parameters for NetBase. It also lists the parameters for a specific node or for all nodes. Subsets of the global parameters may be listed separately by issuing the LIST command with the desired subset as a parameter. This command may be abbreviated to L.
Chapter 3 Example To display the operational parameters: C> L CONFIG GLOBAL - Local Node Number......... 1 GLOBAL - Error Enhancements........ IR GLOBAL - Maximum Local Users....... 383 NFA - Maximum Remote Users......... 64 NFA - Release Server on Last Close. N NFA - Initial Server Allocation.... 0 NFA - Server Allocation Timeout.... 300 NFA - Server Initial Priority...... CS NFA - Server LIB= load flag........ P NFA - Lock Priority Boosting....... Y NFA - Incoming users on startup....
Using CONFIG SHADOW - Enable Quiet Period Flush. SHADOW - Export User Exits......... SHADOW - Export Bridge Exits....... SHADOW - Export Process Info....... SHADOW - Process Info to Exp Exit.. SHADOW - Export Buffer Size (b).... SHADOW - Export Buffer Max BF...... SHADOW - Export Buffer Timeout..... SHADOW - Export Ack Timeout........ SHADOW - Export Initial Priority... SHADOW - Export Upshift Priority... SHADOW - Export Upshift Trigger.... SHADOW - Export Downshift Trigger.. SHADOW - Shift Check Interval..
Chapter 3 To display a list of all nodes configured: C> L NODES Node 1 2* Sys name SYS-A SYS-B Line Type N N Startup A A Spool B N Shadow I N Note that an asterisk (*) appears next to the local node number on this display. To display the configuration for a specific node: C> L 1 Node Number........................ System Name........................ Startup Access (S/I/O/A/W)......... Node Name.......................... Node Connection Timeout............ SPOOL - Direction (N/E/I/B)........
Using CONFIG MODIFY The MODIFY command allows you to modify the configuration parameters and the node specific parameters. You can use this command to modify all the configuration parameters, or just the parameters for a specific subsystem. It can also be used to modify the configuration for a specific node. This command may be abbreviated to M .
Chapter 3 The MODIFY command recognizes the input of special characters used as commands when modifying. These commands and their meaning are: Character Description // Terminates command and abort changes /. Back up to previous field / Terminates command and save changes ? Displays help information on current field Modifying Passwords You can also change the default user, group, account passwords in CONFIG.
Using CONFIG To modify node specific parameters: C> M 1 System Name........................ Startup Access (S/I/O/A/W)......... Node Name.......................... Node Connection Timeout............ SPOOL - Direction (N/E/I/B)........ SPOOL - Allow incoming job streams. SPOOL - Enable Export Flow Control. SHADOW - Direction (N/E/I/B)....... SHADOW - Export queue size......... SHADOW - Import queue size......... SHADOW - Post queue size........... SHADOW - Initial Post Priority.....
Chapter 3 PRINT The PRINT command redirects the output of the LIST command to the output file NBOUTPUT. This is directed to device class LP by default. This command may be abbreviated to P. Syntax C> PRINT {ALL {CONFIG {DIR {GLOBAL {NFA {NODES {QUICK {SHADOW {SPOOL {SQL {STATS {node# } } } } } } } } } } } } Parameters 3-42 Parameter Description ALL Prints the parameters for NetBase and all configured nodes. CONFIG Prints all NetBase parameters. DIR Prints NetBase directory parameters.
Using CONFIG Example For example, to print the global parameters: C> P CONFIG Sending configuration listing to NBOUTPUT C> 3-43
C H A P T E R 4 Using NBDIR NBDIR is an interactive program that creates and maintains NetBase directories. NetBase directories are used by NetBase to determine the location of files in the network. The directories include information about file location, file access, device redirection, program access and file shadowing.
Chapter 4 NBDIR Command Summary The following table lists the NBDIR commands. Command Function D> ACCOUNT Changes the default account to apply to subsequent directory entries. D> BUILD Builds and initializes NetBase directories. D> DEVICE Enters device definitions into NetBase's directory for remote spooling. D> DIR Changes the directory file to be edited. D> DISPLAY Changes node name formats for LIST and UNLOAD commands, either # or name.
Using NBDIR Command Function D> REBUILD Rebuilds the directory KSAM display file. D> RESET Removes an entry from the NetBase directory. D> SHADOW Enters shadow records into the directory. D> SQLIN Enters SQL shadow import records into the directory. D> SQLOUT Enters SQL shadow export records into the directory. D> TABLE Enters the tables which are to be included in or excluded from SQL shadowing.
Chapter 4 NBDIR Command Summary It is a good idea to run NBDIR directly rather than through NBCTRL since only one person can run NBCTRL at a time. This leaves NBCTRL free to be run by other users. Any user may run NBDIR. However, some of the commands require special capabilities. See the list of capabilities in the following “Special Command Features” section. Any NBDIR command may be passed via the INFO parameter of MPE's :RUN command.
Using NBDIR Wildcards within NBDIR NBDIR supports full use of wildcards in its LIST commands. However, it supports wildcards in only a limited manner for FILE, SHADOW and PROGRAM entries. For directory entries, you may use an unqualified @ for either the file portion or for both the file and group specifications. FILE @.group.account, HP995 FILE @.@.account, FOX NBDIR does not support partial wildcarding for directory entries. FILE M@.pub.prod is invalid.
Chapter 4 Editing a NetBase Directory You can edit a directory two ways you can edit online, or you can edit an ASCII file. To edit the directory online: 1. Run NBDIR by entering: :HELLO MGR.NETBASE :NBDIR.PUB.NETBASE 2. List the entry you want to modify. D> LISTF MYDATAB.@.@ Node: FOX Directory: NBD.DATA.NETBASE -----LOCAL REFERENCE-----File Group Account MYDATAB 3.
Using NBDIR To edit the directory using an ASCII file: 1. Create an ASCII file for editing. As an example, D> UNLOAD TEMPDIR.PUB.NETBASE D> UNLOAD filename 2. Edit the ASCII file. :QUAD.LIB.NETBASE /T TEMPDIR /L ALL DIR NBD.DATA.NETBASE FILE MYDATAB.DATA.PROD,HP996,HP947;NOLOG PROGRAM @.PUB.BRADMARK;NONB PROGRAM NBPOST.NB.NETBASE;NONB PROGRAM @.NFSPROG.NETBASE;NONB PROGRAM NBADAGER.PUB.NETBASE;NONB PROGRAM NBGENRL.PUB.NETBASE;NONB PROGRAM @.PUB.REGO;NONB PROGRAM VTSERVER.NET.SYS;NONB PROGRAM CI.PUB.
Chapter 4 Special Command Features The subsystem command processor has the following special features that provide MPE functionality within NetBase. • Any MPE command that is executable in break may be issued from the subsystem. To enter an MPE command, type the command prefixed by a colon (:). • The REDO command allows the last command entered to be modified and then executed.
Using NBDIR NBDIR Commands The following sections describe the NBDIR commands in detail. ACCOUNT The ACCOUNT command changes the current default account name. When the directory subsystem is entered, the default account is the logon account. Subsequent ACCOUNT commands change the default account name. The default account name is used in most NBDIR commands. By changing the default account, the user is not required to type the account name for each command.
Chapter 4 The default account is changed and file entries are made in the directory: D> ACCOUNT=PROD D> FILE AP.DATA=AP.DATA.ACTNG,ACCT D> FILE MFGENG.DATA,MFG,SHADOW The files are listed again: D> LISTF @.
Using NBDIR BUILD The BUILD command creates and initializes NetBase directories. The default directory size is 1024 records. One record in the directory will be used for each file entry, dataset entry, program entry, user logon, device entry, SQL entry or shadow entry defined. The directory is a hashed file, not unlike an IMAGE master set. As such, the same capacity considerations that are applied to IMAGE master sets should be considered for the directory.
Chapter 4 DEVICE The DEVICE command adds device records to NetBase's directory. The device record is used to redirect spooled output from the local node to a remote node. This is done by redirecting the output for a local spooled device or device class to a remote spooled device or device class. The device record can also be used to specify an alternate spooled device. The alternate device will be used if the primary device is unavailable because communication to the node it is on is down.
Using NBDIR Parameter class (alternate) Description ldev If specified, this parameter indicates an alternate spool device. The alternate spool device is the device that the spool file will be redirected to in the event that the primary spool node is unavailable. Node (alternate) If specified, this parameter is the node name or number of the computer to which the alternate spool device is connected. This parameter is valid only if an alternate spool device is defined.
Chapter 4 The new device records can now be listed: D> LISTD NBD.DATA.NETBASE ---LOCAL--ldev/class ------REMOTE-----ldev/class node -----ALTERNATE----ldev/class node 6 LP WANLP PP PP LP LP LP --None-- SYS-B SYS-B SYS-B -----COPY----ldev/class T E M P LP,1,1 - - P - SYS-A SYS-A To remove entry for WANLP: D> RESET WANLP,D For more information on the DEVICE command, turn to Chapter 7 “NetBase Spooling”.
Using NBDIR DIR The DIR command changes which directory NBDIR will use. When NBDIR is first executed, it opens the directory that is specified in the NetBase configuration. This command closes the current directory and opens the specified directory. Syntax D> DIR filename Parameters Parameter Description filename The file name of a valid NetBase directory. Example For example, to change the directory to TESTDIR, enter the following syntax.
Chapter 4 DISPLAY The DISPLAY command allows you to display the current node name or number in the NetBase directory. This command changes the node name formats for LIST and UNLOAD commands. Syntax D> DISPLAY {NAMES | NUMBERS} Parameters Parameter Description names The current node name. Numbers The current node number. Example The following example demonstrates how to show the current node number in the NetBase directory. NetBase Directory Program [x.
Using NBDIR DSET The DSET command is used in data set shadowing. It works in conjunction with the FILE command to define the datasets to be shadowed. The FILE command is used first to define a database. The INCLUDE and EXCLUDE options on the FILE command determine whether the dataset defined by the DSET command is included for shadowing or if the dataset is to be excluded from the shadowing. The RESET option is used to delete a dataset entry from the directory.
Chapter 4 The datasets that are defined for a database can be listed as follows: D> LISTF BANNER.DATA.NETBASE,DSET -----LOCAL REFERENCE-----File Group Account BANNER DATA Data Sets: NETBASE DEVICES -----REMOTE EQUIVALENT----File Group Account Node -> --Same-(Shadow) NODE-A NODE-B D F S P P S L Y R L E E A N O O N T G C T G - I - - - Y HEADERS D> For more information on partial database shadowing, turn to Chapter 5 “NetBase Shadowing”.
Using NBDIR FILE The FILE command identifies a file for NetBase. The parameters on the FILE command change how NetBase treats the file. One function of the command is to enable access to files on a remote computer for local processes. Another is to identify files to be shadowed, ensuring data integrity. The formal file name, or the local reference, is the name of the file as it is referenced by local user processes.
Chapter 4 Syntax D> FILE filename[=remote-name],{nodename}[,shadow[,…]][;options] {node# } where option =| DUALACC | LOCAL | LOCALACC | MASTER | READ ALT=node[,node] BUFONLY CLOSE EXCLUDE | INCLUDE IMAGELOG INFO LOCK LOGONLY | NOLOG MAP NOKFILES NOPEND READPASS=password SHADOW SYNC SYNCERR=FAIL SYNCERR=REMOTE UPDPASS=password Parameters Parameter Description filename The fully-qualified formal file name. Remote-name If specified, this parameter is the actual file name on the remote computer.
Using NBDIR Parameter Description DUALACC Enables NetBase to switch from shadow (local) to remote on locks, staying remote until unlock is enabled. Pending locks must be disabled on the shadow system. LOCAL If a file is defined with the LOCAL option, NetBase always opens the local copy of the file. If the local copy is a shadow copy, access to the file is limited to read only. LOCALACC Same as LOCAL option (above), except that NetBase returns the original access options when requested.
Chapter 4 Parameter Description LOCK This option is only applicable for non-IMAGE files. It causes the shadow posting process to open the shadow copy with LOCK access. This allows user processes to open the file with lock access. LOGONLY This option is only applicable for files that are not shadowed. If logging is enabled, specifying this option causes the export process to log all updates to this file. NOLOG This option is only applicable for files that are shadowed.
Using NBDIR Parameter Description SYNC This option is only applicable for IMAGE files. It must be specified if item level locking (DBLOCK modes 5 and 6) is used on the file. It guarantees synchronization of all updates to shadowed files. SYNCERR=FAIL This option is only applicable to shadow files. It causes NetBase to disable all access to the shadow file if the file loses synchronization with its master copy. SYNCERR=REMOTE This option is only applicable to shadow files.
Chapter 4 GROUP The GROUP command changes the current default group. When the directory subsystem is entered, the default group is the logon group. Subsequent GROUP commands change the default group name. The default group name is used in most NBDIR commands. By changing the default group, the user is not required to type the group name for each command. Syntax D> GROUP=groupname Parameters Parameter Description groupname The new default group name.
Using NBDIR LIMIT This command builds a new directory to the new size specified in the command. It then copies the file entries from the old directory to the new directory and purges the old directory. It also recreates the (KSAM) directory index file and loads it from the new directory. If the filesize parameter is omitted, this command displays the current directory statistics only. To execute this command, exclusive access of the directory must be obtained.
Chapter 4 LISTD The LISTD command is used to display the devices that are defined in the NetBase directory. The display shows the mapping of spool files across the network. For example, the display header appears as follows: ---LOCAL--ldev/class ------REMOTE-----ldev/class node -----ALTERNATE----ldev/class node T E -----COPY-----M ldev/class P U S E R The following table provides descriptions of the items in the display header.
Using NBDIR Example To display all spooled device records in the directory: D> LISTD NBD.DATA.NETBASE ---LOCAL--ldev/class ------REMOTE-----ldev/class node -----ALTERNATE----ldev/class node 105 LP LP88 PP --Same-LP --None---None-LP SYS-B SYS-C SYS-B SYS-A T E -----COPY---- M ldev/class P LP,2,1 U S E R - - U T U D> To display all the devices whose device class starts with the string LP: D> LISTD LP@ NBD.DATA.
Chapter 4 LISTF The LISTF command is used to display files that are in the NetBase directory. The display includes all the information about the file. The flags depict the options that were specified when the file was defined with the FILE command.
Using NBDIR Header Item Description R DSET Only READ access opens are allowed on the shadow copy of the file or database. This flag applies to dataset shadowing only. Valid values are: E I FLAG SYNC Only the datasets defined will be shadowed. The defined datasets for this file are listed using the DSET or ALL options. If this flag is set, its valid values are: I This flag applies to IMAGE files only. It directs NetBase to open a local copy of the database root file to satisfy DBINFO calls.
Chapter 4 Parameters Parameter Description fileset The file set to be listed. If the files are not in the default group and/or account, the group and/or account must be specified. Wildcards are valid. DSET If specified, the dataset records associated with the fileset will be included in the listing. ALL If specified, the FILE parameters and dataset records associated with the fileset will be included in the listing. Example To display all files in the directory: D> LISTF @.@.
Using NBDIR Or to display a subset of the files in the default group and account: D> GROUP=DATA D> ACCOUNT=PROD D> LISTF MFG@ -----LOCAL REFERENCE-----File Group Account -----REMOTE EQUIVALENT----File Group Account Node MFGENG DATA PROD -> MFGORD DATA PROD -> MFGPUR DATA PROD -> MFGWIP DATA PROD -> --Same-(Shadow) --Same-(Shadow) --Same-(Shadow) --Same-(Shadow) MFG ACCT MFG ACCT MFG ACCT MFG ACCT O P E N D S E T F L A G S Y N C P R L O O T G M - I - P - - - Y P Y - - - Y P Y L - -
Chapter 4 LISTL The LISTL command displays remote logon strings used with AutoRPM that have been entered into the NetBase directory. The header for the display appears as follows: -- LOCAL LOGON -User Acct -- TO -Node -------------- REMOTE LOGON --------------Logon String The following table provides descriptions of the items in the display header. Header Item Description LOCAL LOGON User Account The user and account names of a user running a program through AutoRPM.
Using NBDIR Example To list all logon strings in the directory: D> LISTL @.@:@ Directory: NBD.DATA.NETBASE -- LOCAL LOGON -User Acct -- TO -Node -------------- REMOTE LOGON --------------Logon String @ MGR TOM NODE-A NODE-B NODE-A DESKUSER,MGR.NETBASE,PUB RPM,MGR.NETBASE,PUB TOM,MGR/.
Chapter 4 LISTP The LISTP command displays records that are in the NetBase directory. Records are used for two different purposes. One function is to disable NetBase options for a program or a set of programs. They are also used for AutoRPM. The display shows the NetBase options that are to be disabled for this file or file set. It also shows the AutoRPM options that are set for this file set. The header for the display appears as follows: Node: FOX Directory: NBD.DATA.
Using NBDIR If a file is defined with load parameters for AutoRPM, the load parameters are displayed on the second line. This line displays the load library and the run parameter, the XL list and the DEBUG flag. Syntax D> LISTP [fileset] Parameters Parameter Description fileset Indicates the file or set of files to be listed. Wildcards are allowed. If the group or account is not specified, the default group or account is used. Example To display all the files in the directory: D> LISTP @.@.
Chapter 4 LISTS The LISTS command displays shadow records that are in the NetBase directory. A shadow record identifies a shadow file that exists on the local node. It is used by the posting process to identify shadow records as they come in from remote nodes. They are also used for information about the current state of shadowing for the file.
Using NBDIR Header Item Description R Roll forward indicates that a roll forward recovery is in progress. USR = U This flag indicates that Post User Exits are enabled for this file. DIS = D This flag indicates that NetBase is discarding updates to this particular file. If it is set, the SYN flag may also be set, indicating why this is occurring. Turn to Chapter 5 “NetBase Shadowing” for more information on error recovery.
Chapter 4 Parameter Description ERR Shows only those records that are in one of the following states: Q, S, or D. PASS Displays passwords on SHADOW statements. Example To list all the shadow files on this node: D> LISTS @.@.@ Directory: NBD.DATA.
Using NBDIR LISTSQLI The LISTSQLI command displays DBE's that are defined for inbound SQL shadowing in the NetBase directory. The flags depict the options that were specified when the file was defined with the SQLIN command. The header for the inbound SQL shadowing file display appears as follows: ------LOCAL DBE NAME-----File Group Account -----ACTUAL DBE NAME----File Group Account Node E X I T Pri The following table provides descriptions of the items in the display header.
Chapter 4 To list all the SQL shadow files on this node: D> LISTSQLI @.@.@ Directory: NBD.DATA.
Using NBDIR LISTSQLO The LISTSQLO command displays DBE's that are defined for outbound SQL shadowing in the NetBase directory. The flags depict the options that were specified when the file was defined with the SQLOUT command. The header for the outbound SQL shadowing file display appears as follows: ------LOCAL DBE NAME-----File Group Account -----ACTUAL DBE NAME----File Group Account Node E X I # of T Part Freq The following table provides descriptions of the items in the display header.
Chapter 4 Parameters Parameter Description fileset The file set to be listed. Wildcards are allowed. If the group or account is not specified, the default group or account will be used. Example To list all the shadow files on this node: D> LISTSQLO @.@.@ Directory: NBD.DATA.
Using NBDIR LISTX The LISTX command is used to display user-defined XL lists in the directory. The XL list is used by NetBase when running a remote process or creating a local process. The XL= option of the PROGRAM command attaches an XL list to a program to be run by NetBase. Syntax D> LISTX [listname] Parameters Parameter Description listname User-defined name of an XL list. Wildcards are allowed. Example D> LISTX @ Directory: NBD.DATA.NETBASE Name XL List TESTXL NMXL1.PUB,NMXL2.
Chapter 4 LOGON The LOGON command enters logon records into the directory. The logon record is used by AutoRPM when logging a user onto a remote node. Wildcards are valid only for the localuser parameter. This command requires NODE MANAGER (NM) or SYSTEM MANAGER (SM) capability. Syntax D> LOGON localuser[:node]=logonstring Parameters Parameter Description localuser The user name and account name of the local user. The @ wildcard is valid only for user.
Using NBDIR To display the logon records after they have been entered: D> LISTL @.@:@ Directory: NBD.DATA.NETBASE -- LOCAL LOGON -User Acct -- TO -Node -------------- REMOTE LOGON --------------Logon String @ MGR SYSB SYSC NETUSER,MGR.NETBASE,PUB RPM,MGR.DIST,PUB NETBASE DIST For more information, turn to Chapter 8 “AutoRPM”.
Chapter 4 PROGRAM This command writes the program records to the open NetBase directory. There are three purposes for adding program records to the directory, they are: • Disable NetBase functions on one program or on a set of programs. • Override certain run time options from those specified at process creation. • Define processes that NetBase will run on a remote node using NS's RPM. If the command is issued without specifying a remote program name or remote node, it is used to disable NetBase functions.
Using NBDIR Parameters Parameter Description progname The programs running under NetBase whose NetBase functions will be disabled. MAP Uses a remoteprog name instead of a local name for local creations. NOBUF Disables NFA buffering for this program set. NONB Disables all NetBase features for this set of programs. If this option is selected, all other options are invalid. NOREL If this option is selected, the server for a process in this program set is not released on the last file close.
Chapter 4 Parameter Description nodeid The remote node where NetBase will run the remote program. NOEQ This option disables sending the file equates for the local process to the remote node for the remote process. NOJCW If this option is selected, NetBase will not transmit the JCW from the remote process to the local process when the remote process terminates. SHADOW Causes NetBase to preallocate all shadowing buffers before first file open. Required for some V/PLUS applications.
Using NBDIR To run a native mode program on the remote node, specifying an XL list and the DEBUG parameter, first enter the XL list: D> XL TESTXL=NMXL1.PUB,NMXL2.PUB D> PROGRAM XLPROG,3;XL=TESTXL To display all the program records in the directory: D> LISTP @.@.@ Directory: NBD.DATA.
Chapter 4 REBUILD The REBUILD command rebuilds the KSAM file associated with the current directory. This command is normally used if the integrity of the KSAM directory is suspect. To execute this command, you must have exclusive access of the directory KSAM file. You must also be signed onto the same account as the directory. Syntax D> REBUILD Parameters This command does not have any parameters.
Using NBDIR RESET The RESET command removes a record from the NetBase directory. Once an entry is removed, it will no longer be referenced the next time that file is opened. Active processes, with previously defined files opened, will not be affected. DSET records are removed with the DSET command. SQLOUT and SQLIN records are removed by the SQLOUT and SQLIN commands. This command requires NODE MANAGER (NM) or SYSTEM MANAGER (SM) capability.
Chapter 4 Example To remove a file record from the directory: D> RESET MFGENG.DATA.PROD To remove a file record from the directory, using the default group and account: D> GROUP=DATA D> ACCOUNT=DIST D> RESET OPCUST To remove a program record from the directory: D> RESET QUERY.PUB.NETBASE,PROGRAM To remove a device record from the directory, using the short form of the record type flag: D> RESET 88,D To remove all the File statements for files that start with the letter K: D> RESET K@.@.
Using NBDIR SHADOW The SHADOW command adds shadow records to NetBase's directory. The shadow record defines shadowing for a file that is already defined in the network. SHADOW records are entered on the shadow system only. The posting processes uses the shadow record when opening the file for updates and to mark the status of updates to the shadow file. Turn to Chapter 5 “NetBase Shadowing” for more information on how these records are used.
Chapter 4 Parameter Description OVERRIDE Applicable to shadowed MPE files only. If specified, this parameter causes the post process to ignore update related synchronization errors. PASS=password This option applies only to IMAGE databases and is required. It specifies the password for a database to be used by the posting process to open the shadow file for updating. The password must allow update access to all sets and items to be shadowed. Note: Remember that all IMAGE passwords are case sensitive.
Using NBDIR To list a shadow file that has gone out of sync: D> LISTS AP.DATA.PROD Directory: NBD.DATA.
Chapter 4 SQLIN The SQLIN command is used to define which DBE's are importing updates from which nodes. See the NetBase SQL Shadowing Handbook for more information on how these records are used. This command requires NODE MANAGER (NM) or SYSTEM MANAGER (SM) capability. Syntax D> SQLIN dbename node [;PRI=transaction-priority] [;EXECPRI={BS|CS|DS|ES}] [;ORIGDBE=dbename] [;USEREXIT] [;RESET] To set up multiple import processes for one DBE: D> SQLIN fakedbe1=dbename,node;PART=part1,[part2[,...]][...
Using NBDIR Parameter Description EXECPRI=BS|CS|DS|ES Specifies the execution priority for the SQL import process. ORIGDBE Specifies the DBE name on the master. USEREXIT Specifies that a user exit routine should be called with each transaction received for the defined file. fakedbe1, fakedbe2 The pseudo name of the database to be used to administer the partition. Use this name when starting and stopping the import process for the partition.
Chapter 4 SQLOUT The SQLOUT command is used to define which DBEs are to have transactions exported and to which nodes. See the NetBase SQL Shadowing Handbook for more information on how these records are used. This command requires NODE MANAGER (NM) or SYSTEM MANAGER (SM) capability. Syntax D> SQLOUT dbename,node ;HOME=home-partition[,part2[,...]] [;EXECPRI={BS|CS|DS|ES}] [;FREQ=wakeup-seconds] [;{INCLUDE|EXCLUDE}] [;RESET] [;USEREXIT] D> SQLOUT dbename,@;PART=partition1[,partition2[,...
Using NBDIR Parameter Description EXCLUDE Excludes (from shadowing) the tables specified in the TABLE command for this database. INCLUDE Shadows the tables specified in the TABLE command for this database. RESET Resets the SQLOUT record for this database. USEREXIT Specifies that a user exit routine should be called with each transaction sent for the defined file. fakedbe1, fakedbe2 The pseudo name of the database to be used to administer the partition.
Chapter 4 Below is an example of some SQL shadowing using multiple export processes for one DBE: D> SQLOUT GGDBE.PART1.PRODACT=GGDBE.DATAB.PRODACT,shadownode;HOME=1;EXECPRI=CS D> SQLOUT GGDBE.PART4.PRODACT=GGDBE.DATAB.PRODACT,shadownode;HOME=4;EXECPRI=DS D> SQLOUT CCDBE.DATAB.PRODACT,shadownode;HOME=1;EXECPRI=DS;EXCLUDE D> TABLE CCDBE.DATAB.PRODACT,shadownode,TUPLEONE D> TABLE CCDBE.DATAB.PRODACT,shadownode,TUPLETWO D> TABLE CCDBE.DATAB.PRODACT,shadownode,TUPLETHREE D> listsqlo @.@.
Using NBDIR TABLE The TABLE command works in conjunction with an SQLOUT command. The SQLOUT command indicates whether the associated TABLE commands specify tables to be included or excluded from shadowing. See the NetBase SQL Shadowing Handbook for more information. Syntax D> TABLE dbename,node,tablename[,RESET] Parameters Parameter Description dbename The name of the Allbase database. node The name of the node to which this table should or should not be shadowed.
Chapter 4 If DBE2 includes 40 tables, and you want to shadow only the first three, the INCLUDE option is your best choice: On SYSA: :NBDIR.PUB.NETBASE D> SQLOUT DBE2.DATA.PROD,SYSB;HOME=1;INCLUDE D> TABLE DBE2.DATA.PROD,SYSB,TABLE1 D> TABLE DBE2.DATA.PROD,SYSB,TABLE2 D> TABLE DBE2.DATA.PROD,SYSB,TABLE3 On SYSB: :NBDIR.PUB.NETBASE D> SQLIN DBE2.DATA.
Using NBDIR UNLOAD This command is used to create an ASCII file containing the entries in NetBase's directory. The UNLOAD command creates a file which contains the commands necessary to rebuild the NetBase directory. This file may be edited and used to reload the directory. The UNLOAD command does not unload SQL Shadowing commands. This command requires ACCOUNT MANAGER (AM) or SYSTEM MANAGER (SM) capability.
Chapter 4 XL The XL command enters XL list records into the directory. The XL list is used in conjunction with the PROGRAM command to define the run string for a program to be run remotely or created locally through NetBase. This command requires NODE MANAGER (NM) or SYSTEM MANAGER (SM) capability. Syntax D> XL name=[file[,file[,...]]] Parameters Name Description name The user-defined name of the XL list. file The name of an XL file as it should appear in the run command.
C H A P T E R 5 NetBase Shadowing NetBase shadowing provides the ability to maintain concurrent multiple copies of files and databases across one or more systems in a network. Since it does not rely on IMAGE logging, NetBase can shadow all types of disk files, not only databases.
Chapter 5 Process Overview NetBase operates on the principle of master and shadow copies of files and databases. Each file that is to be shadowed will have a master copy to which all updates are performed. The updates are then transported and posted to the shadow copies. This guarantees that all copies will be exact duplicates of each other. In addition, updates occur to the shadow copy in the exact order that they occurred against the master.
NetBase Shadowing The process of reading the transactions from the NBM file is done by NBEXPORT. This is a process under the NetBase background job. If the NetBase background job is not running, the export process cannot read the transactions from the NBM file and send them to the shadow system. The NBEXPORT process reads the transactions from the shadow transport file and sends them to the shadow system.
Chapter 5 Shadow System The shadow transactions are received by the NBIMPORT process. This process writes the transactions into import queue files. These files are contained in the QUEUE.NETBASE group. Next, the posting process, NBPOST, reads the transactions from the import queue files and applies them to the shadow copies. If the posting process is not running, the transactions will accumulate in the import queue files.
NetBase Shadowing Configuration Parameters The operation of NetBase, including its various features, is defined by NetBase's configuration parameters. Configuration maintenance is a subsystem of the NetBase control program, NBCTRL. The configuration parameters can be displayed and modified using the configuration subsystem. The systems manager should become familiar with the control program, the configuration parameters, and the configuration maintenance commands in order to set up the shadowing facility.
Chapter 5 :NBCTRL.PUB.NETBASE NetBase Control Program [x.x] Update 0 (C) QUEST Software 1996 *> CONFIG C>L SHADOW SHADOW SHADOW SHADOW SHADOW SHADOW SHADOW SHADOW SHADOW SHADOW SHADOW SHADOW SHADOW SHADOW SHADOW SHADOW SHADOW SHADOW SHADOW SHADOW SHADOW SHADOW SHADOW SHADOW SHADOW SHADOW SHADOW SHADOW SHADOW SHADOW SHADOW SHADOW SHADOW - Close Log file on suspend. Flush Shadow File Posts... Errors Before Disable..... Check KSAM record counts.. Disable file autoresync .. Log Post Errors...........
NetBase Shadowing There are also node level parameters associated with shadowing. These parameters affect each node in the system. Before modifying any of the node level shadowing parameters, please contact the Technical Support group. The node level parameters may be listed by entering the list command l followed by the node number or node name, in this case, 1: Note. If you have a node name that matches one of the CONFIG categories (SHADOW or NFA), you will have to use the node number.
Chapter 5 Defining a File for Shadowing - NBDIR Entries To define a file for shadowing, NetBase directory entries must be made on both the master and shadow systems. These directory entries tell NetBase which files to shadow and to which nodes. A FILE statement is entered in the directory on the master system, and a FILE and SHADOW statement is required on the shadow system. This section details the steps required to start the shadowing process for a file or database.
NetBase Shadowing Valid FILE Options for the Master System The following table lists FILE command options for affecting processes that access the master file. For a full description of these options, turn to Chapter 4 “Using NBDIR”. Option Description SYNC Use for non-IMAGE files that do not have a locking strategy or with IMAGE databases if not using TPS shadowing. NOKFILES Do not shadow files with names that match the pattern ?#######. EXCLUDE Do not shadow defined datasets.
Chapter 5 5-10 Option Description LOCK For non-IMAGE files, open shadow file with lock access SYNCERR=FAIL Fail open on shadow file if out of sync SYNCERR=REMOTE Access master copy if out of sync (requires NFA) SHADOW This option is only valid if the shadow copy of a file exists on the same computer as the master copy. Specifying this option causes NetBase to treat this file as the shadow copy.
NetBase Shadowing SHADOW Command Options The SHADOW command provides a number of options that affect the way the shadow copy of a file or database is accessed or updated by the NetBase posting process. The posting process uses the SHADOW directory record when opening the file for updates and to mark the status of those updates to the shadow file. The SHADOW command is only issued on the system where the shadow copy of a file or database resides.
Chapter 5 Examples of Directory Entries for Shadowing This section provides three examples of making directory entries for shadowing from one system to another system. Example 1 Set up the directory entries necessary to shadow BANNER.DATA.NETBASE from SYSA to SYSB. In this example the remote name does not need to be specified since we are shadowing to the same group and account on SYSB. On the master system, enter: RUN NBDIR.PUB.NETBASE D> FILE BANNER.DATA.
NetBase Shadowing Example 3: Set up the directory entries necessary to shadow all the files in DATA.PROD from SYSA to SYSB. When shadowing entire groups or accounts, you must still specify an individual SHADOW statement for IMAGE databases. This is to provide NBPOST with the correct password to use for opening the shadow copy. On the master system, enter: RUN NBDIR.PUB.NETBASE D> FILE @.DATA.PROD,SYSA,SYSB On the shadow system, enter: RUN NBDIR.PUB.NETBASE D> FILE @.DATA.PROD,SYSA,SYSB D> SHADOW @.DATA.
Chapter 5 Third Party Shadowing (TPS) for TurboIMAGE databases Hewlett Packard has added TPS (Third Party Shadowing) to IMAGE. This means that for every IMAGE DBPUT, DBUPDATE or DBDELETE NetBase will be called from within the IMAGE transaction. The advantage to NetBase is that the write to the NBM file is a part of the IMAGE transaction. The NetBase TPS procedures are in an XL named XLNETBSE.PUB.SYS. The file is created during the NetBase installation job. Application DBPUT 1 XLNETBSE.PUB.
NetBase Shadowing Run the utility by entering: RUN NBTPSUTL;INFO="[^]name" Name is the name of a database, or if preceded by a carat (^), the name of a file containing a list of databases. The program prints a message for every database that the program attempts to TPS enable, for example: RUN NBTPSUTL;INFO=“^BASELIST” VISTA.DATA now enabled for TPS BANNER now enabled for TPS SWADB already enabled for TPS END OF PROGRAM A database can be RE-enabled for TPS using DBUTIL.
Chapter 5 Setting Up Shadowing Use the following steps to set up NetBase Shadowing on your master and shadow systems. To set up shadowing: 1. On the shadow system, stop the posting process. :NBCTRL.PUB.NETBASE;INFO=“STOP POST” 2. On the master system, store the data. 3. On the master system, add directory entries for shadowing using NBDIR. 4. On the master system, enable databases for TPS using NBTPSUTL. 5. On the master system, allow users access to the data. 6.
NetBase Shadowing Monitoring Shadowing Within NBCTRL, the NetBase shadowing processes can be monitored. This section describes the commands that can be used for monitoring the master and shadow systems. See the following diagram. Master System Shadow System NBCTRL SHOW EXPORT NBCTRL SHOW IMPORT SHOW POST SHOW POST node NBDIR LISTS NBSYNC,Verify On the master system, the SHOW EXPORT command gives a count of the total number of transactions sent to each shadow system.
Chapter 5 On the shadow system, the SHOW IMPORT command gives a count of the total number of transactions received from each master system. These values gets reset whenever the NetBase background job is stopped and restarted or whenever IMPORT is stopped and restarted. :RUN NBCTRL.PUB.NETBASE NetBase Control Program [x.
NetBase Shadowing In the previous display, the column SYN indicates whether or not the file is in sync. If there is an S in the column, that indicates a sync error. The column QUE indicates whether or not the transactions for a particular file are in a queue state. If a Q is present in this column, the posting process is writing all the transactions for that particular file into Post Queues for later recovery. Turn to Appendix B “Troubleshooting NetBase” for information on recovering files in a queue state.
Chapter 5 Checking the State of Shadowed Files The following sections describe two ways to check the state of shadowed files, one using NBDIR.PUB.NETBASE with the LISTS command, and the other using NBSYNC.PUB.NETBASE, VERIFY. NBDIR.PUB.NETBASE - LISTS Command Using NBDIR.PUB.NETBASE, issue the LISTS command and check the status flags. If an S appears in the SYN column, that indicates the file is out of sync. The Sync Lost at ... message is the date and time of the most recent sync error. :RUN NBDIR.PUB.
NetBase Shadowing Checking for Synchronization: The SHADOW statements in the NetBase directory on the shadow system are used by the posting process to flag whether or not a shadow file is in sync. The LISTS command in NBDIR can be used to see which files are out of sync or discarding. However, if you are shadowing numerous files, this display can be cumbersome and hard to read. The utility, NBSYNC, can be used to check to see the state of shadowed files. RUN NBSYNC.PUB.NETBASE,VERIFY;INFO=”@.@.
Chapter 5 Sample NBSYNC Job !JOB CHCKSYNC,MGR.NETBASE !COMMENT Checks for out of sync conditions !COMMENT !COMMENT Step 1 - Clean directory - the REMOVE entry !COMMENT point will remove any SHADOW statements !COMMENT from the directory that do not have a physical !COMMENT file on the shadow system !RUN NBSYNC.PUB.NETBASE,REMOVE !COMMENT !COMMENT Step 2 - Check the state of shadowed files !RUN NBSYNC.PUB.NETBASE,VERIFY;INFO=“@.@.
NetBase Shadowing Sync or Discard State Shadow files that are in either an S (out of sync) or D (discard) state, must be resynced. Resyncing a shadow copy involves refreshing the data on the shadow system with a copy of the data from the master system. To resync: 1. On the master system, stop access to the data. You must do this to create a store of the data. 2. On the shadow system, stop the posting process: :RUN NBCTRL.PUB.
Chapter 5 The posting process will automatically discard any transactions that are prior to the RESYNC time since it is assumed that those transactions were included in the data that was restored. Any transactions after the resync time are applied to the shadow copy. Transactions times are from the master system, the time on the shadow system is irrelevant. Example 1 This example uses NBSYNC to perform the RESTORE on the shadow system. Notice that NBSYNC issues the appropriate STORE/RESTORE command.
NetBase Shadowing To verify that the SYNC flag has been reset, use the NBDIR utility: :RUN NBDIR.PUB.NETBASE NetBase Directory Program [x.x] Update 0 (C) QUEST Software 1996 D> LISTS FT.TEST.QUEST,INFO Node: BUGS Directory: ALS.DATA.
Chapter 5 Example 2 If you use a backup software product at your site, you do not need to have NBSYNC do the restore for you. If you have some method of getting the files from the master to shadow system, then the only step required of NBSYNC is to reset the directory flags for the shadowed file. If the utility that you use for the restore/copy has an OLDDATE option, then you can run NBSYNC with the RESET entry point.
NetBase Shadowing Example 3 You may also resync a file using a copy utility such as DSCOPY. These utilities, however, typically copy the file into a NEW file, rather than retaining the OLD file label information of the original file. In this case, it is necessary to tell NetBase the original modify date and time information from the master copy of the file. For example, to resync the file BANNER.DATA.
Chapter 5 NBSYNC Syntax The syntax for running NBSYNC is as follows: :RUN NBSYNC.PUB.NETBASE[,entry point] where entry point = CLEAR CREATE ENTER DISCARD NOW REMOVE REMOVEALL RESET VERIFY The optional alternate entry points work as follows: Entry Point Description CLEAR Has the same effect as resetting and reentering a shadow entry for a file. CREATE Creates shadow records for any permanent file on the system that is covered by a wildcard shadow record.
NetBase Shadowing Entry Point Description REMOVEALL Deletes all automatically added entries, including ones in the queue state. RESET Running NBSYNC using this entry point causes NBSYNC to not invoke the restore command, but to just prompt for the files to be reset. This is often used when it is desired to restore the files with a utility other than the MPE RESTORE command.
Chapter 5 Structural Changes for Shadowed Databases NetBase maintains exact physical copies of files that are being shadowed. With TurboIMAGE databases, whenever a structural change (such as a capacity change, dataset packing or the creating of new datasets) is made to the master system, it must also be applied to the shadow database. Handling structural changes can be done three ways: through the 1) the ADAGER interface 2) the DBGENERAL interface, or by 3) manually coordinating updates.
NetBase Shadowing Notes • The command file, ADAGER.PUB.NETBASE, must be used. • Only one database can be modified per execution of the command file. • Online changes made with ADAGER are not shadowed. • will work when the data set is out of sync or queuing. The out of sync or queue state will not change, but the capacity change will happen. ADAGER.PUB.NETBASE 2) NetBase DBGENERAL Interface NetBase also has an interface with DBGENERAL.
Chapter 5 On the master system: 1. Get all users out of the master database. 2. Flush all of the records through to the shadow database and then stop posting in the shadow node. This can be accomplished by running the following program on the master machine: RUN NBFLUSH.PUB.NETBASE,STOPWAIT;PARM=node When this program finishes, all the records for the shadow machine will be flushed and posted and then the posting process will be stopped. The node number specified is the node number of the shadow node.
NetBase Shadowing Flushing Shadow Updates It can be useful to know when all updates have been posted to the shadow copies after the update processes have completed. NetBase provides a process called NBFLUSH that can be used to accomplish this task. The NBFLUSH utility is used to flush updates to the shadow copy of a file so it can be released by the posting process. is run on the machine where the master copy of the file resides. The program writes a special record to the shadow log file.
Chapter 5 Entry Point Description STOP The STOP entry point is used to flush updates for all the files on a node. When using this entry point, the INFO parameter is not required, NBFLUSH will write a stop record for the node specified and then terminate. When the posting process receives the stop record, all files will be closed and the post process will enter the STOP state.
NetBase Shadowing The program may be run with alternate entry points to provide optional features. If the program is run with the WAIT entry point specified, the posting process sends a message back to NBFLUSH before terminating. If any of the processes that propagate the message between NBFLUSH and the posting process are down, an error message is returned to NBFLUSH. This works slightly differently if shadowing is being performed using IMAGE log files.
Chapter 5 In all cases, when NBFLUSH completes, it sets a JCW named NBFLUSH. If the value of NBFLUSH is other than zero, an error has occurred. The possible values for NBFLUSH and their meaning are shown in the following table. Value Description 0 Successful, no errors. If a wait option was specified, the task is complete on the shadow system. 1 NetBase is not running. 2 NetBase log control process is not running. 3 The NetBase log process is not running.
NetBase Shadowing To backup files: 1. Run NBCTRL and enter the STOP POST command on the system where the shadow files reside. The import process will start queuing updates to the shadow files. 2. Store the shadow files to tape. 3. Run NBCTRL and enter the START POST command. This will restart the posting process. When the START POST command is issued, NetBase restarts all the posting processes (one process per import node).
Chapter 5 User Exits Two types of user exits are available: export user exits or post user exits. Export user exits can be used to preprocess data before sending it to shadow system or to implement selective shadowing based on the value of the data. Post user exits are called by the posting process prior to writing to the shadow copy. They can be used to implement custom shadowing where a single transaction can be used to update multiple files. Master System NetBase Background Job NBEXPORT NBM.
NetBase Shadowing Note. Since only one user exit procedure name is currently supported, the procedure must have the logic necessary to process all files simultaneously. This typically requires simple switching logic to other procedures. All records that pass through the Shadow Export Transport are sent to the EXPORTEXIT. The procedure can determine the disposition of each record and can individually control logging if necessary.
Chapter 5 Parameters Parameter Description comarea An array of various information used to control the posting of shadow information. Some fields are reserved and cannot be modified. The format is: Bytes Contents 0..1 Action flag. Set by the user exit procedure to determine the action to be taken by the exporting process. The valid values are: 0 Process record normally. 1 Ignore record completely. 2 Disable all subsequent calls to the user exit facility. 3 Send record to ALL configured nodes.
NetBase Shadowing The following additional fields are available only if the Export Process Info configuration option is set on the master machine. The Process Info to Exp Exit option must be set in NBCTRL, CONFIG. All of these fields will be set to binary zeros (0) if these options are either not enabled or not available. Parameter Description comarea Bytes Contents 14..37 Program name. Program name of the updating program. 38..45 Session/Job name. The session/job name of the updating user. 46..
Chapter 5 Parameter Description header Contains all non-data information about the original update. This field contains the following: Bytes Contents 0..23 File name. This is the file name of the original, master copy of the file. The name is formatted as FILE, GROUP, ACCOUNT with no delimiters. 24..25 Flag word #1. Currently reserved. 26..27 Date. CALENDAR format of original date of the update. 28..31 Time. CLOCK format of original time of the update. 32..33 Type of update.
NetBase Shadowing Post User Exits The posting process posts updates to a file or a database that is being shadowed. Sometimes, however, additional processing is required. For instance, updates to a particular set of a database may need to be made to a second database. NetBase's posting process has a method of handling these special cases. When additional processing is required, the posting process calls a usersupplied subroutine. The procedure called by the posting process is called POSTUSEREXIT.
Chapter 5 Parameters Parameter Description comarea An array of various information used to control the posting of shadow information. Some fields are reserved and must not be modified. The format is: Bytes Contents 0..1 Action Flag. Set by the user exit procedure to determine the action taken by the posting process. The valid values are: 2..3 0 Successful call. Do not open shadow file. 2 Successful call. Open shadow file for normal posting. 3 Disable subsequent user exit calls.
NetBase Shadowing The following comarea fields are available only if the Export Process Info configuration option is set on the master system and the Save Process Info on Post option is set on the shadow system. They will be set to all binary zeroes (0) if not enabled or not available. Field Description comarea 14..37 Program name of updating program. 38..45 Session/jobname of updating user. 46..53 User name of updating user 54..61 Logon group of updating user 62..
Chapter 5 Parameters Parameter Description comarea An array of various information used to control the posting of shadow information. Some fields are reserved and must not be modified. The format is: Bytes Contents 0..1 Action flag. Set by the user exit procedure to determine the action taken by the posting process. The valid values are: 0 Update successful. Increment update counter but do not post shadow file. 1 Record ignored. Do not increment the update count. 2 Post normally.
NetBase Shadowing Parameter Description userarea A 1024 byte field initialized to binary 0's. This field is for the use of the user exit procedure. It retains its values between calls. header Contains all non-data information about the original update. This field contains the following: Bytes Contents 0..23 File name. This is the file name of the original, master copy of the file. The name is formatted as FILE, GROUP, ACCOUNT with no delimiters. 24..25 Flag word #1. Currently reserved. 26..
Chapter 5 Parameter Description old data Original data before update.Only applicable for "update" and "delete" type records. Note that this will be the ENTIRE dataset entry or file record. new data New data after update.Only applicable for "update" and "put" type records. Same format as the "old data". Post User Exit Notes The first thing to keep in mind when writing post user exits is that one procedure must handle all the files which require the use of this facility.
NetBase Shadowing Post User Exit COBOL Example Some sample declarations for the call: 01 01 EXIT-COMMON-AREA. 05 ECA-ACTION PIC S9(4) COMP. 88 ECA-ACT-OK VALUE 0. 88 ECA-ACT-DISCARD VALUE -1. 88 ECA-ACT-SYNC-LOST VALUE -2. 88 ECA-ACT-QUEUE VALUE -3. 88 ECA-ACT-CLOSE VALUE -4. 88 ECA-ACT-IGNORE VALUE 1. 88 ECA-ACT-POST-IT VALUE 2. 88 ECA-ACT-DISABLE VALUE 3. 05 ECA-STATUS PIC S9(4) COMP. 05 ECA-FILE-NODE PIC S9(4) COMP. 05 ECA-THIS-NODE PIC S9(4) COMP. 05 ECA-FILE-NUMBER PIC S9(9) COMP.
Chapter 5 01 01 5-50 NEW-DATA. 05 NEW-KEY-VALUE 05 FILLER 05 NEW-QTY 05 FILLER PIC PIC PIC PIC OUR-FILE. 05 OUR-FILE-NAME 05 OUR-GROUP 05 OUR-ACCOUNT PIC X(8) VALUE "BIGDB". PIC X(8) VALUE "DATA". PIC X(8) VALUE "ACCT". X(8). X(20). S9(9) COMP. X(100).
NetBase Shadowing Sample code: PROCESS-USER-EXIT. * * Ignore this file, it's not the one we want. * IF EHI-FILE-NAME NOT = OUR-FILE THEN MOVE 3 TO ECA-ACTION GO EXIT-ROUTINE. * * Is the data base we want to update open? * IF ECA-FILE-NUMBER = 0 THEN PERFORM OPEN-THE-DATA-BASE IF DATA-BASE-NOT-OPEN THEN MOVE -3 TO ECA-ACTION GO EXIT-ROUTINE ELSE MOVE DATA-BASE-ID TO ECA-FILE-NUMBER MOVE "I" TO ECA-FILE-TYPE.
Chapter 5 Dataset Shadowing Databases can be configured for shadowing so that only specific datasets are actually shadowed. This may be accomplished quite simply. However, be sure to read the “Dataset Shadowing Considerations” at the end of this section before doing the configuration. Configuring a database for dataset shadowing requires the use of both the FILE command and the DSET command.
NetBase Shadowing The datasets that are defined for a database can be listed as follows: D> LISTF BANNER.DATA.
Chapter 5 Shadowing With TurboIMAGE Log Files NetBase also provides the ability to shadow TurboIMAGE log files. The log files can be shadowed to another log file or they can be used to shadow changes directly into a shadow copy of the database. This method does not require the NetBase shell to be installed since it does not use the intercept facility. A separate process known as NBILOG is used to read the transactions from the log files and pass them to the shadow transport facility.
NetBase Shadowing :RUN NBDIR.PUB.NETBASE NetBase Directory Program [x.x] (C) QUEST Software 1996 D> FILE BANLG001.DATA.NETBASE=BANNER.DATA.NETBASE,SYSA,SYSB;IMAGELOG D> EXIT 3. Add the database to NetBase's directory on the shadow machine: :RUN NBDIR.PUB.NETBASE NetBase Directory Program [x.x] (C) QUEST Software 1996 D> FILE BANNER.DATA.NETBASE,SYSA,SYSB D> SHADOW BANNER.DATA.NETBASE;PASS=dbpassword D> EXIT Method 2: To shadow TurboIMAGE log files: 1.
Chapter 5 4. Make sure that IMAGE log file shadowing is enabled in the NetBase configuration. The Use IMAGE Log Files parameter is disabled by default. The next time you start NetBase, it will begin shadowing your log file or you can start the logging process with the START ILOG command in NBCTRL. You will receive messages at the console whenever a new log file is opened.
NetBase Shadowing Resetting the Logging Process If you wish to reset your logging process back to log file number 001, perform the following steps. 1. Stop the MPE logging process on the master system. :LOG logid,STOP 2. Shutdown the Netbase log reader process on the master system using the STOP ILOG command in NBCTRL. :NBCTRL.PUB.NETBASE;INFO="STOP ILOG" 3. Backup, purge or rename the old log files on the master system. 4. Build the new log file on the master system. 5.
Chapter 5 Shadowing with Dynamic Rollback Recovery Note. The following procedures must be followed if 1) you are shadowing a TurboIMAGE and not using TPS, and 2) if the application on the master system uses DBXBEGIN, DBXEND and DBXUNDO. If the application on the master system uses the DBXBEGIN, DBXEND and DBXUNDO TurboIMAGE intrinsics, the ;DBX option must be used to ensure the database stays in sync. The ;DBX option is specified on the SHADOW statement on the shadow system.
NetBase Shadowing 3. Your FILE statement on the master machine needs to have SYNC added to it, for example: D>FILE CHKDB.group.account,masternode,shadownode;SYNC 4. If you are setting up shadowing for the first time, perform a store/restore with the OLDDATE option to get the data from the master to the shadow machine. If you have already been shadowing the database, the store/restore step is not necessary.
C H A P T E R 6 NetBase NFA Network File Access (NFA) allows users access to files and databases regardless of where they physically exist in the network. In this chapter, you will find an explanation of how NetBase NFA accomplishes this using the NetBase components.
Chapter 6 NFA Overview The basic operating principles of NetBase NFA are straightforward. All calls to the file and database systems are intercepted by the NetBase shell. Depending on the location of the file as specified in NetBase's directory, NetBase passes the calls either to MPE or to a server on the remote machine. The server process performs the call, and the results of the call are then returned to the user process on the local machine.
NetBase NFA Buffering In order to enhance the performance of remote file access, NetBase reduces the number of network transactions by using buffering. When an application performs a DBFIND, NetBase performs a DBFIND and a DBGET on the remote system, bringing back the data requested plus the data it anticipates the application to need shortly. NetBase returns the requested data to the application and stores the extra data locally.
Chapter 6 Configuring Network File Access The operation of NetBase, including its various features, is defined by NetBase's configuration parameters. Configuration maintenance is a subsystem of the NetBase control program, NBCTRL. The configuration parameters can be displayed and modified using the configuration subsystem.
NetBase NFA Defining a File for NFA As with all files in NetBase, definitions for remote files are entered in NetBase's directory using the directory maintenance program, NBDIR. This is done on the local computer where the program runs so that NetBase knows where the remote files exist and how to access them. This section details the steps required to define a file or database for network file access.
Chapter 6 Option Description UPDPASS=password This option applies to IMAGE databases. It defines a specific password for the remote server to use when opening the database for update access. The server will use this defined password instead of the password specified by the user process. The password is case sensitive. NFA Examples This section provides NFA syntax and examples.
NetBase NFA Example 3 NetBase does not require that the file on the remote machine have the same name as the file referenced by the local process. In the next example, we are going to allow local processes that reference BANNER.DATA.NETBASE to access BANNER.DATA.BACKUP on the remote system. The FILE record tells NetBase that BANNER.DATA.NETBASE is actually BANNER.DATA.BACKUP located on SYSB. D> FILE BANNER.DATA.NETBASE=BANNER.DATA.
Chapter 6 Using OMNIDEX and NetBase The NetBase shell has an enhancement available for capturing and transporting OMNIDEX library calls. Using this enhancement to the shell usually results in lower network traffic and its associated overhead, for remote access of databases that utilize OMNIDEX keys. This is required if any programs will be accessing remote IMAGE databases that contain OMNIDEX indexes.
NetBase NFA Monitoring NFA Use the following NBCTRL commands for monitoring NFA. The NFA services should be configured to come up active with NetBase. For a description of each of these commands, turn to Chapter 2 “Using NBCTRL”. NBCTRL Commands The following table lists the NBCTRL commands used to monitor NFA. Command Function ∗> SERVER Allows or aborts access to specified filesets. ∗> SHOW Displays NetBase's current local and remote user activity and status.
Chapter 6 To abort a particular server: ABORT SERVER id To abort or allow a access to a specified fileset: ∗> SERVER {ABORT=fileset[,fileset[,...]]} {ALLOW=fileset[,fileset[,...
NetBase NFA Remote Procedure Calls The NetBase server process performs operations on a remote system on behalf of a local process. This typically involves satisfying file and IMAGE database calls for remotely located files. The server can also satisfy calls to a user written procedure located in a library on a remote system. This allows a local process to make calls to procedures located on remote systems. When access to remote procedures is required, the local process calls a special subroutine.
Chapter 6 NBRPC Procedure Calling Conventions Use the following syntax and parameters for NBRPC. Syntax NBRPC (node,status,procname,xlname,sendbuff,sendlen,recvbuff,recvlen) Parameters Parameter Description node A 32-bit integer specifying the remote NetBase node number. status A 32-bit signed integer value passed by reference. The status parameter is read in two 16-bit fields: Bits Value/Meaning 16:16 status.subsys: Identifies the subsystem which initiated the error or warning.
NetBase NFA Parameter Description recvlen A 32-bit signed integer by reference returning the actual length in bytes of the data to be transferred in recvbuff. It must be set by the calling process to the maximum receive buffer length. The procedure on the remote system may reset this variable to the actual receive length as long as it is less than or equal to the maximum length. NetBase will return the actual number of bytes returned.
Chapter 6 The following is sample code for NBRPC: 001000 IDENTIFICATION DIVISION. 001100* 001200 PROGRAM-ID. RPCCOB. 001300***************************************************** 001400* Sample main program for use with NBRPC * 001500***************************************************** 001600 ENVIRONMENT DIVISION. 001700 CONFIGURATION SECTION. 001800 SOURCE-COMPUTER. HP-3000. 001900 OBJECT-COMPUTER. HP-3000. 002000* 002100 DATA DIVISION. 002200 WORKING-STORAGE SECTION.
NetBase NFA 005500*Check status of call - if successful, display recv buffer. 005600 IF STATSINFO NOT= 0 THEN 005700 DISPLAY "NBRPC PROCEDURE FAILED" 005800 ELSE 005900 DISPLAY "RECVBUFF = ",RECVBUFF. 006000 006100 STOP-RUN. : 001000$CONTROL SUBPROGRAM 001100 IDENTIFICATION DIVISION. 001200* 001300 PROGRAM-ID. rpctest.
Chapter 6 NFA Security When using NFA, by default all MPE file security is bypassed. If access to data needs to be restricted, NBSECURE must be used to define security. Security for files is defined on the system where the files reside. is used for NetBase security maintenance. The security measures that NetBase has built into it for remote files provides the Network Administrator/Systems Manager a facility for controlling who has what type of access to files on each system.
NetBase NFA Running NBSECURE NBSECURE can be invoked in two ways. To run from MPE, use the following command: :NBSECURE.PUB.NETBASE NBSECURE can also be entered via NBCTRL by entering the SECURITY command: :NBCTRL.PUB.NETBASE ∗> SECURITY S> Any user may run NBSECURE, however, certain commands do require that the user have various capabilities (SM, NM, or OP). Any command other than an inquiry will require special capabilities which are listed in the documentation for each command.
Chapter 6 ACCESS The ACCESS command sets the default file access mode list. The default access is originally set to when the security subsystem is entered. Subsequent ACCESS commands change the default file access mode list. The default access is used by the ALLOW command if the access is not explicitly stated. This default is used for any commands referencing mode list. This command requires SYSTEM MANAGER (SM) capability.
Network File Access ACCOUNT The ACCOUNT command changes the current default account name. When the security subsystem is entered, the default account is the user’s log on account. Subsequent ACCOUNT commands change the default account name. The default account set by ACCOUNT is used by the ALLOW and REMOVE commands when the account name is not explicitly stated. Syntax S> ACCOUNT= {@ } {accountname} Parameters Parameter Description accountname The account name to be used as the default.
Chapter 6 ALLOW This command adds records to NetBase's security directory, thus granting a remote user or a group of remote users the specified access to files. You can open up or restrict access to any set of files existing on the specified system. This command requires SYSTEM MANAGER (SM) capability. The ALLOW command writes a security record to NetBase's security directory.
Network File Access Example Access can be restricted for a specific user or group of users of another system while still allowing the remaining users of the system total access. To do this, first specify the access allowed by all users of a system: S> ALLOW @.@:SYSTEMB;ACCESS=R,W,L,U;@.@.@ All users of SYSTEMB are now allowed unlimited access on our system. To verify what access has been granted, the LISTSEC command is used: S> LISTSEC @.@:SYSTEMB ---------USERSETS--------@.
Chapter 6 GROUP The GROUP command changes the current default group name. When the security subsystem is entered, the default group is the user’s log on group. Subsequent GROUP commands change the default group name. The default group set by GROUP is used by the ALLOW and REMOVE commands when the group is not explicitly stated. Syntax S> GROUP= {@ } {groupname} Parameters Parameter Description groupname The default group name.
Network File Access LISTSEC The LISTSEC command displays all file sets and access that has been granted to a particular user set. This command can also be used to show the type of access a user has to a specific file. The maximum number of entries that LISTSEC will display is 400. Syntax S> LISTSEC [userset] Parameters Parameter Description userset A valid user or user set. If not specified, this command will list all users or user sets. It must be in the one of the following forms.
Chapter 6 NODE This command sets the default node. The default node is either the first node on the list after the node you are on, or a node you have previously specified with the NODE command. Syntax S> NODE={@ } {node} Parameters Parameter Description node The new default node. This may be expressed by name or number.
Network File Access REMOVE Removes files from NetBase's security records. The entire security record is deleted only if all files and filesets have been removed. This command requires SYSTEM MANAGER (SM) capability. Syntax S> REMOVE userset [;fileset [,fileset...]] Parameters Parameter Description userset The userset that is to have files removed. It must be in the one of the following forms: user.account:node @.account:node @.@:node @.@:@ fileset The fileset for which access is to be removed.
C H A P T E R 7 NetBase Spooling NetBase Spooling makes sending your programs’output to any spooled printer anywhere in your HP 3000 network both simple and practical. It provides you with several transparent methods of defining the printing environment and performs the task with a minimal amount of overhead.
Chapter 7 Spooling Overview Since NetBase spooling is positioned between the application and file system, it sends reports directly to the destination computer. This removes the need for a local copy and also eliminates unnecessary disk IOs. The result is a simpler, more efficient method of sharing remote spooled devices.
NetBase Spooling Remote Spooling Remote spooling is a feature of NetBase that allows you to run a program on system A, and create the resulting spool files (other than $STDLISTs) on system B. DEVICE records define the LDEV numbers or device classes of remote printers. Spooled devices can be made available to the network using NetBase's directory. The directory is used to identify and locate devices within the network. This command requires SM and NM capability.
Chapter 7 Disaster Tolerance You may want to create a local copy as well as a remote copy. If this is the case, NetBase spooling allows you to create either a permanent or temporary local copy. The COPY option directs NetBase to create a permanent local copy. If a network failure occurs while a process is outputting to a remote spooler that is defined with the COPY option, NetBase allows the process to continue using just the local spool copy.
NetBase Spooling The TEMP parameter is designed for this issue. When the network is up, NetBase creates a temporary copy on the local system as it creates a permanent one on the remote system. When the remote copy is completely created, the temporary version on the local system is purged. However, if the network fails during the creation or if the network is down during the creation (while the program runs), the local copy is kept.
Chapter 7 Setting Up Remote Spooling In order to use remote spooling, each system must be configured to import/export spool files. For more configuration information, turn to Chapter 3 “Using CONFIG”. To set up: 1. To verify that the nodes are configured: : HELLO MGR.NETBASE : RUN NBCTRL.PUB.NETBASE ∗> CONFIG C> LIST NODES Node Sys name Line Type 8∗ DAFFY N 10 NORWAY N 12 DEVELOP N 2. Startup A A A Spool N B B Shadow B B B Add directory entries for remote devices via NBDIR.
NetBase Spooling Configuring Remote Spooling Below are the additional SPOOL parameters associated with NetBase Spooling. The default values are usually sufficient. For a full description of each parameter, turn to Chapter 3 “Using CONFIG”. C> l spool SPOOL SPOOL SPOOL SPOOL SPOOL SPOOL SPOOL SPOOL SPOOL SPOOL SPOOL SPOOL SPOOL - Remote Transfer Timeout.... Transfer Server Allocation. Maximum Block (bytes)...... Maximum Files per Node..... Use S' and J' on incoming.. Change jsname to node name.
Chapter 7 Using Pseudo Devices with Remote Spooling In the previous example in the “Remote Spooling” section, we assumed that the local device referenced was an actual device class on the local system. With NetBase remote spooling, the local device or device class does not have to exist. Remote spooling supports the use of pseudo devices. For example, we want all the spool files created on a device with the user’s name to be created on the remote system: :RUN NBDIR.PUB.
NetBase Spooling Let us further assume that the local systems EENEY, MENEY or MINEY do not have any printers. In this case, we will need an NBSpool background job to move any $STDLISTs created on the systems to MOE. Also, we need the NBSpool background job to pick up any spool files which were created locally while the network was down, and move them to MOE where they can print.
Chapter 7 NBSpool Program NBSpool streamlines and automates the management of spool files generated by all applications, seamlessly distributing the printing function across networks and printer devices. Originally written to provide a method of moving spool files across a network, NBSpool quickly grew into a powerful, easy-to-use facility for performing a large variety of functions on spool files.
NetBase Spooling • LPR/LPD support which enables you to send and receive print jobs to and from remote hosts, whether they are on HP 9000s, Sun Sparc stations or any other UNIX environment. • support which can make your HP 3000 the BOOTP server for printers that require an IP address before they can be accessed by NBSpool. This eliminates the need for a UNIX system to perform the task.
Chapter 7 • A TIMEOUT= parameter for the MOVE and COPY commands which allows you to override the default time-out values. • The SPOOLACKFREQ JCW available with the MOVE and COPY commands controls how many blocks of spool file data are sent before waiting for a response from a remote computer. The larger the value, the faster the transfer. • A STORE and RESTORE capability for off-line storage. These commands are faster than SPOOK and use less tape. Also, multiple STOREs can be appended to the same tape.
C H A P T E R 8 AutoRPM AutoRPM is NetBase's interface to Hewlett-Packard's Remote Process Management (RPM). Remote Process Management is a feature of HP's Network Services. It provides the ability to run an interactive program on a remote computer.
Chapter 8 AutoRPM Overview To run a program on a remote machine using HP's RPM, the user must perform a series of steps. First, the DSLINE command is issued to open a line to the remote computer. Then, the user must issue a REMOTE LOGON, and then finally a REMOTE RUN to run the program. NetBase makes all this transparent to the user. By entering some information in NetBase's directory, the user can run the program, and NetBase will automatically run the program on the remote computer.
AutoRPM Defining a Program for AutoRPM As with other services in NetBase, definitions for remote programs are entered in NetBase's directory using the directory maintenance program NBDIR. On the local computer, NetBase needs to know where the remote program exists and how to run it. It also needs to know how to logon to the remote system on behalf of the local user in order to create the remote process. Therefore, you must enter PROGRAM and LOGON entries in NBDIR.
Chapter 8 For example, to setup HPMAIL to run on a remote machine: 1. Run NBDIR on the local machine. Enter a PROGRAM record for HPMAIL specifying the node where the remote program resides (on SYSB): PROGRAM HPMAIL.HPMAIL.SYS,SYSB;LIB=G;PARM=1 2. Enter a LOGON record for the users that will be running HPMAIL: LOGON @.@:SYSB=REMOTEU,MGR.MAIL,PUB 3. Copy the stub program NBNULL.LIB.NETBASE to the same file name as the local program: :FCOPY FROM=NBNULL.LIB.NETBASE;TO=HPMAIL.HPMAIL.
AutoRPM Notes on Implementing AutoRPM In some cases, you may want users requesting one program locally to actually run another program remotely. NetBase allows you to do this via the renaming option in the PROGRAM entry. For example, if your users try to run EDITOR.PUB.PROD locally, and you want them to run QUAD.LIB.NETBASE on a remote node, you would enter the following PROGRAM entry: D> PROGRAM EDITOR.PUB.PROD=QUAD.LIB.
Chapter 8 AutoRPM Options The PROGRAM directory command provides a number of options that affect the way remote programs are run: 8-6 Option Description LIB= The load library to be used when the process is created on the remote node. A value of D prevents default LIB=P. PARM= The parameter string to be used in the run command for the program on the remote node. XL= The name of a user defined XL list entered in the directory with the XL command.
C H A P T E R 9 NetBase Statistics NetBase Statistics provides a method for capturing file access and timing information, and process overhead measurements. NetBase also provides reports that clearly illustrate the captured information. Since NetBase is positioned between the application program and the file system, collecting statistical data regarding file access is a byproduct of running applications through NetBase.
Chapter 9 Collecting Statistics Starting, stopping, and inquiring about the statistics process is accomplished using NBCTRL. With statistics enabled, NetBase’s shell procedures accumulate I/O intrinsic counts and timings in an extra data segment assigned to each user process. These timings are posted to disk as the files are closed or the process terminates. The actual posting to the statistics log file is performed by NetBase's statistics logging process (NBSTATLG) running under NBCOP.
NetBase Statistics The STATS STOP command prevents any new processes from collecting statistics. Processes currently running will continue to have statistics collected. Specifying one of the collection parameters can be used to stop collecting a specific type of statistics. *> STATS STOP *> It should be noted that issuing a STATS STOP command does not stop NBSTATLG, nor does it close the current log file. Once NBSTATLG is active, it can only be killed by stopping or aborting NetBase.
Chapter 9 Reporting Statistics The standard NetBase reports provide the technical staff with a great deal of useful information. They aid in network design/management, network and application tuning, and they can be used to monitor computer and user response time. The following is a brief description of these reports: Report Name Description NBLGDUMP NetBase Log Listing Utility. This program formats individual statistics log records. Selection by program file and/or data file is provided.
NetBase Statistics Program Input The following table provides descriptions of the program input. Input Description Enter Log file name The file name of a valid NetBase Statistics log file. No default is allowed. It cannot be the current log file. Do a STATS SWITCH to run against current log file. Enter PROGRAM name The fully-qualified file name of the desired program subset. The default is all programs. Enter FILE name The fully-qualified file name of the desired data file or database subset.
Chapter 9 The heading information is straightforward. The node that the program was run on is listed after the USER: information. The node that the file lives on is listed after the FILE: information. If the program node does not match the file node, the file is designated as a REMOTE FILE. One detail line is given for each intrinsic called by the process for each file. Average timings are computed for each intrinsic. The percentages refer to the relative percentages of access broken down by intrinsic.
NetBase Statistics Running NBRPT01 NBRPT01 is a network statistical analysis. This report was designed to aid in the determination of program and data file location inside the network. It clearly shows the source and volume of all file related activity by programs running through NetBase. NBRPT01 can be run either from a job or a session. The program normally outputs to the spool file NBREPORT, but file equations are allowed. Note. A current log file cannot be specified.
Chapter 9 Program Input The following table provides descriptions of the NBRPT01 reduction options. Reduction Option Description Enter Option The number corresponding to the desired reduction option. 1 reads through statistic log files to compile the data. 2 uses a reduction file created from a previous run of NBRPT01 or NBRPT02. Enter first Stat log # The number of the first log file to be extracted. Applies only when option 1 is selected.
NetBase Statistics Program Output The following table provides definitions of the terms used in the NBRPT01 report. Term Description OPENS The total number of times that this file was opened by this program. READS Count The total number of read type intrinsics issued against this file by this program. Read type intrinsics are considered to be DBFIND, DBGET, FREAD, FREADBYKEY, FREADLABEL, FREADSEEK, FREADC, FFINDBYKEY and FFINDN.
Chapter 9 Running NBRPT02 NBRPT02 is a program activity summary. This report was designed to identify the amount of processing a program devotes to accessing each file. This quantity is expressed as a percentage of total CPU used. NBRPT02 can be run either from a job or a session. The program normally outputs to the spool file NBREPORT but file equations are allowed. :RUN NBRPT02.PUB.NETBASE NetBase Statistics Reporting 1991 Reduction Options: 1) Extract from log files 2) Use existing reduction [v.u.
NetBase Statistics Program Input The following table provides descriptions of the NBRPT02 reduction options. Reduction Option Description Enter Option The number corresponding to the desired reduction option. 1 reads through statistic log files to compile the data. 2 uses a reduction file created from a previous run of NBRPT01 or NBRPT02. Enter first Stat log # The number of the first log file to be extracted. Applies only if option 1 is selected.
Chapter 9 Program Output The following table provides definitions of the terms used in the NBRPT02 report. Term Description OPENS The total number of times that this file was opened by this program. AVG ACCESS TIMES Wall The average amount of elapsed time in msec that it took to complete all calls against this file. This is computed: Total Wall time/Count CPU The average amount of CPU time in msec that it took to process all calls against this file.
NetBase Statistics Generating Scenarios Any network strategy can be modeled using statistics gathered from the current environment, standard NetBase reports and the scenario generator NBLGTRAN. The statistics provide the file and program activity. The reports display the information, and the scenario generator transforms the statistics to reflect the desired configuration. NBLGTRAN creates new statistic log files from existing files, editing the file as it is being processed.
Chapter 9 Running NBLGTRAN may be run either as a job or session. Since log files may span several files, the RANGE alternate entry point allows several consecutive log files to combine into one transformed log file. The following sample shows the processing of one log file. NBLGTRAN :RUN NBLGTRAN.PUB.NETBASE NetBase Log file Translator [v.u.f] Update n Copyright QUEST Software 1990 SCENARIO FILE.... CEI01.
NetBase Statistics If a range of log files is to be translated, the RANGE entry point should be used. This reduces the effort to process the logs and consolidates the scenario output into one log file. The following example illustrates this. :RUN NBLGTRAN.PUB.NETBASE,RANGE NetBase Log file Translator [v.u.f] (C) QUEST Software 1987 SCENARIO FILE.... CEI01.
Chapter 9 Scenario File Format The scenario file command records are prefixed with a two character code indicating the action that is to take place. The delimiter used in all records is the slash (/). Specifying file and program names is accomplished using the MPE file set format complete with wild card characters. The file and program names must be fully qualified. The order in which the command records are entered is important. NBLGTRAN first excludes files and programs.
NetBase Statistics Consolidating Records You can consolidate records by renaming a program or file, or a group of programs or files, to one file. This is very useful in improving the readability of the statistic reports. If a file or program name matches the target file name, NBLGTRAN substitutes the new file name in lieu of the actual file name. The CF command changes the file name, while the CP command changes the program name. See the following syntax for CF and CP.
Chapter 9 Similarly, to exclude the program FIXIT, use the following scenario command: EP/FIXIT.PROG.MFG/ Moving Records You can change the node number associated with the file or program to the node specified. The move command allows modeling of different scenarios by moving processes and files to other computers. If a file or program name matches the target file name, NBLGTRAN changes the associated node to that specified by new node number.
C H A P T E R 1 0 NetBase and Third Party Products This chapter documents the relationship of NetBase to other third party products that may be installed on your system. In This Chapter • ADAGER • DBGENERAL • OMNIDEX • NetBase MPEX Interface If you have any questions regarding NetBase and third party products, please contact Technical Support at 714-720-1434.
Chapter 10 NetBase ADAGER Interface This interface is used in shadowing environments and allows for ADAGER database changes that are performed on the master system to be automatically sent to the shadow system and be performed on the shadow copy of the data. In order to use the NetBase ADAGER Interface, a special command file, ADAGER.PUB.NETBASE, must be used to create an ADAGER job to perform the structural changes. All commands input into this are put into a job stream.
NetBase and Third Party Products To use ADAGER: 1. Execute the command file, ADAGER.PUB.NETBASE. This will run ADAGER.PUB.REGO, which will prompt for the name of the job stream, the database name, and changes to be made. When this step is completed, the job stream will have been created. 2. Stream the job created in Step 1. This will execute the ADAGER changes and once it has completed successfully, NBADAGER will send the changes to the shadow system.
Chapter 10 NetBase DBGENERAL Interface This interface is used in shadowing environments and allows for DBGENERAL database changes that are performed on the master system to be automatically sent to the shadow system and be performed on the shadow copy of the data. When DBGENERAL is run, the input is captured and applied to the master system. Once DBGENERAL has successfully completed the changes on the master system, NBGENERAL writes all of the DBGENERAL commands into the shadow transport file, NBM.IPC.
NetBase and Third Party Products NetBase OMNIDEX Interface This section documents how NetBase and OMNIDEX 3.x work for both NFA and for shadowing. NFA Requirements If using OMNIDEX 3.x or later and NetBase for remote file access, the NetBase OMNIDEX interface must be installed. Installation Requirements • NBINST.PUB.NETBASE;INFO=“INSTALL OMNIDEX” • :NBDIR.PUB.NETBASE D> XL OMNIDEX=XLOMNIDX.PUB.
Chapter 10 Special Installation Steps for Shadowing • If using OMNIDEX 3.x and NetBase in a shadowing environment, there are no special installation steps to be performed by default. • If the customer does not own NFA and is using TPI, then nothing needs to be done on the shadow system as far as NetBase is concerned. If the customer wants the shadow copy to be indexed, then they would set it up via DBUTIL, and OMNIDEX and TPI will automatically maintain the indexes.
NetBase and Third Party Products NetBase MPEX Interface This section documents the NetBase/MPEX integration command files, intended to allow VESOFT's MPEX to be safely used in a NetBase environment. The following MPEX commands are intercepted by the NetBase/MPEX interface: %ALTFILE %BUILD %COPY %PURGE %RENAME %SAVE %YESPURGE When any of the above commands are used, the NetBase/MPEX interface will intercept and execute the command, instead of the normal MPEX command file.
C H A P T E R 1 1 System Operations and Maintenance With NetBase installed on your system, many of your operational procedures must change. In this chapter, you will find recommended and required changes with steps to follow.
Chapter 11 System Startup The system startup procedures need to change to include the starting of NetBase prior to any jobs or users logging on. The following changes are recommended. Action Enter Explanation 1. Start the network :NETCONTROL START;NET=LAN1* NetBase requires the network to be running prior to its starting. :NETCONTROL START;NET=LOOP :NSCONTROL START * Substitute in your actual network name 2. Enable NetBase :RUN NBVERS.PUB.
System Operations and Maintenance System Shutdown The system shutdown procedures need to change to include the stopping of NetBase prior to shutting down the system. The following changes are recommended. Action Enter Explanation 1. Stop NetBase :RUN NBCTRL.PUB.NETBASE;INFO="STOP NETBASE" To stop the NetBase job gracefully, allowing all processes - shadowing, NFA, AutoRPM... to cease without adversely affecting the data.
Chapter 11 Partial Backup If you are shadowing, you can change your partial backups to take place on the shadow system. If you have remote users accessing local data to be stored, your backup procedure will change as well. Below is the process we recommend for partial backups. Action Enter Explanation Flush the pipeline (optional) :RUN NBFLUSH.PUB.NETBASE,STOPWAIT;PARM=s hadownode This step is optional.
System Operations and Maintenance Full Backup For a full backup to include NetBase, you will need to stop the NetBase job. Action Enter Explanation Flush the pipeline (optional) :RUN NBFLUSH.PUB.NETBASE,STOPWAIT;PARM= shadownode This step applies to shadowing environments only, and it is optional for those. If performed, it will force all updates in the shadowing pipeline to post to the shadow files, giving you a sync point at which time both the master and shadow data matches.
Chapter 11 HP Patches Having NetBase installed into your system SL and XL affects HP patch procedures. If you are applying a Power Patch or an Image patch, the patch will expect the Image intrinsics to be where HP put them, as opposed to where NetBase renamed them, when installing the shell. To handle this: Action Enter Explanation Flush the pipeline (optional) :RUN NBFLUSH.PUB.NETBASE,STOPWAIT;PARM= shadownode This step applies to shadowing environments only, and it is optional for those.
System Operations and Maintenance FOS Upgrades When you replace the operating system, you must re-install NetBase. Action Enter Explanation Flush the pipeline (optional) :RUN NBFLUSH.PUB.NETBASE,STOPWAIT;PARM= shadownode This step applies to shadowing environments only, and it is optional for those. If performed, it will force all updates in the shadowing pipeline to post to the shadow files, giving you a sync point at which time both the master and shadow data matches.
Chapter 11 NetBase Updates To update your version of NetBase, you will need to follow the instructions with the tape. In general, you will: Action Enter Explanation Flush the pipeline :RUN NBFLUSH.PUB.NETBASE,STOPWAIT;PARM=s hadownode This step is required for shadowing environments. It will force all updates in the shadowing pipeline to post to the shadow files, eliminating records from queue files which may change size or structure with the update. (on the master node) Stop NetBase :RUN NBCTRL.
System Operations and Maintenance Removing NetBase To remove NetBase completely from the system, follow the instructions below: Action Enter Explanation Flush the pipeline :RUN NBFLUSH.PUB.NETBASE,STOPWAIT;PARM= shadownode This step is required for shadowing environments. It will force all updates in the shadowing pipeline to post to the shadow files, eliminating records from queue files which may change size or structure with the update. (on the master node) Stop NetBase :RUN NBCTRL.PUB.
C H A P T E R 1 2 Disaster Recovery Procedures for NetBase Shadowing Environments This chapter serves as a guideline for NetBase failover procedures. It covers three scenarios in a shadowing environment. It addresses both planned and unplanned failovers in each scenario. This document does not include site specific procedures that may need to be performed. In This Chapter • Case One: Master system fails and the shadow system becomes the master system with shadowing in the reverse direction.
Chapter 12 Case One The Case One scenario assumes that the master system fails and the shadow system becomes the master system, with shadowing in the reverse direction. Planned Failover The following guidelines can be used for a planned failover. An example of a planned failover would be hardware maintenance. On the master system: 1. Quiet the system (except for the NetBase background job). 2. Flush all transactions to the shadow system: RUN NBFLUSH.PUB.NETBASE,STOPWAIT;PARM=ShadowNode# 3.
Disaster Recovery Procedures for NetBase Shadowing Environments RUN NBCTRL.PUB.NETBASE;INFO=“CHGDIR newdir” 8. Stop and start the NetBase background job: RUN NBCTRL.PUB.NETBASE;INFO=“STOP NETBASE” RUN NBCTRL.PUB.NETBASE;INFO=“START NETBASE” 9. Let users on to the new “master” system. When it is time to switch back to the original master/shadow configuration, the above steps for a planned failover would be followed again.
Chapter 12 Unplanned Failover The following guidelines can be used for an unplanned failover. This scenario assumes that the master will become the shadow system and the shadow will become the master. This scenario also assumes that the master system is “dead” or unavailable. On the shadow system: 1. Quiet the system (except for the NetBase background job). 2. Check to make sure all shadow transactions have been posted: RUN NBCTRL.PUB.NETBASE;INFO=“SHOW POST” 3.
Disaster Recovery Procedures for NetBase Shadowing Environments When the old master system is available, it must be brought up to think that it is a shadow system. Follow the steps below for restarting the failed system as a “shadow” system. On the OLD master system: 1. Do not start the NetBase background job at system startup. 2. Check the NBM.IPC file and make sure it is empty. If it is not empty, it must be purged and rebuilt: PURGE NBM.IPC.NETBASE BUILD NBM.IPC.NETBASE;REC=8187;MSG;DISC=31000,32 3.
Chapter 12 When the posting process has completed all transactions and it is time to switch back to the original master/shadow configuration, you can perform the steps in a planned failover. Case Two The Case Two scenario assumes that the master system fails and the shadow system is available for READ only access. By default, shadow data is available for READ only access.
Disaster Recovery Procedures for NetBase Shadowing Environments Case Three The Case Three scenario assumes that the master system fails and the shadow system is set up to operate in a “standalone” environment. No shadowing will be done during this failover. Planned Failover The following guidelines can be used for a planned failover. On the master system: 1. Quiet the system (except for the NetBase background job). 2. Flush all transactions to the shadow system. RUN NBFLUSH.PUB.
Chapter 12 7. Stop and start the NetBase background job: RUN NBCTRL.PUB.NETBASE;INFO=“STOP NETBASE” RUN NBCTRL.PUB.NETBASE;INFO=“START NETBASE” 8. Let users on to the new “standalone” system. Unplanned Failover The following guidelines can be used for a unplanned failover. This scenario assumes that the shadow system will no longer be a shadow system and it will operate in a “standalone” environment. On the shadow system: 1. Quiet the system (except for the NetBase background job). 2.
Disaster Recovery Procedures for NetBase Shadowing Environments Whether a planned or unplanned failover is used in this scenario, at some point it will be necessary to get back to the original configuration. When it is time to go back to the original configuration of master and shadow, there are several different ways that this can be done. One method would be to make a store tape of the standalone system, and then restore it on to the original master and switch back to the original directories.
Chapter 12 Creating Alternate Directories with NBDIR.PUB.NETBASE In order to implement multiple scenarios with NetBase, it requires the use of alternate directories. These directories should be prebuilt whenever possible. Below are the steps outlining how to take a current NetBase directory that defines shadowing for a master system and create a directory for the master system that now defines it as the shadow system. Unload the current NetBase directory using NBDIR.
Disaster Recovery Procedures for NetBase Shadowing Environments The next step is to edit the above file and change the necessary directory entries for the system to think it is the shadow system. In the above example, two lines need to be changed: DIR NBD.DATA.NETBASE File Banner.Data.NetBase,Daffy,Bugs The DIR command needs to be changed to a BUILD command so that we will create a new directory. We do not want to modify the existing directory.
C H A P T E R 1 3 NetBase Utilities A number of utilities are provided with NetBase. Some utilities, such as NBVERS, are used to support the NetBase installation and address specific operational needs. Others are generic utilities that have been Quest contributions to the INTEREX CSL. In This Chapter • NBVERS • NBLOG • NBTRACE • QUARK Two additional utilities are described in this chapter. These two utilities must be purchased separately. The utilities listed above come with the NetBase product.
Chapter 13 NBVERS The NBVERS utility is used to check the versions of the various NetBase programs and segments that have been installed on the system. When NetBase is globally installed, it is used to control the enabling and disabling of the interception of compatibility mode programs. The syntax for running NBVERS is as follows: :RUN NBVERS.PUB.
NetBase Utilities For example, to check the versions of the NetBase programs: :RUN NBVERS.PUB.NETBASE,PROG NetBase Version Display Program Program Program Program Program Program Program Program Program Program Program Program Program Program Program Program Program Program Program Program Program Program Program Program File: File: File: File: File: File: File: File: File: File: File: File: File: File: File: File: File: File: File: File: File: File: File: File: [x.x] Update n NBCOP.PUB.NETBASE NBCTRL.
Chapter 13 To intercept all subsequent CM programs (ones that are not currently running): :RUN NBVERS.PUB.NETBASE,ENABLE To dynamically disable NetBase from new CM processes enter: :RUN NBVERS.PUB.NETBASE,DISABLE To check to see if NetBase is enabled or disabled: :RUN NBVERS.PUB.NETBASE,STATE Note. System Manager (SM) capability is required to run NBVERS for the listing of program versions (RUN NBVERS or RUN NBVERS,PROG). Operator (OP) capability is required to run NBVERS,ENABLE or NBVERS,DISABLE.
NetBase Utilities NBLOG displays the status and error messages NetBase reported to the $STDLIST and the console for the time period specified. You can also use NBLOG with an alternate entry point to display a history of all changes made in the NBDIR, NBCTRL, CONFIG and NBVERS programs for the time period specified. NBLOG When the NetBase background job starts, the NBLOG.DATA.NETBASE file is copied to NBLOGBK, and the previous NBLOGBK file is purged. NBLOG.DATA.
Chapter 13 To see all changes to NBDIR, NBCTRL, CONFIG and NBVERS: :RUN NBLOG.PUB.NETBASE,LOD NetBase Log Dump Facility [x.x] (C) QUEST Software 1987 Enter Start Date for all: 08/15/94 08/15/96 10:26:35.3 Ctl #S1134 PHIL,MGR.NETBASE Pin 66 STOP NETBASE Dev 35 08/15/96 10:30:46.5 Ver #S1134 NetBase Access DISABLED RICK,MGR.NETBASE Pin 65 Dev 35 08/15/96 10:53:11.3 Cfg #S1134 M 2 BIFF,MGR.NETBASE Pin 115 Dev 35 08/15/96 10:53:18.2 Cfg #S1134 BIFF,MGR.NETBASE SHADOW - Direction (N/E/I/B).....
NetBase Utilities To see the changes in NBCTRL only: :RUN NBLOG.PUB.NETBASE,LOD;PARM=2 NetBase Log Dump Facility [0.9.6] (C) QUEST Software 1987 Enter Start Date for all: 08/15/94 08/15/96 10:21:28.8 Ctl #S1134 RICK,MGR.NETBASE Pin 69 START POST 9 Dev 35 08/15/96 10:26:35.3 Ctl #S1134 STOP POST RICK,MGR.NETBASE Pin 66 Dev 35 08/15/96 10:36:50.6 Ctl #S1134 START POST 9 RICK,MGR.NETBASE Pin 136 Dev 35 08/15/96 10:47:37.2 Ctl #S1134 ABORT NETBASE RICK,MGR.
Chapter 13 NBTRACE records an application’s activity from NetBase’s viewpoint. With NBTRACE you can see which calls are being intercepted by the NetBase shell, which ones are successful, and which ones fail. NBTRACE can help identify the exact file not found by identifying which FOPEN failed and what it was attempting to open. NBTRACE.PUB.NETBASE is enabled by setting a JCW for the session. It logs its results to NBATnnn.IPC.NETBASE files, where nnn is the process number.
NetBase Utilities 5. Use NBSpool to view your new spool file which contains the trace results. :RUN NBSPOOL.PUB.NETBASE O> T #* O> L |FOPEN| (or |DBOPEN|) This command (either FOPEN or DBOPEN) lists all the lines where a file open occurs. The following is an example of a trace of an inactive user process using the |DBOPEN| option. TRACE OF INACTIVE USER PROCESS STARTED WED, JAN 26, 1994 Prog: QUERY.PUB.SYS User: MGR.PUB.NETBASE 14:53:46.6 1001 BANNER.DATA.
Chapter 13 QUARK This program is an archiving program similar to the ones available for PCs. It takes a set of files and stores them in a compressed format in one file. A suggested use for QUARK is for copying files between boxes. :RUN QUARK.LIB.NETBASE;INFO="cmd archive [fileset ...
NetBase Utilities Additional Utilities NetBase now additionally offers the QUARK+ and NBCOPY utilities. Note. The NBCOPY and QUARK+ utilities must be purchased separately. QUARK+ QUARK+ is an enhanced version of the QUARK utility. It works like QUARK, but has additional functionality. The following example adds all files in the JOB group to the PURGEME.PUB.PROD quark file. :HELLO MGR.PROD,JOB :COPY PURGEME.LIB.NETBASE,PURGEME.PUB :RUN QUARK.LIB.NETBASE;INFO=“A PURGEME.PUB @.
Chapter 13 • Supports fileset-fileset-fileset-... like STORE/RESTORE. • Stores lockwords and :ALTSEC security information. Note: QUARK+ will not prompt for a lockword if you have SM or AM capability and it is in your account. • Allows redirection to various groups and accounts, like GROUP= and ACCT=. • Can unquark across accounts. If you unquark a database, a NONB record is required for QUARK.PUB.NETBASE. • Locks and compresses files open for lock access. • Supports files created by the older QUARK.
NetBase Utilities Also: Parameter Description D Delete files from archive R Replace files in archive L List archive contents Notes • The AQ option is 8-15 times faster than standard compression, but does not compress more than 88% of a file. • The XO feature requires version A.03.00 of QUARK+. Older archive files are compatible with this version, however, the time stamps will not work unless the archive was created with version A.03.00 or later. • A maximum of 20 filesets may be specified.
Chapter 13 Adding BANNER08.DATA.NETBASE... 89.3%, 31 msecs Adding BANNER09.DATA.NETBASE... 99.7%, 121 msecs 10 files, 0 failed, 97.9% saved END OF PROGRAM :LISTF SAMPLE,2 ACCOUNT= NETBASE FILENAME CODE SAMPLE 707 GROUP= PUB ------------LOGICAL RECORD----------SIZE TYP EOF LIMIT R/B 128W FB 30 30 ----SPACE---SECTORS #X MX 1 32 1 1 The XLO option tells QUARK+ to unarchive the files into the Local group and to preserve the Olddate information: :RUN QUARK.PUB;INFO="XLO SAMPLE.
NetBase Utilities NBCOPY enables you to copy files easily, making exact duplicates on the same or remote systems without the need for remote sessions. Since NBCOPY has been optimized to perform this one function, it copies files many times faster than HP’s FCOPY or DSCOPY. The NBCOPY utility is flexible in the types of files it handles, and it offers several options for modifying the new copy during the copying process. NBCOPY Note.
Chapter 13 NBCOPY Syntax The syntax for NBCOPY closely approximates the FCOPY syntax. As a result, it can be easily inserted into job streams and UDCs where it can replace FCOPY commands. The following table lists the NBCOPY parameters and what they do. Parameters Parameter Description FROM= Specifies the file to copy from (input file). If this parameter is not specified at all, the default FROM file is *QCINPUT. Note that this backreferences a file equation, not a file name.
NetBase Utilities Parameter Description TO= Specifies the file to which to copy (output file). If omitted, this parameter defaults to *QCOUTPUT. If specified without a file name, $STDLIST is assumed. If the specified file exists, it is erased unless a file equation is issued specifying ACC=OUTKEEP. Data sets are never erased. If the TO file does not exist, it will be built as a copy of the FROM file, with the same limit, extents and user labels.
Chapter 13 Parameter Description BF= Specifies the blocking factor of the TO file. If no value is specified, a blocking factor will be computed. If no TO file is specified, the FROM file will be rebuilt with the specified blocking factor. See the LIMIT parameter for more information on this feature. COPYBASE Copies an entire database. Database specifications do not need passwords and modes.
NetBase Utilities Parameter Description LIMIT= Specifies the file limit of the TO file. This assumes the TO file is a new file. If the TO file is not specified, the FROM file is copied to a temporary file of the same name, purged, and the temporary file is saved as the new FROM file. The net effect is to change the limit of the FROM file. For example, to change the limit of the file NAMES.DATA to 5000, you would enter: >FROM=NAMES.
Chapter 13 Running NBCOPY To start NBCOPY, run the program, NBCOPY.PUB.NETBASE. You will see the standard utility prompt, the greater than sign (>). One or more copy commands can be entered. Each command will be processed in turn unless NBCOPY is run from a job and an error is detected. In this case, all other commands are flushed. At the prompt, you must enter either a copy command, HELP, REDO, QUIT or EXIT. The HELP command displays a quick reference chart for command syntax.
NetBase Utilities Limitations In order to copy files as fast as it does, NBCOPY does not really pay too much attention to records. In most copy operations, NBCOPY copies blocks of records, not records. As a result, NBCOPY does not really work as well when copying to or from undefined record length files. In other words, if you simply want to dump a file to your terminal, or key in data to a disk file, use FCOPY instead. Variable files can be copied, but not to a fixed length file.
Chapter 13 Examples Copy the file HISTORY.DATA to the file BACKUP.DATA. In this example, BACKUP.DATA does not necessarily have to exist. If it does, it will be erased (EOF set to 0) before the copy begins. : RUN NBCOPY.PUB.NETBASE NBCOPY [x.x] (C) QUEST Software 1996 > FROM=HISTORY.DATA;TO=BACKUP.DATA {Statistics are printed at the end of the copy} > EXIT : Copy the KSAM file COPYLIB.SOURCE to the file COPYX. If COPYX does not exist, it will be built exactly like the data file for COPYLIB.
NetBase Utilities Extract every entry in the data set CUSTOMERS from the database AR and put it into the new file CUSTFILE. > FROM=AR,,5;FROMSET=CUSTOMERS;TO=CUSTFILE Put records in the file CUSTFILE into the data set OLD-CUSTS of the HIST database: > FROM=CUSTFILE;TO=HIST,,1;TOSET=OLD-CUSTS To reblock and expand the file BIGFILE. > FROM=BIGFILE;LIMIT=100000;BF= To expand the KSAM file NAMELOOK and ignore any duplicate keys.
A P P E N D I X A Installation/Update Procedures For NetBase Overview Typically, the installation and configuration of each system or the updating of software can be accomplished in less than 30 minutes. In general, the following steps comprise the installation/update process: 1. Restore the NetBase software from tape using NETACCT job. 2. Configure operational parameters and define all nodes in the network. Note that this step is required for initial implementation only.
Appendix A Before Installing NetBase Before installing NetBase, determine which of the following scenarios describes your system, and then take the action listed for that scenario. • If you are updating from a NetBase 9.6 global installation, proceed to the “Updating From NetBase 9.6 Global Install” section below. • If you are updating from a version of NetBase that is prior to 9.
Installation/Update Procedures for NetBase Installation Steps Once you have read the “Before Installing NetBase” section, take steps 1 through 4 to install NetBase. Notice that the “Before Starting” section in Step 1 describes two system scenarios with actions to take. Step 1. Restore NETACCT job and STREAM NETACCT To create NetBase's environment and install/update the software, you will restore a job into PUB.SYS.
Appendix A _____ 1.2 If necessary, add any required passwords to the NETACCT.PUB.SYS file. This job may stream additional jobs depending on your environment, so the job limit must allow for at least two NetBase jobs. To stream the job: :STREAM NETACCT <> This job will request the tape and print a message to the console when complete. If the job encounters any errors, a message telling what action is necessary will be displayed to the console. Note.
Installation/Update Procedures for NetBase Example We have two systems we want to configure for NetBase. We will assign node numbers 3 and 4 and use their network node names for the system name: Node # System Name 3 4 FOX VIXEN After the node numbers and names have been assigned, proceed to step 2.1 where a modify quick and add node commands must be performed. To do Step 2: _____ 2.1 Modify the parameters by entering the CONFIG subsystem in NBCTRL as follows: :HELLO MGR.NETBASE :RUN NBCTRL.PUB.
Appendix A _____ 2.2 Enter each system in the network into the configuration using the ADD [Node#] command. This includes the local system being configured. :HELLO MGR.NETBASE :RUN NBCTRL.PUB.NETBASE NetBase Control Program [v.u.f] Update n (C) QUEST Software 1987 *> CONFIG C> ADD 3 System Name........................ Startup Access (S/I/O/A/W)......... Node Name.......................... Node Connection Timeout............ SHADOW - Direction (N/E/I/B)....... SHADOW - Export queue size.........
Installation/Update Procedures for NetBase SHADOW SHADOW SHADOW SHADOW SHADOW SHADOW SHADOW SHADOW SHADOW SHADOW - Post Inactivity Timeout... Enable Post Logging....... Log all Post Transactions. Save Process Info on Post. Abort Post on Errors...... Buffered Exporting........ Transfer mode only........ Transfer Single Queues.... Transfer ACK Frequency.... Post Directory Filename...
Appendix A The following table lists the various installation options and when each is used. Install Option Usage INSTALL Most installations. INSTALL OMNIDEX Required if using OMNIDEX 3.0 and NetBase NFA. If using this option, there is an additional configuration step. Turn to Chapter 10 “NetBase and Third Party Products” for more information on the OMNIDEX/NetBase interface. INSTALL NOIMAGE Used when installing NBSpool Plus only (without NetBase).
Installation/Update Procedures for NetBase Step 4. Validate Installation and Modify System Startup Procedures Once the NetBase Shell has been installed, NetBase will begin to intercept all file system and IMAGE intrinsic calls. This happens automatically for Native Mode (NM) programs. However, for the NetBase Shell to be able to intercept Compatibility Mode (CM) programs, NetBase must be “enabled”. The “enabling” of NetBase for CM programs is done through the utility, NBVERS.PUB.NETBASE.
Appendix A The NetBase utility NBVERS can be used to verify the version of the NetBase shell procedures installed in the system SL (and XL). _____ 4.2 Verify the installation of the NetBase Shell :RUN NBVERS.PUB.NETBASE,SHELL NetBase Version Display SL SL SL SL XL XL XL XL _____ 4.3 Procedure: Procedure: Procedure: Procedure: Procedure: Procedure: Procedure: Procedure: [x.
Installation/Update Procedures for NetBase _____ 4.4 Set the NMCMDUDC to enable the capture of certain MPE commands such as BUILD, PURGE, RENAME etc. This is required if shadowing non-IMAGE files. Note. If the Quest NMCMDUDC was disabled for this update, you must set it again. Enter the following command: :SETCATALOG NMCMDUDC.PUB.
Appendix A Implementation Notes This section provides notes on system startup procedures and global installation. System Startup Procedures Once NetBase is installed and running, you should take steps to insure that it is always running when you expect it to be. We recommend modifying your SYSSTART file to automatically enable NetBase and launch your NetBase services when your system is brought up. Sample startup procedure: 1. Start the network 2. Enable NetBase for CM programs 3.
Installation/Update Procedures for NetBase The default NetBase directory already contains a number of NONB statements. They are automatically added any time a directory is built. To see what PROGRAM statements are already in the NetBase directory, use the LISTP @.@.@ command in NBDIR. Turn to Chapter 4 “NBDIR” for more information on the PROGRAM command. There is also a file called SLEXCLUD.DATA.NETBASE that can be used to prevent NBINST from adding certains segments into the RTMSL.PUB.SYS file.
Appendix A Installation Appendix This Appendix covers the following subjects: • Converting from an account installation to global installation. With the 9.7 release of NetBase, account installations are no longer supported. Before updating to 9.7 NetBase, the account installation must be removed. • Updating from a global installation of NetBase that is previous to the 9.6 Release. If you have any questions, or if you are unsure about any of the steps, please contact Technical Support at (714)-720-1434.
Installation/Update Procedures for NetBase Updating From Global Installation Prior to NetBase 9.6 Any release prior to 9.6 is unsupported and the NetBase Shell must be removed before updating to the 9.7 Release. _____ 1. Logon as MANAGER.SYS,PUB. _____ 2. Remove the NetBase Shell: :RUN NBVERS.PUB.NETBASE,DISABLE :RUN NBINST.PUB.NETBASE;INFO=”REMOVE” _____ 3. Reboot the system. _____ 4. Proceed to Step 1 of the “Installation Steps” section.
A P P E N D I X B Troubleshooting NetBase In this chapter, you will find questions with answers and tips from Quest technical support. Following these, you will find NetBase error messages listed with explanations and actions to take.
Appendix B Technical Support Tips This section lists commonly asked questions on the following topics, with answers and tips from Quest technical support: • SHOW POST • versions • NFA • NBSYNC,VERIFY • MPE builds, purges and renames.
Troubleshooting NetBase The error message in the background job indicates that a bad password has been defined and that queuing for this file has started. The password for a shadowed database is specified with the SHADOW command in NBDIR. Check the database passwords using DBUTIL and reissue the SHADOW statement with the correct password: :RUN NBDIR.PUB.NETBASE D> SHADOW PAYDB.DATA.
Appendix B NetBase Versions QUESTION: How do I tell what version of NetBase is installed on my system? ANSWER: The NBVERS utility can be used to determine the version of the NetBase Shell and the NetBase programs. To find the NetBase Shell version: :RUN NBVERS.PUB.NETBASE,SHELL To find the version of NetBase programs: :RUN NBVERS.PUB.NETBASE,PROG Sample :run nbvers.
Troubleshooting NetBase Program Program Program Program Program Program File: File: File: File: File: File: NBILOG.NB.NETBASE NBSYNC.PUB.NETBASE NBFLUSH.PUB.NETBASE NBSQLCTL.NB.NETBASE NBSQLEXP.NB.NETBASE NBSQLIMP.NB.NETBASE Version: Version: Version: Version: Version: Version: [0.9.7] Upd 00 [0.9.7] Upd 00 [0.9.7] Upd 00 NOT INSTALLED NOT INSTALLED NOT INSTALLED END OF PROGRAM BUGS: BUGS:RUN NBVERS.PUB.
Appendix B NFA QUESTION: Sometimes we seem to get what appears to be a database deadlock on our remote system. We use NetBase for Network File Access (NFA) from our System A to System B, where the database actually resides. When these deadlock situations arise, we look in DBUTIL and find the culprit to be NMSERVER.NB.NETBASE. How can we determine the user process for which the server is handling requests? ANSWER: There is an easy way to do this.
Troubleshooting NetBase The SHOW REMOTE command shows all users coming into this system for their file access. It also displays the PIN number of the associated server in the SPIN column. By matching the pin number from the DBUTIL command with the server pin (SPIN) number from the show remote command, you can identify the user process that is accessing the database. In this example, server pin 92 is associated to job number #S200 with a logon of USER.PROD. This user is running Query to access the database.
Appendix B NBSYNC, VERIFY QUESTION: Is there a program I can run to check the status of my shadowed files in NBDIR? ANSWER: Yes, a VERIFY entry point NBSYNC has been added to allow jobs and UDCs to check to see if a file is in the DISCARD, SYNC or QUEUE state. Run NBSYNC with the VERIFY entry point, specifying the file (or fileset) in the INFO string. A JCW named VERJCW will have the following values: :RUN NBSYNC.PUB.NETBASE,VERIFY;INFO="PAYDB.FILE.
Troubleshooting NetBase MPE Builds, Purges and Renames QUESTION: How can I use NetBase to intercept MPE commands such as BUILD, PURGE, SAVE, COPY and RENAME? ANSWER: You can invoke a UDC from a sample file provided by Quest Software. Essentially, each UDC runs NMCMD.PUB.NETBASE which passes your request to HPCICOMMAND. From this point, NetBase can intercept the command. We recommend the following sample UDCs: build anyparm parm1 xeq nmcmd.pub.
Appendix B NetBase Error Messages This section includes the following types of error messages: • File system • Directory file (NBD) • Network configuration file (NBI) • Network control file (NBN) • Shadowing queue file (NBM) • Statistics logging file (NBVL) • Spooling files (NBSEC and NBSED) Also included are errors that are detected by: • AutoRPM facility • NetBase control program (NBCOP) • Spooling processes • NBSERVER • NMSERVER • Shell Each error message has an explanation and
Troubleshooting NetBase File System Errors The following NetBase errors are returned to the user's program through the FCHECK intrinsic and the CONDITION WORD of all IMAGE calls. If the user's program calls FERRMSG, PRINTFILEINFO, DBERROR or DBEXPLAIN the new messages will automatically be displayed. ERR# Error Message Explanation/Action 1001 LOCAL NETBASE SERVICES ARE DOWN NetBase is not running on the local node.
Appendix B B-12 ERR# Error Message Explanation/Action 1010 INVALID OVERRIDE FLAGS SPECIFIED BY JCW Flags are set in the NBDISABLE JCW that are not used by NetBase. Check the JCW for invalid values. 1011 NO SERVERS AVAILABLE ON REMOTE NODE The number of users accessing files or databases on the remote node exceeds the maximum. The servers may be increased by modifying the NFA - Maximum Remote Users configuration parameter on the remote node.
Troubleshooting NetBase ERR# Error Message Explanation/Action 1026 SHADOWING INVALID WITH SPECIFIED ACCESS OPTIONS Shadowing is invalid for files opened with nowait I/O file access. 1027 USER LACKS CAPABILITY TO SHADOW FILE A user accessing a shadowed file must have both read and write access to the file. 1028 INSUFFICIENT STACK SPACE AVAILABLE Insufficient stack space for IMAGE call. Increase the maximum stack value on the user program.
Appendix B B-14 ERR# Error Message Explanation/Action 1041 GMULTI ACCESS WITHOUT LOCKING INVALID FOR SHADOWING The shadow file is being opened with GMULTI access but not allowing locking. This can be solved by adding ;SYNC to the file statement for the file in question. 1042 UPDATE ON SHADOW FILE INVALID WITHOUT LOCK The shadow file is not locked and the number of writers that have it open exceeds one. 1045 TPS CALLED WITHOUT NETBASE’S IMAGE INTERCEPT Check to make sure NetBase is enabled.
Troubleshooting NetBase ERR# Error Message Explanation/Action 1064 IPCNAME INTRINSIC FAILED This error indicates that a problem exists in the network transport. See the associated error message for the cause of the error. 1065 IPCRECVCN INTRINSIC FAILED This error indicates that a problem exists in the network transport. See the associated error message for the cause of the error. 1066 IPCCONTROL INTRINSIC FAILED This error indicates that a problem exists in the network transport.
Appendix B Directory File (NBD) Related Errors The following NetBase errors are related to the directory file (NBD). B-16 ERR# Error Message Explanation/Action 1100 CANNOT OPEN NETWORK DIRECTORY The directory file is invalid or does not exist. Check that the active directory exists and is valid. Also check for file equations. 1101 CANNOT READ NETWORK DIRECTORY The directory may be corrupt. Rebuild using the LIMIT command in NBDIR.
Troubleshooting NetBase Network Configuration File (NBI) Related Errors The following NetBase errors are related to the network configuration file (NBI). ERR# Error Message Explanation/Action 1120 CANNOT OPEN NETWORK CONFIGURATION FILE The NetBase configuration is corrupt and may require a restore. Contact Technical Support. 1121 CANNOT READ NETWORK CONFIGURATION FILE The NetBase configuration is corrupt and may require a restore. Contact Technical Support.
Appendix B Network Control File (NBN) Related Errors The following NetBase errors are related to the network control file (NBN). B-18 ERR# Error Message Explanation/Action 1141 CANNOT WRITE TO NETWORK CONTROL IPC FILE NetBase internal error. If this error occurs contact Quest Software. 1142 CANNOT CLOSE NETWORK CONTROL IPC FILE NetBase internal error. If this error occurs contact Quest Software. 1143 FFILEINFO ON NETWORK CONTROL IPC FILE FAILED NetBase internal error.
Troubleshooting NetBase Shadowing Queue file (NBM) Related Errors The following NetBase errors are related to the shadowing queue file (NBM). ERR# Error Message Explanation/Action 1170 CANNOT OPEN SHADOW EXPORT FILE The NetBase configuration is corrupt and may require a restore. Contact Quest. 1171 FCONTROL ON SHADOW EXPORT FILE FAILED NetBase internal error. If this error occurs contact Quest Software. 1172 CANNOT CLOSE SHADOW EXPORT FILE NetBase internal error.
Appendix B Statistics Logging File (NBVL) Related Errors The following NetBase errors are related to the statistics logging file (NBVL). B-20 ERR# Error Message Explanation/Action 1180 CANNOT OPEN STATISTICS LOGGING FILE The NetBase configuration is corrupt and may require a restore. 1181 FCONTROL ON STATISTICS LOGGING FILE FAILED NetBase internal error. If this error occurs contact Quest Software. 1182 FFILEINFO ON STATISTICS LOGGING FILE FAILED NetBase internal error.
Troubleshooting NetBase Spooling Files (NBSEC and NBSED) Related Errors The following NetBase errors are related to the spooling files (NBSEC, NBSED). ERR# Error Message Explanation/Action 1190 CANNOT OPEN SPOOLING CONTROL FILE The NetBase configuration is corrupt and may require a restore. 1191 CANNOT SET TIMEOUT ON SPOOLING CONTROL FILE NetBase internal error. If this error occurs contact Quest Software. 1192 CANNOT WRITE TO SPOOLING CONTROL FILE NetBase internal error.
Appendix B AutoRPM Facility Detected Errors The following NetBase errors are detected by the AutoRPM facility. ERR# Error Message Explanation/Action 1301 NOT ENOUGH STACK SPACE TO EXECUTE REMOTE PROCESS Insufficient stack space is available to create the remote process. Increase the MAXDATA for the local program. 1302 CANNOT EXECUTE REMOTE NETBASE PROCESS NetBase internal error. If this error occurs contact Quest Software. 1303 CANNOT EXECUTE LOCAL NETBASE PROCESS NetBase internal error.
Troubleshooting NetBase ERR# Error Message Explanation/Action 1312 SENDMAIL INTRINSIC FAILED NetBase internal error. If this error occurs contact QUEST Software. 1313 RECEIVEMAIL INTRINSIC FAILED NetBase internal error. If this error occurs contact Quest Software. 1314 UNSUCCESSFUL EXECUTION OF LOCAL STUB PROCESS NetBase internal error. If this error occurs contact Quest Software. 1315 USER NOT ALLOWED ACCESS TO SPECIFIED NODE Check the status of the specified node.
Appendix B B-24 ERR# Error Message Explanation/Action 1372 IPCCONTROL INTRINSIC FAILED ON CALL SOCKET This error indicates that a problem exists in the network transport. See the associated error message for the cause of the error. 1373 IPCRECVCN INTRINSIC FAILED This error indicates that a problem exists in the network transport. See the associated error message for the cause of the error.
Troubleshooting NetBase NetBase Control Program (NBCOP) Detected Errors The following NetBase errors are detected by the NetBase control program (NBCOP). ERR# Error Message Explanation/Action 2002 INVALID LOCAL NODE SPECIFIED IN REQUEST NetBase internal error. If this error occurs contact Quest Software. 2003 INVALID REMOTE NODE SPECIFIED IN REQUEST The PROGRAM entry in the directory specifies an invalid node number. Make sure the directory entry matches the configuration.
Appendix B Spooling Processes Detected Errors The following NetBase errors are detected by the spooling processes. ERR# Error Message Explanation/Action 3001 UNABLE TO CREATED SPOOLING DATA SEGMENT An attempt to get an extra data segment failed. 3002 INTERNAL ERROR IN SPOOLING EXPORT PROCESS NetBase internal error. If this error occurs contact Quest Software. 3003 WRITE ERROR ON REMOTE SPOOL FILE NetBase internal error. If this error occurs contact Quest Software.
Troubleshooting NetBase NBSERVER Detected Errors The following NetBase errors are detected by NBSERVER. ERR# Error Message Explanation/Action 5001 FILE RECORD SIZE EXCEEDS NETBASE MAXIMUM The requested remote file I/O is longer than the maximum expected by NetBase. 5002 TOO MANY REMOTE DATA BASES OPEN The number of remote databases opened by one user is greater than 512. 5003 UNKNOWN REQUEST DETECTED BY REMOTE NODE NetBase internal error. If this error occurs contact QUEST Software.
Appendix B NMSERVER Detected Errors The following NetBase errors are detected by NMSERVER. ERR# Error Message Explanation/Action 5001 FILE RECORD SIZE EXCEEDS NETBASE MAXIMUM The requested remote file I/O is longer than the maximum expected by NetBase. 5002 TOO MANY REMOTE DATA BASES OPEN The number of remote databases opened by one user is greater than 512. 5003 UNKNOWN REQUEST DETECTED BY REMOTE NODE NetBase internal error. If this error occurs contact Quest Software.
Troubleshooting NetBase ERR# Error Message Explanation/Action 5800 DATA RETURNED FROM USER PROCEDURE EXCEEDS RECEIVE LENGTH Remote procedure call returned a length greater than specified by remote NBRPC call. 5801 INVALID LENGTH FOR CACHING INFO, TOO MANY ITEMS The number of items in the cached data set is too great. The cache info would exceed the maximum send length.
Appendix B Shell Detected Errors The following NetBase errors are detected by the shell. ERR# Error Message Explanation/Action 8002 SHADOWING INVALID WITH SPECIFIED HPFOPEN OPTIONS Shadowing is invalid when used in conjunction with HPFOPEN options 18, 21 (mapped files), 45, 50 or 52. 8003 REMOTE ACCESS INVALID WITH SPECIFIED HPFOPEN OPTIONS Remote access is invalid when used in conjunction with HPFOPEN options 18, 21 (mapped files), 45, 50, 52 or 54.
Troubleshooting NetBase ERR# Error Message Explanation/Action 8015 RENAME OF SHADOWED FILE TO REMOTE FILE INVALID Cannot rename a shadowed file to a shadow copy or remote file. 8016 MULTIPLE TRANSACTION EXCEEDS MAXIMUM BASES For DBXBEGIN mode 3 or 4, the number of bases in the list is greater than 23. 8017 MULTIPLE TRANSACTION MULTIPLE TRANSACTION ALREADY STARTED A DBXBEGIN mode 3 or 4 was called while multiple transactions were in process.
Appendix B B-32 ERR# Error Message Explanation/Action 8207 SEND LENGTH PASSED TO NBRPC IS INVALID The send length passed to NBRPC is less than 0 or greater than 8192. Check and correct call to NBRPC. 8208 BOUNDS VIOLATION ON SEND BUFFER The send buffer passed to NBRPC has a bounds violation. Check and correct call to NBRPC. 8209 RECEIVE LENGTH PASSED TO NBRPC IS INVALID The receive length passed to NBRPC is less than 0 or greater than 8192. Check and correct call to NBRPC.
A P P E N D I X C Index A ABORT command, NBCTRL Examples............................................................2-9 Parameters CLIENT .........................................................2-8 EXPORT........................................................2-8 IMPORT node-id............................................2-8 NETBASE......................................................2-8 NODE node-id ...............................................2-8 SERVER server-id ....................................
Appendix C B Background job, NetBase Data transport/communication............................ 1-2 NBCOP.NB.NETBASE...................................... 1-2 NBLOG.DATA .................................................. 1-3 NBLOG.PUB.NETBASE ................................... 1-3 Starting.............................................................. 1-2 Backlog information, SHOW POST (NBCTRL).... 2-28 Backups Checkpoint, NBFLUSH.................................... 5-37 Full backup ..........................
Index SPOOL Allow incoming job streams ..................... 3-25 Direction .................................................. 3-25 Enable Export Flow Control ..................... 3-26 Startup Access.............................................. 3-24 System Name ............................................... 3-24 Operational parameters AUTORPM Use Local Logon ...................................... 3-23 DIR Allow File Equates................................... 3-15 Allow Wildcards .........................
Appendix C copyfilename parameter, SHADOW (NBDIR) ...... 4-53 Correcting load imbalance ........................................ iii CRITICAL parameter DISABLE (NBCTRL) ...................................... 2-16 ENABLE (NBCTRL) ....................................... 2-17 D Databases Copying entire.................................................13-18 Dataset shadowing ........................................... 5-51 Protection......................................................... 5-57 Resyncing .......
Index Disable NetBase services ....................................... 2-6, 4-46 NetBase using NBVERS................................... 13-3 NFA buffering .................................................. 4-47 DISABLE command, NBCTRL Examples.......................................................... 2-16 Parameters AUTORPM .................................................. 2-16 CRITICAL.................................................... 2-16 PENDLOCK.................................................
Appendix C Export on Startup parameter, CONFIG ................. 3-22 EXPORT parameter ABORT (NBCTRL) ........................................... 2-8 SHOW (NBCTRL)........................................... 2-26 START (NBCTRL) .......................................... 2-37 STOP (NBCTRL)............................................. 2-44 Export process, queues shadow updates.................. viii Export queue size parameter, CONFIG................. 3-26 Export Upshift Priority parameter, CONFIG .........
Index H header parameter EXPORTEXIT.................................................. 5-41 POSTUSEREXIT ............................................. 5-46 HELP facility, NBCTRL .........................................2-4 home-partition parameter, SQLOUT (NBDIR) ...... 4-58 I I/O intrinsic counts/timings, statistics......................9-2 IDLE status, SHOW POST (NBCTRL) ................. 2-28 ILOG [file] parameter START (NBCTRL) .......................................... 2-37 STOP (NBCTRL) ...............
Appendix C LISTF command, NBDIR Examples .................................................4-30, 4-33 Fields.......................................................4-28, 4-32 Parameters acct .............................................................. 4-32 ALL............................................................. 4-30 DSET........................................................... 4-30 fileset........................................................... 4-30 node........................................
Index Maximum Local Users parameter, CONFIG............3-8 Maximum Remote Users parameter, CONFIG ........3-8 MGR.NETBASE user password............................ 3-12 Minimizing network transactions ............................... v Minimizing spooling overhead .................................. iv MODE1 parameter, SHADOW (NBDIR) .............. 4-53 MODIFY command, CONFIG Examples.......................................................... 3-38 Parameters ALL ................................................
Appendix C LISTSQLI .................................................... 4-39 LISTSQLO................................................... 4-41 LISTX.......................................................... 4-43 LOGON....................................................... 4-44 PROGRAM ................................................. 4-46 REBUILD .................................................... 4-50 RESET ........................................................ 4-51 SHADOW...............................
Index NetBase Client Access for applications ........................................ xv Performance increases ......................................... xv NetBase directory .................... See Directory, NetBase NETBASE parameter ABORT (NBCTRL)............................................2-8 START (NBCTRL) .......................................... 2-37 STOP (NBCTRL) ............................................. 2-44 NetBase shell Avoiding application changes..............................
Appendix C P PARM= parameter, PROGRAM (NBDIR)............ 4-47 PART=part parameter SQLIN (NBDIR) .............................................. 4-57 SQLOUT (NBDIR) .......................................... 4-59 PART=partition parameter, SQLOUT (NBDIR).... 4-58 PASS parameter, LISTS (NBDIR) ........................ 4-37 PASS=password parameter, SHADOW (NBDIR) . 4-54 Password Account............................................................ 3-23 Case sensitivity ............................................
Index PARM=........................................................ 4-47 progname ..................................................... 4-47 remoteprog ................................................... 4-47 SHADOW .................................................... 4-48 TRACE ........................................................ 4-48 XL= ............................................................. 4-47 Syntax ..................................................... 4-46, 4-50 Prompts CONFIG.............
Appendix C SERVER command, NBCTRL Examples ......................................................... 2-21 Parameters ABORT ....................................................... 2-21 ALLOW....................................................... 2-21 Syntax.............................................................. 2-21 Server Initial Priority parameter, CONFIG.............. 3-9 Server LIB= load flag parameter, CONFIG .............
Index Setting up ......................................................... 5-16 SHADOW command......................................... 4-53 Shadow computer down ......................................viii Shadow system ...................................................5-4 Shadow transport................................................5-2 Shadowing TurboIMAGE log files .................... 5-53 SQLIN command .............................................. 4-56 SQLOUT command ................................
Appendix C Spooling, NetBase Backup copies ...................................................... xi Creating local copies ............................................ xi Defining SPOOL parameters ....................... 3-6, 7-7 LISTD command.............................................. 4-26 Multiple output lines............................................. x NBSpool program ............................................ 7-10 Option for network failure.................................... xi Overview .......
Index Statistics, NetBase Collecting statistics.............................................9-2 Consolidating records ....................................... 9-17 Defining STATS parameters ........................3-6, 9-2 Generating reports ..............................................xiii Generating scenarios......................................... 9-13 Minimal overhead incurred.................................xiii Modeling network strategies ...............................xiii Moving records............
Appendix C Third party shadowing NBTPSUTL program ....................................... 5-14 NetBase procedures.......................................... 5-14 TurboIMAGE databases ................................... 5-14 TRACE command, NBCTRL Examples ......................................................... 2-47 Parameters ....................................................... 2-46 Syntax.............................................................. 2-46 TRACE parameter, PROGRAM (NBDIR) ............
