On Tue, Apr 16, 2024 at 10:42:01PM +, Frank Swarbrick wrote:
> Is it possible to list Unix domain sockets? I don't see any netstat
> option to do so.
$ find / -type s
-Alex
--
For IBM-MAIN subscribe / signoff / archive
Turning off s/w compression in CICS & Db2 doesn't always work as advertised
(meaning, it's not always better to turn off s/w compr and let h/w handle it).
Uncompressed = more I/O for SMF processor tooling to handle.
With either way of compressing, bytes stored will be around the same but the
Yes and zEDC poorly compresses internally RLE compressed records.
Plus CSRCESRV uses GP engine cycles, whereas zEDC offloads the
processing and reduces CICS and DB2 address space CPU time, By the
time LOGGER writes the data to the logstream, it is already
compressed and is smaller than the
On 16/04/2024 3:08 am, Jon Perryman wrote:
From a language standpoint, REXX is just another language but it's
real strength is it's environment integration. Instead of the caller
maintaining libraries, the environment automatically integrates with
REXX. For instance, REXX in the TSO
On 17/04/2024 7:52 am, Michael Oujesky wrote:
My current recommendation is to remove internal compression from CICS
CMF (110/112) and DB2 (100-102) records, Zedc compress the SMF
logstreams, then compress the logstream offloads via SMS zEDC
compression.
Have you compared compressed size
Is it possible to list Unix domain sockets? I don't see any netstat option to
do so.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
And SMF data in logstreams too.
Mark Jacobs
Sent from ProtonMail, Swiss-based encrypted email.
GPG Public Key -
https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com
On Tuesday, April 16th, 2024 at 6:32 PM, Mark Jacobs
<0224d287a4b1-dmarc-requ...@listserv.ua.edu> wrote:
Je suis absent le 17 avril 2024.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Our storage team would know more about what they've done with zEDC, but I'm
using it for compression of zFS file systems and JES2 Sysout written to spool.
Mark Jacobs
Sent from ProtonMail, Swiss-based encrypted email.
GPG Public Key -
Have you considered using zEDC on your SMF logstreams?
My current recommendation is to remove internal compression from
CICS CMF (110/112) and DB2 (100-102) records, Zedc compress the SMF
logstreams, then compress the logstream offloads via SMS zEDC
compression. Note that DFHSM archives
Actually to z/OS IAM datasets look like physical
sequential. They look to the application like VSAM.
At 02:02 PM 4/16/2024, Jousma, David wrote:
Thanks for that. We do have IAM here, well
open a ticket with BMC asking about support. I
was just doubting since it presents to the OS as a
Willy,
You don’t actually need the textlenp variable for the call to the subroutine,
you can just pass the ADDRESS of textlen directly with this syntax:
retcode = rxhlicpl (hlicmd, name, namelen, text, );
Unless of course you also need that pointer for some other process later.
Peter
From:
Kirh,
thank you for your alternate solution, I will keep that in mind.
Willy
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Willy,
Lots of info here, but not the essential bits: what addressing mode and
linkage convention would you like to use?
I'll choose to answer for 31-bit C and assembler where the assembler is
standard savearea linkage. This will work from either C/C++ using XPLINK or
non-XPLINK.
In C:
Found it, it was down to C pointers as expected / feared.
This works, note the use of 'textlenp' in the call:
#pragma linkage (rxhlicpl, OS)
main () {
extern int rxhlicpl();
Not surprising. IAM replaces VSAM, including
physical I/O to the file(s), along with better buffering and lookaside.
VSAM can have internally compressed records (like
RMF III data stores do), but the application is
responsible to processing the by the application data into a usable form.
Thanks Tony,
yes I am at the 'I just want it to work stage'.
I do actually have a "#pragma linkage(rxhlicpl,OS)" statement in there, should
have listed that as well.
I would really prefer not to get involved with LE at this point, but if that is
what it takes, then I guess I have to.
Your idea
FWIW, here is a snippet of the SMS ACS DC code that we were using for zEDC.
/* DEFINE extra data sets to receive zEDC compression */
/**/
Michael,
Yes, thanks. It is just the sortwk datsets that are the issue.
Dave Jousma
Vice President | Director, Technology Engineering
From: IBM Mainframe Discussion List on behalf of
Michael Oujesky
Date: Tuesday, April 16, 2024 at 3:24 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re:
No Hogan here. We use IAM in a bunch of applications because it is
significantly faster than VSAM (or was).
Dave Jousma
Vice President | Director, Technology Engineering
From: IBM Mainframe Discussion List on behalf of
rpinion865 <042a019916dd-dmarc-requ...@listserv.ua.edu>
Date:
Curious, do you use IAM for Hogan applications? My previous life did, and the
applications group was very satisfied with the IAM performance vs. native VSAM.
However, we had to impress on them, that periodic reorgs were more necessary
for IAM, than under VSAM. And, we found out that ADRDSSU
Food for thought. zEDC is block oriented rather than record oriented
(i.e. reads/writes full track blocks on DASD and BLKSIZE become
logical (i.e. the size of the buffer used to exchange data with the
application)), so any processing that expects to make use of BLKSIZE
to perform physical I/O
Thanks for that. We do have IAM here, we’ll open a ticket with BMC asking
about support. I was just doubting since it presents to the OS as a VSAM
dataset.
We were hoping to make ZEDC “inclusive” as in everyone gets it to reap the
space reduction, and job performance improvements and that
It depends to some extent on how much you want to learn about C and LE
linkage conventions. If the answer is "nothing at all - I just want it to
work", then you might want to try inserting a
#pragma linkage(rxhlicpl,OS)
which tells the compiler to use an OS-style argument list when it calls
your
At my previous life, we were using BMC's IAM VSAM interface. I think IAM could
use zEDC. But I was told by then IDP support, that IAM's internal compression
was Moe (as in Moe Howard) better than even zEDC.
Regarding coding for PS datasets opened in/out, I think DAF will show how a PS
>> We initially enabled Extended Format/COMPACT ZP, for all DSORG PS datasets,
>> but are quickly finding that DFSORT, SAS, ISPF recovery datasets all have
>> issues.
Dave,
Can you elaborate more on the issue that you have with DFSORT as ZEDC is
supported by DFSORT. You can send an offline
I could be wrong about VSAM compression here then. Maybe that is all CP
compressed and I misunderstood by what mechanism that is done. We could not
survive here without VSAM compression. Many of our VSAM files are > 4G space
even compressed.
I do know we ARE using zEDC based on various
Peter,
Interesting. IBM says VSAM does NOT exploit ZEDC. VSAM can be compressed,
but it must all be done on CP, which would be expensive.Within a VSAM
LINEAR dataset used as ZFS, ZFS will engage ZEDC.
Dave Jousma
Vice President | Director, Technology Engineering
From: IBM
I do not know what criteria the sysprogs here set things up. But we are
successfully using zEDC here especially for our huge VSAM and GDG production
files.
I wish I could tell you more, but the sysprogs here are outsourced and getting
answers from them requires official paperwork and
Thank-you for this feedback. I’m starting to feel like this is a half-baked
solution looking for a problem. I know of no way to systematically code for
open for update….
Dave Jousma
Vice President | Director, Technology Engineering
From: IBM Mainframe Discussion List on behalf of
I'm'a try to post this from my lists@ address, because I suspect it will work.
Longish but (if you're reading it at all) it suggests some progress on the list
email issue.
To recap, as of a couple of weeks ago:
- I was suddenly not able to post from lists@
- I was still getting the daily digest
At a prior life, we got the zEDC cards on a z15, and turned that on for PS
datasets. But like you, we quickly learned that PS datasets opened for in/out
processing (update in place) did not work. As a compromise, we narrowed down
to new PS GDG datasets. Also we looked at new PS GDG datasets
Is anyone exploiting ZEDC data compression accelerator in your environments?
We recently licensed the enablement and are working through the issues in our
DEV environment.
We initially enabled Extended Format/COMPACT ZP, for all DSORG PS datasets, but
are quickly finding that DFSORT, SAS,
Anybody have a sample of how to return a fullword to a C program from an
assembler subroutine?
Apologies if this seems basic, but I really haven't looked seriously at C
before.
I have read about 'Combining C or C++ and Assembler programs', which didn't
help.
I have this C program (extract):
Grant.
We have not done the upgrade yet. I hope to run 2.3 without z/vm. I applied
whatever z16 maintenance was available without an extended support contract (
2.3 is out of support but was still supported when z16 A01 was released so I
was able to apply the PTFs for the 32Gb card and other
Thanks Keith,
Is that 2.3 running under VM? And did you apply the z16 toleration? We have
upgraded FICON cards in the current z14, these will be carried forward onto the
z16.
Thanks,
Grant
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Keith Gooding
Sent:
It may also depend on whether you have any new OSA or FICON cards which are not
supported by z/os 2.1. For instance the Z16 does not support the 8 Gb FICON
cards which could be carried forward to z14 and the new ones are 32Gb and PTFs
are required for these . Under z/Vm it may depend on whether
Classification: Confidential
Nope. z/OS 2.5 is no longer orderable
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Mark Jacobs
Sent: Tuesday, April 16, 2024 6:41 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: zOS and z16
[CAUTION: This Email is from outside the
One thing that might give you problems is WLM. It might behave wonky on a z16
processor. Is 2.5 even orderable any longer?
Mark Jacobs
Sent from ProtonMail, Swiss-based encrypted email.
GPG Public Key -
https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com
On Tuesday, April
Well...
Another reminiscence: I was obliged to destroy data on each medium
leaving datacenter. However I was also obliged to return replaced HDA
modules to supplier.
Fortunately I had a degausser.
--
Radoslaw Skorupka
Lodz, Poland
W dniu 16.04.2024 o 11:49, P H pisze:
Reminds me of
Hi,
We are running zVM 7.3 with zOS 2.1 under it, on a z14. We are upgrading to a
z16 soon - will 2.1 run on the 16 under zVM? I know that the minimum supported
level is 2.2 but (as I have seen asked previously with some of these
supported-or-not queries) does that mean it won't actually come
Reminds me of something that happened decades ago. A failing 3350 disk was
replaced. The failing disk was returned to supplier. The platters were very
shiny. The disk had been through a sand blasting machine
From: IBM Mainframe Discussion List on behalf of
"take disks back to work"
Well, an auditor could be very happy of this finding.
The disk was somewhere outside. Who read it? Was it replaced with
another one? Etc.
No, it is not so funny.
I know the case, financial company ordered disks destroyment. A lot of
disks - over 4000 approximately.
43 matches
Mail list logo
