This service is used to define and maintain the parameters and definitions that are required by Adabas System Coordinator.
To display the Maintenance menu
Select service 1 from the main menu.
Note:
The Current LFILE 152 Settings window may appear before the
Maintenance menu. See the section System
Settings for more information.
18:32:35 ***** A D A B A S SYSTEM COORDINATOR 8.1.2 ***** 2006-07-20
- Maintenance - C11000M1
Run-mode: Local
Code Service
---- ----------------------------
1 Client Runtime Controls
2 Daemon Group Parameters
. Exit
---- ----------------------------
Code..: _
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12
Help Exit Refr Add Menu |
| From this menu, you can | Service | Cmd |
|---|---|---|
| maintain client runtime controls | 1 | 1.1 |
| maintain daemon group parameter values | 2 | 1.2 |
This function is used to define/maintain runtime controls for jobs that use Adabas System Coordinator services and any of the client-based products that depend on Adabas System Coordinator: Adabas Fastpath, Adabas Transaction Manager and Adabas Vista.
Runtime controls determine the operational behaviour of these products in a given job. You can adjust this behaviour on a case-by-case basis by specifying overrides to tailor operation for a particular transaction code (TP systems), stepname (batch jobs) or login id. You can also define a special type of API runtime control, for completely dynamic reconfiguration.
Note:
See section Parameters for a complete description
of all runtime controls.
Note:
Runtime controls are shared between all installed optional products,
and can be defined by any of the administration applications (SYSCOR, SYSAVI,
SYSAFP, SYSATM). You can administer the runtime controls of any product from
any application.
To display a list of existing definitions
Select service 1 from the Maintenance
menu or enter the command 1.1 on the command
line.
09:56:02 ***** A D A B A S SYSTEM COORDINATOR 8.1.2 ***** 2006-07-21
- Client Runtime Controls - U11300M1
Run-mode: Local Reposition to Type: ________
Name: ________
Client Controls
C Type Name AFP AVI ATM COR Comments
_ CICS (DTR) CICCLUST Y Y Y Y Overrides,Info
_ Batch CORP**** Y Y Y Y
_ *DEFAULT Y Y Y Y
_ CORQ0100 Y Y Y
_ CORQ0200 Off Y Y Y
_ COM-PLETE DAEFCODE Y Y Y Y
Mark with Display,Expand,Modify,Purge,Rename,Copy,Overrides,Information
End of List
Command ==>Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Refr Add Prods Menu |
The list shows the service or job type, the name and for which products controls are defined. The Comments column shows whether overrides or site information are defined for this service/job.
The name identifies the service or job to which these controls apply. A service is a collection of jobs which form a single DTR cluster, for example CICSPlex, CICS/MRO with Dynamic Transaction Routing, IMS/TM or UTM. For jobs, the name may be a wildcard or you can specify a set of default controls for jobs of that type.
Taking the above example:
any batch job with a name beginning CORP will use the controls defined for CORP****
job CORQ0100 will use its own controls (but it will use the Adabas Transaction Manager controls defined for *DEFAULT, because there are none defined for CORQ0100)
job CORQ0200 will use its own controls and Adabas Fastpath is disabled for this job
any other batch job will use the controls defined for *DEFAULT
If you wish to display or modify controls or overrides for one of the other products, press PF11 and mark the required product:
+-----------------------------------+ ! 10:05:15 U1PRODM1 ! ! ! ! Select which product's runtime ! ! controls you want to maintain: ! ! ! ! _ System Coord. ! ! _ Adabas Fastpath ! ! x Adabas Vista ! ! _ Transaction Manager ! ! ! ! PF3 Exit ! ! !+ -----------------------------------+ |
If there is more than a screen of definitions, use PF7 and PF8 to scroll up and down, PF6 and PF9 to go to the top or bottom of the list, or use the Reposition field to position anywhere within the list.
To add a new definition
Press PF10 from the Client Runtime Controls list.
The following window will appear:
12:32:48 ***** A D A B A S SYSTEM COORDINATOR 8.1.2 (I003) ***** 2008-05-22
- Add Client Runtime Control - U11310M1
Run-mode: Local (node 0)
Select (mark one) :
_ Batch
_ COM-PLETE
_ CICS (DTR - Dynamic transaction routing)
_ CICS (Standard)
_ IMS (DTR)
_ UTM (DTR)
_ TSO
_ CMS
_ TIAM
_ more choices for type or
_ API controlled - type 1
_ API controlled - type 2
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Menu
|
Select a job type for the job from the list provided.
Each different job type has different characteristics and it is therefore important to select the correct type.
Note:
Select the job type "CICS (Standard)" if CICS/MRO is to be used
without dynamic transaction routing or for other CICS environments. Select the
job type "CICS (DTR – Dynamic Transaction Routing)" if CICS/MRO is to be used
with dynamic transaction routing.
If you mark the selection "more choices for type", another selection window will appear with additional job types. If you need to use any of these, contact Software AG for advice.
If you mark either of the API controlled types, you can define a set of runtime controls which can be activated dynamically by API. You must enable API overrides for any job where you want to use this API definition and name it in the job’s list of permissible APIs.
Note:
Dynamically activated API runtime controls are not yet
available.
After selecting a job type, press Enter. In the following example, the job type "CICS (DTR – Dynamic Transaction Routing)" was selected which results in the following screen being displayed:
10:20:21 ***** A D A B A S SYSTEM COORDINATOR 8.1.2 ***** 2006-07-21
- Add Client Runtime Control - U11310M4
Run-mode: Local
Type: CICS (DTR)
Name: ________
This is a complex type of runtime which is capable of running in basic mode
and in DTR mode.
You must define a System Coordinator group (and its members) with PRODUCT=DTR
AND the member(s) of that group must be executing in order to achieve DTR
capability, otherwise it is ignored.
The name specified above is a unique name for the runtime controls for the
DTR service (it is not a jobname). You must also use the 'Expand' line
command to enter the list of all jobs in the service
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Add Menu |
Enter the service name (which may not contain * wildcards, in this example CICSPROD was entered) and press PF5 to continue:
10:24:07 ***** A D A B A S SYSTEM COORDINATOR 8.1.2 ***** 2006-07-21
- System Coordinator Runtime Controls - U11310M5
Run-mode: Local Operation mode (mark one):
Type: CICS (DTR) Use normal autodetect approach: X
Name: CICSPROD Enable COR even if no products: _
Disable all products including COR: _
General Settings
Estimated Client Sessions: 1000______ API runtime overrides..: N (Y/N)
Memory pool extents (k)..: 256_ Group..................: ________
Use additional exits.....: N (Y/N)
Maximum idle time (sec)..: 3600______ Non-terminal idle time.: __________
Generate RSP009/79 (Y/N).: Y (until 0_________ seconds elapse)
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Add Menu |
The screen is pre-filled with default values for this control type. Please refer to the Parameters section for a description of each parameter. DTR jobs require a System Coordinator Group name. Enter that now or press PF5 which will set the group name, if only one group is defined, or give you a list of defined groups to choose from, if more than one group is defined.
10:28:51 ***** A D A B A S SYSTEM COORDINATOR 8.1.2 ***** 2006-07-21
- System Coordinator Runtime Controls - U11310M5
Run-mode: Local Operation mode (mark one):
Type: CICS (DTR) Use normal autodetect approach: X
Name: CICSPROD Enable COR even if no products: _
Disable all products including COR: _
General Settings
Estimated Client Sessions: 2000______ API runtime overrides..: N (Y/N)
Memory pool extents (k)..: 256_ Group..................: CORGROUP
Use additional exits.....: N (Y/N)
Maximum idle time (sec)..: 3600______ Non-terminal idle time.: __________
Generate RSP009/79 (Y/N).: Y (until 0_________ seconds elapse)
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Add Menu |
Press PF5 again to add the control.
10:32:26 ***** A D A B A S SYSTEM COORDINATOR 8.1.2 ***** 2006-07-21
- System Coordinator Runtime Controls - U11310M5
Run-mode: Local Operation mode (mark one):
Type: CICS (DTR) Use normal autodetect approach: X
Name: CICSPROD Enable COR even if no products: _
Disable all products including COR: _
General Settings
Estimated Client Sessions: 2000______ API runtime overrides..: N (Y/N)
Memory pool extents (k)..: 256_ Group..................: CORGROUP
Use additional exits.....: N (Y/N)
Maximum idle time (sec)..: 3600______ Non-terminal idle time.: __________
Generate RSP009/79 (Y/N).: Y (until 0_________ seconds elapse)
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Add Menu |
You can now:
Modify the values and press PF5 to update them
Press PF3 to return to the list
Press PF12 to return to the main menu
Press PF9 to define permissible API controls (these will only be honoured if you also set API runtime overrides to Y). Enter the names of up to 64 API controls, which must already be defined, and press PF5
10:35:04 ***** A D A B A S SYSTEM COORDINATOR 8.1.2 ***** 2006-07-21
- System Coordinator Runtime Controls - U11310M6
Run-mode: Local
Type: CICS (DTR)
Name: CICSPROD
The following API runtime overrides are allowed:
________ ________ ________ ________ ________ ________ ________ ________
________ ________ ________ ________ ________ ________ ________ ________
________ ________ ________ ________ ________ ________ ________ ________
________ ________ ________ ________ ________ ________ ________ ________
________ ________ ________ ________ ________ ________ ________ ________
________ ________ ________ ________ ________ ________ ________ ________
________ ________ ________ ________ ________ ________ ________ ________
________ ________ ________ ________ ________ ________ ________ ________
Command=>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Upd Menu |
Press PF10 to define additional options and select option 1 to define command retry requirements or option 2 to define debug settings
+---------------------------------------------------------+ ! 10:43:37 Runtime Controls 2006-07-21 ! ! - Additional - U1SCJAM1 ! ! ! ! Code Service ! ! ---- -------------- ! ! 1 Command Retry ! ! 2 Debug Settings ! ! . Exit ! ! ---- -------------- ! ! Code....: _ ! ! ! ! ! ! Command ==> ! ! ! ! PF1 Help PF3 Exit PF12 Menu ! ! ! +---------------------------------------------------------+ |
For command retry, you can define automatic retry of Adabas commands that complete with particular response codes and subcodes. Specify the number of retry attempts and interval. You can also restrict the retry to particular databases or files and request an informational operator message on the first retry attempt. As soon as response 0 is received, control returns to the application. Press PF5 to save the retry settings.
+----------------------------------------------------------------------+ ! 10:51:44 Additional Runtime Controls 2006-07-21 ! ! Retry Settings U1SCJEM1 ! ! Console ! ! Response Subcode Retries Delay (Unit) Dbid Fnr Message ! ! 148__ _____ 60___ 5____ SEC _____ _____ _ ! ! 255__ _____ 30___ 1____ SEC _____ _____ _ ! ! 48___ _____ 5____ 60___ SEC 153__ _____ Y ! ! _____ _____ _____ _____ ___ _____ _____ _ ! ! _____ _____ _____ _____ ___ _____ _____ _ ! ! _____ _____ _____ _____ ___ _____ _____ _ ! ! _____ _____ _____ _____ ___ _____ _____ _ ! ! _____ _____ _____ _____ ___ _____ _____ _ ! ! _____ _____ _____ _____ ___ _____ _____ _ ! ! _____ _____ _____ _____ ___ _____ _____ _ ! ! _____ _____ _____ _____ ___ _____ _____ _ ! ! _____ _____ _____ _____ ___ _____ _____ _ ! ! _____ _____ _____ _____ ___ _____ _____ _ ! ! _____ _____ _____ _____ ___ _____ _____ _ ! ! _____ _____ _____ _____ ___ _____ _____ _ ! ! Use Before/After exits: N (Y/N) Use additional exits: N (Y/N) ! ! PF1 Help PF3 Exit PF5 Upd ! ! ! +----------------------------------------------------------------------+ |
Use debug settings to produce diagnostic snaps for unexpected Adabas response codes. For more information, please refer to Using the Client Event Debug Monitor .
+-------------------------------------------------------+ ! 10:55:02 Additional Runtime Controls 2006-07-21 ! ! Debug Event Monitor controls U1SCJBM1 ! ! ! ! Debug monitoring scope ..................: ALL ! ! Set debug event for: ! ! Adabas Response Code: ___ and Sub-code: ____ ! ! Or mark for generic error: _ ! ! ! ! And optionally restrict to dbid: _____ ! ! and file number: _____ ! ! ! ! Debug event output - choose one of: ! ! None: X ! ! 'Event' session only: _ ! ! All sessions for this client: _ ! ! All sessions for this job: _ ! ! All memory for this job: _ ! ! ! ! Maximum events to output ................: 0____ ! ! ! ! PF1 Help PF3 Exit PF5 Upd PF10 More ! ! ! +-------------------------------------------------------+ |
Here is an example of adding controls for a batch job. Press PF10 from the list, mark Batch and press Enter to continue:
10:58:17 ***** A D A B A S SYSTEM COORDINATOR 8.1.2 ***** 2006-07-21
- Add Client Runtime Control - U11310M1
Run-mode: Local
Select (mark one) :
x Batch
_ COM-PLETE
_ CICS (DTR - Dynamic transaction routing)
_ CICS (Standard)
_ IMS (DTR)
_ UTM (DTR)
_ TSO
_ CMS
_ TIAM
_ more choices for type or
_ API controlled
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Menu |
Enter the jobname and press PF5:
10:20:21 ***** A D A B A S SYSTEM COORDINATOR 8.1.2 ***** 2006-07-21
- Add Client Runtime Control - U11310M4
Run-mode: Local
Type: Batch
Name: natpbat_ (* for default controls for this type)
This is a standard type of runtime.
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Add Menu |
A job name may contain one or more asterisks (*) to indicate a wild card. For example, the runtime control with the name CICS**PR will be found by any job with the value "CICS" in positions 1-4 and the value "PR" in positions 7-8, no matter what the characters are in positions 5-6. If an asterisk (*) is the last character in a job name, the remainder of positions in the name through the eighth are padded with asterisks. A single asterisk indicates that is the default definition for this job type.
Controls are always matched on type. The order of search within type is
Match on exact job name.
Match on wild card definitions.
Use the default for the job type, if one has been defined.
Note:
The number of wild card job names defined for a job type has a
direct effect on the number of Adabas commands needed to establish the runtime
controls at initialization. This is particularly relevant to batch jobs that
process relatively few Adabas commands.
Different control types have different settings and different default values. Make any required changes and press PF5 to add the definition. You can then define API overrides and additional options or return to the list, as described in 6.
11:13:23 ***** A D A B A S SYSTEM COORDINATOR 8.1.2 ***** 2006-07-21
- System Coordinator Runtime Controls - U11310M5
Run-mode: Local Operation mode (mark one):
Type: Batch Use normal autodetect approach: X
Name: NATPBAT Enable COR even if no products: _
Disable all products including COR: _
General Settings
Estimated Client Sessions: 2_________ API runtime overrides..: N (Y/N)
Memory pool extents (k)..: 256_
Use additional exits.....: N (Y/N)
Maximum idle time (sec)..: __________
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Add Menu |
To maintain a job parameter
Select it by entering one of the following options in column C on the Client Runtime Controls list:
| d | display |
| e | expand |
| m | modify |
| p | purge |
| r | rename |
| c | copy |
| o | overrides |
| i | site information |
Display and modify will provide screens in which you can make modifications to the job parameters. See section Parameters for information on each parameter. For purge, rename, and copy, you are prompted to confirm the action to be taken.
to display/modify a runtime control
Select it from the list by marking column C with a “d” or ”m” as appropriate (example below is for modify).
11:37:13 ***** A D A B A S SYSTEM COORDINATOR 8.1.2 ***** 2006-07-21
- System Coordinator Runtime Controls - U11310M5
Run-mode: Local Operation mode (mark one):
Type: COM-PLETE Use normal autodetect approach: X
Name: DAEFCODE Enable COR even if no products: _
Disable all products including COR: _
General Settings
Estimated Client Sessions: 1000______ API runtime overrides..: N (Y/N)
Memory pool extents (k)..: 256_ Group..................: CORGROUP
Use additional exits.....: N (Y/N)
Maximum idle time (sec)..: 3600______ Non-terminal idle time.: __________
Generate RSP009/79 (Y/N).: Y (until 0_________ seconds elapse)
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Add Menu |
Make any necessary modifications (modify only).
Use PF9 to display/modify the list of permissible API overrides.
Use PF10 to display/modify additional options.
Press PF5 to confirm (modify only).
to expand a runtime control
Select it from the list by marking column C with an “e”.
11:39:03 ***** A D A B A S SYSTEM COORDINATOR 8.1.2 ***** 2006-07-21
- Client Runtime Service Members - U11390M1
Run-mode: Local
Job type: CICS (DTR)
Service name: CICCLUST
C Name Comments
_ CICSDAEF
_ CICSDA2F
_ CICSDA3F
Mark with Purge,Rename
Top of List
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Refr Add Menu |
Expand is only relevant for DTR definitions. Expand allows you to define which jobs comprise that DTR service. Use PF10 to add a job. You can subsequently purge or rename it by marking it with P or R. All jobs defined for a DTR service will use the runtime controls specified on that service.
to purge a runtime control
Select it from the list by marking column C with a “p”.
+------------------------------------+ ! 11:41:08 Purge 2006-07-21 ! ! Runtime Control U11340M1 ! ! ! ! Type: Batch ! ! Name: CORQ0200 ! ! ! ! _ All ! ! _ Transaction Mgr. ! ! _ Fastpath ! ! _ Vista ! ! ! ! Mark Product(s) to purge or All ! ! (Overrides will also be purged) ! ! Command ==> ! ! PF1 Help PF3 Exit PF5 Purge ! ! ! +------------------------------------+ |
Mark which products’ runtime controls you wish to purge or All to purge the entire control.
Press PF5 to confirm
to rename a runtime control
Select it from the list by marking column C with a “r”.
+------------------------------------+ ! 11:43:19 Rename 2006-07-21 ! ! Runtime Control U11350M1 ! ! ! ! ! ! Type: Batch ! ! ! ! Name: CORQ0200 ! ! ! ! New Name: ________ ! ! ! ! Press PF5 to confirm rename ! ! ! ! ! ! Command ==> ! ! PF1 Help PF3 Exit PF5 Rename ! ! ! +------------------------------------+ |
Specify the new name, which must not already exist.
Press PF5 to confirm
to copy a runtime control
Select it from the list by marking column C with a “c”.
+------------------------------------+ ! 11:44:20 Copy 2006-07-21 ! ! Runtime Control U11360M1 ! ! ! ! Type: Batch ! ! Name: CORP**** ! ! ! ! _ All ! ! _ Transaction Mgr. ! ! _ Fastpath ! ! _ Vista ! ! ! ! Mark Product(s) to copy or All ! ! ! ! Copy to ......: ________ ! ! Copy Overrides: N (Y/N - All) ! ! Command ==> ! ! PF1 Help PF3 Exit PF5 Copy ! ! ! +------------------------------------+ |
Mark which products’ runtime controls you wish to copy.
Specify the job name to which these runtime controls will be copied, which must not already exist.
If you select All, you may also copy any defined overrides by entering Y against Copy Overrides.
Press PF5 to confirm
To maintain site information
Select it from the list by marking column C with a “i”.
11:45:28 ***** A D A B A S SYSTEM COORDINATOR 8.1.2 ***** 2006-07-21
- Client Runtime Controls Site Information - U11370M1
Run-mode: Local
Type: CICS (DTR)
Name: CICCLUST
Site Information
----------------
DYPR=FNAT=(60099,205) PROFILE=CICSPROD__________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
You may define up to 256 bytes of alphanumeric data (site information), which
is stored with this runtime control definition and may be retrieved at runtime
using the documented API.
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Upd Purge Menu |
Modify the site information as required and press PF5 to save your changes, or press PF9 to purge the site information.
to list runtime control overrides
Select it from the Runtime Control maintenance list by marking column C with an ‘o’.
11:47:11 ***** A D A B A S SYSTEM COORDINATOR 8.1.2 ***** 2006-07-21
- Client Runtime Controls Override Summary - U11380M1
Run-mode: Local
Type: CICS (DTR) Name: CICCLUST
Overrides
C Type Name AFP AVI ATM COR Comments
_ Transaction QA42 Y Y
Mark with Display,Modify,Purge,Rename,Copy,Information
End of List
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Refr Add Menu |
This screen lists the runtime control overrides that have been defined for each product.
To add a new override, press PF10, mark the type of override you want to add and provide a name:
11:50:36 ***** A D A B A S SYSTEM COORDINATOR 8.1.2 ***** 2006-07-21
- Add Client Runtime Control Override - U11381M1
Run-mode: Local
Type: CICS (DTR) Name: CICCLUST
Select the override type ....: _ Login id
(mark one) x Transaction
and specify the override name: natp____
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Add Menu |
Press PF5 to add an empty override, which you can then modify as required:
11:54:07 ***** A D A B A S SYSTEM COORDINATOR 8.1.2 ***** 2006-07-21
- Client Runtime Controls Override Summary - U11380M1
Run-mode: Local
Type: CICS (DTR) Name: CICCLUST
Overrides
C Type Name AFP AVI ATM COR Comments
_ Transaction NATP *Added (empty)
_ QA42 Y Y
Mark with Display,Modify,Purge,Rename,Copy,Information
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Refr Add Menu |
Enter one of the following options in the C column to select an entry:
| d | display |
| m | modify |
| p | purge |
| r | rename |
| c | copy |
| i | site information |
These options are the same as the ones available for maintaining client runtime controls except that they maintain the override controls rather than the base level controls. If a different product was selected with PF11 on the Client Runtime Controls list, the overrides for that product are shown.
This section describes how to add/maintain daemon groups.
Adabas System Coordinator daemon groups are used to manage clustered (multiregion or IBM Sysplex) applications.
The daemon group defines the types of applications to be managed and the Node IDs of the daemons (group members) that will manage those applications. One daemon must be active on each operating system image that hosts the application. Any application job can then be defined to this group using the Client Runtime Controls function of SYSCOR, SYSAVI, SYSAFP, or SYSATM Online Services.
To invoke the daemon group maintenance menu
Select service 2 from the Maintenance
menu or enter the command 1.2 on a command line.
12:07:39 ***** A D A B A S SYSTEM COORDINATOR 8.1.2 ***** 2006-07-21
System Coordinator Groups C11200M1
Run-mode: Local
Cluster Facility
C Group Name Type SVC ID Name Members
_ PRODGRP Sysplex 234 PRODCLS 0
_ TESTADD Single 211
Mark with D(isplay),M(odify),P(urge),R(ename),E(xpand),F(iles)
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Refr Add Menu |
Enter one of the following options in the C column:
| d | display group definition |
| m | modify group definition |
| p | purge group definition |
| r | rename group definition |
| e | expand group definition |
| f | work with group file definitions |
Use PF10 to add a new group definition
to add a new daemon group definition
Press PF10 on the System Coordinator Group menu. The following screen will appear:
+-------------------------------------------------------------------+ ! 12:21:09 Add 2006-07-21 ! ! System Coordinator Group Member C11210M1 ! ! ! ! Group Name: ________ SVC ID: _____ ! ! ! ! System Type: _ Standard single-system image... ! ! (Mark one) There is only one group member. ! ! _ Standard multi-system images - XCF... ! ! This enables multiple XCF group members. ! ! _ Standard multi-system images - Net-Work... ! ! This enables multiple Net-Work group members. ! ! _ IBM Parallel Sysplex... ! ! This enables XCF group and use of the CF to ! ! allow dynamic transaction routing in the plex ! ! Cluster Facility Name: ________________ ! ! Automatic Pool Recovery: Y ! ! ! ! ! ! ! ! Command ==> ! ! PF1 Help PF3 Exit PF5 Add ! ! ! +-------------------------------------------------------------------+ |
In the field Group Name, enter the name for the group.
The group name is used to control communication between Adabas System Coordinator daemon peers in an operating system cluster. For example, the daemons communicate using an XCF group with this name in an IBM parallel sysplex. This name must be specified in the job definition for Adabas options such as Adabas Fastpath or Adabas Vista.
In the field SVC ID, define the router (SVC) number that is used for communicating with the group (not applicable to BS2000 or z/VM systems).
This must be the same in all parts of a cluster.
In the fields System Type, specify whether the group is to coordinate:
A single system image.
Multiple system images without dynamic transaction routing. This is used to support coordinator daemons running Adabas Fastpath buffers across multiple system images. It does not support dynamic transaction routing across a Parallel Sysplex.
Multiple system images without dynamic transaction routing and using Entire Net-Work for communication between images. This is used to support coordinator daemons running Adabas Fastpath buffers across multiple system images. It does not support dynamic transaction routing across a Parallel Sysplex. You are recommended only to use Entire Net-Work if XCF is not available.
Multiple system images with dynamic transaction routing, using an IBM Parallel Sysplex.
If you select system type ”sysplex”, you must provide the name of the cluster facility used to record the global client list. In an IBM Parallel Sysplex, this is the name of the cache structure in the coupling facility as defined in the installation process.
In the field Automatic Pool Recovery, select whether or not automatic pool recovery is to be activated. This feature is recommended in that it ensures that, should a Adabas System Coordinator daemon fail for any reason, existing client session will continue to operate. When the daemon is restarted, it will recover the user pools from the failing daemon.
If you are running under BS2000, specify the global common memory pool using the additional parameters that appear in the Add System Coordinator Group Member window.
Specify a name, virtual start address, and size for the pool.
The pool you specify is used for allocation of all shared user memory for clustered applications defined to this System Coordinator group.
After adding the group, you can change any of its attributes, by entering ‘m’ against it:
+-------------------------------------------------------------------+ ! 16:42:59 Modify 2006-07-21 ! ! System Coordinator Group Member C11230M1 ! ! ! ! Group Name: PRODGRP SVC ID: 234__ ! ! ! ! System Type: _ Standard single-system image... ! ! (Mark one) There is only one group member. ! ! _ Standard multi-system images - XCF... ! ! This enables multiple XCF group members. ! ! _ Standard multi-system images - Net-Work... ! ! This enables multiple Net-Work group members. ! ! X IBM Parallel Sysplex... ! ! This enables XCF group and use of the CF to ! ! allow dynamic transaction routing in the plex ! ! Cluster Facility Name: PRODCLS_________ ! ! Automatic Pool Recovery: Y ! ! ! ! ! ! ! ! Command ==> ! ! PF1 Help PF3 Exit PF5 Upd ! ! ! +-------------------------------------------------------------------+ |
Make any changes required and press PF5 to save them.
You can also purge or rename the group. You must use purge and rename with care as you may invalidate other definitions (client runtime controls and Adabas Fastpath buffer definitions) that refer to the group being purged or renamed.
To purge, enter ‘p’ against the group to be purged:
+-------------------------------------------------+ ! 16:46:15 Purge 2006-07-21 ! ! System Coordinator Group Member C11240M1 ! ! ! ! Group Name: TESTADD ! ! ! ! SVC ID: 211 ! ! ! ! PF5 to Confirm Purge ! ! ! ! ! ! Command ==> ! ! PF1 Help PF3 Exit PF5 Purge ! ! ! +-------------------------------------------------+ |
and press PF5 to confirm.
To rename, enter ‘r’ against the group to be renamed:
+-------------------------------------------------+ ! 16:47:55 Rename 2006-07-21 ! ! System Coordinator Group Member C11250M1 ! ! ! ! Group Name: TESTADD ! ! ! ! New Name: ________ ! ! ! ! PF5 to Confirm Rename ! ! ! ! ! ! Command ==> ! ! PF1 Help PF3 Exit PF5 Upd ! ! ! +------------------------------------------------ |
to maintain a daemon group member definition
On the System Coordinator Group menu, enter ‘e’ in the C column adjacent to an entry in the Group Name column. The following screen will appear:
12:27:32 ***** A D A B A S SYSTEM COORDINATOR 8.1.2 ***** 2006-07-21
- System Coordinator Group Members - C11260M1
Run-mode: Local
Group Name: PRODGRP Cluster Facility Name: PRODCLS
SVC ID: 234 Operating System : Sysplex
Member
Purge(P) Job Name Node ID
_ SYSCO33 33
_ SYSCO34 34
_ SYSCO35 35
________ _____
________ _____
________ _____
________ _____
________ _____
________ _____
________ _____
________ _____
________ _____
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Refr Upd Add Menu |
From this screen, you can
purge a member by entering ‘p’ in the Purge column adjacent to the Member Job Name entry;
update the member entry by pressing PF5; or
add a new member entry by pressing either PF5 or PF10.
If you are adding a new group, you must add at least one member.
For each member, specify the following:
Member Job Name: The name of the job or started task that will run the Adabas System Coordinator daemon (SYSCO).
Node ID: The Adabas Node ID (target) used to identify the daemon to the network.
Note:
You may not define Node ID 255, because 255 is reserved for use
by Natural.
A System Coordinator group provides a central file-store facility that can be used by Adabas options such as the Adabas Transaction Manager. If an Adabas option requires a SYSCO file to be defined, its documentation will give details of the requirement.
A SYSCO file is a logical collection of records which are stored in an Adabas file. The file can be defined on any Adabas database. A database that contains a system file for job parameters will probably be a suitable location for your SYSCO file, since high availability is likely to be a requirement. A single database file can contain just one SYSCO file.
to add a new SYSCO file definition for a daemon group
To create a database file for use as a SYSCO file, run a standard ADALOD job, using input from the distribution tape. Sample job CORI050F can be edited according to site requirements, and used for this purpose.
On the System Coordinator Group menu, once you have defined your System Coordinator group, enter ‘f’ in the C column adjacent to the appropriate entry in the Group Name column. The following screen will appear:
12:33:48 ***** A D A B A S SYSTEM COORDINATOR 8.1.2 ***** 2006-07-21
- System Coordinator File Definitions - C11270M1
Run-mode: Local
Group Name: CORGROUP
C File Name DB ID Fnr Description
Mark with D(isplay),M(odify),P(urge)No records found for selection
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Refr Add Menu |
Press PF10 to add a SYSCO file definition for this group. The following window will appear:
+------------------------------------------------------------------------+ ! 12:37:54 Add File Definition 2006-07-21 ! ! C11270M2 ! ! Group Name: CORGROUP ! ! ! ! File Name: ________ DB ID: _____ File Number: _____ SVC: ___ ! ! ! ! Description: __________________________________________________ ! ! ! ! Press PF5 to confirm ! ! ! ! Command ==> ! ! PF1 Help PF3 Exit PF5 Add ! ! ! +------------------------------------------------------------------------+ |
Enter values for the following parameters for the SYSCO file:
| Parameter | Description |
|---|---|
| File Name | The logical name of the SYSCO file. This name identifies the ownership and purpose of the SYSCO file. Therefore it must exactly match the name given in the documentation of the Adabas option that requires this file. |
| DB ID | The ID of the database that contains the SYSCO file. |
| File Number | The number of the SYSCO file. |
| SVC | The number of the Adabas SVC that is used by the database which contains the SYSCO file. This parameter is only needed for z/OS and VSE systems. |
| Description | Free-format text describing the SYSCO file. |
When you have entered the parameter settings, press PF5 to save them.
The SYSCO file is now ready for use. You might need to restart any software component that will rely on the newly defined file.
to maintain a SYSCO file definition
On the System Coordinator Group menu, enter ‘f’ in the C column adjacent to an entry in the Group Name column. The following screen will appear:
12:39:17 ***** A D A B A S SYSTEM COORDINATOR 8.1.2 ***** 2006-07-21
- System Coordinator File Definitions - C11270M1
Run-mode: Local
Group Name: CORGROUP
C File Name DB ID Fnr Description
_ ATMMTR 135 175 ATM MIGRATED TRANSACTION RECOR <== End of List
Mark with D(isplay),M(odify),P(urge)
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Refr Add Menu |
From this screen, you can
display a file definition by entering ‘d’ in the C column adjacent to the File Name entry;
modify a file definition by entering ‘m’ in the C column adjacent to the File Name entry;
purge a file definition by entering ‘p’ in the C column adjacent to the File Name entry;
add a new file definition by pressing PF10.
If you choose to display or modify a file definition, you will see a window of the same format as when you first defined the file. If you are modifying the definition, you must press PF5 after making your changes, to save them.
