CA Common Services for z/OS
Installation & Maintenance Bulletins
r11 Service Pack 7
Last Updated: January 18, 2007
CA Common Services r11 z/OS Service Pack 7 (SP7) is the successor to CA Common Services r11 for z/OS Service Pack 6 (SP6).
Please review the following items and all Product Bulletins.
- An IPL may be required to implement this new service level as a result of enhancements to the CAIRIM and ENF/USS common services. Please refer to the following sections for more details.
- New Common Services are being delivered on this tape as they were on the prior SP6 tape. Please review the Cover Letter and the Release Summary for descriptions of these new services. The Release Summary is available in softcopy both on the tape and on Support Connect along with the other CA Common Services documentation.
- A new release of the ENF subcomponent, ENF/USS, is being delivered on this tape. This new release provides support of Unix System Services (USS) applications in 64-bit addressing mode. ENF/USS r2.1 will replace (delete) ENF/USS r1.0.
- A new release of CAICCI is being delivered on the tape as it was on the prior SP6 tape. CAICCI r2.1 should be installed. This new release of CCI will replace (delete) CCI r1.1. Support for CCI r1.1 will be discontinued December 31, 2007. CCI r2.1 requires z/OS 1.3 or higher.
- A new Common Service, FMID CAG3000, is being delivered on this tape as it was on the prior SP04, SP05, and SP6 tapes. This new FMID represents CA-Viewpoint release 3.0 and replaces FMIDs: CAG2300, CF62300, CSP2300, CTB2300, CBS2300, CIF2300, and CWC2000. If this FMID was previously installed then maintenance is available at the SP7 level. If you have not yet installed this new FMID, it is recommended that you follow the installation steps as outlined in the ViewPoint Installation Checklist located in Appendix A of the Getting Started Guide.
- A new version of ENFSNMPM (called CAW1SNMP) is delivered on this tape, as it was on the prior SP04, SP05, and SP6 tapes. It provides additional functionality for use with eTrust Audit. The Getting Started Guide documents how to utilize the new monitor. This new version requires OS/390 2.10 (with PQ44370/UQ51618 for LE) or higher. Running at a lower level will result in an error during SMP/E APPLY processing while attempting to link-edit CAW1SNMP. (i.e. IEW2456E SYMBOL __osname UNRESOLVED)
The "old" ENFSNMPM proc and related CAS9SNMP program are no longer delivered. They have been removed at this service level by APAR QO74277.
- If upgrading the CAIENF/DB2 component from a level prior to SP05, an IPL will be required. Beginning at the SP05 service level, support for DB2 v8.1 was made available. If you are already running DB2 V8.1 and have implemented ENF/DB2 APAR QO61463, then an IPL is not required on behalf of ENF/DB2.
- If upgrading from a level prior to Service Pack 1 (SP01), an IPL is required in order to implement CAICCI/MVS or CAIENF/DB2 maintenance.
- If upgrading from a level prior or equal to 9909, it is highly recommended that a new base install be performed as opposed to a maintenance upgrade.
- If upgrading from the SP02 level, a RC=8 on the maintenance APPLY or APPLY CHECK is possible using SMP/E on z/OS 1.2 where UR53295 has been applied. To avoid this possibility, please run SAMPJCL job W010MUCL before running the SMP/E APPLY.
- The various GENLEVEL stamps for the previous two levels, including the current SP7 level are as follows:
SP05 stamp is LVL200407. The CAS9075I message will report Genlvl(SP05...)
SP6 stamp is LVL200506. The CAS9075I message will report Genlvl(B006...)
SP7 stamp is LVL200606. The CAS9075I message will report Genlvl(B007...)
- The various past and current tapes are as follows:
CA90S Services/MVS Release 1.0 Genlevel 9901 ( March 1999 )
Unicenter TNG Framework for OS/390 r2.2 9909 ( August 2000 )
Unicenter TNG Framework for OS/390 r2.2 SP01 ( February 2001 )
Unicenter TNG Framework for OS/390 r2.2 SP02 ( December 2001 )
CA Common Services for z/OS and OS/390 r2.2 SP03 ( November 2002 )
CA Common Services for z/OS and OS/390 r3.0 SP00 (SP04) ( October 2003 )
CA Common Services r3.0 for z/OS SP05 ( January 2005 )
CA Common Services r11 for z/OS SP6 ( September 2006 )
CA Common Services r11 for z/OS SP7 ( August 2007 )
- Included with this service level and the prior SP6 service level are some LMP enhancements (refer to: QO66300). These enhancements primarily pertain to LMP warning/violation messages. As a result of these enhancements an IPL may be required to implement or back out this new service level. If SP6 or QO66300 have already been implemented, then an IPL is not necessary for this reason.
- For those customers that only utilize the CAIRIM component, beginning with the SP6 service level, a DDDEF for CSSLIB is required. If installing for the first time, the definition for the CSSLIB DDDEF is already included as part of the installation process, within SAMPJCL member W010DDEF. If applying maintenance to a previously installed copy of CAIRIM, you must first define the DDDEF. In order to accomplish this, you have a few options. You can manually define the DDDEF using the SMP/E administration panels; you may customize and run W010DDEF; or you may run the following UCLIN against your SMP CSI.
//SMPCNTL DD * SET BOUNDARY(CAITGT). UCLIN. REP DDDEF(CSSLIB) DA (SYS1.CSSLIB) SHR. ENDUCL.
UCLIN. REP DDDEF(CSSLIB) DA (SYS1.CSSLIB) SHR.
ENDUCL. /* //
CAIENF and CAICCI
- Support for the CAICCI r1.1 "C" versions of CCITCP and CCITCPGW will be dropped after September 30th, 2006. You are encouraged to install CAICCI r2.1 which does not deliver the "C" versions of this code. If you choose to continue to use CAICCI r1.1 you should use the assembler versions of the code by updating your CCITCP and CCITCPGW procs to reference programs CAS9ATGS (CCITCP) and CAS9ATPS (CCITCPGW). The assembler versions remove all requirements to run W010LINK. Support for CAICCI r1.1 in its entirety will be discontinued after December 31, 2007.
The CAICCI r2.1 FMID CW42100 will delete the CAICCI r1.1 FMID CW41100 in the target data sets. If you want the flexibility to be able to back out only CAICCI r2.1 and run with CAICCI r1.1, but with the remainder of the Common Services at the r11 SP7 level, you may wish to spend the time to setup target data sets that only contain CAICCI r1.1. This would allow you to switch between the two versions of CAICCI. You can then run CAICCI r1.1 by concatenating the CAICCI r1.1 target CAILIB data set ahead of the full CA Common Services target CAILIB data set in either the system linklist or STEPLIB (in ENF, CCITCP, and CCITCPGW procs). Remember that an IPL is always necessary to switch between the different releases of CAICCI. In order to apply only CAICCI r1.1 FMID CW41100, you must specify BYPASS(PRE) on the SMP/E APPLY statement.
- New datasets are needed for ENF (and CCI).
( Note: If you have already upgraded to SP04, SP05, or SP6 then this item does not apply to you )
The new datasets are CAIPDSE, CW110LPD, and SMPLTS. These are PDSE libraries and must be allocated as such. If a new install is being performed then these new libraries will be allocated during the install process. If maintenance is being performed, then maintenance Step 13 will direct you to run SAMPJCL member W010MALC to allocate the additional libraries.
- For those clients preparing to apply maintenance to any of the installed CAIENF components (i.e. CAIENF/CICS, CAIENF/DB2, CAICCI and CAIENF utilities) that are still at a level prior to SP04, an error indicating insufficient directory blocks may occur when ACCEPTing this maintenance. The error refers to the distribution library CAI.W110.CW110LLD. To prevent this error, it is necessary to first allocate a new larger CW110LLD dataset and copy the contents of the old CW110LLD dataset to the new one. The recommended space parameter for the new CW110LLD DLIB is as follows: SPACE=(6144,(3500,200,175)).
- With the introduction of APAR QO64745, which was delivered starting with the SP6 service level, it is required that modules CAS9UDTN and CAE$BQRY be added to the AUTHCMD table of IKJTSOxx.
- DCM CAL2DCM2 (CA-XPS event) was updated at Service Pack 6
DCM CAS9DCM0 (ENF base events) was updated at Service Pack 5
DCM CAS9DCM4 (CAIENF/SNMP Monitor) was updated at Service Pack 4.
Depending on the service level you are upgrading from, you may need to update your ENF database to replace any of the above DCM's that may currently be installed. Use the CAS9DB utility to re-install the DCM using the replace option. Following is some example JCL. Please refer to the CA Reference Guide for further details.
//CAS9DB1 EXEC PGM=CAS9DB,REGION=4M //*ENFDB DD DISP=SHR,DSN=cai.enfdb //DBOUT DD SYSOUT=* //DBIN DD * INST DB(*) ID(CAS9DCM4) REPLACE * * USE THE FOLLOWING CONTROL CARD IF ENF IS NOT ACTIVE. THE FOLLOWING METHOD * REQUIRES THE //ENFDB DD STATEMENT BE MODIFIED AND UNCOMMENTED. * * INST DB(ENFDB) ID(CAS9DCM4) REPLACE * /* //* NOTE: The ENF task must be recycled in order for this change to take effect.
- Beginning at the CA Common Services r11 SP6 service level, a small change was made to one of the CAICCI messages that get generated during the initialization of either the CCITCP or CCITCPGW task. This change applies to both CCI r1.1 and CCI r2.1. The change involves the CAS9850I message:
CAS9850I - CCI TCP/IP Server Ready. Port =
CAS9850I: CCI TCP/IP Server Ready. Port =
While there was no technical problem due to this change, we have had reports that this has affected some automation rules previously defined by our customers. Please take note of this change if you are keying off this message for any reason.
CA-GSS and/or GREXX
- GSS solution QO58462 is not included with the current SP7 maintenance. If this solution was previously applied, you will need to re-APPLY after completing the upgrade to the SP7 service level.
- For those clients who are applying maintenance to an SP01 or earlier level of CA-GSS and GREXX, an error will be seen on the ACCEPT of SP01 (or earlier release) indicating insufficient directory blocks. A formatting discrepancy exists in the old CYS28LLD library, and a similar formatting discrepancy exists in the old CJD41LLD library. In SP01 and prior the CYS28LLD and CJD41LLD distribution libraries were improperly allocated causing libraries to become corrupted if maintenance were ACCEPTed. The following steps are required to insure that the CYS28LLD and the CJD41LLD distribution libraries are updated correctly if maintenance is being done:
Note: It is NOT necessary to follow these steps if a base install of GSS and GREXX is being done at the SP7 level, or if a base install of GSS and GREXX was done at the SP02, SP03, SP04, SP05, or SP6 levels. It is only necessary if the base install of these products was done prior to SP02.
Step 1: After downloading the SAMPJCL from the SP7 tape, edit SAMPJCL member YS28LLD. First change the job as described in the comments. Second, make the following changes:
Change: LABEL=(XX,SL,EXPDT=98000) to LABEL=(131,SL,EXPDT=98000) for the //IN DD for jobstep COPYJD41. Change: LABEL=(YY,SL,EXPDT=98000) to LABEL=(132,SL,EXPDT=98000) for the //IN DD for jobstep COPYYS28. Submit this job. This job will create new CYS28LLD and CJD41LLD libraries and load these libraries from the install tape. The old libraries will then be renamed to CYS28LLD.O and CJD41LLD.O and the new libraries will be renamed to the production DLIB names. This expands the library in order to accommodate the new maintenance.
Step 2: RECEIVE, APPLY and ACCEPT the maintenance as normal. It is important that the maintenance PTF's LYS2807 and LJD4107 be accepted in order to correctly synchronize SMP/E with the new DLIBs.
- Agent Technology release 3.0 was first delivered on the previously available CA Common Services 3.0 SP00 tape [We sometimes reference SP00 as SP04]. The new FMID is CID3000. If this new release was previously installed, maintenance was last made available at the SP05 level. If you have not yet installed this new release, you can do so using this SP7 tape. An install using this SP7 tape will contain the current maintenance. Therefore no additional maintenance steps need to be performed. An install of this new release will attempt to delete all previously installed releases of Agent Technology.
- With Agent Technology 3.0, the LOADLIB is no longer created as part of this install. All executables will now be linked into the CAI.CAILIB data set. Please review the startup JCL for all MVS regions that run z/OS agents. Any JCL references to an Agent Technology LOADLIB must be removed before attempting to use an agent with Agent Technology 3.0. This change has also been documented in QI44260.
- If you have Agent Technologies already installed at the 2.2 release, the transition to release 3.0 involves a complete re-install in a new set of HFS files. Formerly only an R/W HFS was used for everything. With release 3.0 the HFS structures have changed significantly by splitting into two HFS files: a read-only file system and a read-write file system. (However, during the install both of the files need to be mounted read-write and the 2.2 file should be unmounted.) For processing after the install and post-install are done, the read-only HFS can be shared among systems while the read-write file should be mounted only on its owning system.
The following files may have been customized for release 2.2, so you should compare the contents of the 2.2 files with the new files resulting from the 3.0 install. There may be some customizations that need to be brought over to the 3.0 files, such as settings for RESOLVER_CONFIG, BPX environment variables, MIB list, and/or SNMP trap destinations.
Customized files for Agent Technology:
- Event Management release 3.0 was first delivered on the previously available CA Common Services 3.0 SP00 tape [We sometimes reference SP00 as SP04]. The new FMID is CTN3000. A base install must be performed to obtain this new release. An install using this SP7 tape will contain the current maintenance. This new release will attempt to delete previously installed releases of Event Management. If CTN3000 was previously installed, maintenance is available at the SP7 level.
- Applying SP7 maintenance may move the PROFILE file from the R/O HFS to the R/W HFS, and establish a symbolic link on the R/O HFS. If the symbolic link already exists from previous maintenance, it will remain.
- After completing the maintenance upgrade of Event Management from this SP7 tape, please follow the directions in PML QI80957 to correct the permission bits for two files.
- If you have Event Management already installed at the 2.2 release, the transition to release 3.0 involves a complete re-install in a new set of HFS files. Formerly only an R/W HFS was used for everything. With release 3.0 the HFS structures have changed significantly by splitting into two HFS files: a read-only file system and a read-write file system. (However, during the install both of the files need to be mounted read-write and the 2.2 file should be unmounted.) For processing after the install and post-install are done, the read-only HFS can be shared among systems while the read-write file should be mounted only on its owning system. The following files may have been customized for release 2.2, so you should compare the contents of the 2.2 files with the new files resulting from the 3.0 install. There may be some customizations that need to be brought over to the 3.0 files, such as settings for RESOLVER_CONFIG, and BPX environment variables.
Customized files for Event Management:
- To install Event Management on multiple systems, please refer to the Getting Started Guide Chapter 4: Post Installation Tasks under "Installing Multiple Systems - Event Management". Please note the following considerations:
- The mount points for the RO and RW directories should be identical on all systems.
- In Step 7 you are directed to run the TNGFWMIG job. This execution of this job may produce errors in the fwmig.err file, which may be ignored. Please see QI63447 for details.
- Each system should have a Datacom/TR database that can be used by the Event Management processes that require it. A local database may be created on each system, or a central database on a remote system may be used. To use a central database on a remote system, add the following environment variable to the PROFILE file on each system and export it:
- If applying maintenance to a previously installed 3.0 release of Event Management, there are some considerations to be aware of.
- The RO HFS must be mounted RW during maintenance jobs.
- This service pack and the previous SP05 and SP6 service packs, moves the PROFILE file from the RO HFS to the RW HFS and establishes a symbolic link on the RO HFS. SAMPJCL job EMCPPROF can be used to do this (Getting Started Guide, Chapter 7, Step 23). This must be run on each system where Event Management will run. If SP05 or SP6 maintenance has been applied, this item may be skipped.
A new library for CA-SRAM was introduced with SP05. It is a source distribution library CSR70MLD. If a new install is being performed then this library will be allocated during the install process. If maintenance is being performed, step 13 will direct you to run SAMPJCL member W010MALC to allocate the new library.
Activator has been removed from support as of December 31, 2004 and is no longer supplied on the CA Common Services tape.