Table of Contents
Announcements, Changes and Updates for This Release
In order to install the new encrypted z/OS 3.1 ADCD, users must
install as a prerequisite zPDT Version 11.0.
In preparation for IMS NEXT, the IMS Catalog with Managed ACBs has been implemented as this will be a requirement to maintain IMS by June 2025. The address spaces for the Common Service Layer (Structured Call Interface, Operations Manager, Resource Manager) are automatically invoked during the Control Region initialization. The Repository Server for DRD management is now implemented and required for startup. OTMA and ODBM are also configured to work together with IMS Connect for client-side IMS applications.
Downloads of ADCD z/OS 3.1 May 2024 Edition images were made available via this website in conjunction with zPDT Version 11.0.
The user IDs, ADCDA-ADCDZ and OPEN1-OPEN3, have been removed. If you need to create more user IDs, please use the example in ADCD.LIB.JCL(USERID2).
The default passwords for the IBMUSER and ADCDMST are the same as the user ID. You will be prompted to change the password at first logon.
With this release the default SSH port number id 65522
With this release of ADCD, the z/OSMF Server and Angel are started at IPL using VTAMAPPL. Additionally, the TSO logon procedures have been changed to end at the READY prompt. So, it will be necessary to type ISPF to access the ISPF panels.
Starting with ADCD 3.1A, RACF certificates were added to the base z/OS and the following components: TCP/IP, TN3270, z/OSMF, Zowe, z/OS Connect, and WAS. These certificates are generated at the very first IPL of your ADCD system.Db2®
- Effective with the December 2023 edition of ADCD z/OS, Db2 Change Management Solution Pack for z/OS (5655-CH1) will be removed and replaced by Db2 Administration Tool for z/OS (5698-AT3).
- Db2 13 now supports encryption of Db2 data with z/OS DFSMS data set encryption, and function level 506 introduces new policy controls for managing of key labels. For more information go to DB2 Administration Tool(DM) and DB2 V12 with V12R1M506
The option to use Secure SSL/TLS for TN3270 has been provided with
this ADCD release. We know the newer versions of PCOMM, after V6.0,
will not require any special action to use SSl/TLS and most third
party emulators will work as well. We believe the most current version
of PCOMM is V13 and it will only run on Windows 10 and above. If you
still have the Windows 10 box you should try it out. If you are using
a third party TN3270 emulator then you should check with owner of the
third party TN3270 emulator for assistance with implementing SSl/TLS.
USER.** libaries changed to use the ADCD release level &SYSVER, USER.Z31C, to provide uniqueness based on ADCD release level.
Console member in PARMLIB updated to allow Health Checker messages to roll off.
Accessing the ADCD z/OS 3.1 December 2024 Edition
ADCD is only available to ISVs who are enrolled in the IBM Z and IBM LinuxONE On-premises Development Program (ZOPD) with a current, valid contract and existing zPDT license/serial number.
- ISVs wishing to join the ZOPD Program may apply for admission at https://zlpn.ibm.com/zopd-application-form/
-
Existing ZOPD Program participants who need support accessing
the latest download (including password resets) may contact
ztech@us.ibm.com.
- List ADCD 3.1 December 13 2024 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.1 December 2024 Edition under zPDT
For information on the zPDT Version 11.1 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 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.
What's New in ADCD z/OS 3.1 December 2024 Edition
NOTE: As of ADCD z/OS 3.1 December 2024 Edition, distribution via DVDs has been discontinued and all future distribution of ADCD Editions will only be available via download.
The ADCD Release Guide z/OS 3.1 December 2024 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:
- CICS TS V6.2
- IBM IMS V15.5
- IBM Open Enterprise SDK for GO V1.23
- IBM Open Enterprise Foundation for z/OS V1.1.0
- IBM Z Open Automation Utiities V1.3.0
- IBM DevOps Deploy V8.0.1
- CICS Interdependency Analyzer for z/OS V6.1
- IBM Hourglass V8.1.0
- IBM Decision Runtime Manager V9.1.0
- IBM Application Discovery for IBM Z V6.1.3
The following products have been updated to PUT2409 / RSU2409
- z/OS 3.1 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.
Products contained in this release
Reported Problems, Fixes, Maintenance and Observations
- The screens for VT Terminal and TN3270 on Zowe Desktop fail to connect. A case has been opened to seek resolution.
Build Structure
| Volume | Description |
|---|---|
|
C3RES1, C3RES2 |
C3RES1
Base MVS system software target, or run-time libraries, and other
system data sets required to use TSO/E and ISPF.
C3RES2 An extension of the SYSRES volume C3RES1 and C3RES2 both are required for IPL C3RES1 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. C3RES2 is a 3390-9 volumes that are an extension of the SYSRES volume C3RES1. The volume is also required for IPL. |
| C3SYS1 |
System control data sets, such as SYS1.IPLPARM,IODF (I/O
Definition File), and system's master catalog
(CATALOG.Z31C.MASTER) reside on this volume.
C3SYS1 contains the usercatalog
USERCAT.Z31C.PRODS containing entries for
z/OS relate products.
C3SYS1 is required for IPL 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.Z31C.MASTER) reside on this volume. This volume is required to IPL. C3SYS1 contains the usercatalog USERCAT.Z31C.PRODS containing entries for z/OS related products |
| C3CFG1 |
The 'USER.**' data sets reside on this volume, they are cataloged
in the master catalog. The RACF database resides on this volume.
C3CFG1 is required for IPL 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. |
| C3USS1, C3USS2, C3USS3 |
C3USS1
Contains the Fonts, Version and zOSMF zFS files for UNIX System
Services of z/OS.
C3USS2 Contains root zFS and zFS files for UNIX System Services of z/OS C3USS3 Contains root zFS and zFS files for UNIX System Services of z/OS C3USS1, C3USS2, and C3USS3 are all required for IPL C3USS1 is a 3390-9 volume that contains the Fonts, Version and zOSMF zFS files for UNIX System Services of z/OS. C3USS2 is a 3390-9 volume that contains root zFS and zFS files for UNIX System Services of z/OS. C3USS3 is a 3390-9 volume that contains root zFS and zFS files for UNIX System Services of z/OS. |
| C3PAGA, C3PAGB, C3PAGC |
C3PAGA contains
the PLPA, common and one Local page data set.
C3PAGB contains Contain one Local page data set C3PAGC contains Contain one Local page data set C3PAGA is required for IPL Note: The loadparms that bring up DB2 or WAS have been defined to use C3PAGA C3PAGB and C3PAGC , 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. These volumes contain page data sets. The C3PAGA 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. |
|
C3PRD1, C3PRD2, C3PRD3, C3PRD4, C3PRD5 |
C3PRD1 to C3PRD5 are 3390-9 volumes that contains all z/OS products. |
| SARES1 |
This 3390-9 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. No other volumes required to IPL this Standalone volume. Use the following information: Load Address: 0Axx Load Parms: 0AxxSAM |
| Volume | Description |
|---|---|
|
C3DIS1, C3DIS2, C3DIS3 |
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. |
|
C3DBD1, C3DBD2, C3DBAR |
C3DBD1 is an 18,000 cylinder volume that contains DB2 V13 related data. C3DBD1 contains the DB2 usercatalog, USERCAT.Z31C.DB2VD. Also C3DBD1 contains all DB2 target libraries and DB2 V13 utility products. This volume is not required to IPL but is required to bring up DB2 V13. C3DBD2 is a 3390-9 volume that contains DB2 catalog and directories with HLQ DSNCD10, which are SMS managed. The volume is not required for IPL but is needed to bring up DB2. C3DBAR 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 V13. |
|
C3C620 |
C3C620 is a 3390-9 volume that contains CICS 6.2 Target, DLIB and all related data for CICS 6.2. USERCAT.Z31C.CICS620 resides on this volume. This volume is not required to IPL but is required to bring up CICS 6.2 and apply CICS maintenance. |
|
C3C610 |
C3C610 is a 3390-9 volume that contains CICS 6.1 Target, DLIB and all related data for CICS 6.1. USERCAT.Z31C.CICS610 resides on this volume. This volume is not required to IPL but is required to bring up CICS 6.1 and apply CICS maintenance. |
| C3W901, C3W902 |
C3W901 and C3W902 are 3390-9 volumes that contains target and distribution libraries for Websphere Application Services. |
|
C3IMF1 |
C3IMF1 is a 3390-9 volume that contains IMS Target, DLIB and all related data for IMS 15. USERCAT.Z31C.IMS15 resides on this volume. This volume is not required to IPL but is required to bring up IMS and perform maintenance on IMS. |
| C3KAN1 |
C3KAN1 is a 3390-9 volume that contains Target and DLIB libraries for IBM Z Monitoring Suite 1.3.0. |
| C3BLZ1 |
C3BLZ1 is a 3390-9 volume that contains Target and DLIB libraries for IBM Engineering Workflow Management 7.0.2. This volume is not required to IPL but is required to bring up RTC. |
| C3INM1 |
C3INM1 is a 20,000 cylinder volume that contains Target and DLIB libraries for Installation Manager 1.8.8. |
| Volume | Description | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| C3USR1 |
The data class DCEXTEAV is defined to allow larger than four
Gigabyte dataset allocation. With this data class and the
accompanying storage group and class, a dataset can be allocated
on the provided SMS managed volume
C3USR1.
The ACS routines are
defined so no filtering is needed. To allocate and SMS managed
dataset, specify the data class (DCEXTEAV) in the allocation JCL
and the dataset will be defined on the provided volume.
Below are
the names of the
|
||||||||||||
| C3ZCX1 |
The data class CXDC is defined to allow larger than four
Gigabyte dataset allocation. With this data class and the
accompanying storage group and class, a dataset can be allocated
on the provided SMS managed volume
C3ZCX1.
The ACS routines are
defined so no filtering is needed. To allocate and SMS managed
dataset, specify the data class (CXDC) in the allocation JCL
and the dataset will be defined on the provided volume.
Below are
the names of the
|
| Volume | Description |
|---|---|
| C3ZWE1 | C3ZWE1 is a 3390-9 volume that contains ZOWE Target, and DLIB This volume is not required to IPL but is required to bring up zOWE . |
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 C3xxxx volumes except for C3SYS1. C3CFG1 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.Z31C.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.Z31C.xxxxxx libraries be backed up regularily. When a new ADCD release is installed the USER.Z31C.xxxxxx libraries can be copied from backups to the new USER.Z31C.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.Z31C.LINKLIB
- ADCD.Z31C.LINKLIB
- SYS1.LINKLIB
USER.Z31C.xxxxxx libraries have all been built on C3CFG1 which is the only volume that should contain user data.
USER.Z31C.xxxxxx will not be changed by ADCD or System processes; thus, user updates in USER.Z31C.xxxxxx will be retained between release levels. ADCD.Z31C.xxxxxx libraries are allocated on C3SYS1 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:
- Copy the system data from SYS1.xxxxx or ADCD.xxxx to USER.Z31C.xxxxxx
- Edit, compile, or run user program against the USER.Z31C.xxxxxx item
- Re-ipl, recycle system service, or re-logon to TSO
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.
| LOADPARM | Description |
|---|---|
| CS | CLPA and Cold start of JES2. Base z/OS system functions i.e. no CICS, DB2, IMS, WAS, etc. |
| WS | CLPA and Warm start of JES2. Base z/OS system functions i.e. no CICS, DB2, IMS, WAS, etc. |
| 00 | CLPA and Warm start of JES2. Base z/OS system functions i.e. no CICS, DB2, IMS, WAS, etc. |
| CI | CLPA and Warm start of JES2. Loads CICS 6.2 and 6.1 libraries. up Starts up CICS 6.2 and RDz. |
| DB | CLPA and Warm start of JES2. Loads DB2 V13 libraries. Starts up DB2 V13 and IDz. |
| IM | CLPA and Warm start of JES2. Loads IMS 15 libraries. up Starts up IMS 15 and IDz. |
| IZ | CLPA and Warm start of JES2. Starts up z/OSMF and IDz. |
| WA | CLPA and Warm start of JES2. Loads WAS 9.0 libraries.Starts up IDz. WAS needs to be manually started. |
| AL | CLPA and Warm start of JES2. Loads all middleware libraries. Starts up CICS 6.2, DB2 V13, IMS 15, z/OSMF and IDz. |
| DC | CLPA and Cold start of JES2. Loads CICS, DB2 libraries. Starts up CICS 6.2, DB2 V13, UCD 8.0.1, RTC 7.0.3 and IDz. |
| DW | CLPA and Warm start of JES2. Loads CICS, DB2 libraries. Starts up CICS 6.2, DB2 V13, UCD 8.0.1, RTC 7.0.3 and IDz. |
| ZE | CLPA and Warm start of JES2. Loads all middleware libraries. Starts up z/OSMF, Zowe, IDz, and UCD. Other subsystems need to be manually started if desired. |
Console PF Key Settings
| Action/Command | PFKey |
|---|---|
| Display Devices | PF1 |
| Display 3270 Devices | PF2 |
| Clear Top of Screen | PF3 |
| Create a 10-line Display Area | PF4 |
| Display Address Space Information | PF5 |
| Display Outstanding Reply Requests and Error Messages | PF6 |
| Display PF Keys | PF7 |
| Scroll Display Area | PF8 |
| Display TSO Users | PF9 |
| Display Active Address Spaces | PF10 |
| Display Active Jobs | PF11 |
| Clear Bottom Screen | PF12 |
USERIDS
| Userid | Password |
|---|---|
| ADCDMST (RACF special authority) | SYS1 or ADCDMST |
| IBMUSER (RACF special authority) | SYS1 or IBMUSER |
| SYSADM (DB2 and RACF special authority) | SYS1 or SYSADM |
| SYSOPR (DB2 and RACF special authority) | SYS1 or SYSOPR |
| WEBADM | WEBADM |
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.
- All functions of the base z/OS 3.1 December 2024 Edition are at PUT2409 / RSU2409
- All functions of the CICS TS 5.6 are at PUT2409 / RSU2409.
- All functions of the CICS TS 6.1 are at PUT2409 / RSU2409.
- The functions of the DB2 12 base are at PUT2409 / RSU2409.
- The functions of the DB2 13 base are at PUT2409 / RSU2409.
- All functions of the IMS 15.1.0 are at PUT2409 / RSU2409.
- IBM Z Monitoring Suite V1.3.0 is at PUT2409 / RSU2409.
DISCLAIMER
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.