The following features have been enhanced for version 7.4.2.
Internal improvements have resulted in reduced processor path length in Adabas System Coordinator, particularly in heavily loaded, multiuser TP systems.
When Adabas System Coordinator detects a client that has been
dynamically routed across a Sysplex, it manages the move of client session
context to the new system. Previously this was done separately for each Adabas
session (UB) that has been routed. Clients using Adabas X48 communications
(Natural with ADAMODE=2 or 3) create at least two Adabas
sessions. If 3GL programs are also used, further sessions can be created.
Adabas System Coordinator now identifies all of these sessions as belonging to
the same dynamic transaction, and moves them at the same time, thereby becoming
more tolerant of outages of parts of the TP service.
Messages displayed by the Adabas System Coordinator daemon, as well as exception messages displayed by the client and server components, are now displayed in mixed case.
The following enhancements have been made to the SYSCOR administration application.
The run mode will be displayed on an Environment Information screen at logon. This screen also shows information about the current Coordinator daemon, if one is used.
The run mode can be:
Coordinator not installed. The Adabas link module does not contain the Coordinator stub. Local session information will not be available but all other functions will work.
Local. The TP system is running in local (non-daemon) mode. By default, session information will be obtained locally.
Daemon/nnn. The TP system is running with a Adabas System Coordinator daemon. The daemon Node ID is displayed. By default, session information will be obtained from the daemon.
The run mode is also displayed at the top of all SYSCOR screens.
A new option on the Session Monitoring menu can be used to change the source of session information. For example, you can be running in local run mode, but you can still obtain information from an active Coordinator daemon, by changing the information source to the daemon Node ID.
The current session information source is displayed at the top of all SYSCOR screens.
Job parameters can now be defined in SYSCOR (previously SYSAVI or SYSAFP were required to define job parameters). The new Command Retry and Debug Settings options (if required) must be configured in SYSCOR job maintenance.
There are now three system type specifications for Coordinator groups:
Standard (single system images) . This is the same as in the previous release.
Standard (multisystem images). This is new, and is used to support Coordinator daemons running Adabas Fastpath buffers across multiple system images. It does not support dynamic transaction routing (DTR) across a Parallel Sysplex.
This option was available in the previous release, by selecting type ‘Sysplex’ without specifying a ‘Cluster Facility’ name. It has been made a selectable option, for clarity.
Sysplex (IBM Parallel Sysplex). This is the same as in the previous release.
The limits for Fixed Memory Pool size on the job parameter have been changed for batch jobs. The minimum size is now 32K. This is to reduce unwanted virtual storage allocations in batch jobs.
An inactivity timeout limit can now be specified in the job parameter definition for a job. Also, initial timeout limits can be changed dynamically for a running job. This new feature is provided from the Special Services menu.
Automatic pool recovery can be selected or suppressed using a parameter on the Coordinator Group definition.
The Session Monitoring menu has changed.
There is a new option 0 – Change Information Source.
Option 1 (Active Nodes) is now called Daemon Group Information.
Option 2 (Active Jobs) is now called Adabas Client Jobs.
Option 3 (User Information) has been deleted. This information is now available from the Adabas Client Jobs display. Later menu option are re-numbered.
The Session Monitoring Jobs display has changed:
The display now shows the service name as well as the job name.
The columns User Size and Thread Size have been deleted.
The column Tput (throughput) has been renamed Maximum Concurrent.
The Session Monitoring Client Session (User) display has changed:
When running in DTR mode, all client sessions in the service are displayed. In the previous version, only the sessions attached to the selected Job were displayed. The session display shows the service name as well as the current job name.
There is a new option to sort the client list into name order.
The Session Monitoring Network Display has been changed to identify Adabas Parallel Services nuclei. These are shown as type ‘ADA Cluster(L)’. Also, Adabas (Sysplex) Cluster nuclei are now shown as ‘ADA Cluster(S)’.
