Installation verification procedure

Overview

Providing access to the Adabas Audit Data Retrieval application completes the installation of Adabas Audit Data Retrieval. This section contains an overview of what to do next to verify whether Adabas Audit Data Retrieval is running correctly.

Starting the STC (BETA97)

Check the LST parameters in the B97LSTxx to make sure that this member has been tailored correctly. For more information on LST parameters, see "How to use LST parameters".

Check the started task procedure (default name: BETA97) to make sure that is has been tailored correctly. For more information on the BETA97 STC procedure, see "Adabas Audit Data Retrieval started task procedures".

Then start the started task using the following console command:

S stcname

where stcname is the name of the started task procedure.

BETA97 started task JES message log (JESMSGLG)

+------------------------------------------------------------------------------------------+
|IRR813I NO PROFILE WAS FOUND IN THE STARTED CLASS FOR |
| BETA97 WITH JOBNAME BETA97. RACF WILL USE ICHRIN03. |
|IEF695I START BETA97 WITH JOBNAME BETA97 IS ASSIGNED TO USER BETA97 , GROUP NOACCESS |
|$HASP373 BETA97 STARTED |
|IEF403I BETA97 - STARTED - TIME=10.16.29 |
|IGD104I BETA.PARMLIB RETAINED, DDNAME=SYS00001 |
|IGD104I BETA.PARMLIB RETAINED, DDNAME=SYS00002 |
|IRM9151I B97LSTxx LOADED, SVC(nnn/PBSnnnn/epaddr) SSID(ssid) SYSNAME(sysname) SYSPLEX(sysp|
|IRM9151I BSA INITIALIZATION nnnnnn LEVEL: nn / PBSnnnn / PBSnnnn |
|IRM9151I CPU INFORMATION - TYPE: tttt ID: nnnn LPAR: l TLCPU: tccc CLCPU: cccc SLCPU: sccc|
|IRM9005I LICENSE FILE filename WILL BE USED |
|IRM9004I product HAS BEEN LICENSED FOR CUSTOMER: customername |
|... (more license information) |
|IRM9557I DATABASE INITIALIZATION WITH VERSION: PBSnnnn / PBSnnnn |
|IRM9506I DATABASE INITIALIZATION COMPLETE |
|IRM9506I ACTIVE DATABASES ARE: |
|IRM9506I DATABASE NAME ID HA-RBA HU-RBA STATUS |
|IRM9506I ----------------------------------------------------------------------- |
|IRM9506I BETA97.DB.SYNC 1000 0000000 0000000 OPN |
|IRM9506I BETA97.DB.LOG 1001 0000260 0000260 OPN |
|IRM9506I BETA97.DB.MAIN 1002 0003600 0003600 OPN |
|IRM9506I BETA97.DB.MAIN.KEY 1004 0001800 0001800 OPN |
|IRM9506I BETA97.DB.LIST.KEY 1006 0003600 0003600 OPN |
|IRM9506I BETA97.DB.LIST 1008 0003600 0003600 OPN |
|IRM9506I BETA97.DB.SPOOL1 1010 0003600 0003600 EMP |
|IRM9506I BETA97.DB.RELOD1 1011 0003600 0003600 EMP |
|IRM9506I BETA97.DB.CACHE1 1012 0018000 0018000 EMP |
|IRM9506I BETA97.DB.INDEX1 1013 0018000 0018000 EMP |
|IRM9506I BETA97.DB.GLOBL1 1014 0018000 0018000 EMP |
|IRM9506I BETA97.DB.ARC 1015 0007200 0007200 OPN |
|IRM9506I BETA97.DB.ARC.KEY 1017 0002700 0002700 OPN |
|IRM9506I BETA97.DB.MSG 1019 0003600 0003600 OPN |
|IRM9506I BETA97.DB.MSG.KEY 1020 0001800 0001800 OPN |
|IRM9506I BETA97.DB.NOTES.KEY 1021 0000900 0000900 OPN |
|IRM9506I BETA97.DB.NOTES 1022 0001800 0001800 OPN |
|IRM9506I BETA97.DB.SFR 1023 0003600 0003600 OPN |
|IRM9506I BETA97.DB.SFR.KEY 1025 0001800 0001800 OPN |
|IRM9506I BETA97.DB.LGF 1027 0003600 0003600 OPN |
|IRM9506I BETA97.DB.LGF.KEY 1028 0001800 0001800 OPN |
|IRM9506I ----------------------------------------------------------------------- |
|IRM9558I DATABASE FUNCTION WILL BE ACTIVATED AS MASTER / SHAREOPTION(NO) |
|... |
|IRM9265I SERVER(port/AAV): INIT TO TCPIP (V6R24) AND IPA ipaddress (n) SUCCESSFUL |
|IRM9260I SERVER(port/AAV) IS WAITING FOR WORK FOR BWE97 (taskname / IPA#n: ipaddress) |
+------------------------------------------------------------------------------------------+

What to check

Check the following:

  • Displayed levels are correct.

    Make sure that the BSA levels displayed in the JESMSGLG (message IRM9151I) are not lower than the ones named in the release notes.

  • Database status is okay.

    Make sure that all databases are available and that none of the databases has status ERR (error).

  • The BSA TCP/IP server is listening to specified TCP/IP port.

    Make sure that the message IRM9265I SERVER(port/AAV): INIT TO tcpipstc (VxRx) AND IPA ipaddress (n) SUCCESSFUL is present.

    Note: There may be an authorization problem if this message is not present (see "OMVS segment entry required for using TCP/IP").

Calling Adabas Audit Data Retrieval

To call the Adabas Audit Data Retrieval ISPF application, enter the TSO command TSO clistname or select Adabas Audit Data Retrieval from the modified ISPF panel.

What to check

Under option S.2, make sure that the Adabas Audit Data Retrieval subsystem options record contains the values you specified when running the installation REXX (see "Adabas Audit Data Retrieval subsystem definition (Option S.2)" in Adabas Audit Data Retrieval Administrator Guide).

Defining model spool files

Initially, Adabas Audit Data Retrieval requires one spool file of each type (SPOOL, CACHE, INDEX, GLOBAL, RELOAD). Additional spool files for each type can be allocated manually or they can be allocated by the system on the fly when it runs out of storage space in the existing spool files.

To enable Adabas Audit Data Retrieval to allocate additional spool files on the fly, use option D.1 to define model spool files for each type.

A model spool file does not require any storage space while its status is MODEL. We recommend that you define several models for each type.

For more information, see "Spool files" and following in Adabas Audit Data Retrieval Administrator Guide.

Further actions

Refer to "How does Adabas Audit Data Retrieval work" in Adabas Audit Data Retrieval Administrator Guide for an overview of how Adabas Audit Data Retrieval works and which further actions are required.