This document covers the following topics:
These Release Notes inform you of the enhancements and new features that are provided with Entire Output Management Version 2.2.1.
Note:
Migrations from versions earlier than 1.4.1 are not
supported.
Entire Output Management 2.2.1 requires
Adabas version 7.1.2 or above;
Natural Version 3.1.6 or above, including the Software AG Editor component;
Entire System Server Version 3.1.1 or above; if Entire System Server 3.2.1 is installed, it enables the new long record and e-mail integration functions, but only node numbers below 255 can be used.
Entire System Server for Unix 2.1.1.05 and above (optional);
System Automation Tools Version 3.1.3 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).
With the release of Entire Output Management 2.2.1, versions below 2.1.1 can no longer be supported. You are, therefore, strongly advised to migrate to the current version at your earliest convenience.
 |
Warning: The order of the STEPLIBs has changed. SYSSAT must precede SYSEXT. If this is not the case, the program menu will not be found. |
All solved problems of version 2.1.1 are included in this release.
NOM can hold 126 lines of output during a separation operation. This improves performance significantly, if a user separation exit repositions in large files. In NOM 2.2.1 the default has been changed from 'CHACHEOFF' to 'CACHEON', because we do not expect disadvantages from caching, even if no repositioning takes place. In some cases, active caching has resulted in execution time savings of more than 95%.
Sometimes errors require user intervention. The monitor will try to re-execute its tasks each monitor cycle. To reduce logging during such transient error situations, repeated identical log messages will be automatically suppressed as follows:
Identical messages 1 to 9 are written to monitor log as usual;
Message 10 is preceded by a warning, that further identical messages will be suppressed;
Next identical messages that are written to log (reminders) are 20, 30, 40, … 100, 200, 300, … 1000, 2000, 3000, …;
Suppression of duplicates is reset whenever the monitor task is restarted. Additionally, duplicates are not suppressed if there is a delay of 23 hours (or more) between occurrences;
No parameter settings are necessary to influence suppression.
Following enhancements have been implemented in NOM 2.2.1:
| Number | Description |
|---|---|
| 2774 | User-exit for EXPORT to PC, NOMEX011 in library SYSNOMS. |
| 5593 | Automate batch functions. See the field "Delete empty" in the section Defining Default Parameters for Archiving in the System Programmer's Guide. |
| 5903 | BOT does not work in several listings. |
| 7165 | Improve error messages NOM / Online / Manual / SAT. |
| 7187 | Automatic restart after DB shut. If an error 3148 occurs, react like NOP. |
| 7196 | Improve performance of display printout queue. |
| 7553 | Default profile for non-defined users. |
| 9413 | Print bundle table of contents more than one time – example print exit PRBUVTOC in the SYSNOMS library. |
Redesign System Structure
You may optionally split your NOM System File 1 into two system
files. One contains static data such as definitions; the other contains
volatile data such as active reports, active bundles and printouts. This allows
more flexible database administration.
XML Support
NOM can supply
style sheets for XML
documents at print time. A style sheet can be associated with a
report created from an XML document. Additionally, style sheets can be stored
in NOM.
Flexible Archiving
As well as the standard archive datasets, you can now
define up to 9
additional archive dataset types, this allows:
multiple hierarchies of archived reports. For example, reports which need to be revived quickly can be archived to disk, with all other reports being archived to tape;
archiving to non-standard datasets (that is, datasets which cannot be accessed as a Natural work file) such as optical disks.
Process Long Records
It is now possible to archive and print
reports with more than 251
characters per line (for example AFP data). These reports are copied
to a container file, their records are segmented and then reassembled at print
time. This feature is only available for the z/OS JES2 spool system and
requires Entire System Server version 3.2.1 or above.
Monitor Error Recovery
If a monitor function fails, an error message is generated and the
corresponding object is set to error status. However, there are a number of
errors which are not caused by malfunctions of the product, but by error
situations of the environment, and these can be solved by operator
intervention. Now you can enter a maximum number of retries and an interval in
seconds to repeat failed monitor operations. You can enter the values from the
Monitor Defaults
Screen.
E-mail Integration
Any report can now be sent as e-mail. Physical and logical printers
of the type
'e-mail' can be defined to send the output to an e-mail recipient.
These virtual printers are treated as real printers: a printer task is started,
which will send the report using Entire System Server's 'SEND-EMAIL' view
(Entire System Server version 3.2.1 and above). No size limits are implemented.
The report size is limited to the e-mail system definition.
NOM GUI Client
NOM GUI Client allows you to access NOM functions on mainframe from
a native PC application. The calls are passed to NOM mainframe via RPC and
return the desired information, also enabling you to browse output, edit
definitions and view log information. Intelligent traffic management allows you
to look into millions of output lines without passing everything across the
network. Together with Software AG's Mainframe Navigator as a part of Natural
for Windows, you can create NOM reports without using a mainframe emulation,
simply by editing and submitting mainframe jobs on the PC. In future the NOM
GUI Client will also be able to start and stop the NOM monitor and edit its
defaults.
