900 Series HP 3000 Computer Systems ALLBASE/NET User's Guide ABCDE HP Part No. 36216-90031 Printed in U.S.A.
The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability or tness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for direct, indirect, special, incidental or consequential damages in connection with the furnishing or use of this material.
Printing History The following table lists the printings of this document, together with the respective release dates for each edition. The software version indicates the version of the software product at the time this document was issued. Many product releases do not require changes to the document. Therefore, do not expect a one-to-one correspondence between product releases and document editions.
ALLBASE/SQL Manuals Title Customer Order Number ALLBASE/NET User's Guide ALLBASE/SQL Advanced Application Programming Guide ALLBASE/SQL C Application Programming Guide ALLBASE/SQL COBOL Application Programming Guide ALLBASE/SQL Database Administration Guide ALLBASE/SQL FORTRAN Application Programming Guide ALLBASE/SQL Message Manual ALLBASE Pascal Application Programming Guide ALLBASE/SQL Performance and Monitoring Guidelines ALLBASE/SQL Reference Manual HP ALLBASE/QUERY User's Guide HP PC API User's Gui
Preface The ALLBASE/NET User's Guide describes ALLBASE/NET, a product that allows an application on one MPE/iX or HP-UX system to access an ALLBASE/SQL DBEnvironment on another MPE/iX system or HP-UX system. This manual is written for the system administrator who is using ALLBASE/NET on an MPE/iX system. He or she uses this guide to understand how ALLBASE/NET works and to learn how to use the NETUtil utility to maintain necessary les.
What's New in this Release The following table highlights the new or changed functionality in this release, and shows you where each feature is documented. New Features in ALLBASE/SQL Release G.0 Feature (Category) Description Documented in ... Stored procedures (Usability) Provides additional stored procedure functionality for application programs. Allows declaration of a procedure cursor and fetching of multiple rows within a procedure to applications. New statement: ADVANCE.
New Features in ALLBASE/SQL Release G.0 (continued) Feature (Category) Description Documented in ... New SQLGEN GENERATE parameters (Usability) Generates SQL statements necessary to recreate modi ed access plans for module sections. New syntax for GENERATE: DEFAULTSPACE, MODOPTINFO, PARTITION, PROCOPTINFO, SPACEAUTH. ALLBASE/SQL Database Administration Guide , \SQLGEN Commands" appendix.
New Features in ALLBASE/SQL Release G.0 (continued) Feature (Category) High Availability Description Provides a collection of features to keep systems available nonstop including: Partial STORE and RESTORE, Partial rollforward recovery, DBEFiles in di erent groups (MPE/iX), detaching and attaching database objects, CHECKPOINT host variable, changing log les, console messages logged to a le, generating fewer log records by using TRUNCATE TABLE to delete rows, and new system catalog information.
New Features in ALLBASE/SQL Release G.0 (continued) Feature (Category) New and changed SQLUtil commands for increased availability (High Availability) Description Documented in ... Adds support for high availability ALLBASE/SQL Database Administration Guide , \SQLUtil" appendix. and System Management Intrinsics. Intended for non-stop, continuously available operations. New SQLUtil commands: ATTACHFILE, CHANGELOG, DETACHFILE, RESTORE PARTIAL, STORE PARTIAL, STOREINFO, STOREONLINE PARTIAL, WRAPDBE.
New Features in ALLBASE/SQL Release G.0 (continued) Feature (Category) Description Documented in ... Optimizer enhancement (Performance) ALLBASE/SQL Performance and Uses a more e cient algorithm that signi cantly reduces the time Monitoring Guidelines , \Optimization" in \Basic Concepts in ALLBASE/SQL to generate the access plan. Performance." Access plan modi cation (Performance) Allows modi cation of access plans for stored section to optimize performance. View the plan with SYSTEM.SETOPTINFO.
New Features in ALLBASE/SQL Release G.0 (continued) Feature (Category) I/O performance improvement (Performance) Description Optimizes I/O for initial load, index build, serial scans, internal data restructuring, le activity, pseudo mapped les and temporary les. See the following features for new and changed syntax. Documented in ... ALLBASE/SQL Reference Manual , \SQL Statements." Deletes all rows in a speci ed table ALLBASE/SQL Reference Manual , TRUNCATE TRUNCATE TABLE in \SQL Statements.
New Features in ALLBASE/SQL Release G.0 (continued) Feature (Category) Description Documented in ... Modi ed SET options (Performance) Provides better performance for LOADs and UNLOADs. Specify bu er size, status reporting for LOAD/UNLOAD or exclusive lock for data table. AUTOSAVE row limit increased to 2147483647. New and changed SET options: LOAD BUFFER, LOAD ECHO, AUTOLOCK, AUTOSAVE. SQLMON (Tools) ALLBASE/SQL Performance and Monitors the activity of ALLBASE/SQL DBEnvironment.
New Features in ALLBASE/SQL Release G.0 (continued) ... Feature (Category) Description Documented in Increased memory for MPE/iX (HP-UX shared memory allocation is unchanged) (Performance) Increases memory up to 50,000 data bu er pages and 2,000 run time control block pages. Increases the limits signi cantly allowing allocation of enough data bu er pages to keep the entire DBEnvironment in memory if desired for performance.
Conventions UPPERCASE In a syntax statement, commands and keywords are shown in uppercase characters. The characters must be entered in the order shown; however, you can enter the characters in either uppercase or lowercase. For example: COMMAND can be entered as any of the following: command Command COMMAND It cannot, however, be entered as: comm italics comamnd In a syntax statement or an example, a word in italics represents a parameter or argument that you must replace with the actual value.
Conventions (continued) [ ... ] In a syntax statement, horizontal ellipses enclosed in brackets indicate that you can repeatedly select the element(s) that appear within the immediately preceding pair of brackets or braces. In the example below, you can select parameter zero or more times. Each instance of parameter must be preceded by a comma: [,parameter][...
Contents 1. Getting Started How ALLBASE/NET Works . . . . . . . . ALLBASE/NET Con gurations . . . . . . Hardware and Software Requirements . . . . The NETUtil Utility . . . . . . . . . . . The AliasDB and NETUsers Files . . . . . Creating the AliasDB and NETUsers Files . The Listener . . . . . . . . . . . . . . . Cross-System Connectivity . . . . . . . . . MPE/iX and HP-UX Syntax Di erences . . Client and Server Login Names . . . . . . ALLBASE/NET System Administrators .
Adding a User Pro le . . . . . . . . Changing a User Pro le . . . . . . . Deleting a User Pro le . . . . . . . . Displaying a User Pro le . . . . . . . Checking the Services File on the Server Examples of Setting Up ALLBASE/NET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14 2-15 2-16 2-16 2-17 2-18 3. Using ALLBASE/SQL Through ALLBASE/NET Using ALLBASE/ISQL . . . . . . . . . . . . . .
Figures 1-1. 1-2. 2-1. 3-1. Node as Client and Server . . . . . . . . . . System Administrators Using NETUtil . . . . Sample Pro les in AliasDB and NETUsers Files Connecting to a DBEnvironment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 1-4 2-18 3-6 . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Tables 4-1.
1 Getting Started ALLBASE/NET is a database access product that provides access to remote data as though it were stored locally. It allows the user of an application on one MPE/iX or HP-UX system to query and update a database in an ALLBASE/SQL DBEnvironment on another MPE/iX or HP-UX system. The remote DBEnvironment must reside on either a HP 3000 Series 900 or a HP 9000 Series 700/800. ALLBASE/SQL on the HP 3000 must be Version A.12.0, or later. ALLBASE/SQL on the HP 9000 must be Version A.03.
ALLBASE/NET gives users the same SQL functionality provided by the equivalent version of ALLBASE/SQL, with the following exceptions: DBEnvironments cannot be created remotely. New log les cannot be created remotely. Long column data types cannot be used remotely. The ALLBASE/SQL database administration utilities SQLUtil, SQLGEN, and SQLMigrate cannot access a remote DBEnvironment. How ALLBASE/NET Works ALLBASE/NET uses a client/server architecture.
ALLBASE/NET Configurations The client and server systems can be either an HP 3000 Series 900s running MPE/iX or an HP 9000 Series 700s/800s running HP-UX. For full client/server functionality on both HP-UX and MPE/iX platforms, ALLBASE/SQL must be installed on both the client and server systems. This con guration allows the user to create and maintain DBEnvironments and develop programs on the client as well as to access DBEnvironments on the server.
The NETUtil Utility ALLBASE/NET provides the NETUtil utility for creating and maintaining the AliasDB and NETUsers les that are discussed below. For complete descriptions of all the NETUtil commands, their syntax, and how they are used, refer to the \NETUtil Reference" chapter. The AliasDB and NETUsers Files For a user to connect to a remote DBEnvironment, two les must exist: the AliasDB le and the NETUsers le. The AliasDB le resides on the client.
Creating the AliasDB and NETUsers Files After ALLBASE/SQL has been installed on both the client and the server, the AliasDB and NETUsers les must be created using NETUtil. Adding the rst pro le to the AliasDB or NETUsers le automatically creates the respective le. These pro les allow speci ed users on the client to access particular DBEnvironments on the server. As system administrator on the client, you invoke NETUtil and use the ADD ALIAS command to add an alias pro le to the AliasDB le.
Cross-System Connectivity With ALLBASE/NET, dissimilar HP systems can be connected. This is called cross-system connectivity. The client and server can be any combination of HP 3000 Series 900s, or HP 9000 Series 700s/800s. However, the G.0 version of ALLBASE/SQL does not support the HP 9000 Series 300/400 as a server; it can be used as a client. If you are developing applications that do dynamic queries, do not assume that you know the format of fetched data.
One recommendation is to create an authorization group and add the server login name (DBEUserID) to the group. Be sure to grant all the desired authorizations to this group. Give the name of the group to the application users and developers on the remote client. Encourage them to use this group as the ownership quali er when accessing and creating SQL objects that they own.
Native Language Support ALLBASE/NET is localizable to a variety of other languages, including languages using 8-bit and 16-bit character sets. In MPE/iX, the default language is called NATIVE-3000 . A list of supported languages can be found by running NLUTIL.PUB.SYS.
Gathering Your Data Before you set up ALLBASE/NET, you need to gather the information about the client and/or server that you will be entering in the AliasDB and NETUsers les. If you are the system administrator on both the client and server, all the information you need is readily available to you. If you are the system administrator on only the client or the server, contact the system administrator on the other server or client to obtain speci c information.
If you specify ARPA as the datacomm type, the ARPA domain name must be speci ed. To set or change the local domain name, do the following: 1. Run the NMGR program: :RUN NMMGR.PUB.SYS 2. Open the con guration le: 4OPEN CONFIG5 3. Go to the NS screen: [NS] 4. Type in the local domain name and save it: LocalDomainName [SAVE DATA] 5.
2 Setting Up ALLBASE/NET This chapter provides you with procedures for setting up ALLBASE/NET on both the client and server. It explains how to: Use NETUtil to migrate pro les before HP-UX 10.0 is installed on a server system. Invoke and use NETUtil. Set up ALLBASE/NET on the client. Set up ALLBASE/NET on the server. Before you begin setting up ALLBASE/NET, make sure your networking software is up and running. To do this, type NSCONTROL STATUS at the system prompt.
2. Patch releases are available on HP-UX 9.0 and must be installed on the HP 9000 S700 or S800 client. The patch release numbers are phne 3502 (for S700) and phne 2288 (for S800). 3. Remote loopback must be enabled on the server machine for the conversion of NS node name to ARPA host name to work. The implementation of the MIGRATE ALIAS command on the HP 9000 S700 and S800 makes a connection to the remote loopback service on the server.
Here is a sample log le for a server. The MIGRATE USER BACKWARD command returns the NETUsers le to its state before the 3:41 PM migration. TUE, APR 20, 1993, 3:40 PM: MIGRATE USER Migrated Client : Umach.Udom.Uorg -> Umach.Usite.Uco.Udom Login Name : user1.somegrp.someacct Login Name : user2.somegrp.someacct Migration complete. 2 user(s) migrated successfully. 0 user(s) NOT migrated successfully - see above for error information. TUE, APR 20, 1993, 3:41 PM: MIGRATE USER Migrated Client : mach2.dom.
Using NETUtil NETUtil is the utility you use to create and maintain your AliasDB and NETUsers les. For descriptions of the NETUtil commands and examples of how they are used, refer the \NETUtil Reference" chapter. Invoking NETUtil To invoke NETUtil, type netutil at the MPE/iX prompt.
Adding an Alias Profile To add an alias pro le to the AliasDB le, you must either log on as MANAGER.SYS, have SM capability, or have AM capability for the account you are working in. Follow these steps to add an alias pro le to the AliasDB le: 1. Invoke NETUtil. 2. Type ADD ALIAS at the NETUtil prompt. ADD ALIAS prompts you rst for the alias name of the DBEnvironment on the server and then prompts you for additional information. 3.
After you respond to the last prompt, the following message appears, followed by the NETUtil prompt: Profile added. For an example of how ADD ALIAS is used, refer to \Examples of Setting Up ALLBASE/NET" at the end of this chapter. Warning Use only NETUtil to modify the AliasDB file. Using other software, such as an editor, could damage the file. Changing an Alias Profile You can change the contents of an alias pro le with the CHANGE ALIAS command.
For examples of how DELETE ALIAS is used, refer to \NETUtil Reference" chapter. Displaying an Alias Profile To display one or more alias pro les in the AliasDB le, use the SHOW ALIAS command at the NETUtil prompt. For the naming conventions and syntax to use to respond to the prompts, refer to \Adding an Alias Pro le," above. To display one alias pro le, enter the alias name of the alias pro le you want to display. To display all of the alias pro les, enter an asterisk for the alias name.
Setting Up ALLBASE/NET on the Server The following steps assume that you are setting up ALLBASE/NET on an MPE/iX server and the user is located on an MPE/iX client. However if the user is located on an HP-UX client, you must use HP-UX naming conventions when you enter information in a user pro le. HP-UX naming conventions and syntax are described for each NETUtil command in the \NETUtil Reference" chapter.
is one of either ARPA, NS or NETWARE. This indicates which connection to start. The NETWARE listener is only used for PC access. indicates that the spool le for the listener job should not be deleted automatically and that the log le is always readable. Network Interface DEBUG Here are some examples of starting the listener. Start the listener for the ARPA interface with DEBUG. :ANSTART ARPA DEBUG anutil.pub.
Here are some examples of stopping the listener. Stop the listener for the ARPA interface. :ANSTOP ARPA (ANUtil): ALLBASE/NET LISTENER FOR ARPA HAS BEEN STOPPED SUCCESSFULLY. Stop the listener for the NS interface. :ANSTOP NS (ANUtil): ALLBASE/NET LISTENER FOR NS HAS BEEN STOPPED SUCCESSFULLY. Stop the listener for NetWare. :ANSTOP NETWARE (ANUtil): NETWARE LISTENER HAS BEEN STOPPED SUCCESSFULLY. Alternatively, you can use the following NETWARE command.
Check the status of the listener for the NS interface. : ANSTAT NS numservers If the given listener is currently running and if the number of active servers is requested, the following message is returned. (ANUtil): ALLBASE/NET LISTENER FOR NS IS ALREADY ACTIVE. (ANUtil): Listener process 43 has 0 remote network connection(s) to DBEs. Check the status of the listener for NetWare. : ANSTAT NETWARE If the given listener is currently running, the following message is returned.
Checking the Number of Processes For Each Listener You can use the SHOWPROC command as an alternative to the ANSTAT command. To display the number of processes active in each listener job, use the SHOWPROC command with the TREE option. The INFO string used when the process was created is displayed after the process name. For example: : showproc ;job=#j22;tree QPRI CPUTIME STATE JOBNUM PIN (PROGRAM) STEP C152 0:01.985 WAIT B149 0:02.934 WAIT C152 0:00.
MON. JUL 30, 1993. 9:05 AM: Client: #S54 Server: NodeName: MATE.DBMS.HP Client Version: -CLIVER001 Client MON. JUL 30, 1993. 9:07 AM: Idtfy_clnt CF_GET_PROFILE ClientNode MATE.DBMS.HP ClientLogin MANAGER.SYS.PUB not found: 26002 MON. JUL 30, 1993. 9:07 AM: Hpdadvr IDTFY_CLNT: 26002 MON. JUL 30, 1993. 9:07 AM: Hpdadvr SHUTDOWN CIRCUIT with error 26002 MON. JUL 30, 1993. 9:07 AM: Hpdadvr FATAL_ERROR The rst line of the listener log le shows the date and time of when the listener was started.
Adding a User Profile To add a user pro le to the NETUsers le, you must either log on as MANAGER.SYS, have SM capability, or have AM capability for the account you are working in. To add a user pro le to the NETUsers le: 1. Invoke NETUtil. 2. Type ADD USER at the NETUtil prompt. ADD USER prompts you rst for the node name of the client at which the user is located and then prompts you for additional information. 3.
After you respond to the last prompt, the following message appears followed by the NETUtil prompt: Profile added. For an example of how ADD USER is used, refer to \Examples of Setting Up ALLBASE/NET" at the end of this chapter. Warning Use only NETUtil to modify the NETUsers file. Using other software, such as an editor, could damage the file. Changing a User Profile You can change the contents of one or more user pro les with the CHANGE USER command.
Deleting a User Profile To delete one or more user pro les from the NETUsers le use the DELETE USER command at the NETUtil prompt. The current client node name and client login name uniquely identify the entry to be deleted. If you enter the client login name, you delete the user pro le that has the same name. If you enter an asterisk, you delete all user pro les with the current client node name.
Checking the Services File on the Server If you are using ARPA services, check for a user entry in the SERVICES.NET.SYS le on the client. This le is used by ARPA for dynamic port assignment. The le entry for the ALLBASE/NET service has the o cial service name DAServer, the port number 987, and the protocol name tcp. The le should look like this: :PRINT SERVICES.NET.SYS # This file contains the information about the services provided.
Examples of Setting Up ALLBASE/NET Figure 2-1 shows pro le in the AliasDB and NETUsers les. Both the client and server are MPE/iX systems. Note that the NETUtil commands have varying user restrictions. Refer to the chapter \NETUtil Reference" for complete information. Figure 2-1. Sample Profiles in AliasDB and NETUsers Files To create the sample AliasDB le on the client and add the information shown, you would do the following: 1. Invoke NETUtil on the client. 2. Type ADD ALIAS at the NETUtil prompt.
3. Type show alias to check the alias pro le in the AliasDB le: Alias Name: InvenDB Alias Name: InvenDB Database Server Type: ALLBASE/SQL Server Node Name: snode DBEnvironment Name on Server: PartsDB.DBGroup.Inven Machine Type: hp3000 s900 Datacomm Type: arpa netutil=> Similarly, to create the above NETUsers le on the server and add the information shown in Figure 2-1 , you would do the following: 1. Invoke NETUtil: :netutil 2. Type add user at the NETUtil prompt.
3 Using ALLBASE/SQL Through ALLBASE/NET After the AliasDB and NETUsers les have been created and contain valid pro les and the Listener is running on the server, an application can transparently access a remote ALLBASE/SQL DBEnvironment through ALLBASE/NET. You can use ALLBASE/NET with many applications.
Using the Preprocessor To develop and run an application program from the client, the client must have the following software: ALLBASE/NET utility program le (NETUtil) ALLBASE/SQL software The server must have the following software: The Listener ALLBASE/NET utility program le (NETUtil) ALLBASE/SQL software To use the preprocessor, do the following steps: 1. In the source code, de ne the DBEnvironment on the server with the alias name: begin . . . EXEC SQL CONNECT TO `AliasName'; . . .
2. Invoke the preprocessor on the client and use the alias name for the DBEnvironment. In the following example, the Pascal preprocessor is used. :run psqlpas.pub.sys;info="AliasName" A module is created and stored in the system catalog of the DBEnvironment on the server. The modi ed source code le and the four include les created by the preprocessor remain on the client. For more information on preprocessors, refer to the speci c ALLBASE/SQL application programming guide for the language you are using. 3.
Using ALLBASE/Query To access a remote DBEnvironment using ALLBASE/Query (formerly called HP Visor), enter the alias name on the ALLBASE/Query Choose DBEnvironment screen. You must have Version A.01.03 of ALLBASE/QUERY to use an alias name. It is recommended that client and server logins be the same for remote access with ALLBASE/Query. However, in some cases, such as in MPE/iX to HP-UX connections, this is not always possible.
Using PC-based Application Software From your PC, you can use Microsoft Windows-based application software (4GLs, 3GLs, query or report writing tools) to access ALLBASE/SQL. Simply copy the HP PC API installation le, HPPCAPI.PUB.SYS, to your PC and follow the installation directions. For more information refer to the HP PC API User's Guide for ALLBASE/SQL and IMAGE/SQL.
Figure 3-1.
4 NETUtil Reference This chapter describes the NETUtil commands and gives examples of how they are used. To invoke NETUtil, type netutil at the MPE/iX prompt. The NETUtil prompt looks like this: netutil=> NETUtil lets you type these special control characters: A double forward slash (//), which terminates a command while in prompting mode and returns the NETUtil prompt. 4Control5-Y, which terminates an executing command and returns to the NETUtil prompt.
Command Summary The table below lists the NETUtil commands along with their abbreviations and functions. Table 4-1. NETUtil Commands Command Abbre- Function viation ADD ALIAS AA Adds an alias pro le to the AliasDB le. ADD USER AU Adds a user pro le to the NETUsers le. CHANGE ALIAS CA Changes an alias pro le in the AliasDB le. CHANGE USER CU Changes a user pro le in the NETUsers le, or changes all user pro les having a given client node name with a new client node name in the NETUsers le.
ADD ALIAS ADD ALIAS Use the ADD ALIAS command to add an alias pro le to the AliasDB le on the client. The rst time you use this command to add an alias pro le, the AliasDB le is created. To display the contents of one or more alias use the SHOW ALIAS command. ADD ALIAS can be abbreviated to AA. To issue this command, you must log on as MANAGER.SYS or have SM capability.
ADD ALIAS ServerNodeName MachineType DatacommType is the node name of the server you want to access. The server node name is not case-sensitive and is stored and displayed exactly as it was entered. However, \node" is the same as \NODE" when the SQL application is running and executes a CONNECT or START DBE command with an alias name. The name format is based on the datacommm type. is the machine type of the server. Enter HP 3000 S900, HP9000 S700, or HP9000 S800.
ADD USER ADD USER Use the ADD USER command to add a user pro le to the NETUsers le on the server. The rst time you use this command to add a user pro le, the NETUsers le is created. To display the contents of one or more user pro les, use the SHOW USER command. ADD USER can be abbreviated to AU. To issue this command, you must log on as MANAGER.SYS, have SM capability, or have AM capability for the account speci ed in the command.
ADD USER ServerLoginName The client login name is stored and displayed exactly as it was entered. is the login name used on the server for the user accessing the DBEnvironment on the server. This name follows MPE/iX naming conventions for a login name and is not case-sensitive. The session and group names are optional. The server login name is stored and displayed exactly as it was entered.
CHANGE ALIAS CHANGE ALIAS Use the CHANGE ALIAS command to change an alias pro le in the AliasDB le on the client. CHANGE ALIAS prompts you for the current value of the alias name of the alias pro le you want to change, and then for a new alias name. If you do not want to change the alias name, press the 4Return5 key instead of entering a new name. The current value of each parameter following the alias name is displayed. You are prompted to enter a new value.
CHANGE ALIAS DBEnvironmentName is the fully quali ed lename of the DBEnvironment on the MPE/iX server or the absolute pathname of the DBEnvironment on the HP-UX server. This name follows the le naming conventions of the operating system on which the DBEnvironment resides. The MPE/iX DBEnvironment name cannot exceed 26 characters in length and is not case-sensitive. The HP-UX DBEnvironment name cannot exceed 128 characters in length and is case-sensitive.
CHANGE USER CHANGE USER Use the CHANGE USER command to change a user pro le in the NETUsers le on the server. CHANGE USER can be abbreviated to CU. To issue this command, you must log on as MANAGER.SYS, have SM capability, or have AM capability for the account speci ed in the command.
CHANGE USER ServerLoginName is the login name used on the server for the user accessing the DBEnvironment. You are prompted for the server login name only if you enter the client login name. The MPE/iX server login name follows MPE/iX naming conventions for a user name and is not case-sensitive, The session and group names are optional. The server login name is stored and displayed exactly as it was entered. Only one server login name is allowed for each client node name and client login name combination.
DELETE ALIAS DELETE ALIAS Use the DELETE ALIAS command to delete one or more alias pro les from the AliasDB le on the client. To prevent you from accidentally deleting an alias pro le, you are prompted to con rm the deletion. DELETE ALIAS can be abbreviated to DA. To issue this command, you must log on as MANAGER.SYS or have SM capability.
DELETE ALIAS In this example, all alias pro les for a speci c node are deleted. netutil=> delete alias Alias Name: * Database Server Type: ALLBASE/SQL Server Node Name: snode.sdomain.sorg Profiles qualified: 2 Delete all (y/n)? y Profiles deleted.
DELETE USER DELETE USER Use the DELETE USER command to delete one or more user pro les from the NETUsers le on the server. The values supplied by the client node name and client login name parameters uniquely identify the user pro le to be deleted. To prevent you from accidentally deleting a user pro le, you are prompted to con rm the deletion. DELETE USER can be abbreviated to DU. To issue this command, you must log on as MANAGER.
DELETE USER In this example, all user pro les at the speci ed node are deleted from the NETUsers le. netutil=> delete user Client Node Name/Session Type Name: cnode.cdomain.corg Client Login Name: * Profiles qualified: 2 Delete all (y/n)? y Profiles deleted.
EXIT EXIT Use the EXIT command to terminate execution of the NETUtil program. EXIT can be abbreviated to E. Anyone can issue this command.
HELP Use the HELP command to display and describe all NETUtil commands. HELP can be abbreviated to H or ?. Anyone can issue this command. To leave the HELP command, type //. NETUtil Syntax netutil=> HELP Command Name (opt): CommandName Parameters CommandName is the name or abbreviation of a NETUtil command. If you specify a command name or abbreviation, the correct syntax and a description of that command is displayed. If no name or abbreviation is given, a list of all NETUtil commands is displayed.
HELP Command Summary: ADD ALIAS ADD USER CHANGE ALIAS CHANGE USER AA AU CA CU DELETE ALIAS DA DELETE USER DU EXIT E HELP H or ? MIGRATE ALIAS MA MIGRATE ALIAS BACKWARD MAB MIGRATE USER MIGRATE USER BACKWARD MUB QUIT SET ECHO SHOW ALIAS SHOW USER SYSTEM Q SE SA SU : Adds a profile into the AliasDB file. Adds a profile into the NETUsers file. Changes a profile in the AliasDB file.
HELP netutil=> ADD ALIAS Alias Name: AliasName Database Server Type: DB2 DB2 Database Name: DatabaseName DB2 Connection Type: ConnectionType CICS Transaction ID: TransactionID LU6.2 Time Out Value: TimeoutValue APPC Session Type: SessionType LU6.2 Input Buffer Length: InputBufferLength LU6.2 Output Buffer Length: OutputBufferLength LU6.2 Trace On Flag: TraceOnFlag Machine Type: MachineType Datacomm Type: DatacommType Adds a DB2 profile into the AliasDB file.
MIGRATE ALIAS MIGRATE ALIAS Use the MIGRATE ALIAS command to migrate alias pro les from NS to ARPA in the AliasDB le on the client. You can choose the automatic option to migrate all pro les or the manual option which prompts you for the server node name of each pro le. To use the automatic option, this command must be used before installing HP-UX 10.0 on the client and/or the server. If you execute MIGRATE ALIAS VERBOSE, all diagnostic information written to the log le will also appear on the screen.
MIGRATE ALIAS manual - For each targeted alias pro le, the alias name and current server node name will be displayed. A prompt will appear for the new server node name, with the ARPA host name in parentheses (if it can be determined by NETUtil). You may enter an ARPA host name at the prompt, or if the ARPA host name appears, you may press the 4Return5 key instead. The datacomm type will automatically change from NS to ARPA.
MIGRATE ALIAS Alias: testdb Migrated Server : snode.sdomain.sorg -> snode Cannot migrate alias (testdb2) for server (node1.dom.org) (DBERR 28029) Alias: testdb3 Migrated Server : hana.dom.org -> hana1.site1.co1.domain1 Alias: testdb4 Migrated Server : merc.dom.org -> merc2 Migration complete. 3 alias(es) migrated successfully. 1 alias(es) NOT migrated - see screen above or HPDAMIG.PUB.SYS for error information. Save migration changes (y/n)? y Migration changes saved.
MIGRATE ALIAS In this example, the manual option is chosen. The user exits before all migration is completed. netutil=> MIGRATE ALIAS Automatic Migration (y/n)? n Alias Name : testdb Current Server Node Name : snode.sdomain.sorg New Server Node Name (snode) : 4Return5 Migrate profile (y/n)? y Profile migrated. Alias Name : testdb2 Current Server Node Name : node1.dom.org New Server Node Name () : // Migration complete. 1 alias(es) migrated successfully.
MIGRATE ALIAS BACKWARD MIGRATE ALIAS BACKWARD Use the MIGRATE ALIAS BACKWARD command to change the AliasDB le back to the state prior to the most recent migration. MIGRATE ALIAS BACKWARD can be abbreviated to MAB. You must be logged on as MANAGER.SYS or have SM capability to execute this command. NETUtil Syntax netutil=> MIGRATE ALIAS BACKWARD 2 Migrate AliasDB file backward (y/n)? y es 2 3 n o 3 Description When you use this command the following information is written to the log le, HPDAMIG.
MIGRATE USER Use the MIGRATE USER command to change all user pro les for a given client node name in the NETUsers le on the server. To change individual user pro les based on client login name, use the CHANGE USER command. MIGRATE USER can be abbreviated to MU. MIGRATE USER VERBOSE can be abbreviated to MUV. You must be logged on as MANAGER.SYS or have SM capability to execute this command.
MIGRATE USER Example In this example, the MIGRATE USER command is issued twice; rst with the VERBOSE option, second without. The ARPA host name value for the new client node name could only be determined for the rst pro le. netutil=> MIGRATE USER VERBOSE Current Client Node Name: cnode.cdom.corg New Client Node Name (cnode.cdom1.cdom2.edu) : 4Return5 Migrate All Profiles (y/n)? y Migration in progess ... Migrated Client : rosanne.dbms.
MIGRATE USER BACKWARD Use the MIGRATE USER BACKWARD command to change the NETUsers le back to how it was prior to the most recent migration. MIGRATE USER BACKWARD can be abbreviated to MUB. You must be logged on as MANAGER.SYS or have SM capability to execute this command. NETUtil Syntax netutil=> MIGRATE USER BACKWARD 2 Migrate NETUsers file backward (y/n)? y es 2 3 n o 3 Description When you use this command the following information is written to the log le, HPDAMIG.PUB.
QUIT QUIT Use the QUIT command to terminate execution of the NETUtil program. QUIT can be abbreviated to Q. Anyone can issue this command.
SET ECHO Use the SET ECHO command to echo user input to a standard output le. To turn ECHO on, type SET ECHO; to turn it o , type the command again. The SET ECHO command is useful for checking the job stream output le on MPE/iX. SET ECHO can be abbreviated to SE. Anyone can issue this command. NETUtil Syntax netutil=> SET ECHO Examples Here is an example of a command le that includes the SET ECHO command: 1 2 3 4 5 set echo show user cnode.cdomain.
SHOW ALIAS SHOW ALIAS Use the SHOW ALIAS command to display the contents of one or more alias pro les in the AliasDB le on the client. SHOW ALIAS can be abbreviated to SA. Anyone can issue this command. NETUtil Syntax netutil=> SHOW ALIAS Alias Name: AliasName Parameters AliasName is either the alias name of the DBEnvironment that resides on the server, or an asterisk (*). If you enter an alias name, the contents of that alias pro le is displayed.
SHOW ALIAS When an asterisk is entered for the alias name, all alias pro les in the AliasDB le are shown: netutil=> show alias Alias Name: * Alias Name: InvenDB2 Database Server Type: ALLBASE/SQL DBEnvironment Name on Server: PartsDB.DBgroup2.Inven2 Server Node Name: snode1.sdomain1.sorg1 Machine Type: HP3000 S900 Datacomm Type: NS Alias Name: InvenDB3 Database Server Type: ALLBASE/SQL DBEnvironment Name on Server: PartsDB.DBgroup3.Inven3 Server Node Name: snode.sdomain.
SHOW USER SHOW USER Use the SHOW USER command to display the contents of one or more user pro les in the NETUsers le on the server. SHOW USER can be abbreviated to SU. To issue this command, you must log on as MANAGER.SYS, have SM capability, or have AM capability for the account speci ed in the command.
SHOW USER In this example, all the user names are shown for a particular node. netutil=> show user Client Node Name/Session Type Name: cnode.cdomain.corg Client Login Name: * Client Node Name/Session Type Name: cnode.cdomain.corg Client Login Name: ann.orders,vendors Server Login Name: ann.orders,vendors Client Node Name/Session Type Name: cnode.cdomain.corg Client Login name: charly.finance,stmts Server Login Name: charly.finance,stmts netutil=> In this example, all pro les in the NETUsers le are shown.
SYSTEM SYSTEM Use the SYSTEM command to escape temporarily to the operating system to execute a single operating system command. SYSTEM can be abbreviated with a colon (:). Anyone can issue this command. NETUtil Syntax netutil=> SYSTEM Command: SystemCommand Parameters SystemCommand is the MPE/iX command to be executed.
A ALLBASE/NET File Names The following ALLBASE/NET les are supplied with ALLBASE/SQL: File Name Description ANUTIL.PUB.SYS ANSTART.PUB.SYS ANSTOP.PUB.SYS ANSTAT.PUB.SYS HPDALSTN.PUB.SYS HPDALSNP.PUB.SYS ALLBASE/NET listener utility program. Command le that starts the listener. Command le that stops the listener. Command le that checks if the listener is running. Listener for NS, ARPA, and NetWare. Listener for HP PC API NetWare access linked with the POSIX C library.
One of the following les is created when the listener is started on the server: File Name Description HPDAARLG.PUB.SYS HPDANSLG.PUB.SYS HPNWLG.PUB.SYS Listener log le for ARPA Listener log le for NS Listener log le for NetWare The following les are created by the migration commands: File Name Description HPDAMIG.PUB.SYS DAUSFMIG.PUB.
Glossary alias name The unique name on the client that represents a speci c DBEnvironment on the server. The alias name is part of each alias pro le in the AliasDB le. alias pro le A set of information that is associated with the alias name for a DBEnvironment. Alias pro les are contained in the AliasDB le on the client. They are created and maintained by the system administrator using NETUtil.
database A structured arrangement of data elements designed for the easy selection of information. In ALLBASE/SQL, a database is a collection of tables, views, and indexes having the same ownership in a DBEnvironment. DBEnvironment A collection of les containing one or more ALLBASE/SQL databases, plus other entities that contain information for all databases in the DBEnvironment. DBEUserID A login name that is one type of owner of database objects.
NETUsers le The NETUsers le contains sets of information, called user pro les, that are associated with each ALLBASE/NET user. The NETUsers le resides on the server. It is created when the rst user pro le is entered. NetWare A networking product originally from Novell that is used in the PC environment. NetWare/iX is Hewlett-Packard Company's port of Novell Inc.'s NetWare for UNIX. node name The \NS node name" is used by NS/Net/IPC and de ned through NMMGR on MPE/iX or through SAM on HP-UX.
Index 4 4GLs on the PC, 3-5 A abbreviations, NETUtil, 4-2 accessing a remote DBE, 3-1 ADD ALIAS command, 1-5, 2-4, 2-5, 4-3 adding an alias pro le, 2-5, 4-3 adding a user pro le, 2-14, 4-5 adding pro les, 1-4 ADD USER command, 1-5, 2-8, 2-14, 4-5 AliasDB le, 1-4, 1-8, A-1 adding an alias pro le, 2-5, 4-3 changing an alias pro le, 2-6, 4-7 creating, 1-5, 4-4 deleting an alias pro le, 2-6, 4-11 displaying an alias pro le, 2-7 example, 2-18 alias name, 1-4, 1-8, 4-3 alias pro le, 1-4 ALLBASE/4GL, 1-1, 3-4 AL
E M etc/hosts, 1-9 examples adding an alias pro le, 4-4 AliasDB le, 2-18, 4-29 changing an alias pro le, 4-8 changing a user pro le, 4-10 deleting an alias pro le, 4-11 deleting a user pro le, 4-13 displaying an alias pro le, 4-29 displaying a user pro le, 4-31 NETUsers le, 2-19, 4-31 using the HELP command, 4-16 using the SET ECHO command, 4-28 EXIT command, 4-15 Microsoft Windows applications, 3-5 MIGRATE ALIAS, 4-19 MIGRATE ALIAS BACKWARD, 4-23 MIGRATE USER, 4-24 MIGRATE USER BACKWARD, 4-26 migrating
NS location of node name, 1-9 NS3000/XL Network Services, 1-3 O OWNER authority, 3-3 P patches needed for migration, 2-1 PC application software, 3-5 Q QUIT command, 4-27 R remote DBEnvironment connecting to, 3-5 remote loopback for migration, 2-1 report writers on the PC, 3-5 RUN authority, 3-3 running a program, 3-3 S server list le, 2-2, 4-20 server login name, 1-6, 4-6 server node name, 2-5, 4-4 SERVICES.NET.
