Adabas Review can be installed in local mode in the Adabas address space, or as a hub (server) in its own address space with an interface (client) located in the address space of the Adabas being monitored. The procedures are the same except as noted.
Adabas Review is installed in two phases. This document describes Phase 1, which comprises all the steps that are independent of any particular TP monitor environment, as follows:
To complete Phase 1 of the installation, read the sections in Phase 1 that apply to the type of installation you have chosen and follow the steps described in those sections in order they are described in this document.
Phase 2, which comprises the steps that are specific to the TP monitor being used, is described in Installation: Phase 2
If you are using SMA, refer to the System Maintenance Aid documentation, included in the current edition of the Natural documentation CD.
If you are not using SMA, use the following steps to download all product data sets from tape to disc.
The data set COPY.JOB (Label 2) contains the JCL to unload all other existing data sets from tape to disk. To unload COPY.JOB, use the following sample JCL:
//SAGTAPE JOB SAG,CLASS=1,MSGCLASS=X //* --------------------------------- //COPY EXEC PGM=IEBGENER //SYSUT1 DD DSN=COPY.JOB, // DISP=(OLD,PASS), // UNIT=(CASS,,DEFER), // VOL=(,RETAIN,SER=tape-volume), // LABEL=(2,SL) //SYSUT2 DD DSN=hlq.COPY.JOB, // DISP=(NEW,CATLG,DELETE), // UNIT=3390,VOL=SER=volume, // SPACE=(TRK,(1,1),RLSE), // DCB=*.SYSUT1 //SYSPRINT DD SYSOUT=* //SYSIN DD DUMMY //
where:
hlq = valid high level qualifier
tape-volume = the tape volume name (e.g., T12345)volume = the desired target volume on disk.
Modify the COPY.JOB to conform with your local naming conventions. Set the disk space parameters before submitting this job, as follows:
Set HILEV to a valid high level qualifier.
Set LOCATION to a storage location.
Set EXPDT to a valid expiration date.
Submit COPY.JOB to unload all other existing data sets from the tape to your disk.
This section applies to both local and hub mode installations. It includes the following steps:
Note:
There is no longer a SYSREV or SYSREVUP library. The entire
application is now contained in the SYSREVDB library.
INPL the Adabas Review programs and DDMs from the INPL data set to your Natural system files.
You may use any of your site-dependent Natural INPL JCL. Sample job REVINPL is provided in the Adabas Review jobs library.
Include the following parameter settings in the Natural profile:
| Parameter | Requirement |
|---|---|
| LS=250 | minimum |
| PS=80 | minimum |
| MADIO=5000 | minimum |
| MAXCL=0 | minimum |
| ESIZE=40 | minimum |
| ADAPRM=ON | required. ADAPRM=ON must be specified in order to use Adabas Review to report on Natural information. |
| NTWORK(7),AM=PC | required for PC downloads. NTWORK is a Natural macro used to define the work file(s) to be used; AM is the access method. For more information, see the Natural documentation. |
| NTPRINT(1) | Review uses Natural printer 1 to generate report display programs in the Natural source area. For more information see the Natural documentation. |
Add a Natural NTFILE definition for the physical database ID and file number of the Adabas Review repository file as follows:
NTFILE 241,dbid,fnr
Replace dbid and fnr with the database ID and file number, respectively, of the Adabas Review repository.
Note:
The Adabas Review repository may not reside on a database with a
database ID (DBID) of 255. If the database ID is 255, Adabas Review cannot be
accessed in local or hub mode. However, a database with a DBID of 255 can send
data to a hub.
Reassemble and link the NATPARM module to your Natural nucleus.
If Natural Security is installed:
Define the SYSREVDB library for the Adabas Review system.
Note:
If the Adabas Review application SYSREVDB is made private (i.e.,
the parameter PEOPLE=Y is specified), each user of Adabas Review must be linked
to the SYSREVDB application.
Define Adabas Review DDMs to Natural Security as public DDMs:
REVIEW-ADABAS-V45-CLOG REVIEW-FNAT REVIEW-ADABAS-v45-SYSTEM
This section applies to both local and hub mode installations.
The Adabas Review repository is a system file used for storing descriptions of interactive reports, target definitions, and for saving historical data accumulated by Adabas Review reports. Any Adabas file may be used to contain the Adabas Review repository. The corresponding file number should also be reflected in the NATPARMs used to invoke Adabas Review.
Hub mode only: The Adabas Review repository can be created on any database accessible to Natural. It does not need to be on a database that is monitored by the Adabas Review hub.
Notes:
This step includes the following substeps:
Before submitting the job REVLOAD provided in the Adabas Review jobs library, change:
the DBID=dbid parameter in the two ADARUN statements to reflect the DBID number of the database that will contain this file;
Note:
The Adabas Review repository may not reside on a database with a
database ID (DBID) of 255. If the database ID is 255, Adabas Review cannot be
accessed in local or hub mode. However, a database with a DBID of 255 can send
data to a hub.
the SVC=svc parameter of the same two ADARUN statements to reflect the number of the SVC used for the database defined in the above step; and
the ADALOD LOAD FILE=fnr statement to reflect the number of the file that will contain the Adabas Review file.
Load the Adabas Review repository file using the job REVLOAD modified in step 1.
If you used the same repository file for a version of Adabas Review older than this release, use the EXPAND3 job in the JOBS library to convert the repository.
If you used the same repository file for a version of Adabas Review older than this release, Adabas Review 4.5 requires that you convert your history data prior to running any new reports in 4.5. For complete information on doing this, read Migration from Previous Versions.
This section includes the following steps:
Read ADARUN Parameters for information about the relevant ADARUN parameters. Then modify the Adabas ADARUN parameters to include the following:
local mode only:
ADARUN PROGRAM=ADANUC ADARUN REVIEW=LOCAL
hub mode only for each database to be monitored by Adabas Review:
ADARUN PROGRAM=ADANUC ADARUN REVIEW=hubid ADARUN UEX5=user-exit (optional)
where hubid is the Adabas Review hub ID and UEX5 is optional (see Operations).
Perform one of the sets of steps below, depending on whether you are installing Adabas Review in local mode or in hub mode:
Before you modify the Adabas startup JCL, you may need to increase the REGION parameter for the Adabas nucleus job step to accommodate Adabas Review. An increase of one megabyte is normal.
This section covers the following topics:
The RVUALT DD statement refers to the data set that contains the alternate history file. You may use the same data set you used for earlier versions. .
The MAKEALT member of the jobs library contains sample JCL to create a RVUALT data set.
 |
Warning: Do not use IEFBR14 to allocate RVUALT. |
If Adabas Review is installed on multiple databases, a RVUALT data set must be allocated for each database.
Refer to the Operations for RVUALT guidelines.
The RVUAUT1 and RVUAUT2 DD statements refer to the data sets that contain the report definitions for autostarted reports. These statements point to members of a PDS; however, they may be defined to point to sequential data sets if desired.
You can use the distributed RVUAUT1 and RVUAUT2 files from earlier versions.
Note:
In a future release of Adabas Review, RVUAUT2 will no longer be supported.
RVUAUT1 only will be used for autostarted reports.
To modify the Adabas startup JCL for local mode:
Add the following DD statements to the Adabas startup JCL, replacing the vrs with the current version, revision, and system maintenance level number for Adabas Review:
//RVUEXI DD DISP=SHR,DSN=REVvrs.SRCE(RVUEXI) //RVUEXP DD SYSOUT=X,LRECL=80 //RVUALT DD DISP=SHR,DSN=REVvrs.ALTHIST //RVUAUT1 DD DISP=SHR,DSN=REVvrs.SRCE(AUT1PARM) //RVUAUT2 DD DISP=SHR,DSN=REVvrs.SRCE(AUT2PARM) //RVUCARD DD DISP=SHR,DSN=REVvrs.SRCE(RVUCARD) //RVUFLD DD DISP=SHR,DSN=REVvrs.SRCE(USRPARM) //RVUPARM DD DUMMY //RVUPRT00 DD SYSOUT=X,LRECL=133 //RVUPRT01 DD SYSOUT=X,LRECL=133 //RVUPRT02 DD SYSOUT=X,LRECL=133 //RVUPRT03 DD SYSOUT=X,LRECL=133
Add the Adabas Review load library to the Adabas STEPLIB concatenation.
Note:
To retain APF authorization for Adabas, you must authorize the
Adabas Review load library as well when it is added to the Adabas STEPLIB
concatenation.
To install the Adabas Review client interface, repeat the following
instructions for each database to be monitored. Note that each database to be
monitored must use the same SVC as the Adabas Review hub.
Apply the required ZAPs.
Ensure that an unmodified ADALNK is available to Adabas in the Adabas load library or in a library concatenated before the Adabas load library.
ADALNK is loaded by Adabas to send information to the Adabas Review hub. Link routine exits such as RDBLXMVS or UEXB are not useful for the process of sending data to the hub and create unnecessary overhead when included in the ADALNK.
Put ADALNKs that include exits into another library.
Modify the Adarun parameters of the database.
If the Adabas Adarun parameter LOGCLEX=Y is specified to write the Review specific Command Log Extension (CLEX) to the command log, the Adabas Review library must be available in the client address space. If Review modules are not available, the warining message ARVU20 is issued.
Restart Adabas.
To install the Adabas Review Hub, complete the steps described in this section:
Use the sample JCL member MAKEALT. Do not use IEFBR14 to allocate RVUALT.
This alternate history file is used to contain history information if Adabas Review is unable to access the Adabas Review repository. You may use the same data set you used for Adabas Review 4.1 or 4.2. Refer to Operations for RVUALT guidelines.
Correct any library names or file names.
Modify the ADARUN parameter REVIEW=hubid to reflect the target ID you plan to use for the Adabas Review hub.
Modify the ADARUN parameter SVC to reflect the correct SVC number. This SVC must be the same as that used by the sending Adabas nuclei.
The ADARUN parameters supplied in the sample JCL member HUBJCL are the only ones recognized for setting up the hub nucleus. Read ADARUN Parameters for information about these ADARUN parameters.
Note:
Software AG recommends that you set the dispatching priority of
the Adabas Review hub higher than that of the sending Adabas nuclei.
The RVUALT DD statement refers to the data set that contains the alternate history file.
The RVUAUT1 and RVUAUT2 DD statements refer to the data sets that contain the report definitions for autostarted reports. These statements point to members of a PDS; however, they may be defined to point to sequential data sets if desired.
You can use the distributed RVUAUT1 and RVUAUT2 files from Adabas Review 4.1.
Note:
The reports contained in the RVUAUTn files have a TARGET=
parameter that specifies the database that the report will monitor. The default
setting is TARGET=001. You may wish to change this setting.
Note:
The STEPLIB needs to be APF-authorized.
The following optional installation procedures may be completed as part of Phase 1 of the Adabas Review installation:
From within Adabas Native SQL, use the global ADACALL statement with the LAST parameter to specify that the Adabas call will use the seventh parameter.
Refer to the Adabas Native SQL documentation.
This (optional) step applies both to local and hub mode installations.
To report on Natural activity from a batch Natural job:
Modify and relink the Adabas link routine for batch/TSO as described in Install Adabas Review under Batch/TSO .
