These Release Notes inform you of the enhancements and new features provided with Version 3.2.2 of Entire Output Management; they cover the following topics:
Unless otherwise indicated, the information in these Release Notes applies to Version 3.2.2 on both mainframe and UNIX platforms.
Before you can install Entire Output Management on a mainframe computer, the following Software AG products must have been installed at your site:
Adabas Version 8 or above;
Natural Version 4.2 or above; the Natural installation must include the Software AG Editor component;
Entire System Server Version 3.3 or above; the use of the operator command STATUS NOM requires Version 3.4.1 or above, as well as zap XC71022 for z/OS or the corresponding zap for z/VSE or BS2000/OSD;
System Automation Tools Version 3.2, with service pack 2, or above;
Natural Security (optional; required for UTM users under BS2000/OSD);
Entire Network (optional, for multi-CPU support);
Con-nect Version 3.1 or above (optional).
Before you can install Entire Output Management on a UNIX system, the following Software AG products must have been installed at your site:
Adabas Version 6.1 for UNIX or above;
Natural Version 6.3.4 for UNIX or above; the Natural installation must include the Software AG Editor component;
Entire System Server 2.1.3 for UNIX, patch level 2, or above;
EntireX Version 7.3.4 (optional, for multi-CPU support).
Migration to Version 3.2.2 is possible from Version 3.1.1, but not from earlier versions. No migration is required from Version 3.2.1.
Before attempting to migrate, you have to restart the Entire System Server node and ensure that the Entire Output Management Monitor is inactive. Use the job examples in your job library file as templates.
For a detailed migration description, see the section Migrating from Previous Versions in the Installation documentation.
All solved problems of Version 3.2.1 and its patch levels are included in this release.
The following enhancements and new features are available with this version:
A printer of type DISKUNIX can be used to write the document on any file system of a UNIX or Windows machine where an Entire System Server UNIX node is active. A command or a script can be executed which will continue the processing of the document on the target system. See Defining Physical Printers in the System Administration documentation.
On UNIX or Windows nodes where Entire System Server for UNIX is active, Entire Output Management can load documents that were saved to the file system. These documents can also be read in binary format. If the corresponding report definition contains an input command, this will be executed on the source system to process the contents of the document. This feature can be used, for example, to convert the format of the data in the document. After the input command has been executed, no further report processing will be performed. To further process the document, another report definition has to be applied to the document.
By default, the active record in #Inbasket are sorted by date. A new option in the user profile definition (see Adding a User Profile in the System Administration documentation) allows you to decide whether you want them to be sorted by name or by date. Normally, selecting a report name would cause the reports to be sorted by name. If the option is set, the date order will be kept even if report names are selected.
Printouts of a certain status can be selected by entering the desired status code in the Status column of the printout list. Now all unsuccessfully printed documents (status E, F, T, O or S) can be selected by entering "U" in the Status field. See Listing Printouts in the User's Guide.
As of the next version - that is, the version after Version 3.2.2 - the processing of so-called long records (records with more than 250 characters per line) will no longer be supported. The intention of long records was to process binary data as a stream, not limited by physical lines. Entire Output Management now supports the processing of native binary data, as described under Processing of Binary Data in the Concepts and Facilities documentation. Therefore the long records feature will cease to be available.
