CA Common Services for z/OS
Installation Bulletin for r12 SP00
Last Updated: November 24, 2011
Please review the following items and all Product Bulletins.
- This is a new release of CA Common Services for z/OS therefore you must perform a new installation. Applying maintenance to your existing CA Common Services r11 for z/OS installation is not an option for upgrading to the r12 level.
- The new release of CCI introduces a couple a changes that may impact your ability to establish peer-to-peer connections as before. The first change involves the new programs and default Port#'s. The second change involves how CCI will resolve the hostname for the system.
- The CCI procs use new programs, so be sure to replace your existing procs with the new procs that are delivered. Also be aware that while the CCITCP/CCISSL procs will continue to use PORT# 1202, the CCITCPGW/CCISSLGW procs will now default to PORT# 1721. Review the PROTOCOL and NODE control options in the Reference Guide for details on how to override the default PORT#.
- Please review Technical Document TEC552083 for information about how CCI changes the way host name is assigned for a given MVS system.
- This new release must be installed into a new SMP/E environment. This new release incorporates new FMIDs, changes in DDDEFs, and changes to Target & Distribution data set names.
- An IPL is required to implement r12. An IPL is also required to backout to a previous release.
- Please refer to solution RI19438 before implementing r12. This common upgrad solution identifies any HIPER and/or highly recommended PTFs that are above the base r12 level. It is recommended that the solutions pertaining to the componets you installed be applied before implementing r12 for the firs time. This solution is a "living document" and will periodically be updated as needed.
- ENF r12 no longer requires a database. A database is only required if you are running a CA Product that records events or does checkpointing. If a database is required, ENF r12 is now using CA Datacom/AD as its database. A review of the CA Common Services r12 for z/OS Release Notes will let you know if CA Datacom/AD is required. The CA Common Services for z/OS r12 Best Practices Guide can also be used as a reference.
- DCMs provided by CA Common Services and CA Products are no longer installed into a data base. Instead they are defined via DCM statements in the ENFPARMS file. An ENF utility called ENFUTIL is provided to help define the necessary DCM and EVENT statements based on information found in your current r11 ENF data base. Please refer to the CA Common Services for z/OS r12 Reference Guide and the CA Common Services for z/OS r12 Best Practices Guide for more information.
- CA products that make use of the CAIENF common service and deliver product DCM modules which define ENF events, require maintenance to be in place in order to be compatible with CA Common Services r12 for z/OS. Review the table below and if you are running any of the CA products at the release shown, make sure that the listed PTF is applied in your running environments. The below PTFs are compatible with CA Common Services r11 for z/OS with CAIENF PTF QO88354 applied. PTF QO88354 has been available since May 22, 2007 and was included with CCS r11 service pack 8. Therefore there is a reasonable chance you already have QO88354 applied. With CCS r11 PTF QO88354 applied, you can apply any of the below PTFs before upgrading to CA Common Services r12.
|CA Product ||Release ||Required PTFs|
|CA Scheduler ||9.1 ||RO06409|
|CA Scheduler ||11.0 ||RO06408|
|CA 7 ||11.0 ||T5DR044 (Contact CA 7 support for fix)|
|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 PDC RI10078)|
- Due to a problem identified with CCI solution RO19322, please do not attempt to install it. New solution RO19624 has been made available as a replacement.
- If performing a pax (tapeless) based install, take note that when editing the UNZIPJCL job, the value for yourHLQ cannot exceed 19 characters. This is to account for the ".CCSESD" qualifier that is included in the JCL as provided, and to adhere to the RFPREFIX restriction of 26 characters.
- Due to the ease of applying a large number of PTFs with CA MSM, there is a greater likelihood of not having enough directory blocks in the delivered SMPWRKn DDDEF allocations. Please run the UCLIN found in RI32190 to increase the number of dir blocks on the SMPWRKn allocations.