On Tue, 9 Nov 2021 12:09:38 +0400, Jake Anderson <[email protected]>
wrote:
>Hello
>
>Cross posted
>
>I am applying a APAR related to CSSMTP to zOS 2.4 and it fails with below
>messge
>
>GIM42500W AN ATTEMPT TO OBTAIN THE NAME OF THE PHYSICAL DATA SET CONTAINING
>A
>
> SYMBOLIC LINK FOR HFS EZAMLCAT IN SEZAMMSC FAILED. THE RETURN
>CODE
>
> FROM THE BPX1LST CALLABLE SERVICE WAS '00000081'X AND THE
>REASON
>
> CODE WAS '0594003D'X.
>
Jake,
Is that an APARfix for PH38318? I see the APAR is still open. Could be a
packaging error by IBM too…..
I look up the same module in my 2.4 environment
Entry Type: HFS Zone Name: MVSTZN
Entry Name: EZAMLCAT Zone Type: TARGET
FMID : HIP6240 DISTLIB : AEZAXLT3 LASTUPD: HIP6240 TYPE=ADD
RMID : UI66498 SYSLIB : SEZAMMSC BINARY
SHSCRIPT:
----------------------------------------------------------------
LINK '../ezamlcat.cat'
PARM PATHMODE(0,6,4,4)
SYMLINK '../../../../../../../../usr/lib/nls/msg/C/ezamlcat.cat'
SYMPATH '../../../../../usr/lpp/tcpip/lib/nls/msg/C/ezamlcat.cat'
Yours seems to have an extra directory in it? I don’t have /IBM/ in mine.
BPXF150I MVS DATA SET WITH DDNAME SYSUT1 SUCCESSFULLY COPIED INTO BINARY
HFS FILE /Service/usr/lpp/tcpip/lib/nls/msg/C/IBM/EZAMLCAT.
BPXF170E RETURN CODE 00000081, REASON CODE 0594003D. A SYMLINK FAILED FOR
LINK NAME /Service/usr/lpp/tcpip/lib/nls/msg/C/IBM/../../
../../../../../...
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
