Entire Output Management Version 3.5.1 Release Notes

#### Search Results

Search

# Entire Output Management Version 3.5.1 Release Notes

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

- Prerequisites for Mainframes (NOM)

- Prerequisites for UNIX (NOM)

- Prerequisites for Output Management GUI Client (NGC)

- NGC Versions Supported by NOM

- Migrating from Previous Versions

- Solved Problems

- Enhancements and New Features

- Deprecated Features

Unless otherwise indicated, the information in these Release Notes applies to Version 3.5.1:

- for both Entire Output Management (NOM) and the Output Management GUI Client (NGC),

- on all supported platforms.

## Prerequisites for Mainframes (NOM)

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 8.2 or above; the Natural installation must include the Software AG Editor component;

- Entire System Server Version 3.6.3 or above;

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

- System Automation Tools Version 3.5.1 or above;

- Natural Security (optional; required for UTM users under BS2000);

- EntireX Version 10.3 for z/OS, Version 10.3 for BS2000, Version 9.6 for z/VSE, or above (optional, for multi-node support and Open Print Option);

- Entire Network (optional, for multi-node support);

## Prerequisites for UNIX (NOM)

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.6 for UNIX, or above;

- Natural Version 9.1 for UNIX, or above;

- Entire System Server Version 2.1.12 for UNIX, or above;

- System Automation Tools Version 3.5.1, or above;

- EntireX Version 10.3, or above (optional, for multi-node support, cross-platform access, and Open Print Option) (*).

(*) Fix 5 has to be installed using the Software AG Update Manager. The libraries are delivered as a separate component under Infrastructure > Libraries > EntireX Libraries in the Software AG Installer (see the webMethods documentation, Installing webMethods and Intelligent Business Operations Products).

## Prerequisites for Output Management GUI Client (NGC)

Output Management GUI Client Version 3.5.1. requires the following products:

- Natural for Windows, Version 9.1 or above; Development version or Runtime version;

- EntireX Version 10.3 or above; Development version or Runtime version (*);

- Entire Output Management Version 3.5.1 (or above) for Mainframes/UNIX.

(*) Fix 5 has to be installed using the Software AG Update Manager. The libraries are delivered as a separate component under Infrastructure > Libraries > EntireX Libraries in the Software AG Installer (see the webMethods documentation, Installing webMethods and Intelligent Business Operations Products).

## NGC Versions Supported by NOM

Entire Output Management Version 3.5.1 does not support any Output Management GUI Client version below 3.5.1.

## Migrating from Previous Versions

A migration of Entire Output Management to Version 3.5.1 is possible from Version 3.4.3, but not from earlier versions. Output Management GUI Client does not require any migration.

## Solved Problems

All solved problems of the previous version are included in this version.

## Enhancements and New Features

- Code Page Support

- Mainframe Nodes

- Email Messages

- System Defaults (NGC only)

- Reports - Identification Attributes

- Reports - Separator Pages

- Reports - Editing of Separator Pages and Separation Routines (NGC only)

- Active Reports - Dialog Layout (NGC only)

- Active Reports and Active Bundles - Printing (NGC only)

- Monitor Tasks (NGC only)

- Monitor Defaults - Jobcard NOSTATISTICS Obsolete

- Transferring Objects - Mainframe Nodes

### Code Page Support

With the new system administration function Default Code Pages you can specify the code pages which are to be available in Entire Output Management. The defined code pages can be used in report and node definitions for mainframes.

### Mainframe Nodes

The system administration function Node Definitions has been revised and enhanced. In addition to UNIX and Windows nodes, you can now also define mainframe nodes.

### Email Messages

With the new system administration function Email Message Definitions, you can define certain error situations which will trigger the sending of emails to specified email addresses. You identify an error situation by its Natural or Entire Output Management message number. You can specify which email text is to be sent and to whom. In this way, you can inform the appropriate persons whenever a certain error situation occurs.

In addition, Entire Output provides a set of standard emergency emails, which are sent automatically in the case of certain severe error situations.

See Email Message Definitions for details.

### System Defaults (NGC only)

A new system default option Perform search in advance when opening the search dialog is available: It applies to the search for active reports in a folder and may be used to prevent time-outs caused by searches in environments with a large number of active reports. Depending on this option, when you open the Search dialog, the result list may initally be either empty or already filled with the search results based on the current search criteria. .

### Reports - Identification Attributes

The source of a report is now selected on the Report Definition > General Attributes screen (fields Node name and Ident. source). With PF7, you can specify the identification values for the selected type. See Attributes of a Report

The new option Source contains ASA control characters in the UNIX/Windows Indentification Attributes can be used if a report is to be created as a text file and the print data from the data source already contain ASA control characters.

### Reports - Separator Pages

With previous versions, the separator pages specified in the Printing Attributes of a report were printed on all printers assigned to the report. Now you can specify for each assigned printer in the Printing Attributes whether or not the separator pages are to be printed on it.

### Reports - Editing of Separator Pages and Separation Routines (NGC only)

With previous versions, it was necessary to invoke the Natural editor in a separate Natural session in order to edit a separator page (text member) or user separation routine (subprogram). Now Edit buttons are provided next to the separator pages and user routine specified in the report's Printing Attributes and Separation Attributes respectively. They can be used to invoke the editor directly, allowing you to edit the separator page or separation routine in question.

With the new option Allow to edit separator pages and separation routines in the Access Rights section of user definitions, the system administrator can allow/disallow the use of these editing functions for individual users.

### Active Reports - Dialog Layout (NGC only)

The dialog layout for the attributes of active reports has been improved to be more user friendly.

### Active Reports and Active Bundles - Printing (NGC only)

The functions to print active reports and active bundles have been enhanced. With previous versions, it was only possible to select a single active report or active bundle for printing. Now you can select multiple active reports or active bundles simultaneously for printing. In addition, you have the option to either print them all on the same printer or print them on different printers. See Printing an Active Report and Printing an Active Bundle.

### Monitor Tasks (NGC only)

The function to list the monitor subtasks has been enhanced to be more user friendly.

### Monitor Defaults - Jobcard NOSTATISTICS Obsolete

In the Monitor Defaults, the specification of the jobcard entry `NOSTATISTICS` (deactivation of statistics-data writing) can be omitted, as it applies by default now.

If statistics data are to be written for Optimize for Infrastructure (O4I), the jobcard entry `STATISTICS=ON` has to be specified explicitly.

### Transferring Objects - Mainframe Nodes

The functions for Transferring Objects from one environment to another have been enhanced: Now you can also export/import mainframe nodes.

For the importing of objects, the fifth `RMIMPORT` parameter (node number) is now obsolete.

## Deprecated Features

- SAP Spool Reports

- Con-nect Interface

- Obsolete Printer Types

- Report Identification Attributes

- Linking Folders

- Style Attribute of Reports

- Automatic User Definition

- User Exit NOMEX008

### SAP Spool Reports

As of this release, reports from SAP Spool are no longer supported.

Existing data referring to SAP Spool reports which were created with previous versions of Entire Output Management are still available for retrieval. They will be removed with the next release.

Before you install Version 3.5.1, you should run the program `CHCKOLD` provided in the library `SYSNOM` in your old Version 3.4.3 environment to find out if you still have SAP Spool reports.

### Con-nect Interface

As of this release, the Entire Output Management interface to Con-nect is no longer supported.

Existing data referring to the Con-nect interface which were created with previous versions of Entire Output Management are still available for retrieval. They will be removed with the next release.

Before you install Version 3.5.1, you should run the program `CHCKOLD` provided in the library `SYSNOM` in your old Version 3.4.3 environment to find out if you still have Con-nect interface-related objects.

### Obsolete Printer Types

As of this release, the following printer types are no longer supported:

- CON-NECT

- ECL 2.1.1

- XML

Before you install Version 3.5.1, you should run the program `CHCKOLD` provided in the library `SYSNOM` in your old Version 3.4.3 environment to find out if you still have definitions for these printer types.

### Report Identification Attributes

In previous versions, it was possible to define report attributes for more than one identification source, which could lead to inconsistencies. As already communicated in the Version 3.4.1 Release Notes, this was rectified and you can now only define reports with identification attributes for one identification source.

Old report definitions, however, may still contain attributes for more than one identification source. When you open such a report definition, you will be prompted to choose which identification attributes are to be kept.

To find out if you still have report definitions with multiple identification attributes, you can run the program `CHCKIDNT` provided in the library `SYSNOM`.

### Linking Folders

As of this release, the line command LF (Link folder) is no longer available, because its functionality was redundant. The same applies to the corresponding NGC command Link on the context menu for folders.

As before, the linking of a folder to another user's folder is done via the Linked Folder fields, as described under Attributes of a Folder.

### Style Attribute of Reports

The printing attribute Style of reports will be removed with one of the next releases.

### Automatic User Definition

The System Defaults field Automatic user definition - and the functionality attached to it - will be removed with one of the next releases.

### User Exit NOMEX008

The user exit NOMEX008 will be removed with one of the next releases.

### On this page

- Prerequisites for Mainframes (NOM)
- Prerequisites for UNIX (NOM)
- Prerequisites for Output Management GUI Client (NGC)
- NGC Versions Supported by NOM
- Migrating from Previous Versions
- Solved Problems
- Enhancements and New Features
- Deprecated Features