Datacom GA Announcement: Continuous Delivery Service Update S2501 for Datacom Core Products 15.1

[Rajesh Mandava]

As part of our Enable strategy, the Datacom team is pleased to announce the publication of Service Update S2501 for Datacom Core Products 15.1.

Feature Overview                                            
This service update for Datacom Core Products consolidates all Version 15.1 features and fixes into one unified upgrade. It includes maintenance through CARS 2501 and Level Set 15.1.06 and is effective April 2025.

• BD.V15R1.CARS2501.CLASSIC.pax.Z (a single pax file for SMP/E installation)
• BD.V15R1M6.ZOSMF.pax.Z (a PSWI file for installation with z/OSMF workflows)

Key Benefits
Using the latest Service Update S2501, you can easily upgrade to Datacom/DB 15.1 from an earlier release or update libraries to the latest level of maintenance.

To learn more, please visit our New Features in TechDocs. We also encourage you to visit the product information and review the product documentation

-----------------------------------------------------
Rajesh Mandava
Product Owner, Datacom Product Family
Broadcom Software
-----------------------------------------------------

[a.elbachiri]

Hello,

I need to clarify some points about Level of Datacom DB :

• Is there any dependencies between Datacom Core Level and Datacom Tools levels (Ideal, Cics Services Facility, IPC, CCS). For exemple, If I install CA DATACOM DB level set 15.1.06, is there any requirements for CA IDEAL 15.1 and others or not?
• Is BD.V15R1M6.ZOSMF.pax.Z a new installation Package that include all PTFS up to Level Set 15.1.06 ? if so, what about post deployment process and upgrade process, if there is any?
• Could you share a small document to show the differents paths and scenarios to get to Level Set 15.1.06 ? Exemple : Installing all individuals PTFs, installing PTF for level set and its pre-requisite, installing ZOSMF PSWI, etc.

Best regards,

[Kenneth Eaton]

Hello

Question dealing with IDEAL, CICS Services, IPC and Common Services is
generally not an issue but if there is an intersection you will have
a ++HOLD for action if there is one. Generally each Datacom product PAX is
somewhat independent for the most part other than they need Datacom?DB core
has to exist for them to work.. Ths assumes you are running GA code for
all of these Broadcom products and running supported IBM releases.

Clients can be many years back on maintenance for Datcom/DB Core plus any
mix of hyper going back over 8 to 9 years.

Key item to pay attention to is ++HOLD for actions. WHen you do the
receive action on the pax you will get a list of ++HOLD with action. You
will need to review that for each MUF instance you will be adding this
maintenance level from this PAX that matches that SMP/E environment. You
may have more than one SMP/E environment for DB 15.1 DB core and if so you
will need to repeat this process.

All sites by now are supposed to be running 15.1 for DB CORE products.
Support for older versions of the code have long ago ended for Datacom DB
core products so in theory no upgrade paths are needed. There are no
real JCL structural changes from SU2401 to SU2501 for new install and
upgrades.

One item to note on the ++HOLD action for module DBPCCPR is a module loaded
by CAIRIM or CAS9 at the LPAR level. Every LPAR that can run any
Datacom/DB code will need to have this process executed. Be sure the
library that you are using by CAIRIM or CAS9 points to the
maintenance library you are wanting to use for this new Service update
2501. Some sites use a one off placeholder library for this process so
you may need to copy this module to that place if you do this kind of
processing.

++HOLDs for action should drive your requirements. You will need to proceed
for all of your MUF instances to apply this maintenance based on your
schedule. This list will be different if not all of your MUF instances
are not running the same level of base code.

This pax has code on it that is past level set 15.1.06.

regards

Ken Eaton

--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.