Adabas Review can be installed in local mode in the Adabas address space, or a hub (server) located 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 section of the documentation describes phase one, which comprises all the steps that are independent of any particular TP monitor environment.
To complete phase 1 of the installation, include all steps that apply to the type of installation you have chosen and follow them in order.
Phase 2, which comprises the steps that are specific to the TP monitor being used, is described in section Installation (Phase 2).
This document covers the following topics:
Note:
Instructions for copying the tape contents to disk are provided in
Copying the Tape
Contents.
This section applies to both local and hub mode installations. It includes the following steps:
Note:
The entire Adabas Review application is stored in the SYSREVDB
library. User profiles are stored in the SYSREVDU 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 JCS. Sample job REVINPL.X is provided in the Adabas Review library.
To create a Natural profile using the SYSPARM facility:
Include the following parameter settings in the Natural profile:
| Parameter | Requirement |
|---|---|
| LS=250 | minimum |
| PS=80 | minimum |
| MADIO=5000 | minimum |
| MAXCL=0 | minimum |
| ESIZE=64 | minimum |
| ADAPRM=ON | required in order to for 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) | Adabas Review uses Natural printer 1 to generate report display programs in the Natural source area. For more information, see the Natural documentation. |
| COMP | Parameters for Com-plete. Set the value for NTHSIZE greater than 2400. |
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, complete the following steps:
Define the SYSREVDB library for the Adabas Review system and the SYSREVDU library for the Adabas Review user profiles to Natural Security.
Note:
If the Adabas Review application SYSREVDB is made private (i.e.,
the parameter People-protected=Y is specified), each user of Adabas Review must
be linked to the SYSREVDB application.
Define Adabas Review Files to Natural Security as public DDMs:
REVIEW-ADABAS-Vvrs-CLOG REVIEW-FNAT REVIEW-ADABAS-Vvrs-SYSTEM
where vrs is the new Adabas Review version, release and SM.
This procedure 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.
This section includes the following substeps:
Important:
Users loading a new Adabas Review repository should run Steps 1
and 2 only and omit Step 3. Users converting the Adabas Review repository from
a previous release should omit Steps 1 and 2 and run Step 3
only.
Before submitting the job REVLOAD.X provided in the Adabas Review sublibrary, change:
the DATABASE=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.X as modified in step 1.
If you used the same repository file for a version of Adabas Review older than this release, Adabas Review requires that you convert your repository file and history data prior to running any new reports in this release of Adabas Review. For complete information on doing this, read Migration from Previous Versions .
To install Adabas Review under Adabas, complete the following steps:
Use the sample JCS member DBFILES.X in the Adabas Review sublibrary to create the data sets necessary to store autostarted report definitions, parameters, and the alternate history file.
To create Adabas Review-specific data sets:
Modify DBFILES.X by replacing
| s | with the current system maintenance level of Adabas Review |
| nnnn | with the starting track number for each step in the job |
| vvvvvv | with the tape volume serial number |
Execute the modified DBFILES.X.
For information about the relevant ADARUN parameters, read ADARUN Parameters for Adabas Review.
Modify your existing Adabas ADARUN parameters to include the following:
local mode only:
ADARUN REVIEW=LOCAL
hub mode only for each database to be monitored by Adabas Review:
ADARUN REVIEW=hubid ADARUN UEX5=user-exit (optional)
where hubid is the Adabas Review hub ID and UEX5 is optional. For more information, read REVUEX5: Adabas Review Hub Event Handler (Adabas Exit 5).
This section describes how to modify the Adabas startup JCS for local mode and for hub mode.
To modify the Adabas startup JCS for local mode installations:
Before you modify the Adabas startup JCS, you may need to increase the available GETVIS in the Adabas partition to accommodate Adabas Review. An increase of 500K is normal.
RVUALT Considerations
RVUALT refers to the data set that contains the alternate history file. You may use the same data set you used for earlier versions.
If Adabas Review is installed on multiple databases, a RVUALT data set must be allocated for each database.
Refer to section RVUALT History File in Operations for RVUALT guidelines.
RVUAUT1 and RVUAUT2 Considerations
RVUAUT1 and RVUAUT2 refer to the data sets that contain the report definitions for autostarted reports.
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 startup JCS for local mode
Add the following statements to the Adabas startup JCS replacing
| vrs | with the current version, revision, and system maintenance level of Adabas Review |
| vvvvvv | with the tape volume serial number |
Note:
In Adabas Review, each logical unit (SYS number) is assigned to a
specific Adabas Review function (see Assigning
Logical Units). If these logical units conflict with the assignments made in
the Adabas data container procedure or the nucleus startup JCS, we recommend
you change the SYS number allocation for Adabas to a number range above 50 in a
copied procedure for use by the Adabas Review Local Nucleus. The currently assigned
logical units are as shown below:
// ASSGN SYS005,IGN RVUPARM - batch parameters // ASSGN SYS007,DISK,VOL=vvvvvv,SHR RVUAUT1, RVUAUT2, RVUFLD // ASSGN SYS008,DISK,VOL=vvvvvv,SHR RVUALT - alt history file // ASSGN SYS020,SYSLST RVUPRT0 - printer // ASSGN SYS021,SYSLST RVUPRT1 - printer // ASSGN SYS022,SYSLST RVUPRT2 - printer // ASSGN SYS023,SYSLST RVUPRT3 - printer // ASSGN SYS041,DISK,VOL=vvvvvv,SHR RVUCARD - GENCARD // ASSGN SYS006,DISK,VOL=vvvvvv,SHR RVUEXI - operating env parameters // ASSGN SYS019,SYSLST RVUEXP - EXI parameters printer * // DLBL RVUAUT1,'REVvrs.AUTO1',0 // EXTENT SYS007,vvvvvv,1,0,nnnn,5 // DLBL RVUAUT2,'REVvrs.AUTO2',0 // EXTENT SYS007,vvvvvv,1,0,nnnn,5 * // DLBL RVUCARD,'REVvrs.CARD.FILE',0 // EXTENT SYS041,vvvvvv,1,0,nnnn,5 * // DLBL RVUALT,'REVvrs.ALT.FILE',0 // EXTENT SYS008,vvvvvv,1,0,nnnn,30 * // DLBL RVUEXI,'REVvrs.EXI.PARAMETERS',0 // EXTENT SYS006,vvvvvv,1,0,nnnn,5 * // DLBL RVUFLD,'REVvrs.USER.FIELDS',0 // EXTENT SYS007,vvvvvv
Add the following statements to the Adabas startup JCS, replacing
| vrs | with the current version, revision, and system maintenance level of Adabas Review |
| vvvvvv | with the tape volume serial number |
Note:
In Adabas Review, each logical unit (SYS number) is assigned to a
specific Adabas Review function (see Assigning
Logical Units). If these logical units conflict with the assignments made in
the Adabas data container procedure or the nucleus startup JCS, we recommend
you change the SYS number allocation for Adabas to a number range above 50 in a
copied procedure for use by the Adabas Review Local Nucleus. The currently assigned
logical units are as shown below:
// ASSGN SYS005,IGN RVUPARM - batch parameters // ASSGN SYS007,DISK,VOL=vvvvvv,SHR RVUAUT1, RVUAUT2, RVUFLD // ASSGN SYS008,DISK,VOL=vvvvvv,SHR RVUALT - alt history file // ASSGN SYS020,SYSLST RVUPRT0 - printer // ASSGN SYS021,SYSLST RVUPRT1 - printer // ASSGN SYS022,SYSLST RVUPRT2 - printer // ASSGN SYS023,SYSLST RVUPRT3 - printer // ASSGN SYS041,DISK,VOL=vvvvvv,SHR RVUCARD - GENCARD // ASSGN SYS006,DISK,VOL=vvvvvv,SHR RVUEXI - operating env parameters // ASSGN SYS019,SYSLST RVUEXP - EXI parameters printer * // DLBL RVUAUT1,'REVvrs.AUTO1',0 // EXTENT SYS007,vvvvvv,1,0,nnnn,5 // DLBL RVUAUT2,'REVvrs.AUTO2',0 // EXTENT SYS007,vvvvvv,1,0,nnnn,5 * // DLBL RVUCARD,'REVvrs.CARD.FILE',0 // EXTENT SYS041,vvvvvv,1,0,nnnn,5 * // DLBL RVUALT,'REVvrs.ALT.FILE',0 // EXTENT SYS008,vvvvvv,1,0,nnnn,30 * // DLBL RVUEXI,'REVvrs.EXI.PARAMETERS',0 // EXTENT SYS006,vvvvvv,1,0,nnnn,5 * // DLBL RVUFLD,'REVvrs.USER.FIELDS',0 // EXTENT SYS007,vvvvvv
Modify the Adabas startup JCS to execute the Adabas Review procedure and add the Adabas Review sublibrary to the LIBDEF search chain.
To install the client interface in hub mode:
Repeat the following substeps for each database to be monitored.
Each database to be monitored must use the same SVC as the Adabas Review hub.
If the Adabas ADARUN parameter LOGCLEX=Y is specified to write the Adabas Review specific Command Log Extension (CLEX) to the command log, the Adabas Review library must be available in the client address space. If Adabas Review modules are not available, the warning message ARVU20 is issued.
Maintenance fixes are distributed in MSHP format. In order to apply these maintenance fixes, Adabas Review must be defined to MSHP as a product/component using the MSHP ARCHIVE process.
Modify and run the sample job stream ARCHIVE.X in the Adabas Review sublibrary to define Adabas Review to MSHP. Make sure you have specified the Adabas Review and the Adabas library in your MSHP job which applies the fixes for Adabas Review. For example:
// LIBDEF OBJ,SEARCH=(SMALIB.REVvrs,SMALIB.ADAvrs),TEMP
Complete the steps in this section to install the Adabas Review Hub.
When modifying the sample JCS member, be sure to:
Correct any library names or file names.
Modify the ADARUN parameters:
Modify the ADARUN parameter REVIEW to reflect the TARGET ID you wish 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 HUBJCS.X are the only ones recognized for setting up the hub nucleus. For information about these ADARUN parameters, read ADARUN Parameters for Adabas Review.
Note:
Software AG recommends that the dispatching priority of the Adabas Review
hub be set higher than that of the sending Adabas nuclei.
Verify that the RVUALT DLBL statement refers to the data set that contains the alternate history file.
The RVUALT or "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 RVUALT data set you used for earlier versions.
Refer to section Operations for RVUALT guidelines.
Verify that the RVUAUT1 and RVUAUT2 DLBL statements refer to the data sets that contain the report definitions for autostarted reports.
You can use the distributed RVUAUT1 and RVUAUT2 files from earlier versions.
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.
The RVUFLD DLBL statement refers to the data set that contains the user-defined field parameters.
Run the HUBJCS member you created in the previous step.
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.
