If you cannot change code or apply PTFs immediately, use a SLIP (Serviceability Level Indication Processing) trap to turn the ABEND into a non-terminating error.
//SLIPTRAP EXEC PGM=SLIPCS
//SYSIN DD *
SET,ID=TRAP113
SLIP SET,ID=TRAP113,ABEND=(113,13),ACTION=MSG,NODUMP,END
Caution: This masks the problem. Use only in non-production ADCD development environments.
Scenario: A z/OS 2.5 system attempts to apply RSU 2113 (containing PTFs UA11313 and UA12313). The job fails with message GIM24701E ** SMP/E WORK dataset allocation failed, return code 13.
Root Cause: The AD/CD workflow allocated WORK with DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120) but “13” group PTFs contained load modules requiring larger block size.
Fix: Modify AD/CD JCL to include BLKSIZE=32760 for WORK datasets and re-run APPLY with GROUPEXTEND.
The days of hunting for the latest ADCD download and wrestling with emulation scripts are fading. While the term "ADCD" still holds nostalgia for many System Z veterans, the industry has moved toward a faster, more integrated future. For the modern developer, "z/os work" is no longer about managing the operating system—it is about writing code, deploying applications, and leveraging the power of the mainframe through the same tools used for cloud development.
Understanding z/OS ADCD 1.13: A Comprehensive Guide for Mainframe Developers z os adcd 113 13 work
The z/OS ADCD (Application Developers Controlled Distribution) 1.13 is a pre-configured, customized bundle of the IBM z/OS operating system and essential middleware designed specifically for development and testing environments. Often utilized with the IBM Z Development and Test Environment (ZD&T) or the System z Personal Development Tool (zPDT), this distribution allows developers to run a mainframe environment on commodity x86 hardware. What is z/OS ADCD 1.13?
ADCD stands for Application Developer Controlled Distribution. It is not a standard IBM program product and does not receive traditional product support; instead, it is intended to help developers quickly implement a working z/OS system to focus on application development rather than complex system installation. Key features of the z/OS 1.13 ADCD release include:
Version Foundation: Based on the z/OS Release 1.13 operating system, which introduced enhancements like the z/OS Management Facility (zOSMF) and improved batch runtime environments.
Integrated Middleware: Pre-configured versions of critical mainframe software such as CICS 5.1, DB2, IMS, MQ, and WebSphere Application Server (WAS).
Language Support: Built-in support for programming languages like COBOL, PL/I, Java, and C/C++.
Simplified Booting: Consolidated LOADPARMs (e.g., "CI" for CICS) to speed up the system initialization and testing process. Z Os Adcd 1.13 - If you cannot change code or apply PTFs
z/OS ADCD 1.13 (Application Developer Controlled Distribution) is a customized bundle of the z/OS operating system and various middleware products designed specifically for application development and testing on personal systems rather than production mainframes. Core Components and Environment
Operating System: It provides z/OS version 1.13, a 64-bit operating system for IBM z/Architecture.
Middleware: The package typically includes critical subsystems like CICS, Db2, IMS, MQ, and WebSphere Application Server (WAS).
Emulation: It is intended to run on the IBM System z Personal Development Tool (zPDT) or IBM Z Development and Test Environment (ZD&T), which emulates mainframe hardware on x86-based PCs or servers.
Licensing: This distribution is restricted to development and testing only; production use is strictly prohibited. It requires a valid license agreement and an annual subscription fee (approximately $900). Working with z/OS ADCD 1.13
To perform work in this environment, you generally interact with the system through several interfaces and tools: 1. System Interfaces Caution: This masks the problem
3270 Terminal Emulators: The primary way to access z/OS is via a 3270 emulator (e.g., PCOM, Vista TN3270) to use TSO/ISPF.
z/OS Management Facility (zOSMF): Introduced in earlier releases and enhanced in 1.13, this provides a web-based interface for system management tasks, including an ISPF task that allows launching classic functions directly from a browser.
REST Interface: Release 1.13 added a REST interface that enables submitting batch jobs and retrieving job output from non-z/OS systems. 2. Common Developer Tasks Z Os Adcd 1.13 -
If the failing module uses EXCP (Execute Channel Program) or VSAM RLS, the I/O control blocks (DECBs, ECB lists) reside in the work area. A premature FREEMAIN while an I/O is pending leads to 113-13 at the next CHECK macro.
IBM’s z/OS operating system relies on a structured maintenance delivery mechanism known as AD/CD (Application Development/Component Distribution). System programmers frequently encounter cryptic identifiers (e.g., “113,” “13”) in SMP/E logs, HOLDDATA, and exception reports. The phrase “z os adcd 113 13 work” — while informal — encapsulates a real-world troubleshooting scenario: determining which PTFs, APARs, or RSU levels correspond to those numbers and how they interact with ongoing AD/CD operations.
Objectives:
Use the SDSF (System Display and Search Facility) command:
//STEP1 EXEC PGM=SDSF
//* Or from TSO/E: SDSF LOG
Look for messages resembling:
IEA995I SYMPTOM DUMP OUTPUT - ABEND=113-13
MODULE=IGC00113 OFFSET=000015A0
DATA AT PSW -...
PROGRAM=YOURPGM WORKAREA=07F2A000