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

This service is used to define and maintain the parameters and definitions that are required by Adabas System Coordinator.

• Maintenance Menu

• Maintain Client Runtime Controls

• Maintain Daemon Groups

Maintenance Menu

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.

  17:36:58 ***** A D A B A S SYSTEM COORDINATOR 8.2.2 ***** 2011-12-03 - Maintenance - C11000M1 Run-mode: Pulsing (node 2650) 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 Menu

  From this menu, you can	Service	Cmd
  maintain client runtime controls	1	1.1
  maintain daemon group parameter values	2	1.2

Maintain Client Runtime Controls

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.

• List Runtime Controls

• Add a Runtime Control

• Maintain Runtime Controls

List Runtime Controls

To display a list of existing definitions

1. Select service 1 from the Maintenance menu or enter the command 1.1 on the command line.

   18:08:21 ***** A D A B A S SYSTEM COORDINATOR 8.2.2 ***** 2011-12-03 - Client Runtime Controls (COR) - U11300M1 Run-mode: Pulsing (node 2650) 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 _ TSO *DEFAULT Y Y Y 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 Add Prods Menu

2. 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.

3. 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.

4. 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

5. If you wish to display or modify controls or overrides for one of the other products, press PF11 until the required product appears in the screen title and message line:

   18:10:27 ***** A D A B A S SYSTEM COORDINATOR 8.2.2 ***** 2011-12-03 - Client Runtime Controls (AFP) - U11300M1 Run-mode: Pulsing (node 2650) 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 _ TSO *DEFAULT Y Y Y Y Mark with Jobs,Modify,Purge,Rename,Copy,Overrides,Information,History Now maintaining Adabas Fastpath runtime controls Command ==> Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Refr Add Prods Menu

6. If there is more than a screen of definitions, use PF7 and PF8 to scroll up and down, m and PF7 and m and PF8 to go to the top or bottom of the list, or use the Reposition field to position anywhere within the list.

Add a Runtime Control

To add a new definition

1. Press PF10 from the Client Runtime Controls list.

   The following window will appear:

   18:16:44 ***** A D A B A S SYSTEM COORDINATOR 8.2.2 ***** 2011-12-03 - Add Client Runtime Control - U11310M1 Run-mode: Pulsing (node 2650) 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

2. 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.

3. 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:

   18:17:29 ***** A D A B A S SYSTEM COORDINATOR 8.2.2 ***** 2011-12-03 - Add Client Runtime Control - U11310M4 Run-mode: Pulsing (node 2650) 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 daemons) with PRODUCT=DTR AND the daemon(s) in 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

4. Enter the service name (which may not contain * wildcards, in this example CICSPROD was entered) and press PF5 to continue:

   15:41:23 ***** A D A B A S SYSTEM COORDINATOR 8.2.2 (I001) ***** 2012-08-29 - System Coordinator Runtime Controls - U11310M5 Run-mode: Pulsing (node 2660) Type: CICS (DTR) Name: CICSPROD Operation: Normal autodetect: X Enable without products: _ Disable all: _ API runtime overrides....: N (Y/N) Threadsafe operation...: Y (Y/N) 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) Messages - Local.........: Console Y and/or DDMSG file _ Or - Daemon routing: _ Latency - Local (Y/N)....: N Latency - Daemon (Y/N)...: Y to disk........: N Activity pulse every.....: _______ commands or _____ seconds Group name...............: ________ Daemon connection messages (Y/N): N Area.....................: ________ System...................: ________ Command ==> Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Add Menu

5. 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:50:27 ***** A D A B A S SYSTEM COORDINATOR 8.2.2 ***** 2012-03-13 - System Coordinator Runtime Controls - U11310M5 Run-mode: Pulsing (node 2650) Type: CICS (DTR) Name: CICSPROD Operation: Normal autodetect: X Enable without products: _ Disable all: _ API runtime overrides....: N (Y/N) Threadsafe operation...: Y (Y/N) 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) Messages - Local.........: Console Y and/or DDMSG file _ Or - Daemon routing: _ Latency - Local (Y/N)....: N Latency - Daemon (Y/N)...: Y to disk........: N Activity pulse every.....: _______ commands or _____ seconds Group name...............: DEMO82__ Daemon connection messages (Y/N): N Area.....................: ________ System...................: ________ Fields Modified - Use PF5 to Update or PF3 to Exit Command ==> Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Add Menu

6. Press PF5 again to add the control.

   10:51:20 ***** A D A B A S SYSTEM COORDINATOR 8.2.2 ***** 2012-03-13 - System Coordinator Runtime Controls - U11310M5 Run-mode: Pulsing (node 2650) Type: CICS (DTR) Name: CICSPROD Operation: Normal autodetect: X Enable without products: _ Disable all: _ API runtime overrides....: N (Y/N) Threadsafe operation...: Y (Y/N) 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) Messages - Local.........: Console Y and/or DDMSG file _ Or - Daemon routing: _ Latency - Local (Y/N)....: N Latency - Daemon (Y/N)...: Y to disk........: N Activity pulse every.....: _______ commands or _____ seconds Group name...............: DEMO82__ Daemon connection messages (Y/N): N Area.....................: ________ System...................: ________ Parameter ADDED Command ==> Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Upd More API 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 PF10 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

   18:21:32 ***** A D A B A S SYSTEM COORDINATOR 8.2.2 ***** 2011-12-03 - System Coordinator Runtime Controls - U11310M6 Run-mode: Pulsing (node 2650) 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 PF9 to define additional options and select option 1 to define command retry requirements, option 2 to define debug settings or option 3 to define unified trace settings:

   +---------------------------------------------------------+ | 18:23:28 Runtime Controls 2011-12-03 | | - Additional - U1SCJAM1 | | | | Code Service | | ---- ---------------------- | | 1 Command Retry | | 2 Debug Settings | | 3 Unified Trace 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 .

   17:49:17 ***** A D A B A S SYSTEM COORDINATOR 8.2.2 ***** 2010-12-15 - Debug Event Monitor Controls - U1SCJBM1 Debug all sessions (Y/N) .......: Y Maximum debug reports ......: _____ Response code: ___ Sub-code : _____ or mark for generic monitor : _ Optionally for database ....: _____ and file number ............: _____ Additional debug monitor (Y/N), use only as directed by Software AG: System Coordinator .........: N Adabas Transaction Manager .: N Adabas Fastpath ............: N Adabas Vista ...............: N Report content in order of output amount, mark one: None .......................: X Client session only ...........: _ All sessions for the client : _ All sessions for the job ......: _ All memory for the job .....: _ Additional report content (Y/N): CIB ...............: Y CAB ..............: Y ID table .........: Y Registers on entry : Y TP areas .........: Y Stack ............: Y Command ==> Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Upd

   • Use unified trace settings to define trace requirements for this client job:

     1. Size of in-memory trace buffer.

     2. Trace collection; local trace file is only available for batch-type jobs and forward to the daemon trace file is only available for jobs defined to use a daemon

     3. Adabas response code and sub-code that cause trace data to be written and whether or not generic errors trigger tracing

     4. Whether or not to trigger a debug event on response code trace activation

     18:25:48 ***** A D A B A S SYSTEM COORDINATOR 8.2.2 ***** 2011-12-03 - Unified Trace Settings - U1SCTRM1 Trace size (KB): 0_ (no tracing = 0; maximum = 32) Trace collection (mark one) No collection.......................: X In memory only......................: _ Local trace file....................: Forward to the daemon trace file....: _ Dynamic options Limited debug trace: Response code trace activation....: 0__ Sub-code..........................: 0____ Generic error response codes (Y/N): N Debug event activation (Y/N)......: N Command ==> Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Upd

7. Here is an example of adding controls for a batch job. Press PF10 from the list, mark Batch and press Enter to continue:

   18:33:14 ***** A D A B A S SYSTEM COORDINATOR 8.2.2 ***** 2011-12-03 - Add Client Runtime Control - U11310M1 Run-mode: Pulsing (node 2650) 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 - type 1 _ API controlled - type 2 Command ==> Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Menu

8. Enter the jobname and press PF5:

   18:35:06 ***** A D A B A S SYSTEM COORDINATOR 8.2.2 ***** 2011-12-03 - Add Client Runtime Control - U11310M3 Run-mode: Pulsing (node 2650) Type: Batch Name: natbat__ (* 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

9. 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.

10. Controls are always matched on type. The order of search within type is

    1. Match on exact job name.

    2. Match on wild card definitions.

    3. 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.

11. 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.

    10:52:32 ***** A D A B A S SYSTEM COORDINATOR 8.2.2 ***** 2012-03-13 - System Coordinator Runtime Controls - U11310M5 Run-mode: Pulsing (node 2650) Type: Batch Name: NATBAT__ Operation: Normal autodetect: X Enable without products: _ Disable all: _ API runtime overrides....: N (Y/N) Use additional exits.....: N (Y/N) Maximum idle time (sec)..: __________ Messages - Local.........: Console Y and/or DDMSG file _ Or - Daemon routing: _ Latency - Local (Y/N)....: Y Latency - Daemon (Y/N)...: N to disk........: N Activity pulse every.....: _______ commands or _____ seconds Group name...............: ________ Daemon connection messages (Y/N): N Area.....................: ________ System...................: ________ Command ==> Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Add Menu

Maintain Runtime Controls

To maintain a job parameter

• Select it by entering one of the following options in column C on the Client Runtime Controls list:

  j	list jobs
  m	modify
  p	purge
  r	rename
  c	copy
  o	overrides
  i	site information

  Modify provides 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.

• Modify Runtime Control
• List jobs in Runtime Control
• Purge a Runtime Control
• Rename a Runtime Control
• Copy a Runtime Control
• Maintain Site Information
• Maintain Client Runtime Control Overrides
• Dynamic Client Runtime Configuration for Experts

Modify Runtime Control

To modify a runtime control:

1. Select it from the list by marking column C with an "m".

   16:03:05 ***** A D A B A S SYSTEM COORDINATOR 8.2.2 ***** 2012-03-12 - System Coordinator Runtime Controls - U11310M5 Run-mode: Pulsing (node 2650) Type: COM-PLETE Name: DAEFCODE Operation: Normal autodetect: X Enable without products: _ Disable all: _ API runtime overrides....: N (Y/N) 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) Messages - Local.........: Console _ and/or DDMSG file _ Or - Daemon routing: _ Latency - Local (Y/N)....: Y Latency - Daemon (Y/N)...: N to disk........: N Activity pulse every.....: _______ commands or _____ seconds Group name...............: ________ Daemon connection messages (Y/N): N Area.....................: ________ System...................: ________ Command ==> Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Upd More API Menu

2. Make any necessary modifications.

3. Use PF9 to modify additional options.

4. Use PF10 to modify the list of permissible API overrides.

5. Press PF5 to confirm your changes or PF3 to exit.

List jobs in Runtime Control

To list jobs in a runtime control:

1. Select it from the list by marking column C with a "j".

   15:25:27 ***** A D A B A S FASTPATH SERVICES 8.2.2 ***** 2012-03-08 - Client Runtime Service Members - U11390M1 Job type: IMS (DTR) Service name: BLA01 C Name Comments _ IMSJOB1 Mark with Purge,Rename,History Top of List Command ==> Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Refr Add Menu

2. List jobs is only relevant for DTR definitions. It 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.

Purge a Runtime Control

To purge a runtime control

1. 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 ! ! ! +------------------------------------+

2. Mark which products’ runtime controls you wish to purge or All to purge the entire control.

3. Press PF5 to confirm

Rename a Runtime Control

To rename a runtime control

1. 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 ! ! ! +------------------------------------+

2. Specify the new name, which must not already exist.

3. Press PF5 to confirm

Copy a Runtime Control

To copy a runtime control

1. 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 ! ! ! +------------------------------------+

2. Mark which products’ runtime controls you wish to copy.

3. Specify the job name to which these runtime controls will be copied, which must not already exist.

4. If you select All, you may also copy any defined overrides by entering Y against Copy Overrides.

5. Press PF5 to confirm

Maintain Site Information

To maintain site information

1. Select it from the list by marking column C with a "i".

   11:45:28 ***** A D A B A S SYSTEM COORDINATOR 8.2.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

2. Modify the site information as required and press PF5 to save your changes, or press PF9 to purge the site information.

Maintain Client Runtime Control Overrides

To list runtime control overrides

1. Select it from the Runtime Control maintenance list by marking column C with an ‘o’.

   18:45:25 ***** A D A B A S SYSTEM COORDINATOR 8.2.2 ***** 2011-12-03 - Client Runtime Controls Override Summary (COR) - U11380M1 Run-mode: Pulsing (node 2650) Reposition to Type: ________ Type: CICS (DTR) Name: CICCLUST Name: ________ Overrides C Type Name AFP AVI ATM COR Comments _ Transaction N426 Y Y Mark with 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 Prods Menu

2. This screen lists the runtime control overrides that have been defined for each product.

3. 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.2.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

4. Press PF5 to add an empty override, which you can then modify as required:

   18:47:13 ***** A D A B A S SYSTEM COORDINATOR 8.2.2 ***** 2011-12-03 - Client Runtime Controls Override Summary (COR) - U11380M1 Run-mode: Pulsing (node 2650) Reposition to Type: ________ Type: CICS (DTR) Name: CICCLUST Name: ________ Overrides C Type Name AFP AVI ATM COR Comments _ Transaction NATP *Added (empty) _ N426 Y Y Mark with Modify,Purge,Rename,Copy,Information Command ==> Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Refr Add Prods Menu

5. Enter one of the following options in the C column to select an entry:

   m	modify
   p	purge
   r	rename
   c	copy
   i	site information

6. 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.

7. Use PF11 to select the product for which you want to define or modify an override.

Dynamic Client Runtime Configuration for Experts

You can dynamically change some runtime controls for your current session. To do this, enter CORENV and use PF11 to select the required product as in the following example.

Note:
Some dynamic changes may take some time to take effect depending upon the product/setting in question.

 18:49:59     ***** A D A B A S   SYSTEM COORDINATOR 8.2.2 *****     2011-12-03
                            -  Main Menu  -                          C1MAINM1  
 Run-mode: Pulsing (node 2650)                                                 
                                                                               
                  Code    Service                                              
                  ----    -------------------------                            
                   0      System Settings                                      
                   1      Maintenance                                          
                   2      Current Activity Displays                            
                   3      Special Services                                     
                   4      About System Coordinator                             
                   .      Exit                                                 
                  ----    -------------------------                            
           Code..: _                                                           
                                                                               
                                                                               
                                                                               
You can easily switch around the tools for Fastpath, Vista etc by use of
PF11, or use the codes COR, AFP, AVI, AAF, ATM as commands - anytime.

Command ==> corenv

Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help        Exit                                            Prods Vers

Which shows you the current System Coordinator runtime controls in effect for your session.

 16:09:27            ***** CURRENT SESSION CONTROLS *****            2012-03-12
                  -  System Coordinator Session Controls  -          CORENVM1  
                                                                               
                                                                               
   API runtime overrides....: N          Threadsafe operation...: Y            
   Use additional exits.....: N                                                
   Maximum idle time (sec)..: 3600       Non-terminal idle time.:              
   Generate RSP009/79 (Y/N).: Y (until 0          seconds elapse)              
   Cleanup at start.........: N (Y/N)                                          
   Messages - Local.........: Console Y and/or DDMSG file _                    
         Or - Daemon routing: _                                                
   Latency - Local (Y/N)....: Y                                                
             TSQ prefix.....: WORK                                             
   Latency - Daemon (Y/N)...: N                                                
             to disk........: N                                                
   Activity pulse every.....: 100     commands or 30    seconds                
   Group name...............: WORKSHOP   Daemon connection messages (Y/N): N                                      
   Area.....................: ________   System...................: ________                                                                            
                                                                               
                                                                               
Command ==>
                                                                   
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help        Exit        Upd   Reset             More        Prods

Maintain Daemon Groups

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 numbers of the daemons 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.

• Main Menu

• Adding a Daemon Group Definition

• Maintaining a Daemon Group Definition

• Maintain a Daemon Group Daemon Definition

Main Menu

To invoke the daemon group maintenance menu

1. Select service 2 from the Maintenance menu or enter the command 1.2 on a command line.

   09:25:46 ***** A D A B A S SYSTEM COORDINATOR 8.2.2 ***** 2011-12-04 System Coordinator Groups C11200M1 Run-mode: Pulsing (node 2650) C Group Name Type SVC ID Daemons _ DEMO82 Multi 254 2 _ TSTGROUP Single 253 1 Mark with M(odify),P(urge),R(ename),L(ist) Command ==> Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Refr Add Menu

2. Enter one of the following options in the C column:

   m	Modify group definition
   p	Purge group definition
   r	Rename group definition
   l	List daemons in group

3. Use PF10 to add a new group definition

Adding a Daemon Group Definition

To add a new daemon group definition

1. Press PF10 on the System Coordinator Group menu. The following screen will appear:

   +-------------------------------------------------------------------+ | 09:27:38 Add 2011-12-04 | | System Coordinator Group C11210M1 | | | | Group Name: ________ SVC ID: _____ | | | | System Type: _ Standard single-system image... | | (Mark one) There is only one daemon in the group. | | _ Standard multi-system images - XCF... | | This enables multiple XCF group daemons. | | _ Standard multi-system images - Net-Work... | | This enables multiple Net-Work group daemons. | | | | Group-wide latency service: | | Full crash recovery disk file (Y/N): N | | | | | | | | | | | | Command ==> | | PF1 Help PF3 Exit PF5 Add PF9 More | | | +-------------------------------------------------------------------+

2. 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.

3. 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.

4. In the fields System Type, specify whether the group is to coordinate:

   • A single system image.

   • Multiple system images. This is used to support coordinator daemons running Adabas Fastpath buffers or Adabas Transaction Manager across multiple system images and also to support dynamic transaction routing across multiple system images.

   • Multiple system images using Entire Net-Work for communication between images. This is used to support coordinator daemons running Adabas Fastpath buffers or Adabas Transaction Manager across multiple system images and also to support dynamic transaction routing across multiple system images. You are recommended only to use Entire Net-Work if XCF is not available.

5. In the field Full crash recovery disk file, select whether or not latent sessions for client jobs managed by this daemon group are to be written to disk file. This feature allows client sessions to resume processing after a client job or daemon failure.

6. 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.

7. Press PF5 to add the group definition.

8. Press PF9 to see more Daemon Group definition fields and the following screen will appear:

   +------------------------------------------------------------------------+ | 16:04:19 Additional Group Parameters 2012-03-08 | | System Coordinator Groups C11210M2 | | | | | | Messages - daemon...... Console: Y and/or DDMSG file: _ | | Messages - databases... Console: Y and/or DDMSG file: _ | | | | | | | | | | | | | | Command ==> | | PF3 Quit PF5 Upd | | | | | | | +------------------------------------------------------------------------+

9. In the "Runtime messages – databases" fields select either one or both options for the destination of messages output by the Adabas System Coordinator component in the database and the other products that use its services.

   Messages, by default, are written to the console. Messages issued by databases that are within the same daemon group may either be directed instead (or in addition) to a file (DDMSG) by selecting the Local file option. The DDMSG output must be introduced to the databases execution control script and the file must be correctly in place for the messages to appear. In some operating systems it will automatically appear to list output.

10. The settings from the "More" screen can be confirmed by using PF10. The daemon group will not be created until PF5 is pressed on the first screen.

11. Press PF5 to confirm any changes made on this screen, or PF3 to return to the main group screen.

Maintaining a Daemon Group Definition

After adding the group, you can change any of its attributes, by entering ‘m’ against it:

+-------------------------------------------------------------------+
|  10:55:35                   Modify                    2011-12-04  |
|                    System Coordinator Group           C11230M1    |
|                                                                   |
|             Group Name: DEMO82        SVC ID: 254__               |
|                                                                   |
|    System Type: _  Standard single-system image...                |
|     (Mark one)     There is only one daemon in the group.         |
|                 X  Standard multi-system images - XCF...          |
|                    This enables multiple XCF group daemons.       |
|                 _  Standard multi-system images - Net-Work...     |
|                    This enables multiple Net-Work group daemons.  |
|                                                                   |
|    Group wide latency service:                                    |
|      Full crash recovery disk file (Y/N): N                       |
|                                                                   |
|                                                                   |
|                                                                   |
|                                                                   |
|                                                                   |
|  Command ==>                                                   |
|      PF1 Help         PF3 Exit       PF5 Upd        PF9 More      |
|                                                                   |
+-------------------------------------------------------------------+

Make any changes required and press PF5 to confirm them. Press PF9 to see further parameters:

+------------------------------------------------------------------------+
|  16:10:00         Additional Group Parameters         2012-03-08       |
|                   System Coordinator Groups           C11210M2         |
|                                                                        |
|                                                                        |
|  Messages - daemon...... Console: Y and/or DDMSG file: _               |
|  Messages - databases... Console: Y and/or DDMSG file: _               |
|                                                                        |
|                                                                        |
|                                                                        |
|                                                                        |
|                                                                        | 
|                                                                        |
| Command ==>                                                         |
|                     PF3 Quit        PF5 Upd                            |
|                                                                        |
|                                                                        |
|                                                                        |
+------------------------------------------------------------------------+

Make any changes required then enter PF5 to confirm these changes or PF3 to return to the first screen.

+------------------------------------------------------------------------+
|  16:10:00         Additional Group Parameters         2012-03-08       |
|                   System Coordinator Groups           C11210M2         |
|                                                                        |
|                                                                        |
|  Messages - daemon...... Console: Y and/or DDMSG file: _               |
|  Messages - databases... Console: Y and/or DDMSG file: _               |
|                                                                        |
|                                                                        |
|                                                                        |
|                                                                        |
|                                                                        | 
|                                                                        |
| Command ==>                                                         |
|                     PF3 Quit        PF5 Upd                            |
|                                                                        |
|                                                                        |
|                                                                        |
+------------------------------------------------------------------------+

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:

+-------------------------------------------------+
|  11:25:01          Purge            2011-09-01  |
|          System Coordinator Group   C11240M1    |
|                                                 |
|              Group Name: TESTMULT               |
|                                                 |
|                  SVC ID: 253                    |
|                                                 |
|              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:

+-------------------------------------------------+
|  11:25:31          Rename           2011-09-01  |
|           System Coordinator Group  C11250M1    |
|                                                 |
|              Group Name: TESTMULT               |
|                                                 |
|                New Name: ________               |
|                                                 |
|             PF5 to Confirm Rename               |
|                                                 |
|                                                 |
|  Command ==>                                 |
|        PF1 Help    PF3 Exit    PF5 Upd          |
|                                                 |
+-------------------------------------------------+

Maintain a Daemon Group Daemon Definition

To maintain a daemon group daemon definition

1. On the System Coordinator Group menu, enter "l" in the C column adjacent to an entry in the Group Name column. The following screen will appear:

   10:59:37 ***** A D A B A S SYSTEM COORDINATOR 8.2.2 ***** 2011-12-04 - Daemon Parameters (COR) - C11260M1 Run-mode: Pulsing (node 2650) Group Name: WORKSHOP Operating System: Multi SVC ID: 254 Daemon C Job Name Node ID _ ICFDCOR5 2650_ <== Top of List _ ICFDCOR6 2660_ <== End of List ________ _____ ________ _____ ________ _____ ________ _____ ________ _____ ________ _____ ________ _____ ________ _____ ________ _____ ________ _____ Mark with M(odify),P(urge) Command ==> Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Refr Upd Add Prods Menu

   From this screen, you can

   • Use PF11 to select the product whose daemon parameters you wish to maintain.

   • Purge a daemon by entering ‘p’ in the C column adjacent to the Daemon Job Name entry;

   • change the daemon job name or node id by overtyping it and pressing PF5;

   • add a new daemon entry by pressing either PF5 or PF10; or

   • modify a daemon entry by entering ‘m’ in the C column adjacent to the entry to be modified.

2. If you are adding a new group, you must add at least one daemon.

   For each daemon, specify the following:

   • Daemon 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.

3. Entering m against a daemon presents the product specific parameter modification screen.

   Maintaining Adabas System Coordinator daemon parameters:

   17:07:44 ***** A D A B A S SYSTEM COORDINATOR 8.2.2 ***** 2012-03-12 - Adabas System Coordinator Daemon Parameters - C11261M1 Run-mode: Pulsing (node 2650) Group: WORKSHOP Daemon: ICFDCOR5 SVC: 254 Node: 2650 System: Multi Recovery Continuous Operation (Y/N).......: Y Daemon latency/pulse services Shared memory area size (k)......: 1800____ Minimum (k): 0_______ Dataspace name (if used)..: #WRKSP1_ Daemon memory area size (k)......: 0_______ Minimum (k): 0_______ Unified trace settings Trace size (k)..................: 32 (no tracing = 0; maximum = 32) Use trace file (Y/N)............: N Wraparound file when full (Y/N).: N Note: Activation must be performed manually in daemon/database 'tasks'. Note: This same configuration is shared by any databases too. Debug settings CORDUMP for transient situations: N Number of outputs: 0____ Command ==> Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Upd Menu

   Here you can modify latency/activity services:

   • Whether to use shared memory, maximum and minimum sizes and whether to use a dataspace and unified trace settings for this daemon and (currently) the databases it knows about.

   • Trace buffer size, whether to write to a trace file and whether to wraparound the trace file when it fills. Make any required changes and press PF5 to confirm them or PF3 to return to the daemon list.

Maintaining Adabas Transaction Manager daemon parameters:

For more information refer to the How to maintain TM controls section in Adabas Transaction Manager Online Services documentation.

www.softwareag.com

Copyright © 2013 Software AG, Darmstadt, Germany.

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