HP 3000 Manuals HP 3000 Manuals
Host Sessions
Below we briefly discuss how the PC user establishes a session on the HP
3000, using an IAFILE, and how serious errors are reported.
Establishing a Host Session
The PC user must have a session on the host HP 3000 in order for Access
PC to communicate with Access Server.
There are several ways for the PC user to log on to the HP 3000. For a
description of all the logging on procedures, see in the Information
Access PC Connections and Batch Files manual.
PC Users Running an MPE Interface Program
In a basic serial environment, you may have MPE users who are not
permitted to log on to the host HP 3000 directly, but who use instead a
logon UDC that runs an MPE interface program like HP Menu or HP Desk. Or
you may have normal MPE users who prefer to remain in HP Desk and run
programs from within HP Desk.
These users need to do the following to access remote tables using Access
PC:
1. From the MPE interface program, run the program file PCCI.PUB.SYS.
The prompt PCCI: appears on the screen.
2. Switch the PC from terminal mode to PC mode.
3. Run Access PC in the normal way.
4. After exiting from Access PC, revert to terminal mode and, at the
PCCI: prompt, type EXIT and press Return. This returns the user
to the MPE interface program.
Using an IAFILE
A PC user can enter MPE commands in a file and have them executed when
Information Access is started up. This file, called an IAFILE, is mainly
used to allow file equations to be generated for files that are not fully
described in the data dictionary.
An IAFILE is useful in an HP OfficeShare environment since logon UDCs
cannot be executed in sessions created by Access PC in this environment.
The file equations could be used to access files or to redirect ASCII
output files to a printer. (For more information about file equations,
see "Using File Equations" under "Defining Files on HP 3000" in Chapter
4.)
HDSP and the Administrator Utility execute all commands in the IAFILE
before the program begins. HDSP issues all file equations before the
message catalog is opened. Thus, the IAFILE can be used to set the
appropriate user language by setting the appropriate native language
JCWs.
Access Server supports both global and local IAFILEs. The global IAFILE
resides in PPCSAVE.HPOFFICE and the local IAFILE resides in the user's
logon group and account. The global IAFILE is executed before the local
one, so a user can overwrite a file equation.
For example, you or your System Manager might create the file
IAFILE.PPCSAVE.HPOFFICE. It looks like this:
FILE LPLONG;DEV=PP,9;ENV=LPLONG.HPENV.SYS
FILE PP;DEV=PP,13;ENV=LP2.HPENV.SYS
FILE DATAFILE=DATAFILE.MYGROUP.MYACCNT
The user could then set up her own IAFILE that looks like this:
REMOTE HELLO USER.ACCOUNT;DSLINE=REM=REMOTE.LOCAL.LAN
FILE DATAFILE=DATAFILE.REMGRP.REMACCT;DEV=REM#
FILE MYPP;DEV=PP;ENV=ELITE.HPENV.SYS
The Spoolfiles HDSPERR and HDSPNSE
When the user establishes a host session, Access Server sets up one or
two spoolfiles associated with that session. The spoolfile HDSPERR is
used to record serious errors with the HDSP server process; the spoolfile
HDSPNSE is used to record serious errors with the HDSPNS server process
in the OfficeShare networking environment.
If the user interaction with Access Server is free of error, the
spoolfiles are deleted when the session terminates. But if serious
errors occur, the error messages are written to the appropriate
spoolfile, which is sent to the printer when the session terminates.