Re: zOS.e, yes there was.

CVTOSLV5 DC    XL1'7F'       BYTE 5 OF CVTOSLVL
CVTZOSE  EQU   X'80'         z/OS.e
CVTZOSAS EQU   X'80'         z/OS.e
CVTPUMA  EQU   X'80'         z/OS.e

Mark Jacobs

Sent from ProtonMail, Swiss-based encrypted email.

GPG Public Key - 
https://api.protonmail.ch/pks/lookup?op=get&[email protected]

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Monday, April 5th, 2021 at 5:37 PM, Charles Mills <[email protected]> wrote:

> 1.  I have my reasons that I do not wish to go into in public. They are valid 
> reasons, and no, the reason does not involve bypassing any restriction.
> 2.  I do not want to use the CPU machine type for the exact reasons you 
> describe. I know IBM has done this with other models from time to time. I am 
> looking for a software flag.
>
>     Remember z/OS.e? Was there an in-memory flag for that?
>
>     Right: what is "production"? If you are a software development shop, 
> aren't compiles your "production"? I used to try (with limited success) to 
> make that argument with IBM support to justify a Sev 1: all my developers are 
> dead in the water -- development is my "production."
>
>     Charles
>
>     -----Original Message-----
>
>     From: IBM Mainframe Discussion List [mailto:[email protected]] On 
> Behalf Of Dave Jousma
>
>     Sent: Monday, April 5, 2021 11:36 AM
>
>     To: [email protected]
>
>     Subject: Re: Machine-readable flag for "development-only z/OS'
>
>     So, this question got me thinking.....
>
>     We have a few ZD&T instances running here. I was not fully involved with 
> the group bringing it in, other than setting some ground rules regarding 
> customization, and "who" would be supporting.
>
>     My recollection though, is that the Terms & Conditions of ZD&T state "no 
> production workload". However, to my knowledge there is no mechanical 
> enforcement of that? I mean what constitutes production workloads?
>
>     I'm only asking a theoretical question, in that since IBM doesn't enforce 
> via mechanical means, why bother at your end Charles to try to code something 
> for that? You know darn well the machine type will change one day, and if you 
> code off of that, it will break your code? What if someone is testing your 
> code validly in zD&T, but not using it for production?
>
> For IBM-MAIN subscribe / signoff / archive access instructions,
>
> send email to [email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to