HP 3000 Manuals

Diagnostic Tests [ Information Access Server: System Management ] MPE/iX 5.0 Documentation


Information Access Server: System Management

Diagnostic Tests 

Access Server is now resident on your system.  The program files, data
and message files, the Information Access data dictionary, and the
account structures are all in place, and you are ready to verify that the
installation is correct.

Verification Testing 

The verification test is automatically run by the VERIFY job as a result
of streaming JINSTHDP.PPCUTIL.HPOFFICE during installation.  It shows
whether Access Server was installed correctly on the HP`3000.  It checks
that all Access Server software components are present and that their
versions are correct.

To see the results of the verification test, type the UDC:

          :HOSTVERIFY

or

          :RUN ADMIN.PPC.SYS;PARM=5

Results of the verification test can also be found under the logon
MGR.HPOFFICE in the VERIFY job $STDLIST file.

The diagnostic looks for a file called DHDPJOBS in the group
PPCSAVE.HPOFFICE. This file, which is created by the installation jobs,
tracks the progress of the installation.

   *   If no DHDPJOBS file is found, the diagnostic proceeds with the
       verification.

   *   If the DHDPJOBS file indicates a successful installation, the
       diagnostic purges the file and proceeds with the verification.

   *   If the DHDPJOBS file indicates that an installation job failed,
       the diagnostic reports which job failed, purges the file, and
       halts the verification.  In this case, check the spoolfile and
       correct the problem; then repeat the installation steps again.

The Access Server module versions installed on the host HP`3000 are
checked.  The DHDPMODS.PPCUTIL.HPOFFICE file includes the names of all
Access Server modules.  This file is used to find the modules for
verification.  The verification test checks to see that each is present
and that the versions are correct.

Specifically, it verifies that each Access Server module listed in
DHDPMODS has a version number identical to all other Access Server module
version numbers.

The verification test creates the file DHDPVERS.PPCSAVE.HPOFFICE that
contains all module names and their versions found during the run.  If
incorrect versions are found, an error message directs you to check the
DHDPVERS file to find the errors.

Each Access Server module contains a version stamp of eight characters,
in the format V.UU.FF.III, where:

V = Version code, identifying a major software revision.

U = Update level, identifying a major product revision.

F = Fix level, identifying a new supported revision of the software.

I = Internal fix level, identifying a special software release that does
not correspond to a normal MIT cycle.  The Verification Test does not
check this field, but it is displayed in all version numbers.


NOTE If you have assigned a lockword to the ADMIN.PPC.SYS file, remove it before running the verification test. Otherwise, the test will be unable to open the file to check the version and will return an error.
The files are listed on the screen when the test is complete. An example of this display is shown on the next page. IMAGE/3000 Version=C.00.81 V/3000 Version=B.05.12 Forms file : ADFRM000.PPC.SYS Version=A.05.00.000 Data file : ADMENUS.PPCUTIL.HPOFFICE Version=A.05.00.000 Program file: ADMIN.PPC.SYS Version=A.05.00.000 Data file : ALLDBIN.PPCUTIL.HPOFFICE Version=A.05.00.000 Data file : DHDPGINP.PPCUTIL.HPOFFICE Version=A.05.00.000 Data file : DHDPMAP.PPCUTIL.HPOFFICE Version=A.05.00.000 Data file : DHDPMODS.PPCUTIL.HPOFFICE Version=A.05.00.000 Program file: DICINIT.PPC.SYS Version=A.05.00.000 Program file: DICTCONV.PPC.SYS Version=A.05.00.000 Program file: HDPBATCH.PPC.SYS Version=A.05.00.000 Catalog file: HDPHC000.PPC.SYS Version=A.05.00.000 Program file: HDPLOAD.PPC.SYS Version=A.05.00.000 Catalog file: HDPMC000.PPC.SYS Version=A.05.00.000 Program file: HPUNLD.PPC.SYS Version=A.05.00.000 Program file: HDPUTIL.PPC.SYS Version=A.05.00.000 Program file: HDSP.PPC.SYS Version=A.05.00.000 Program file: HDSPNS.PPC.SYS Version=A.05.00.000 Data file : SAMPL1IN.PPCUTIL.HPOFFICE Version=A.05.00.000 Program file: TRANS.PPC.SYS Version=A.05.00.000 Forms file : TRFRM000.PPC.SYS Version=A.05.00.000 Dictionary : HDPDIC.PPCUTIL.HPOFFICE Version=A.05.00.000 Dictionary : HDPENV.PPCUTIL.HPOFFICE Version=A.05.00.000 Information Access verified correctly; Version=A.05.00.000 If the MPE/XL version of Access Server is installed, the following additional files will be listed: Program file: XL.PPC.SYS Version=A.05.10.000 Data file : HDSPFILE.NET.SYS Version=A.05.10.000 Data file : HDSPMAST.NET.SYS Version=A.05.10.000 Data file : HDSPSERV.NET.SYS Version=A.05.10.000 The Go/No Go Test The Go/No Go Test exercises the minimum functions of Access Server to ensure that basic operation is possible. The Go/No Go test checks basic functions of Access Server. The following operations are performed: * A table is opened. * The table is closed as a saved table. * The saved table is deleted. * Interaction is terminated. To run the Go/No Go test, type the UDC :GONOGO or :RUN HDPBATCH.PPC.SYS;STDIN="DHDPGINP.PPCUTIL.HPOFFICE" Logging With HP OfficeShare Networking or Basic Serial Connections You can turn on host logging of datacomm packets transferred between the PC and the host HP 3000 by creating a LINKLOG.ACC file in the subdirectory where Access PC resides. Enter the following DOS commands in command mode or in a command file. :COPY CON LINKLOG.ACC <CR> <CTRL Z><CR> If your connection to the HP 3000 is basic serial, logging will be to file LINKLOG in your logon group. If you are connected to the HP 3000 through HP OfficeShare, logging will be to file HDSPNSLG in your logon group. Remember to delete PC file LINKLOG.ACC after you have obtained the desired host log file. LINKLOG.ACC is also used for logging PC software internal status, and consumes PC disc space if it continues to exist. Using HDSPNS IPC Logging. Alternatively for HP OfficeShare, you can build the file HDSPNSLG in the group and account that the user will log onto. HDSPNS will see the file and rebuild the file with the proper attributes (such as the correct record size). To turn on HDSPNS IPC logging, enter the following command from the correct logon group and account: :BUILD HDSPNSLG To view the file, use FCOPY. For example: :FCOPY FROM=HDSPNSLG;TO=*LP;HEX;CHAR Error Messages Error messages and recovery procedures are listed in the Information Access Server: Error Messages manual.
NOTE If an error is detected by a test, run the test again after correcting the problem to ensure that no other errors occur.


MPE/iX 5.0 Documentation