ADCD z/OS V2R4 December Edition of 2020

Learn about the new release ADCD z/OS® V2R4 December Edition of 2020.

Note: The SMS section in the general release information is replaced by the SMS that is provided by ZD&T. For more information, see Customizing ADCD for ZD&T.

What is new in this release

The following Workflow Provisions have been added to the Market Place:

The following products have been added:

The following products have been updated to PUT2009 / RSU2009

All of z/OS base, z/OS products and middleware volume size has been increased to mod-9 (10,017 cylinders) to provide more free space for expansion

Products contained in this release

  • z/OS 2.4 December 2020 Edition

    Lists the products available in the z/OS® 2.4 December 2020 Edition.

  • CICS 5.5

    Describes the CICS® 5.5 features shipped with the z/OS® 2.4 ADCD.

  • CICS 5.6

    Describes the CICS® 5.6 features shipped with the z/OS® 2.4 ADCD.

  • Db2 11

    Describes the Db2® 11 features shipped with the z/OS® 2.4 ADCD.

  • Db2 12

    Describes the Db2® 12 features shipped with the z/OS® 2.4 ADCD.

  • IMS 14.1

    Describes the IMS™ 14.1 features shipped with the z/OS® 2.4 ADCD.

  • IMS 15.1

    Describes the IMS™ 15.1 features shipped with the z/OS® 2.4 ADCD.

  • IBM Z Monitoring Suite v1.1.1

    Describes the IBM Z Monitoring Suite v1.1.1 features shipped with the z/OS® 2.4 ADCD.

  • Tivoli Workload Scheduler 9.5.0

    Describes the Tivoli® Workload Scheduler 9.5.0 features shipped with the z/OS® 2.4 ADCD.

  • WebSphere Application Server ND for z/OS 9.0

    Describes the WebSphere® Application Server ND for z/OS 9.0 features shipped with the z/OS® 2.4 ADCD.

  • IBM BATCHPIPES FOR OS/390 2.1.0

    Describes the IBM BATCHPIPES FOR OS/390 2.1.0 features shipped with the z/OS® 2.4 ADCD.

  • IBM z Distribution ZOWE 1.10.0

    Describes the IBM z Distribution ZOWE V1.10.0 features shipped with the z/OS® 2.4 ADCD.

  • Build Structure

    Migration Guidelines

    The following guidelines will make it easier for you to replace this level of system software with new levels built the same way.

    Only IBM-supplied system software should reside on C4xxxx volumes except for C4SYS1. C4CFG1 contains RACF, IPL, and catalog datasets that are user dependent.

    The ADCD does not contain a generalized migration utility or process. Each user has unique requirements. It is recommended that you build a migration plan based on your unique needs. The ADCD does have some assistance. The ADCD uses a system of concatenated libraries (see below) The highest level of concatenation is USER.Z24C.xxxxxx The ADCD distributes these libraries empty. It is recommended that the user place changes or overrides in these libraries. It is further recommended that the USER.Z24C.xxxxxx libraries be backed up regularily. When a new ADCD release is installed the USER.Z24C.xxxxxx libraries can be copied from backups to the new USER.Z24C.xxxxxx libraries to provide assistance in migration of programs and parameters.

    The ADCD is distributed with a standard library concatenation for the following:

    The configured order of concatenation is user, ADCD developers, and z/OS system datasets. For example, the LINKLST concatenation would be as follows:

    USER.Z24C.xxxxxx libraries have all been built on C4CFG1 which is the only volume that should contain user data.

    USER.Z24C.xxxxxx will not be changed by ADCD or System processes; thus, user updates in USER.Z24C.xxxxxx will be retained between release levels. ADCD.Z24C.xxxxxx libraries are allocated on C4SYS1 and are the libraries that are used by ADCD developers. No RACF rules exist on these libraries; however, changes to these libraries could destroy customization necessary to bring up many products. SYS1.xxxxxxx libraries should NEVER be updated by users or ADCD development. System libraries should ONLY be updated through SMP/E install, maintenance processes, or like processes.

    NOTE: Changes to System libraries or ADCD pre-customization may corrupt your system and prevent or delay IBM support activites.

    The correct procedure for a user update to system data is to:

    Removing a user update would be the reverse of the above procedure.

    LOADPARMS Options

    NOTE: JES2 should be COLD started the FIRST time you bring up the system.

    Console PF Key Settings

    USERIDS

    Maintenance Service Levels

    All the products on the ADCD consist of maintenance that is in a closed status. A PTF that is still in open status or has other than a document hold at the time the ADCD was built would not be added to the ADCD. The following PUT levels may be minus PTFs that were open at build time. Also some functions may be better than the PUT level due to the addition of RSUs and individual PTFs. In general the following is valid.