CA 2E compatibilities
Article ID: 49173
Updated On:
Products
Issue/Introduction
This document explains where to find that compatibility matrix and provides some further detail on CA 2E
Environment
CA 2E 8.x
Resolution
CA 2E techdocs web site
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/ca-2e/8-7.html
** Navigating from CA 2E Product page
- Go to the CA 2E Product Page:
https://www.broadcom.com/products/software/service-management/2e - Click "CA 2E Fix Strategy" (Under Product Status).
* Overview
The strategy defines a Test Program Temporary Fix (Test PTF) and a Cumulative Program Temporary Fix (CUM PTF).
A Test PTF will typically be emailed to a customer by CA Support or CA Sustaining Engineering.
A CUM PTF will be available for download as a Published Solution.
NOTE: The CA 2E team will typically provide NEITHER individual Published PTFs (that address a single product defect), NOR Test CUM PTFs.
* Test PTFs and CUM PTF targets
Test PTFs and CUM PTFs will target the latest published Service Pack / CUM PTF. Therefore in order to use Test PTFs and CUM PTFs, customers are required to upgrade to the latest Service Pack / CUM PTF, for a supported release.
* .CAZ Test PTF/ CUM PTF packaging.
Test PTFs and CUM PTFs are now packaged using the .CAZ file format.
Documentation accompanying the Test PTF / CUM PTF will explain how to unzip .CAZ files, e.g.
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/ca-2e/8-7/CA-2E-Cumulative-Patches/ca-2e-r8-7-3/install-ca-2e-r8-7-3.html
* Problem Record updates
** Test PTF
When a Test PTF is available for a given problem, the problem record will be updated to indicate the details, e.g:
"Test PTF: Test PTF T51M006 is available and may be obtained by contacting CA Support."
** CUM PTF
When a CUM PTF is available for a given problem, the problem record will be updated to indicate the details, e.g:
"Solution: This Problem is addressed in Solution RO12345 (CUM PTF Y2860AC), or its successor. Solutions may be downloaded from support.ca.com"
* Naming conventions
** Test PTF
This section describes the naming convention for a Test PTF.
A Test PTF will be packaged in a .CAZ file.
* Txxxnnn.CAZ file
Where T = Test and xxxnnn = Test PTF Identifier.
The Txxxnnn.CAZ file will contain a "README" and a .SAV file.
** Txxxnnn.TXT - "README".
** YPMmSCnnn+.SAV
The .SAV file will contain the actual PTF objects.
The .SAV file name and Test PTF library name share a common name in the following format: YPMmSCnnn+
Y = Denotes 2E family of Products.
P = Product code: 1=CA 2E Toolkit , 2=CA 2E, W=CA 2E Web Option, T=CA 2E Translator
M = Major Release number (Version)
m = Minor Release number (Release)
S = Service Pack number.
C = CUM PTF identifier. (A through Z).
nnn = Problem record number.
+ Provides for a unique revision name (if needed).
Initially blank, then A, B, C, etc.
E.g: Y2861A401B represents revision B of a fix for Problem 401. The fix targets CA 2E r8.6 SP1 CUM PTF A.
** CUM PTF
This section describes the naming convention for a CUM PTF.
A CUM PTF will be packaged in a .CAZ file.
* ROnnnnn.CAZ file
Where RO = Auto-generated solution prefix and nnnnn = Auto-incremented solution number.
The ROnnnnn.CAZ file will contain the .SAV file. NOTE: For a CUM PTF Solution the "README" is not contained with the .CAZ file.
** YPMmSnC.SAV - PTF objects.
The .SAV file name and CUM PTF library name share a common name in the following format: YPMmSnC.
Y = Denotes 2E family of Products.
P = Product code: 1=CA 2E Toolkit , 2=CA 2E, W=CA 2E Web Option, T=CA 2E Translator
M = Major Release number (Version)
m = Minor Release number (Release)
S = Service Pack number.
n = CUM PTF identifier. (A through Z).
C = Hard coded literal to denote a CUM PTF.
E.g: Y2860AC represents CUM PTF A, targeting CA 2E r8.6 GA.
* PTF Identification data area
* Each Test PTF library and CUM PTF library contains a PTF Identification Data Area, which can be used to swiftly and accurately identify Test PTFs or CUM PTFs in a given environment, e.g:
WRKOBJ OBJ(*LIBL/YHFM*) OBJTYPE(*DTAARA)
** Naming convention
YHFMnnnnn
Y = Denotes CA 2E family of Products.
HFM = Literal for backward compatibility to find Test Fixes from the prior Traditional 2E Fix Process.
nnnnn = Internal 2E MOD identification number.
* Searching for Problems and Solutions
There are many ways to locate Problems and Solutions on support.ca.com
** Search for Problem number on support.ca.com
E.g. Enter C22E 460 in Search field
** Search for Solution (CUM or PIB) number on support.ca.com
E.g. Enter RO50607 or RI51323 in Search field
** Download Center > Published Solutions on support.ca.com
Lists Solutions and PIBs (Product Information Bulletins)
* CA 2E Solutions & Patches
** Direct Link
A direct link to the CA 2E Solutions & Patches can be found here:
https://support.broadcom.com/group/ecx/productdownloads?subfamily=2E
** Navigating from CA 2E Product page
- Go to the CA 2E Product Page:
https://support.broadcom.com/group/ecx/productdownloads?subfamily=2E - From this product page you can click to go to support, tutorial and others
* Forum announcements
The CA 2E Product Team will typically not make an announcement on the Communities Message Boards.
Rather, important or urgent announcements will be made using the Hyper PIB mechanism.
* Test PTF Clashes
Test PTFs target the latest Service Pack/CUM PTF.
Therefore Test PTFs are not designed to work with each other and results are unpredictable. The email documentation accompanying a Test PTF warns of such Test PTF clashing.
Test PTF clashes will be resolved during merge/build of a CUM PTF.
* Documentation issues
All resolutions to documentation issues will result in the publication of a PIB (Product Information Bulletin). If the impact is significant, the PIB will be marked as Hyper.
The documentation set will be updated in the subsequent Service Pack or Release.
* Feedback
If you have any comments, questions or concerns on the CA 2E Fix Strategy or Process, please do contact support.broadcom.com.
Attachments
Feedback
