How to apply outstanding fixes for products CA Z/OS products not under CSM control?

Document ID : KB000047052
Last Modified Date : 14/02/2018
Show Technical Document Details

Introduction: 

After a new install have been completed or for ongoing preventive maintenance the installer may have to apply many outstanding fixes. Downloading and applying these fixes one at a time would be very time consuming. It is strongly rcommended that client us the common services utility CAUNZIP to mass apply outstanding fixes.

Instructions:

For non-CA CSM users, we now offer a new CAUNZIP utility to simplify maintenance management. CAUNZIP is a TSO utility that extracts the contents of a Published Solutions maintenance package order from the Download Center on CA Support Online. This utility lets you process zip-format packages directly on z/OS without the need for an intermediate platform such as a Windows workstation. The utility extracts the contents of the order and produces a Network Temporary Store (NTS) formatted set of z/OS UNIX files. These files can be used for SMP/E RECEIVE processing.

In the CA UNZIP Utility Quick Reference Guide quick reference guide are common services fix level required in order to use the CAUNZIP utility. 

Requirements Your site must meet the following requirements to use CAUNZIP 

Verify that the following PTF is applied based on your version of CA Common Services for z/OS: – CCS Release 14.0: PTF RO54887 – CCS Release 14.1: PTF RO54635

An OMVS segment for the user executing the utility

Read/write access to the z/OS Unix Systems Services (USS) directory – The directory can reside in a zFS, HFS, or TFS file system. Network File Systems (NFS) are not supported. – The file system must be allocated with approximately 4.5 times the space of the zip file being processed. Each 3390 track is the equivalent of 56 KB. Te actual size that is required varies, depending on the content of the order.

IBM Java SDK for z/OS, Version 5 or higher (31-bit and 64-bit are both supported)

A minimum REGION size of 128 MB. We recommend REGION=0M.

The IBM REXX LPA data set, REXX.SEAGLPA, must be in the system LPALSTxx ‘SYS1.PARMLIB’ member and be included with the last IPL. If the REXX.SEAGLPA data set is not available on the system, you can alternatively add the REXX alternative library, REXX.SEAGALT, to the system linklist

Additional Information:

Please see the CA Common Services for z/OS Administration Guide Chapter 11: CAUNZIP Utility for additional information.