This section covers the following topics:
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.2.
Notes:
Entire Output Management 2.2.2 requires
Adabas version 7.1.3 or above;
Natural Version 3.1.6 or above, including the Software AG Editor component;
Entire System Server Version 3.2.1 or above.
Entire System Server for Unix 2.1.1.10 and above (optional);
System Automation Tools Version 3.1.3 SP1 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).
You are strongly advised to migrate to the current version at your earliest convenience.
All solved problems of version 2.2.1 are included in this release:
| Problem | Short Description |
|---|---|
| 246164 | NOM and NPR3.2 with JES3 |
Additional Installation Steps for JES3 Environments accessed by NPR 3.2.1 and above.
These NPR32 zaps are prerequisites:
XC51021
XC51022
XC51023
XC51080
XC52003
There are the following restrictions:
Fields PAGEDEF and FORMDEF are not available. This means that NOM cannot automatically propagate these fields to printouts.
Field DESTINATION is not honored. This means that container files cannot be used for JES3 output and that report identification by Destination is not possible (this is compatible with NPR 2.2).
Some migration of NOM data is required. This applies to the NOM system files. The migration procedure is:
Shut down the NOM monitor.
Back up the NOM system file
Execute program NOMJ3DSK (in library SYSNOM) from a standard batch Natural job, with lfile 206 and lfile 91 (NOM Data) correctly set to point to the NOM system file to be converted. NOMJ3DSK requires two input NPR node numbers. The first must be an NPR 2.2 node and the second must be an NPR 3.2 node.
Example of CMSYNIN:
SYSNOM,userid,password NOMJ3DSK 62,112 FIN
where 62 is the NPR 2.2 node and 112 is the NPR 3.2 node.
Start the NOM monitor NPR node using NPR 3.2.
Ensure that the active reports with location S can still be browsed.
If for any reason you decide to revert to NPR 2.2, this can be done as follows:
Shut down the NOM monitor.
Back up the NOM system file.
Execute program NOMJ3BAK (in library SYSNOM) from a standard batch Natural job, with lfile 206 and lfile 91 (NOM Data) correctly set to point to the NOM system file to be converted. NOMJ3BAK requires two input NPR node numbers. The first must be an NPR 2.2 node and the second must be an NPR 3.2 node.
Example of CMSYNIN:
SYSNOM,userid,password NOMJ3BAK 62,112 FIN
where 62 is the NPR 2.2 node and 112 is the NPR 3.2 node.
Start the NOM monitor NPR node using NPR 2.2.
Ensure that the active reports with location S can still be browsed.
If you subsequently migrate to NPR 3.2 again, the migration procedure (NOMJ3DSK) must be repeated.
This release contains several problem solutions. There are no new features implemented and no changes of the user interface compared to NOM 2.2.1.
NOM GUI Client allows you to access NOM functions on a 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.
This NOM release is intended to run together with NGC 1.1.1.2 and above and with SAT 3.1.3 SP1.
