This section describes the INSTADA program for Adabas installation on z/VM systems. INSTADA is invoked internally by the INSTPROD program, which loads product files from installation tapes. INSTADA can also be invoked directly to define new databases. INSTADA must be run at the appropriate step of the z/VM or VM/GCS installation sequence, as described in the section Install Procedure.
The installation instructions for Adabas are documented in the section Install Procedure. The information in this section presumes that the reader has read and is familiar with that information.
Note:
INSTADA and ADAMAINT do not support the shared file system (SFS)
option or 2-byte DBIDs.
This section describes how to load the INSTADA program.
To load the INSTADA program:
Enter the following commands on the terminal:
TAPE FSF 1
TAPE LOAD * * filemode
—where filemode is the filemode of the minidisk where the TAPE LOAD command will place the output. After the TAPE LOAD command has completed, the following appears on your terminal:
VOL1ADAvrs REST HDR1ADAvrs.EXEC ADAvrs00010001 88160 000000000000IBM OS/VS 370 HDR2F008000008040DAF0300 /STEP001 B 61918 FILE ’INSTPROD EXEC C1’ COPIED. FILE ’INSTXED1 EXEC C1’ COPIED. R; T=0.03/0.10 15:18:23
The first line of the output is the volume serial number of the tape, followed by two lines of header information. The two files INSTPROD EXEC and INSTXED1 EXEC are used to create the online installation panels to unload the product files on the installation tape. These files are copied to the filemode minidisk that was specified in the TAPE LOAD command.
Enter the name of the EXEC that will perform the online installation procedure:
INSTPROD
This EXEC, in turn, invokes INSTADA to generate the online panels.
For already installed databases, you can run INSTADA to re-define the existing environment by entering the following command in place of INSTPROD:
ADAMAINT
This command presents the same online installation panel sequence as INSTPROD. However, instead of re-installing the database, ADAMAINT stores the new definition in the library. The new definition becomes effective only after each virtual machine re-accesses the library.
This section describes the panels that appear when either the INSTPROD or ADAMAINT command is entered.
Note:
Some panels and fields are not present for VM/GCS systems, as noted
in the text. The VM/GCS system is supported by Entire Net-Work, but not by
Adabas.
HH:MM:SS ***** software ag Online Installation ***** YYYY-MM-DD
- A D A B A S Installation - Panel 0
Parameter sets exist for the following Adabas identification numbers
Select a parameter set by marking any ID:
5
112
PF3 will reset modifications |
| Field | Description |
|---|---|
| ID (database ID) | To change the parameters of an existing database, enter any character next to the database number. For a new database, press Enter for the next screen. |
Note:
This panel appears only when databases have already been defined
using INSTPROD or
ADAMAINT.
This panel is for defining the requirements for the general Adabas environment. If an existing environment was selected on the previous panel, that database name, ID, and present values are displayed in the input fields of this and all following screens. If a new database is being installed, all input fields are empty.
HH:MM:SS ***** software ag Online Installation ***** YYYY-MM-DD
- A D A B A S Installation - Panel 1
Define your Adabas environment
Modify the following fields to meet your requirements:
Database name: VMESA-DATABASE112 Database id: 00112 Convert: NO
Logon IDs of the DB machine: XDB200 ID service machine: DBIDSERV
ID service machine target ID: 65535 Automatic restart: YES
System file numbers: 004 000 000 000 000 000 000 000
Maximum number of files: 020 Demo file numbers: 001 002 003
Update profile EXECs: YES RR Password for the D-disk: RAD
PF3 will reset modifications |
The following data can be entered on this screen:
| Field | Description |
|---|---|
| Database Name | Name assigned to the database. This name appears in the ADAREP report. |
| Database ID | Numerical identification to be assigned to the database. A value in the range 1-255 may be specified. |
| Convert | Change to YES if you are converting an existing database to Adabas. |
| Logon ID of the DB Machine | Logon of the Adabas virtual machine where the Adabas nucleus will be located. |
| ID Service Machine | ID of the ID table manager virtual machine. If not specified, the ID is DBIDSERV. |
| ID Service Machine Target ID | ID of the ID table manager virtual machine. |
| Automatic Restart (z/VM systems only) | If YES is specified, the ID table manager virtual machine restarts automatically if an abend occurs. |
| System File Numbers | The first entry is required and must be the checkpoint file. By entering a second number, control statements will be generated for the security file. All additional file numbers are optional. |
| Maximum Number of Files | Value in the range 5-255 representing the maximum number of files that can be loaded in the database. |
| Demo File Numbers | File numbers used to load the three demo files: EMPLOYEES, VEHICLES, and MISCELLANEOUS. If any one of these fields is set to zero, the respective demo file will not be loaded. |
| Update Profile EXECs | If YES is specified, the entries required for Adabas version 7 are added to your existing PROFILE EXEC. If NO is specified, an EXEC named “????” is generated, which may then be invoked from your PROFILE EXEC. |
| RR Password for the D-Disk | Enter the read-only password for the Adabas library minidisk where the installation tape is unloaded. |
When all correct values have been entered, press Enter to make the values effective. If you change values for an existing database and then decide to restore the old values, press PF3 before pressing Enter to restore all old values on the existing panel (other panels are not affected).
After pressing Enter to accept entered values, the prompt shown above appears at the bottom of each panel asking you to either confirm by pressing Enter again, or to press PF3 to abort the online installation procedure. In other words, you must press Enter twice following entry of each panel data to accept and confirm the entries, and then move to the next panel. If you decide that the values entered on the current panel are not valid, press PF3 to exit from the procedure and return to the z/VM environment.
On all subsequent screens, pressing PF3 to exit saves all values entered on previous panels, and restores any preexisting values on the current panel before exiting. If you press PF3 following the first Enter, you must reenter the INSTPROD or ADAMAINT command to complete the installation. An ID for the partially completed installation appears on the list in the first panel, which you can then select and continue.
The next panel, shown below, is used to define the environment for the ID table manager virtual machine.
Note:
This panel does not appear for VM/GCS systems.
HH:MM:SS ***** software ag Online Installation ***** YYYY-MM-DD
- A D A B A S Installation - Panel 2
Define your Adabas ID service machine
Modify the following fields to meet your requirements:
ID service machine target ID: 65535 Automatic restart: YES
ID service machine: DBIDSERV
Nodename: ITM65535 DBAVMID: SAGDBA
Net-work Resource ID: SAGNETWK
PF3 will reset modifications |
| Field | Description |
|---|---|
| ID Service Machine Target ID | Target ID Target ID of the ID table manager virtual machine. This value must be entered. |
| ID Service Machine | Logon of the ID table manager virtual machine. If you are not using the default DBIDSERV, another name must be entered here. |
| Nodename | (Entire Net-Work database only). Defines the ID table manager node name for Entire Net-Work. |
| Automatic Restart | If the ID table manager virtual machine abends, it will restart automatically if YES is specified. |
| DBAVMID | ID of the database administrator (DBA) virtual machine. |
| Net-Work Resource ID | Defines the IUCV node name for Entire Net-work. |
This panel is the first of a series for defining the Adabas ADARUN parameter values, which define and control the Adabas nucleus.
HH:MM:SS ***** software ag Online Installation ***** YYYY-MM-DD
- A D A B A S Installation - Panel 3
Define your Adabas nucleus parameters
Modify the following fields to meet your requirements:
No. of - commands: 020 Held ISNs: 0500 Users: 0020
Threads: 05 Att. buffs: 016 ISN per TBI: 50
Held isn per user: 050 TBLES CIDs per user: 05
PF3 will reset modifications |
In the following list, the Field column is the description of the input field on the panel. The ADARUN Parameter column specifies the ADARUN parameter corresponding to the input field. The Default column is the default value in effect if you make no entry. Refer to Adabas Operations for specific information about the Adabas ADARUN parameters.
| Field | ADARUN Parameter | Default |
|---|---|---|
| Commands | NC | 200 |
| Held ISNs | NH | 500 |
| Users | NU | 200 |
| Threads | NT | 5 |
| Att. Buffs | NAB | 16 |
| ISN per TBI | NSISN | 51 |
| Held ISNs per User | NISNHQ | 20 (this default is conditional. See Adabas Operations for more information) |
| TBLES CIDs per User | NQCID | 20 |
This panel continues the definition of the Adabas ADARUN parameter values for z/VM installation.
Note:
This panel does not appear in the VM/GCS sequence.
HH:MM:SS ***** software ag Online Installation ***** YYYY-MM-DD
- A D A B A S Installation - Panel 4
Define your Adabas nucleus parameters
Modify the following fields to meet your requirements:
Size of - buffer pool: 0250000 FB pool: 012000 ISN lists: 010000
Prot. area: 01000 Work pool: 150000 Sort area: 050000
User buffer: 065535 Table of sequential commands: 010000
UQ Pool: 0005000 Asynch. Buffer flush Pool: 0000000
Work Part 2: 00000
PF3 will reset modifications |
In the following list, the Field column is the description of the input field on the panel. The ADARUN Parameter column specifies the ADARUN parameter corresponding to the input field. The Default column is the default value in effect if you make no entry. Refer to Adabas Operations for specific information about the Adabas ADARUN parameters.
| Field | ADARUN Parameter | Default |
|---|---|---|
| Buffer Pool | LBP | 250000 |
| FB Pool | LFP | 12000 |
| ISN Lists | LI | 10000 |
| Protection Area | LP | 10000 |
| Work Pool | LWP | 150000 |
| Sort Area | LS | 49920 |
| User Buffer | LU | 65535 |
| Table of Sequential Commands | LQ | 10000 |
| UQ Pool | LDEUQP | 5000 |
| Asynchr. Buffer Flush Pool | LFIOP | 0/6000 (the default is zero to disable asynchronous buffer flushing, or a minimum of 6000 to enable asynchronous buffer flushing. See Adabas Operations for more information) |
| Work, Part 2 | LWKP2 | 0 |
This panel continues the definition of the Adabas ADARUN parameter values, and applies to both z/VM and VM/GCS systems.
HH:MM:SS ***** software ag Online Installation ***** YYYY-MM-DD
- A D A B A S Installation - Panel 5
Define your Adabas nucleus parameters
Modify the following fields to meet your requirements:
Read-only: NO Utility-only: NO Open command required: NO
Time windows - command: 0060 Search: 0900 Transaction: 0900
Non-activity - access: 0900 ET/BT: 0900 Exclusive: 0900
- Online services: 0900
Sequential block size: 00000 Buffer Flush Duration: 001
PF3 will reset modifications |
In the following list, the Field column is the description of the input field on the panel. The ADARUN Parameter column specifies the ADARUN parameter corresponding to the input field. The Default column is the default value in effect if you make no entry. Refer to Adabas Operations for specific information about the Adabas ADARUN parameters.
| Field | ADARUN Parameter | Default |
|---|---|---|
| Read-only | READONLY | NO |
| Utility-only | UTIONLY | NO |
| OPEN command required | OPENRQ | YES |
| Time windows-command | CT | 60 (see note below) |
| Search | TLSCMD | 300 (see note below) |
| Transaction | TT | 900 (see note below) |
| Non-activity-access | TNAA | 900 (see note below) |
| ET/BT | TNAE | 900 (see note below) |
| Exclusive Use | TNAX | 900 (see note below) |
| Sequential block size | QBLKSIZE | 0 |
| Buffer Flush Duration | TFLUSH | 1 (see note below) |
Note:
All default or specified times are in units of 1.08 seconds. See
Adabas
Operations for more information.
This panel accepts information associated with protection logging.
HH:MM:SS ***** software ag Online Installation ***** YYYY-MM-DD
- A D A B A S Installation - Panel 4
Define your Adabas nucleus parameters (Protection logging)
Modify the following fields to meet your requirements:
Protection logging: NO Protection logging required: NO
Dual logging device: 3380 Size: 000120 CMS-directory: YES
Dual logging file name: TESTCMS.PLOG
Unit 1: 440 Volume: DPLOG1 Link Unit: 440 Password: MAD
Unit 2: 441 Volume: DPLOG2 Link Unit: 441 Password: MAD
PF3 will reset modifications |
| Field | Description |
|---|---|
| Protection Logging | Enter either YES or NO. Even if you specify NO,
first read and provide the applicable information for other panel fields before
continuing to the next panel.
If NO is entered, then one of the following cases applies:
|
| Protection Logging Required | If YES is specified, the ADARUN parameter PLOGRQ=YES is created. In this case, any attempt to start an Adabas nucleus without a protection log causes Adabas initialization to terminate with an error message. |
| Dual Logging Device | Enter the device type to be used. (3380, for example). |
| Size | Enter the number of blocks available for each PLOG minidisk. See Device and File Considerations for blocksize information. |
| CMS-Directory | Enter YES if the dual PLOG is a z/VM minidisk; enter NO if the dual PLOG is an OS-formatted disk. |
| Dual Logging File Name | Enter the file name and file type of the file. |
| Unit 1 and Unit 2 | Enter the CUU of the minidisk defined to the Adabas virtual machine for the protection log. |
| Volume | Enter the volume name, (i.e., LABEL) of each minidisk identified. |
| Link Unit | Enter the link CUU for each PLOG minidisk identified. |
| Password | Enter the MULTI-WRITE password for each PLOG minidisk identified. |
Caution:
Failure to enter the MW link passwords when implementing dual
protection logging will cause the installation to terminate abnormally since no
CP LINK statements will be generated.
This panel accepts information that controls command logging.
HH:MM:SS ***** software ag Online Installation ***** YYYY-MM-DD
- A D A B A S Installation - Panel 5
Define your Adabas nucleus parameters (Command logging)
Modify the following fields to meet your requirements:
Command logging: NO Command log size: 04000
Dual logging device: 3380 Size: 000135 CMS-directory: YES
Dual logging file name: TESTCMS.CLOG
Unit 1: 430 Volume: DCLOG1 Link Unit: 430 Password: MAD
Unit 2: 431 Volume: DCLOG2 Link Unit: 431 Password: MAD
Log - CB: NO FB: NO RB: NO SB: NO VB: NO IB: NO IO: NO
PF3 will reset modifications |
| Field | Description |
|---|---|
| Command Logging | Enter YES or NO. If you enter NO, you can continue directly to the next panel. |
| Command Log Size | Enter the blocksize if using DDLOG (single logging). |
| Dual Logging Device | Enter the device type to be used. (3380, for example). |
| Size | Enter the number of blocks available for each CLOG minidisk. See Device and File Considerations for blocksize information. |
| CMS-Directory | Enter YES if the dual CLOG is a z/VM minidisk; enter NO if the dual CLOG is an MVS-formatted disk. |
| Dual Logging File Name | Enter the file name and file type of the file. |
| Unit 1 and Unit 2 | Enter the CUU of the minidisk defined to the Adabas virtual machine for the command log. |
| Volume | Enter the volume name, (i.e., LABEL) of each minidisk identified. |
| Link Unit | Enter the link CUU for each CLOG minidisk identified. |
| Password | Enter the MULTI WRITE password for each CLOG minidisk identified. |
| Log | Select command logging controls; valid only if
command logging on this panel specifies YES. Enter YES or NO to log the
following information:
|
This panel is used to define the Adabas Associator.
HH:MM:SS ***** software ag Online Installation ***** YYYY-MM-DD
- A D A B A S Installation - Panel 7
Define your ASSOCIATOR structure for FILE 1
Device type: 3380 Size in cylinders: 00049 CMS-directory: YES
File name: TESTCMS.ASSO1
Volume labels: ASS200
Unit addresses: 200 000 000 000
Link addresses: 200 000 000 000
Link passwords: MAD
More volumes for file: NO More ASSO files: NO
PF3 will reset modifications |
| Field | Description |
|---|---|
| Device Type | Enter the device type to be used. |
| Size in Cylinders | Enter the size of minidisks as the number of cylinders in the MDISK statement minus 1. A warning will be displayed, reminding you that Adabas does not use the first cylinder of the minidisk. |
| CMS-Directory | Enter YES if ASSO is on a z/VM minidisk; enter NO if ASSO is on an MVS-formatted disk. |
| File Name | Enter the file name and the file type of the file. |
| Volume Label(s) | Enter up to four volume names for ASSO. |
| Unit Address(es) | Enter the corresponding CUUs for the volumes. |
| Link Address(es) | Enter the link CUUs being used for ASSO. |
| Link Password(s) | Enter the corresponding MULTI WRITE passwords for each volume. |
| More Volumes for File | Enter YES if you want to define more than four volumes for ASSO. Another panel will be provided for additional volumes. |
| More ASSO Files | YES produces panel to define ASSOR2, 3, 4, and 5. |
Note:
Adabas does not use the first cylinder of a z/VM-formatted disk.
Therefore, when specifying size, use the actual size in number of cylinders,
minus 1. Do this for every minidisk used for Adabas files. In addition,
subtract one cylinder for every additional volume specified.
This panel is used to define the Adabas Data Storage.
HH:MM:SS ***** software ag Online Installation ***** YYYY-MM-DD
- A D A B A S Installation - Panel 8
Define your DATA STORAGE structure for FILE 1
Device type: 3380 Size in cylinders: 00111 CMS-directory: YES
File name: TESTCMS.DATA1
Volume labels: DAT300 DAT301 DAT302 DAT303
Unit addresses: 300 301 302 303
Link addresses: 300 301 302 303
Link passwords: MAD MAD MAD MAD
More volumes for file: NO More DATA files: NO
PF3 will reset modifications |
| Field | Description |
|---|---|
| Device Type | Enter the device type to be used (3380, for example). |
| Size in Cylinders | Enter the size of the minidisk in number of cylinders, minus 1. |
| CMS-Directory | Enter YES if DATA is on a z/VM minidisk; enter NO if DATA is on an MVS-formatted disk. |
| File Name | Enter the file name and file type of the file. |
| Volume Label(s) | Enter up to four volume names for DATA. |
| Unit Address(es) | Enter the corresponding CUUs for the volumes. |
| Link Address(es) | Enter the link CUUs that will be used on this virtual machine. |
| Link Password(s) | Enter the corresponding MULTI WRITE passwords for each volume. |
| More Volumes for File | Enter YES if you want to define more than four volumes for DATA. Another panel will be provided for additional volumes. |
| More DATA files | Enter YES to produce panel to define DATAR2, 3, 4, or 5. |
This panel is used to define the Adabas Work area.
HH:MM:SS ***** software ag Online Installation ***** YYYY-MM-DD
- A D A B A S Installation - Panel 9
Define your WORK STORAGE structure for FILE 1
Device type: 3380 Size in cylinders: 00024 CMS-directory: YES
File name: TESTCMS.WORK1
Volume labels: WOR400
Unit addresses: 400 000 000 000
Link addresses: 400 000 000 000
Link passwords: MAD
More volumes for file: NO More WORK files: NO
PF3 will reset modifications |
| Field | Description |
|---|---|
| Device Type | Enter the device type to be used (3380, for example). |
| Size in Cylinders | Enter the size of the minidisk in number of cylinders, minus 1. |
| CMS-Directory | Enter YES if WORK is on a z/VM minidisk; enter NO if WORK is on an MVS-formatted disk. |
| File Name | Enter the file name and file type of the file. |
| Volume Label(s) | Enter up to four volume names for WORK. |
| Unit Address(es) | Enter the corresponding CUUs for the volumes. |
| Link Address(es) | Enter the link CUUs that will be used on this virtual machine. |
| Link Password(s) | Enter the corresponding MULTI WRITE passwords for each volume. |
| More Volumes for File | Enter YES if you want to define more than four volumes for WORK. Another panel will be provided for additional volumes. |
This panel is used to define the Adabas Temp area.
HH:MM:SS ***** software ag Online Installation ***** YYYY-MM-DD
- A D A B A S Installation - Panel 10
Define your TEMPORARY STORAGE structure for FILE 1
Device type: 3380 Size in cylinders: 00009 CMS-directory: YES
File name: TESTCMS.TEMP1
Volume labels: TEM410
Unit addresses: 410 000 000 000
Link addresses: 410 000 000 000
Link passwords: MAD
More volumes for file: NO More TEMP files: NO
PF3 will reset modifications |
| Field | Description |
|---|---|
| Device Type | Enter the device type to be used (3380, for example). |
| Size in Cylinders | Enter the size of the minidisk in number of cylinders, minus 1. |
| CMS-Directory | Enter YES if TEMP is on a z/VM minidisk; enter NO if TEMP is on an MVS-formatted disk. |
| File Name | Enter the file name and file type of the file. |
| Volume Label(s) | Enter up to four volume names for WORK. |
| Unit Address(es) | Enter the corresponding CUUs for the volumes. |
| Link Address(es) | Enter the link CUUs that will be used on this virtual machine. |
| Link Password(s) | Enter the corresponding MULTI WRITE passwords for each volume. |
| More Volumes for File | Enter YES if you want to define more than four volumes for TEMP. Another panel will be provided for additional volumes. |
This panel is used to define the Adabas Sort area.
HH:MM:SS ***** software ag Online Installation ***** YYYY-MM-DD
- A D A B A S Installation - Panel 11
Define your SORT STORAGE structure for FILE 1
Device type: 3380 Size in cylinders: 00009 CMS-directory: YES
File name: TESTCMS.SORT1
Volume labels: SOR420
Unit addresses: 420 000 000 000
Link addresses: 420 000 000 000
Link passwords: MAD
More volumes for file: NO More SORT files: YES
PF3 will reset modifications |
| Field | Description |
|---|---|
| Device Type | Enter the device type to be used (3380, for example). |
| Size in Cylinders | Enter the size of the minidisk in number of cylinders, minus 1. |
| CMS-Directory | Enter YES if SORT is on a z/VM minidisk; enter NO if SORT is on an MVS-formatted disk. |
| File Name | Enter the file name and file type of the file. |
| Volume Label(s) | Enter up to four volume names for WORK. |
| Unit Address(es) | Enter the corresponding CUUs for the volumes. |
| Link Address(es) | Enter the link CUUs that will be used on this virtual machine. |
| Link Password(s) | Enter the corresponding MULTI WRITE passwords for each volume. |
| More Volumes for File | Enter YES if you want to define more than four volumes for SORT. Another panel will be provided for additional volumes. |
| More SORT Files | YES produces a panel to define SORT2. |
This panel accepts ADALOD utility parameters used for loading the checkpoint file.
HH:MM:SS ***** software ag Online Installation ***** YYYY-MM-DD
- A D A B A S Installation - Panel 12
Define your Checkpoint and ET-data File
Modify the following fields to meet your requirements:
File name: CHECKPOINT Max. ISN: 001000 Min. CP ISN: 00255
ASSO padding factor: 10 AC-RABN: 00000
Normal index size: 64B NI-RABN: 00000 Max. secondary alloc: 00000
Upper index size: 03B UI-RABN: 00000 Max. secondary alloc: 00000
DATA padding factor: 10 DS-RABN: 00000 Max. secondary alloc: 00000
DS-reusage: NO DS-size: 100B DS-device: 3380
PF3 will reset modifications |
The left column equates to the description prior to the input field on the panel. The right column represents the ADALOD parameter associated with the description. Refer to Adabas Utilities for more specific information on the ADALOD parameters.
| Field | ADARUN Parameter |
|---|---|
| File Name | NAME |
| Max ISN | MAXISN |
| Min CP ISN | MINISN |
| ASSO Padding Factor | ASSOPFAC |
| AC-RABN | ACRABN |
| Normal Index Size | NISIZE |
| NI-RABN | NIRABN |
| Max Secondary Alloc | MAXNI |
| Upper Index Size | UISIZE |
| UI-RABN | UIRABN |
| Max Secondary Alloc | MAXUI |
| DATA Padding Factor | DATAPFAC |
| DS-RABN | DSRABN |
| Max Secondary Alloc | MAXDS |
| DS-Reusage | DSREUSE |
| DS-Size | DSSIZE |
| DS-Device | DSDEV |
This panel accepts ADALOD parameters used when loading the EMPLOYEES demo file.
HH:MM:SS ***** software ag Online Installation ***** YYYY-MM-DD
- A D A B A S Installation - Panel 14
Define your DEMO-File 1, Employees File
Modify the following fields to meet your requirements:
File name: EMPLOYEES Max. ISN: 001500
ASSO padding factor: 10 AC-RABN: 00000
Normal index size: 140B NI-RABN: 00000 Max. secondary alloc: 00000
Upper index size: 15B UI-RABN: 00000 Max. secondary alloc: 00000
DATA padding factor: 10 DS-RABN: 00000 Max. secondary alloc: 00000
DS-reusage: YES DS-size: 110B DS-device: 3380
PF3 will reset modifications |
| Field | ADARUN Parameter |
|---|---|
| File Name | NAME |
| Max ISN | MAXISN |
| Min CP ISN | MINISN |
| ASSO Padding Factor | ASSOPFAC |
| AC-RABN | ACRABN |
| Normal Index Size | NISIZE |
| NI-RABN | NIRABN |
| Max Secondary Alloc | MAXNI |
| Upper Index Size | UISIZE |
| UI-RABN | UIRABN |
| Max Secondary Alloc | MAXUI |
| DATA Padding Factor | DATAPFAC |
| DS-RABN | DSRABN |
| Max Secondary Alloc | MAXDS |
| DS-Reusage | DSREUSE |
| DS-Size | DSSIZE |
| DS-Device | DSDEV |
This panel accepts ADALOD parameters when loading the VEHICLES demo file.
HH:MM:SS ***** software ag Online Installation ***** YYYY-MM-DD
- A D A B A S Installation - Panel 15
Define your DEMO-File 2, Vehicles File
Modify the following fields to meet your requirements:
File name: VEHICLES Max. ISN: 001500
ASSO padding factor: 10 AC-RABN: 00000
Normal index size: 35B NI-RABN: 00000 Max. secondary alloc: 00000
Upper index size: 10B UI-RABN: 00000 Max. secondary alloc: 00000
DATA padding factor: 10 DS-RABN: 00000 Max. secondary alloc: 00000
DS-reusage: YES DS-size: 50B DS-device: 3380
PF3 will reset modifications |
| Field | ADARUN Parameter |
|---|---|
| File Name | NAME |
| Max ISN | MAXISN |
| Min CP ISN | MINISN |
| ASSO Padding Factor | ASSOPFAC |
| AC-RABN | ACRABN |
| Normal Index Size | NISIZE |
| NI-RABN | NIRABN |
| Max Secondary Alloc | MAXNI |
| Upper Index Size | UISIZE |
| UI-RABN | UIRABN |
| Max Secondary Alloc | MAXUI |
| DATA Padding Factor | DATAPFAC |
| DS-RABN | DSRABN |
| Max Secondary Alloc | MAXDS |
| DS-Reusage | DSREUSE |
| DS-Size | DSSIZE |
| DS-Device | DSDEV |
This panel accepts ADALOD parameters to load the MISCELLANEOUS demo file.
HH:MM:SS ***** software ag Online Installation ***** YYYY-MM-DD
- A D A B A S Installation - Panel 16
Define your DEMO-File 3, MISCELLANEOUS File
Modify the following fields to meet your requirements:
File name: MISCELLANEOUS Max. ISN: 002000
ASSO padding factor: 10 AC-RABN: 00000
Normal index size: 50B NI-RABN: 00000 Max. secondary alloc: 00000
Upper index size: 07B UI-RABN: 00000 Max. secondary alloc: 00000
DATA padding factor: 10 DS-RABN: 00000 Max. secondary alloc: 00000
DS-reusage: YES DS-size: 76B DS-device: 3380
PF3 will reset modifications |
| Field | ADARUN Parameter |
|---|---|
| File Name | NAME |
| Max ISN | MAXISN |
| Min CP ISN | MINISN |
| ASSO Padding Factor | ASSOPFAC |
| AC-RABN | ACRABN |
| Normal Index Size | NISIZE |
| NI-RABN | NIRABN |
| Max Secondary Alloc | MAXNI |
| Upper Index Size | UISIZE |
| UI-RABN | UIRABN |
| Max Secondary Alloc | MAXUI |
| DATA Padding Factor | DATAPFAC |
| DS-RABN | DSRABN |
| Max Secondary Alloc | MAXDS |
| DS-Reusage | DSREUSE |
| DS-Size | DSSIZE |
| DS-Device | DSDEV |
After panel 16 has been completed, the remaining online panels require no input. They simply display statements giving the status of the installation procedure.
HH:MM:SS ***** software ag Online Installation ***** YYYY-MM-DD
- A D A B A S Installation - Panel 18
The Adabas execution environment for data base 112 is being established
The PROFILE EXEC for the ID table service machine already exists
The zap file for the ID table service machine already exists
The zap file for ADALDI already exists
The PROFILE EXEC XDB200 has been created
The ADAFRM control cards to format DB 112 already exist
The PROFILE EXEC for SAGDBA has been created or modified
The ADADEF control cards to define DB 112 already exist
Hit ENTER to proceed
|
During the building of panel 18, messages will appear giving a step by step status of the installation process. During the building of panel 18 there will be two interruptions, and at both times the literal “MORE...” will be displayed on the bottom right corner of the terminal. The messages that will appear will be the names of the ID table service machine and the Adabas nucleus machine. Output should look similar to the following:
DBIDSERV: R; T=0.01/0.01 15:33:20 ADABASVv: R; T=0.01/0.01 15:33:20
This message will indicate that a PROFILE EXEC has been created for these machines and has been punched over to that virtual machine. It will be necessary to press the Clear key to continue the installation process.
When panel 18 is completed, you will be prompted to press the Enter key to proceed.
HH:MM:SS ***** software ag Online Installation ***** YYYY-MM-DD
- A D A B A S Installation - Panel 19
The Adabas execution environment for database 112 is being established
The control cards to run the nucleus for DB 112 already exist
The ADARUN control cards for device 3380 already exist
The control cards to load demo-file EMPLOYEES already exist
The control cards to load demo-file VEHICLES already exist
The control cards to load demo-file MISCELLANEOUS already exist
The volume list for DB 112 has been created
The ADADEFS EXEC for DB 112 has been created
Hit ENTER to proceed
|
Panel 19 will continue to display updates on the creation of ADARUN control cards and the control cards to load the demonstration files. At the end of all the messages, you will be prompted to press Enter to proceed. At this point, the database environment has been set up. If the procedure is not to be continued, press PF3 to terminate.
LINK statements should appear for each Adabas file required for the installation followed by a message indicating that the Adabas library minidisk is being accessed as READ ONLY. The output should look similar to the following:
DASD 200 LINKED R/W; R/W BY ADABASVv DASD 300 LINKED R/W; R/W BY ADABASVv DASD 400 LINKED R/W; R/W BY ADABASVv DASD 410 LINKED R/W; R/W BY ADABASVv DASD 420 LINKED R/W; R/W BY ADABASVv DMSACC724I ‘202’ REPLACES ‘ C (202) ’ DMSACC723I C (202) R/O
If a LINK statement is not displayed for each required Adabas file, ADAFRM will terminate abnormally. Check to see that the correct MULTI WRITE passwords were entered for each Adabas file.
The installation procedure can be restarted to change passwords or make other corrections by entering:
INSTADA
The installation procedure continues by invoking the following EXECs to perform the previously mentioned functions:
DBINIT perform z/VM minidisk functions ADAFRM format the files for the database ADADEF define the database ADALOD load the three demo files ADAREP produce a database report
The Adabas environment for database 112 has been successfully modified
Ready;
RUNNING HOSTSYS |
The final step of the installation procedure is to bring the nucleus up if the Adabas machine has the DBA machine defined as a secondary console. The following message appears after that step has started:
The Adabas nucleus for database 225 has been started Adabas installed successfully READY;
Whether you are on the DBA or Adabas machine, the following messages are displayed:
ADAN02 00225 NUCLEUS-RUN WITHOUT PROTECTION-LOG ADAN03 00225 ADABAS COMING UP ADAN01 00225 A D A B A S IS ACTIVE ADAN01 00225 MODE = MULTI
The installation has finished, and the nucleus should be active.
