These Release Notes inform you of the enhancements and new features that are provided with Entire Output Management Version 3.1.1 and covers the following topics:
This document covers the following topics:
Before you can install Entire Output Management, the following Software AG products must already be installed at your site:
Adabas version 7.1.3 or above;
Natural version 4.1.3 or above, including the Software AG Editor component;. If you are using Natural 4.1.3 please apply Natural source change NA41306 and zap NA63110 to enable the AM=NOM parameter. Natural 4.1.4 already contains these changes.
Entire System Server Version 3.2.2 or above; only node numbers below 255 can be used.
Entire System Server for Unix 2.1. and above (optional);
System Automation Tools Version 3.1.4 or above;
Natural Security (optional); for openUTM users under BS2000/OSD Natural Security is required;
Entire Network (optional, for multi-CPU support), and
Con-nect Version 3.1 or above (optional).
The installation procedure for Entire System Server is described in the Entire System Server Installation Documentation.
The installation procedure for System Automation Tools is described in the separate SAT Installation and Customization Documentation .
Migrations from versions earlier than 1.4.1 are not supported.
Important:
Before attempting to migrate, 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 Migrating from Previous Versions in the Installation Documentation.
All solved problems of version 2.2.2 and its patch levels are included in this release.
NOM provides methods for accessing printers: It is able to directly print to TCP/IP printers. This print method is intended to access printers that have either got a dedicated IP address or can be reached using printer queue names of printer servers.
This print method has been designed for direct printing of shorter documents directly from online applications. However, it is executed in a Natural subtask and no online space, such like CICS memory, is affected. No spooling system is required, and no extra address space will be used, even no ESY server. This makes this print method independent from batch jobs, Broker, CA-SPOOL, ESY, JES, and NAF (in alphabetical order).
Performance enhancements are achieved and 4 MB of space in a NOM printer subtask per 1000 pages of text output are needed as soon as the printer (server) acknowledges the reception of the printout.
TCP/IP direct printing relieves the former printer type 'UNIXLP' which worked with servers across broker communication.
At print time, the printout will be initiated online or by the monitor and executed in one of the defined print tasks of NOM. At execution time, the printout will be kept in virtual memory and then sent to TCP/IP directly (via socket programming) using the LPR/LPD protocol (RFC1179).
The monitor trace output has been improved. Now an extended format, including time stamps, is used. The new direct command TRACE ON has been created: TRACE ON in the monitor maintenance screen (“8.6”) will switch tracing on dynamically, TRACE OFF will reset tracing.
Until version 2.2 of NOM, long records could only be used for JES2 sources. Now additional source types can contain record lengths greater 251:
JES3
Sequential files
It is now possible to read the whole JES output of a job into one report. The different record lengths and carriage control characters are regarded.
NOM 3.1.1 now can execute under Unix. It has got nearly the same character interface. However, it is recommended to use NOM 3.1.1 Unix as a server only and access all functions with NOM GUI Client. For details see NOM Unix documentation.
NOM’s GUI interface for Windows® has been extended to cover allmost all functions of NOM. Not only end user functions but also the administrative functions have been implemented and can be used to control NOM/Mainframe or NOM/Unix nearly without using the character interface.
The following restrictions have to be considered while working with NOM:
Incompatibility of User Exits: The data areas of the separation and printer exits have changed. Please recatalog your exits to run properly under Natural 4 (and above).
Incompatibility of special printer attributes: Due to enhancements in the special printer attributes of printer type ‘EMAIL’ and the reusage of printer type ‘UNIXLP’ for TCP direct printing, it may be necessary to delete and recreate the NOM printers of these types.
