HPlogo ALLBASE/NET User's Guide: HP 9000 Computer Systems > Chapter 2 Setting Up ALLBASE/NET

Setting Up ALLBASE/NET on the Server
» 

Technical documentation

Complete book in PDF
» Feedback

 » Table of Contents

 » Glossary

 » Index

spacerspacerspacer
spacer
spacer
  		 
 
NOTE: The following steps assume that you are setting up ALLBASE/NET on an HP-UX server and the user is located on an HP-UX client. However, if the user is located on an MPE/iX client, you must use MPE/iX naming conventions when you enter information in a user profile. MPE/iX naming conventions and syntax are described for each NETUtil command in the "NETUtil Reference" chapter.

Procedures for setting up ALLBASE/NET on an MPE/iX server are in "Setting Up ALLBASE/NET" chapter of the 900 Series HP 3000 Computer Systems ALLBASE/NET User's Guide.

To set up ALLBASE/NET, perform the following steps:

  • Start the listener.

  • Assign a server login name for the client.

  • Add user profiles to the NETUsers file.

  • Check the /etc/service file (for ARPA services).

Starting the Listener Daemon on an HP-UX Server

As system administrator on the server, you need to start the listener daemon after ALLBASE/NET is installed. (You must have superuser capability to do this.) The listener daemon must be started the first time ALLBASE/NET is used after a system boot.

NOTE: These steps are for starting the listener on an HP-UX server. To start the listener on an MPE/iX server, refer to "Setting Up ALLBASE/NET on the Server" chapter of the 900 Series HP 3000 Computer System ALLBASE/NET User's Guide.

To start the listener daemon, type:

  $ /usr/bin/hpdaX

where X is either NS or ARPA.

When the listener daemon is started, a log file named /tmp/hpdaX.log is automatically created (where X is either NS or ARPA). This is a circular file that holds 1000 entries containing listener daemon status information.

NOTE: NS is not included in the 10.0 version of HP-UX.

Error Handling

If an error occurs, determine the cause of the error and take the appropriate action. If you are using NS, the NetIPC error code is contained in the last three digits of the error number returned.

For descriptions of NetIPC error messages, refer to the NetIPC Programmer's Guide.

If you are using ARPA services, refer to the ALLBASE/SQL Message Manual for error message descriptions. The last three digits are specify the ARPA error message number.

After the error is corrected, terminate the listener daemon process, remove the log file (if desired), and restart the listener daemon using the following steps. You must have superuser capability to remove the log file.

  1. Obtain the process identification number (pid) of the listener daemon by typing:

      $ ps -ef | grep hpdaX

  2. Kill the process by typing:

      $ kill -9 pid

  3. Remove the /tmp/hpdaX.log file by typing:

      $ rm /tmp/hpdaX.log

    If this file is not removed, it will be appended to as new activities are logged.

  4. Restart the listener daemon by typing:

      $ /usr/bin/hpdaX

  5. Once the listener daemon is started, modify the /etc/netlinkrc file on the server to start the listener daemon files automatically when the system is booted. For example:

      $ vi /etc/netlinkrc

  [vellip]

  #start hpdaNS daemon, for HP-UX 9.0 or earlier 

  #for ALLBASE/NET

  if [ -f /usr/bin/hpdaNS ]

  then

    /bin/rm -f /tmp/hpdaNS.log

    /usr/bin/hpdaNS

  fi

  #start hpdaARPA daemon

  #for ALLBASE/NET

  if [ -f /usr/bin/hpdaARPA]

  then

    /bin/rm -f /tmp/hpdaARPA.log

    /usr/bin/hpdaARPA

  fi

Examples of Listener Daemon Log Files

In the following NS log file example, the first three lines show that the listener daemon has started; the next three lines show an example of the information displayed when a connection has been made.

  $ more /tmp/hpdaNS.log

  Mon Jul 11 13:30:28 1993:  ipccreate: 0

  Mon Jul 11 13:30:28 1993:  ipcname: 0

  Mon Jul 11 13:30:28 1993:  ipccontrol: 0

  Mon Jul 11 13:30:28 1993:  ipcrecvcn: 0

  Tue Jul 12 12:27:12 1993:  ipccontrol: 0

  Tue Jul 12 12:27:12 1993:  Client PID:19914  Server PID:11910

  Client Nodename: cnode.cdomain.corg

The ARPA log file is similar, as the following example shows.

  $ more /tmp/hpdaARPA.log

  Mon Jul 11 13:30:28 1993:  socket: 0

  Mon Jul 11 13:30:28 1993:  bind: 0

  Mon Jul 11 13:30:28 1993:  listen: 0

  Tue Jul 12 12:27:12 1993:  accept: 0

  Tue Jul 12 12:27:12 1993:  Client PID:19914  Server PID:11910

  Client Nodename: clientsystem

If there are no errors, a zero (0) is returned, as indicated in the examples above. A number other than zero or another message appears in the log file if an error condition has occurred.

Assigning a Server Login

Assign a server login for the user on the client who is accessing the DBEnvironment on the server. Use the information about the client login name and client node name that you obtained from the client's system administrator. For more information about server login names, refer to "Client and Server Login Names" under "Cross-System Connectivity" in the "Getting Started" chapter.

Add the server login name to the /etc/passwd file on the server. Put an asterisk (*) in the password field of the entry so that someone with the same name as the server login name cannot use the remote login (rlogin) command to access files on the server.

NOTE: If you are setting up ALLBASE/NET on an HP-UX server but the user is on an MPE/iX client, refer to "Client and Server Login Names" under "Cross-System Connectivity" in the "Getting Started" chapter.

Authorities

The user for whom you are assigning the server login name will need the necessary authorities (such as CONNECT authority) for accessing the DBEnvironment on the server. These authorities must be granted by the database administrator responsible for the DBEnvironment.

Adding a User Profile

To add a user profile to the NETUsers file:

  1. Invoke NETUtil.

  2. Type ADD USER at the NETUtil prompt.

    ADD USER prompts you first for the node name of the client at which the user is located and then prompts you for additional information.

  3. Respond to each prompt as follows:

Prompt

Response

Client Node Name:

Enter the name of the client node at which the user is located. The client node name is not case-sensitive.

Client Login Name:

Enter the login name of the user on the client. This name can be either a HP-UX or MPE/iX login. A wildcard (@) can be used as the login name. This is explained in the "NETUtil Reference" chapter.

If the client is HP-UX, this name follows HP-UX naming conventions for a login name, cannot exceed eight characters in length, and is case-sensitive.

If the client is MPE/iX, this name follows MPE/iX naming conventions for a logon name, a component cannot exceed eight characters in length, and is not case-sensitive. The session and logon group names are optional. The session name is not allowed. The group name is required.

Server Login Name:

Enter the server login name you assigned to the user accessing the DBEnvironment on the server. This name follows HP-UX naming conventions for a login name, cannot exceed eight characters in length, and is case-sensitive. The server login name must reside in the /etc/passwd file. When possible, this name should be the same as the client login name. Refer to "Client and Server Login Names" under "Cross-System Connectivity" in the "Getting Started" chapter.

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 a user profile with the CHANGE USER command.

For the naming conventions and syntax to use to respond to the prompts, refer to "Adding a User Profile," above.

To change a user profile, do the following:

  1. Type CHANGE USER at the NETUtil prompt.

    CHANGE USER prompts you first for the node name of the client at which the user is located and then prompts you for additional information.

  2. Enter the client node name of the profile you want to change.

  3. Enter a new client node name. If you do not want to change the current name, press the Return key.

  4. Enter the current client login name of the user or an asterisk (*).

    If you enter an asterisk, all client node names in the NETUsers file that match the current client node name are changed to the new client node name.

    If you enter the current client login name of the user, you are prompted for a new client login name.

  5. Enter a new client login name.

    The current server login name is displayed, followed by a prompt for a new server login name.

  6. Enter a new server login name. If you do not want to change the current name, press the Return key.

  7. Confirm the changes by entering Y or N.

For examples of how CHANGE USER is used, refer to the "NETUtil Reference" chapter.

Deleting a User Profile

To delete one or more user profiles from the NETUsers file 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 profile that has the same name. If you enter an asterisk, you delete all user profiles with the current client node name.

For the naming conventions and syntax to use to respond to the prompts, refer to "Adding a User Profile," above.

To delete a single user profile, do the following:

  1. Enter the client node name for the user profile you want to delete.

  2. Enter the client login name.

  3. Confirm the deletion by entering Y or N.

To delete all user profiles with the same client node name, do the following:

  1. Enter the client node name for the user profiles you want to delete.

  2. Enter an asterisk (*) for the client login name.

  3. Confirm the deletions by entering Y or N.

For examples of how DELETE USER is used, refer to "NETUtil Reference" chapter.

Displaying a User Profile

To display the contents of one or more user profiles in the NETUsers file type the SHOW USER command at the NETUtil prompt. You can display all user profiles, user profiles for a specific node, or user profiles with the same client login name.

For the naming conventions and syntax to use to respond to the prompts, refer to "Adding a User Profile," above.

To display one user profile, do the following:

  1. Enter the client node name for the user profiles you want to display.

  2. Enter the client login name for the user.

To display all of the user profiles in the NETUsers file, do the following:

  1. Enter an asterisk (*) for the client node name.

  2. Enter an asterisk (*) for the client login name.

To display all user profiles with the same client login name, do the following:

  1. Enter an asterisk (*) for the client node name.

  2. Enter the client login name.

To display all user profiles for a specific client node, do the following:

  1. Enter the client node name.

  2. Enter an asterisk (*) for the client login name.

For an example of how SHOW USER is used, refer to "Examples of Setting Up ALLBASE/NET" at the end of this chapter.



Setting Up ALLBASE/NET on the Client
  		 


Examples of Setting Up ALLBASE/NET  
Feedback to webmaster