Re: Netview

Radoslaw Skorupka wrote: >"vel" is not Polish. We don't have letter "v". It is latin, so I >supposed it is wide known. >And yes, it is "aka". >BTW: WTF is aka??? :-) Interesting. I believe ya (not gonna argue with someone about their native language!) but the usage seems to be Polish, per:

Re: Netview

"vel" is, amongst other things, Latin for "or". Peter *Vel*s On Sun, 28 Apr 2024 at 10:03, Bob Bridges < 0587168ababf-dmarc-requ...@listserv.ua.edu> wrote: > "Also Known As...". > > --- > Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313 > > /* I believe what really happens in history

Re: Netview

"Also Known As...". --- Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313 /* I believe what really happens in history is this: The old man is always wrong, and the young people are always wrong about what is wrong with him. The practical form it takes is this: that, while the old man may

Re: Netview

LOL, "polish my English" a small play on words. Sent from Proton Mail Android Original Message On 4/27/24 6:07 PM, Radoslaw Skorupka <0471ebeac275-dmarc-requ...@listserv.ua.edu> wrote: > (off-topic, but on-thread) > "vel" is not Polish. We don't have letter "v". It is

Re: Netview

On Sat, 27 Apr 2024, at 23:07, Radoslaw Skorupka wrote: > "vel" is not Polish. > And yes, it is "aka". > BTW: WTF is aka??? :-) "Also Known As", commonly used when listing aliases used by criminals, eg "Fred Smith aka Fred Jones aka James Jones". -- Jeremy Nicoll - my opinions are my own.

Re: Netview

Also Known As > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of Radoslaw Skorupka > Sent: Saturday, April 27, 2024 3:08 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Netview > > [EXTERNAL EMAIL] > > (off-topic, but on-thread) > "vel" is not Polish. We don't

Re: Netview

(off-topic, but on-thread) "vel" is not Polish. We don't have letter "v". It is latin, so I supposed it is wide known. And yes, it is "aka". BTW: WTF is aka??? :-) Last, but not least: thank you for kind words about my English (I still polish my English :-) ) -- Radoslaw Skorupka Lodz, Poland

Re: Hex error code interpreter?

Thanks to all; BPXMTEXT is what I was looking for, though it didn't help in this case. -Original Message- From: Phil Smith III Sent: Friday, April 26, 2024 6:16 PM To: 'IBM Mainframe Discussion List' ; 'mvs...@vm.marist.edu' Subject: Hex error code interpreter? Did I dream it, or is

Re: Anyone exploiting ZEDC?

On 4/16/2024 9:16 AM, Jousma, David wrote: Is anyone exploiting ZEDC data compression accelerator in your environments? We zEDC compress and encrypt our zFS file systems and SVC dumps. We zEDC compress our HSM backups on both DASD and TAPE and other large data sets such as the *huge* PDSEs

Re: Hex error code interpreter?

See gsk_strerror() On Fri, 26 Apr 2024 at 23:16, Phil Smith III wrote: > Did I dream it, or is there some utility that can take an error such as > gsk_encrypt_tls13_record(): AES GCM Encryption failed: Error 0x03353084 > and

Re: finding callers key in svc

is there any logic behind why MVC uses the actual byte count and MVCSK uses the 'number of bytes to the right'? As Wayne D pointed out, for MVC the user codes "n" and the instruction text uses "n-1". This is almost certainly for effectiveness. Having 8 bits of instruction text lets you cover

Re: Hex error code interpreter?

Here is the link (3,1) https://www.ibm.com/docs/en/zos/3.1.0?topic=errnojrs-description-location-information Reason codes are sometimes referred to as errnojrs or as errno2 values. The reason code is made up of 4 bytes in the following format: rrr is a halfword reason