Re: [EXTERNAL] Re: USS zlib issues
Thanks, Mark, that's very helpful. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Mark Zelden Sent: Friday, March 17, 2023 10:14 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [EXTERNAL] Re: USS zlib issues I meant to add that the sourceid is PUT2208, RSU2209. I'm at RSU2212. Best Regards, Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS ITIL v3 Foundation Certified mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html On Fri, 17 Mar 2023 10:09:50 -0500, Mark Zelden wrote: >It's good on my system. This is the PTF that last updated it all. >it's security / integrity so you won't find out much about it. > > >++ PTF (UJ09020)/* >//UJ09020 JOB 5695-09020,SCPX7,MSGLEVEL=(1,1),CLASS=A */ . >++VER(Z038) FMID(HOT77C0) > SUP(AA60361,AA63294,CA57154,CA57870,CA58433,CA63294,UA99527,UJ00876, > UJ01516,UJ08514) > /* > PROBLEM DESCRIPTION(S): >OA63294 - > INTEGRITY PROBLEM -- 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: [EXTERNAL] Re: USS zlib issues
Thanks, Ann, that's very useful to know. I will pass on the info to our sysprogs. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Ann Kelley Sent: Friday, March 17, 2023 7:04 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [EXTERNAL] Re: USS zlib issues I checked my z/OS 2.4 system. At RSU2008, the zlibs were truncated. At RUS2212, the files were restored to what appears to be proper length --- UJ09020 is the latest PTF for this part, at RSU2212. -- 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: [EXTERNAL] Re: USS zlib issues
I meant to add that the sourceid is PUT2208, RSU2209. I'm at RSU2212. Best Regards, Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS ITIL v3 Foundation Certified mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html On Fri, 17 Mar 2023 10:09:50 -0500, Mark Zelden wrote: >It's good on my system. This is the PTF that last updated it all. it's >security / integrity >so you won't find out much about it. > > >++ PTF (UJ09020)/* >//UJ09020 JOB 5695-09020,SCPX7,MSGLEVEL=(1,1),CLASS=A */ . >++VER(Z038) FMID(HOT77C0) > SUP(AA60361,AA63294,CA57154,CA57870,CA58433,CA63294,UA99527,UJ00876, > UJ01516,UJ08514) > /* > PROBLEM DESCRIPTION(S): >OA63294 - > INTEGRITY PROBLEM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: USS zlib issues
It's good on my system. This is the PTF that last updated it all. it's security / integrity so you won't find out much about it. ++ PTF (UJ09020)/* //UJ09020 JOB 5695-09020,SCPX7,MSGLEVEL=(1,1),CLASS=A */ . ++VER(Z038) FMID(HOT77C0) SUP(AA60361,AA63294,CA57154,CA57870,CA58433,CA63294,UA99527,UJ00876, UJ01516,UJ08514) /* PROBLEM DESCRIPTION(S): OA63294 - INTEGRITY PROBLEM COMPONENT: 5695-SCPX7-HOT77C0 APARS FIXED: OA63294 SPECIAL CONDITIONS: COPYRIGHT: 5695-SCPE1 COPYRIGHT IBM CORP. 2022 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DOCUMENTATION: update publications SA23-1377-40 and SA23-1377-50 with follow new content: 5. Use the z/OS UNIX environmental variable, _HZC_CHECKSUM_METHOD, to control if SIMD acceleration is used in checksum verification. Note If the value of software is set, software-based checksum verification is used. All other values result in the default behavior, which means if hardware supported SIMD, then SIMD acceleration is used. ENHANCEMENT: This New Function shall be considered part of the "Program" with which it is associated, and its use is subject to the license terms that govern the Program, as set forth in the ICA,CRA, or equivalent agreement between you and IBM. Additional verbiage describing the enhancement is zlib crc32 checksum performance is improved. INTEGRITY: INTEGRITY SET: UJ09020 COMMENTS: THE FOLLOWING PARTS ARE AFFECTED BY THIS PTF: HFS HZCLIBS4 HFS HZCLIBSO HFS HZCLIBSX HFS HZCLIBX1 HFS HZCLIBX4 HFS HZCLIBXX HFS HZCLIBZZ HFS HZCZCONF HFS HZCZLIB HFS HZCZLIBZ Best Regards, Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS ITIL v3 Foundation Certified mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: USS zlib issues
I checked my z/OS 2.4 system. At RSU2008, the zlibs were truncated. At RUS2212, the files were restored to what appears to be proper length --- UJ09020 is the latest PTF for this part, at RSU2212. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: USS zlib issues
Hi Tony, Here is my zPDT ADCD z/OS V2.5 Directory: $ cd /usr/lpp/hzc/lib $ ls -al total 4560 drwxr-xr-x 3 OMVSKERN OMVSGRP 8192 Sep 7 2022 . drwxr-xr-x 4 OMVSKERN OMVSGRP 8192 Apr 19 2021 .. drwxr-xr-x 2 OMVSKERN OMVSGRP 8192 Apr 19 2021 IBM -rwxr-xr-x 2 OMVSKERN OMVSGRP 1031756 Sep 7 2022 libzz.a -rwxr-xr-x 2 OMVSKERN OMVSGRP 389120 Sep 7 2022 libzz.so -rwxr-xr-x 2 OMVSKERN OMVSGRP 6723 Sep 7 2022 libzz.x -rwxr-xr-x 2 OMVSKERN OMVSGRP 413696 Sep 7 2022 libzz64.so -rwxr-xr-x 2 OMVSKERN OMVSGRP 7209 Sep 7 2022 libzz64.x -rwxr-xr-x 2 OMVSKERN OMVSGRP 405504 Sep 7 2022 libzzX.so -rwxr-xr-x 2 OMVSKERN OMVSGRP 6723 Sep 7 2022 libzzX.x Regards, David On 2023-03-16 23:14, Tony Harminc wrote: My ADCD-based z/OS 2.5 has the same truncated files with the same dates and sizes. A non-ADCD 2.5 here looks the same. Interestingly, a non-ADCD 2.3 system has only one file in the directory: libzz.a . No .x or .so at all. Tony H. On Thu, 16 Mar 2023 at 09:47, Pommier, Rex wrote: Robin and Barbara, Interesting. My 2.4 system looks a lot like Robin's. Prod2:RRP:/usr/lpp/hzc/lib: # ls -l total 4560 drwxr-xr-x 2 BPXROOT AOPOPER 8192 Sep 25 2019 IBM -rwxr-xr-x 2 BPXROOT AOPOPER 1012800 Mar 25 2020 libzz.a -rwxr-xr-x 2 BPXROOT AOPOPER 405520 Mar 25 2020 libzz.so -rwxr-xr-x 2 BPXROOT AOPOPER 252 Mar 25 2020 libzz.x -rwxr-xr-x 2 BPXROOT AOPOPER 417840 Mar 25 2020 libzz64.so -rwxr-xr-x 2 BPXROOT AOPOPER 252 Mar 25 2020 libzz64.x -rwxr-xr-x 2 BPXROOT AOPOPER 413760 Mar 25 2020 libzzX.so -rwxr-xr-x 2 BPXROOT AOPOPER 252 Mar 25 2020 libzzX.x Something slipped thru IBM packaging for a couple releases of z/OS? Rex -Original Message- From: IBM Mainframe Discussion List On Behalf Of Barbara Nitz Sent: Thursday, March 16, 2023 4:14 AM To:IBM-MAIN@LISTSERV.UA.EDU Subject: [EXTERNAL] Re: USS zlib issues Hi Robin, drwxr-xr-x 2 BPXROOT RSEGROUP8192 Apr 19 2021 IBM -rwxr-xr-x 2 BPXROOT RSEGROUP 1012800 Apr 19 2021 libzz.a -rwxr-xr-x 2 BPXROOT RSEGROUP 405520 Apr 19 2021 libzz.so -rwxr-xr-x 2 BPXROOT RSEGROUP 252 Apr 19 2021 libzz.x -rwxr-xr-x 2 BPXROOT RSEGROUP 417840 Apr 19 2021 libzz64.so -rwxr-xr-x 2 BPXROOT RSEGROUP 252 Apr 19 2021 libzz64.x -rwxr-xr-x 2 BPXROOT RSEGROUP 413760 Apr 19 2021 libzzX.so -rwxr-xr-x 2 BPXROOT RSEGROUP 252 Apr 19 2021 libzzX.x your *.x files are definitely truncated. They all have al length of 252 which is extremely unlikely. This is what it looks like on my system (only the *x files): libzz.x fff--- --s- BPXROOT SYS1 6723 libzzX.xfff--- --s- BPXROOT SYS1 6723 libzz64.x fff--- --s- BPXROOT SYS1 7209 The last change date on mine is 2023/01/06, which is the time I last put maintenance in. No idea what that was, but I guess that's your only chance of fixing the truncated stuff. The date you show is when this stuff was first installed by IBM. I am guessing for the ServerPac. Regards, Barbara -- For IBM-MAIN subscribe / signoff / archive access instructions, send email tolists...@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 tolists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email tolists...@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: USS zlib issues
There is a RSU available every month, (best to be done quarterly). 2.5 came out over a year ago, and is about to be replaced with 3.1. Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: USS zlib issues
My ADCD-based z/OS 2.5 has the same truncated files with the same dates and sizes. A non-ADCD 2.5 here looks the same. Interestingly, a non-ADCD 2.3 system has only one file in the directory: libzz.a . No .x or .so at all. Tony H. On Thu, 16 Mar 2023 at 09:47, Pommier, Rex wrote: > Robin and Barbara, > > Interesting. My 2.4 system looks a lot like Robin's. > > Prod2:RRP:/usr/lpp/hzc/lib: # ls -l > total 4560 > drwxr-xr-x 2 BPXROOT AOPOPER 8192 Sep 25 2019 IBM > -rwxr-xr-x 2 BPXROOT AOPOPER 1012800 Mar 25 2020 libzz.a > -rwxr-xr-x 2 BPXROOT AOPOPER 405520 Mar 25 2020 libzz.so > -rwxr-xr-x 2 BPXROOT AOPOPER 252 Mar 25 2020 libzz.x > -rwxr-xr-x 2 BPXROOT AOPOPER 417840 Mar 25 2020 libzz64.so > -rwxr-xr-x 2 BPXROOT AOPOPER 252 Mar 25 2020 libzz64.x > -rwxr-xr-x 2 BPXROOT AOPOPER 413760 Mar 25 2020 libzzX.so > -rwxr-xr-x 2 BPXROOT AOPOPER 252 Mar 25 2020 libzzX.x > > Something slipped thru IBM packaging for a couple releases of z/OS? > > Rex > > -Original Message- > From: IBM Mainframe Discussion List On Behalf > Of Barbara Nitz > Sent: Thursday, March 16, 2023 4:14 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [EXTERNAL] Re: USS zlib issues > > Hi Robin, > > >drwxr-xr-x 2 BPXROOT RSEGROUP8192 Apr 19 2021 IBM > >-rwxr-xr-x 2 BPXROOT RSEGROUP 1012800 Apr 19 2021 libzz.a > >-rwxr-xr-x 2 BPXROOT RSEGROUP 405520 Apr 19 2021 libzz.so > >-rwxr-xr-x 2 BPXROOT RSEGROUP 252 Apr 19 2021 libzz.x > >-rwxr-xr-x 2 BPXROOT RSEGROUP 417840 Apr 19 2021 libzz64.so > >-rwxr-xr-x 2 BPXROOT RSEGROUP 252 Apr 19 2021 libzz64.x > >-rwxr-xr-x 2 BPXROOT RSEGROUP 413760 Apr 19 2021 libzzX.so > >-rwxr-xr-x 2 BPXROOT RSEGROUP 252 Apr 19 2021 libzzX.x > > your *.x files are definitely truncated. They all have al length of 252 > which is extremely unlikely. This is what it looks like on my system (only > the *x files): > > libzz.x fff--- --s- BPXROOT SYS1 6723 > libzzX.xfff--- --s- BPXROOT SYS1 6723 > libzz64.x fff--- --s- BPXROOT SYS1 7209 > > The last change date on mine is 2023/01/06, which is the time I last put > maintenance in. No idea what that was, but I guess that's your only chance > of fixing the truncated stuff. The date you show is when this stuff was > first installed by IBM. I am guessing for the ServerPac. > > Regards, Barbara > > -- > 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 > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: USS zlib issues
Robin and Barbara, Interesting. My 2.4 system looks a lot like Robin's. Prod2:RRP:/usr/lpp/hzc/lib: # ls -l total 4560 drwxr-xr-x 2 BPXROOT AOPOPER 8192 Sep 25 2019 IBM -rwxr-xr-x 2 BPXROOT AOPOPER 1012800 Mar 25 2020 libzz.a -rwxr-xr-x 2 BPXROOT AOPOPER 405520 Mar 25 2020 libzz.so -rwxr-xr-x 2 BPXROOT AOPOPER 252 Mar 25 2020 libzz.x -rwxr-xr-x 2 BPXROOT AOPOPER 417840 Mar 25 2020 libzz64.so -rwxr-xr-x 2 BPXROOT AOPOPER 252 Mar 25 2020 libzz64.x -rwxr-xr-x 2 BPXROOT AOPOPER 413760 Mar 25 2020 libzzX.so -rwxr-xr-x 2 BPXROOT AOPOPER 252 Mar 25 2020 libzzX.x Something slipped thru IBM packaging for a couple releases of z/OS? Rex -Original Message- From: IBM Mainframe Discussion List On Behalf Of Barbara Nitz Sent: Thursday, March 16, 2023 4:14 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [EXTERNAL] Re: USS zlib issues Hi Robin, >drwxr-xr-x 2 BPXROOT RSEGROUP8192 Apr 19 2021 IBM >-rwxr-xr-x 2 BPXROOT RSEGROUP 1012800 Apr 19 2021 libzz.a >-rwxr-xr-x 2 BPXROOT RSEGROUP 405520 Apr 19 2021 libzz.so >-rwxr-xr-x 2 BPXROOT RSEGROUP 252 Apr 19 2021 libzz.x >-rwxr-xr-x 2 BPXROOT RSEGROUP 417840 Apr 19 2021 libzz64.so >-rwxr-xr-x 2 BPXROOT RSEGROUP 252 Apr 19 2021 libzz64.x >-rwxr-xr-x 2 BPXROOT RSEGROUP 413760 Apr 19 2021 libzzX.so >-rwxr-xr-x 2 BPXROOT RSEGROUP 252 Apr 19 2021 libzzX.x your *.x files are definitely truncated. They all have al length of 252 which is extremely unlikely. This is what it looks like on my system (only the *x files): libzz.x fff--- --s- BPXROOT SYS1 6723 libzzX.xfff--- --s- BPXROOT SYS1 6723 libzz64.x fff--- --s- BPXROOT SYS1 7209 The last change date on mine is 2023/01/06, which is the time I last put maintenance in. No idea what that was, but I guess that's your only chance of fixing the truncated stuff. The date you show is when this stuff was first installed by IBM. I am guessing for the ServerPac. Regards, Barbara -- 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: USS zlib issues
Thanks, Barbara, I will forward your post to the sysprog! I don't know if our z/OS 2.5 has had any maintenance yet. Robin -Original Message- From: IBM Mainframe Discussion List On Behalf Of Barbara Nitz Sent: Thursday, March 16, 2023 4:14 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: USS zlib issues Hi Robin, >drwxr-xr-x 2 BPXROOT RSEGROUP8192 Apr 19 2021 IBM >-rwxr-xr-x 2 BPXROOT RSEGROUP 1012800 Apr 19 2021 libzz.a >-rwxr-xr-x 2 BPXROOT RSEGROUP 405520 Apr 19 2021 libzz.so >-rwxr-xr-x 2 BPXROOT RSEGROUP 252 Apr 19 2021 libzz.x >-rwxr-xr-x 2 BPXROOT RSEGROUP 417840 Apr 19 2021 libzz64.so >-rwxr-xr-x 2 BPXROOT RSEGROUP 252 Apr 19 2021 libzz64.x >-rwxr-xr-x 2 BPXROOT RSEGROUP 413760 Apr 19 2021 libzzX.so >-rwxr-xr-x 2 BPXROOT RSEGROUP 252 Apr 19 2021 libzzX.x your *.x files are definitely truncated. They all have al length of 252 which is extremely unlikely. This is what it looks like on my system (only the *x files): libzz.x fff--- --s- BPXROOT SYS1 6723 libzzX.xfff--- --s- BPXROOT SYS1 6723 libzz64.x fff--- --s- BPXROOT SYS1 7209 The last change date on mine is 2023/01/06, which is the time I last put maintenance in. No idea what that was, but I guess that's your only chance of fixing the truncated stuff. The date you show is when this stuff was first installed by IBM. I am guessing for the ServerPac. Regards, Barbara -- 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: USS zlib issues
Hi Robin, >drwxr-xr-x 2 BPXROOT RSEGROUP8192 Apr 19 2021 IBM >-rwxr-xr-x 2 BPXROOT RSEGROUP 1012800 Apr 19 2021 libzz.a >-rwxr-xr-x 2 BPXROOT RSEGROUP 405520 Apr 19 2021 libzz.so >-rwxr-xr-x 2 BPXROOT RSEGROUP 252 Apr 19 2021 libzz.x >-rwxr-xr-x 2 BPXROOT RSEGROUP 417840 Apr 19 2021 libzz64.so >-rwxr-xr-x 2 BPXROOT RSEGROUP 252 Apr 19 2021 libzz64.x >-rwxr-xr-x 2 BPXROOT RSEGROUP 413760 Apr 19 2021 libzzX.so >-rwxr-xr-x 2 BPXROOT RSEGROUP 252 Apr 19 2021 libzzX.x your *.x files are definitely truncated. They all have al length of 252 which is extremely unlikely. This is what it looks like on my system (only the *x files): libzz.x fff--- --s- BPXROOT SYS1 6723 libzzX.xfff--- --s- BPXROOT SYS1 6723 libzz64.x fff--- --s- BPXROOT SYS1 7209 The last change date on mine is 2023/01/06, which is the time I last put maintenance in. No idea what that was, but I guess that's your only chance of fixing the truncated stuff. The date you show is when this stuff was first installed by IBM. I am guessing for the ServerPac. Regards, Barbara -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
