IDMS Release and Software Maintenance Delivery - Aggregate Maintenance

Discussion created by Gary_Cherlet on Apr 12, 2011
Latest reply on Apr 27, 2011 by Gary_Cherlet
Hi Everyone,
I'm writing in response to the original questions from Richard Jenks.
[color=#1B03FA]1. Is the drop date of 16 on January 31, 2012 a firm date?[color]
Yes. As Tommy Petersen pointed out, the original IDMS 16 End of Service (EOS) date was August 2011, but we pushed it out to January 31, 2012 so you could go directly from r16 to IDMS 18 z/OS if you like.
[color=#1B03FA]2. What is the status of 18?[color]
The status of IDMS Version 18.0 for z/OS is that it entered beta testing yesterday January 26, 2011. Our target date for GA is the end of May 2011. If you are interested in the 18.0 beta program, go to the IDMS 18 entry at (requires sign on to CA Support Online) and read about the beta program and register for it. Among many other features (including more zIIP), IDMS 18 installs and deploys with CA Mainframe Software Manager (MSM). We have room for a few more sites to test, so check it out.
[color=#1B03FA]3. What is the status of 17 service pack 2?[color]
With Mainframe 2.0, CA Technologies has changed how we deliver maintenance. We have adopted two new methods, Aggregate Maintenance and CA Recommended Service (CA RS).

Aggregate Maintenance (AM). Similar to (and replacing) Service Packs, about twice a year we will issue Aggregate Maintenance for IDMS which will be an electronic package of PTFs for a specific period of time, typically six months. CA is supposedly abandoning the Service Packs for recommended service packs (CA RS in MSM), there will not be a dedicate SP2 for IDMS, but RO22608 is a collection of published updates
PROBLEM IDMSDC 3244 explains how to combine all PTFs into one Source.
RO22608 Collection of Publisehd APARS
Problem Document
Problem Description:
The Aggregate Maintenance solution for IDMS (RO22608) contains instructions for receiving the PTFs contained within the solution. The following SMP/E syntax can be used in place of Step 3 in the instructions to assign a "sourceid" to all PTFs within the solution. Use of the "sourceid" parameter provides the ability to "apply" and "accept" all ptfs without having to code individual SMP/E statements for each PTF.

3. Receive the Maintenance.
A sourceid of "RO22608" will be assigned to all PTFS. To apply and accept all PTFs, the following SMP/E syntax would need to be used.
** Important **
Prior to applying and accepting the PTFs you will need to review the "++HOLDDATA"
To Apply:
To Accept:
CA Recommended Service (CA RS). CA RS provides fixes that have been testing with all IDMS software and all other CA mainframe software in our in our Integrated System Test (IST) labs. CA RS will be available quarterly. For IDMS this is planned to start in the fall of 2011.
For more info on AG and CA RS see

[color=#1B03FA]4. Is CA only going to support one version of IDMS?[color]
No. In fact from May through January 2011, we'll be supporting IDMS 16, 17 and 18 for z/OS. Typically we'll be supporting the current GA release, and one previous. End of Service date for 17 has not been announced, and typically we provide 18-24 months notice.
Greg Beedy
CA Sr Principal Product Manager
CA Recommended Service (CA RS)
As part of the Mainframe 2.0 strategy, CA Technologies is keeping our promise to simplify software management by delivering CA Recommended Service (CA RS). CA Recommended Service identifies PTFs that have passed additional quality validation criteria over a measured time cycle. CA RS is patterned after IBM's preventative maintenance model, Recommended Service Upgrade (RSU), which has been widely adopted.

CA Technologies created a mainframe Integrated System Test (IST) environment for the continuous testing of published service (PTFs) for the products in the CA Technologies Mainframe Stack for z/OS. The products that comprise the CA Technologies Mainframe Stack can be found at All of these products have been implemented at their latest GA release across the IST multiple system sysplex. The IST environment runs all supported releases of the z/OS operating system and multiple releases of IBM subsystems (CICS, DB2, IMS) which are maintained at quarterly IBM RSU levels.

CA Recommended Service is a list of ++ASSIGN statements for all regular PTFs that have been tested in the IST environment for at least 90 days and for all HIPER PTFs that have been validated for at least 30 days. A SOURCEID of CARyymm is part of the ASSIGN statement. CA RS will be delivered quarterly, beginning in October 2010. You can review the CA RS Quarterly Report for complete information on what is included.

CA Mainframe Software Manager (CA MSM) 3.1 introduces automated support for CA RS. Using CA MSM, you can schedule product catalog updates to receive service (published PTFs) for the products you have licensed. You can also use CA MSM to receive the CA Technologies ERROR HOLDDATA bucket, and then apply the CA RS level as part of your ongoing preventative maintenance cycles. Customers who have not yet adopted CA MSM can also benefit from CA RS, though the manual processes are more time consuming.
Because CA RS provides a new preventative maintenance methodology, service packs will no longer be delivered for the product releases in the CA Technologies May 2010 Mainframe Stack and beyond. Of course, you can RECEIVE and APPLY service anytime for corrective maintenance. CA RS provides IST-verified preventative maintenance across the entire CA Technologies Mainframe Stack, giving you a way to manage risk while keeping your CA Technologies software environment up to date.

Obtaining CA Recommended Service using CA MSM r3.1

Obtaining CA Recommended Service without using CA MSM

CA RS Quarterly Report 1010

CA RS Quarterly Report 1101

CA MSM Product Page


Paul Mak
Database Administrator – CA-IDMS & ObjectStar
Best Shore Application Services
HP Enterprise Services, South Pacific
Telephone +61 2 9022 2604
Mobile +61 419 398 116