Version 8.2.2
 —  Adabas System Coordinator 8.2.2 Release Notes  —

Enhancements

The following features have been enhanced for Version 8.2.2:


Daemon Network Node Number Included in Messages

Messages issued by Adabas System Coordinator daemon have been enhanced. They now include as a prefix the node (in the Adabas network) of the daemon. This enables messages from different daemons to be easily distinguished.

Top of page

Online Fix Description

The fix display in SYSCOR has been enhanced to include a short description of each fix that is applied which helps you to get a better understanding of each fix that is in use.

Top of page

Activity display for jobs

You can now display all System Coordinator activities for every job in the system whether running local, pulsing or daemon mode. This allows you to see exactly what is happening in each job in the system. All you have to do is configure the client runtime controls to make the activity details available to the System Coordinator group running in your system. Refer to the section Maintain Client Runtime Controls in the Adabas System Coordinator Online Services documentation for more information. For information about the activity displays, please refer to Adabas Client Activities.

Top of page

Activity display for client sessions

You can now display all System Coordinator activities for every Adabas client session in the system whether running local, pulsing or daemon mode. This allows you to see exactly what is happening in each Adabas client session in the system. All you have to do is configure the client runtime controls to make the activity details available to the System Coordinator group running in your system. Refer to the section Maintain Client Runtime Controls in the Adabas System Coordinator Online Services documentation for more information. For information about the activity displays, please refer to Adabas Client Activities.

Top of page

New memory management options, removing usage of user-key ECSA

System Coordinator offers new options for memory management. These options reduce the amount of memory consumed and also allow advanced crash-recovery capabilities for compliant TP systems such as CICS. They also remove the usage of user-key ECSA, which was a requirement for DTR client jobs in previous System Coordinator versions.

Additionally, there is no longer a need to define a System Coordinator group cache structure; this option has been removed from the online services Daemon Group Parameters maintenance.

Top of page

Support for CICS threadsafe operation

At version 8.2 CICS threadsafe operation is the default. In threadsafe mode, all load modules required by System Coordinator and its sibling products must reside in the CICS RPLLIB, with appropriate definitions (or autoinstall). Also, the Debug Event Monitor and local DDMSG files are disabled when running in threadsafe mode. If you wish to use either of these facilities, set the "Threadsafe operation" runtime control to N and then set it back after you have finished.

Top of page

Optional use of latency file

A System Coordinator group can be configured to use a latency file to contain "at rest" sessions.

Top of page

Optional use of dataspaces

Adabas System Coordinator daemons and client jobs can be configured to use dataspaces for latent ("at rest") sessions or for current activity displays in addition to private or common memory.

Top of page

Daemon COLD start option

If you have configured the daemon to use common memory, it will automatically recover that common memory when restarting. If you wish to discard the memory and start afresh, specify START=COLD in the daemon’s DDCARD input file. This replaces the former Automatic pool recovery group configuration option.

Top of page

Enhanced online services

The SYSCOR Natural application has been enhanced:

Top of page

Enhanced support for BS2000 and UTM

Adabas System Coordinator’s use of common memory pools has been revised to give greater flexibility and reliability:

Top of page