Question & Answer
Question
Why is my SMP/E APPLY job failing with message BPXF140E return code 81 and reason code 0594003D indicating no such directory exists when I am applying z/OS Connect Enterprise Edition (zCEE) V2 PTF UI41811 to bring zCEE up to V2.0.4.0?
BPXF140E RETURN CODE 00000081, REASON CODE 0594003D. A LINK FAILED FOR LINK NAME /usr/lpp/IBM/zosconnect/v2r0/IBM/../runtime/templates/servers/sa.
The /../ seems strange and I definitely do not have a directory named "sa". I checked my job to make sure the DDDEF is correct and it is and I know I have the correct permissions set up.
ZONE DDNAME DDDEFNAM SMPDDNAM TYPE --------------DATA SET OR PATH-------------- VOLSER UNIT STATUS SBAQZFS SBAQZFS PATH '/usr/lpp/IBM/zosconnect/v2r0/IBM/'
PATHHFS ZOSCON.V2R0.HFS
The SMP/E output shows it successfully copied members up to BAQ00132 and failed on BAQ00133.
GIM69168E ** HFSCOPY PROCESSING TO THE SBAQZFS LIBRARY FAILED FOR HFS
BAQ00133 IN SYSMOD UI41811. THE RETURN CODE (12) EXCEEDED THE ALLOWABLE VALUE. DATE 16.314 - TIME 10:56:48 - SEQUENCE NUMBER 000019.
GIM30216I APPLY PROCESSING FAILED FOR SYSMOD UI41811. SYSTEM UTILITY PROCESSING FAILED FOR AN ELEMENT IN UI41811.
The BAQ00133 is going to..
++HFS(BAQ00133) SYSLIB(SBAQZFS) DISTLIB(ABAQZFS) PARM(PATHMODE(0,6,4,4)) BINARY LINK('../runtime/templates/servers/sampleWolaCatalogManager/resources/ zosconnect/services/inquireCatalog_request.json').
Answer
The BPXF140E message truncates the full directory name. You are correct, in that there is no "sa" directory. The "sa" is the leading characters of sampleWolaCatalogManager.
The BAQ00133 is the first reference to the "/services/" part of the new paths to be created in the ++HOLD action in UI41811.
Can you check to make sure the following directory exists?
/usr/lpp/IBM/zosconnect/v2r0/runtime/templates/servers/sampleWolaCatalogManager/resources/zosconnect/services
Can you make sure it has Permissions - rwxrwxr-x for 775?
Here is the ++HOLD from PTF UI41811...
++HOLD(UI41811) SYSTEM FMID(HZCN200) REASON(ACTION) DATE(16294)
COMMENT(
Before applying this PTF:
There is a known issue with PE PTF UI35770 that corrupts Liberty.
If PTF UI35770 has been applied you must delete z/OS Connect EE
V2 and reinstall the GA version of z/OS Connect EE V2.
Prior to applying this PTF new directories must be created.
At an OMVS command prompt issue the following commands:
su -
umask 0002
INSTALL_DIR=<zos_connect_install_dir>
mkdir -p $INSTALL_DIR/runtime/lib/versions
mkdir -p $INSTALL_DIR/samples/scenarios/haWola
SERVERS_DIR=$INSTALL_DIR/runtime/templates/servers
SWCM_DIR=sampleWolaCatalogManager/resources/zosconnect
mkdir -p $SERVERS_DIR/$SWCM_DIR/apis
mkdir -p $SERVERS_DIR/$SWCM_DIR/services
To confirm that the new directories have the correct ownership
and permissions issue the following command:
ls -ldR $SERVERS_DIR $INSTALL_DIR/samples
Check that the listed directories have the same ownership and
permissions as the features directory:
ls -ld $INSTALL_DIR/runtime/lib/features
e.g:
drwxrwxr-x 3 ROOT TSOUSER ... $INSTALL_DIR/runtime/lib/features
If necessary update the ownership and permissions of the new
directories to match the features directory.
After applying this PTF:
Customers using z/OS Connect EE V2 with IMS must apply the PTF
for APAR PI67597
Customers using z/OS Connect EE V2 embedded in CICS TS V5 require
a CICS TS V5 PTF.
CICS TS V5.2 users must apply the PTF for APAR PI64748
CICS TS V5.3 users must apply the PTF for APAR PI64749
Customers using WOLA with CICS TS must copy the WOLA load modules
from directory <zos_connect_install_dir>/wlp/clients/zos
to the load library referenced in the DFHRPL of the CICS TS
region startup JCL.
Customers using z/OS Authorized Services with Liberty must ensure
that the Liberty angel process they are using is the latest
version on the LPAR. The Liberty angel version installed with
this PTF is 16.0.0.2. If necessary stop the angel process and
start the angel process supplied with this PTF.
).
Product Synonym
zCEE
Was this topic helpful?
Document Information
Modified date:
14 February 2023
UID
dwa1319951