On Tue, 9 Nov 2021 08:04:56 -0600, Dave Jousma <[email protected]> wrote:
> >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/../../ > >../../../../../... > Correction. I just went and looked at the actual filesystem -rw-r--r-- 2 BPXROOT OMVSGRP 699 Sep 25 2019 EZAITMSG -rw-r--r-- 2 BPXROOT OMVSGRP 26230 Dec 23 2019 EZAMLCAT -rw-r--r-- 2 BPXROOT OMVSGRP 5026 Sep 25 2019 EZAMLRPY TEC1:$ pwd /RST01A/usr/lpp/tcpip/lib/nls/msg/C/IBM TEC1:$ My apologies for the red herring. I'd still ask IBM to investigate a possible packaging error though since it appears to be an APARfix ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
