This section describes the contents of the distribution medium and the Software AG product prerequisites.
Note:
For information regarding Software AG product compatibility with IBM
platforms and any IBM requirements for Software AG products, please review the
Product Compatibility
for IBM Platforms web page.
This document covers the following topics:
This document refers only to dataset names, so the information presented here is applicable to each type of medium.
Note:
Most parts of the ASF installation can be performed with Software
AG's System Maintenance Aid (SMA). Refer to the SMA
documentation for more details.
| Data Set Name | Contents | Format |
|---|---|---|
| ASFvrs.INPL | ASF programs and messages. | INPL/OBJH |
| ASFvrs.SYS1 | ASF-DATA | ADALOD |
| ASFvrs.SYS2 | ASF-PROFILES (Profiles and Help Texts) | ADALOD |
| ASFvrs.HELP | ASF-PROFILES (Help Texts for upgrade installation only.) | ADALOD |
| ASFvrs.JOBS | ASF Installation Jobs (z/OS and BS2000 only) | SOURCE |
| ASFvrs.LIBJ | ASF Installation Jobs (z/VSE only) | SOURCE |
| ASFvrs.TAPE | ASF Installation Jobs (z/VM only) | SOURCE |
(v = version, r = release, s = SM level)
Following operating systems are supported:
This section explains how to:
Copy data set COPY.JOB from medium to disk.
Modify the data set according to your local naming conventions.
You can use the modified data set to copy all data sets from medium to disk. You will then need to perform the individual install procedure for each component.
Note:
If you are using SMA, please refer to the chapter Installing
Software AG Products with SMA in the System Maintenance
Aid documentation. If you are not using SMA, please follow the
instructions below.
Step 1a: Copy Data Set COPY.JOB from Medium to Disk (SMA Job Number Tnnn).
Step 1b: Modify COPY.JOB to Local Naming Conventions.
Step 1c: Submit COPY.JOB.
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 medium number.
<vvvvvv> is the desired volser.
There are three parameters to set before you can submit 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 medium to your disk.
To position the medium for the TAPE LOAD command, calculate the number of medium marks as follows:
If the sequence number of ASFnnn.TAPE, as shown by the Software AG Product Delivery Report, is n, you must position over 3n - 2 medium marks (that is, FSF 1 for the first dataset, FSF 4 for the second, etc.).
Access the disk that is to contain the ASF installation files as disk "A" or use the Shared File System (SFS).
Ask the system operator to attach a medium drive to your virtual machine at address X'181' and mount the ASFnnn installation medium.
Position the medium by issuing the CMS command:
TAPE FSF fsfs
where fsfs is the number of medium marks and is calculated as described above.
Load the ASF installation material by issuing the CMS command:
TAPE LOAD * * A
Keep the medium drive attached to your virtual machine, because the medium is still needed during the installation procedure.
This section explains how to:
Copy data set COPY.JOB from medium to disk.
Modify this member according to your local naming conventions.
The JCL in this member is then used to copy all data sets from the medium to disk.
If the data sets for more than one product are delivered on the medium, the member COPYTAPE.JOB contains JCL to unload the data sets for all delivered products from the medium to your disk, except the data sets that you can directly install from medium, for example, INPL objects.
You can use the modified data set to copy all data sets from medium to disk. You will then need to perform the individual install procedure for each component.
Note:
If you are using SMA, please refer to Installing Software AG
Products with SMA in the System Maintenance Aid
documentation. If you are not using SMA, please follow the instructions
below.
Step 1: Copy Data Set COPYTAPE.JOB from Medium to Disk.
Step 2: Modify COPYTAPE.JOB.
Step 3: Submit COPYTAPE.JOB.
The data set COPYTAPE.JOB (file 5) contains the JCL to unload all other existing data sets from medium to disk. To unload COPYTAPE.JOB, use the following sample JCL:
* $$ JOB JNM=LIBRCAT,CLASS=0, + * $$ DISP=D,LDEST=(*,UID),SYSID=1 * $$ LST CLASS=A,DISP=D // JOB LIBRCAT * ***************************************** * CATALOG COPYTAPE.JOB TO LIBRARY * ***************************************** // ASSGN SYS004,nnn <------ medium address // MTC REW,SYS004 // MTC FSF,SYS004,4 ASSGN SYSIPT,SYS004 // TLBL IJSYSIN,’COPYTAPE.JOB’ // EXEC LIBR,PARM=’MSHP; ACC S=lib.sublib’ <------- for catalog /* // MTC REW,SYS004 ASSGN SYSIPT,FEC /* /& * $$ EOJ
where nnn is the medium address, and lib.sublib is the library and sublibrary of the catalog.
Modify COPYTAPE.JOB to conform with your local naming conventions and set the disk space parameters before submitting this job.
Submit COPYTAPE.JOB to unload all other data sets from the medium to your disk.
Release mediums available to Software AG affiliates contain all Adabas product options. The affiliates use these release mediums to create custom installation mediums for customers according to contract agreements.
For specific information about your particular release medium, refer to the Installation Notes delivered with the installation medium.
Installation Using SMA
Installation Not Using SMA
If you are installing Adabas using the Software AG System Maintenance Aid (SMA), refer to the System Maintenance Aid documentation and to the information provided with the installation medium for specific installation instructions.
If you are not using SMA, copy the data sets from medium to disk using the procedure described below:
Step 1: Copy the Library SRVnnn.LIB from Medium to Disk.
Step 2: Copy the Procedure COPY.PROC from Medium to Disk.
Step 3: Copy all Product Files from Medium to Disk.
Note:
This step is not necessary if you have already copied the
library SRVnnn.LIB from another Software AG medium. For more
information, refer to the element #READ-ME in this library.
The library SRVnnn.LIB is stored on the medium as the sequential file SRVnnn.LIBS containing LMS commands. The current version nnn can be obtained from the Software AG Product Delivery Report. To convert this sequential file into an LMS library, execute the following commands:
/IMPORT-FILE SUPPORT=*TAPE(FILE-NAME=SRVnnn.LIBS, - / VOLUME=<volser>, DEV-TYPE=<tape-device>) /ADD-FILE-LINK LINK-NAME=EDTSAM, FILE-NAME=SRVnnn.LIBS, - / SUPPORT=*TAPE(FILE-SEQ=3), ACC-METH=*BY-CAT, - / BUF-LEN=*BY-CAT, REC-FORM=*BY-CAT, REC-SIZE=*BY-CAT /START-EDT @READ ’/’ @SYSTEM ’REMOVE-FILE-LINK EDTSAM’ @SYSTEM ’EXPORT-FILE FILE-NAME=SRVnnn.LIBS’ @WRITE ’SRVnnn.LIBS’ @HALT /ASS-SYSDTA SRVnnn.LIBS /MOD-JOB-SW ON=1 /START-PROG $LMS /MOD-JOB-SW OFF=1 /ASS-SYSDTA *PRIMARY
<tape-device> = device type of the medium, for example, TAPE-C4.
<volser> = VOLSER of medium (see Software AG Product Delivery Report).
Call the procedure P.COPYTAPE in the library SRVnnn.LIB to copy the procedure COPY.PROC to disk:
/CALL-PROCEDURE (SRVnnn.LIB,P.COPYTAPE), - / (VSNT=<volser>, DEVT=<tape-device>)
If you use a TAPE-C4 device, you can omit the parameter DEVT.
Enter the procedure COPY.PROC to copy all Software AG product files from medium to disk:
/ENTER-PROCEDURE COPY.PROC, DEVT=<tape-device>
If you use a TAPE-C4 device, you can omit the parameter DEVT. The results of this procedure are written to the file L.REPORT.SRV.
The following environment is required to install ASF:
Adabas Version 7 or above.
Natural Version 4.2 or above.
Adabas Online Services.
We recommend you to install ASF in a central service database containing service programs for the whole Adabas environment.
The following examples show the calculation of disk requirements for ASF-DATA and ASF-PROFILES. Also the minimum disk requirements for the Natural system file are listed.
The values shown are for a 3390 disk, on which the DATA block size is 4820 bytes and the ASSO block size is 2004 bytes. The RABNSIZE is 3. The block sizes of DATA and ASSO on all supported disks, as well as the cylinder size of the disks, are listed in Appendix A of the Adabas Operations documentation.
You can use the AOS "space calculation" function for the calculation of your own disk requirements.
This section covers the following topics:
For the calculation of MAXISN and the required disk space, it is important to n ote that the following Nucleus information is stored in ASF-DATA:
A record is created for every database
An additional record is created for every file
The number of records created is (1 database + 50 files) * 365 days = 18615 records. Therefore MAXISN can be set to 18615. The average compressed record length is 400 bytes, and the padding factor is 3%. The number of different values per record is 1, so the number of different values in the file is 18615. The average length of the descriptor value is 84 bytes.
| Area | Size (blocks) | Size (cylinders) |
|---|---|---|
| AC | 28 | 1 |
| NI | 853 | 3 |
| UI | 42 | 1 |
| DS | 1693 | 11 |
The number of records created is (10 databases + 10*50 files) * 3 stores per day * 365 days = 558450 records. Therefore MAXISN can be set to 558450. The average compressed record length is 400 bytes, and the padding factor is 3%. The number of different values per record is 1, so the number of different values in the file is 558450. The average length of the descriptor value is 84 bytes.
| Area | Size (blocks) | Size (cylinders) |
|---|---|---|
| AC | 837 | 3 |
| NI | 25569 | 74 |
| UI | 1209 | 5 |
| DS | 50769 | 309 |
This file is used for storing profile information. For each profile, 10 records are generated. The maximum length of a record before compression is 3600 bytes.
There are 10 profiles, so MAXISN is 10 * 10 = 100. The average compressed record length is 100 bytes, and the padding factor is 3%. The number of different values in the file is 400. The average length of the descriptor value is 38 bytes.
| Area | Size (blocks) | Size (cylinders) |
|---|---|---|
| AC | 1 | 1 |
| NI | 9 | 1 |
| UI | 2 | 1 |
| DS | 1 | 1 |
There are 100 profiles, so MAXISN is 100 * 10 = 1000. The average compressed record length is 100 bytes, and the padding factor is 3%. The number of different values in the file is 4000. The average length of the descriptor value is 38 bytes.
| Area | Size (blocks) | Size (cylinders) |
|---|---|---|
| AC | 2 | 1 |
| NI | 84 | 1 |
| UI | 3 | 1 |
| DS | 1 | 1 |
ASF requires the following additional disk space in the Natural System File:
| Area | Size (blocks) |
|---|---|
| UI | 15 |
| NI | 280 |
| DS | 2000 |
The value of TOPISN must also be increased by 8500.