 |
» |
|
|
|
To set up ALLBASE/NET, perform the following steps:
Assign a server login name for the client.
Add user profiles to the NETUsers file.
Check the SERVICES.NET.SYS file (when using ARPA services) on the server.
Maintaining the Listener on an MPE/iX Server | |
As system administrator on the server, you need to start, stop, and
check the status of the listener
after ALLBASE/NET is installed. You must have NM (Node Manager)
capability to do these tasks. Sometimes you may want to check the
listener log file. These tasks are discussed in the sections below.
The listener must be started the first time ALLBASE/NET is used after a
system boot.
| | | |  | NOTE:
These steps are for starting the listener on an MPE/iX server node.
To start the listener on an HP-UX server node, refer to "Setting Up
ALLBASE/NET on the Server" chapter of the
HP 9000 Computer System ALLBASE/NET User's Guide.
| | | | |
Before you start the listener, be sure that the network transport
loopback interface has been turned on. It should be turned on at
system boot up time with the command:
:NETCONTROL START;NET=LOOP
|
To start the listener, use the ANSTART command. This command streams
a job which runs the listener. The listener job is streamed with the
;HIPRI option to ensure a timely logon. Once the listener program is
started, it runs in the B queue at priority 149.
The syntax for this command is: ANSTART " {Network Interface} [DEBUG] where - Network Interface
is one of either ARPA, NS or NETWARE.
This indicates which connection to start. The NETWARE listener is only
used for PC access.
- DEBUG
indicates that the spool file for the listener job should not be
deleted automatically and that the log file is always readable.
Here are some examples of starting the listener.
Start the listener for the ARPA interface with DEBUG.
:ANSTART ARPA DEBUG
anutil.pub.sys START ARPA DEBUG
(ANUtil): Checking ALLBASE/NET listener status for ARPA.
(ANUtil): Starting ALLBASE/NET listener for ARPA.
#J17
(ANUtil): Verifying ALLBASE/NET listener for ARPA is started.
(ANUtil): ALLBASE/NET LISTENER FOR ARPA HAS BEEN STARTED SUCCESSFULLY.
Start the listener for the NS interface with DEBUG.
:ANSTART NS DEBUG
(ANUtil): ALLBASE/NET LISTENER FOR NS HAS BEEN STARTED SUCCESSFULLY.
Start the listener for NetWare without DEBUG. NetWare is for
ALLBASE/SQL PC API only.
:ANSTART NETWARE
(ANUtil): NETWARE LISTENER HAS BEEN STARTED SUCCESSFULLY.
Alternatively, you can use the following command file.
:NWSTART
(ANUtil): ANSTART NETWARE
(ANUtil): NETWARE LISTENER HAS BEEN STARTED SUCCESSFULLY.
|
To stop the listening, use the ANSTOP command.
When all server processes have terminated, the listener terminates.
The listener stops listening when it receives the ANSTOP command.
The syntax for the ANSTOP command is:
ANSTOP {Netware Interface} where - Network Interface
is one of either ARPA, NS or NETWARE.
This indicates which connection to stop. The NETWARE listener is only
used for PC access.
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.
:NWSTOP
(ANUtil): ANSTOP NETWARE
(ANUtil): NETWARE LISTENER HAS BEEN STOPPED SUCCESSFULLY.
|
Checking the Status of the ListenerTo check the status of the listener, use the ANSTAT command.
This command checks to see if a given listener job is running.
The syntax for this command is:
ANSTAT [Network Interface] [NUMSERVERS] where
- Network Interface
is one of either ARPA, NS or NETWARE.
This indicates which connection to check the status of. The NETWARE listener
is only used for PC access. If no network interface is specified, status
will be reported for all interfaces.
- NUMSERVERS
indicates that the current number of RDA servers for
this listener be displayed.
Here are some examples of checking the status of the listener.
Check the status of the listener for the ARPA interface.
: ANSTAT ARPA
If the given listener is not currently active, the following message
is returned.
(ANUtil): ALLBASE/NET LISTENER FOR ARPA IS NOT ACTIVE,
TO START USE 'ANSTART ARPA'.
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.
(ANUtil): NETWARE LISTENER IS ALREADY ACTIVE.
Alternatively, you can use the NWSTAT command.
: NWSTAT
(ANUtil): ANSTAT NETWARE
(ANUtil): NETWARE LISTENER IS ALREADY ACTIVE.
Check the status of all listners at once.
: ANSTAT
(ANUtil): ALLBASE/NET LISTENER FOR ARPA IS ALREADY ACTIVE,
TO START USE 'ANSTART'.
(ANUtil): ALLBASE/NET LISTENER FOR NS IS ALREADY ACTIVE.
(ANUtil): NETWARE LISTENER IS NOT ACTIVE.
|
Here's what the SHOWJOB command displays when both the NS and ARPA
listeners are active. J22 is the NS listener and J23 is the ARPA listener.
: showjob job=@j
JOBNUM STATE IPRI JIN JLIST INTRODUCED JOB NAME
#J2 EXEC 10S LP THU 12:01P FTPMON,FTP.SYS
#J22 EXEC 10S LP MON 9:56A HPDANS,MANAGER.SYS
#J23 EXEC 10S LP WED 9:38A HPDARPA,MANAGER.SYS
3 JOBS (DISPLAYED):
0 INTRO
0 WAIT; INCL 0 DEFERRED
3 EXEC; INCL 0 SESSIONS
0 SUSP
JOBFENCE= 7; JLIMIT= 4; SLIMIT= 20
|
Checking the Number of Processes For Each ListenerYou 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 J22 36 :HPDALSTN '-l NS'
B149 0:02.934 WAIT J22 65 (HPDALSTN.PUB.SYS) -l NSC
C152 0:00.099 WAIT J22 37 (HPDADVR.PUB.SYS) 11000001,1,NS
:showproc; job=#j23
QPRI CPUTIME STATE JOBNUM PIN (PROGRAM) STEP
C152 0:02.076 WAIT J23 68 :HPDALSTN '-l ARPA'
B149 0:02.666 WAIT J23 54 (HPDALSTN.PUB.SYS) -l ARPA
C152 0:00.106 WAIT J23 40 (HPDADVR.PUB.SYS) 11000001,1,ARPA
:
A user without the appropriate privilege (SM or OP) will get the following
error when a showproc is attempted:
:showproc; job=#j22;tree
Cannot access job #J22. (CIERR 11002)
:
|
Checking the Listener Log FileTo check the listener log file, HPDANSLG (for NS) or HPDAARLG (for
ARPA), use the PRINT
command. This can be done when the listener is not running or if the
listener was started with the DEBUG option. For example:
The listener log file shows the date and time when the listener was
started or restarted. It then shows the client node name of the user
that has been successfully connected by the listener and the client
version. The client version indicates whether the client is on an MPE/iX
system (-) or on an HP-UX (*) system. If the connection was made with
a client running a version of ALLBASE/NET that is earlier than A.30.00
(MPE/iX) or A.08.00 (HP-UX), the ALLBASE/NET version number is shown.
Listener error codes are also shown. Refer to the ALLBASE/SQL Message Manual for
descriptions of listener error codes.
The listener log file is a circular file that holds 1000 entries. The
last entry in the file is the most recent.
Here is an example of a typical listener log file:
MON, JUL 30, 1993. 9:01 AM: ***** ALLBASE / NET LISTENER *****
MON, JUL 30, 1993. 9:01 AM: - ALLBASE/NET LISTENER FOR ARPA IS
ALREADY ACTIVE.
MON. JUL 30, 1993. 9:05 AM: Client: #S54 Server: Client
NodeName: MATE.DBMS.HP Client Version: -CLIVER001
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 first line of the listener log file shows the date and time of
when the listener was started.
The next line shows the date and time of an attempt to restart the
listener.
The following two lines show that a successful connection was made.
The last five lines show an unsuccessful attempt to make a connection.
Assigning a Server Login | |
Assign a server login name for the user on the client that 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. The server login name should
be in the format:
[session,]user.account[,group]
|
The session name is optional.
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, 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 profile to the NETUsers file:
Invoke NETUtil.
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.
Respond to each prompt as follows:
- Prompt
Response
- Client Node Name/Session Type Name:
Enter the name of the client node where the user is located. The
client node name is not case-sensitive. (Ignore Session Type Name.
It is used only for setting up ALLBASE/DB2 CONNECT on the client.)
- 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 using the format:
[session,]user.account[,group]
This name follows MPE/iX naming conventions for a login name; a
component cannot exceed eight characters in length, and is not
case-sensitive. The session and logon group names are optional. (For
guidelines on specifying session and group names, refer to the
previous section, "Assigning a Server Login Name.")
| | | | | NOTE:
The client node, client login, and server login names are stored and
displayed exactly as they were entered.
| | | | |
After you respond to the last prompt, the following message appears
followed by the NETUtil prompt:
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 profiles 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:
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.
Enter the client node name of the profile you want to change.
Enter a new client node name. If you do not want to change the current name, press the Return key.
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.
Enter a new client login name.
The current server login name is displayed, followed by a prompt for a new server login name.
Enter a new server login name. If you do not want to change the current name, press the Return key.
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:
Enter the client node name for the user profile you want to delete.
Enter the client login name.
Confirm the deletion by entering Y or N.
To delete all user profiles with the same client node name, do the following:
Enter the client node name for the user profiles you want to delete.
Enter an asterisk (*) for the client login name.
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:
Enter the client node name for the user profiles you want to display.
Enter the client login name for the user.
To display all of the user profiles in the NETUsers file, do the following:
Enter an asterisk (*) for the client node name.
Enter an asterisk (*) for the client login name.
To display all user profiles with the same client login name, do the following:
Enter an asterisk (*) for the client node name.
Enter the client login name.
To display all user profiles for a specific client node, do the following:
Enter the client node name.
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.
Checking the Services File on the Server | |
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 987, and the
protocol name tcp. 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.
|
