Entire System Server 3.4.1 Release Notes

#### Search Results

Search

# Entire System Server 3.4.1 Release Notes

For further information, you should also read the Entire System Server 3.3.2 Release Notes, which are delivered with Version 3.4.1 on the current Natural Documentation CD-ROM and in printed form. References contained in the Version 3.3.2 Release Notes generally refer to the corresponding Version 3.3.2 manuals, which are included in the Version 3.4.1 documentation.

These Release Notes provide an overview of solved problems provided for Entire System Server Version 3.4.1.

This document covers the following topics:

- Support of Previous Versions

- Prerequisites

- New Features

- Enhancements

- Solved SAGSIS Problems

- Migration Checklists

- Changes with the Next Version

## Support of Previous Versions

For information on how long a product is supported by Software AG, log in to Empower and select "Product Version Availability".

## Prerequisites

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

- Natural Version 4.2.2 or above;

- Adabas Version 7.4.4 or above;

- Entire System Server Interface (provided with Natural);

- Entire Net-Work Version 5.9.1 (optional, for multi-CPU Support);

- Natural ISPF Version 2.5.4 or above (optional)

- Predict Version 4.5.1 or above (optional).

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

- z/OS Version 1.6 or above;

- z/VSE Version 3.1 or above;

- BS2000/OSD Version 5 or above.

### Notes:

In a z/OS environment, Zap XC71001 must be applied to Entire System Server, if Dual Data Set Command Logging is to be used.

For z/OS, the relevant PTFs for APARs OA10472 and OA17274 must be applied.

For z/OS JES2, the PTFs for APARs OA06694 and OA11039 must be applied.

For z/OS JES3, the PTFs for APARs OA16284, OA19893 and OA20685 must be applied.

See also Information APAR II11784 for recommended JES3 SAPI maintenance.

Software AG 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 AG cannot continue to support operating system versions that are no longer supported by the system's provider.

## New Features

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

- Common New Features

- New Features for z/OS

- New Features for BS2000/OSD

### Common New Features

#### Enhancements to SEND-EMAIL

With the SEND-EMAIL view now also BCC-RECIPIENT addresses can be specified.

To send a text file as an e-mail attachment, a DSNAME and optionally a MEMBER or ELEMENT name can be specified with the first PROCESS statement for a SEND-EMAIL command sequence.

For the details of these enhancements, see View Descriptions, SEND-EMAIL, in the User's Guide.

### New Features for z/OS

#### Support for Dual Data Set Command Logging

To handle an out-of-space condition with a CLOG data set, command logging was enhanced to handle two data sets (CLOGR1 and CLOGR2) which will be used alternating. If only one CLOG data set is used, command logging will be disabled when the data set is full.

#### Command Authorizations Now Checked in the CONSOLE View Processor

Command authorization checking was enhanced to determine the proper resource name and required access authority in the OPERCMDS class for the system command to be issued. Checking is now done in a subroutine of the CONSOLE view processor, and the OPRVRACF security exit is only to be used for additional checks to be implemented by the customer.

#### Support for Review in Local Mode

The command logging function has been enhanced to also provide Adabas command data to Review in local mode. A new startup parameter REVIEW has been introduced to control if command log records are to be passed to Review. For details, see the sections Startup Parameters and z/OS Considerations, Using Review with Entire System Server in the Administration Guide.

#### SVC Screening Eliminated

SVC screening had been used in previous releases of Entire System Server for z/OS to intercept some SVCs issued in the Entire System Server address space in order to propagate a security environment to subtasks. By changing the IDCAMS and SYSTEM-COMMAND view processors the need to manipulate those SVCs has been eliminated.

#### SYSTEM-COMMAND View Processor Rewritten

The implementation of the SYSTEM-COMMAND view processor in previous releases of the Entire System Server had some security and APF authorization issues. These issues have been resolved by redesigning the view processor to schedule the TSO/E commands to be issued to an APPC/MVS transaction outside the Entire System Server address space.

Three new startup parameters (APPC-TPNAME, APPC-LUNAME and APPC-MODENAME) have been introduced to define the APPC/MVS transaction. In addition, resources need to be defined for APPC/MVS, TSO/E and VTAM. For details, see the sections Startup Parameters and z/OS Considerations, APPC/MVS Definitions for the SYSTEM-COMMAND View in the Administration Guide.

#### Support for SMF Log Stream Recording (z/OS 1.9)

With z/OS 1.9, customers may choose to have SMF record accounting data either to VSAM data sets (SYS.MANx) or to z/OS log streams. The ACCOUNTING view processor has been changed to determine where the SMF data is recorded and eventually to read the data from an SMF log stream.

#### ESY Single-User Mode

ESY single-user mode is now available in batch mode and under TSO.

### New Features for BS2000/OSD

#### Support for Encrypted Passwords

Support has been added to the SUBMIT view for BS2000/OSD to be used on systems with encrypted passwords.

#### Continuation of Parameters in NPR3xx.PARM

All Entire System Server tasks can now be started by an SDF-P procedure. Additional operands to adjust /ENTER-PROCEDURE are supplied by new entries in the parameter file. Each /ENTER-PROCEDURE operand is represented by a separate parameter. There is no need for multi line parameter values anymore.

#### ERROR Message if SPOOL Not Active

Entire System Server will issue an error message if the Spool subsystem is not active at startup time. It will come up with setting SPOOL=NONE.

#### New, Changed and Deleted Fields

The following table summarizes the fields that have been added, changed or deleted. For details regarding the affected fields, see the associated view descriptions in the User's Guide.

View | Field | Change
--- | --- | ---
CONSOLE | DESCR-CODE-STRING | New, A16
| HOLD-FLAG | New, A1
| ROUTE-CODE-STRING | New, A28
| TIME-STAMP-LONG | New, A11
CONSOLE-LOG | LOG-TIME-LONG | New, A11
SEND-EMAIL | BCC-RECIPIENT | New, A128
| DSNAME | New, A54
| ELEMENT | New, A64
| MEMBER | New, A10
| PASSWORD | New, A8
| ELEMENT-PASSWORD | New, A8
| ELEMENT-TYPE | New, A8
| MEMBER-TYPE | New, A8
| ELEMENT-VERSION | New, A24
| VOLSER | New, A6
| LIBRARY | New, A8
| SUB-LIBRARY | New, A8
SYSTEM-INFO | LOGON-ID | Now also valid for z/OS and z/VSE

## Enhancements

The following Enhancement Proposals have been implemented:

EP 325 | System command authorization checking in CONSOLE view (z/OS)
EP 1382 | Handle out-of-space condition for command log data set (z/OS)
EP 1564 | SEND-EMAIL with attachments
EP 1565 | Provide Blind Carbon Copy functionality for SEND-EMAIL
EP 2189 | Continuation of Parameters in NPR322.PARM
EP 2192 | ERROR message if SPOOL is not active

## Solved SAGSIS Problems

This section describes SAGSIS problems reported for Entire System Server that have been solved since Version 3.3.2.

The following topics are covered:

- Solved SAGSIS Problems on z/OS

- Solved SAGSIS Problems on VSE/ESA and z/VSE

- Solved SAGSIS Problems on BS2000/OSD

### Solved SAGSIS Problems on z/OS

Problem | Short Description
--- | ---
284670 | ABEND S201
285439 | ESY5996 in NOP with archived Data
286061 | Abend S0C4-11 in XCOMV003+X'133A'
286307 | ADAM99 ADABAS Abend code 840C4
287296 | 0c7 in XCOMSSB after z/OS upgrade
289284 | Support for z/OS 1.9 JES2 & JES3
289908 | File Attribute wrong size value
290090 | IEA705I ERR DURING GETMAIN 80A-10
290516 | ABENDS0C4 in SVC when using Version 8
291102 | lib-update open error
291271 | abend 0C4 during init of ESY
291592 | Process Node abended U0253
293090 | Incorrect SYSOUT attribute field
293569 | abend S0C4 in XCOMV044+184A
294750 | ESY5777 after B37 messages

### Solved SAGSIS Problems on VSE/ESA and z/VSE

Problem | Short Description
--- | ---
271672 | submit without dsname and card
280639 | S0c4 ESYNMAIN +6B16 ADA8
287658 | copy-file returns wrong node
287728 | submit from dataset
288701 | Support z/VSE V4.1

### Solved SAGSIS Problems on BS2000/OSD

Problem | Short Description
--- | ---
293103 | Create Backupfiles abends
293751 | ESYMAIN loop after WCP abend
295187 | ESYMAIN does not respond

## Migration Checklists

The following check lists are provided to assist you in migration from NPR33x:

### z/OS

Startup Parameters:

- If you are using the SYSTEM-COMMAND view, you will need to specify three new startup parameters (APPC-TPNAME, APPC-LUNAME and APPC-MODENAME) to define the APPC/MVS transaction that will process the TSO/E commands. In addition, resources need to be defined for APPC/MVS, TSO/E and VTAM. For details, see the sections Startup Parameters and z/OS Considerations, APPC/MVS Definitions for the SYSTEM-COMMAND View in the Administration Guide.

- If you are going to use Adabas Review in Local Mode with Entire System Server, specify REVIEW=YES on your startup parameters. The parameter UEX4, which could be used in former releases of Entire System Server, is no longer supported.

JCL Procedure:

- If you are using command logging, you may want to define an alternate command log data set. To use dual data set recording for the command log, replace the CLOG DD statement with a CLOGR1 and a CLOGR2 DD statement in your JCL for Entire System Server.

- If you are going to use Adabas Review in Local Mode with Entire System Server, specify your Adabas Review load library in the STEPLIB concatenation for Entire System Server. Additional DD statements for data sets used by Adabas Review will be needed in your JCL. For details, see z/OS Considerations, Using Adabas Review with Entire System Server in the Administration Guide and the Adabas Review documentation.

### BS2000/OSD

Startup Parameters:

- If you want to use the delivered SDF-P P.ESY procedure to run the Entire System Server, please customize the values within the parameter declaration section of P.ESY and use the procedures P.ESYMAIN, P.ESYSTOP. P.ESYTRACE to start, stop, or trace the Entire System Server. There is a set of new startup parameters to adjust the properties of the ESY tasks. For further information, refer to the startup parameters SDF-P, JOB-CLASS, JOB-ELEM, JOB-LIB, JOB-NAME-CONS, JOB-NAME-EMAIL, JOB-NAME-EVENT, JOB-NAME-SERVER, JOB-RUN-PRIORITY, JOB-START-OPTION, JOB-TIME.

The IPV6 enabled version of program ESYMAIL (formerly named ESYMAIL6) is now renamed to ESYMAIL and the /ENTER procedure E.ESYMAIL6 is renamed to E.ESYMAIL. If you want to use the new startup procedure P.ESY and there is a need to run ESYMAIL4, please uncomment the following lines in P.ESY:

/&*IF (PGM = 'ESYMAIL') /&* PGM = 'ESYMAIL4' /&*END-IF

## Changes with the Next Version

Based on customer feedback, we will not remove the support to run Entire System Server in single-user mode as stated in the Release Notes for Entire System Server Version 3.3.1.

We plan to remove the support to change the DBID for Entire System Server DDMs using the installation aid (SYSNPR) in a future 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 Software AG Customer Support.

### On this page

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