Entire Output Management Version 3.3.1 Release Notes

These Release Notes inform you of the enhancements and new features provided with Version 3.3.1 of Entire Output Management; they cover the following topics:

Unless otherwise indicated, the information in these Release Notes applies to Version 3.3.1 on both mainframe and UNIX platforms.

Update information:

The following section has been added for Open Print Option (OPO) Version 3.3.2 in November 2012: OPO Silent Installation and Uninstallation.


Prerequisites for Mainframes

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.5 or above;

  • Entire System Server Version 2.1.4.6 for UNIX/Windows, or above (optional; for UNIX/Windows access);

  • System Automation Tools Version 3.3.1.4 or above;

  • Natural Security (optional; required for UTM users under BS2000/OSD);

  • EntireX (optional, for multi-CPU support) Version 8.1.1 or above for z/OS, Version 7.2.3 or above for z/VSE, Version 7.1.4 or above for BS2000/OSD;

  • Entire Network (optional, for multi-CPU support);

  • Con-nect (optional).

Prerequisites for UNIX

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.8 for UNIX, or above; the Natural installation must include the Natural Web Interface package and the Software AG Editor component;

  • Entire System Server Version 2.1.4.6 for UNIX, or above;

  • System Automation Tools Version 3.3.1, or above;

  • EntireX Version 8.2, or above (optional, for multi-CPU support).

Migrating from Previous Versions

Migration to Version 3.3.1 is possible from Version 3.2.1 or 3.2.2, but not from earlier versions.

In addition to performing the migration procedure, you have to perform the following:

  • Change to (A250) the format/length of the error text fields NOMEXnnn-ERROR-TEXT related to the user exits NOMEX* in SYSNOMS.

  • Change to (A/120) DYNAMIC the format/length of the application-independent variable +P-SPOOL-ATTRIBUTES-EXTENDED in the user separation routines in which it is used.

  • Recatalog with the new version all your user exits and programs which use Entire Output Management application programming interfaces.

  • Under UNIX, replace the scripts used for customization (see Customization in the Installing and Setting Up Entire Output Management on UNIX Platforms documentation) with those of the current Entire Output Management version from the INSTALL directory.

Solved Problems

All solved problems of Version 3.2 and its service packs are included in this version.

Enhancements and New Features

The following enhancements and new features are available with this version:

Multitasking Monitor under UNIX and Printer Tasks

As of this version, you can run the Entire Output Management Monitor under UNIX as a multitasking system with up to five tasks in the same way as in mainframe environments. The subtasks can be customized with the same functions as on mainframes; see Subtask Processing in the section Monitor Defaults of the System Administration documentation.

In addition, printer tasks will no longer end after a printout. Instead, they will be "idle" and wait for further incoming printout requests. If a printer task is idle for more than 30 minutes, it will terminate with error message 1566: “Printer task terminates (long idle time).” This new behavior contributes to improving performance.

New Printer Type WRTSPOOL

The new printer type WRTSPOOL is available under z/OS and z/VSE to write output directly to the spool.

Attribute Symbols

In the special attributes of the printer types EMAIL, UNIXLP, NATUNIX and DISKUNIX, you can specify attribute symbols. At the time of printing, these symbols will then be replaced by the corresponding attribute values.

Enhanced Transfer Utility

The Transfer Object utility has been enhanced. It now allows you to:

  • transfer folders from one environment to another;

  • transfer objects together with their authorization lists; this applies to bundles, distribution lists, logical printers, reports, and folders (as described in the corresponding sections of Transferring Objects in the System Administration documentation).

Enhanced Monitor Log

The print facility of the monitor log has been enhanced. Now it is possible to enter a search string for full text search: Only the log entries containing this string are printed.

In addition, the monitor log now uses a formatted page.

Enhanced Logging

The Entire Output Management log now contains all messages, including trace messages. This means that the output is written to the System Automation Tools log file, which may increase significantly if tracing is switched on. Thus you can obtain a complete log even in server environments which do not allow I/Os.

One Entire Output Management log message can now contain up to 250 characters per program level; previously the limit was 70 characters altogether.

The first line of the log message is displayed in the log display (see Displaying the Monitor Log in the System Administration documentation) as before. However, the line command IN (info) now displays the whole message with all lines, and you can scroll within the display.

Enhanced Tracing

With the TRACE jobcards in the monitor defaults (menu 8.1, item 2), you can now restrict the trace function to certain program levels (Natural system variable *LEVEL) and components. For details, see the trace information under "Jobcards" in the section Monitor Defaults of the System Administration documentation

The specified trace level also applies if tracing is activated with the direct command T+ in menu 8.6. If no trace level is specified, T+ will cause all levels to be traced.

If modules for UNIX access are called with tracing, the trace facility of Entire System Server on UNIX will be switched on automatically, too. This will create a selective trace even in Entire System Server in case of problems with UNIX or Windows nodes.

You should only activate tracing when Software AG Support personnel requests you to do so.

VTAM Print Requests

As of this version, it is possible to re-route VTAM print requests to Entire Output Management. See Re-Routing VTAM Output to Entire Output Management in the Installation and Customization documentation for details.

Parameter SATVERS in Server Definition

The parameter SATVERS in the parameter block SATSTART of the server environment definition (see Define Environment for Entire Output Management Server in the Installation and Customization documentation) is now obsolete.

OPO Silent Installation and Uninstallation

The Open Print Option (Version 3.3.2) can be installed and uninstalled in silent mode, that is, without requiring user interaction. See Silent Installation and Uninstallation in the Installation and Customization documentation for details.

Discontinued Features

Long Records

As of this version, the processing of so-called long records (records with more than 250 characters per line) is no longer 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.

Batch Monitors

Previously, System Automation Tools could start the runtime environment for the Entire Output Management monitor in either batch mode or subtask mode. As of this version, batch mode is no longer supported. Subtask mode has proven to be a stable and convenient method to have the batch tasks controlled by Entire System Server, and it is available for all mainframe platforms.