ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Error: GIM69168E HFSCOPY FAILED FOR J2Z4IAKI while installing CFF6F00

book

Article ID: 200779

calendar_today

Updated On:

Products

COMMON SERVICES FOR Z/OS COMMON PRODUCT SERVICES COMPONENT Common Services CHORUS SOFTWARE MANAGER

Issue/Introduction

While running the APPLY job for CA COMMON SERVICES (CCS) 15.0 the following error is encountered:

CFF6F00  CFF6F00  GIM69168E     36   HFSCOPY PROCESSING FAILED FOR HFS J2Z4IAKI TO THE CFF6PLAT LIBRARY. THE RETURN
                                     CODE WAS 12. THE SEQUENCE NUMBER WAS 000051.

BPXF151I BPXCOPY WAS INVOKED FOR HEAD ID 000051.
BPXF150I MVS DATA SET WITH DDNAME SMP00056 SUCCESSFULLY COPIED INTO BINARY HFS FILE /opt/ca90s/J2Z4IAKI.
BPXF140E RETURN CODE 00000081, REASON CODE 0594003D.  A LINK FAILED FOR LINK NAME /opt/ca90s/../cff6/lib/j2zsdk.jar.

Cause

In this specific environment the problem definitely looks related to the DDDEF for CFF6PLAT.

Review of the FILE ALLOCATION REPORT found in the apply output showed the following information for DDDEF for CFF6PLAT

ZONE    DDNAME   DDDEFNAM SMPDDNAM TYPE     --------------DATA SET OR PATH-------------- VOLSER UNIT     STATUS
         
      CFF6PLAT CFF6PLAT          PATH     '/opt/ca90s/'
                                 PATHHFS SYSHLQ.CA90S.R15.ZFS


This is not accurate since the PATH should end with /CA/

The DDDEF for CFF6PLAT must have /CA/ as the last directory in the name.

If the DDDEF looks good, other possible problems are:

  • the directories were not created as required
  • the filesystem is mounted to the incorrect mountpoint.


During the initial install, job AW006MKD is used to create and mount the filesystems and job AW015CSU is used to define the CFF6PLAT DDDEF.

 

Environment

Release : 15.0
Component : CCS390 - CA COMMON SERVICES FOR Z/OS

Resolution

Review AW006MKD and AW015CSU and either...

  • redefine the DDDEF as required
  • create the required directories
  • unmount and re-mount the filesystem to the correct mountpoint (the mountpoint does not include /CA/)

 

Once corrected, rerun the APPLY specifying REDO.