release notes - overview - software ag · 2014. 6. 13. · console descr-code-string new,a16...

Entire System Server

Release Notes - Overview

Version 3.4.2

December 2009

This document applies to Entire System Server Version 3.4.2.

Specifications contained herein are subject to change and these changes will be reported in subsequent release notes or new editions.

Copyright © 1987-2009 Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, United States of America,and/or their licensors.

The name SoftwareAG,webMethods and all SoftwareAGproduct names are either trademarks or registered trademarks of SoftwareAGand/or Software AG USA, Inc. and/or their licensors. Other company and product names mentioned herein may be trademarks oftheir respective owners.

Use of this software is subject to adherence to Software AG's licensing conditions and terms. These terms are part of the product doc-umentation, located at http://documentation.softwareag.com/legal/ and/or in the root installation directory of the licensed product(s).

This softwaremay include portions of third-party products. For third-party copyright notices and license terms, please refer to "LicenseTexts, Copyright Notices and Disclaimers of Third-Party Products". This document is part of the product documentation, located athttp://documentation.softwareag.com/legal/ and/or in the root installation directory of the licensed product(s).

Table of Contents

1 Release Notes - Overview ............................................................................................... 12 Entire System Server 3.4.2 Release Notes ........................................................................ 3

Support of Previous Versions .................................................................................... 4Prerequisites ............................................................................................................... 4Enhancements ............................................................................................................ 4Solved SAGSIS Problems ........................................................................................... 5Changes with the Next Version ................................................................................. 7

3 Entire System Server 3.4.1 Release Notes ........................................................................ 9Support of Previous Versions ................................................................................... 10Prerequisites ............................................................................................................. 10New Features ........................................................................................................... 11Enhancements .......................................................................................................... 14Solved SAGSIS Problems ......................................................................................... 14Migration Checklists ................................................................................................ 16Changes with the Next Version ................................................................................ 17

4 Entire System Server 3.3.2 Release Notes ...................................................................... 19Support of Previous Versions ................................................................................... 20Solved SAGSIS Problems ......................................................................................... 20Changes with the Next Version ................................................................................ 22

5 Entire System Server 3.3.1 Release Notes ...................................................................... 25Support of Previous Versions ................................................................................... 26Prerequisites ............................................................................................................. 26New Features ........................................................................................................... 27Migration Checklists ................................................................................................ 29Changes with the Next Version ................................................................................ 31

6 Entire System Server 3.2.2 Release Notes ...................................................................... 33Support of Previous Versions ................................................................................... 34Restrictions ............................................................................................................... 34Prerequisites ............................................................................................................. 34Solved SAGSIS Problems ......................................................................................... 35Changes with the Next Version ................................................................................ 38

7 Entire System Server 3.2.1 Release Notes ...................................................................... 39Support of Previous Versions ................................................................................... 40Prerequisites ............................................................................................................. 40New Features ........................................................................................................... 41Changes / Enhancements ......................................................................................... 50Solved SAGSIS Problems ......................................................................................... 50Migration Checklists ................................................................................................ 53Discontinued Support .............................................................................................. 56Changes with the Next Version ................................................................................ 56

8 Entire System Server 3.1.2 Release Notes ...................................................................... 57Support of Previous Versions ................................................................................... 58Prerequisites ............................................................................................................. 58

iii

Solved SAGSIS Problems on z/OS and OS/390 ........................................................ 59Solved SAGSIS Problems on VSE/ESA .................................................................... 63Solved SAGSIS Problems on BS2000/OSD ............................................................... 64Changes with the Next Version ................................................................................ 64

9 Entire System Server 3.1.1 Release Notes ...................................................................... 67Support of Previous Versions ................................................................................... 68Prerequisites ............................................................................................................. 68Restrictions ............................................................................................................... 69New Features ........................................................................................................... 69Changes/Enhancements ........................................................................................... 76Solved SAGSIS Problems ......................................................................................... 78Cancelled Support .................................................................................................... 79

10 Entire System Server 2.2.2 Release Notes .................................................................... 81Support of Previous Versions ................................................................................... 82Prerequisites ............................................................................................................. 82Solved SAGSIS Problems on OS/390 ........................................................................ 83Solved SAGSIS Problems on VSE/ESA .................................................................... 85Solved SAGSIS Problems on BS2000/OSD ............................................................... 85

11 Entire System Server 2.2.1 Release Notes .................................................................... 87Support of Previous Versions ................................................................................... 88Prerequisites ............................................................................................................. 88New Features ........................................................................................................... 89OS/390 Operating System ........................................................................................ 90BS2000/OSD Operating System ................................................................................ 90Installation Guidelines for ESX 2.3.1 ........................................................................ 91Changes / Enhancements ......................................................................................... 93Solved SAGSIS Problems ......................................................................................... 94

Release Notes - Overviewiv

Release Notes - Overview

1 Release Notes - Overview

Besides the Entire System Server Version 3.4.2 Release Notes, this page contains an overview ofearlier Release Notes which are relevant for customers whowant to migrate from an earlier EntireSystem Server version to Version 3.4.2.

Entire System Server 3.4.2 Release Notes




For background information, further Release Notes of earlier Entire System Server versions areavailable on the current Natural Documentation CD-ROM in the folder Archive.

1

2 Entire System Server 3.4.2 Release Notes■ Support of Previous Versions .............................................................................................................. 4■ Prerequisites .................................................................................................................................... 4■ Enhancements ................................................................................................................................. 4■ Solved SAGSIS Problems ................................................................................................................... 5■ Changes with the Next Version ............................................................................................................ 7

3

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

These Release Notes provide an overview of solved problems provided for Entire System Server3.4.2.

Support of Previous Versions

For information on how long a product is supported by SoftwareAG, see SoftwareAG's ServLine24web site at http://servline24.softwareag.com/public/. In the left menu of this site, expand "MyServLine24" and login to "Secured Services". Once you have logged in, you can expand Productsin the left menu of the web page and select “Product Roadmaps” to access the Product VersionRoadmaps application. This application allows you to request support information for specificproducts and releases.

Prerequisites

See the list of prerequisites given in the introductionary section in Installation and Customization.

Enhancements

The following Enhancement Proposals have been implemented:

Support more than 7 digits (9999999) used PAM pagesEP 4197

NPR332 field REGION in VIEW ACTIVE-JOBS only (N5)EP 5181

Release Notes - Overview4


http://servline24.softwareag.com/public/

Changed and new fields

The following table summarizes the fields that have been added or changed. Please see the associ-ated view descriptions in the “User's Guide” for details regarding the affected fields.

ChangeFieldView

Changed, N5 -> N7REGIONACTIVE-JOBS

Changed, N7 -> N10FILE-SIZECATALOG

Changed, N7 -> N10PRIMARY-ALLOCATIONFILE-ALLOCATE

Changed, N7 -> N10SECONDARY-ALLOCATION

New, A8DSNTYPEFILE-ATTRIBUTES

Changed, N7 -> N10FILE-SIZE

New, B4LAST-TTTR

New, N10PRIMARY-QTY

Changed, N7 -> N10SECONDARY-QTY

Changed, N7 -> N11MODULE-LENGTHLIB-DIRECTORY

Changed, N5 -> N7CONTIG-CYLINDERSUNIT-ATTRIBUTES

Changed, N5 -> N7FREE-CYLINDERS

Changed, N5 -> N7TOTAL-CYLINDERS

New, A8DSNTYPEVTOC

Changed, N7 -> N10FILE-SIZE

New, B4LAST-TTTR

New, N10PRIMARY-QTY

Changed, N7 -> N10SECONDARY-QTY

Note: These changes and additions are not included in the Predict Data for the viewdescrip-tions which still represents the NPR341 level. The changes and additions will be includedin the next regular release of NPR.

Solved SAGSIS Problems

This section describes solved SAGSIS problems for Entire System Server 3.4.2. SAGSIS is the in-ternal Software AG Support Information System where we track problem issues. The sectioncovers the following topics:

■ Solved SAGSIS Problems for z/OS■ Solved SAGSIS Problems for z/VSE

5Release Notes - Overview


■ Solved SAGSIS Problems on BS2000/OSD

Solved SAGSIS Problems for z/OS

Short DescriptionProblem

Console-Log FIND nnn PREV loops293993

GETMAIN error SYS CODE= 878-10298362

XCO0026E 00125 APPL stop error298525

"CEEPIPI ERROR1"298999

NATPROC-USERS Nat subtask missing299168

New function299596

system-command large output299847

COPY-FILE alias invalid ESY5554299930

IEBCOPY - wrong COMPLETION-CODE300320

Messages "ESY0563I $CBIO failed"300975

SMS CLASSES missing301054

NAT5690 :1: error :2: during :3301381

ABEND S0C4 in XCOMSFB offset 80301393

status command nom302777

abend 0C1 using console view303305

ADARSP 2510 during direct calls303505

Error ESY5846 for STATUS request303599

NPR332 field REGION in ACTIVE-JOB303985

NPR stops IEF238D305587

0C4 in XCOMV035 offset 2446305667

lib-directory scan with blanks305704

SYSTEM-COMMAND ATB80054I305916

IDCAMS: Message "IDC4999I"306353

print to VTAM hangs307320

ESY5710 - leading 0 missing308567

NewLine suppressed by IBM PDT308642

error-text contains garbage308881

LIB-DIRECTORY search lower case309016



Solved SAGSIS Problems for z/VSE


send-email VB attachment297987

Solved SAGSIS Problems on BS2000/OSD


Duplicate CSECT in ESYPROC297897

E.ESYSTOP hangs after long run298809

View File-Attributes LAST-TTR301704

SUBMIT returns JMS0028 to NOP301903

Abend 8C in Event task at ADAEND303496

Changes with the Next Version

We plan to implement support for multi-level security in z/OS with a future version of EntireSystem Server. This may require changes to customized versions of the current security exits. Ifyou are using non-standard resource classes in your security exits, please communicate your re-quirements to Software AG Customer Support.



3 Entire System Server 3.4.1 Release Notes■ Support of Previous Versions ............................................................................................................. 10■ Prerequisites .................................................................................................................................. 10■ New Features ................................................................................................................................. 11■ Enhancements ................................................................................................................................ 14■ Solved SAGSIS Problems ................................................................................................................. 14■ Migration Checklists ......................................................................................................................... 16■ Changes with the Next Version .......................................................................................................... 17

9


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


For information on how long a product is supported by SoftwareAG, see SoftwareAG's ServLine24web site at http://servline24.softwareag.com/public/. In the left menu of this site, expand MyServLine24 and login to Secured Services. Once you have logged in, you can expand Products inthe left menu of the web page and select Product Roadmaps to access the Product VersionRoadmaps application. This application allows you to request support information for specificproducts and releases.

Prerequisites

Before you can install the Entire System Server, the following Software AG products must alreadybe 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 acombination 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 SetCommand 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 supportedby their respectivemanufacturers. Generally, when an operating systemprovider stops supportinga version of an operating system, SoftwareAGwill stop supporting that operating system version.

Although it may be technically possible to run a new version of Entire System Server on an oldoperating system, Software AG cannot continue to support operating system versions that are nolonger 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 ELEMENTname 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 tohandle two data sets (CLOGR1 and CLOGR2) which will be used alternating. If only one CLOGdata 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 re-quired access authority in the OPERCMDS class for the system command to be issued. Checkingis now done in a subroutine of the CONSOLE view processor, and the OPRVRACF security exitis only to be used for additional checks to be implemented by the customer.

Support for Review in Local Mode

The command logging functionhas been enhanced to also provideAdabas commanddata toReviewin local mode. A new startup parameter REVIEW has been introduced to control if command logrecords are to be passed to Review. For details, see the sections Startup Parameters and z/OSConsiderations, Using Review with Entire System Server in the Administration Guide.

SVC Screening Eliminated

SVC screening had been used in previous releases of NPR for z/OS to intercept some SVCs issuedin the NPR address space in order to propagate a security environment to subtasks. By changingthe IDCAMS and SYSTEM-COMMAND view processors the need to manipulate those SVCs hasbeen eliminated.

SYSTEM-COMMAND View Processor Rewritten

The implementation of the SYSTEM-COMMANDviewprocessor in previous releases ofNPR hadsome security and APF authorization issues. These issues have been resolved by redesigning theviewprocessor to schedule the TSO/E commands to be issued to anAPPC/MVS transaction outsidethe NPR 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 bedefined for APPC/MVS, TSO/E and VTAM. For details, see the sections Startup Parameters andz/OS Considerations, APPC/MVSDefinitions for the SYSTEM-COMMANDView in the Adminis-tration 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 datasets (SYS.MANx) or to z/OS log streams. The ACCOUNTING view processor has been changedto determine where the SMF data is recorded and eventually to read the data from an SMF logstream.

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 SUBMITview for BS2000/OSD to be used on systemswith encryptedpasswords.

Continuation of Parameters in NPR3xx.PARM

All Entire System Server tasks can now be started by an SDF-P procedure. Additional operandsto 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 lineparameter values anymore.

ERROR Message if SPOOL Not Active

Entire System Server will issue an error message if the Spool subsystem is not active at startuptime. 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 detailsregarding the affected fields, see the associated view descriptions in the User's Guide.

ChangeFieldView

New, A16DESCR-CODE-STRINGCONSOLE

New, A1HOLD-FLAG

New, A28ROUTE-CODE-STRING

New, A11TIME-STAMP-LONG

New, A11LOG-TIME-LONGCONSOLE-LOG

New, A128BCC-RECIPIENTSEND-EMAIL

New, A54DSNAME



ChangeFieldView

New, A64ELEMENT

New, A10MEMBER

New, A8PASSWORD

New, A8ELEMENT-PASSWORD

New, A8ELEMENT-TYPE

New, A8MEMBER-TYPE

New, A24ELEMENT-VERSION

New, A6VOLSER

New, A8LIBRARY

New, A8SUB-LIBRARY

Now also valid for z/OS and z/VSELOGON-IDSYSTEM-INFO

Enhancements

The following Enhancement Proposals have been implemented:

System command authorization checking in CONSOLE view (z/OS)EP 325

Handle out-of-space condition for command log data set (z/OS)EP 1382

SEND-EMAIL with attachmentsEP 1564

Provide Blind Carbon Copy functionality for SEND-EMAILEP 1565

Continuation of Parameters in NPR322.PARMEP 2189

ERROR message if SPOOL is not activeEP 2192


This section describes SAGSIS problems reported for Entire System Server that have been solvedsince 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


ABEND S201284670

ESY5996 in NOP with archived Data285439

Abend S0C4-11 in XCOMV003+X'133A'286061

ADAM99 ADABAS Abend code 840C4286307

0c7 in XCOMSSB after z/OS upgrade287296

Support for z/OS 1.9 JES2 & JES3289284

File Attribute wrong size value289908

IEA705I ERR DURING GETMAIN 80A-10290090

ABENDS0C4 in SVC when using Version 8290516

lib-update open error291102

abend 0C4 during init of ESY291271

Process Node abended U0253291592

Incorrect SYSOUT attribute field293090

abend S0C4 in XCOMV044+184A293569

ESY5777 after B37 messages294750

Solved SAGSIS Problems on VSE/ESA and z/VSE


submit without dsname and card271672

S0c4 ESYNMAIN +6B16 ADA8280639

copy-file returns wrong node287658

submit from dataset287728

Support z/VSE V4.1288701



Create Backupfiles abends293103

ESYMAIN loop after WCP abend293751

ESYMAIN does not respond295187



Migration Checklists

The following checklists 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 startupparameters (APPC-TPNAME, APPC-LUNAME and APPC-MODENAME) to define the AP-PC/MVS transaction that will process the TSO/E commands. In addition, resources need to bedefined for APPC/MVS, TSO/E and VTAM. For details, see the sections Startup Parameters andz/OS Considerations, APPC/MVSDefinitions for the SYSTEM-COMMANDView in theAdmin-istration Guide.

■ If you are going to use Adabas Review in Local Mode with Entire System Server, specify RE-VIEW=YES on your startup parameters. The parameter UEX4, which could be used in formerreleases 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 aCLOGR1 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 yourAdabas Review load library in the STEPLIB concatenation for Entire System Server. AdditionalDD statements for data sets used by Adabas Reviewwill be needed in your JCL. For details, seez/OS Considerations, Using Adabas Review with Entire System Server in the AdministrationGuide 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, pleasecustomize the values within the parameter declaration section of P.ESY and use the proceduresP.ESYMAIN, P.ESYSTOP. P.ESYTRACE to start, stop, or trace the Entire System Server. Thereis a set of new startup parameters to adjust the properties of the ESY tasks. For further informa-tion, refer to the startupparameters 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 renamedto ESYMAIL and the /ENTER procedure E.ESYMAIL6 is renamed to E.ESYMAIL. If you want touse the new startup procedure P.ESY and there is a need to run ESYMAIL4, please uncommentthe following lines in P.ESY:

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


Based on customer feedback,wewill not remove the support to run Entire SystemServer 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 in-stallation 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 usingnon-standard resource classes in your security exits, please communicate your requirements toSoftware AG Customer Support.



4 Entire System Server 3.3.2 Release Notes■ Support of Previous Versions ............................................................................................................. 20■ Solved SAGSIS Problems ................................................................................................................. 20■ Changes with the Next Version .......................................................................................................... 22

19




For information on how long a product is supported by SoftwareAG, see SoftwareAG's ServLine24web site at http://servline24.softwareag.com/public/. In the left menu of this site, expand "MyServLine24" and login to "Secured Services". Once you have logged in, you can expand Productsin the left menu of the web page and select Product Roadmaps to access the Product VersionRoadmaps application. This application allows you to request support information for specificproducts and releases.


This section describes solved SAGSIS problems for Entire System Server 3.2.2. SAGSIS is the in-ternal Software AG Support Information System where we track problem issues.

The section covers the following topics:

■ 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


Errors after JES hotstart240446

abend D37 using IEBCOPY view245831

BAD PARM CARD: X-COM stopped265803

VTAM ACB open failed RC=090266209

Abend S0C7 in XCOMV012+X'1196'266249

file-attributes SYSRES extent 1266256

file-attributes abend266309

S80A-10 abends266338





View FILE-ALLOCATE - SMS266618

abend 913-38266974

write-to-spool returns 5874267009

file-attibutes dsname=dummy267029

lib-dir scan with alias name267142

nom/eor monitor and npr hang267218

Abend S0C4-04 in IFG019RA+X'1E58'267431

SYSNPR change default db-id267902

ESY5731 Error .. during spool GET268263

ADARSP254 subcode 6268552

CLASSES and JES-INIT-ID incorrect268865

file-attributes multi-volume269198

PDSE load module displayed wrong270055

file-attributes270196

Abend S0C1 in XCOMV011 + X'458'270249

ESY0579I SSI req 79 SSS2REAS 10270299

ESY5722 Req. data set not found270553

inact/act spoolacb during run270627

Panvalet and wildcard271639

submit without dsname and card271672

spool-queue find submitter,JES3271791

0C4 ESYTRACE rc=4 offset 38E272314

Monitor subtask ended not success272728

NAT5777 while browsing panvalet272821

Support for z/OS 1.8 JES2 & JES3273518

*USER for SUBMIT not correct273692

abend 213-30274263

Potential exposure for READ-SPOOL274960

NAT5871 MEMBER/TYPE not specified276603

error 5507 - read empty file277675

ACTIVE-JOBS JES-INIT-ID bad data279197

JES3 command prefix changed280137

ACTIVE SUBT DETACH IN PROGRESS280403

S0c4 ESYNMAIN +6B16 ADA8280639

FILE-ATTRIBUTES GDG problem280744

Support for mixed case password280838




abend 0C4 xcomv204 offset 0B6280906

Abend S0C4-04 in XCOMV032+X'AD6'281658

Subtask error not reported via CC281776

Abend S0C4-04 in ESYNMAIN+X'453A'282460

LOG-TIME field precision282540

TIME-STAMP field precision282972

Solved SAGSIS Problems on VSE/ESA and z/VSE


ESY5631 running below265530

ESY5631 running below265530

shutdown npr with active nom mon265667

ESY0084W ALL TASKS ACTIVE270030

Inconclusive server display270093

ILLEGAL SVC CODE HEX 18270300

mynode returns node=000 in nat42271395

LOG-TIME field precision283106



OSD: VTOC-UPDATE rename, NEWNAME272507


We plan to remove the support to run Entire System Server in single-user mode with the nextversion. If you still have any single-user environment that cannot be converted to a multi-userenvironment, please communicate your requirements to Software AG Customer Support.

We plan to remove the support to change the DBID for Entire System Server DDMs using the in-stallation aid (SYSNPR) with the next version.

We plan to implement support for multi-level security in z/OS with a future version of EntireSystem 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 re-quirements to Software AG Customer Support.



5 Entire System Server 3.3.1 Release Notes■ Support of Previous Versions ............................................................................................................. 26■ Prerequisites .................................................................................................................................. 26■ New Features ................................................................................................................................. 27■ Migration Checklists ......................................................................................................................... 29■ Changes with the Next Version .......................................................................................................... 31

25

These Release Notes provide an overview about all changes for Entire System Server 3.3.1.

For background information, further Release Notes of earlier Entire System Server versions areavailable on the current Natural Documentation CD-ROM in the folder Archive.


Note that with the release of Entire System Server 3.3.1, versions of Entire System Server lowerthan 3.2.1 can no longer be supported. You are therefore strongly advised tomigrate to the currentversion at your earliest convenience.

Prerequisites


■ Natural Version 4.1.3 or above;■ Adabas Version 7.1.3 with zaps AI713016 and AD713023, or above;■ Entire System Server Interface (provided with Natural);■ Entire Net-Work Version 5.8.1 (optional, for multi-CPU Support);■ Natural ISPF Version 2.5.3 or above (optional)■ Predict Version 4.3.2 or above (optional).

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

■ z/OS Version 1.4 or above,■ VSE/ESA Version 2.6 or above; or z/VSE 3.1 or above,■ BS2000/OSD Version 4 or above.

For z/OS, the relevant PTFs for APARs OW56714, OW56783, OW56980, OW57015, OA03327,OA06209, OA07934, OA10472 and OA12853 must be applied.

(The PTFs related to APAR OA07934 are UA13071 for HDZ11H0 and UA13111 for HDZ11J0 andcan be obtained from IBM.)

For z/OS JES2, the PTFs forAPARsOW55671, OW55856, OW57577, OA01880, OA02753, OA03125,OA03546, OA05247, OA06230 and OA06694 must be applied.



For z/OS JES3, the PTFs for APARs OW56608, OA01553, OA01715, OA02735, OA03934, OA04380,OA04501, OA06480, OA06535, OA06622, OA07372 and OA13218 must be applied.

See also Information APAR II11784 for recommended JES3 SAPI maintenance.

Since Entire System Server on BS2000/OSD is using operating system interfaces introduced withBS2000/OSD Version 2, it cannot run on earlier operating system versions.



New Features


■ Common New Features■ New Features for z/OS■ New Features for BS2000/OSD■ New, changed and deleted fields

Common New Features

Enhancements to SEND-EMAIL

The SEND-EMAIL support provided with Entire System Server Version 3.2.1 supported thecharacter set defined in ISO 646-US (ASCII). To enable the usage of international character setswith a broader scope of special characters, the new version allows you to specify a HOST-CODE-PAGEas a startup parameter and/or as a field on the SEND-EMAIL request. The EBCDIC charactersof the e-mail text will be translated to the ISO 8859-15 character set.

If you want to specify a default reply e-mail address that is different from the sender address, youmay now use the new REPLY-TO field of the SEND-EMAIL view.

For the details of these enhancements please see the section Startup Parameters in theAdministrationGuide and the section SEND-EMAIL, in the User's Guide (see View Descriptions>).



New Features for z/OS

New field in view CATALOG

A new field (FILE-SYSTEM) has been introduced to the CATALOG view to provide the capabilityto identify a zFS aggregate. Alternatively you may now check the DSORG field of the FILE-AT-TRIBUTES view to determine the zFS attribute.

New fields in SPOOL-QUEUE

Three newfields (MAX-RETURN-CODE, SUBMITTER andWLM-QUEUE-POSITION) have beenintroduced to view SPOOL-FILES to provide more information about jobs in JES2 or JES3.


Changed CONSOLE Task Setup

In order to control the CONSOLE Task, this task is no longer running as service for all EntireSystem Server nodes on one host.With version 3.3.1, it is an integrated component of Entire SystemServer. Therefore, it is not necessary anymore to stop the CONSOLE task with BCAM commandBCLOSE.

This architectural change requires individual settings for every CONSOLE Task running on onehost. Especially application name used in the SET-DCAM-APPL-LINK statement and user ID andpassword parameters provided via SYSDTA must be unique for every console task.

New Startup Parameter MONITOR-CANCEL

Startup parameterMONITOR-CANCELprovides additional control forNatural subtasks. If EntireSystem Server is shutting down, it will cancel active Natural subtasks after elapsed SHUTDOWN-MAX-DELAY if MONITOR-CANCEL=YES is supplied.

For details please see section Startup Parameters in the Administration Guide.

New Startup Parameter NUMCONSMSG

Startup parameter NUMCONSMSG defines the size of the table collecting console messages innumber of messages. It was formerly provided as SYSDTA value in the CONSOLE task, but withversion 3.3.1 of Entire System Server 3.3.1 it is a regular startup parameter.

For details please see section Startup Parameters in the Administration Guide.



New, changed and deleted fields

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

ChangeFieldView

New, A3FILE-SYSTEMCATALOG

A180 --> A253TEXTCONSOLE

A180 --> A253NETTO-TEXT

N7 --> N9RECORD-NUMBERCONSOLE-LOG

Now also valid for z/OSEXTENTS-ARRAYFILE-ATTRIBUTES

Now also valid for z/OSSERIES-ARRAY

Now also valid for z/OSVOLSER-ARRAY

DeletedBLOCK-TTRLOAD-MODULE

New, A8HOST-CODE-PAGESEND-EMAIL

New, A128REPLY-TO

New, A10MAX-RETURN-CODESPOOL-QUEUE

New, A8 (for z/OS JES3 only)SUBMITTER

New, N7WLM-QUEUE-POSITION

New, A8WLM-SERVICE-CLASS

N5 --> N7BLOCK-COUNTLIB-DIRECTORY


■ z/OS■ VSE/ESA and z/VSE■ BS2000/OSD



z/OS

Startup Parameters

■ If you are using the SEND-EMAIL view and you want to use a specific host code page, specifythe HOST-CODE-PAGE parameter.

(See Run E-Mail Client for details.)

VSE/ESA

Startup Parameters


(See Run E-Mail Client for details.)

BS2000/OSD

Startup Parameters


(See Run E-Mail Client for details.)■ If you are using CONSOLE, please adjust the job control of the CONSOLE Task.

The second SYSDTAentry defining the dimension of the consolememory poolmust be removed.Please define startup parameter NUMCONSMSG instead.

The application name used in SET-DCAM-APPL-LINK and user ID and password parametersprovided via SYSDTA must be unique for every console task.

Please use the provided job control sample to avoid missing file assignments.■ If you are running EOMor EOR, youmay specify startup parameterMONITOR-CANCEL=YESto make sure all Natural subtasks are stopped during shutdown of Entire System Server.




We plan to remove the support to run Entire System Server in single-user mode with the nextversion. If you still have any single-user environment that cannot be converted to a multi-userenvironment, please communicate your requirements to Software AG Customer Support.

We plan to remove the support to change the DBID for Entire System Server DDMs using the in-stallation aid (SYSNPR) with the next version.




6 Entire System Server 3.2.2 Release Notes■ Support of Previous Versions ............................................................................................................. 34■ Restrictions .................................................................................................................................... 34■ Prerequisites .................................................................................................................................. 34■ Solved SAGSIS Problems ................................................................................................................. 35■ Changes with the Next Version .......................................................................................................... 38

33


These Release Notes provide an overview of all changes for Entire System Server 3.2.2.


With the release of Entire System Server 3.2.2, versions of Entire System Server lower than 3.1.2can no longer be supported. You are therefore strongly advised to migrate to the current versionat your earliest convenience.

Restrictions

On an OS/390 or z/OS JES3 local processor not all functions are currently available with theviews SPOOL-QUEUE, READ-SPOOL and SPOOL-FILES. A subset of spool data sets is madeavailable with ZAP XC51067, which uses the SYSOUT API (SSI 79) on a JES3 local processorto provide access to SYSOUT data sets. However, spool data sets of active jobs, JESJCLIN andSYSIN data sets are not accessible through the SYSOUT API.

To provide access to the full range of spool data sets for applications running on a JES3 local pro-cessor, the following options are currently available:

■ RunNPR322 on the JES3 global processor and establish an Entire Net-work connection betweenthe local and the global processor.

■ Run NPR222 on a JES3 local processor. (Support for NPR222 in a JES3 local environmentwill be extended for OS/390 V2R10 and z/OS 1.1 through 1.4, without the PTFs for APAROW57535 being applied, until the restrictions for NPR322 in a JES3 local environment areresolved.)

Prerequisites


■ Natural Version 3.1.6 or above;■ Adabas Version 7.1.3 with zaps AI713016 and AD713023 (VSE/ESA only), or above;■ Entire System Server Interface (provided with Natural);



■ Entire Net-Work Version 5.8.1 (optional, for multi-CPU Support);■ Natural ISPF Version 2.4.3 or above (optional)■ Predict Version 4.2.1 or above (optional).


■ OS/390 Version 2.10 or above; or z/OS Version 1.1 or above;■ VSE/ESA Version 2.5 or above;■ BS2000/OSD Version 2 or above.

Notes:

■ OS/390 or z/OS: the relevant PTFs for APARs OW56714, OW56783, OW56980, OA06209 andOA07934 must be applied. (The PTFs related to APAR OA07934 are UA13071 for HDZ11H0and UA13111 for HDZ11J0 and can be obtained from IBM.)

■ OS/390 or z/OS, JES2: the PTFs forAPARsOW44349, OW52411, OW55671, OW55856, OW57486,OW57577, OA02753, OA03125, OA03546, OA06230 and OA06694 must be applied.

■ OS/390 or z/OS, JES3: the PTFs forAPARsOW34753, OW36022, OW49881, OW50990, OW56608,OW57110, OA01553, OA01715, OA02735, OA03934, OA04380, OA04501, OA06480, OA06535,OA06622 and OA07372 must be applied.

See also Information APAR II11784 for recommended JES3 SAPI maintenance.■ BS2000/OSD: since Entire System Server on BS2000/OSD uses operating system interfaces intro-duced with BS2000/OSD Version 2, it cannot run on earlier operating system versions.




This section describes solved SAGSIS problems for Entire System Server 3.2.2. SAGSIS is the in-ternal Software AG Support Information System where we track problem issues.

It covers the following topics:

■ Solved SAGSIS Problems on OS/390



■ Solved SAGSIS Problems on VSE/ESA■ Solved SAGSIS Problems on BS2000/OSD

Solved SAGSIS Problems on z/OS and OS/390


ESY5551 Member not specified220944

BROWSE of multivolume datasets236314

Gaps in Spool DATA-SET Numbers238705

Abend S0C4 in XCOMV002+X'2922'238798

Improve ACTIVE-JOBS performance238844

abend 213-xx238966

LIB-DIRECTORY errors w/PRODUCTs239063

Abend S72A in XDBPROC at +X'1EA239135

SYNCDB parm comments interpreted239205

ESY5580 Binder API INCLUDE ...239265

S913-0C at call to LIB-DIRECTOR239591

S0C1 in XCOMV003 at X'1490'239592

ESY5897 Mailer resp... RC 503239673

Performance active-jobs239906

Abend 0C4 in XCOMV003 at 12A2240024

dataset shown as migrat or arcive240123

Improve JES3 spool performance240724

Abend S0E0-28 in READCONS241432

copy-file FAMS error241641

Performance problem w.view VTOC241663

zap not shown241713

console-log with negative numbers241721

Browse SYSOUT data incomplete242159

COPY-FILE, REPLACE is set to YES242222

Abend S0C4 in XCOMJESC +X'B48'242255

CLASSES and JES-INIT-ID incorrect242291

ESY5683 FAMS error, 0C, 28010001242558

Bad performance w/t display CSECT242675

Improve SPOOL-QUEUE performance242818

ESY5995 File not in catalog242962

NAT5777 during 'BROWSE'243180




Error ESY5722 in NPR321243204

Abend S0C4 in XCOMJESC +X'2CB8'243294

abend 80A243744

Function 'Send-Message' problem244112

Getmained storage not released244114

abend S0C4 in LIB-DIRECTORY244144

DESTINATION LOCAL incorrect244363

0C4 When Doing Panvalet Search245543

ESY5782 during CATALOG-UPDATE245603

VTAM-abend245617

SO datasets not found245943

CONSOLE-LOG shows old SYSLOG data246263

joblist not displayed in esy321246271

SPOOL-FILES attributes missing246299

Repeated 80A-0C and 878-10 abends246342

CONSOLE-LOG shows old SYSLOG data247063

Solved SAGSIS Problems on VSE/ESA


Calls being routed to wrong view238725

NATWSPDF two byte dbid support238754

Possible storage fragmentation238860

NSPF dsn list shows VSAM only238919

WRITE-FILE causes GETVIS loss238928

SYNCDB parm comments interpreted239206

CONSOLE-LOG inconsistencies239409

ESY5508 - NOM send email task239423

NAT subtasks ATTACHed in key 0239570

COPY-FILE causes GETVIS loss239858

ESY5897 Mailer resp... RC 503240385

esy5508-152 using recipient(*)240428

Erroneous ESY3084W after ESY3051W241203

NAT subtasks not reuseable241386

copy-file return wrong node241509

zap not shown241713




COPY-FILE, REPLACE is set to YES242222

zap not shown242293

submit does not set JOB-ID242932


None.


ThefieldBLOCK-TTR (obsolete as of release 3.2.1)will be removed from the viewLOAD-MODULE.

We plan to implement support for multi-level security in z/OS with a future version of EntireSystem Server. This may require changes to customized versions of the current security exits. Ifyou are using non-standard resource classes in your security exits, please communicate your re-quirements to Software AG Customer Support.



7 Entire System Server 3.2.1 Release Notes■ Support of Previous Versions ............................................................................................................. 40■ Prerequisites .................................................................................................................................. 40■ New Features ................................................................................................................................. 41■ Changes / Enhancements ................................................................................................................. 50■ Solved SAGSIS Problems ................................................................................................................. 50■ Migration Checklists ......................................................................................................................... 53■ Discontinued Support ....................................................................................................................... 56■ Changes with the Next Version .......................................................................................................... 56

39

These Release Notes provide an overview about all changes for Entire System Server 3.2.1.


With the release of Entire System Server 3.2.1, versions of Entire System Server lower than 3.1.1can no longer be supported. You are therefore strongly advised to migrate to the current versionat your earliest convenience.

Due to the restrictions of the Common JES Interface in Entire System Server Version 3.1 regardingJES3, Entire System Server Version 2.2.2 and its JES3 Interface will be supported for z/OS andOS/390 JES3 installations until December 31, 2003.

Prerequisites


■ Natural Version 3.1.6 or above;■ Adabas Version 7.1.2 with zaps AI712015 and AI712047, Version 7.1.3 with zaps AI713016 andAD713023, or above;

■ Entire System Server Interface (provided with Natural);■ Entire Net-Work Version 5.8.1 (optional, for multi-CPU Support);■ Natural ISPF Version 2.4.3 or above (optional)■ Predict Version 4.2.1 or above (optional).


■ OS/390 Version 2.9 or above; or z/OS Version 1.1 or above■ VSE/ESA Version 2.5 or above;■ BS2000/OSD Version 2 or above.

Notes:

■ OS/390 or z/OS: the relevant PTF for APAR OW56783 must be applied.■ OS/390 or z/OS, JES2: the PTFs forAPARsOW44349, OW52411, OW55671, OW55856, OW57486,OA03125 and OA03546 must be applied.



■ OS/390 or z/OS, JES3: the PTFs forAPARsOW34753, OW36022, OW49881, OW50990, OW56608,OW57110, OA01553, OA01715, OA02735, OA03934 and OA04380 must be applied. See also In-formation APAR II11784 for recommended JES3 SAPI maintenance.

■ BS2000/OSD: since Entire System Server on BS2000/OSD uses operating system interfaces intro-duced with BS2000/OSD Version 2, it cannot run on earlier operating system versions.



New Features


■ Common New Features■ New Features for z/OS and OS/390■ New Features for VSE/ESA■ New Features for BS2000/OSD

Common New Features

■ Support of 2-byte DBIDs■ E-mail support■ New, changed and deleted fields

Support of 2-byte DBIDs

Entire System Server Version 3.2.1 supports 2-byte node numbers (DBIDs), thus extending thepossible range from 255 up to 65,535. To facilitate this innovation, the following field definitionshave been changed from N3 to N5:

■ NODE field of all view DDMs■ FROM-NODE and TO-NODE fields in view COPY-FILE■ FROM-NODE field in view SUBMIT



Natural programs will not need to be re-stowed if the Entire System Server node is less than 256,however they will need to be re-stowed (and possibly modified) to access node numbers greaterthan 255.

The Entire System Server Default DBID specified in theNatural NTDBPROCESSmacro statementand used in the view DDMs must still be in the range between 1 and 254.

NAT mainframe version 3.1.6 or Windows and UNIX version 5.1.1 is required to take advantageof an Entire System Server nodewith a 2-byte DBID.However, not all SoftwareAGproducts usingEntire System Server currently support node numbers greater than 255.

E-mail support

The newEntire System Server version provides support for sending e-mail. A new view processorand the new SEND-EMAIL DDM are provided. For details of using the new DDM, refer to theEntire System Server User's Guide. All administrative requirements for enabling e-mail supportare described in Entire System Server Administration Documentation.

Under VSE/ESA, e-mail support has been testedwithConnectivity Systems, Inc's and IBM's TCP/IPstack products.

Caution: Under VSE/ESA, if you have an ADA71x (713 or earlier) library in the LIBDEFPHASE statement for Entire System Server, there is an error in the library that must becorrected. An invalid CEEBXITA (both .OBJ and .PHASE)modulewas accidentally includedas part of the distribution. Although this does not affect ADABAS operation, it does causean addressing exception when using the e-mail support. You must delete these modulesfrom the library. For more information, contact Software AG support.

New, changed and deleted fields

Apart from the NODE fields, the fields listed in the table below have been added, changed or de-leted. See the associated view descriptions in the User's Guide for details regarding the affectedfields.

In addition, JOB-ID and JOB-NUMBER fields have been changed to support 7-digit job numbersin z/OS. See the section New Features for z/OS and OS/390 for a description of these changes.

ChangeFieldView

A2 -> A4JES-INIT-IDACTIVE-JOBS

New, A3QUIESCE

New, A8RESOURCE-GROUP

New, A3SERVER

New, A8SERVICE-CLASS

New, N3SERVICE-CLASS-PERIOD



ChangeFieldView

New, A8WORKLOAD

DeletedALIASCATALOG-UPDATE

DeletedCVOL

DeletedDELETE

DeletedEMPTY

DeletedINDEX

DeletedNUMBER-OF-GENERATIONS

DeletedALIASCOPY-FILE

New, N5ERROR-NODE

New, N3ERROR-VIEW

New, A3DATA-APPENDIXJOB-VARIABLES

New, A3LONG-ALIASLIB-DIRECTORY

B4 -> B3MEMBER-TTR

A80 -> A253MODULE-ATTRIBUTES

New, A253 (see also LONG-ALIAS above)MEMBER-LONG-NAME

N7.0->N11.0MODULE-LENGTHLOAD-MODULE

A80->A253MODULE-ATTRIBUTES

Obsolete (see below)BLOCK-TTR

New, A253ESD-NAME-LONG

New, A253IN-CSECT-LONG

New, A80IDR-CALLERID

A4 -> A10NATPROC-IDNATPROC-USERS

New, A8NEW-FORMSPOOL-FILES

New, A8NEW-WRITER

New, A6OUTDISP

N7 -> N9RECORD-COUNTSPOOL-QUEUE

N7 -> N9REAL-RECORD-COUNT

New, A1JES3-CLASSSPOOL-UPDATE

New, A4JES3-QUEUE

New, A8PRODUCT-NAMESYSTEM-INFO

New, A8PRODUCT-VERSION

Now a descriptorSTARTUP-PARM

Renamed to PRODUCT-OPTIONSOPTIONSWRITE-FILE

Valid for BS2000/OSD onlyEXPIRATION-DATE/X

A50 -> A127DESTINATIONWRITE-SPOOL

A8 -> A127FSSDATA



ChangeFieldView

A17 -> N5PORTNO

A17 -> A16PRTOPTNS

New Features for z/OS and OS/390

■ Support for 7-digit job numbers■ Replacement of ADALNA5■ CONSOLE FUNCTION='DIS-WTOR': Display pending operator replies■ COPY-FILE PDSE: Program object copy between nodes■ LIB-DIRECTORY: Support of long alias names for PDSEs■ LIB-DIRECTORY: Removal of undocumented behavior■ LOAD-MODULE Changes■ New operator command EVENTS

Support for 7-digit job numbers

In z/OS release 1.2, the format of the JES JOBID has changed to support job numbers greater than99,999. For details, see "z/OS V1R2 JES2 Migration, Chapter 3.1.3: Support for a Maximum of999,999 Job Numbers", and "z/OS V1R2 JES3 Migration, Chapter 3.1.4: Support for 999,999 jobnumbers" in IBM's z/OS Library.

To support these higher job numbers, JOB-ID fields have been changed from A5 to A8, and JOB-NUMBERfields have been changed fromN5 toN7 (see table of affected views below). EvenDDMsandfields not related toOS/390 and z/OS containing JOB-NUMBERor JOB-ID have beenmodifiedto consistently support the new formats.

ChangeFieldView

A5 -> A8JOB-IDACTIVE-JOBS

N5 -> N7JOB-NUMBER

A5 -> A8JOB-IDCONSOLE

N5 -> N7LOG-JOB-NUMBERCONSOLE-LOG

A5 -> A8JOB-ID 1NATPROC-USERS

A5 -> A8JOB-IDREAD-SPOOL

N5 -> N7JOB-NUMBER

A5 -> A8JOB-ID 1SPOOL-FILES

N5 -> N7JOB-NUMBER

A5 -> A8ORIGINATOR-JOB-ID 1

A5 -> A8JOB-IDSPOOL-QUEUE



ChangeFieldView

N5 -> N7JOB-NUMBER


A5 -> A8JOB-IDSPOOL-UPDATE

N5 -> N7JOB-NUMBER

A5 -> A8JOB-IDSUBMIT

N5 -> N7JOB-NUMBER

A5 -> A8JOB-ID 1TASK-INFO

N5 -> N7JOB-NUMBER 1


A5 -> A8JOB-IDWRITE-SPOOL

N5 -> N7JOB-NUMBER

1 These fields have been changed for the reason of consistency and are not related to z/OS andOS/390.

With previous releases of Entire System Server, the JOB-ID field used to contain the five rightmostbytes of the eight-byte JES JOBID (representing the job number in character format). As of EntireSystem Server 3.2.1 the JOB-ID field contains the complete JES JOBID (three letters followed byfive digits or one letter followed by seven digits).

To achieve the best possible compatibility for five-digit job numbers with previous releases ofEntire System Server, the JOB-ID fields for z/OS and OS/390 are handled right-justified. In thisway, a five-byte JOB-ID field from a back-level DDM will continue to receive the five rightmostbytes of the JES JOBID.

Only the numeric part of the JOB-ID field will be used for selection purposes. This ensures that aFIND statement with JOB-ID = '23456' will not return a JOB-ID of 'J0123456'. On the other hand, astarted task with a JOB-ID value of 'S0123456' will be selected for a FIND statement with JOB-ID= 'J0123456' specified.

Replacement of ADALNA5

Entire SystemServer no longer requires use of the special ADABAS linkmoduleADALNA5. EntireSystem Server now uses the standard reentrant ADABAS link module ADALNKR.



CONSOLE FUNCTION='DIS-WTOR': Display pending operator replies

To obtain pending operator reply messages (WTORs) that have been issued before the start ofEntire System Server, the operator command 'D R,R,T,SYS=sysid' is issued during initialization.

COPY-FILE PDSE: Program object copy between nodes

COPY-FILE now supports copying of PDSE program objects between nodes. Mixed PDS/PDSEcopies are still prohibited due to IBM restrictions; an intermediate IEBCOPY of the member to theproper format data set is required.

LIB-DIRECTORY: Support of long alias names for PDSEs

Upon request, LIB-DIRECTORY now returns the first 253 bytes of a long alias name in a PDSE.

LIB-DIRECTORY: Removal of undocumented behavior

There was an undocumented feature under OS/390 and z/OS where the LIB-DIRECTORY fieldMEMBER-TYPE would contain the value "ALIAS" if the member was an alias. This conflicts withinternal COPY-FILE view processing, and also has never been documented; therefore this featurehas been removed fromEntire SystemServerwith this release. TheALIASfield continues to contain"YES" if the member is an alias - this functionality remains unchanged.

LOAD-MODULE Changes

■ Removal of support for field BLOCK-TTR■ Changes in $PRIVATE entries■ Differences in order/content of output■ SEGMENT-LENGTH behavior

Removal of support for field BLOCK-TTR

Due to improvements in the internal processing in the LOAD-MODULE view, it has become ne-cessary to remove support for the BLOCK-TTR field. This field will contain binary zeros with thisrelease, and it will be removed in the next release.

Changes in $PRIVATE entries

Also due to these improvements, ESD entries formerly identified as $PRIVATE will now be iden-tified as $Pxxxxxx, where xxxxxx is a hexadecimal representation of a binder-internally-generatedidentifier. (Thesewill be equivalent to "$PRIVxxxxxx" entries in correspondingAMBLIST output.)

Differences in order/content of output

In addition, IDR records may appear in a slightly different order, and multiple records may bemerged into a single record. Theremay also be slight differences in the return order of ESD entries.



TEXT entries are unchanged.

SEGMENT-LENGTH behavior

For further information, see new additional documentation regarding the value of SEGMENT-LENGTH and large occurrences of the BIND-specified FILL character in the User's Guide.

New operator command EVENTS

A new operator command, EVENTS, has been provided to allow diagnosis of problems withEVENTING tasks.

New Features for VSE/ESA

■ Use of 31-bit storage■ Support of VSE/ESA POWER CRE queue■ Support of VSE/ESA POWER multiple browsing of spool files■ Support of XEQ-START/STOP fields in SPOOL-QUEUE■ IDCAMS view now available for VSE/ESA■ Retrieval of contents from VSAM catalogs■ Use of dataspaces in a CA-Dynam/D environment■ Enhancements to label processing■ CONSOLE-LOG field PARTITION now a descriptor■ Support of various LOG-xxx fields in CONSOLE-LOG, deprecation of undocumented fieldsDATX and TIMX

■ New operator command EVENTS■ LIB-DIRECTORY enhancements

Use of 31-bit storage

Internal improvements have increased the amount of 31-bit storage used by Entire System Server.We now recommend runningNPR in a partition or class with a size greater than 16M. In addition,see the section below regarding Use of dataspaces in a CA-Dynam\D environment.



Support of VSE/ESA POWER CRE queue

Entire System Server fully supports browsing of POWER spool files in the CRE queue by SPOOL-FILES and READ-SPOOL. A new SPOOL-FILES STATUS value, 'CRE', has been added.

Support of VSE/ESA POWER multiple browsing of spool files

Entire System Server fully supports multiple browsing of POWER spool files without changes toexisting NATURAL programs.

Support of XEQ-START/STOP fields in SPOOL-QUEUE

The various fields referencing execution start and stop times are now valid for VSE/ESA. Theyreflect information about the POWER queue entry rather than the job.

IDCAMS view now available for VSE/ESA

TheVSAMutility IDCAMS is now available toNATURALprograms byway of the IDCAMSview.

Retrieval of contents from VSAM catalogs

The CATALOG view now supports retrieval of information from the VSAMmaster catalog andVSAM user catalogs.

Use of dataspaces in a CA-Dynam/D environment

To reduce VTOC resource conflicts, the VTOCviewprocessor nowutilizes dataspaceswhen EntireSystem Server runs in an environment where CA-Dynam/D is active. For more details, see Step13: Dataspace Requirements in the Installation for VSE/ESA section of the Installation andCustom-ization documentation.

Enhancements to label processing

Improvements have been made in the internal label processing table management that shouldimprove performance when accessing files.



CONSOLE-LOG field PARTITION now a descriptor

The field PARTITION is now a descriptor, which allows it to be used in the WITH clause of theFIND statement.

Support of various LOG-xxx fields in CONSOLE-LOG, deprecation of undocumented fields DATX and TIMX

Several of the LOG-xxx fields that were formerly documented as being OS/390-only have nowbeen added to the VSE/ESA support. This includes LOG-TIMX and LOG-DATX, which replacethe undocumented fields DATX and TIMX. The CONSOLE-LOG DDM has been updated so thatthe fields DATX and TIMX now point to the same short DB names as their LOG-xxx counterparts.These two fields are scheduled to be deleted in a future release of Entire System Server.

Important: If you have a program that uses either DATX or TIMX, you must recatalog theprograms due to the DDM changes before using NPR321, and you should also change theprograms to use the LOG-DATX and LOG-TIMX fields.

New operator command EVENTS

A new operator command, EVENTS, has been provided to allow diagnosis of problems withEVENTING tasks.

LIB-DIRECTORY enhancements

ThefieldsBLOCK-COUNTandDATE/DATX/TIME-CREATEDare nowsupported if LIST-SUBLIBS= 'YES'.


All executable components of Entire System Server in BS2000/OSD are built as LLM objects (LMStype L). This reduces the load time significantly.

The newoperator command FILES is supported to display all open files per server task (ESYSERV).For further information see FILES in the Operator Commands section of the Entire System ServerAdministration Documentation.



Changes / Enhancements

The following C/E's have been implemented:

■ CE 4049: More NEW fields in SPOOL-FILES■ CE 9965: Provide ALIAS creation for PDSE load modules


This section describes solved SAGSIS problems for Entire System Server. SAGSIS is the internalSoftware AG Support Information System, where we track problem issues.

It covers the following topics:

■ Solved SAGSIS Problems on OS/390■ Other Problems Solved on z/OS■ Solved SAGSIS Problems on VSE/ESA■ Solved SAGSIS Problems on BS2000/OSD

Solved SAGSIS Problems on OS/390


re-reading temp files177840

Output datasets of running jobs191009

S0C4 REFRESH JES Command217384

ESY5787 CSI ... Reason 8, RC 64217416

View CONSOLE field JOB-TYPE217791

Spool Files with OUTDISP=PURGE218067

S0C4 in NATPVTPR offset 49E218125

ASMA034E OPRVRACF assembly error218315

ESY5551 copying PDSE member218544

Operator enters ADAEND dump A03218758

ADAEND is not possible218779

Abend S30A-18 in XCOMV200+X'5CA'218858

esy5803 with allocations219499

Spool ds not found for held job219723

Device-names: address not found219851




NATPROC-LOGON without USER-ID220020

ICH409I 582-000 ABEND RACHECK220224

S0C7 in XCOMV044 at x'2A30'220419

JES2 spool utilization incorrect220421

copy-file write-file VB PDS fails220715

ESY5900 Cannot allocate SYSOUT220895

ESY5722 error using READ-SPOOL220902

Reading multi-volume datasets221058

S0C1 in XCOMV003 +95C221245

TIME-XEQ-START value wrong221609

S80A reason 10221949

READ-SPOOL TYPE=AL does not work221957

read-file, multi-volume, volser222191

ESY5902 reading dataset/member222336

SPOOL-Q:CLASS not filled f.input222689

FILE ATTRIBUTES for migrated ds222848

record-number and read-spool view222887

Hang using REMOTE callers223022

Recall should show volser223128

Zero AREA is filled with blanks223454

ABEND 5777 READ-FILE223642

S0C4 in NATPREP+0x382223691

Support for JES2 z/OS 1.4223774

FIND SPOOL-QUEUEWITH 'OR' INCORR223831

Print with NPR-Exit NATWSP23224040

SPOOL RELEASE with CLASS224300

Npr311 Abends S0c4 with ADAM99.225152

line limit reached225524

SPOOL-FILES CPU consumption225894

ESY5904 SCLM protection226469

User can't release his own job226869

S0c4 at start natprep + x'1e6'227280

IEA705I GETMAIN 878-10227584

RACF error browsing own job227600

S0C1 in XCOMJESCW. SPOOL-QUEUE227979

ESY5833 trying to change class228423




NAT3254 with NAT subtasks228483

Perform. degradation at PO SCAN229336

ABEND SA0A RC=0010229991

S0C1 at address X'00000052'230147

S0C4 in LIBRVS of LIBRARIAN230524

Find catalog GDG doesn't work231067

Copy of PDS datasets fails231348

SPOOL-FILES AND DATA-SET-KEY231527

ADAEND doesn't work232553

CONSOLE: TIMX - wrong year 19xx233602

Read VSAM always No Records.234049

ESY5899 on READ-FILE multi VOLUME234299

ABEND CODE 8423E000234596

Real size of trace storage ?235014

ABEND S0C7 in XCOMV002236854

ESY5777 during a 3GL-PAC-Migration236905

Other Problems Solved on z/OS

The restrictions for OS/390 JES3 installations as described in the Entire System Server 3.1.1 ReleaseNotes no longer apply. The Common JES Interface now returns spool information from JES3 inthe sameway as from JES2,which is slightly different from theway spool informationwas returnedfrom the JES3 interface of NPR22. To easemigration in a JES3 environment, the spool-related viewprocessorswill support either a 'compatibilitymode' or a 'consistencymode'. Themode is determ-ined from the value specified for the SPOOL startup parameter. SPOOL=JES3 sets the 'compatib-ility mode'; the 'consistency mode' can be requested with SPOOL=JESC. For details, see z/OS andOS/390 JES3 Considerations in the section OS/390 Considerations of the Entire System ServerAdministrationDocumentation.We plan to remove support for the 'compatibilitymode' in a futurerelease.

Solved SAGSIS Problems on VSE/ESA


ESY5996 DYNAMPOOL=poolname200121

LIB-DIRECTORY ends prematurely213413

Various abends with CA-Dynam/D215309

ESY5551 copying PDSE member218604

ESY5996 browse VSE-members220460




Browse VSE File under DYNAM fails221018

BROWSE SAM ESDS VSAM files221080

Reduce size of POWER ERROR-TEXT221752

ADAM98 error (no common memory)224060

ESY5904 SCLM protection226468

NAT3254 with NAT subtasks228483

Support POWER 6.7229656

Possible FREEVIS errors231461

Cancel code 25 if MSGLEVEL=2231701

CONSOLE: TIMX - wrong year 19xx232716

CONSOLE-LOG wrong LOG-TIMX232720

ESY5701 in READ-FILE execution234446

Real size of trace storage ?235417



Communication lost227660

NPR31x does not start with ADA731227736


■ z/OS and OS/390■ VSE/ESA■ BS2000/OSD

z/OS and OS/390

■ Startup Parameters■ JCL Procedure■ RACF Definitions



Startup Parameters

■ Remove retired parameters MIGRAID and SYSLOG-REFRESH, if still specified.■ If you intend to use the new e-mail feature:

■ add SMTP-HOST, TCP-STACK and, optionally SMTP-PORT parameters. For further inform-ation, see Run E-Mail Client in the sectionCommonEntire System Server Features of the EntireSystem Server Administration Documentation.

■ If you are using JES3 and you want to exploit the 'consistency mode':■ change your SPOOL parameter value from 'JES3' to 'JESC'. For further information, see z/OS

and OS/390 JES3 Considerations in the section OS/390 Considerations of the Entire SystemServer Administration Documentation.

■

■ Check for IUBL= settings and remove it. The default value is now 32767, and a smaller valuemay cause problems with the remote PDSE copy function of COPY-FILE

JCL Procedure

■ If you intend to use the new e-mail feature:■ youmayhave to add a SYSTCPDDDstatement to your JCLprocedure. For further information,see Run E-Mail Client in the section Common Entire System Server Features of the EntireSystem Server Administration Documentation.

■ If you are using JES3, and you are migrating from NPR222:■ remove the UQJ3JOBS DD statement for the DSP data set.

■ When theDSP data set is no longer needed by any back-level Entire System Server or Com-pleteaddress space, you should:■ cancel the UQJ3 DSP in JES3;■ RESTORE and REJECT the USERMOD to add the DSP directory entry to IATGRPT;■ delete the DSP load module IATUQJ3 from your load library;■ remove the allocation for the DSP data set from your JES3 JCL procedure or initializationstatement deck, and

■ delete the DSP data set.

For further information, see z/OS and OS/390 JES3 Considerations in the section OS/390Considerations of the Entire System Server Administration Documentation.



RACF Definitions

■ Add READ authority for the MVS.DISPLAY.R profile in the OPERCMDS resource class to yourEntire System Server's MCS console, if not already defined.

■ If you intend to use the new e-mail feature:■ define the Entire System Server Started Task and all users requesting SEND-EMAIL as UNIXSystem Services users (define an OMVS segment in RACF). For further information, see RunE-Mail Client in the section Common Entire System Server Features of the Entire SystemServer Administration Documentation.

VSE/ESA

■ Startup Parameters■ Partition/Class Size■ Dataspaces■ CONSOLE-LOG

Startup Parameters

■ If you intend to use the new e-mail feature, add SMTP-HOST, TCP-STACK and, optionallySMTP-PORTparameters. For further information, see RunE-Mail Client in the sectionCommonEntire System Server Features of the Entire System Server Administration Documentation. SeealsoWarning regarding CEEBXITA in older ADABAS libraries.

Partition/Class Size

■ Due to changes in internal processing, we recommend increasing the size of the partition orclass to a value greater than 16M.

Dataspaces

■ If you are using CA-Dynam/D, see Step 13: Dataspace Requirements in the Installation forVSE/ESA section of the Installation and Customization documentation.



CONSOLE-LOG

■ Check programs for use of deprecated fields DATX and LOGX.

BS2000/OSD

■ Startup Parameters

Startup Parameters

■ If you intend to use the new e-mail feature, add SMTP-HOST, TCP-STACK and, optionallySMTP-PORTparameters. For further information, see RunE-Mail Client in the sectionCommonEntire System Server Features of the Entire System Server Administration Documentation.

Discontinued Support

As announced in the Entire System Server 3.1.2 Release Notes:

■ support for files 100 and 202 (sequential file support using a DDM to describe the data) has beenremoved;

■ fields and functions related to CVOLs have been removed from the DDM for CATALOG-UP-DATE. IBM has dropped support for CVOLs as of January 1st, 2000.


The field BLOCK-TTR (obsolete as of this release)will be removed from the viewLOAD-MODULE.




8 Entire System Server 3.1.2 Release Notes■ Support of Previous Versions ............................................................................................................. 58■ Prerequisites .................................................................................................................................. 58■ Solved SAGSIS Problems on z/OS and OS/390 .................................................................................... 59■ Solved SAGSIS Problems on VSE/ESA ............................................................................................... 63■ Solved SAGSIS Problems on BS2000/OSD .......................................................................................... 64■ Changes with the Next Version .......................................................................................................... 64

57

For further information, you should also read the Entire System Server 3.1.1 Release Notes whichare delivered with Version 3.1.2 on the current Natural Documentation CD-ROM and in printedform.

References contained in theVersion 3.1.1 ReleaseNotes generally refer to the correspondingVersion3.1.1 manuals which are included in the Version 3.1.2 documentation.



Note that with the release of Entire System Server 3.1.2, versions of Entire System Server lowerthan 2.2.2 can no longer be supported. You are therefore strongly advised tomigrate to the currentversion at your earliest convenience.

The restrictions for OS/390 JES3 installations described in the Entire System Server Version 3.1.1release notes also apply to this maintenance level. If your applications need the missing function-ality for the JES3 interface or you are using EntireOutputManagement (NOM), youmust not installEntire System Server Version 3.1.2. Instead, you have to use Entire System Server Version 2.2.2,until the missing functionality of the JES3 interface is implemented in the next release of EntireSystem Server.

Prerequisites


■ Natural Version 3.1.4 or above;■ Adabas Version 7.1.2 or above;■ Entire System Server Interface (provided with Natural);■ Entire Net-Work Version 5.6.1 (optional, for multi-CPU Support);■ Predict Version 4.1.2 or above (optional).

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

■ OS/390 Version 2.6 or above; or z/OS Version 1.1 or above■ VSE/ESA Version 2.4 or above;■ BS2000/OSD Version 2 or above.



For OS/390, JES2 the PTF's for APAR's OW35104, OW36019, OW44349 and OW52411 must beapplied.

For OS/390, JES3 the PTF's for APAR's OW34753, OW36019, OW36022 and OW44298 must beapplied. See also Information APAR II11784 for recommended JES3 SAPI maintenance.

Since Entire System Server on BS2000/OSD is using operating system interfaces introduced withBS2000/OSD Version 2, it cannot run on former operating system versions.



If Natural ISPF is used, Version 2.4.3 or above is required to support the new Entire System Serverversion.

If Natural ISPF Version 2.4.2 is used, the solutions for the following problems have to be installed:

z/OS and OS/390:

DescriptionSolutionProblem

Error NAT1305 in ISPJLS1P / 5580 Numeric value truncatedIS24204195165

BS2000/OSD:

DescriptionSolutionProblem

Browse / Find in LMS elements slow.IS24205202180

Solved SAGSIS Problems on z/OS and OS/390


NAT0954 on IF ERROR-CODE168615

RLSE not releasing unused space190497

Lib-update doesn't scratch190840

Rename dataset ACF2 message200106

Fields not filled, DIS-WTOR201694

No user-id from NATPROC-

release notes - overview - software ag · 2014. 6. 13. · console descr-code-string new,a16...

Documents