Entire System Server 3.6.1 Release Notes

#### Search Results

Search

# Entire System Server 3.6.1 Release Notes

These Release Notes provide an overview on all changes for Entire System Server 3.6.1. The following topics are covered:

- Support of Previous Versions

- Prerequisites

- New Features and Enhancements

- Solved Problems

- Migration Checklists

- Changes with the Next Version

## Support of Previous Versions

For information on how long a product is supported by Software GmbH, access Software GmbH's customer support web site at https://empower.softwareag.com/Products/default.asp. This application allows you to retrieve support information for specific products and releases.

## Prerequisites

Before you can install Entire System Server, the following Software AG products must already be installed at your site:

- Natural Version 8.2.4 or above;

- Adabas Version 8.2.5 or above;

- Entire System Server Interface (provided with Natural);

- Entire Net-Work Version 6.3.1 or above (optional, for multi-CPU Support);

- Natural ISPF Version 8.2.4 or above (optional);

- Adabas Review Version 4.7.1 (optional);

- Predict Version 8.2.3 or above (optional).

Entire System Server Services are available in any Natural environment that runs any or a combination of the following operating systems:

- z/OS Version 1.13 or above;

- z/VSE Version 5.1 or above;

- BS2000 Version 8 or above.

#### Notes:

- For z/OS 2.1 and above, the relevant PTF for APAR OA48683 must be applied.

- For z/OS JES3, please refer to APAR II11784 for recommended JES3 SAPI maintenance.

- Software GmbH provides Entire System Server support for the operating system versions supported by their respective manufacturers. Generally, when an operating system provider stops supporting a version of an operating system, Software AG will stop supporting that operating system version.

- Although it may be technically possible to run a new version of Entire System Server on an old operating system, Software GmbH cannot continue to support operating system versions that are no longer supported by the system's provider.

## New Features and Enhancements

This section describes new Entire System Server Features. It covers the following topics:

- Common New Enhancements

- New Features for z/OS

- New Features for BS2000

- New, Changed and Deleted Fields

### Common New Enhancements

#### NPRMF-1129 New Operator Command XABS

The new operator command XABS provides a report on the usage of attached buffers which are displayed as a set of console messages.

### New Features for z/OS

#### EF-1824 Support PDSE Version 2 and Member Generations, Stage 2 (z/OS)

The DDMs for the views LIB-UPDATE, SUBMIT and WRITE-FILE now contain a GENERATION field to be used with PDSE version 2 libraries and member generation.

#### EF-1105 New Parameter OUTPUT MAILTO in WRITE-SPOOL View

The DDM for view WRITE-SPOOL now contains new fields to support the OUTPUT JCL parameters MAILBCC, MAILCC, MAILFROM, MAILTO, REPLYTO and TITLE.

### New Features for BS2000

#### EF-1857 BS2000 SECOS Co-owner Integration

A new startup mode has been implemented on BS2000. The parameter SERVER-PER-USER=YES instructs Entire System Server (NPR) to enter the ESYSERV job control with the user ID of the requesting user. Refer to

- chapter How to Start/End Entire System Server on BS2000, section Server-per-User Mode

- chapter BS2000 Security Considerations, section Server-per-User Mode

- Startup Parameter SERVER-PER-USER

Currently, this parameter cannot be used when running EOM (Entire Output Management) and EOR (Entire Operations).

#### EF-1898 Support LMS Typ L

LLMs can be read with view READ-FILE now.

### New, Changed and Deleted Fields

The following table summarizes fields that have been added, changed or deleted in an existing view. Please refer to the respective view in View Descriptions in the User's Guide documentation.

View | Field | Change
--- | --- | ---
LIB-UPDATE | GENERATION | New for z/OS, N9
SUBMIT | GENERATION | New for z/OS, N9
WRITE-FILE | GENERATION | New for z/OS, N9
WRITE-SPOOL | MAILTO | New for z/OS, A60
| MAILCC | New for z/OS, A60
| MAILBCC | New for z/OS, A60
| MAILFROM | New for z/OS, A60
| REPLYTO | New for z/OS, A60
| TITLE | New for z/OS, A60

## Solved Problems

This section describes solved problems for Entire System Server 3.6.1.

- Solved Problems for z/OS

- Solved Problems for z/VSE

- Solved Problems for BS2000

### Solved Problems for z/OS

Problem | Short Description
--- | ---
NPRMF-1116 | Support for z/OS 2.2 JES2 and JES3.
NPRMF-1130 | Support for IBM APAR OA46291.
NPRMF-1135 | Loop in XCOMJESC trying to read an IOT from JES2 spool.
NPRMF-1142 | FILE-ATTRIBUTES may incorrectly return a value of zero for NUMBER-OF-MEMBERS.

### Solved Problems for z/VSE

Problem | Short Description
--- | ---
NPRMF-1083 | NSPF823 / NPR352 for VSE: Time missing in SYSLOG.

### Solved Problems for BS2000

n/a

## Migration Checklists

The following checklists are provided to assist you in migration from NPR35x:

- z/OS

- z/VSE

- BS2000

### z/OS

Startup Parameters:

- If you are using the SYSTEM-COMMAND view, please note that the default value for APPC TPNAME is now `SAG.NPR361.XCOMTP46`. If you are going to use this default value, the transaction program name needs also to be defined for APPC/MVS. For details, please refer to APPC/MVS Definitions for the SYSTEM-COMMAND View in the section z/OS Considerations, in the Administration Guide chapter.

- If you are using the READ-FILE view with the GENERATION parameter introduced with NPR354, please note that now error message `ESY5541 Member generation not found in directory.` is returned if the requested member generation is not found in the PDSE directory. The NPR354 version of READ-FILE used to return error message `ESY5998 MEMBER not found.` in this situation. Please adapt your applications accordingly.

JCL Procedure:

- Update the DD statement for LICENSE to reflect the new license key file for your processor(s).

### z/VSE

JCL Procedure:

- Update the DD statement for LICENSE to reflect the new license key file for your processor(s).

### BS2000

JCL Procedure:

- Update the ADD-FILE-LINK statement for LICENSE to reflect the new license key file for your processor(s).

## Changes with the Next Version

We plan to implement support for multi-level security in a future version of Entire System Server. This may require changes to customized versions of the current security exits. If you are using non-standard resource classes in your security exits, please communicate your requirements to Customer Support.

### On this page

- Support of Previous Versions
- Prerequisites
- New Features and Enhancements
- Solved Problems
- Migration Checklists
- Changes with the Next Version