Re: SMPE apply error SYMLINKS
Hello All Thanks to Kurt. Under the /Service some of the directories were missing and I created those. Then tried applying again and it went fine. Thanks all for your help On Tue, 9 Nov, 2021, 7:51 pm Kurt J. Quackenbush, wrote: > > Based on reason code I have looked into each directory and it exists but > > not sure which file it is looking for and failing. > > Unfortunately message BPXF170E truncates the desired SYMLINK value. I > can't see the ++APAR so don't know for sure the SYMLINK value but if it > matches the prior value for EZAMLCAT the message is complaining about this > directory: > > /Service/usr/lpp/tcpip/lib/nls/msg/C/IBM/ > ../../../../../../../../usr/lib/nls/msg/C/ezamlcat.cat > > After resolving the "../" you get this directory: > > /Service/usr/lib/nls/msg/C/ > > Does that directory exist? Is it mounted? Does the SYMLINK value on the > ++HFS statement in the ++APAR match the existing SYMLINK value for > EZAMLCAT? Look at the ++APAR in your SMPPTS and look at the HFS entry in > the target zone to compare the SYMLINK values. > > Kurt Quackenbush -- IBM, z/OS SMP/E and z/OSMF Software Management > > Chuck Norris never uses CHECK when he applies PTFs. > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMPE apply error SYMLINKS
> Based on reason code I have looked into each directory and it exists but > not sure which file it is looking for and failing. Unfortunately message BPXF170E truncates the desired SYMLINK value. I can't see the ++APAR so don't know for sure the SYMLINK value but if it matches the prior value for EZAMLCAT the message is complaining about this directory: /Service/usr/lpp/tcpip/lib/nls/msg/C/IBM/ ../../../../../../../../usr/lib/nls/msg/C/ezamlcat.cat After resolving the "../" you get this directory: /Service/usr/lib/nls/msg/C/ Does that directory exist? Is it mounted? Does the SYMLINK value on the ++HFS statement in the ++APAR match the existing SYMLINK value for EZAMLCAT? Look at the ++APAR in your SMPPTS and look at the HFS entry in the target zone to compare the SYMLINK values. Kurt Quackenbush -- IBM, z/OS SMP/E and z/OSMF Software Management Chuck Norris never uses CHECK when he applies PTFs. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMPE apply error SYMLINKS
Classification: Confidential Check for action holds on the relevant PTF. If a new directory is required, IBM will typically detail what is required and (usually) supply a sample job to create the directories. HTH, -Original Message- From: IBM Mainframe Discussion List On Behalf Of Dave Jousma Sent: Tuesday, November 9, 2021 8:19 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SMPE apply error SYMLINKS [CAUTION: This Email is from outside the Organization. Unless you trust the sender, Don’t click links or open attachments as it may be a Phishing email, which can steal your Information and compromise your Computer.] On Tue, 9 Nov 2021 08:04:56 -0600, Dave Jousma 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 0081, 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 OMVSGRP26230 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMPE apply error SYMLINKS
On Tue, 9 Nov 2021 08:04:56 -0600, Dave Jousma 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 0081, 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 OMVSGRP26230 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMPE apply error SYMLINKS
On Tue, 9 Nov 2021 12:09:38 +0400, Jake Anderson 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 '0081'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 0081, 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: SMPE apply error SYMLINKS
Check to see if there's a security violation in the path? -Original Message- From: IBM Mainframe Discussion List On Behalf Of Jake Anderson Sent: Tuesday, November 9, 2021 5:38 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [EXTERNAL] Re: SMPE apply error SYMLINKS Hello I have double checked the DDDEF and the path is correct for the failing DDDEF On Tue, 9 Nov, 2021, 3:31 pm SUBSCRIBE IBM-MAIN Marc Yves Desravines, < marc.yves.desravi...@kyndryl.com> wrote: > Hi Jake, > > I suspect the problem is related with a wrong DDDEF. Could you list > the DDDEFs and check if the related pathname required is correct? > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMPE apply error SYMLINKS
Hi Jake, 0594003D according to BPXMTEXT means: JRDirNotFound: A directory in the pathname was not found So it looks like your HFS files directories are not set up or mounted properly. Could you check them and compare with what you have in the DDDEF? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMPE apply error SYMLINKS
Hello I have double checked the DDDEF and the path is correct for the failing DDDEF On Tue, 9 Nov, 2021, 3:31 pm SUBSCRIBE IBM-MAIN Marc Yves Desravines, < marc.yves.desravi...@kyndryl.com> wrote: > Hi Jake, > > I suspect the problem is related with a wrong DDDEF. Could you list the > DDDEFs and check if the related pathname required is correct? > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMPE apply error SYMLINKS
Hi Jake, I suspect the problem is related with a wrong DDDEF. Could you list the DDDEFs and check if the related pathname required is correct? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
SMPE apply error SYMLINKS
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 '0081'X AND THE REASON CODE WAS '0594003D'X. GIM69168E ** HFSCOPY PROCESSING TO THE SEZAMMSC LIBRARY FAILED FOR HFS EZAMLCAT IN SYSMOD AH38318. THE RETURN CODE (12) EXCEEDED THE ALLOWABLE VALUE. DATE 21.313 - TIME 10:17:10 - SEQUENCE NUMBER 01. 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 '0081'X AND THE REASON CODE WAS '0594003D'X. CAUSER FMID MESSAGE ID PAGE ERROR DESCRIPTION AND POSSIBLE CAUSES AH38318 HIP6240 GIM69168E 1 HFSCOPY PROCESSING FAILED FOR HFS EZAMLCAT TO THE SEZAMMSC LIBRARY. THE RETURN CODE WAS 12. THE SEQUENCE NUMBER WAS 01. 1BPXF151I BPXCOPY WAS INVOKED FOR HEAD ID 01. 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 0081, REASON CODE 0594003D. A SYMLINK FAILED FOR LINK NAME /Service/usr/lpp/tcpip/lib/nls/msg/C/IBM/../../ ../../../../../... Based on reason code I have looked into each directory and it exists but not sure which file it is looking for and failing. Any clue where else I need to be looking ? Jake -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
