r11 SP06 Installation and Maintenance Bulletins - CA Technologies
{{search ? 'Close':'Search'}}

CA Common Services for z/OS
Installation & Maintenance Bulletins
r11 Service Pack 6

Last Updated: January 18, 2007

CA Common Services r11 for z/OS Service Pack 6 is the successor to CA Common Services r3 for z/OS Service Pack 5.

Please review the following items and all Product Bulletins

General Information

  • An IPL is required to implement this new service level as a result of enhancements to the CAIRIM service. See below for more information.

  • New Common Services are being delivered on this tape. Please see 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 CAICCI is being delivered on the tape. CAICCI r2.1 can optionally be installed off the CA Common Services r11 tape. This new release of CCI will replace (delete) CCI r1.1 if you choose to install it. CCI r2.1 requires z/OS 1.3 or higher. Please see the Cover Letter for more information.

  • A new Common Services FMID CAG3000 is being delivered on this tape, as it was on the prior SP04 and SP05 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 SP05 level. There is no maintenance for this component at the SP06 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 and SP05 tapes. It is to be used for 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 is still being delivered on this SP06 tape, but will be dropped on future tapes. To use the "old" ENFSNMPM you must run SAMPJCL member SNMPLINK to perform the needed linkedits.


  • If your site has CAIENF/USS actively running, you will need to schedule an IPL to implement Service Pack 6 if upgrading from a level prior to SP05. If you are already at the SP05 level, or have already implemented QO62378, then an IPL is not required on behalf of CAIENF/USS.

  • This Service Pack and the previous SP05 service pack, includes maintenance to CAIENF/DB2 that provides support for DB2 V8.1. In order to activate the DB2 V8.1 support, an IPL is required. If you are already running DB2 V8.1 and have implemented CAIENF/DB2 APAR QO61463, then an IPL is not required on behalf of CAIENF/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 SP06 level are as follows:

    SP04 stamp is LVL200306
    SP05 stamp is LVL200407
    SP06 stamp is LVL200506

CAIRIM

  1. Included with this 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 is required to implement this new service level. Consequently, an IPL is required in order to back-out.


  2. As a result of changes in QO66300, the CAIRIMU utility will not generate any output. Please apply QO73961 to correct this problem.


  3. As a result of changes in QO66300, a possible SQA storage overlay may result if there are NO valid LMP keys. Please review PEA QI74263 for recommended remediation.


  4. For those customers that only utilize the CAIRIM component, beginning with this 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.   SET   BDY(CAIDLIB) .   UCLIN .    REP    DDDEF(CSSLIB)         DA   (SYS1.CSSLIB)         SHR.   ENDUCL. /* // 

CAIENF and CAICCI

  1. Concerning CAICCI r1.1, the "C" versions of CCITCP and CCITCPGW will no longer be supported after September 30 th, 2006. You are encouraged to switch to the assembler versions of the code by updating your procs to reference programs CAS9ATGS (CCITCP) and CAS9ATPS (CCITCPGW). The assembler version removes all requirements to run W010LINK.

  2. New datasets are needed for ENF (and CCI).
    ( Note: If you have already upgraded to SP04 or SP05 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 CAIPDSE and CW110LPD libraries. In addition, if you are using an SMP/E environment that existed prior to the 9909 genlevel, then it is possible that you will not have an allocation for the SMPLTS library. In this situation, please refer to SAMPJCL member CAINITE5 for an example of the proper allocation of the SMPLTS library.

  3. 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)).

  4. 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 your 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.

    The following sample JCL can be used to alter the ENF database.
       //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.
  5. 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 =

    changed to:

    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

  1. 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 SP06 level, or if a base install of GSS and GREXX was done at the SP02, SP03, SP04, or SP05 level. It is only necessary if the base install of these products was done prior to SP02.

    Step 1: After downloading the SAMPJCL from the SP06 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 LYS2806 and LJD4106 be accepted in order to correctly synchronize SMP/E with the new DLIBs.

Agent Technologies

  1. Agent Technology release 3.0 was first delivered on the previously available CA Common Services 3.0 SP00 tape. The new FMID is CID3000. If this new release was previously installed, maintenance was available on the prior SP05 tape. If you have not yet installed this new release, you can do so using this SP06 tape. An install using this SP06 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.

  2. 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.

  3. 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 a 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:
    cai/agent/agentworks.profile
    cai/agent/services/tools/install_mibs
    cai/agent/services/config/aws_sadmin/aws_sadmin.cfg
    cai/agent/services/config/awservices/awservices.cfg

Event Management

  1. Event Management release 3.0 was first delivered on the previously available CA Common Services 3.0 SP00 tape. The new FMID is CTN3000. A base install must be performed to obtain this new release. If CTN3000 was installed from a prior tape (SP00 or SP05), you may simply apply maintenance to Event Management. An install using this SP06 tape will contain the current maintenance. This new release will attempt to delete previously installed releases of Event Management. Event Management release 3.0 consists of only a single FMID. The WorldView component has been incorporated within this single FMID.


  2. Applying SP06 maintenance will 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.


  3. 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 a 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:
    $CAIGLBL0000/PROFILE
    $CAIGLBL0000/browser/httpd.conf
    $CAIGLBL0000/browser/httpd.config


  4. 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:





  5. The mount points for the RO and RW directories should be identical.
  6. 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.
  7. 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:

    CAI_OPR_REMOTEDB=ccisysid

  8. If applying maintenance to a previously installed 3.0 release of Event Management, there are some considerations to be aware of.



    CA-SRAM

    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.

    CA-Activator

    Activator has been removed from support as of December 31, 2004 and is no longer supplied on the CA Common Services tape.

  9. The RO HFS must be mounted RW during maintenance jobs.
  10. This service pack and the previous SP05 service pack, moves the PROFILE file from the RO HFS to the RW HFS and establishes a Symbolic link on the RO HFS to the RW HFS. The SAMPJCL job EMCPPROF to do this (Step 23 in the Getting Started Guide chapter 7: Maintenance Steps) must be run on every system where Event Management will run. If SP05 maintenance has been applied, this item can be skipped.

Chat with CA

Just give us some brief information and we'll connect you to the right CA Expert.

Our hours of availability are 8AM - 5PM CST.

All Fields Required

connecting

We're matching your request.

Unfortunately, we can't connect you to an agent. If you are not automatically redirected please click here.

  • {{message.agentProfile.name}} will be helping you today.

    View Profile


  • Transfered to {{message.agentProfile.name}}

    {{message.agentProfile.name}} joined the conversation

    {{message.agentProfile.name}} left the conversation

  • Your chat with {{$storage.chatSession.messages[$index - 1].agentProfile.name}} has ended.
    Thank you for your interest in CA.


    How Did We Do?
    Let us know how we did so that we can maintain a quality experience.

    Take Our Survey >

    Rate Your Chat Experience.

    {{chat.statusMsg}}

agent is typing