HP 3000 Manuals HP 3000 Manuals
Setting Up ALLBASE/NET on the Client
There are two tasks you perform on the client to set up ALLBASE/NET:
* Adding alias profiles to the AliasDB file.[REV BEG]
* Checking the SERVICES.NET.SYS file (for ARPA services).[REV END]
The AliasDB file contains an alias profile for each alias name that
corresponds to a DBEnvironment on the server. You create the file the
first time you add an alias profile with NETUtil's ADD ALIAS command.
Once the file is created, use ADD ALIAS to add more alias profiles to it.
NETUtil provides three commands for maintaining alias profiles in the
AliasDB file: CHANGE ALIAS, DELETE ALIAS, and SHOW ALIAS. Instructions
for using these commands follow later in this section. If you are using
ARPA services, the[REV BEG] SERVICES.NET.SYS[REV END] on the client
requires an ARPA user entry. If this entry doesn't exist, you must
update the file.[REV BEG] The section "Checking the Services File on the
Client" later in this chapter discusses updating the file.[REV END]
If loopback is being used, the ARPA name needs to be the local host.
Adding an Alias Profile
[REV BEG]
To add an alias profile to the AliasDB file, you must either log on as
MANAGER.SYS, have SM capability, or have AM capability for the account
you are working in.[REV END] Follow these steps to add an alias profile
to the AliasDB file:
1. Invoke NETUtil.
2. Type ADD ALIAS at the NETUtil prompt. ADD ALIAS prompts you first
for the alias name of the DBEnvironment on the server and then
prompts you for additional information.
3. Respond to each prompt as follows:
Prompt Response
Alias Name: Enter the alias name of the DBEnvironment
on the server, to be used by an
application on the client. The alias
name must be unique on the client and
does not have to be the same as the
DBEnvironment name. It can consist of
ASCII 7-bit characters as well as some
8-bit and 16-bit character sets (either
ASCII or non-ASCII), can contain up to
128 characters, and must not begin with
an asterisk (*). The alias name is not
case-sensitive and it is stored and
displayed exactly as it was entered.
Database Server Type: [REV BEG]
Enter ALLBASE/SQL, the database
management system server type on the
server. (HP SQL is still supported as a
database server type. However, if you
enter HP SQL, NETUtil displays it as
ALLBASE/SQL.) The database server type
name is not case-sensitive and is
stored and displayed in uppercase
characters.[REV END]
DBEnvironment Name: Enter the fully qualified filename of the
DBEnvironment on the server. This name
follows the file naming conventions of
the operating system in which the
DBEnvironment resides. It cannot exceed
26 characters in length, is not
case-sensitive, and is stored and
displayed exactly as it was entered.
Server Node Name: Enter the node name of the server. This
name is not case-sensitive and is stored
and displayed in uppercase characters.
Machine Type: [REV BEG]
Enter the machine type of the server:
HP3000 S900, HP9000 S700, or HP9000 S800.
A space is required between HP3000 or
HP9000 and the series number. The
machine type name is not case-sensitive
and is stored and displayed in uppercase
characters.[REV END]
Datacomm Type: Enter the type of network service you are
using, either ARPA or NS.[REV BEG] If you
are using HP-UX release 10.0 on either
the client or server, ARPA is the only
valid entry.[REV END] The datacomm type
name is not case-sensitive.
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 profile with the CHANGE ALIAS
command.
For the naming conventions and syntax to use to respond to the prompts,
refer to "Adding an Alias Profile," above.
To change an alias profile:
1. Type CHANGE ALIAS at the NETUtil prompt.
CHANGE ALIAS prompts you first for the current alias name of the
profile you want to change and then prompts you for additional
information.
2. Enter the current alias name.
3. Enter a new alias name. If you do not want to change the current
alias name, press the Return key.
The current value for each parameter in the entry is displayed in
succession. You are prompted to enter a new value for each
parameter. If you do not want to change a current value, press
the Return key.
4. Confirm the changes by entering Y or N.
For examples of how CHANGE ALIAS is used, refer to the "NETUtil
Reference" chapter.
Deleting an Alias Profile
To delete one or more aliases from the AliasDB file use the DELETE ALIAS
command at the NETUtil prompt. If you enter an alias name, you delete
the alias profile for that name. If you enter an asterisk, you delete
all alias profiles for a specific server.
For the naming conventions and syntax to use to respond to the prompts,
refer to "Adding an Alias Profile," above.
To delete one alias profile, do the following:
1. Enter the alias name of the alias profile you want to delete.
2. Confirm the deletion by entering Y or N.
To delete alias profiles for a specific server node, do the following:
1. Enter an asterisk (*) for the Alias Name.
2. Enter the database server type (ALLBASE/SQL).
3. Enter the server node name.
4. Confirm the deletions by entering Y or N.
For examples of how DELETE ALIAS is used, refer to "NETUtil Reference"
chapter.
Displaying an Alias Profile
To display one or more alias profiles in the AliasDB file, 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 Profile," above.
To display one alias profile, enter the alias name of the alias profile
you want to display.
To display all of the alias profiles, enter an asterisk for the alias
name.
For an example of how SHOW ALIAS is used, refer to "Examples of Setting
Up ALLBASE/NET" at the end of this chapter.
[REV BEG]
Checking the Services File on the Client
If you are using ARPA services, check for a user entry in the
SERVICES.NET.SYS file on the client. This file is used by ARPA for
dynamic port assignment. The file entry for the ALLBASE/NET service has
the official service name DAServer, the port number is usually 987, and
the protocol name tcp. The port number in this file must match the port
number in the SERVICES.NET.SYS file on the server. The file should look
like this:
:PRINT SERVICES.NET.SYS
# This file contains the information about the services provided.
#
# The form for each entry is:
# <official service name> <port number/protocol name> <aliases>
#
# See the services(4) manual page for more information.
# Note: The entries cannot be preceded by a blank space.
#
ftp 21/tcp
DAServer 987/tcp #SQL distributed access
:
If the last line above is not there, update the SERVICES.NET.SYS file to
include this line. You may need to create a services file. Refer to the
sample file SERVSAMP.NET.SYS for the format.[REV END]