What you should know about ADCD.

The ADCD is built on a twice per year schedule typically coinciding with the release of new versions of z/OS. The ADCD is created to provide qualified Independent Software Vendors (ISVs) with the latest z/OS System along with associated middleware products at the latest available maintenance level. For quite some time now, we have been offering the z/OS System also via download option, in addition to the DVDs. The z/OS ADCD can run under the IBM's System z Personal Development Tool (zPDT).

NOTE: There is an annual US $900 subscription fee for the use of the ADCD SW distributions. This annual fee covers the z/OS, z/VM, and z/VSE and Parallel System Starter System SW stacks and is regardless if one, two, or all four ADCD stacks are requested.

Important: Important information is found in this disclaimer so Please READ the Disclaimer!!

Announcements, Changes and Updates for this release.

Application Developer Controlled Distribution (ADCD) for z/OS Release 2.2 May 2016 Edition is available via DVD as of May 26, 2016. The same is available via download option as of May 19, 2016.

How to request the z/OS 2.2 May 2016 ADCD.

License

The ADCD is a customized bundle of z/OS and related products. It is not an IBM program product and is not supported as a product. The intent of the ADCD is to allow a user a way to quickly implement a z/OS system in order to concentrate on application development. In general choice of parameters and customizations are default install options with some changes due to user experiences.

Approved ISVs with zPDT based systems will need to have agreed to the ADCD license agreement, and have a signed System z Developer Discount contract on file with IBM prior to receiving a copy of the z/OS ADCD. All license and agreements are done through the System z Developer Discount offering.

System Requirements

The currently supported ADCD environments is:

For information on the zPDT Version 1.6 release, please see zPDT What is New

For the z/OS ADCD and z/VM ADCD Startup zPDT mimimum system requirements.

The z/OS ADCD packet is in Linux gzip format. The *.gz files are gzipped directly from the 3390 images running under zPDT.

Downloads

A procedure for obtaining z/OS, CICS, DB2, IMS, WAS and DB2 PE in gzip zpdt formats is found at Subsystem Downloads.

Download authentication page is here.

Customization Help and Location of Product PGMDIR's

A great deal of effort has gone into the ADCD to customize the products. However, you may find some products that are not fully customized or are customized with options that you need to change. Included in this release, are files in the format of p.SVSC.l where p=product HLQ and l=library name. The purpose of these files is to provide PGMDIR's, README, and INSTALL instructions. This ADCD is built from a driver system that uses different volume and library names. Thus, you will notice that the names referenced in the SVSC files are different than the ADCD. You may need to make translations on names to implement in the ADCD. Included on DVD1 on the RES1 volume are datasets with HLQ of MVS.ZOSRxx that document MVS. The MVS PGMDIR is contained in this grouping.

What's New in this release

The following items have been added to the distributed DVD packet.

Products contained in this release

Reported problems, fixes, and maintenance

Build Structure

B2RES1 and B2RES2

B2RES1 is a 3390-9 volume that contains the base MVS system software target, or run-time libraries, and other system data sets required to IPL the system and use TSO/E and ISPF. This is the MVS IPL volume.

B2RES2 is a 3390-9 volumes that are an extension of the SYSRES volume B2RES1. The volume is also required for IPL.

B2SYS1

This 3390-9 volume contains data sets that you might change, either through normal use of the system or user customization. System control data sets, such as SYS1.IPLPARM,IODF (I/O Definition File), and system's master catalog (CATALOG.Z22B.MASTER) reside on this volume. This volume is required to IPL. B2SYS1 contains the usercatalog USERCAT.Z22B.PRODS containing entries for z/OS related products

B2CFG1

This 3390-9 volume contains data sets for storing user configuration. The 'USER.**' data sets reside on this volume, they are cataloged in the master catalog. The RACF database reside on this volume.

B2USS1 and B2USS2

B2USS1 is a 3390-9 volume that contains the Fonts, Version and zOSMF zFS files for UNIX System Services of z/OS. This volume is required to IPL.

B2USS2 is a 3390-9 volume that contains root zFS and zFS files for UNIX System Services of z/OS. This volume is required to IPL.

B2PRD1, B2PRD2 and B2PRD3

B2PRD1 to B2PRD3 are 3390-9 volumes that contains all z/OS products.

B2DIS1 and B2DIS2

These volumes contains the base MVS system software distribution libraries. They contain the DLIB (Distribution Library) and zone CSI's. These volumes are needed to install service or products on the MVS system using SMP/E. These volumes are all 3390-9.

B2PAGA, B2PAGB and B2PAGC

These volumes contain page data sets. The B2PAGA volume has the PLPA, Common and one Local page data set. Rest of the 2 volumes each have one Local page data set. The loadparms that bring up DB2 or WAS have been defined to use all the above 3 page volumes, all other loadparms use only the first two volumes. If you do not want to use all of these local page data sets, you can modify the PAGE parameter on IEASYSnn member, accordingly.

B2DBB1, B2DBB2 and B2DBAR

B2DBB1 is a 3390-9 volume that contains DB2 V11 related data. B2DBB1 contains the DB2 usercatlog, USERCAT.Z22B.DB2VB. Also B2DBB1 contains all DB2 target libs AND DB2 V11 utility products. This volume is not required to IPL but is required to bring up DB2 V11.

B2DBB2 is a 3390-9 volume that contains DB2 catalog and directories with HLQ DSNCB10, which are SMS managed. The volume is not required for IPL but is needed to bring up DB2.

B2DBAR is a 3390-9 volume defined in a new esoteric called DBARCH. This esoteric has been defined in DB2, for allocating the archive logs into this storage volume. This volume is required, if you want to bring up DB2 V11.

B2DBA1, B2DBA2 and B2DBAR

B2DBA1 is a 3390-9 volume that contains DB2 V10 related data. B2DBA1 contains the DB2 usercatlog, USERCAT.Z22B.DB2VA. Also B2DBA1 contains all DB2 target libs and DB2 V10 utility products. This volume is not required to IPL but is required to bring up DB2 V10.

B2DBA2 is a 3390-9 volume that contains DB2 catalog and directories with HLQ DSNCA10, which are SMS managed. The volume is not required for IPL but is needed to bring up DB2.

B2DBAR is a 3390-9 volume defined in a new esoteric called DBARCH. This esoteric has been defined in DB2, for allocating the archive logs into this storage volume. This volume is required, if you want to bring up DB2 V10.

B2C531

B2C531 is a 3390-9 volume that contains CICS 5.3 Target, DLIB and all related data for CICS 5.3. USERCAT.Z22B.CICS530 resides on this volume. This volume is not required to IPL but is required to bring up CICS 5.3 and apply CICS maintenance.

B2C521

B2C521 is a 3390-9 volume that contains CICS 5.2 Target, DLIB and all related data for CICS 5.2. USERCAT.Z22B.CICS520 resides on this volume. This volume is not required to IPL but is required to bring up CICS 5.2 and apply CICS maintenance.

B2C511

B2C511 is a 3390-9 volume that contains CICS 5.1 Target, DLIB and all related data for CICS 5.1. USERCAT.Z22B.CICS510 resides on this volume. This volume is not required to IPL but is required to bring up CICS 5.1 and apply CICS maintenance.

B2W851, B2W852, B2W853, B2W854, B2W855, B2W856 and B2W857

B2W851, B2W852 and B2W853 are 3390-9 10000 cyls volume that contains target and distribution libraries for Websphere Application Services.

B2W855 to B2W857 are 3390-9 volumes that contain pre-configured zFS files required for manually starting WAS.

B2W801, B2W802, B2W803, B2W804 and B2W805

B2W801, B2W802 and B2W803 are 3390-9 10000 cyls volume that contains target and distribution libraries for Websphere Application Services.

B2W804 and B2W805 are 3390-9 volumes that contain pre-configured zFS files required for manually starting WAS.

B2IME1, B2IMD1, B2IMC1, B2IMU1 and B2IMU2

B2IME1 is a 3390-9 volume that contains IMS Target, DLIB and all related data for IMS 14. USERCAT.Z22B.IMS14 resides on this volume. This volume is not required to IPL but is required to bring up IMS and perform maintenance on IMS.

B2IMD1 is a 3390-9 volume that contains IMS Target, DLIB and all related data for IMS 13. USERCAT.Z22B.IMS13 resides on this volume. This volume is not required to IPL but is required to bring up IMS and perform maintenance on IMS.

B2IMC1 is a 3390-9 volume that contains IMS Target, DLIB and all related data for IMS 12. USERCAT.Z22B.IMS12 resides on this volume. This volume is not required to IPL but is required to bring up IMS and perform maintenance on IMS.

B2IMU1 and B2IMU2 are 3390-9 10000 cylinder volumes that contain IMS Utilities. These volumes are not required to IPL but is required for IMS Utilities and perform maintenance on IMS Enterprise Suite.

B2KAN1

B2KAN1 is a 3390-9 volume that contains Target and DLIB libraries for Tivoli OMEGAMON XE for DB2 Performance Expert on z/OS 5.3.0. This volume is not required to IPL but is required to bring up Omegamon XE for DB2 PE.

B2BLZ1

B2BLZ1 is a 3390-9 volume that contains Target and DLIB libraries for Rational Team Concert 6.0.1 This volume is not required to IPL but is required to bring up RTC.

SARES1

This 3390-3 volume contains a single volume stand alone system. This volume can be used to IPL and logon to a TSO/ISPF session.

The disk volume can assist in building LPAR environments and correct errors that prevent system IPL.

Recommended use of this volume is to install the volume and leave accessible. The volume should not be altered. The volume should stay in a background mode and be available for emergency type of situations. If other z/OS, OS/390, or LPAR partitions contain errors, the SARES1 volume could be used to solve the problem.

The stand alone system does not contain TCPIP or Unix system service support. The system cannot be used to install products or apply maintenance via SMP/E.

To IPL the standalone res volume:

Load Address: 0Axx

Load Parms: 0AxxSAM

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 B2xxxx volumes except for B2SYS1. B2SYS1 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.xxxxxxxx. 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.xxxxxxxx libraries be backed up regularily. When a new ADCD release is installed the USER.xxxxxxxx libraries can be copied from backups to the new USER.xxxxxxxx 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.xxxxx libraries have all been built on B2CFG1 which is the only volume that should contain user data.

USER.xxxxx will not be changed by ADCD or System processes; thus, user updates in USER.xxxxx will be retained between release levels. ADCD.Z22B.xxxxxx libraries are allocated on B2SYS1 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.

DISCLAIMER

The z/OS ADCD is a special packaging of z/OS software for the exclusive use of product development and support. It is restricted for use by qualified PartnerWorld Independent Software Vendors (ISVs) who are active participants in the System z Developer Discount offering and have a zPDT system. The z/OS ADCD software stack and associated downloads are licensed to the specific system by zPDT machine type/model serial number and cannot be transferred to any other machine. The Programs provided in the ADCD SW stack and associated downloads, are owned by IBM or an IBM supplier, and are copyrighted and licensed, not sold. Use of the products provided in the ADCD SW stack and associated downloads, are subject to the terms and conditions of the ICA - Attachment for Developer Discount - System z, and associated Addendum, the individual product licenses, and the z/OS Application Developers Controlled Distribution 5799 HHC License Agreement. Use of the z/OS ADCD software on any other system or software emulator is strictly prohibited and is in violation of the terms and conditions of the z/OS ADCD License agreement and the System z Developer Discount offering.

If you have any feedback or questions, please respond to: ztech@us.ibm.com