Re: Netview

[Phil Smith III]

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:
https://en.wiktionary.org/wiki/vel#Polish

For anyone wondering: AKA is a TLA for Also Known As, i.e., vel :-)

("Wait, haven't we done this?" "Oh, yes, sorry!" - Monty Python, though I'm 
damned if I can remember anything else from the sketch
and probably don't have it 100% right)


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Netview

[Peter Vels]

"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 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
> stand by some stupid custom, the young man always attacks it with some
> theory that turns out to be equally stupid.  -G K Chesterton */
>
> -Original Message-
> From: IBM Mainframe Discussion List  On Behalf
> Of Radoslaw Skorupka
> Sent: Saturday, April 27, 2024 18:08
>
> "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 :-) )
>
> --
> 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: Netview

[Bob Bridges]

"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 stand by some 
stupid custom, the young man always attacks it with some theory that turns out 
to be equally stupid.  -G K Chesterton */

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Radoslaw Skorupka
Sent: Saturday, April 27, 2024 18:08

"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 :-) )

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Netview

[rpinion865]

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 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
>  
>  
>  
>  
>  W dniu 26.04.2024 o 18:25, Phil Smith III pisze:
>  > For those who are curious like me, "vel" is Polish for "AKA". That was my 
> guess, confirmed via Tha Goog.
>  >
>  > Not throwing shade at Radoslaw, whose English is better than that of a lot 
> of folks on the list who are native speakers!
>  >
>  > -Original Message-
>  > From: IBM Mainframe Discussion List  On Behalf 
> Of Radoslaw Skorupka
>  > Sent: Friday, April 26, 2024 7:22 AM
>  > To:IBM-MAIN@LISTSERV.UA.EDU
>  > Subject: Re: Netview
>  >
>  > It is not so easy.
>  > Do you know IWS vel TWS vel Workload Scheduler?
>  > It is still being sold by IBM, but development is out of IBM.
>  > The same for SDSF (Rocket), PCOMM (HCL), Omegamon, etc. The list is longer.
>  > And it is nothing new IMHO, as far as I remember ESCON Director was also 
> third party product under IBM logo.
>  >
>  > Note, JES3 and z/VSE are different - in both cases products are supported 
> and marketed by their current producers - that means PSI and 21CS.
>  >
>  > --
>  > Radoslaw Skorupka
>  > Lodz, Poland
>  >
>  >
>  >
>  > W dniu 26.04.2024 o 07:38, Bruce Hewson pisze:
>  >> Hello Steve,
>  >>
>  >> FUD
>  >>
>  >> "IBM Netview for Z/OS" is still being sold and supported by IBM, and is a 
> pre-req for IBM System Automation and GDPS.  No evidence that this product 
> has been sold.
>  >>
>  >> On Wed, 24 Apr 2024 16:19:17 -0500, Steve Beaver  
> wrote:
>  >>
>  >>> My understanding is that IBM sold off Netview.
>  >>>
>  >>> Who did they sell it to?
>  >>>
>  >>>
>  >>> Sent from my iPhone
>  >>>
>  >>> No one said I could type with one thumb
>  >>>
>  
>  --
>  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: Netview

[Jeremy Nicoll]

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.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Netview

[Gibney, Dave]

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 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
> 
> 
> 
> 
> W dniu 26.04.2024 o 18:25, Phil Smith III pisze:
> > For those who are curious like me, "vel" is Polish for "AKA". That was my
> guess, confirmed via Tha Goog.
> >
> > Not throwing shade at Radoslaw, whose English is better than that of a lot 
> > of
> folks on the list who are native speakers!
> >
> > -Original Message-
> > From: IBM Mainframe Discussion List  On
> > Behalf Of Radoslaw Skorupka
> > Sent: Friday, April 26, 2024 7:22 AM
> > To:IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: Netview
> >
> > It is not so easy.
> > Do you know IWS vel TWS vel Workload Scheduler?
> > It is still being sold by IBM, but development is out of IBM.
> > The same for SDSF (Rocket), PCOMM (HCL), Omegamon, etc. The list is
> longer.
> > And it is nothing new IMHO, as far as I remember ESCON Director was also
> third party product under IBM logo.
> >
> > Note, JES3 and z/VSE are different - in both cases products are supported
> and marketed by their current producers - that means PSI and 21CS.
> >
> > --
> > Radoslaw Skorupka
> > Lodz, Poland
> >
> >
> >
> > W dniu 26.04.2024 o 07:38, Bruce Hewson pisze:
> >> Hello Steve,
> >>
> >> FUD
> >>
> >> "IBM Netview for Z/OS" is still being sold and supported by IBM, and is a
> pre-req for IBM System Automation and GDPS.  No evidence that this product
> has been sold.
> >>
> >> On Wed, 24 Apr 2024 16:19:17 -0500, Steve
> Beaver  wrote:
> >>
> >>> My understanding is that IBM sold off Netview.
> >>>
> >>> Who did they sell it to?
> >>>
> >>>
> >>> Sent from my iPhone
> >>>
> >>> No one said I could type with one thumb
> >>>
> 
> --
> 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: Netview

[Radoslaw Skorupka]

(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




W dniu 26.04.2024 o 18:25, Phil Smith III pisze:

For those who are curious like me, "vel" is Polish for "AKA". That was my 
guess, confirmed via Tha Goog.

Not throwing shade at Radoslaw, whose English is better than that of a lot of 
folks on the list who are native speakers!

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Radoslaw Skorupka
Sent: Friday, April 26, 2024 7:22 AM
To:IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Netview

It is not so easy.
Do you know IWS vel TWS vel Workload Scheduler?
It is still being sold by IBM, but development is out of IBM.
The same for SDSF (Rocket), PCOMM (HCL), Omegamon, etc. The list is longer.
And it is nothing new IMHO, as far as I remember ESCON Director was also third 
party product under IBM logo.

Note, JES3 and z/VSE are different - in both cases products are supported and 
marketed by their current producers - that means PSI and 21CS.

--
Radoslaw Skorupka
Lodz, Poland



W dniu 26.04.2024 o 07:38, Bruce Hewson pisze:

Hello Steve,

FUD

"IBM Netview for Z/OS" is still being sold and supported by IBM, and is a 
pre-req for IBM System Automation and GDPS.  No evidence that this product has been sold.

On Wed, 24 Apr 2024 16:19:17 -0500, Steve Beaver  wrote:


My understanding is that IBM sold off Netview.

Who did they sell it to?


Sent from my iPhone

No one said I could type with one thumb



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Hex error code interpreter?

[Phil Smith III]

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 there some utility that can take an error such as
gsk_encrypt_tls13_record(): AES GCM Encryption failed: Error 0x03353084 and 
interpret the 0x03353084? I swear I remember seeing this but can't find it now. 
Getting old sucks*.

*But consider the alternatives.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Anyone exploiting ZEDC?

[Ed Jaffe]

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 that hold our product ADATA.


zEDC has saved us *significant* amounts of DASD space and actually sped 
up some processes that read these giant files.


I know everyone says "DASD is cheap" and I've heard the same about tape, 
but we never seem to have enough. IJS...


--
Phoenix Software International
Edward E. Jaffe
831 Parkview Drive North
El Segundo, CA 90245
https://www.phoenixsoftware.com/



This e-mail message, including any attachments, appended messages and the
information contained therein, is for the sole use of the intended
recipient(s). If you are not an intended recipient or have otherwise
received this email message in error, any use, dissemination, distribution,
review, storage or copying of this e-mail message and the information
contained therein is strictly prohibited. If you are not an intended
recipient, please contact the sender by reply e-mail and destroy all copies
of this email message and do not otherwise utilize or retain this email
message or any or all of the information contained therein. Although this
email message and any attachments or appended messages are believed to be
free of any virus or other defect that might affect any computer system into
which it is received and opened, it is the responsibility of the recipient
to ensure that it is virus free and no responsibility is accepted by the
sender for any loss or damage arising in any way from its opening or use.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Hex error code interpreter?

[Colin Paice]

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 interpret the 0x03353084? I swear I remember seeing this but can't
> find it now. Getting old sucks*.
>
> *But consider the alternatives.
>
> --
> 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: finding callers key in svc

[Peter Relson]

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 a range of 1-256 bytes instead of 0-255 bytes. 
You would have been very unhappy if you could only move 255 bytes with a single 
MVC if moving a long string (particularly in the days before MVCL). FWIW, this 
is why if you EXecute an MVC, the value you put into the register is "n-1".

For MVCSK/MVCDK, the user does not code a length, and the length is not in the 
instruction text. The length is in a register. So the user puts the value there 
by a separate instruction.

So both actually use "number of bytes to the right" (or, as I think of it, 
"length minus one").

You could ask "for MVCSK/MVCDK, since the length is in a register, why did you 
go with n-1 in the register instead of n?". I don't recall exactly but it was 
likely for either (or both) of consistency with MVC (such as the execute case) 
or for cost savings (perhaps being able to share part of the implementation).

As to the initial question, as pointed out, it depends on the type of the SVC. 
The SVC owner knows what type it is (because they defined it) and can look in 
the right place for that type of SVC, just as they look in the right place for 
the caller's regs (for which the answer is different than the psw/key, but 
similarly depends on the type of the SVC.

Peter Relson
z/OS Core Technology Design


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Hex error code interpreter?

[David Geib]

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 code qualifier. Generally this is used to identify 
the issuing module and represents a module ID.
 is the halfword reason code that is described in this documentation. Only 
this part of the reason code is intended as an interface for programmers.
If the contents of the two high-order bytes are within the range of X'' – 
X'20FF' the error that is represented by the reason code is provided in this 
documentation. The two high-order bytes of the reason codes returned contain a 
value that is used to qualify the contents of the two low-order bytes.

If the contents of the two high-order bytes are outside the range, the error 
that is represented by the reason code is not a z/OS UNIX reason code. Use 
Table 1 to determine where additional information on the reason code can be 
found.
For z/OS® UNIX, zFS, TCP/IP and Language Environment® reason codes, users can 
use either the BPXMTEXT TSO/E command or the bpxmtext shell command to display 
a reason code's meaning and recommended action.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN