Review the Software AG Product Delivery Report that accompanies the release package before restoring the release data to disk. Information in this report supersedes the information in this documentation.
The installation medium contains the following data sets in the sequence indicated in the report:
| Data Set | Contents |
|---|---|
| AVIvrs.LOAD | AVI load modules |
| AVIvrs.SRCE | AVI source modules |
| AVIvrs.INPL | SYSAVI objects |
| AVIvrs.ERRN | SYSAVI error messages |
where vrs in data set names represents the version, revision, and system maintenance level of the product.
The configuration file, configuration module, and client component of the Adabas System Coordinator must already be installed as indicated in the following checklist before any attempt is made to install Adabas Vista:
| Step | Description |
|---|---|
| 1 | Load the Adabas System Coordinator configuration file |
| 2 | Build the Adabas System Coordinator configuration module CORCFG |
| 3 | Build the modified Adabas link module by including the Adabas System Coordinator client component |
The installation of these components is described in detail in the Adabas System Coordinator documentation.
Once the required Adabas System Coordinator components have been installed, you can proceed to install Adabas Vista. The following checklist identifies the steps necessary to successfully complete the installation:
| Step | Description |
|---|---|
| 1 | Restore the Adabas Vista libraries and other items from the installation medium |
| 2 | Prepare SYSAVI |
| 3 | Enable the client process |
| 4 | Enable the database process |
| 5 | Enable the Adabas System Coordinator daemon process |
Following is the general Adabas Vista installation procedure. The actual installation depends on your particular requirements and the specific contents of the release package provided by Software AG for your site. Information in the release package is intended for your system. If that information differs from the information in this section, use the release package information or contact Software AG technical support for assistance.
If you are using System Maintenance Aid (SMA), refer to the SMA documentation (included on the current edition of the Natural documentation CD). If you are not using SMA, perform steps 1a, 1b and 1c as described in this section:
Note:
If the data sets for more than one product are delivered on the
medium, the data set COPY.JOB contains the JCL to unload the data sets for all
delivered products from the medium to your disk. After that, you will have to
perform the individual install procedure for each
component.
The data set COPY.JOB (label 2) contains the JCL to unload all other existing data sets from medium 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=<Tnnnnn>), // LABEL=(2,SL) //SYSUT2 DD DSN=<hilev>.COPY.JOB, // DISP=(NEW,CATLG,DELETE), // UNIT=3390,VOL=SER=<vvvvvv>, // SPACE=(TRK,(1,1),RLSE), // DCB=*.SYSUT1 //SYSPRINT DD SYSOUT=* //SYSIN DD DUMMY //
where: <hilev> is a valid high level qualifier <Tnnnnn> is the tape number <vvvvvv> is the desired volser
Modify the COPY.JOB to conform with your local naming conventions and set the disk space parameters before submitting this job:
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 data sets from the medium to your disk.
The Adabas Vista Online Services (SYSAVI) objects are delivered on the Adabas Vista distribution medium.
To prepare SYSAVI:
Use your everyday Natural INPL job to load the administration tool (Natural application SYSAVI) and associated message texts into your Natural system. For reference a sample Natural INPL job called CORI061 can be found with the sibling System Coordinator product in the jobs distribution file. The INPL job’s work file 1 must reference the distribution file AVIvrs.INPL and work file 2 must reference AVIvrs.ERRN.
Note:
If you use Natural Security in this system, define the libraries
SYSAVI and SYSMVvrs (where vrs is the level you are installing, for
example 821) and protect as you require. You may define MENU as the startup
transaction for SYSAVI. However, you must not define a startup transaction for
SYSMVvrs.
2. Use the following parameter to define the Natural session where SYSAVI is to be used:
LFILE=(152,dbid,fnr<,passw><,ciph>)
where dbid and fnr define the location of the Adabas System Coordinator configuration file.
Alternatively, assemble the Natural parameter module with
NTFILE,ID=152,DBID=dbid,FNR=fnr
To enable the Adabas Vista client process
for the Adabas System Coordinator:
make the modified Adabas link module available (COMPLIB for Com-plete, DFHRPL for CICS, STEPLIB for all other client systems);
make the generated configuration module CORCFG available (COMPLIB for Com-plete, STEPLIB for all other client systems); and
make the Adabas System Coordinator load library available (COMPLIB for Com-plete, STEPLIB for all other client systems).
for Adabas Vista:
make the Adabas Vista load library available (COMPLIB for Com-plete, STEPLIB for all other client systems).
To enable the Adabas Vista database process
for the Adabas System Coordinator:
make the Adabas System Coordinator load library available (STEPLIB).
for Adabas Vista:
set the Adabas parameter ADARUN
VISTA=YES.
Note:
This step is required only if you intend to run clustered
applications with dynamic transaction routing across multiple operating system
images in an IBM sysplex environment.
To enable the Adabas Vista System Coordinator daemon process
Add the control statement PRODUCT=AVI to the
DDCARD input of the startup procedures for the Adabas System Coordinator
daemon.
Make the Adabas Vista load library available to the Adabas System Coordinator daemon (STEPLIB).