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 |
|---|---|
| CORvrs.LIBR | Source, macro, object, and load modules |
| CORvrs.INPL | SYSCOR INPL file |
| CORvrs.ERRN | SYSCOR error messages file |
| CORvrs.SYSF | Base configuration file |
where vrs in dataset names represents the version, revision, and system maintenance level of the product.
The steps needed for a successful installation are as follows:
| Step | Description | Job Name |
|---|---|---|
| 1 | Restore the libraries from the installation tape | |
| 2 | Load (INPL) the SYSCOR application | CORI061 |
| 3 | Load the configuration file and prepare SYSCOR | CORI050 |
| 4 | Assemble the configuration module | CORI055 |
| 5 | Add the Adabas System Coordinator to the Adabas clients | CORI060, CORI080x |
| 6 | Define the Adabas System Coordinator group and members | |
| 7 | Install the CICS node error program (optional) | |
| 8 | Create startup procedures for the Adabas System Coordinator member(s) |
The Adabas System Coordinator daemon must execute at a higher priority than the TP monitors and jobs it coordinates.
Corrections for the Adabas System Coordinator will be distributed as
zaps which are applied using the MSHP CORRECT facility. Before applying
corrections you must define Adabas System Coordinator to MSHP with the
MSHP ARCHIVEcommand. Here is a sample job to do
this:
// JOB ARCHIVE ARCHIVE COORDINATOR // OPTION LOG // EXEC MSHP ARCHIVE CORvrs COMPRISES 9001-COR-00 RESOLVES ’SOFTWARE AG - SYSTEM CORDINATOR Vv.r’ ARCHIVE 9001-COR-00-vrs RESIDENCE PRODUCT=CORvrs - PRODUCTION=saglib.CORvrs - GENERATION=saglib.CORvrs /* /&
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.
Use the following sample JCS to restore the Adabas System Coordinator library. Modify the following variables to reflect the standards at your site:
| Variable | Is the... |
|---|---|
| cuu | tape unit number |
| tttttt | volume serial number of the installation tape |
| vrs | version, revision, and system maintenance level |
| xx | file spacing information; see the Report of Tape Creation |
* $$ JOB JNM=LIBREST,CLASS=O,DISP=D * $$ LST CLASS=A,DISP=H // JOB LIBREST // ASSGN SYS006,cuu,VOL=tttttt // ASSGN SYS005,IGN // MTC REW,SYS006 // MTC FSF,SYS006,xx // EXEC LIBR RESTORE S=SAGLIB.CORvrs:SAGLIB.CORvrs – TAPE=SYS006 TL=tttttt LIST=Y /* // MTC REW,SYS006 /& * $$ EOJ
Note:
The library contains the kernel phase CORKRN, which must be
available to the various databases, TP monitors, and batch jobs that will use
Adabas System Coordinator.
Use sample job CORI061 to load the SYSCOR online administration and error messages file into Natural.
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
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 SVC, database, and file number of the Adabas System Coordinator configuration file.
| Keyword | Description |
|---|---|
| SVC= | Your installation’s Adabas SVC number |
| 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.
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 |
|---|---|---|
| Batch/TSO | CORS11 | CORI060 |
| Com-plete | CORS12 | CORI080C |
| CICS command level | CORS13 | CORI080B |
Define a System Coordinator group and member(s). This is required if you intend to use:
Adabas Fastpath
clustered applications with dynamic transaction routing.
Job parameters for each product also contain settings that are relevant to the operation of the Adabas System Coordinator. For more information, see SYSCOR Administration.
The node error program CORNEP is used by sites running CICS command-level applications in CICS for VSE/ESA or CICS Transaction Server for VSE/ESA. It is not an essential component, but it does improve efficiency when reclaiming memory after user sessions terminate.
CORNEP is started (with Transaction ID ANEP) from the real CICS node error program DFHZNEP. The source for DFHZNEP is supplied on the installation tape and can be installed without change. If you have your own DFHZNEP program already installed, you will need to implement the code for starting CORNEP into your own DFHZNEP.
Following are the required CICS resource definition parameters for CORNEP:
Language: Assembler
RESident: No
Datalocation: Any
EXECKey: User
Note:
To use CORNEP, assemble your Adabas link module with
PARMTYP=ALL on the ADAGSET macro.
The following is a job example for running a Adabas System Coordinator daemon:
* ££ JOB JNM=SYSCO1,CLASS=5,DISP=D * ££ LST CLASS=A,DISP=D * ******************************************************* // JOB SYSCO1 * ******************************************************* * JOB TO RUN SYSCO: THE SYSTEM COORDINATOR * * ******************************************************* // OPTION NOSYSDUMP // EXEC PROC=ADAVvLIB // LIBDEF PHASE,SEARCH=(SAGLIB.CORvrs,SAGLIB.ADAvrs) // EXEC SYSCO,SIZE=AUTO PRODUCT=CAS FORCE=NO /* * *********** JOB END SYSC01 /& * ££ EOJ
If SYSCO terminates abnormally, it may be necessary to specify
FORCE=YES on restart.
