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 |
|---|---|
| CORvrs.LOAD | COR load modules |
| CORvrs.INPL | SYSCOR INPL file |
| CORvrs.ERRN | SYSCOR error messages file |
| CORvrs.SRCE | Source modules |
| CORvrs.JOBS | Installation jobs |
| CORvrs.SYSF | Base configuration file |
| CORvrs.LXnn |
Compatible database components for this version of the Adabas System Coordinator. This library must be added to the start of the load library concatenation in all database startup procedures, thereby replacing the equivalent modules in the Adabas library. If the Adabas nucleus is running with APF-authorization the LXnn library must also be APF-authorized. Note: |
where vrs in data set names represents the version, revision, and system maintenance level of the product and nn represents the patch number of the latest LX library.
The steps needed for a successful installation are as follows:
| Step | Description | Required | Job Name |
|---|---|---|---|
| 1 | Restore the libraries from the installation medium | Yes | |
| 2 | Load (INPL) the SYSCOR application | Yes | CORI061 |
| 3 | Load the configuration file and prepare SYSCOR | Yes | CORI050 |
| 4 | Assemble the configuration module | Yes | CORI055 |
| 5 | Add the System Coordinator to the Adabas clients | Yes |
CORI060, |
| 6 | Define the System Coordinator group and daemons | Required if a COR daemon is to be used | |
| 7 | Install the CICS node error program (optional) | Optional | |
| 8 | Create startup procedures for the Adabas System Coordinator daemons | Required if a COR daemon is to be used | |
| 9 | Create System Coordinator daemon disk files | Optional, depending on which products are installed and how they are configured. | CORI040 |
| 10 | Define runtime controls for Client jobs and TP systems | Optional |
In a multi-systems environment a Coordinator daemon is normally defined for each system. In a parallel sysplex daemons use the IBM XCF facility to communicate. All COR daemons are defined (in the COR configuration file) with the same group name, and this name is used as the XCF group name. The group name selected must be unique to the COR daemon group, and must not be the same as the group name (CLUGROUPNAME) selected for any Adabas Cluster Services database.
The Adabas System Coordinator daemon must execute:
from an authorized load library; and
at a higher priority than the TP monitors, databases, and jobs it is used to coordinate.
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.
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.
Use sample job CORI061 to load the SYSCOR online administration and error messages file into Natural.
System Coordinator and related products operate according to definitions contained in the configuration file. You must allocate a new Adabas file for the Version 8.3 configuration file and load CORvrl.SYSF into it using the supplied sample job CORI050. The online services will guide you through the steps required to make the new file ready for use, including conversion from previous versions of System Coordinator.
To load the configuration file
Load the Adabas System Coordinator configuration file from the distribution medium using the standard Adabas load utility ADALOD. Use sample job CORI050. If you are using an alternate configuration file you need to run this job to initialize both files.
If Natural Security is installed, define the libraries SYSCOR and SYSMPvrs (where vrs is the version you are installing, for example 821) and protect as required. You may define MENU as the startup transaction for SYSCOR. DO NOT define a startup transaction for SYSMPvrs.
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 primary Adabas System Coordinator file.
Alternatively, assemble the Natural parameter module with:
NTFILE
,ID=152,DBID=dbid,FNR=fnr
To convert a previous version’s definitions to version 8 format
Logon to library SYSCOR and enter MENU.
SYSCOR will detect that the configuration file is new and will guide you
through the steps required to copy and convert the definitions from a previous
version.
Repeat this procedure for each configuration file to be converted. The procedure only needs to be done once for each configuration file, regardless of how many products use it. Other products may have additional conversion requirements.
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 |
| ADBID= | Database number for the alternate System Coordinator configuration file. If not specified, an alternate file will not be used. |
| AFNR= | File number for the alternate System Coordinator configuration file. If not specified, an alternate file will not be used. |
| 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, the RETRY= setting takes effect (see below).
|
| CRITICAL= |
Use this keyword if you want System Coordinator to check for availability and correct functioning of supported add-on products. You may specify one or more of the following, separated by commas:
If any critical product is not functioning correctly, all Adabas requests will be rejected with response code 101, subcode 59. |
| DMWAIT= | Specifies a maximum time (in minutes) that the System Coordinator daemon will wait for the configuration file database to be activated. If not specified, the daemon will wait indefinitely. The default is 60. |
| ZOSDUMP= |
This option applies to z/OS installations only and determines the style of dump the System Coordinator daemon produces, in the event of an abnormal termination. The default, ABEND, produces a standard operating system dump to SYSUDUMP, SYSABEND or SYSMDUMP. SVC produces an SVC dump on the system dump datasets. This can often be quicker than producing a standard dump. The daemon issues message: COR037I SVC dump created and the operating system writes messages to the system log to identify the dump dataset. If the SVC dump fails for any reason, the daemon issues message: COR038E SVC dump failed, R15: hhhhhhhh and a standard dump is produced. |
| RETRY= | RETRY specifies the frequency (number of Adabas
calls issued in this client job) at which System Coordinator in the client job
will retry access to its configuration file after a response 148. The default
is 1000. Client services provided by System Coordinator and its supported
add-on products are not available until the configuration file becomes active.
RETRY only takes effect if SF148=WAIT has not been
specified.
|
Name the resulting load module CORCFG (this is required).
Use sample job CORI055.
The client components are named CORS0n where n is a subsystem suffix.
First, you must re-assemble the Adabas LNKGBLS table, specifying the
parameter COR=YES in the LGBLSET macro.
Next, link the appropriate Adabas System Coordinator client component with your Adabas link components (note - the resulting COR-enabled Adabas link components must only be used for client jobs).
Finally, to enable the Adabas System Coordinator client process, make the following components available in STEPLIB (or COMPLIB or DFHRPL if indicated in the table below):
the COR-enabled Adabas link components;
the generated configuration module CORCFG; and
the Adabas System Coordinator load library.
All Adabas System Coordinator components involved in the client process must be of the same version, release, sm-level, and patch-level. For example, for a particular client process, the version of the CORS0n component included in the COR-enabled Adabas link module must be identical to the version of the Adabas System Coordinator library made available to that client process.
For ease of reference, the table below lists a number of job types, the corresponding CORS0n component, the corresponding sample job, and any relevant installation notes that may apply.
You must use the linkage editor options specified in the sample jobs
The sample install jobs referenced below may not match what is needed for the release of Adabas used at your site. Please refer to your Adabas installation documentation and JCL to ensure you use the appropriate JCL for your release, adjusted for the needs of the sample jobs supplied here.
| Job Type | CORS0n Component | Sample Job and Installation notes |
|---|---|---|
| Batch/TSO | CORS01 | CORI060 |
| Com-plete | CORS02 | CORI080C
Notes:
|
| CICS Command Level | CORS03 | CORI080B
Notes:
For sites that require CICS definitions the member CORI080R in the Coordinator JOBS library shows the input needed for all modules (for all sibling products too). Note: Note: |
| IMS | CORS05 | CORI080G |
| Multi-task Batch (for Software AG products Natural RPC Server, Natural Development Server, Adabas SOA Gateway, Adabas SQL Gateway) | CORS07 / CORS09 | CORI080H
Note: Notes:
|
| Other 3rd party or in-house multi-task server environments. | CORS07 / CORS09 | CORI080H
Note: Notes:
|
| NIM: Natural TP monitor | CORS07 | CORI080N
Note: |
| Triggers and Stored Procedures
Note: |
CORS08 | CORI080S
Note: |
Define your 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/ESA or CICS Transaction Server for z/OS. It is not an essential component, but it does improve efficiency when reclaiming user memory after user sessions terminate.
CORNEP must be called as a started task (with Transaction ID ANEP) from the real CICS node error program DFHZNEP. If you do not use DFHZNEP, a sample is provided on the source library. If you do use DFHZNEP, you will need to implement the code for starting CORNEP into your own DFHZNEP as shown in the provided sample source.
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 (Version 7 link module) or
LGBLSET (Version 8 link module) macro.
Note:
CORNEP must be called only from DFHZNEP.
The following is a job example for running a Adabas System Coordinator daemon:
//SYSCO1 PROC //*----------------------------------------------------------------* //* System Coordinator SYSCO Vv.r.s. STARTUP * //*----------------------------------------------------------------* //SYSCO1 EXEC PGM=SYSCO,REGION=0M,TIME=1440 //STEPLIB DD DISP=SHR,DSN=SAG.CORvrs.LOAD // DD DISP=SHR,DSN=ADABAS.Vvrs.LOAD //SYSUDUMP DD SYSOUT=* //CORDUMP DD SYSOUT=* //SYSPRINT DD SYSOUT=* //DDPRINT DD SYSOUT=* //DDCARD DD DISP=SHR,DSN=SAG.CORvrs.SRCE(CORCNTL) //*
The file referenced by the DDCARD statement should contain the following control statements:
PRODUCT=CASPRODUCT=AFP (If FASTABM is to be run)FORCE=NOIf SYSCO terminates abnormally, it may be necessary to specify
FORCE=YES on restart.
Some products require a daemon disk file. This is described in the relevant product documentation. Tailor and run job CORI040 to create each required disk file. Examples of products for which you might need to create disk files are:
System Coordinator’s latency file for latency management of TP systems.
Adabas Transaction Manager’s recovery file.
System Coordinator can be installed for all client jobs, but will be inactive until runtime controls are defined. Controls are defined in the SYSCOR Natural application, using the Maintenance menu. Refer to the Online Services section for further information.
Alternatively, you can delay this task until you have installed the appropriate add-on product(s). You may then use any of the supplied maintenance applications (SYSAFP, SYSAVI or SYSATM).
Multi-task batch environments have special requirements. These are discussed below for the most common environment types.
Installing the Adabas System Coordinator with the Adabas SQL Gateway in z/OS
Installing Adabas System Coordinator with Natural RPC Batch Server
Installing Adabas System Coordinator with Natural Development Server
Installing Adabas System Coordinator with the Adabas SOA Gateway
Installing Adabas System Coordinator in 3rd party or in-house multi-task server environments
The Adabas SQL Gateway uses z/OS UNIX Systems Services to run as a multi-threaded server. This requires re-entrant operation which has additional installation considerations for products based upon Adabas System Coordinator such as Adabas Fastpath, Adabas Vista and Adabas Transaction Manager.
The Adabas SQL Gateway uses z/OS UNIX Systems Services to run either in basic or authorized multi-threaded server mode. This choice affects the method of installation of the Adabas System Coordinator as the base for Adabas Fastpath, Adabas Vista, Adabas Transaction Manager, etc.
Specifically, it is important that a single copy of the Adabas Link Module (ADALNKR) containing the System Coordinator interface (CORS07) is used, and that this module is linked as specified in the sample CORI080H job.
There are two ways to run the Adabas SQL Gateway which directly affect the way Adabas System Coordinator must be installed:
Basic multi-thread (not APF authorized): When the Adabas SQL Gateway runs without APF authorization it does not activate its low-level RACF interface.
Authorized multi-thread (APF authorized): In its authorized state the Adabas SQL Gateway activates its RACF interface.
The following steps are required for both installation types:
Complete normal SQL Gateway installation (and make sure it works correctly in isolation) before adding the System Coordinator interface. (See the Installation for z/OS section of the Adabas SQL gateway documentation).
Assemble the Adabas Link routine globals module LNKGBLS and link ADALNKR using sample job CORI080H. This COR-enabled ADALNKR should be made available in the appropriate STEPLIB concatenation.
Modify the Server Job CNXADA. Include the Coordinator load library, plus any installed add-on product libraries (Fastpath, Vista, ATM), in the STEPLIB concatenation. For the authorized installation, all libraries must be APF-authorized.
Define the SQL Gateway started task as job type multi-TCB to the desired product(s) in the appropriate administration center: Adabas System Coordinator (SYSCOR), Adabas Fastpath (SYSAFP), Adabas Vista (SYSAVI) and/or Adabas Transaction Manager (SYSATM). See the relevant product documentation for details. The Multi-TCB option is on the second screen of selectable runtime control types, accessible by selecting "more choices for type or" when adding the runtime control.
for this type of operation:
Ensure that SQL Gateway basic multi-thread installation is completed before adding the System Coordinator interface.
Re-link the module named CNXRUNA with the REUS attribute, replacing ADALNK with ADAUSER. Here is a sample of the required JCL:
//LKED EXEC PGM=IEWL,PARM='REUS' //ADALIB DD DSN=ADABAS.VVRS.LOAD,DISP=SHR ... Adabas library ... //SYSLMOD DD DSN=PPP.CONNX.LOAD,DISP=SHR ... Connx Library ... //SYSPRINT DD SYSOUT=* //SYSLIN DD * REPLACE ADABAS ... Delete ADALNK entry ... INCLUDE SYSLMOD(CNXRUNA) INCLUDE ADALIB(ADAUSER) ENTRY MAIN NAME CNXRUNA(R) /*
The Linkage Editor will produce warning messages indicating that some Csects are not re-usable. These can be ignored.
Re-link the module named CNXADA0B with the REUS attribute, replacing ADALNK with ADAUSER. Here is a sample of the required JCL:
//LKED EXEC PGM=IEWL,PARM='REUS' //ADALIB DD DSN=ADABAS.VVRS.LOAD,DISP=SHR ... Adabas library ... //SYSLMOD DD DSN=PPP.CONNX.LOAD,DISP=SHR ... Connx Library ... //SYSPRINT DD SYSOUT=* //SYSLIN DD * REPLACE ADABAS ... Delete ADALNK entry ... INCLUDE SYSLMOD(CNXADA0B) INCLUDE ADALIB(ADAUSER) ENTRY MAIN NAME CNXADA0B(R) /*
The Linkage Editor will produce warning messages indicating that some Csects are not re-usable. These can be ignored.
Do not specify the RENT atrribute for either of these modules. The linked modules must be re-usable but not re-entrant. Failure to do this will result in the System Coordinator failing with S0C4 (addressing) abends.
Ensure that the ADARUN parameter
PROG=RENTUSER is specified in order that the COR-enabled
ADALNKR (created by CORI080H and made available in the STEPLIB concatenation)
is used.
for this type of operation:
Ensure that SQL Gateway authorized multi-thread installation is completed before adding the System Coordinator interface.
Re-link the module named CNXRUNA with the RENT and AC=1 attributes, replacing ADALNK with CORLNKR. Here is a sample of the required JCL:
//LKED EXEC PGM=IEWL,PARM='RENT,AC=1' //CORLIB DD DSN=SAG.CORVRS.LOAD,DISP=SHR ... COR library ... //SYSLMOD DD DSN=PPP.CONNX.LOAD,DISP=SHR ... Connx Library ... //SYSPRINT DD SYSOUT=* //SYSLIN DD * REPLACE ADABAS ... Delete ADALNK entry ... INCLUDE SYSLMOD(CNXRUNA) INCLUDE CORLIB(CORLNKR) ENTRY MAIN NAME CNXRUNA(R) /*
Re-link the module named CNXADA0B with the RENT and AC=1 attributes, replacing ADALNK with CORLNKR. Here is a sample of the required JCL:
//LKED EXEC PGM=IEWL,PARM='RENT,AC=1' //CORLIB DD DSN=SAG.CORVRS.LOAD,DISP=SHR ... COR library ... //SYSLMOD DD DSN=PPP.CONNX.LOAD,DISP=SHR ... Connx Library ... //SYSPRINT DD SYSOUT=* //SYSLIN DD * REPLACE ADABAS ... Delete ADALNK entry ... INCLUDE SYSLMOD(CNXADA0B) INCLUDE CORLIB(CORLNKR) ENTRY MAIN NAME CNXADA0B(R) /*
In order for execution with a Natural RPC Batch Server using multiple tasks you must do the following:
A multi-TCB type runtime control must be defined for the Natural RPC Batch Server job. Multi-TCB type option is on the second screen of selectable runtime control types…select more choices for type when adding the runtime control to see the multi-TCB choice.
Link the Adabas System Coordinator client component (CORS09 if zIIP enabler for Natural is in use or CORS07 if it is not) to the re-entrant Adabas link module using sample job CORI080H. The resulting COR-enabled link module must be named according to the requirements of the Natural RPC Batch Server (for example, ADALNKR) and must be linked with the attributes specified in the sample job.
Use the Natural profile parameter ADANAME and set ADANAME=ADALNKR (or whatever you have named the COR-enabled link module). This will cause Natural to load ADALNKR dynamically at runtime.
Instead of using ADANAME you may link the COR-enabled link module with the Natural RPC Server front-end, however this will only operate correctly
if the Natural front-end is loaded from non-authorized libraries, otherwise protection exceptions may occur. Our recommendation
is therefore to use ADANAME.
The COR load library must be added to the STEPLIB concatenation of the Natural RPC Batch Server job.
The load library for the additional products being used (Fastpath, Vista, Transaction Manager etc) must be added to the STEPLIB concatenation for the Natural RPC Batch Server job.
Restart the Natural RPC Batch Server.
In order for execution with a Natural Development Server using multiple tasks you must do the following:
A multi-TCB type runtime control must be defined for the Natural Development Server job. Multi-TCB type option is on the second screen of selectable runtime control types…select more choices for type when adding the runtime control to see the multi-TCB choice.
Link the Adabas System Coordinator client component (CORS09 if zIIP enabler for Natural is in use or CORS07 if it is not) to the re-entrant Adabas link module using sample job CORI080H. The resulting load module must be named according to the requirements of the Natural Development Server (for example, ADALNKR) and linked with the attributes specified in sample job CORI080H.
Use the Natural profile parameter ADANAME and set ADANAME=ADALNKR (or whatever you have named the COR-enabled link module). This will cause Natural to load ADALNKR dynamically at runtime.
Instead of using ADANAME you may link the COR-enabled link module with the Natural Development Server front-end, however this will only operate correctly
if the Natural front-end is loaded from non-authorized libraries, otherwise protection exceptions may occur. Our recommendation
is therefore to use ADANAME.
The COR load library must be added to the STEPLIB concatenation of the Natural Development Server job.
The load library for the additional products being used (Adabas Fastpath, Adabas Vista, Adabas Transaction Manager etc) must be added to the STEPLIB concatenation for the Natural Development Server job.
Restart the Natural Development Server.
In order for execution with the Adabas SOA Gateway you must do the following:
A multi-TCB type runtime control must be defined for the Adabas SOA Gateway job. Multi-TCB type option is on the second screen of selectable runtime control types…select more choices for type when adding the runtime control to see the multi-TCB choice.
Link the Adabas System Coordinator client component (CORS07) to the re-entrant Adabas link module using sample job CORI080H. The resulting load module must be named according to the requirements of the Adabas SOA Gateway (for example, ADALNKR) and linked with the attributes specified in sample job CORI080H.
The resulting load module must be named according to the requirements of the Adabas SOA Gateway (for example, ADALNKR) and linked with the attributes specified in sample job CORI080H.
The COR load library must be added to the STEPLIB concatenation of the Adabas SOA Gateway job.
The load library for the additional products being used (Fastpath, Vista, Transaction Manager etc) must be added to the STEPLIB concatenation for the Adabas SOA Gateway job.
Restart the Adabas SOA Gateway.
This section applies to 3rd party and customer-written multi-task batch applications designed to use the re-entrant Adabas link module. Note: Quite obviously, these types of environments are unknown to Software AG so the information here is only a guideline on what may be appropriate, the specifics of what is actually appropriate are dictated by the design of the server in question. Therefore you must check with Software AG in case there are any other considerations before implementing.
In order for execution with 3rd party or in-house multi-task server environments you must do the following:
A multi-TCB type runtime control must be defined for the multi-task server job. Multi-TCB type option is on the second screen of selectable runtime control types…select more choices for type when adding the runtime control to see the multi-TCB choice.
Link the Adabas System Coordinator client component (CORS07) to the re-entrant Adabas link module using sample job CORI080H. The resulting load module must be named according to the requirements of the multi-task server (for example, ADALNKR) and linked with the attributes specified in sample job CORI080H.
The resulting load module must be named according to the requirements of the multi-task server (for example, ADALNKR) and linked with the attributes specified in sample job CORI080H.
The COR load library must be added to the STEPLIB concatenation of the multi-task server job.
The load library for the additional products being used (Fastpath, Vista, Transaction Manager etc) must be added to the STEPLIB concatenation for the multi-task server job.
Restart the multi-task server.
Usually, the server application must ensure that either:
the task which causes the COR environment to initialize (usually the first task to issue an Adabas call) stays active for the duration of the job
or
the load modules required for the product are pre-loaded by a task which stays active for the duration of the job. The modules required for COR are listed above (under Job Type CICS Command Level) and each product names its required modules.
To install Adabas System Coordinator to run with the TP system NIM you must do the following:
A multi-TCB type runtime control must be defined for the NIM job. Multi-TCB type option is on the second screen of selectable runtime control types…select more choices for type when adding the runtime control to see the multi-TCB choice.
Adjust and use the sample job CORI080N to link your re-entrant Adabas link module with the System Coordinator components.
Name the supplied NIMUEXC as the NIM user exit C.
Name the supplied NIMUEXD as the NIM user exit D.
An additional module (CORXNIM) is needed (use sample job CORI090) if any of the following is true…
You have another NIM exit C and/or D. Name these other exit modules here so that System Coordinator will invoke them after the actual Coordinator equivalents have run.
Here is an example of how to name these other exit modules in the CORI090 job:
//SYSIN DD *
CORMNIM EXITC=TESTEXC, <== ENTER NIM EXIT C MODULE NAME
EXITD=TESTEXD <== ENTER NIM EXIT D MODULE NAME
/*
Your version of NIM pre-dates NIM 4.5.3. For these earlier releases…
i. Identify one of the four GlobMap user words that is
available for use by System Coordinator.
ii. Identify one of the four TaskMap user words that is
available for use by System Coordinator (it does not have to be the same number
as the GlobMap).
Here is an example of how to identify the GlobMap and TaskMap user word fields in the CORI090 job:
//SYSIN DD *
CORMNIM GBLWORD=GBLUWRD3, <== GLOBAL USER WORD FOR USE BY COR
TSKWORD=TSKUSRW2 <== TASK USER WORD FOR USE BY COR
/*
The System Coordinator load library must be added to the STEPLIB concatenation of your NIM job.
The load libraries for the additional products being used (Fastpath, Vista, Transaction Manager etc) must be added to the STEPLIB concatenation for your NIM job.
Restart NIM.
This documentation describes the implementation of Adabas System Coordinator for zIIP.
zIIP support by Adabas System Coordinator requires that Adabas for zIIP is installed at your site.
Adabas for zIIP relevant prerequisites are described in Prerequisites in Installing Adabas for zIIP in the Installation for z/OS Adabas documentation.
The following table describes the additional Add-on product maintenance for supporting Adabas System Coordinator for zIIP:
| Add-on Product | Fix number |
|---|---|
| Adabas Fastpath | None required. |
| Adabas SAF Security | AX822013 |
| Adabas Transaction Manager | AT822035 |
| Adabas Vista | None required. |
Mainframe License Check version 1.3.3 is the minimum MLC version required for the Adabas for zIIP license check performed
by the Adabas System Coordinator daemon when running ZIIP=YES (see also License below).
For up to date information on the required MLC version please refer to the Adabas documentation appropriate for the version of Adabas you are running.
An Adabas System Coordinator Daemon that is to run with zIIP activated requires the availability of the Adabas for zIIP license file (AZPAD). If the AZPAD license is not provided or erroneous, the Daemon will run with zIIP deactivated.
The license can be made available to the Adabas System Coordinator Daemon in exactly the same way it is made available to an Adabas nucleus, that is, as a load module with the name AZPADLIC.
Alternatively, the license file can be referred to by a "DDLAZPAD" DD statement in the Daemon job/started task. This is a fall back in case the AZPADLIC module cannot be loaded.
Refer to the licensing information in the Adabas documentation for further information.
After following the standard Installation Procedure, perform the
following additional steps to implement Adabas System Coordinator for zIIP
Modify your Daemon job/started task as follows:
If you are running Adabas for zIIP version 8.4 or below, replace the standard Adabas library in the Daemon job/started task with the AZPvrs library installed at your site.
Include the MLCvrs library for licensing support.
Include your license module or dataset (see License above)
For example:
//SYSCO1 PROC //*----------------------------------------------------------------* //* System Coordinator SYSCO Vv.r.s. STARTUP * //*----------------------------------------------------------------* //SYSCO1 EXEC PGM=SYSCO,REGION=0M,TIME=1440 //STEPLIB DD DISP=SHR,DSN=SAG.CORvrs.LOAD // DD DISP=SHR,DSN=SAG.ADAvrs.LOAD // DD DISP=SHR,DSN=SAG.MLCvrs.LOAD // DD DISP=SHR,DSN=your.azpadlic.load.library //SYSUDUMP DD SYSOUT=* //CORDUMP DD SYSOUT=* //SYSPRINT DD SYSOUT=* //DDPRINT DD SYSOUT=* //DDCARD DD DISP=SHR,DSN=SAG.CORvrs.SRCE(CORCNTL) //* |
Specify ZIIP=YES in the Daemon Runtime Parameters.
Start the Adabas System Coordinator Daemon
New messages and user abend codes may be observed when running the Adabas System Coordinator Daemon with zIIP activated.
The description of these new messages and codes is organized in the following parts:
| ADAI* - ADAIOR System Messages | Describes ADAIOR system messages. |
| ADAZ* - ADAZIP System Messages | Describes ADAZIP system messages. |
| CORD* - Adabas System Coordinator Daemon Messages | Describes messages issued by the Adabas System Coordinator daemon. |
| MLC* - Software AG Mainframe Licensing Error Messages | Describes error messages issued by Software AG's mainframe licensing software and the license utility. |
| User Abend Codes | Describes user abend codes. |
For ADAI*, ADAZ*, MLC* and User Abend Codes, refer to the corresponding sections of the appropriate Adabas Messages and Codes documentation for the version of Adabas you are using.