Entire Event Management 2.1.2 Release Notes

This document provides a brief overview of how the current version of Entire Event Management differs from the previous version. If not stated otherwise, the items are valid for all supported operating systems: z/OS, BS2000/OSD and VSE/ESA.

If this is your first version of Entire Event Management or if you are migrating from an earlier version than 2.1.1 of Entire Event Management, you should also read the Release Notes and Reference Documentation for Version 2.1.1.

This section covers the following topics:

Change Summary

Year 2000 Compliance

All date processing is now based on four-digit years and, wherever possible, dates are displayed with a century. To achieve this, change your session profile using the SET command.

Enter "Y" in the field Date Format to display all system dates in four-digit format: YYYYMMDD.

For a description of the set session parameters, see the section Using Entire Event Management, subsection How to Set up a User-specific Session Profile in the Entire Event Management User's Guide.

Natural Version 2.3 Compatibility

Entire Event Management 2.1.2 can run under Natural 2.2.8 or 2.3.1 and above. Please see the subsection Prerequisites.

If you are using System Automation Tools 3.1.1 (SAT), please see also Installation on Mainframe Platforms in the System Automation Tools documentation.

Support for 5-digit Database ID & File Number

Entire Event Management 2.1.2 fully supports database IDs and file numbers greater than 255, both for Natural system files and its own system files. Please see the subsections Prerequisites and Compatibility and Migration.

Enhanced Support for Time Changes

To improve support for multiple time zones and clock changes in a single time zone, Entire Event Management uses a new user exit, YGETGMTN (see the example in the library SYSNCLCO). This user exit allows the monitor to normalize message times to Greenwich Mean Time, thus ensuring that messages are processed in the correct chronological order. The online system also uses YGETGMTN to display messages with the appropriate local time.

Corrections / Solved SAGSIS Problems

A list of solved SAGSIS requests and problems is provided on request by Software AG Customer Support.



Before you can install Entire Event Management, the following Software AG products must already be installed at your site:

  • Adabas Version 5.3 or higher. It is recommended to install Adabas Version 6.2.

  • Natural Version 2.2.8 or higher

    The following zaps must be applied to Natural Version 2.3.1 and Natural Version 2.3.2:

    NA32186, NA32164, NA32160, NA32159.

  • Entire System Server Version 2.1.4 or higher (for BS2000/OSD, z/OS and VSE/ESA)

  • System Automation Tools sub-component SAT Version 2.3.1 (or higher).

  • Natural Security (optional)

  • Entire Net-Work (optional, for multi-CPU support)

  • Entire Broker Version 1.1.1 or higher (optional when using the API)

  • Update tape CL1201 must be installed


  1. BS2000/OSD: When the Entire Event Management Server is running on BS2000/OSD, XS capability is required.
  2. OS/390: Entire Event Management must run on OS/390 Version 5.1 or higher and use JES2 Version 5.2 or higher.
  3. VSE/ESA: Entire Event Management must run on VSE/ESA Version 2.1 or higher.

Compatibility and Migration

With the release of Entire Event Management 2.1.2, Version 1.3.2 and earlier versions will no longer be supported. You are therefore urged to migrate to the current version as soon as possible.

For a detailed description of the installation, see the Installation and Customization on Mainframes documentation.

Migration from Version 2.1.1 to Version 2.1.2 - Job I051, Step 3150

To migrate from Version 2.1.1, you must:

  1. load the new System File 1 provided with Version 2.1.2

  2. use the ADABAS utility (or ADADBS On-line Services) to modify the FDT of System File 2 to change the lengths of fields Q6, Q7, Q9 and QA from 3 to 5, for example:


    Alternatively, you can load the new System File 2 supplied with Version 2.1.2 and use the import/export utility to migrate your existing definitions.

    Because of the change in message logging, to normalize the message time to Greenwich Mean Time (GMT), thus avoiding problems when the clock changes, it may be necessary to modify existing logged messages.

    For example, when local time is two hours ahead of GMT, if the Entire Event Management 2.1.2 server is started less than two hours after the Entire Event Management 2.1.1 server ended, it can lead to messages being logged with a duplicate time, causing the monitor to fail with Adabas Response Code 198 (duplicate value for unique descriptor).

    To prevent this, a routine, MLOGMIGR, is provided in library SYSNCL. You should execute this routine prior to starting the Entire Event Management monitor for the first time. The routine has one optional parameter of format N5 which specifies the number of records to be updated between ETs. The default is 10 and we recommend a small number to avoid Adabas Response Code 197 (unique descriptor pool full). MLOGMIGR (Job I500, Step 3100) then calls the new GMT exit YGETGMTN to obtain the difference between local time and GMT and updates all logged messages appropriately so that:

    1. there will be no duplicates when Entire Event Management monitor 2.1.2 starts, and

    2. messages logged under Entire Event Management 2.1.1 still display the correct time after migration to Version 2.1.2.

In summary:

  • take a backup of your Entire Event Management Log File 3 (via ADAULD or ADASAV, Job I500, Step 3100),

  • start NATURAL, ensuring that LFILE 203 is correctly set to point to the Entire Event Management system file 3 containing the messages to be adjusted (Job I500, Step 3102),

  • logon to SYSNCL,

  • execute MLOGMIGR (in batch or online),

    Execute MLOGMIGR only once.

  • in the event of any failure during migration, restore your log file and contact Software AG Support with details of the error.

Migration from Earlier Versions than 2.1.1 to Version 2.1.2

To migrate from an earlier version than 2.1.1, you must load the new System File 1 and also migrate your definitions in System File 2 and your messages in System File 3, as follows:

  1. use the Export Utility in the old version in your existing environment (Job I050, Step 3104/Step 3107),

  2. reload System Files 2 and 3 using the supplied installation files (Job I050, Step 3106/Step 3109),

  3. before importing the data, define a user ID. See the Installation and Customization on Mainframes documentation, section Logging on to Entire Event Management for the First Time.

  4. use the Import Utility in the new version to import your previously exported data (Job I200, Step 3102/Step 3103),

  5. migrate the logged message timestamps with routine MLOGMIGR, as described above (Job I500, Step 3100).

Updating SYSSATU

For Entire Event Management, set SATVERS to 23 in the member SYSSATU.