Runtime controls determine the operational behavior of Adabas Transaction Manager in the job. You can adjust this behavior 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.
Note:
See section Parameters for a complete description
of all client runtime controls.
Note:
Client runtime controls are shared between all installed optional
products, and can be defined by any Online Services application (SYSCOR,
SYSAVI, SYSAFP, SYSATM).
To display a list of jobs with runtime control definitions
Select service 1 from the Maintenance menu
or enter the command 1.1 on the command line.
08:29:12 ***** A D A B A S TRANSACTION MANAGER 8.2.2 ***** 2006-04-13
- Client Runtime Controls (ATM) - U11300M1
Reposition to Type: ________
Name: ________
Client Controls
C Type Name AFP AVI ATM COR Comments
_ Batch UKAQBDUS Y Y Overrides,Info
_ UKAQBMM0 Y Y
_ UKAQB85A Y Y Overrides,Info
_ UKPDNAT Y Y Overrides,Info
_ UKPDSER Y Y Overrides,Info
_ UKPDV75 Y Y
_ UKPDV75A Y Y
_ UKPDV75B Y Y
_ UKPDWLS Y Overrides,Info
_ CICS *DEFAULT Y Y Overrides,Info
_ IMS (DTR) *DEFAULT Y Y
_ TSO *DEFAULT Off Y Overrides,Info
Mark with Jobs,Modify,Purge,Rename,Copy,Overrides,Information,History
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Refr Top Back Fwd Bot Add Prods Menu
|
Press PF11 to view the Adabas add-on products for which runtime controls are currently defined, and then press PF11 again in order to modify the controls related to that product.
Press PF8 to move to the next page, or use the Reposition field to position anywhere within the list.
A set of runtime controls includes the name of the Adabas System Coordinator group in which the job will execute. You must define the group before you create any runtime controls that include the name of the group. Refer to the Adabas System Coordinator documentation for details of groups, and how to define them.
To add a new set of runtime controls
Once you have defined your System Coordinator group, or groups, navigate to ATM’s Runtime Controls screen, and press PF10.
The following menu will appear:
08:33:18 ***** A D A B A S TRANSACTION MANAGER 8.2.2 ***** 2006-04-13
- Add Client Runtime Control - U11310M1
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
|
Select the required job type and press Enter. A new screen will prompt you to enter the name of the job for which you want to define runtime controls. You can use wild-card notation to represent a collection of jobs, and you can define a default set of runtime controls for the chosen type of job. For further details, refer to the documentation for the Adabas System Coordinator.
When you have entered the job name, press PF5. You will be prompted to enter some information for the Adabas System Coordinator. Refer to the Adabas System Coordinator documentation for details. When you have done this, press PF5. You will see the following screen, which allows you to specify the ATM runtime controls for the current job.
12:25:13 ***** A D A B A S TRANSACTION MANAGER 8.2.2 ***** 2012-02-23
- Adabas Transaction Manager Runtime Controls - U1133TM1
Job Type: Batch
Name: TESTJOB2 Last modified 2012-02-23 at 12:25:13 by UKGXN
ATM ON/OFF ...... ON_ Added 2012-02-23 at 12:25:13 by UKGXN
System coordinator group name ......... WORKSHOP
Maximum number of open databases ...... 4____
Continuous operation mode ............. FORCE (Yes/No/Force)
Coordinate Adabas outside the group ... YES (Yes/RM/No)
ET data storage location............... NONE (TM/Adabas/RM/NONE)
Generate OP commands .................. NO_ (Yes/No)
Use extended hold processing .......... NO_ (Yes/No)
Distributed transaction timeout(secs).. 0_______ (0 to 16777215)
Adabas transaction dynamics ........... FULL__ (TP/Full/Forced)
Open distributed transaction support... NO_ (Yes/No)
Transaction control by other vendors NO_ (Yes/No)
by ET .......... YES (Yes/No)
by BT .......... YES (Yes/No)
by CL .......... YES (Yes/No)
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Upd Menu
|
For specific information on each of these controls, see section Client Runtime Controls.
Note:
The initial controls for the new job are copied from those
specified in the *DEFAULT entry for the selected job type. If no default entry
exists for the job type, then product default values are displayed.
Note:
Each job or TP system that uses Adabas Transaction Manager must be
associated with an Adabas System Coordinator group, the name of which must be
specified in the above screen. If you have not yet defined the group in which
your job will execute, quit this operation, and use the Adabas System
Coordinator Online Services application to define the group. Refer to the
Adabas System Coordinator documentation for details.
Change any of the displayed values as required, then use PF5 to save the updated control settings.
To modify client runtime controls, on the client runtime controls
screen, enter the option code "M" next to the job for which
parameters are to be maintained. In the sample screen shown below, the job
parameters for CICS job DAEFCI18 are displayed.
The following screen will be displayed:
11:23:13 ***** A D A B A S TRANSACTION MANAGER 8.2.2 ***** 2014-04-01
- Adabas Transaction Manager Runtime Controls - U1133TM1
Job Type: CICS
Name: DAEFCI18 Last modified 2013-11-08 at 10:47:58 by UKRPE
ATM ON/OFF ...... ON_ Added 2011-10-21 at 13:34:12 by UKLT
System coordinator group name ........... WORKSHOP
Maximum number of open databases ........ 4____
Continuous operation mode ............... FORCE (Yes/No/Force)
Coordinate Adabas outside the group ..... YES (Yes/RM/No)
ET data storage location ................ NONE__ (TM/Adabas/RM/None)
Generate OP commands .................... NO_ (Yes/No)
Use extended hold processing ............ NO_ (Yes/No)
Distributed transaction timeout(secs) ... 0_______ (0 to 16777215)
Adabas transaction dynamics ............. FULL__ (TP/Full/Forced)
Open distributed transaction support .... NO_ (Yes/No)
Transaction control by other vendors NO_ (Yes/No)
by ET .......... YES (Yes/No)
by BT .......... YES (Yes/No)
by CL .......... YES (Yes/No)
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Upd Menu |
For specific information on each of these controls, see the section Client Runtime Controls.
Overrides to the base-level client runtime controls may be specified. This provides the possibility for a greater granularity of control, allowing controls to relate specifically to particular logins, job steps or transactions.
Enter "O" (for Overrides) next to a job which already has Adabas Transaction Manager client controls in the Client Runtime Controls screen.
Note:
Not all job types will support overrides.
Then enter PF10 to add some client runtime control overrides.
The following screen will be displayed:
11:24:32 ***** A D A B A S TRANSACTION MANAGER 8.2.2 ***** 2014-04-01
- Add Client Runtime Control Override - U11381M1
Type: CICS Name: DAEFCI18
Select the override type ....: _ Login id
(mark one) X Transaction
and specify the override name: ATMTEST1
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Add Menu |
Select the type of override required, and the override name, and press PF5 to add.
Select "M" to modify the newly created override client runtime controls.
The following screen will be displayed:
11:26:55 ***** A D A B A S TRANSACTION MANAGER 8.2.2 - DEMO ***** 2014-04-01
- Adabas Transaction Manager Runtime Controls - U1138TM1
Control Type: CICS Override Type: Transaction Name: ATMTEST1
Name: DAEFCI18 Last modified 2014-04-01 at 11:26:55 by UKRPE
ATM ON/OFF ...... ON_ Added 2014-04-01 at 11:26:55 by UKRPE
System coordinator group name ........... WORKSHOP
Maximum number of open databases ........ 4
Continuous operation mode ............... FORCE (Yes/No/Force)
Coordinate Adabas outside the group ..... YES (Yes/RM/No)
ET data storage location ................ NONE__ (TM/Adabas/RM/None)
Generate OP commands .................... NO_ (Yes/No)
Use extended hold processing ............ NO_ (Yes/No)
Distributed transaction timeout(secs) ... 0_______ (0 to 16777215)
Adabas transaction dynamics ............. FULL__ (TP/Full/Forced)
Open distributed transaction support..... NO_ (Yes/No)
Transaction control by other vendors NO_ (Yes/No)
by ET .......... YES (Yes/No)
by BT .......... YES (Yes/No)
by CL .......... YES (Yes/No)
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Upd Menu |
Overridable runtime controls may be modified and saved using "PF5".
In the Client Runtime Controls screen "Overrides" will appear in the comments (as seen in the screen below).
These overrides will now apply in preference to the base-level controls for the specific login, job step or transaction.
10:59:03 ***** A D A B A S SYSTEM COORDINATOR 8.2.2 (I007) ***** 2014-04-02
- Client Runtime Controls (COR) - U11300M1
Run-mode: Daemon (node 2650) Reposition to Type: ________
Name: ________
Client Controls
C Type Name AFP AVI ATM COR BOX Comments
_ CICS DAEFCI18 Y Y Y Y Y Overrides
_ TSO *DEFAULT Y Y Off
_ LAM Y Off Off Y Off
_ UKGXN Y Off Off Y Off
_ UKRPE Y Y Off Y
_ UKSJU Y Y Y Y Y
_ UKSJU1 Y Y Y Y Y
_ UKSTAD Y Y Y
_ SPATs STAD**** Y
_ GXNTEST Y
Mark with Jobs,Modify,Purge,Rename,Copy,Overrides,Information,History
End of List
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Refr Back Add Prods Menu |
Please refer to the Adabas System Coordinator documentation and the section on Dynamic Client Runtime Configuration for Experts.