z/VSE Considerations

This document covers the following topics:

VSE/POWER Considerations

Entire System Server as supplied, supports all versions of z/VSE/POWER from SP5 onwards. No customization is therefore necessary.

z/VSE Maintenance Considerations

Maintenance to Entire System Server objects and phases will be performed using the MSHP utility. Prior to applying maintenance, the Entire System Server must be defined to MSHP as follows: 

  ARCHIVE NPRvrs
  COMPRISES 9001-ESY-00
  RESOLVES 'ENTIRE SYSTEM SERVER Vvrs'
  ARCHIVE 9001-ESY-00-vrs
  RESIDENCE PRODUCT=NPRvrs            -
            PRODUCTION=library.NPRvrs -
            GENERATION=library.NPRvrs

where:

vrs refers to the relevant Entire System Server Version, Release and System maintenance level.

Entire System Server Zaps will be supplied using the following format: 

  CORRECT 9001-ESY-00-vrs : XC14nnn REVOKABLE
  AFFECTS PHASE=name
  ALTER   offset verify : replace
  RESOLVES 'reason'

z/VSE Security Considerations

As of z/VSE Version 2.4, a SAF security interface is now provided. Either the Basic Security Manager (minimal security, distributed as part of z/VSE) or CA TOP SECRET (a third-party product, additional cost) may be used. Entire System Server has the ability to use SAF for security for users and datasets. However, the routines must be written by the user. Please contact Software AG support for information on writing the exits.

CA-Dynam/D Considerations

When Entire System Server is used in an environment where the CA-Dynam/D product is active, several items must be taken into consideration:

  • Use of DYNAMPOOL=value as the VOLSER value is supported only in the FILE-ATTRIBUTES, READ-FILE, LIB-DIRECTORY, LIB-UPDATE, VTOC-UPDATE and WRITE-FILE views under two conditions:

    • when a non-generic data set name is specified;

    • if the data set is defined in the CA-Dynam/D catalog (which is used to look up the real volume serial), whether automatically or manually added.

  • Other file views (such as VTOC and FILE-ALLOCATE) are not currently supported.

  • Other uses (for example, generic data set names) are not supported due to the limited amount of data returned by defined CA-Dynam/D interfaces.