The following features have been enhanced for Version 8.2.2:
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.
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.
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.
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.
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.
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.
A System Coordinator group can be configured to use a latency file to contain "at rest" sessions.
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.
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.
The SYSCOR Natural application has been enhanced:
Better handling of configuration modification. All configuration modification screens now allow PF5 to commit changes and if you make any changes without pressing PF5 you are prompted to commit them with PF5 or exit with PF3.
The Display line command has been removed. Use Modify to view configuration objects. If you use SAF security to protect SYSCOR, you will need READ access to enter the modify screen and UPDATE access to commit modifications.
PF6 (Top) and PF9 (Bot) have been removed. Their functionality is replaced by entering m on the command line and pressing PF7 or PF8 respectively.
PF9 (More) is now used to access additional configuration screens for those objects such as runtime controls and daemon groups which have more than one configuration screen.
PF11 (Prods) has been enhanced so that it automatically cycles around the available products.
Current activity displays have been enhanced to make them easier to use; to provide more dynamic information; and to offer unified trace displays for client jobs, databases and daemons.
A new current activity display option has been introduced to show Adabas activity across all jobs, by login id. For more information refer to Adabas Client Activities.
Adabas System Coordinator’s use of common memory pools has been revised to give greater flexibility and reliability:
The daemon memory pool attributes are now defined for the individual daemon rather than the group. When you first logon to the SYSCOR Natural library and enter the main menu, the daemon definitions are automatically populated from their group.
Each UTM service now has its own common memory pool. Specify the fixed address (the same fixed address must be used by the daemon and by all jobs in the same UTM service). Also specify the size if the fixed pool in the UTM service’s runtime control. As a guide, the size should allow 100kb for each job in the service.
