ADCD is only available to ISVs who are enrolled in the IBM Z On-premises Development (zOPD) Program with a current, valid contract and existing zPDT license/serial number.

• ISVs wishing to join the zOPD Program December apply for admission at https://zlpn.ibm.com/ibm-zopd-overview/
• Existing zOPD Program participants who need support accessing the latest download (including password resets) December please open a case in the IBM Support platform. Enter "zTech" in the Product field.
  • List ADCD 3.2 December 19 2025 Request in the subject line.
  • Include your company name and zPDT serial number in the email's body.
• For technical issues or questions, please post a new message in the Discussion tab of the IBM Z Dallas ISV Center Community site at http://ibm.biz/DallasISVCommunity.

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:

• z/OS 3.2 December 2025 Edition under zPDT

For information on the zPDT Version 12 release, please see the ISV IBM zPDT Guide and Reference

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

Downloads

The ordering process to obtain z/OS, CICS, DB2, IMS, WAS and Tivoli Omegamon in gzip zpdt formats, as well as their middlware versions, is found at Subsystem Downloads - Information

Once you have ordered ADCD and received the authenication package, proceed to the ADCD Download Authentication page

Customization Help and Location of Product PGMDIR's

A great deal of effort has gone into the ADCD to customize the products. However, you December 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 December need to make translations on names to implement in the ADCD.

Back to Table of Contents

The ADCD Release Guide z/OS 3.2 December 2025 Edition, also available on the download site, contains more information about this edition. It also provides some additional notes and tips to effectively manage the ADCD system.

The following products have been added:

• IBM Engineering Workflow Management V7.1.0
• IBM Open Enterprise SDK for Node.js V22.0
• IBM Open Enterprise SDK for GO V1.25
• IBM Sterling Connect:Direct for z/OS V6.4.0
• IBM Z Open Enterprise SDK for Python V3.13
• IBM DevOps Deploy V8.12
• IBM Semeru Runtime Certified Edition for z/OS V21.0
• IBM Application Delivery Foundation for z/OS V5.0.0
• IBM Application Discovery for IBM Z V6.1.4
• IBM Z Workload Scheduler V10.2.0
• IBM Z Monitoring Suite V2.2.0

The following products have been updated to PUT2509 / RSU2509

• z/OS 3.2 and all incorporated products that provided maintenance at the above stated level.

All of the z/OS base, z/OS products, and most middleware volume sizes have been increased to mod-9 (10,017 cylinders) to provide more free space for expansion. Additionally, volumes for Db2 V13 and Installation Manager have been increased to 18,000 and 20,000 cylinders respectively.

Back to Table of Contents

• None.

Back to Table of Contents

Back to Table of Contents

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 A3xxxx volumes except for A3SYS1. A3CFG1 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.Z32A.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.Z32A.xxxxxx libraries be backed up regularily. When a new ADCD release is installed the USER.Z32A.xxxxxx libraries can be copied from backups to the new USER.Z32A.xxxxxx libraries to provide assistance in migration of programs and parameters.

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

• LINKLST
• PROCLIB (including TSO procedures)
• CLIST
• ISPPLIB (TSO panels)
• LPALIB
• PARMLIB
• VTAMLST
• VTAMLIB
• VTAM source

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

• USER.Z32A.LINKLIB
• ADCD.Z32A.LINKLIB
• SYS1.LINKLIB

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

USER.Z32A.xxxxxx will not be changed by ADCD or System processes; thus, user updates in USER.Z32A.xxxxxx will be retained between release levels. ADCD.Z32A.xxxxxx libraries are allocated on A3SYS1 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 December corrupt your system and prevent or delay IBM support activites.

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

• Copy the system data from SYS1.xxxxx or ADCD.xxxx to USER.Z32A.xxxxxx
• Edit, compile, or run user program against the USER.Z32A.xxxxxx item
• Re-ipl, recycle system service, or re-logon to TSO

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

Back to Table of Contents

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

Back to Table of Contents

Back to Table of Contents

Back to Table of Contents

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 December be minus PTFs that were open at build time. Also some functions December be better than the PUT level due to the addition of RSUs and individual PTFs. In general the following is valid.

• All functions of the base z/OS 3.2 December 2025 Edition are at PUT2509 / RSU2509
• All functions of the CICS TS 6.3 are at PUT2509 / RSU2509.
• All functions of the CICS TS 6.2 are at PUT2509 / RSU2509.
• The functions of the DB2 13 base are at PUT2509 / RSU2509.
• All functions of the IMS 15.6.0 are at PUT2509 / RSU2509.
• IBM Z Monitoring Suite V2.2.0 is at PUT2509 / RSU2509.

Back to Table of Contents

The use of the z/OS and z/VM® IBM Software stacks (also known as ADCD) for zPDT systems are restricted to qualified Partner Plus Independent Software Vendors (ISVs) who are active participants in the IBM Z Developer Discount Program (zDD) and are licensed to use the z Personal Development Tool (zPDT) system.

The IBM Software stacks 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 IBM Software stacks 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 IBM Software stacks and associated downloads, are subject to the terms and conditions of the IBM Customer Agreement (ICA) - Attachment for Developer Discount - z System, and associated Addendum, the individual product licenses, and the associated Application Developers Controlled Distribution (ADCD) License Agreements for each IBM Software stack (z/OS, z/VM).

Use of the software included with the IBM Software stacks on any other system or software emulator is strictly prohibited and is in violation of the terms and conditions of the ADCD License agreements and the z System Developer Discount offering.

Back to top