CA Technologies

CA Common Services for z/OS Release 14.1 Readme


1.0 Welcome

2.0 Known Issues
2.1 JCL Procedures
2.2 Changes and Obsolescence
2.3 Switch to CA Datacom/AD v14.0
2.4 CICS JCL Review
2.5 Apply Necessary Fixes
2.6 CAS9SAFC USERMOD Elimination
2.7 CA Easytrieve
2.8 CAICCI PORT#s
2.9 CA Master Distribution Data Sets

3.0 Contact CA Support


1.0 Welcome

Welcome to the CA Common Services for z/OS readme. This readme contains issues and other information that is discovered after publication or items of emphasis. For a complete list of the known issues for this release, and details about how the features and enhancements affect you, see the Release Notes. If you skip over a release when upgrading to r14.1, review the Release Notes for each release that occurred between your current release and r14.1.


2.0 Known Issues

2.1 JCL Procedures

Use the JCL procedures that come with this release. Do not use any existing JCL procedures that you have from previous releases.

2.2 Changes and Obsolescence

Review the Release Notes for important information about changes to data sets. CA Common Services r14.1 only delivers new levels of the Base and Optional Common Services. Legacy and MFNSM Common Services remain at version 14.0 levels. CCCSxxxx and CNSMxxxx low-level qualifier data sets must remain in place and must continue to be used.

You can install CA Common Services r14.1 into a new SMP environment or you can install CA Common Services r14.1 into the same SMP environment as CA Common Services v14.0. If you are upgrading from an older than v14.0 release of CA Common Services you must install r14.1 into a new SMP environment.

If you install CA Common Services r14.1 into a new SMP environment, your new environment will only contain the CCS Base and Optional components. You can continue to use your older v14.0 SMP environment for CCS Legacy and/or MFNSM components. You may wish to clean up the Base and Optional FMIDs from the older v14.0 SMP environment. To do so you can run sample JCL member CAW0CLN, which can be found in the CCS r14.1 CAW0JCL dataset.

2.3 Switch to CA Datacom/AD v14.0

CAIENF r14.1 is designed and documented to be used with CA Datacom/AD v14.0. CAIENF r14.1 sample jobs and procs are constructed to be used with CA Datacom/AD v14.0. CAIENF users that have RECORD(YES) specified should upgrade to CA Datacom/AD v14.0 either at the same time as the CA Common Services r14.1 upgrade, or ahead of time utilizing CAIENF r14.0 PTF RO44982, which allows CAIENF r14.0 to be run with CA Datacom/AD v14.0. When you switch to Datacom/AD v14.0, start CAIENF with a newly initialized CAIENF database. You do not need to migrate any data from the old ENF database.

CAIENF r14.1 is still compatible with CA Datacom/AD v12.0, but we recommend upgrading to CA Datacom/AD v14.0 as soon as possible. If you decide to delay upgrading to CA Datacom/AD v14.0, you must import the CAIENF r14.1 Datacom Plan into the Datacom catalog using the sample AW1IMPRT job from your 14.0 CAW0JCL data set. The CAIENF r14.1 plan has a new name so it can be imported with CAIENF up and running ahead of your CCS r14.1 upgrade.

Sites that use Event Management Calendars or Message Actions also need to upgrade the shared CAIENF MUF to CA Datacom/AD v14.0. Sites can either redefine their Calendars and/or Message actions in an AD v14.0 Event Management newly initialized database, or they can use the CA Datacom/AD database backup and restore utility to migrate the Event Management database from an AD v12 database to an AD v14.0 one.

Sample Datacom v12.0 Event Management database backup JCL:

//BKUPSTP  EXEC PGM=DBUTLTY,REGION=1M                   
//STEPLIB  DD DSN=&ADHLQ.CUSLIB,DISP=SHR                
//         DD DSN=&ADSHLQ.CAAXLOAD,DISP=SHR             
//CXX      DD DSN=&CXXHLQ.CUSTOM.CXX,DISP=SHR 
//DBK00001  DD DSN=&CAIEMBK..BK1011,DISP=(NEW,CATLG),   
//        UNIT=&BKUPU,&BKUPVOL,SPACE=(CYL,&BKUPCYL)     
//SNAPER   DD  SYSOUT=*                                 
//SYSOUT   DD  SYSOUT=*                                 
//SYSPRINT DD  SYSOUT=*                                 
//SYSUDUMP DD  SYSOUT=*                                 
//SYSIN DD *                                            
COMM OPTION=CLOSE,DBID=1011                             
BACKUP DBID=1011,DDNAME=DBK00001,SEQ=PHYSICAL           
/*      
                                                

Sample Datacom v14.0 Event Management Restore JCL:

//DBUTL EXEC PGM=DBUTLTY,REGION=4M                                 
//STEPLIB DD DISP=SHR,DSN=&ADHLQ.CUSLIB                            
//        DD DISP=SHR,DSN=&ADSHLQ.CAAXLOAD                         
//*                                                                
//EM00001 DD DISP=SHR,DSN=&BKHLQ.CUSTOM.BK1011      
//*                                                                
//EM01011 DD DSN=&EMDBHLQ.DCOMAD14.EM01011,
//        DISP=(NEW,CATLG),
//        SPACE=(TRK,(375,50)),          <=== CHANGE               
//        UNIT=SYSDA,VOL=SER=vvvvvv           <=== CHANGE          
//IXX1011 DD DSN=&EMDBHLQ.DCOMAD14.IXX1011,
//        DISP=(NEW,CATLG),
//        SPACE=(TRK,(175,50)),          <=== CHANGE               
//        UNIT=SYSDA,VOL=SER=vvvvvv           <=== CHANGE          
//*                                                                
//CXX     DD DISP=SHR,DSN=&ADMHLQ.&CXXNAME.CXX                      
//*                                                                
//SYSIN DD *                                                       
INIT DBID=1011,AREA=IXX                                            
INIT DBID=1011,AREA=EM0                                            
LOAD DBID=1011,DDNAME=EM00001,FORMAT=BACKUP,                       
SORT=10000000,OPTIMIZE=YES,KBYTES=500                              
/* 

2.4 CICS JCL Review

When implementing CA-ENF/CICS Release 14.1, you must review all CICS JCL to determine if a region runs with a private area copy of the CA ENF/CICS intercept module CAS9Cxx (where xx is the CICS release number 64-67).

A CICS region loads a private area copy of the intercept module if the module resides in either the CICS STEPLIB or a special DD in the CICS JCL called CENFLIB. If you determine that a CICS region is running in such a manner under an older CA Common Services release, modify the JCL to point to the new CA Common Services CAW0LOAD data set at the time when CA Common Services r14.1 is implemented. Failure to do so can lead to unpredictable results.

2.5 Apply Necessary Fixes

To ensure proper operation, apply the necessary fixes provided by CA Technologies.

Note: If a higher release of the following CA products is available, the required PTFs are included with that release.

CA Product Release Required PTFs
CA Scheduler 9.1 RO06409
CA Scheduler 11.0 RO06408
CA 7 11.1 RO06863
CA Jobtrac 11.0 RO06413
CA CPM for Scheduler, 7 or Jobtrac 3.0 RO06862
CA Dispatch 11.0 RO02756 (Also see PDCRI10078)
MSM 3.1 RO31485
    RO44241
  4.1 RO42491
CAICCI (Compatibility) 12.0 RO28817
CA Easytrieve Plus Report Generator 11.6

RO42229

RO42230

RO42231

CAIENF 14.1 RO46101

The following PTFs are included with the CCS r14.1 optional services SMPMCS as PTFs that must be applied on top of the installed FMID.

CA Product Release Required PTFs
GSS 14.0

RO31779

RO34310

RO39025

RO42823

RO43136

RO44289

RO45372

RO45564

XPS 14.0

RO35679

RO44367

RO45565

2.6 CAS9SAFC USERMOD Elimination

Review the Release Notes Changes to the Customization Required for RACF Sites section.

2.7 CA Easytrieve

CA Easytrieve Common Reporting Service has been discontinued and replaced with CA Easytrieve r11.6, the full product. This product operates in a CA Common Service-restricted manner if the full product LMP key is not installed. CA Easytrieve Plus Report Generator r11.6 PTFs RO42229, RO42230, and RO42231 must be applied for the common service functionality to work properly. CA Easytrieve r11.6 is packaged in its own pax file now and is not part of the CA Common Services r14.1 pax files. This reduces maintenance for environments that currently have multiple releases of both EZT CCS and full blown EZT since now there is a single EZT instance.

The CA Easytrieve r11.6 installation process builds a separate SMP environment for CA Easytrieve. If CA Common Services r14.1 is being installed into the same SMP environment where CA Common Services v14.0 was installed, clean up the old release of the CA Easytrieve Common Service (r6.4) from this SMP environment. CA Common Services r14.1 supplies a sample job, CAW0EZTD, in the CAI.CAW0JCL dataset that must be used to delete the old release of the Easytrieve Common Service from the CA Common Services r14.0-14.1 SMP environment.

2.8 CAICCI PORT#s

If you are upgrading from a CA Common Services release below v14.0, the CCITCPGW/CCISSLGW procs now default to PORT# 1721. Review the PROTOCOL and NODE control options in the Reference Guide for details about how to override the default PORT# if you want to revert to the previous default PORT# of 7000.

2.9 CA Master Distribution Data Sets

The Installation Guide does not include the following information for CA Master. This information should appear under the Component Installation Requirements. The second edition of the Installation Guide will have this information.

Library Name Block Size Tracks Directory Blocks
CAI.AEI0MOD 6144 31 -
CAI.AEI0SCST 0 1 1
CAI.AEI0XML 32760 29 1


3.0 Contact CA Support

Contact CA Support

For your convenience, CA Technologies provides one site where you can access the information you need for your Home Office, Small Business, and Enterprise CA Technologies products. At http://ca.com/support, you can access the following: