Entire Operations Version 5.5.3 Release Notes

#### Search Results

Search

# Entire Operations Version 5.5.3 Release Notes

These release notes inform you of the enhancements and new features provided with Version 5.5.3 of Entire Operations.

Unless otherwise indicated, the information in these release notes applies to Version 5.5.3:

- for both Entire Operations (NOP) and Entire Operations GUI Client (OGC),

- on all supported platforms.

This document supersedes and replaces the release notes for Entire Operations from Version 5.5.1 to Version 5.5.2.

#### Legacy Platforms z/VSE and BS2000

Natural add-on products are no longer delivered for the z/VSE and BS2000 operating systems.

Contact your local representative for assistance in planning and executing your rehosting from z/VSE or BS2000 to an alternative operating system.

Notes:

1. Starting with Natural for Linux and Cloud version 9.2, UNIX platforms are no longer supported. Instead, Software AG promotes applications for Linux and Cloud. However, some Add-On products still run with older versions of Natural and therefore will still be able to support UNIX platforms.
2. Starting with Natural for Mainframe version 9.2, BS2000 and VSE platforms are no longer supported. Instead, Software AG promotes applications for z/OS or re-hosting to Linux and Cloud. However, some Add-On products still run with older versions of Natural and therefore will still be able to support BS2000 or VSE platforms.
3. BS2000 platforms are only supported on ESA nodes.

This document covers the following topics:

- General System Updates

- Entire Operations Documentation Updates

- Supported Operating Systems

- Supported Browsers

- Prerequisites for the Mainframe

- Prerequisites for UNIX/Linux

- Prerequisites for Windows GUI Client

- Special Considerations

- Platforms and Required Middleware

- Compatibility and Migration

- Code Page Setting

- Solved Issues

- Previous Release Notes

## General System Updates

In addition to new or changed functions, each release of Entire Operations is associated with maintenance corrections and enhancements of internal functions and text fields on screens or windows of the CUI or GUI interface.

## Entire Operations Documentation Updates

Entire Operations documentation in HTML and PDF format is provided in the Documentation section of Software GmbH's Empower web site at http://empower.softwareag.com/ (Empower login required). The documentation is usually updated whenever a new Entire Operations version or cumulative fix (CF) is released.

Note
Due to last-minute documentation updates, it may be possible that the online help that you can invoke directly from the product does not yet contain the latest information. The most up-to-date Entire Operations documentation can always be found in the Documentation section of Software GmbH's Empower web site.

## Supported Operating Systems

Entire Operations Version 5.5.3 supports the following operating systems:

- z/OS,

- BS2000 (via ESA only),

- UNIX/Linux and

- Windows (Intel) (managed nodes only).

For detailed information on the supported operating system versions, see the current Natural Release Notes for mainframes, Linux or Windows.

## Supported Browsers

As of Version 5.5.3, Entire Operations GUI Client supports the following browsers:

- Mozilla Firefox Version 60.4.0esr (64-bit) or above

  Only the Extended Support Releases (ESR) of Mozilla Firefox are explicitly supported.

- Microsoft Internet Explorer Version 11 or above.

## Prerequisites for the Mainframe

Before you can install Entire Operations on a mainframe system, the following Software GmbH products must already be installed at your site:

- Adabas Version 8.5.4 or above;

- Natural Version 9.2.2 or above; the Natural installation must include the Software AG Editor component. We recommend to apply the current zaps. For further information, please refer to the Natural documentation.

- Entire System Server Version 3.7.2 or above;

- Entire System Server Version 2.1.16 (UNIX/Linux and Windows) or above.

- System Automation Tools Version 3.5.3 or above;

- Natural Security (optional);

- Entire Net-Work (optional); this product is required for any kind of multi-CPU constellation where mainframe and/or UNIX/Linux and/or Windows partners are involved (non-local);

- EntireX Broker Version 10.9 for z/OS (optional);

- EntireX Broker is required for any kind of multi-machine constellation if one partner is a UNIX/Linux system or Windows or different UNIX/Linux systems are involved. EntireX Broker is not required if you are running Entire Operations on a UNIX/Linux or Windows platform and controlling the job networks on a mainframe system.

- Entire Connection (optional)

  This product is required for importing or exporting data from or to a PC file or a Natural work file on a PC.

The installation procedure for Entire System Server is described in the Entire System Server documentation.

The installation procedure for System Automation Tools is described in the System Automation Tools documentation.

## Prerequisites for UNIX/Linux

Before you can install Entire Operations on a UNIX/Linux system, the following Software GmbH products must have been installed at your site:

- Natural Version 9.2 (or above) for UNIX/Linux;

- Adabas Version 7.1 (or above) for UNIX/Linux.

With Entire Operations Version 5.5.3, the following products will be installed automatically:

- Entire System Server Version 2.1.16 (or above) for UNIX/Linux;

- System Automation Tools Version 3.5.3 or above;

- EntireX Libraries 10.9 (or above). 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).

- Entire Systems Management Adapter (ESA) Version 4.1.1, or above (optional, to access nodes on BS2000 Systems).

## Prerequisites for Windows GUI Client

Entire Operations GUI Client will run on any Windows platform on which Natural Version 9.2 (or above) for Windows runs.

Note
Make sure the machine on which you are going to run the Software AG Installer contains the latest Windows updates.

Entire Operations GUI Client Version 5.5.3 requires the following products:

- Natural Version 9.2 (or above) for Windows. You can use either Natural Development version or Natural Runtime.

  Entire Operations GUI Client runs on any Windows platform on which Natural Version 9.2.1 (or above) for Windows runs.

- Entire Operations Server Version 5.5.3;

- EntireX Libraries 10.9 or above (optional). 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).

## Special Considerations

Database ID (DBID) 148 is reserved for Entire System Server and must not be used for any database.

## Platforms and Required Middleware

The following products are required to connect the individual platforms:

Online System/Monitor | Job Execution | Connection / Products
--- | --- | ---
mainframe | mainframe (local*) | none
mainframe | other mainframe | Entire Net-Work
mainframe | UNIX/Linux | EntireX Broker
mainframe | Windows | EntireX Broker
UNIX/Linux | UNIX/Linux (local*) | none
UNIX/Linux | other UNIX/Linux | EntireX Broker
UNIX/Linux | Windows | EntireX Broker
UNIX/Linux | mainframe | Entire Net-Work

* "local" means that the Entire Operations online system is installed on the same machine on which jobs are executed.

Combinations are also possible. For example, if you want to install the Entire Operations online system on one mainframe and execute jobs on another mainframe and another UNIX/Linux or Windows machine, you would need:

- Entire Net-Work (one for each system to be connected) for connecting to the other mainframe and to UNIX/Linux or Windows, and

- EntireX Broker (on one system) for connecting to UNIX/Linux or Windows.

## Compatibility and Migration

- Support for Previous Versions

- Compatibility Check for System Automation Tools Versions

- Data Migration

- Database File Migration

- Application Programming Interface (API) Versions

### Support for Previous Versions

Entire Operations Version 5.5.x is the official replacement for Entire Operations Version 5.4.3, or earlier versions.

You can view all available Software GmbH product versions and check the dates when their maintenance ends by visiting the Empower website at https://empower.softwareag.com/:

1. Log in to Empower.

2. Expand Products & Documentation in the left menu of the page and select Product Version Availability:

3. Select the required filter criteria from the drop-down list boxes and click on the SEARCH button.

   A list of supported Software GmbH products that meet the filter criteria is shown. In addition, the end-of-standard-maintenance dates are indicated in the EOM column.

   If you mark Show prior Product Versions, only product versions that are out of maintenance are listed.

### Compatibility Check for System Automation Tools Versions

(with Version 5.5.1 CF 02)

Entire Operations requires the following versions of System Automation Tools (SAT):

- Entire Operations versions earlier than version 5.5.x. require System Automation Tools versions earlier than Version 3.5.2.

- Entire Operations Version 5.5.x requires System Automation Tools Version 3.5.2 (and above).

Compatibility check constraints are used to enforce valid version combinations:

- At the start of an Entire Operations session on a CUI client (NOP),

- At the start of an Entire Operations session on a GUI client (OGC),

- At the start of the Entire Operations Monitor.

Incompatible versions cause start failures and an error message similar to the following occurs and is written to the SYSOUT file of the Entire Operations Monitor:

`EOR2598 - SAT Version >= 3.5.2 required for NOP 5.5.2`

### Data Migration

The data migration from Entire Operations Version 5.4.3 to Version 5.5.x is performed as part of the migration process.

The data migration can be run any time manually by using a Natural batch JCL:

    LOGON SYSEOR
    DMDRIV-P
    FIN

Internal control records prevent repeating of already completed migration steps.

### Database File Migration

This following migration steps are only required if you migrate data from an Entire Operations Version earlier than Entire Operations Version 5.5.x:

To migrate data from Entire Operations Version 5.4.3 to Version 5.5.x

1. Make a backup of the Entire Operations Version 5.4.3 system files.

2. Unload the old database files and load the new database files by using the import/export functions.

   Or:
   Adapt the old Entire Operations System File 1 for use with Entire Operations Version 5.5.x. Some data fields have larger field lengths and some descriptors have been released or added.

3. If you want to keep your log data: Adapt the System Automation Tools log file for use with System Automation Tools Version 3.5.1.

   Or:
   On UNIX: If migration is required, it is performed automatically within the guided installation.

### Application Programming Interface (API) Versions

The API versions remain the same as in Entire Operations Version 5.4.3.

Notes:

1. Parameters reserved for future use in a previous Entire Operations version may be used in Entire Operations Version 5.5.x.
2. Parameters with names like `-NETWORK-VERSION` or `-SYMTAB-VERSION` have been used since Entire Operations Version 5.4.3. Please refer to the descriptions of Versioning of Job Networks and Versioning of Symbol Tables in the User's Guide documentation.
3. For several APIs, new return codes were added. Please check the description of the API Routines in the User's Guide.

Only the latest versions of APIs should be used for new development. These are documented in the section API Routines in the User's Guide. Starting with the next Entire Operations version, older APIs will be supported for the two previous versions only. The existence of an older API routine in the Natural SYSEOR system library does not imply that it is still supported.

Most API routines contain a version number as the seventh character of their name. For example, in this Entire Operations version the Log API is NOPULW9N. The previous version NOPULW8N is still supported for a limited time.

## Code Page Setting

we recommend that you run the Natural environments for the Entire Operations Monitor, the Entire Operations character interface and the Entire Operations RPC server with enabled code page support. For the required Natural parameter settings, see the Natural parameters `CFICU` and `CP` described in the Natural Parameter Reference documentation.

If code page support is enabled, user exits and macro JCL defined in Entire Operations can use the Natural system variable `*CODEPAGE` (see the Natural System Variables documentation) which determines the current code page for correct code page conversion, for example, with the Natural `MOVE ENCODED` statement.

The Entire Operations Monitor tasks log the current code page setting during startup. In the Entire Operations character interface, the current code page setting is shown by the `TECH` direct command (see the Direct Commands documentation).

When using the `CFICU` and `CP` parameters, they must be set to the same values for the Entire Operations Monitor, the Entire Operations character interface and the Entire Operations RPC server.

## Solved Issues

All solved issues of Entire Operations (NOP) version 5.5.2 (with cumulative fixes CF 01 through CF 12) and version 5.5.3 (with cumulative fixes CF 01 through CF 02) are included in this release.

All solved issues of Entire Operations GUI Client (OGC) version 5.5.2 (with cumulative fixes CF 01 through CF 12) and version 5.5.3 (with cumulative fixes CF 01) are included in this release.

- Entire Operations (NOP) Version 5.5.3 Cumulative Fix 02

- Entire Operations (NOP) Version 5.5.3 Cumulative Fix 01

- Entire Operations (NOP) Version 5.5.2 Cumulative Fix 12

- Entire Operations (NOP) Version 5.5.2 Cumulative Fix 11

- Entire Operations (NOP) Version 5.5.2 Cumulative Fix 10

- Entire Operations (NOP) Version 5.5.2 Cumulative Fix 9

- Entire Operations (NOP) Version 5.5.2 Cumulative Fix 8

- Entire Operations (NOP) Version 5.5.2 Cumulative Fix 7

- Entire Operations (NOP) Version 5.5.2 Cumulative Fix 6

- Entire Operations (NOP) Version 5.5.2 Cumulative Fix 5

- Entire Operations (NOP) Version 5.5.2 Cumulative Fix 4

- Entire Operations (NOP) Version 5.5.2 Cumulative Fix 3

- Entire Operations (NOP) Version 5.5.2 Cumulative Fix 2

- Entire Operations (NOP) Version 5.5.2 Cumulative Fix 1

- Entire Operations GUI Client (OGC) Version 5.5.3 Cumulative Fix 02

- Entire Operations GUI Client (OGC) Version 5.5.3 Cumulative Fix 01

- Entire Operations GUI Client (OGC) Version 5.5.2 Cumulative Fix 12

- Entire Operations GUI Client (OGC) Version 5.5.2 Cumulative Fix 11

- Entire Operations GUI Client (OGC) Version 5.5.2 Cumulative Fix 10

- Entire Operations GUI Client (OGC) Version 5.5.2 Cumulative Fix 9

- Entire Operations GUI Client (OGC) Version 5.5.2 Cumulative Fix 8

- Entire Operations GUI Client (OGC) Version 5.5.2 Cumulative Fix 7

- Entire Operations GUI Client (OGC) Version 5.5.2 Cumulative Fix 6

- Entire Operations GUI Client (OGC) Version 5.5.2 Cumulative Fix 5

- Entire Operations GUI Client (OGC) Version 5.5.2 Cumulative Fix 4

- Entire Operations GUI Client (OGC) Version 5.5.2 Cumulative Fix 3

- Entire Operations GUI Client (OGC) Version 5.5.2 Cumulative Fix 2

### Entire Operations (NOP) Version 5.5.3 Cumulative Fix 02

Problem | Short Description
--- | ---
NOPALL-4273 | NOP 553 CF2 Several Corrections N4273.7 NOP LDA XSFILATL got new attribute XS-FILAT-LINE-LEN-GT-250 (A1) The input and output values are described below any line longer than 250 bytes. With NPROS-436, the NPROSA struct fileAttr got the new attribute anyLineLongerThan250:
    struct fileAttr {
    /* X00083           214 01 ff. */
       ...
       CE_CHAR anyLineLongerThan250 [1];    /* v NP436  2II 03 */
          /**         in:  '+'    perform this check
                     *in:  other  skip this check
                     *out: 'N'    file has no line longer than 250 bytes
                     *out: 'Y'    file has at least one line longer than 250 bytes
                     *out: ' '    skipped, unknown
                     *out: '+'    skipped; NPROS < 2.1.18.3 doesn't support this
          *//* ^NP436 */
             ...
       };
Usage:NPROS, Function FILE / GETATTR:If you like to know whether the file contains at least one record longer than 250 bytes, please set XS-FILAT-LINE-LEN-GT-250 := '+' prior to the invocation of FILE / GETATTR. The result is passed back also in XS-FILAT-LINE-LEN-GT-250. See above for the possible result values. N4273.A - NOP 553 CF2 - workSome message (long text) corrections.1859 - mod - eqaced1860 - mod - eqaced
NOPALL-4274 | OGC: Monitor Status Window - Status text truncated
NOPALL-4286 | More objects imported than selected
NOPALL-4288 | NAT1305 in IRREL--N Line 2580 - Shutdown
NOPALL-4289 | OGC Server - Duplicate node "Short Names" must be avoided. Added the check for Node short name check as well...
NOPALL-4291 | Job Activation is not aborted, if the Global JCL Activation Exit sets P-RC >= 2 If the Global JCL Activation Exit comes back with a return code >= 2, the JCL loading for the affected job will be aborted, and the job will be set to a permanent error state. A documentation update is not necessary. The exit error handling now works as already documented. CUI and OGC, active JCL regeneration: The 'normal' JCL regeneration will be rejected for a job for which the JCL loading was rejected by the exit. A re-activation of the job must be performed for such a case.
NOPALL-4296 | RPC loops in OPJADJ-N on Linux
NOPALL-4294 | End-of-Job action delays - eventually related to NOM API NOMTP01N processing - EJANOMDP Replaced FIND loop with SORT by READ loop without SORT. Reason: Performance.- EJANOM-P The elapsed time of NOMTP01N API calls will be logged if they were longer or equal than 5 seconds. Example: NOM API Call - 5.3 Sec - Error Code 0 NOM < (194) $SN.NOPALL.N4294B100.0006.J200######A SYSOUT File passed to NOM
NOPALL-4295 | z/OS: In User node maintenance once LOGON-DEFAULT 'No Password' is set as 'Y', it cannot be reset by user
NOPALL-4151 | z/OS: EOR0254 error for function (technical) user (without password) while regenerating jobs
NOPALL-4285 | NPROS Error NPR3361, etc. - SU-X---N:Avoid shortening of message NPR3361.- Corrected the error handling for 'File can't be written'.
NOPALL-4272 | SYSOUT Lines > 250 bytes are truncated, if SYSOUT is copied from Linux to NOM via BS2000 Some error handling improvements.
NOPALL-4201 | Wrong message for "Where used" in: Waiting for prerequisites NOP CUI: Window 'Waiting for Prerequisites':Line command 'W' (Where used) for an input condition:If no matching condition can be found, the messageEOR0798 - No matching Condition found will be shown on top of the window, instead of EOR0930 - Object not found
NOPALL-4301 | Promoted networks disappear from the list "Next scheduled network starts (CUI -> PF11)" Additional screen to confirm modification if PF3 is pressed instead of PF5.
NOPALL-4305 | Summary Messages missing at End of the Export File, when using Batch Export NOP Export in batch to location WRK (work file):The epilog messages will be appended (as comments) to the work file now.
NOPALL-4306 | EOR-SYMBOL Command Meta-command EOR-SYMBOL:Avoid the shortening of the written symbol to 80 bytes.The maximum symbol value size (120 bytes) can be set correctly now.
NOPALL-4276 | License Check on Mainframe: Pgm NOPLC1-N Line 2160 Error NAT1143 Avoid NAT1143
NOPALL-4237 | NOP network no longer starts if all activities are defined in Task1 with NOP 5.5.2 CF12 With the introduction of new global variable for task matrix, the defaults were not updated while installing NOP. Fixed the issue to update the defaults and eventually the global variable.
NOPALL-4315 | Monitor hanging - Activations not performed Just added some (disabled) diagnostics.
NOPALL-4307 | Monitor does not start up properly after Adabas shutdown FROM NOP 553 CF02 THE PACKAGE CONTAINS THE SOLUTION FOR THE ENHANCEMENT
NOPALL-4040 | Copy SYSOUT Files not only to BS2000 Nodes, but to Linux Nodes also. For this enhancement currently exists one known issue: in case of an inactive SYSOUT store node it could be that the dedicated SYSOUT Store task (task 92) comes into a functional loop if the SYSOUT store node becomes active again and starts with the file transfer. In this case, you might try to stop just this task (in the CUI task list with line command 'C'), and try to restart it (with line command 'S').

### Entire Operations (NOP) Version 5.5.3 Cumulative Fix 01

Problem | Short Description
--- | ---
NOPALL-4187 | Active jobs have disappeared from the display before or after execution. New direct command (to be used for debugging in this specific case): `SET MONITOR JA-CT <level>` 10 log job active count, only if changed compared with previous count 20 log job active count, always 30 same as 20, log active jobs, too. The setting is not persistent. It must be repeated if the monitor was started newly. The setting has also effect on the NOP CUI session where the command was issued.- Location of job active counting - active jobs list of current NOP CUI session - before job submission - at active network end - during network deactivatiion or job deactivtion, on job level - in API NOPUAC5N- target of counting. All counting results will be written to the NOP log. The additional log messages contain owner, network, run number. If related to a dedicateed job, also the job name. Examples of NOP log messages Run 2464 - 14 active Job(s) Run 2453 - 12 (after 13) active Job(s)- Test module NAJACT-T can be called from the Natural command line in library SYSEOR. The counting result will be shown, and will be written to the NOP log.
NOPALL-4212 | Monitor Accounting - automatic stopping erroneous
NOPALL-4219 | Error 5510 during SYSOUT Copy from Linux to BS2000 - with NPROS 2.1.17.3 With NOPALL-4098, XS-FIL-N (the Unix file access module) returned 5510 for an invalid session ID. But the End-of-Job Action module EJA----P checked for 510 only. Correction: XS-FIL-N sets return code 510 instead of 5510 for invalid session ID. EJA----P checks for both 510 and 5510. With the correction, the existing SYSOUT copy retry mechanism in EJA----P works correctly again. Note: The correction is in NOP only. It should work with all NPROS versions.
NOPALL-4221 | NOP 5.5.2.12: Follow up of -NOPALL-4160- Redundant log texts with symbol resolution Follow-up for NOPALL-4160: Avoid redundant symbol replacement logging at more locations.
NOPALL-4229 | NOP 5.5.2.12: Monitor crash due to unexplained cause Probably caused by EOR3215 in Unix string search End-of-job checking, Unix, string search: Corrected the error handling for `EOR3215 - Node :1: - Service :2: not in SYSSATU/SATSRV`. In this case, the affected active job will be set to 'not ok'. Note: The error EOR3215 is caused by an inconsistent Unix or Windows node definition by the customer. Each Unix or Windows node must have a related entry (section) in SYSSATU / SATSRV.
NOPALL-4185 | Node Logoff and / or Node Invalidation at End of End-of-Job Action (EJA) Exit Processing Some enhancements for the handling and logging of the node invalidation at the end of an exit execution. Please refer to NOPALL-4233 for a documentation update. See also item 6 in User Exit Coding Restrictions.
NOPALL-4209 | Symbol is unexpectedly resolved from 'other active Symbol Table of Network' - caused by NOPALL-4147 Default Setting (4): `Added the settingSearch also in other symbol tables of active network ==> (Y/N)` If `Y` is specified here, symbols will be searched also in other active symbol tables of the active network. The default is `N`. Note: After a change of this setting, a monitor restart is required.
NOPALL-4251 | NOP - No JV possible after changeover to dummy Prerequisite checking: Corrected the NOP node table handling for job type 'DUM' and temporary dummy jobs. BS2000 ESA nodes: Corrected the job variable availability detection. Hotfix compatibility: An engineering hotfix is possible. It would be applicable from NOP 552 CF12 through NOP 553 CF1.
NOPALL-4248 | NOP 5.5.2.CF12: Regenerate JCL deletes SYSOUT History JCL regeneration: Don't reset the current job ID. The history of previous SYSOUTs will not be disturbed anymore. NOPALL-4193 NOP552/10 CLEAN: Monitor-Error NAT3009 in IRREL--N line 2595
NOPALL-4259 | Schedule uses calendar incorrectly Corrected the schedule calculation from the schedule definition, for schedule definitions with Weekly Schedule, and Week Days definition like 1W 2W 3W 4W 5W(W means: W is n-th workday of week, e.g. 1W). The error occurred during the first (incomplete) week of a year. The correction is compatible to NOP 552 CF11 or above.
NOPALL-4249 | NOP 5.5.2. CF12 / NPR 2.1.17.3: Repeat count not consecutive with job repetition - Re-submission handling correction. Avoid race condition in prerequisite checking.- Avoid unnecessary SYSOUT file renaming before job repetition on Unix and Windows. SYSOUT file names on Unix and Windows contain the repeat count since a long time.
NOPALL-4257 | Network and Job Activation - Inconsistent Time Frame CUI: Default Setting (2): Default Deadline after earliest start must be larger than default latest start after earliest start. Job master - scheduling parameters: deadline must be later than latest start. Network schedule definition:deadline must be later than latest start.
NOPALL-4244 | NOP 5.5.2.10: HIST-DAY= imported wrongly before NOPALL-4136 - Can these days be corrected?
NOPALL-4243 | NOP 5.5.2.10 Active job recovery parallel to batch cleanup causes monitor errors and monitor shutdown The CLEAN would not deactivate the jobs that came in the queue after lock was placed. Hence reducing the conflict with the general process of deactivation which will continue as normal. Also the locks are placed specifically only for deactivation and file deletion.
NOPALL-4258 | Again and again the LOGON login screen (NPR) NOP CUI: Corrected an invalid error handling in SYSOUT Browsing for Unix and Windows jobs. NOP CUI: Corrected the Node Autologon handling for SYSOUT Browsing for Unix and Windows jobs. In some cases the logon screen was presented superfluously. (N4258.1) NOP CUI, node status list: After 'LOGOFF NODE <node>', the node's operating system name was deleted. (N4258.2) NOP CUI: 'Waiting for' for input condition depending on BS2000 job variable: Message 'JV ... doe not exist' was not shown. Notes on Autologon The combination of 'NOP Userid + Node + Unix Userid' must be defined for autologon for JCL editing and / or SYSOUT browsing. For each allowed combination, a successful NOP node logon with a valid Unix user ID and valid Unix password must have been performed. This must be repeated after each Unix password change because NOP keeps ciphered passwords of successful node logons which are necessary for autologon.
NOPALL-4226 | Follow-up of NOPALL-4170: Utility or API requested to delete remaining active conditions of de-activated runs Added in 'Default Setting (3)' `Network Deactivation: with active conditions` If `Y` is specified here: If an active network is deactivated, the belonging active conditions will be deactivated, too. During a cleanup, active conditions will be be deactivated not only by retention period but also if their creating network run or job run is not active anymore. Default: `N`
NOPALL-4238 | NOP 5.5.2.10: Symbols are not activated or deleted from the active area Preface: This update does *not* fix the root cause of the active symbol loss. It only provides a utility to list the current content of the active symbol tables of an active network. Updates Some enhancements for the ET logic for symbol table activations, in the monitor. Added utility to list the current active symbols of an active network as a snapshot. The target is the NOP Extennded Logging. Defining an additional job to list active symbols. Example:
                           Job
         Definition (Master) Job Name       ==> NASYLE____
         Mod ==> SN       17.12.24 09:03 Description    ==>
         NA symbols -> extended log________________________ Job
         Type       ==> NAT Execution Node ==> N0518
         Linux Special Type   ==> ________
         Symbol Table ==> NET01-518_ Milestones     ==> ________
         Symbol Table Version ==> __________ Restartable
         ==> N           Suffix Symbol ==>
         ________________________________________
         Escape Characters:    Activation ==> @
         Submit
         ==> ? End-of-Job Action Errors set 'not ok' Conditions
         ==>
         NEnter-PF1---PF2--PF3--PF4---PF5---PF6---PF7---PF8-
         --PF9--PF10---PF12-      Help  Add  End  Edit  Save
         Spec  Symb  Net   JCL  Browse Menu
         Job: JCL Definition (Master)Job Name
         ==> NASYLE            Mod ==> SN       17.12.24
         09:03Description    ==> NA symbols -> extended
         logJob Type       ==> NATExecution Node ==> N0518
         Linux           Symbol Table ==> NET01-518JCL
         Location   ==> NAT                  JCL Load Mode ==>
         AJCL Node       ==> N0518 LinuxFile/NatLib    ==>
         SYSEOR______________________________________Member
         ==> NASYLE-N ________VolSer         ==> ______  (if
         not catlgd)   Password ==>
         defined ==>
         nonter-PF1--------PF3--PF4---PF5---PF6---PF7---PF8-----
         -PF10-----PF12--     Help       End  Edit  Save  Spec
         Symb  Import   Browse   MenuExecuting the
         active symbol listing in a Natural batch
         jobExample:LOGON SYSEORNASYLI-P S
         @P-OWNER @P-NETWORK @P-RUN
         @P-JOBFINParameters of NASYLI-P1
         P-TARGET              (A01)      /* in*     'S'  job
         SYSOUT*     'E'  NOP extended log1 P-OWNER
         (A10)      /* in1 P-NETWORK             (A10)
         /* in1 P-RUN                 (I04)      /* in1
         P-OWN-JOB             (A10)      /* inViewing
         the lsit of active symbols (snapshot)1. Check when
         the NASYLE (NASYLE-N) utility was executed:20.01.25
         ***** Entire Operations *****
         10:31:02Active Jobs           Owner TESTBED     Network
         NET01-518   VersionSelection AW________
         Run from 2683_ to
         2684_--------------------------------------------------
         ----------------------------C   Job          Run Typ Loc
         JobId  Node  Date  Time Message    *---------
         ---_   NASYLE      2683 NAT NAT          N0518 20.01
         09:25 Ended ok...Open the NOP Log for that time
         (here: 09:25)eventually with preselection of owner,
         network, run.Search for Log messages like
         EOR53D51 TESTBED    NET01-518  NASYLE      2683 20.01
         09:25:14.8 Submitted: NAT Pgm SYSEOR/NASYLE-N Node 518 User
         ID nprusr01* EOR53D51 TESTBED    NET01-518  NASYLE
         2683 20.01 09:25:14.8 Active Symbols logged  EOR53D51
         TESTBED    NET01-518  NASYLE      2683 20.01 09:25:14.8
         Natural Pgm SYSEOR/NASYLE-N terminatedThe message
         'Active Symbols logged' is prefixed by an
         asterisk.Overtype the asterisk with any character and
         press Enter.The list of the currently active symbol
         tables of the network with their respective content will be
         shown:Owner TESTBED Network NET01-518 Run 2683 -
         Active Symbols   ---Columns 001 072====>
         SCROLL===>
         PAGE***** ****************************** top of data
         *****************************00001 NASYLI-P - List of
         active Symbols - 20/01/25 09:25:14.800002 Owner TESTBED
         Network NET01-518 Run 2683 Job NASYLE00003
         -------------------------------------------------------
         00004 Owner TESTBED SymTab NET01-518 Run 2683 Type NV Status
         1000005 CMDLINE-EXE100006 ... nprusr
         /etc/passwd00007 ... origin: activation00008
         GREP00009 ... /bin/grep00010 ... origin:
         activation00011 JCLDIR00012 ...
         /home/sag/jcl/testbed00013 ... origin:
         activation...
NOPALL-4263 | NOP/OGC - Error after import - EOR3218 Evaluierungs-Fehler
NOPALL-4246 | NOP 5.5.2.12: still incomplete mails / Follow-up of NOPALL-4026 Corrected the Subject generation for emails sent via Unix (Linux). Corrected the end-of-job condition setting for the case when an error occurred during SYSOUT copying from Linux to BS2000 and if in a job master definition `End-of-Job Action Errors set 'not ok' Conditions` is set to `Y`.
NOPALL-4267 | Message sending loops if not existing Message Sending Exit is specified at global user exits Corrected the error handling for the following cases: The Global Message Sending Exit is changed while the monitor is running. The exit does not exist. Before the correction, a functional error handling loop occurred. With this correction, error messages will be logged, and the monitor will be shut down.
NOPALL-4196 | NOP552/preCF12 EOR4000 - Editor Error: COPY Error 510 X-EDSV-P:Corrected the JCL node testing. If a matching NPROS session exists already, the node testing will be skipped.
NOPALL-4269 | Utility ND-LB--P issues Customer's macro source needs to be corrected at the places marked with N4269. This will avoid a NAT1305 error. See attached Macro source EOR-T001.N4269M01.txt. Utility ND-LB--P: More logging in bulk mode. Macro objects will be deleted by NOP, if a runtime error occurs during their execution. The macro source will be kept. This will prevent repeated occurrences of the same error in the NOP monitor, and will prevent the NOP monitor to be terminated due to this. Works as designed. CUI Log display: Avoid message truncation.
NOPALL-4270 | Cleanup: Sporadic abort in CL-LOG1N line 2930 with NAT3009 subcode 0 CL-LOG1N: Extended the ON ERROR routine. After a NAT3009 error, a retry of the cleanup will be attempted.
NOPALL-4275 | OGC: Filling a multiple symbol leads to error NAT1305
NOPALL-4279 | NOP552/12 symbol tables are missing after export There was an issue with the examine statement because of which some symbol tables were not exported. `EXAMINE` has been replaced with `FOR` loop comparing all the fields to find unique symbol tables.
NOPALL-4278 | NOP 5.5.2.12 Preferred networks disappear from the 'Next planned network starts (CUI -> PF11)' list

### Entire Operations (NOP) Version 5.5.2 Cumulative Fix 12

Problem | Short Description
--- | ---
NOPALL-3958 | Browse of Sysout on ESA node without password results in ESY5510 instead of being prompted for the password
NOPALL-4135 | Schedule setting partially exported incorrectly
NOPALL-4145 | Message "Übergabe an NOM abgebrochen" although files were passed to NOM File passing to NOM: Log message 'Passing to NOM aborted' is no longer shown if the file passing was successful.
NOPALL-4146 | EJC----P Line 3118 Error NAT1316 - after a Node Definition was deleted EJC----P: Added some more checks for the validity of G-NI (node index in internal node table).
NOPALL-4136 | HIST-DAY= imported incorrectly IENMI--PHIST-TO-TABLELogic simplification by using CALL 'NOPDTA'
NOPALL-4138 | No EOR message (mail / event) for NPR3406 - 10 exit code read attempts If Global Message Sending for the event Job not ok, or execution error is enabled, and if after multiple read attempts no exit code message could be retrieved from the SYSOUT of a UNIX or Windows job, a global message (e.g. Email) will be sent. Example: Entire Operations Monitor
    (DAEF 55D) on 04.04.2024 at 11:17:57Owner NOPALL -
         Network N4138A - Run 17 - Job ASYNC-001... Execution
         Node 518 (npr_pcsn02) - JobId 9624Event: NPR3406 Exit
         code message not foundNPR3406 Exit code message not
         found10 Exit Code Read Attempts failed...
         Message generated on 04.04.2024 at 11:17:57
NOPALL-4144 | Input Condition Check Issue Disabled Round Robin mechanism in prerequisite checking.The field EOR-JOB-ACTIVE.A-RR-POSITION is obsolete now. GDA1---G.G-USE-PQC-ROUND-ROBIN is also obsolete.
NOPALL-4148 | Dummy job executed although execution node not available / Follow-up SI-547036 HF55 -NOPALL-4069 - NAT1316 in SYSEOR/PQC----P line 6942 Avoid NAT1316 at multiple locations in PQC----P.
NOPALL-4152 | Since NOP552 CF3 jobs receive error message `EOR1329 - A JCL record is longer than 80 characters` z/OS: Skip the JCL line length check (introduced with NOPALL-3664). If the record does not begin with '//'-, the record begins with '//*'.
NOPALL-4147 | Symbol Search Order Extension - Additionally search other Symbol Tables of Active Network If a symbol could not be found in the search hierarchy up to 'NA' (network active), it will be searched addionally in the new level 'NO' (network active - other symbol tables).This will be done before checking the 'OD' (owner default) and 'SD' (system default) symbol tables.The additional search is intended for the following case: An active symbol is being written by the API into a symbol table which in it's superdescriptor has the active network's owner, the network and the run but is not defined on network or job level. This includes the case in which no symbol table is defined on network or job level.
NOPALL-4154 | Linux: execvp errno 26 = ETXTBSY; Process times for accounting not found NOTE The main correction comes in NPROS 2.1.17 CF3 with NPROS-419. Correction here: Unification or UNIX (Linux) script frame exit codes for specific events.These are contained in the new LDA.
         KONXEC-L.*  1 KXEC-EXECVP-ERROR                I
         4 CONST<100>*    -- execvp error*  1
         KXEC-EXECVP-TEMP-ERROR           I          4
         CONST<100>*    -- execvp temporary error   1
         KXEC-SYSOUT-TOO-LARGE            I          4
         CONST<101>*    -- SYSOUT too large*    -- used for
         NPR/Windows too   1 KXEC-SIGTERM-RECEIVED            I
         4 CONST<102>*    -- signal SIGTERM or
         SIGKILL*    -- received   1 KXEC-SCRIPT-NOT-FOUND
         I          4 CONST<103>*    -- (user) script
         not found   1 KXEC-EPILOG-SCRIPT-ERROR         I
         4 CONST<104>*    -- epilog script not executable*
         -- etc.   1 KXEC-SUBMIT-ERROR                I
         4 CONST<105>*    -- (other) submit error*  1
         KXEC-EXECVP-PERM-ERROR           I          4
         CONST<120>*    -- execvp permanent error
NOPALL-4163 | EOR0339 - Maximale SYSOUT-Groesse 0 MB ueberschritten UNIX and Windows jobs: For 'SYSOUT too large' the exit code 101 (= KXEC-SYSOUT-TOO-LARGE) will still be set by the script frame generated by NOP. The prohibition of SYSOUT actions for excessive SYSOUT is no longer depending on exit code 101. Instead, the NPROS flag nprJobSubmit.sysoutTooLarge[0] (Natural equivalent: XS-JOB-A.XS-JSU-SYSOUT-TOO-LARGE will be checked. The flag was added to NPROS for NPROS-404, and is available with NPROS 2.1.17 CF1 or above. Setting the exit code 101 in a user script does no longer cause an unwanted 'SYSOUT too large' handling. Note: SYSOUTs that exeed defined maximum SYSOUT size can still be browsed up to the 'SYSOUT Line Limit' if it is defined in the NOP defaults.
NOPALL-4164 | Windows: Job exit code 1 not triggering a failure The SYSOUT size determination and comparison for Windows jobs (in the script frame) was corrected. The handling of Windows job exit codes was checked. End-of-job actions for 'job not ok' and / or for specific exit codes are performed correctly. The handling is analogous to UNIX jobs.
NOPALL-4160 | Redundant log texts with symbol resolution The job submission modules which invoke NOPSYR8N (symbol replacement routine) provide a table for already logged symbol replacement. In NOPSYR8N: If a replaced symbol is already in the table P-ALREADY-LOGGED, it's logging will be skipped.
NOPALL-4131 | CUI and GUI - Network start time modification faulty Before this fix, whenever the time for network start and the time for job start were different, this difference was added to the difference of old and new network start. This is fixed now and network start time modification works as expected.
NOPALL-4155 | NOP 5.5.2 CF11 + HFs 55-57: NAT1316 in PQC----P - other line PQC----P: Execution node index #ENI will be re-determined, if not in valid range.
NOPALL-4177 | Follow up of NOPALL-4090 CUI: EOR4000 - Editor-Error: ADD - Cannot allocate BP block
NOPALL-4132 | NOP 552 CF12 several corrections All mentioned corrections are done.
NOPALL-4174 | Question (NOP552 CF10): Task09 (Message sending) Status: pending triggers and pending triggers at other Task07 (activation) Some enhancements and corrections of the error handling for cases such as `EOR3263 - Kn. 867 - Service NPR_NI1DPDPILX not definedEOR3215 - Kn. 867 - Service NPR_NI1DPDPILX not in SYSSATU/SATSRV`. Excessive logging and message sending could not be observed for this case in the NOP development environment.
NOPALL-4142 | Erroneous usage of BS2000 user IDs for NPR/UNIX node logon during job execution tracking Several coding enhancements for the setting and checking of the operating system class of nodes.
NOPALL-4031 | NOP Reactions on ESA: ESY5999 TCP:connect:111:Connection refused.
NOPALL-4170 | Cleanup or Deactivation cause Detection of Input Condition Reference LNT Several corrections for the input condition reference LNT.
NOPALL-4182 | Recovery Repetition not working with "non Recovery-Jobs" In NOP 552 CF1, a recovery is also possible for jobs which don't have the special type 'R' (for recovery only). Until now, the customer's issue was not reproducible.The code changes for this iTrac are for robustness, error handling, logging etc. Also fixed an issue with status 1000 (passive wait) and stacked status 2500 (prerequisite check). This might be related to NOPALL-4197.
NOPALL-4198 | CUI and Batch: Report "Accounting Data" is empty Conditions for read loop were faulty. Fixed the read loop by redefining the field and comparing it with another field.
NOPALL-4199 | Accounting Data for BS2000 Jobs: CPU Time missing Jobs running on BS2000: Corrected the propagation of the CPU time into the accounting data.
NOPALL-4195 | NOP - Error in IE-EXA-P - Less Objects and Owners are exported after upgrade to CF11 IE-EXA-P : Avoid NAT1108IENMX1-N : Avoid NAT1143
NOPALL-4207 | NOP 5.5.2.12: Symbol is unexpectedly resolved from 'other active Symbol Table of Network' - caused by NOPALL-4147 N004207A is a special module to replace NOPSTW-N. With this, NOPALL-4147 can be rolled back until NOPALL-4209 will be available.

### Entire Operations (NOP) Version 5.5.2 Cumulative Fix 11

Problem | Short Description
--- | ---
NOPALL-4114 | OGC 5.5.2 CF10: Last 20 lines duplicated during SAVE with JCL Loc
NOPALL-4098 | Follow up of NOPALL-4081 and SI-548810 for 5.5.2 CF10- Usage of NOP API NOPUNX1N - LOGOUT during READ-FILE Loop
NOPALL-4120 | MAC-GE-P does not catalog MACROs for job type DAT
NOPALL-4079 | OGC: MACRO JCL Command TEST - NAT0610 This statement is not permitted in reporting mode
NOPALL-4038 | New 'effective to' attribute in the Network Schedule Definition
NOPALL-4123 | CUI: Stuck in NOP Active Scheduling Parameters Screen - follow up to NOPALL-4062
NOPALL-4133 | Multiple UNIX nodes with same node number - No EOJ actions of uninvolved jobs
NOPALL-4128 | Export of EOJ string check omits leading blank
NOPALL-3958 | Browse of Sysout on ESA node without password gets ESY5510 Instead of being prompted for the password
NOPALL-3898 | CUI on Linux, using ESA BS2000 node: Manual logon necessary for SYSOUT Browsing
NOPALL-4084 | MACRO TEST: Email for missing Symbol: Context Information missing
NOPALL-4069 | Dummy job is executed although execution node is not available
NOPALL-4070 | Email Sending - Loop, if wildcard in attachment
NOPALL-4062 | CUI: Stuck in NOP Active Scheduling Parameters Screen
NOPALL-4089 | Multiple symbol values are cut to 54 characters by symbol function MV (multiple value)
NOPALL-4082 | Follow-up for NOPALL-4026 - No Event, when 'File in Use' message is issued for SYSOUT copy to BS2000
NOPALL-4088 | OGC 5.5.2.10 - Saving large JCL with Location NAT causes error EOR4000 - Editor error: STAT 504 Session does not exist
NOPALL-4090 | CUI: EOR4000 - Editor-Fehler: ADD - Cannot allocate BP block
NOPALL-4095 | NOP 552 CF10: CUI: JCL location change on ActiveQueue doesn't work any more
NOPALL-4096 | Error in NOP: PQC-SY-N 1455 - JV def. record missing
NOPALL-4117 | Monitor Error NAT3145 in JARSPWFN Line 1630
NOPALL-4074 | Monitor Error NAT3009 in JA-SCS-P Line 2410
NOPALL-4093 | NOP 5.5.2.CF10 - Follow up of SI-492225 and NOPALL-3894 - Input condition reference WCW-1 does not work over turn of the year
NOPALL-4097 | Truncation of File Name with DAT Job
NOPALL-4094 | OGC 552 CF10 - JCL Load Mode 'S': Changes to the active JCL of a job are not taken into account when the job is repeated
NOPALL-4106 | NOP543/13 CL-SYA-P 2120 NAT3113 Specified ISN invalid. DB/FNR/Subcode 216/36/0
NOPALL-2873 | OGC: Direct 'OPEN Natural Member' function in Job Definition dialog

### Entire Operations (NOP) Version 5.5.2 Cumulative Fix 10

Problem | Short Description
--- | ---
NOPALL-4081 | Usage of NOP API NOPUNX1N - LOGOUT during READ-FILE loop, when NP
NOPALL-4080 | Batch catalog of MACROs abends when one member cannot be cataloged
NOPALL-4035 | z/OS: MACRO JCL loaded incompletely - sporadically
NOPALL-4029 | Job in passive wait for resource, but resource available
NOPALL-4021 | NOP 552 CF10 several corrections
NOPALL-4037 | OGC - Error NAT1316 while attempting to set a condition, within Network Graphics
NOPALL-4048 | After using wildcard for profile when adding a new user, user won't be added
NOPALL-4005 | Error NAT3144 in line 5595 of JA-DJ--P
NOPALL-3980 | NOP 5.5.2.8 + Hotfix 31: NOP on UNIX: Error NAT0104 occurs during batch catalog
NOPALL-4057 | P-REPEAT and P-REPEAT-COUNT symbols faulty
NOPALL-4051 | Recursive Symbol Resolution in Input Conditions
NOPALL-4008 | BS2000 LMS Member Name in Job List of Network only 8 Characters
NOPALL-4054 | NPR Node not active - due to end-of-job check issues for excessive UNIX SYSOUT size --> SYSOUT Size Limit
NOPALL-4042 | OGC/RPC - EXX10030069 opening SYSOUT (for one user only) after NPR upgrade
NOPALL-4071 | OGC - DAT Job cannot be defined for BS2000 execution nodes (ESA)
NOPALL-4073 | Error handling using program MAC-GE-P (MACRO Generation)

### Entire Operations (NOP) Version 5.5.2 Cumulative Fix 9

Problem | Short Description
--- | ---
NOPALL-4027 | OGC and NOW: Waiting for: Actions for active Input Conditions dep
NOPALL-3894 | Input condition reference WCW-1 does not work over turn of the year
NOPALL-3987 | CAPS setting cannot be saved in SAG Editor
NOPALL-4010 | BS2000: Line wrap undercuts subsystem specific double-slash
NOPALL-3979 | SYSOUT Browsing: UNIX SYSOUT not found, after SYSOUT Copy to BS2000. GUI OK.
NOPALL-4006 | Finish editing JCL with SAVE will not save last change
NOPALL-3998 | Follow-up of itrac NOPALL-3966: Blockade Situation with Resources
NOPALL-3981 | Cyclic job: JCL load behavior, load mode 'S'
NOPALL-4020 | SYSOUT Browsing Issues with UTF-8 characters
NOPALL-4026 | No Event, when 'File in Use' message is issued for SYSOUT copy to BS2000
NOPALL-4028 | NAT-Error in symbol function in input condition check causes emergency Monitor shutdown[or abend
NOPALL-3991 | When calling a subnet with more than 5 levels, the subnet is not 'terminated'
NOPALL-3971 | Logon Prompt to Linux Node with unresolved Symbol in User ID
NOPALL-3978 | OGC: Deleting an active input condition: EOR0070 - No Objects found for Selection Criteria
NOPALL-3977 | Import/Export several runtime errors
NOPALL-3972 | Batch Cataloging of MACROs on UNIX - MAC-GE-P - EOR4000 - Editor Error: UPDM 504 Session does not exist
NOPALL-3982 | End-of-job action - Set symbol - Length > 80
NOPALL-3984 | NOP on Linux: SAG Editor of active JCL duplicates or triples last line after editing
NOPALL-3976 | MACRO JCL Loading: Logon to Execution Node (an ESA node): NPR5510
NOPALL-3993 | Error in Symbol Function TIMN
NOPALL-3983 | Export Network Defintion HIST-DAY= is displayed with 1 day delay (Tag Versatz) gespeichert
NOPALL-4000 | NPROS node disappears from system without error messages - NOP Part
NOPALL-3994 | Usage of Symbol Function ?W with Recursive Symbol Resolution
NOPALL-3986 | NAT Member as EOJ Exit - Library SYSEORU has precedence before user-defined library
NOPALL-4007 | Import function refuses EOJ-Action with Symbol length > 20
NOPALL-4001 | NOP 5.5.2.8 + Fix31-35: Logon error leaked into other job
NOPALL-3989 | File existence check with symbols, that are created during the network run
NOPALL-4025 | No short Text with EOJ Action 'Symbol Setting', if Symbol missing

### Entire Operations (NOP) Version 5.5.2 Cumulative Fix 8

Problem | Short Description
--- | ---
NOPALL-3947 | User in OGC has Access to Active Jobs w/o Access Rights in NOP (N
NOPALL-3949 | BS2000 Job Variable Checking via ESA: Monitor Task Usage is too high
NOPALL-3955 | File Existence Check with wildcard: Error message instead of defined action
NOPALL-3875 | OGC - NAT0104 error during TEST or MACRO function of a MACRO
NOPALL-3961 | Recursive Symbol Resolution in Input Conditions
NOPALL-3963 | File Existence Check with long Pathname ignored
NOPALL-3959 | Multiple symbol values are cut to 54 characters by symbol function MV (multiple value)
NOPALL-3917 | BS2000 via ESA: EOJ Checking, Input Condition depending on Job Variable: Handling of 'Node not active'
NOPALL-3953 | Import - Status 'aborted' import despite success
NOPALL-3860 | Error with Monitor Defaults / Monitor UserId
NOPALL-3967 | Node level user id is not honored as Submit User ID in the search hierarchy
NOPALL-3965 | Node as a Symbol - Evaluation Error
NOPALL-3905 | Remove OPO from NOP - CUI and Monitor
NOPALL-3966 | Blockade Situation with Resources
NOPALL-3936 | Input Condition Type DUM with Symbol Value not honored
NOPALL-3858 | EOR2030 Monitor-Fehler NAT0082 in . Zeile 0
NOPALL-3923 | NAT1305 in RN-TI--N line 2995
NOPALL-3930 | OPJACJ-N: Typo Correction
NOPALL-3929 | Error NAT1305 in IENMX1-N line 1340
NOPALL-3932 | Error NAT0938 in DI-DF--N line 380 with HotFix OP55218 / NOPALL-3820

### Entire Operations (NOP) Version 5.5.2 Cumulative Fix 7

Problem | Short Description
--- | ---
NOPALL-3892 | Email notification: Error message not displayed correctly
NOPALL-3895 | Condition with reference DUM - subsequent condition depending on BS2000 file is not evaluated - postrequisite for NOPALL-3882
NOPALL-3868 | NOP on UNIX: SAG Editor randomly displays wrong characters in BS2000 SYSOUT
NOPALL-3893 | EOJ check, string check in file, job start escape character in fields 'String' and 'in File'
NOPALL-3897 | No "Ended not OK" if SYSOUT limit reached and default setting 'Interrupt End-of-Job Checking on BS2000' = B
NOPALL-3886 | "?*TIMN" built-in symbol: leading zeroes missing before 10:00
NOPALL-3865 | Number of Active Jobs > 100
NOPALL-3850 | API NOPUNX1N - Add F-LINE-LIMIT in parameter area NOPUNX1A
NOPALL-3913 | Symbol Resolution in File Existence Checks not at Activation Time
NOPALL-3914 | Input Condition: File Existence Check Fails because of Error: Condition fulfilled
NOPALL-3827 | UNIX script frame - Don't use realpath command, where it is not available
NOPALL-3829 | OGC Server - Report 'Activation Overview' Message data is not language dependent
NOPALL-3826 | Report RE-ACO-P - Usage improvements due to performance issues
NOPALL-3828 | Two entries are generated per activation - one with Type: API and one with Type: Planned - NOP 543 CF21
NOPALL-3832 | Additional network execution day displayed at the turn of the year
NOPALL-3857 | OGC/ESA - ESY5799 at BS2000 LMS Member Selection
NOPALL-3835 | NOP on UNIX: API NOPUMT3N does not find SYSERR messages for library SYSEOR - ESY5999 TCP:socket:24:Too many open files
NOPALL-3842 | OGC Server ? NAT1316 if too many filters exist for one user
NOPALL-3848 | CUI: User Definition and Profile / Selection Criteria: Enable modification for General Users
NOPALL-3855 | NAT1316 in OPJAOP-N Line 4946
NOPALL-3839 | Symbol Function D: Error Handling for missing Calendar
NOPALL-3854 | Node Default User IDs - Differences between NOP and OGC
NOPALL-3861 | NAT1305 in ICDJV--N Line 3440
NOPALL-3820 | Linux: Job result not-ok although it ran with return code 0, if 'command not found' detected in SYSOUT
NOPALL-3870 | Transfer to NOM even if EOJ action has been removed in active Job
NOPALL-3869 | Job type DAT: When transferring files with NPR, characters are swallowed
NOPALL-3878 | API NOPURE2N doesn't block Resource across Network
NOPALL-3884 | Input condition reference DUM - File existence check without rights: job is started
NOPALL-3890 | Faulty re-activation, if latest start time exceeded
NOPALL-3880 | Error in EOJ Definition and Execution, if Symbol Value is longer than 80 Characters
NOPALL-3862 | Inheritance of Parameter Values from Network to JOB: BS2000 Account Number
NOPALL-3885 | OGC: Job type DAT: Changing the target file in the active run not possible
NOPALL-3891 | OGC/ESA - ESY5799 at BS2000 LMS Member Selection - NOP RPC Server Correction

### Entire Operations (NOP) Version 5.5.2 Cumulative Fix 6

Problem | Short Description
--- | ---
NOPALL-3761 | OGC: EOR0240 at JCL location modification from TXT to NAT
NOPALL-3773 | OGC-Server: Incomplete error message text for NAT0104
NOPALL-3779 | NOP543 CF20: RE-ACO-P causing performance issue - more logging for a
NOPALL-3785 | Usage of symbol functions ?D and ?W
NOPALL-3788 | BS2000: SYSOUT Selection only shows last Repetition (Current JobId)
NOPALL-3790 | NOP 552 CF6 several corrections
NOPALL-3801 | Export: EXECUTION-NODE Node Number vs. Short Name
NOPALL-3803 | EOR2030 - Monitor Error NAT3009 in PWT----P Line 3430
NOPALL-3804 | Set NOP Job to DUM using symbols in input condition doesn't work in
NOPALL-3809 | Job definition: Symbol replacement in SYSOUT user ID
NOPALL-3821 | OGC - after JCL regeneration and release from hold: job starts witho

### Entire Operations (NOP) Version 5.5.2 Cumulative Fix 5

Problem | Short Description
--- | ---
NOPALL-3427 | Validate expiration date in license key at session start
NOPALL-3766 | SYSEOR7065 and SYSEOR7254 are not included in NOP552 CF3
NOPALL-3767 | Log status 7528: Symbol not found - Follow-up for NOPALL-3754 and N
NOPALL-3768 | Error paging on ActiveQueue - PF7 and PF8
NOPALL-3770 | JA-SCS-P Line 1940 Error NAT3009
NOPALL-3772 | API NOPUCS1N Function=2, Object Type=S -> RC 103
NOPALL-3786 | NAT0966 in RSM-US-N Line 9750
NOPALL-3789 | Doc: Input condition reference AAC, Corrections + reference YYYYMMDD

### Entire Operations (NOP) Version 5.5.2 Cumulative Fix 4

Problem | Short Description
--- | ---
NOPALL-3713 | Provide exact number of runs on CUI Active Queue
NOPALL-3718 | E-Mail notification about network waiting for symbol prompting - Pos
NOPALL-3721 | Monitor Error NAT3041 in NOPSYMVN Line 1370
NOPALL-3725 | z/OS: No node logon possible to "technical" RACF userid without pass
NOPALL-3728 | Unexpected error message 'ICDMS--N 5160 - #EOR-ERC: 70' by using Inp
NOPALL-3732 | CUI: z/OS RACF Security Error Handling for JCL Definition
NOPALL-3734 | EOR Import fails with error NAT1319
NOPALL-3738 | NOP 5.5.2.3 export file cannot be imported to same version
NOPALL-3739 | A network activated in the OGC does not appear in the Activation Sum
NOPALL-3740 | NOP 543 CF19: Missing objects during Export with IE-EXA-P
NOPALL-3742 | NOP EOJ Action "T" ends with NPR FILE/COPY Error
NOPALL-3745 | OGC: Using nodes in cross-references
NOPALL-3747 | Powershell exit code not carried through
NOPALL-3749 | Monitor should not be started from MENUEOR in Batch Mode
NOPALL-3754 | Input Condition depending on Symbol: If symbol missing, always wait
NOPALL-3755 | New julian date formats in symbol function 'D'

### Entire Operations (NOP) Version 5.5.2 Cumulative Fix 3

Problem | Short Description
--- | ---
NOPALL-3161 | API NOPUAC5N - add latest start time (in hours) parameter
NOPALL-3656 | NOPUNX1N Password only A16; no enciphered password possible
NOPALL-3658 | Server functionality to serve GoJS coordinates
NOPALL-3659 | BS2000 Submit: Long lines will be cut at column 80
NOPALL-3667 | EOR5509 - Logon fehlerhaft, Kn. 1070 User ID SB - in job execution t
NOPALL-3670 | CUI Calendar list: Wrong behaviour in filtering owners
NOPALL-3674 | NOP Logfile (SATLOG) grows after migration NOP 5.4.3 CF14 to 5.5.2 C
NOPALL-3678 | z/OS: No node logon possible to "technical" RACF userid without pass
NOPALL-3679 | Error by using empty symbol tables by activating a network - Follow-
NOPALL-3685 | Unnecessary continuation lines when starting a job in BS2000 from NO
NOPALL-3691 | More than 100 symbol tables in active Network
NOPALL-3693 | OGC (Server): Edit of active JCL fails with more than 100 Lines
NOPALL-3697 | Report RE-ACO-P: Performance in Batch Mode
NOPALL-3699 | Input Condition depending on Symbol: No Log Message, if Symbol is mi
NOPALL-3700 | Incomplete SYSOUT transfer from Linux to BS2000
NOPALL-3702 | Pre-filled Values For Escape Characters In Job Definition
NOPALL-3704 | NAT program defined as EOJ action is executed at network activation
NOPALL-3706 | OGC + CUI - EOR1070 - Networks can't be deleted

### Entire Operations (NOP) Version 5.5.2 Cumulative Fix 2

Problem | Short Description
--- | ---
NOPALL-3341 | OGC Import / Export e-mail messages: Correction of header and conten
NOPALL-3385 | CE: Next scheduled network starts: Deactivate all active Networks in
NOPALL-3478 | Temporary elements in library SYSEORU not deleted
NOPALL-3486 | Additional network execution displayed at the turn of the year
NOPALL-3515 | Performance: Check necessity of Node Logon before Linux Job executio
NOPALL-3563 | OGC - Export Summary missing
NOPALL-3564 | Pre-generated JCL overwritten, if a network has several versions
NOPALL-3619 | NOP 552 CF2 several corrections
NOPALL-3623 | NOP does not replace variable for Email for network
NOPALL-3624 | Utility to list jobs with empty or invalid JCL userid or submit user
NOPALL-3634 | Suspension functionality: Post-corrections
NOPALL-3635 | z/VSE Corrections
NOPALL-3636 | EXPORT ALL Parameter for IE-EXA-P need to be corrected
NOPALL-3638 | Monitor Error NAT0966 in SYSEOR/EJC----P Line 6774
NOPALL-3639 | EOR2030 - Monitor Error NAT1305 in RSM-US-N Line 8200
NOPALL-3641 | Some adaptations for the ESM Adapter (BS2000)
NOPALL-3647 | Unnecessary logon requests with "Submit Security User Type" = Owner
NOPALL-3648 | Definition of a job suffix symbol for dynamic use
NOPALL-3649 | NOPUT1-P: API NOPUSY7N invocation: Multiple symbol reading with 'N'
NOPALL-3651 | Browsing BS2000 SYSOUT from NOP on UNIX fails with 'SO-XB--P 1500 -
NOPALL-3653 | Pgm SYSEOR/CL-JA--N Line 2990 Error NAT1257/0000

### Entire Operations (NOP) Version 5.5.2 Cumulative Fix 1

Problem | Short Description
--- | ---
NOPALL-2986 | Loading JCL fails due to Invalid UserID
NOPALL-3481 | Active condition list: Show modification date + time, instead of act
NOPALL-3561 | Import v551/4 rejects jobs (migrated from v543) dependent on symbol
NOPALL-3567 | NOP 552 CF1 several corrections
NOPALL-3569 | BS2000 openFT Usage - Continuation
NOPALL-3571 | Symbol table missing when Network export is executed via batch job
NOPALL-3575 | Network Export from Owner SYSTEM impossible
NOPALL-3576 | Active Job - SYSOUT Browsing (CUI) - File name in header incorrect,
NOPALL-3590 | The "Day Deadline" is not observed
NOPALL-3591 | EOR2030 - Monitor Error NAT3009 in SYSEOR/IRREL--N Line 2455
NOPALL-3597 | CUI: Change Monitor Node: NAT3144 in DF-MO--P line 5160
NOPALL-3602 | Unexpected 'Logon failed' global message during job execution tracki
NOPALL-3603 | EOJ Action "Set Symbols Y" not imported correctly

### Entire Operations GUI Client (OGC) Version 5.5.3 Cumulative Fix 02

Problem | Short Description
--- | ---
NOPALL-4268 | Make 'SYSOUT Line Limit' Owner Dependent
NOPALL-4310 | OGC - OGC to cater for Send to SYSOUT Store flag
NOPALL-4201 | Wrong message for "Where used" in: Waiting for prerequisites
NOPALL-4274 | OGC - Monitor Status Window - Status text truncated
NOPALL-4277 OGC | Network Master / Define Scheduling - Day deadline not modified
NOPALL-4309 | Job Master/EOJ Checking: OPCMPNIS 1130 NAT1322

### Entire Operations GUI Client (OGC) Version 5.5.3 Cumulative Fix 01

Problem | Short Description
--- | ---
NOPALL-4265 | OGC Part for NOPALL-4226: Utility or API requested to delete remaining active conditions of de-activated runs. See new field `Network deactivation: with active conditions`in Defaults for Other Settings in the Admin documentation.
NOPALL-4239 | OGC - "Symbol instance" of a JM Input Condition missing
NOPALL-4222 | OGC: Add some fields for 'EOR Defaults' Search symbols also in other symbol tables of active network Show installed ESM Products Maximum SYSOUT Size (in MB) SYSOUT Store Node

### Entire Operations GUI Client (OGC) Version 5.5.2 Cumulative Fix 12

Problem | Short Description
--- | ---
NOPALL-4115 | OGC: Error when displaying an active symbol table - NAT6971 Connection error on Client, reason 09
NOPALL-4166 | Report 'Network Description (detailed)' incorrect depending on the impact or release cycle Completed
NOPALL-4167 | OGC- Crash ESM-GUI (Natural 9.2.1.0 & Natural 9.1.1.0)
NOPALL-4191 | OGC - Disable z/VSE in GUI
NOPALL-4200 | OGC - Waiting for Job Active: EOR9998 - EOR internal error has occurred.
NOPALL-4204 | OGC - Display Accounting for Job with more then 1000 runs

### Entire Operations GUI Client (OGC) Version 5.5.2 Cumulative Fix 11

Problem | Short Description
--- | ---
NOPALL-4101 | OGC- Network Master with more than 999 lines "Long Description" => NAT1305
NOPALL-4126 | OGC - New 'effective to' attribute in the Network Schedule Definition

### Entire Operations GUI Client (OGC) Version 5.5.2 Cumulative Fix 10

Problem | Short Description
--- | ---
NOPALL-4067 | OGC 5.5.2.9 - Error NAT1316 in Node List Display
NOPALL-4008 | BS2000 LMS Member Name in Job List of Network only 8 Characters

### Entire Operations GUI Client (OGC) Version 5.5.2 Cumulative Fix 9

Problem | Short Description
--- | ---
NOPALL-4027 | OGC and NOW: Waiting for: Actions for active Input Conditions depending on anything are not grayed out
NOPALL-3978 | OGC: Deleting an active input condition: EOR0070 - No Objects found for Selection Criteria
NOPALL-3830 | OGC - WorldView shrinks when expanding the network view
NOPALL-3819 | OGC - wrong job sequence in network plan at actualization

### Entire Operations GUI Client (OGC) Version 5.5.2 Cumulative Fix 8

Problem | Short Description
--- | ---
NOPALL-3950 | OGC: Active Jobs Filter: Not Accessible Owners offered
NOPALL-3948 | OGC - Reactivate not grey despite there is no right to do so
NOPALL-3943 | Remove OPO from OGC and NOW
NOPALL-3922 | Remove Job Type SAP (JEXA4S) from OGC and NOW
NOPALL-3920 | User in OGC has Access to Active Jobs w/o Access Rights in NOP

### Entire Operations GUI Client (OGC) Version 5.5.2 Cumulative Fix 7

Problem | Short Description
--- | ---
NOPALL-3885 | OGC: Job type DAT: Changing the target file in the active run not possible
NOPALL-3867 | OGC Report - Detailed Network Report is incomplete
NOPALL-3855 | NAT1316 in OPJAOP-N Line 4946
NOPALL-3854 | Node Default User IDs - Differences between NOP and OGC
NOPALL-3846 | OGC - NSC - Browse Sysout failed with certain passwords
NOPALL-3842 | OGC Server – NAT1316 if too many filters exist for one user
NOPALL-3829 | OGC Server - Report 'Activation Overview' Message not language dependent
NOPALL-3828 | Two entries are generated per activation - one with Type
NOPALL-3822 | OGC - Performance with huge networks in network plan

### Entire Operations GUI Client (OGC) Version 5.5.2 Cumulative Fix 6

Problem | Short Description
--- | ---
NOPALL-3818 | OGC - object name comfirmation at job re-submit mandatory?
NOPALL-3793 | OGC: The network version is displayed incorrectly
NOPALL-3730 | Provide exact number of runs on CUI Active Queue - OGC and NOW adaptations and testing

### Entire Operations GUI Client (OGC) Version 5.5.2 Cumulative Fix 5

Problem | Short Description
--- | ---
NOPALL-3765 | OGC: Report CNV delivers wrong values

### Entire Operations GUI Client (OGC) Version 5.5.2 Cumulative Fix 4

Problem | Short Description
--- | ---
NOPALL-3745 | OGC: Using nodes in cross-references

### Entire Operations GUI Client (OGC) Version 5.5.2 Cumulative Fix 3

Problem | Short Description
--- | ---
NOPALL-3692 | OGC: It is not possible to repeat an Import because the Repeat button is inactive

### Entire Operations GUI Client (OGC) Version 5.5.2 Cumulative Fix 2

Problem | Short Description
--- | ---
NOPALL-3637 | OGC – Resubmit Job-Active: <Yes to All> requested
NOPALL-3622 | OGC: Browse - Edit error in Diagram mode

## Previous Release Notes

Here are links to PDF files of the release notes for prior versions of Entire Operations. They are provided for users who may be upgrading from an earlier version of Entire Operations other than the most recent.

- Entire Operations Version 5.5.2

- Entire Operations Version 5.5.1

### On this page

- General System Updates
- Entire Operations Documentation Updates
- Supported Operating Systems
- Supported Browsers
- Prerequisites for the Mainframe
- Prerequisites for UNIX/Linux
- Prerequisites for Windows GUI Client
- Special Considerations
- Platforms and Required Middleware
- Compatibility and Migration
- Code Page Setting
- Solved Issues
- Previous Release Notes