This document covers the following topics:
Migration of Log Data to the System Automation Tools Log File
Usage of Separate System Automation Tools Log Files for Several Products
With Entire Operations Version 5.4.3, the Natural steplib table is completely replaced during startup of an Entire Operations session. With this correction, several user-defined steplibs from the user's steplib original steplib table are merged into the effective steplib table.
The following rules apply:
The effective steplib table may contain up to 2 user-defined steplibs only because 6 of the available 8 entries are used by Entire Operations itself. The original steplibs are taken over in the order they were previously defined.
Only original user-defined steplibs will be merged. The steplib setting is performed by the module NOPSLS-P.
It is recommended to invoke NOPSLS-P during the startup of the RPC server for OGC.
Example:
STACK=(LOGON SYSEOR;NOPSLS-P)
During the shutdown of an Entire System Server node on a mainframe, the Entire Operations and Entire Output Management monitors running as subtasks under this node will be notified to shutdown themselves first.
To allow enough time for an Entire Operations Monitor and its Monitor
tasks for termination, please set the Entire System Server parameter
SHUTDOWN-MAX-DELAY to at least twice the value of the
largest Entire Operations Monitor
task wait
time.
If the Entire Operations Monitor wait time is 30 seconds, and if there are no higher task wait times, please specify SHUTDOWN-MAX-DELAY=60 or more in the Entire System Server parameters.
The Software AG Editor is being used in the Entire Operations Monitor as well as in the Entire Operations online system. To avoid side effects from the online usage of Entire Operations, the Entire Operations Monitor should use an Editor Buffer Pool other than the online system of NOP.
On account of performance reasons, it is also recommended to define these buffer pools large enough that the editor does not need to swap to the EDTWORK dataset.
From Entire Operations Version 5.3.1 to Version 5.4.1, no migration of the System Automation Tools (SAT) log data is necessary. The format of the log file remains the same.
If you run several Entire Systems Management products in the same environment, you have the choice between
using a common System Automation Tools log file for all products
using separate System Automation Tools log files for each product.
In the SYSSATU/SPnnn member, there must be different assignments for the System Automation Tools log file for each product.
If you use a common Natural parameter module for the Entire Systems Management products, only one NTLFILE setting for the System Automation Tools log file can be defined there. Therefore it is recommended to use the Natural SYSPARM facility to create a separate profile for each Entire Systems Management product. These profiles must contain the setting of the LFILE 131 to the product-specific System Automation Tools log file.