
	Version 7.4.2	SEARCH INDEX CONTENTS \| PDF PAGE PDF BOOKS \| HOME UP PREV NEXT

BS2000 Installation

The Installation Tape
Installation Overview
System Programming Considerations
Installation Procedure

The Installation Tape

Review the Report of Tape Creation that accompanies the release package before restoring the release data to disk. Information in this report supersedes the information in this documentation.

The installation tape contains the following datasets in the sequence indicated in the report:

Dataset	Contents
COR`vrs`.SRC	Source modules
COR`vrs`.JOBS	Installation jobs
COR`vrs`.MOD	Load modules
COR`vrs`.INPL	SYSCOR INPL file
COR`vrs`.ERRN	SYSCOR error messages file
COR`vrs`.SYSF	Base configuration file

where vrs in dataset names represents the version, revision, and system maintenance level of the product.

Installation Overview

The steps needed for a successful installation are as follows:

Step	Description	Job Name
1	Copy SRVnnn.LIBR from tape to disk
2	Copy the procedure COPY.PROC from tape to disk
3	Copy all product files from tape to disk
4	Load (INPL) the SYSCOR application	CORI061
5	Load the configuration file and prepare SYSCOR	CORI050
6	Assemble the configuration module	CORI055
7	Add the Adabas System Coordinator to the Adabas clients	CORI060, CORI080x
8	Define a System Coordinator group and member(s)
9	Create startup procedures for the Adabas System Coordinator member(s)

System Programming Considerations

The Adabas System Coordinator daemon must execute at a higher task priority than the TP monitors and jobs it coordinates. The daemon requires system administrator (TSOS) privileges because it uses a JOBINFO macro to monitor job activity.

Multiple jobs (UTM jobs, for example) defined in the Adabas System Coordinator groups use subpools allocated from a shared memory pool. For BS2000, Adabas System Coordinator requires that you specify the virtual start address and size of the shared pool. This is done when the Coordinator Group is set up in the SYSCOR administration application. The start address selected must be valid in all UTM jobs that will use Adabas System Coordinator, and also in the Adabas System Coordinator daemon task. Ensure that the address spaces defined are large enough to accommodate the defined memory pool.

Adabas System Coordinator requires approximately 256 bytes of shared memory for each user session active in a Client job. Additional memory will be required, depending on the options that have been installed. For more information, refer to the installation documentation for the Adabas options.

If you are installing Adabas System Coordinator for use with Adabas version 7.1.3, you must execute ADARUN from the ADA713.LX01 load library, and ensure other load libraries are concatenated in the correct sequence, as follows:

/ ADD-FILE-LINK DDLIB , $SAG.ADA713.LX01
/ ADD-FILE-LINK BLSLIB00, $SAG.COR742.LX01
/ ADD-FILE-LINK BLSLIB01, $SAG.COR742.MOD
/ ADD-FILE-LINK BLSLIB02, $SAG.ppp742.MOD
(ppp=AFP, AVI)
/ START-PROG *MOD($SAG.ADA713.LX01,ADARUN, -
/ RUN-MODE=*ADVANCED(ALT-LIB=*YES))

Installation Procedure

Following is the general Adabas System Coordinator 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.

Step 1: Copy the Library SRVnnn.LIB from Tape to Disk

Note:
This step is not necessary if you have already copied the library SRVnnn.LIB from another Software AG tape. For more information, refer to the element #READ-ME in this library.

The library SRVnnn.LIB is stored on the tape as the sequential file SRVnnn.LIBS containing LMS commands. The current version nnn can be obtained of the Report of Tape Creation. To convert this sequential file into a 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 tape, e.g. TAPE-C4
<volser> = VOLSER of tape (see Report of Tape Creation)

Step 2: Copy the Procedure COPY.PROC from Tape to Disk

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.

Step 3: Copy all Product Files from Tape to Disk

Enter the procedure COPY.PROC to copy all Software AG product files from tape 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 is written to the file L.REPORT.SRV.

Step 4: Load (INPL) the SYSCOR Application (Job I061)

Use sample job CORI061 to load the SYSCOR online administration and error messages file into Natural.

Step 5: Load the Configuration File and Prepare SYSCOR (Job I050)

Note:
If you are upgrading from version 7.1 of Adabas Vista or Adabas Fastpath, you can omit substep 1 below and use the existing configuration file. You must run the conversion program U1JPARM, located in the INPL file, to convert your existing job parameters.

To load the configuration file

Load the Adabas System Coordinator configuration file from the distribution tape using the standard Adabas load utility ADALOD. Use sample job CORI050.
If you are using Natural Security, define SYSCOR and SYSMPvrs to Natural Security with MENU as the startup program name. Restrict the application to authorized personnel.
Use the following parameter to define the Natural session where SYSCOR is to be used:

LFILE=(152,dbid,fnr<,passw><,ciph>)

where dbid and fnr define the Adabas System Coordinator file.

Alternatively, assemble the Natural parameter module with:

NTFILE ,ID=152,DBID=dbid,FNR=fnr

Step 6: Assemble the Configuration Module (Job I055)

Adabas System Coordinator parameters are located in the configuration file. At job start, the Adabas System Coordinator needs to know the location of this file. This information is kept in the configuration module.

Create the configuration module by assembling the CORMCFG parameters defining the database and file number of the Adabas System Coordinator configuration file.

Keyword	Description
DBID=	Database number for the System Coordinator configuration file
FNR=	File number for the System Coordinator configuration file
SF148=WAIT	Use this keyword if you want client jobs to wait when the specified configuration file is not active. If you omit this keyword, default job parameters will be assumed for the job when the configuration file is not active.

Name the resulting load module CORCFG (this is required).

Use sample job CORI055.

Step 7: Add the Adabas System Coordinator to the Adabas Clients (Jobs I060, I080x)

The Adabas System Coordinator client components are supplied as object files and are called CORS1n where n is a subsystem suffix.

The modified Adabas client (link module) is for use by client jobs only. Refer to the section Mandatory Use of Unmodified ADALNK.

Job Type	Stub Module	Sample Job	Natural Link Job
Batch	CORS21	CORI060	LNATBAT
TIAM	CORS21	CORI060	LNRTFRNT
UTM with Natural	CORS26	CORI080A	LNRTFRNT
UTM without Natural	CORS26	CORI080B

Note:
The stub module can be added directly to the Natural link job (see the appropriate name in above table,) instead of creating an additional link job.

Step 8: Define an Adabas System Coordinator Group

Define an Adabas System Coordinator group and members. This is required if you intend to use:

Adabas Fastpath
Adabas Vista or Adabas Fastpath with UTM with dynamic transaction routing.

For more information, refer the section SYSCOR Administration.

Step 9: Create Startup Procedures for the System Coordinator Servers

The following is a job example for running a Adabas System Coordinator daemon:

/.SYSCO LOGON
/ ASSIGN-SYSLST L.SYSCO
/ ASSIGN-SYSOUT O.SYSCO
/ MOD-JOB-OPT LOG=(LIST=*YES)
/ SHOW-JOB-STATUS
/ REMARK +-----------------------------------------------------+
/ REMARK I CREATE SYSCO PARAMETER FILE (SYSCO.DDCARD) I
/ REMARK +-----------------------------------------------------+
/ MOD-JOB-SW ON=(4,5)
/ DELETE-FILE SYSCO.DDCARD,SUPPRESS-ERRORS=DMS0533
/ START-EDT
@ CR 1’MPMWTO=YES’
@ CR 2’PRODUCT=CAS’
@ CR 3’TIMER=10’
@ WR ’SYSCO.DDCARD’
@ HALT
/ REMARK +-----------------------------------------------------+
/ REMARK I CREATE ADALNK PARAMETER FILE (SYSCO.DDLNKPAR) I
/ REMARK +-----------------------------------------------------+
/ DELETE-FILE SYSCO.DDLNKPAR,SUPPRESS-ERRORS=DMS0533
/ START-EDT
@ CR 1’ADALNK IDTNAME=idtname’
@ CR 2’ADALNK DBID=dbid’
@ WR ’SYSCO.DDLNKPAR’
@ HALT
/ MOD-JOB-SW OFF=(4,5)
/ REMARK +-----------------------------------------------------+
/ ADD-FILE-LINK DDLIB, $SAG.ADAvrs.MOD
/ ADD-FILE-LINK BLSLIB01, $SAG.ADAvrs.MOD
/ ADD-FILE-LINK BLSLIB02, $SAG.CORvrs.MOD
/ ADD-FILE-LINK DDCARD, SYSCO.DDCARD
/ ADD-FILE-LINK DDLNKPAR, SYSCO.DDLNKPAR
/ REMARK +-----------------------------------------------------+
/ REMARK I START-PROG SYSCO I
/ REMARK +-----------------------------------------------------+
/ START-PROG *MOD($SAG.CORvrs.MOD,ELEM=SYSCO,PROG-MODE=ANY)
/LOGOFF

If SYSCO terminates abnormally, it may be necessary to specify FORCE=YES on restart.

SEARCH INDEX CONTENTS | PDF PAGE PDF BOOKS | HOME UP PREV NEXT