date:20220301

Re: Meet Zorow, An Open Mainframe Project For z/OS Systems - Open Mainframe Project

2022-03-01 Thread Gord Tomlin


On 2022-03-01 22:49 PM, Matt Hogstrom wrote:

Zafod


Can't leave out Zardoz.

--

Regards, Gord Tomlin
Action Software International
(a division of Mazda Computer Corporation)
Tel: (905) 470-7113, Fax: (905) 470-6507
Support: https://actionsoftware.com/support/

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

Re: ZAD and C/C++ (was:: 2.5 Heads Up)

2022-03-01 Thread David Crayford

On Tue, 2022-03-01 at 10:35 -0800, Charles Mills wrote:
> Well, I am not the C standard, but you can find it online. 
> 
> I believe nullptr is numerically equal to zero, but it is a pointer
> type. It
> is perhaps equivalent to (void *)0

nullptr is a pointer literal of type std::nullptr_t, and it's a prvalue
  (you cannot take the address of it using &).

4.10 about pointer conversion says that a prvalue of type
std::nullptr_t is a null pointer constant, and that an integral null
pointer constant can be converted to std::nullptr_t. The opposite
direction is not allowed. This allows overloading a function for both
pointers and integers, and passing nullptr to select the pointer
version. Passing NULL or 0 would confusingly select the int version.

A cast of nullptr_t to an integral type needs a reinterpret_cast, and
has the same semantics as a cast of (void*)0 to an integral type
(mapping implementation defined). A reinterpret_cast cannot convert
nullptr_t to any pointer type. Rely on the implicit conversion if
possible or use static_cast.

The Standard requires that sizeof(nullptr_t) be sizeof(void*).

> 
> It is specifically not an integer, unlike NULL, which is another name
> for
> the integer zero.
> 
> 
> 
> int foo = NULL;  // compiles
> int bar = nullptr;  // generates an error 
> void *sojack = nullptr;   // compiles
> 
> Charles
> 
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On
> Behalf Of Seymour J Metz
> Sent: Tuesday, March 1, 2022 10:09 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: ZAD and C/C++ (was:: 2.5 Heads Up)
> 
> Is nullptr an address of 0, or is it an address guarantied to not be
> valid?
> 
> "An integer constant expression with the value 0, or such an
> expression cast
> to type void *, is called a null pointer constant. If a null pointer
> constant is converted to a pointer type, the resulting pointer,
> called a
> null pointer, is guaranteed to compare unequal to a pointer to any
> object or
> function."
> 
> 
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
> 
> 
> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on
> behalf of
> Charles Mills [charl...@mcn.org]
> Sent: Tuesday, March 1, 2022 11:46 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: ZAD and C/C++ (was:: 2.5 Heads Up)
> 
> C is a standardized language. IBM's main target market is programs
> ported
> from other platforms. I have no idea what the standard is, but IBM
> *may*
> simply be following it. fopen(NULL, ...) is pretty useless any way
> you slice
> it.
> 
> I have no idea what (void I)"" would mean and I don't *think* it is
> valid C.
> A quick test of auto foo = (void I)""; gives me a bunch of errors.
> 
> NULL is nothing special in C: it is just an alias for 0 (zero). That
> lead to
> a somewhat astonishing behavior in a particular situation involving
> overloaded functions, and the new (C++ only? Perhaps C also) language
> standards include nullptr, which is specifically an *address* of
> zero, and
> is a better usage than NULL if the meaning is "the address of
> nothing." That
> is, "you are expecting me to pass you an address and I am telling you
> that I
> have no address to give you."
> 
> Charles
> 
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On
> Behalf Of Paul Gilmartin
> Sent: Tuesday, March 1, 2022 8:30 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: ZAD and C/C++ (was:: 2.5 Heads Up)
> 
> On Tue, 1 Mar 2022 13:28:01 +,  wrote:
> > 
> > ZAD is not supported on z/OS under z/VM. ":-(
> > Is there any SOD or RFE or the like for this?
> > 
> > 
> Many releases ago, I saw a report the C RTL treatment of following a
> NULL pointer was changing.  I tested open( NULL, ... ) with releases
> before and after the change.  The earlier reported Invalid Pointer;
> the
> later Invalid Filename.  I considered the earlier more precise and
> correct.  I conjecture that IBM had fecklessly accommodated
> programmers accustomed to misusing NULL instead of e.g. (void I)"".
> 
> There are probably still programs that follow null pointers. What
> will
> become of them?
> 
> I favor strict error reporting.
> 
> -- gil
> 
> ---
> ---
> 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
> 
> ---
> ---
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-
> MAIN
> 
>

Re: Meet Zorow, An Open Mainframe Project For z/OS Systems - Open Mainframe Project

2022-03-01 Thread Matt Hogstrom

Zafod

Matt Hogstrom
PGP key 0F143BC1

> On Mar 1, 2022, at 21:51, David Spiegel  wrote:
> 
> Take a cue from Charles Manson ... Zezozose Zadfrack
> 
>> On 2022-03-01 20:01, PINION, RICHARD W. wrote:
>> No wait, Zoltar, from a MST3000 episode.
>> 
>> -Original Message-
>> From: IBM Mainframe Discussion List  On Behalf Of 
>> Charles Mills
>> Sent: Tuesday, March 1, 2022 7:49 PM
>> To: IBM-MAIN@LISTSERV.UA.EDU
>> Subject: Re: Meet Zorow, An Open Mainframe Project For z/OS Systems - Open 
>> Mainframe Project
>> 
>> [External Email. Exercise caution when clicking links or opening 
>> attachments.]
>> 
>> Geez, they're going to run out of weird Z words.
>> 
>> Zeme?
>> Zelotic?
>> Zarf?
>> Zari?
>> Zeze?
>> Ziti?
>> Zygon?
>> 
>> Charles
>> 
>> 
>> -Original Message-
>> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
>> Behalf Of Mark Regan
>> Sent: Tuesday, March 1, 2022 4:44 PM
>> To: IBM-MAIN@LISTSERV.UA.EDU
>> Subject: Fwd: Meet Zorow, An Open Mainframe Project For z/OS Systems - Open 
>> Mainframe Project
>> 
>> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2F%2Fwww.openmainframeproject.org%2Fblog%2F2022%2F02%2F23%2Fmeet-zorow-an-open-mainframe-project-for-z-os-systems__%3B!!HnnddUIWDII9UQ!GuvbfAnnC3hbYjun-Is7gluORxcAS5w0kiXFqvQmAWhJXlPRwysMd8ZeCiWQ%24data=04%7C01%7C%7C9a790e676a3f4ae7220408d9fbe8326e%7C84df9e7fe9f640afb435%7C1%7C0%7C637817797045843534%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=2SGJiNkfmL4UOFMSN5B8Q%2FgSQ%2F0N0TV6Hx2tUAL%2B16w%3Dreserved=0
>> 
>> 
>> 
>> Regards,
>> 
>> Mark Regan, K8MTR General, EN80tg
>> CTO1 USNR-Retired (1969-1991),
>> 
>> RUENAAA/CNO WASHINGTON DC//OP-009QCP
>> 
>> Nationwide Insurance, Retired, 1986-2017 z/OS Network Software Consultant (z 
>> NetView, z/OS Communications Server) Contractor, Checks & Balances, Inc.
>> Email: marktre...@gmail.com 
>> LinkedIn:  
>> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2F%2Fwww.linkedin.com%2Fin%2Fmark-t-regan__%3B!!HnnddUIWDII9UQ!GuvbfAnnC3hbYjun-Is7gluORxcAS5w0kiXFqvQmAWhJXlPRwysMdwcaCbEB%24data=04%7C01%7C%7C9a790e676a3f4ae7220408d9fbe8326e%7C84df9e7fe9f640afb435%7C1%7C0%7C637817797045843534%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=p5ncZgcjHSLNN%2BLUtPstwMVKr5MES%2FqR8rLfUPBGR0M%3Dreserved=0
>> 
>> 
>> 
>> 
>> 
>> 
>> --
>> 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
>> Confidentiality notice:
>> This e-mail message, including any attachments, may contain legally 
>> privileged and/or confidential information. If you are not the intended 
>> recipient(s), or the employee or agent responsible for delivery of this 
>> message to the intended recipient(s), you are hereby notified that any 
>> dissemination, distribution, or copying of this e-mail message is strictly 
>> prohibited. If you have received this message in error, please immediately 
>> notify the sender and delete this e-mail message from your computer.
>> 
>> 
>> --
>> 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

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

Re: ZAD and C/C++ (was:: 2.5 Heads Up)

2022-03-01 Thread Mike Schwab

https://en.wikipedia.org/wiki/Chin-Lung_Hu play for 2 MLB baseball teams.

On Tue, Mar 1, 2022 at 6:53 PM Charles Mills  wrote:
>
> > any ethnicity but their own
>
> In my much younger days -- the first significant system I ever worked on --
> I wrote a name-indexing scheme that assumed all surnames were at least three
> characters long. This was of course back in the day when we worried
> obsessively about bytes and CPU cycles.
>
> Turned out that the client -- Blue Cross of Northern California -- had
> hundreds of customers surnamed Ng.
>
> Oops.
>
> Charles
>
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Seymour J Metz
> Sent: Tuesday, March 1, 2022 10:46 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: ZAD and C/C++ (was:: 2.5 Heads Up)
>
> Metz's Law of Anal Retentive Developers: "Never validate an input field
> unless you *KNOW* what the rules are: assumption, belief, habit, urban
> legends, etc., don't count!" The world is full of people that "validate"
> names without having a clue about any ethnicity but their own and e-mail
> addresses when the can't even spell RFC. "An e-mail address is invalid if it
> uses characters hat I don't use in mine." or some such idiocy.
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



-- 
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

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

Re: Meet Zorow, An Open Mainframe Project For z/OS Systems - Open Mainframe Project

2022-03-01 Thread David Spiegel


Take a cue from Charles Manson ... Zezozose Zadfrack

On 2022-03-01 20:01, PINION, RICHARD W. wrote:

No wait, Zoltar, from a MST3000 episode.

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Charles Mills
Sent: Tuesday, March 1, 2022 7:49 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Meet Zorow, An Open Mainframe Project For z/OS Systems - Open 
Mainframe Project

[External Email. Exercise caution when clicking links or opening attachments.]

Geez, they're going to run out of weird Z words.

Zeme?
Zelotic?
Zarf?
Zari?
Zeze?
Ziti?
Zygon?

Charles


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Mark Regan
Sent: Tuesday, March 1, 2022 4:44 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Fwd: Meet Zorow, An Open Mainframe Project For z/OS Systems - Open 
Mainframe Project

https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2F%2Fwww.openmainframeproject.org%2Fblog%2F2022%2F02%2F23%2Fmeet-zorow-an-open-mainframe-project-for-z-os-systems__%3B!!HnnddUIWDII9UQ!GuvbfAnnC3hbYjun-Is7gluORxcAS5w0kiXFqvQmAWhJXlPRwysMd8ZeCiWQ%24data=04%7C01%7C%7C9a790e676a3f4ae7220408d9fbe8326e%7C84df9e7fe9f640afb435%7C1%7C0%7C637817797045843534%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=2SGJiNkfmL4UOFMSN5B8Q%2FgSQ%2F0N0TV6Hx2tUAL%2B16w%3Dreserved=0



Regards,

Mark Regan, K8MTR General, EN80tg
CTO1 USNR-Retired (1969-1991),

RUENAAA/CNO WASHINGTON DC//OP-009QCP

Nationwide Insurance, Retired, 1986-2017 z/OS Network Software Consultant (z 
NetView, z/OS Communications Server) Contractor, Checks & Balances, Inc.
Email: marktre...@gmail.com 
LinkedIn:  
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2F%2Fwww.linkedin.com%2Fin%2Fmark-t-regan__%3B!!HnnddUIWDII9UQ!GuvbfAnnC3hbYjun-Is7gluORxcAS5w0kiXFqvQmAWhJXlPRwysMdwcaCbEB%24data=04%7C01%7C%7C9a790e676a3f4ae7220408d9fbe8326e%7C84df9e7fe9f640afb435%7C1%7C0%7C637817797045843534%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=p5ncZgcjHSLNN%2BLUtPstwMVKr5MES%2FqR8rLfUPBGR0M%3Dreserved=0






--
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
Confidentiality notice:
This e-mail message, including any attachments, may contain legally privileged 
and/or confidential information. If you are not the intended recipient(s), or 
the employee or agent responsible for delivery of this message to the intended 
recipient(s), you are hereby notified that any dissemination, distribution, or 
copying of this e-mail message is strictly prohibited. If you have received 
this message in error, please immediately notify the sender and delete this 
e-mail message from your computer.


--
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: JES2, meaning of parameter value codes

2022-03-01 Thread Frank Swarbrick

Thanks!

For future reference: 
https://www.ibm.com/docs/en/zos/2.5.0?topic=rules-specifications

From: IBM Mainframe Discussion List  on behalf of 
Dana Mitchell 
Sent: Tuesday, March 1, 2022 11:15 AM
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: JES2, meaning of parameter value codes

I found this in the Introduction section of the JES2 Init & Tuning Reference:

Table 1. Initialization Parameter Character Specifications and Their Meanings
Character Meaning
a Alphabetic (A-Z)
c All EBCDIC characters (except ,()-=)
n Numeric (0-9)
m Numeric (0-9)
h Hexadecimal (0-9 and A-F)
j Alphabetic (A-Z) and the special characters ($, #, @)
v Alphabetic (A-Z) and numeric (0-9)
x Alphabetic (A-Z), numeric (0-9), and the special characters ($, #, @


On Tue, 1 Mar 2022 08:38:37 -0800, Tom Brennan  
wrote:

>I was thinking j might mean alpha and national, and c might mean alpha,
>national, or numeric.
>
>On 3/1/2022 2:51 AM, Seymour J Metz wrote:
>> Neither the J nor the Cs have any significance; jccc is just a variable 
>> name , as is nn. I probably would have used the name ddname, but that's only 
>> six characters.
>>

--
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: Meet Zorow, An Open Mainframe Project For z/OS Systems - Open Mainframe Project

2022-03-01 Thread PINION, RICHARD W.

No wait, Zoltar, from a MST3000 episode.

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Charles Mills
Sent: Tuesday, March 1, 2022 7:49 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Meet Zorow, An Open Mainframe Project For z/OS Systems - Open 
Mainframe Project

[External Email. Exercise caution when clicking links or opening attachments.]

Geez, they're going to run out of weird Z words.

Zeme?
Zelotic?
Zarf?
Zari?
Zeze?
Ziti?
Zygon?

Charles


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Mark Regan
Sent: Tuesday, March 1, 2022 4:44 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Fwd: Meet Zorow, An Open Mainframe Project For z/OS Systems - Open 
Mainframe Project

https://urldefense.com/v3/__https://www.openmainframeproject.org/blog/2022/02/23/meet-zorow-an-open-mainframe-project-for-z-os-systems__;!!HnnddUIWDII9UQ!GuvbfAnnC3hbYjun-Is7gluORxcAS5w0kiXFqvQmAWhJXlPRwysMd8ZeCiWQ$



Regards,

Mark Regan, K8MTR General, EN80tg
CTO1 USNR-Retired (1969-1991),

RUENAAA/CNO WASHINGTON DC//OP-009QCP

Nationwide Insurance, Retired, 1986-2017 z/OS Network Software Consultant (z 
NetView, z/OS Communications Server) Contractor, Checks & Balances, Inc.
Email: marktre...@gmail.com 
LinkedIn:  
https://urldefense.com/v3/__https://www.linkedin.com/in/mark-t-regan__;!!HnnddUIWDII9UQ!GuvbfAnnC3hbYjun-Is7gluORxcAS5w0kiXFqvQmAWhJXlPRwysMdwcaCbEB$






--
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
Confidentiality notice: 
This e-mail message, including any attachments, may contain legally privileged 
and/or confidential information. If you are not the intended recipient(s), or 
the employee or agent responsible for delivery of this message to the intended 
recipient(s), you are hereby notified that any dissemination, distribution, or 
copying of this e-mail message is strictly prohibited. If you have received 
this message in error, please immediately notify the sender and delete this 
e-mail message from your computer.


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

Re: Meet Zorow, An Open Mainframe Project For z/OS Systems - Open Mainframe Project

2022-03-01 Thread PINION, RICHARD W.

Zoltron, master of the universe!

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Charles Mills
Sent: Tuesday, March 1, 2022 7:49 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Meet Zorow, An Open Mainframe Project For z/OS Systems - Open 
Mainframe Project

[External Email. Exercise caution when clicking links or opening attachments.]

Geez, they're going to run out of weird Z words.

Zeme?
Zelotic?
Zarf?
Zari?
Zeze?
Ziti?
Zygon?

Charles


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Mark Regan
Sent: Tuesday, March 1, 2022 4:44 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Fwd: Meet Zorow, An Open Mainframe Project For z/OS Systems - Open 
Mainframe Project

https://urldefense.com/v3/__https://www.openmainframeproject.org/blog/2022/02/23/meet-zorow-an-open-mainframe-project-for-z-os-systems__;!!HnnddUIWDII9UQ!GuvbfAnnC3hbYjun-Is7gluORxcAS5w0kiXFqvQmAWhJXlPRwysMd8ZeCiWQ$



Regards,

Mark Regan, K8MTR General, EN80tg
CTO1 USNR-Retired (1969-1991),

RUENAAA/CNO WASHINGTON DC//OP-009QCP

Nationwide Insurance, Retired, 1986-2017 z/OS Network Software Consultant (z 
NetView, z/OS Communications Server) Contractor, Checks & Balances, Inc.
Email: marktre...@gmail.com 
LinkedIn:  
https://urldefense.com/v3/__https://www.linkedin.com/in/mark-t-regan__;!!HnnddUIWDII9UQ!GuvbfAnnC3hbYjun-Is7gluORxcAS5w0kiXFqvQmAWhJXlPRwysMdwcaCbEB$






--
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
Confidentiality notice: 
This e-mail message, including any attachments, may contain legally privileged 
and/or confidential information. If you are not the intended recipient(s), or 
the employee or agent responsible for delivery of this message to the intended 
recipient(s), you are hereby notified that any dissemination, distribution, or 
copying of this e-mail message is strictly prohibited. If you have received 
this message in error, please immediately notify the sender and delete this 
e-mail message from your computer.


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

Re: Meet Zorow, An Open Mainframe Project For z/OS Systems - Open Mainframe Project

2022-03-01 Thread Charles Mills

Geez, they're going to run out of weird Z words.

Zeme?
Zelotic?
Zarf?
Zari?
Zeze?
Ziti?
Zygon?

Charles


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Mark Regan
Sent: Tuesday, March 1, 2022 4:44 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Fwd: Meet Zorow, An Open Mainframe Project For z/OS Systems - Open 
Mainframe Project

https://www.openmainframeproject.org/blog/2022/02/23/meet-zorow-an-open-mainframe-project-for-z-os-systems
 

 

Regards,

Mark Regan, K8MTR General, EN80tg
CTO1 USNR-Retired (1969-1991), 

RUENAAA/CNO WASHINGTON DC//OP-009QCP

Nationwide Insurance, Retired, 1986-2017
z/OS Network Software Consultant (z NetView, z/OS Communications Server)
Contractor, Checks & Balances, Inc.
Email: marktre...@gmail.com  
LinkedIn:  https://www.linkedin.com/in/mark-t-regan

 

 


--
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

Fwd: Meet Zorow, An Open Mainframe Project For z/OS Systems - Open Mainframe Project

2022-03-01 Thread Mark Regan

https://www.openmainframeproject.org/blog/2022/02/23/meet-zorow-an-open-mainframe-project-for-z-os-systems
 

 

Regards,

Mark Regan, K8MTR General, EN80tg
CTO1 USNR-Retired (1969-1991), 

RUENAAA/CNO WASHINGTON DC//OP-009QCP

Nationwide Insurance, Retired, 1986-2017
z/OS Network Software Consultant (z NetView, z/OS Communications Server)
Contractor, Checks & Balances, Inc.
Email: marktre...@gmail.com  
LinkedIn:  https://www.linkedin.com/in/mark-t-regan

 

 


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

Re: APAR closures

2022-03-01 Thread Lennie Dymoke-Bradshaw

When I worked at IBM I was told that FIN was Fixed If Next. That is, it would 
be fixed if there was a next release.

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Bill Johnson
Sent: 01 March 2022 16:46
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: APAR closures

https://www.mainframes.com/Apar.html

Sent from Yahoo Mail for iPhone

On Tuesday, March 1, 2022, 11:38 AM, Phil Smith III  wrote:

Anyone got a complete list of APAR close statuses? Offhand I can think of 
things like FIN, IDOC, PTF (I think). I know there are more. It works, no point 
in reinventing that wheel.

--
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

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

Re: JES2, meaning of parameter value codes

2022-03-01 Thread Seymour J Metz

I submitted an RCF.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Dana Mitchell [mitchd...@gmail.com]
Sent: Tuesday, March 1, 2022 1:15 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: JES2, meaning of parameter value codes

I found this in the Introduction section of the JES2 Init & Tuning Reference:

Table 1. Initialization Parameter Character Specifications and Their Meanings
Character Meaning
a Alphabetic (A-Z)
c All EBCDIC characters (except ,()-=)
n Numeric (0-9)
m Numeric (0-9)
h Hexadecimal (0-9 and A-F)
j Alphabetic (A-Z) and the special characters ($, #, @)
v Alphabetic (A-Z) and numeric (0-9)
x Alphabetic (A-Z), numeric (0-9), and the special characters ($, #, @


On Tue, 1 Mar 2022 08:38:37 -0800, Tom Brennan  
wrote:

>I was thinking j might mean alpha and national, and c might mean alpha,
>national, or numeric.
>
>On 3/1/2022 2:51 AM, Seymour J Metz wrote:
>> Neither the J nor the Cs have any significance; jccc is just a variable 
>> name , as is nn. I probably would have used the name ddname, but that's only 
>> six characters.
>>

--
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: ZAD and C/C++ (was:: 2.5 Heads Up)

2022-03-01 Thread Paul Gilmartin

On Tue, 1 Mar 2022 10:53:44 -0800, Charles Mills wrote:

>> any ethnicity but their own
>.   ...
>I wrote a name-indexing scheme that assumed all surnames were at least three
>characters long. This was of course back in the day when we worried
>obsessively about bytes and CPU cycles.
> 
I worked at a site that required user names be (truncated) surname,
first initial, middle initial.  I searched CA directories so I could wonder
what they'd do if Cheng K. Fu of San Diego ever was hired.


>-Original Message-
>From: Seymour J Metz
>Sent: Tuesday, March 1, 2022 10:46 AM
>
>Metz's Law of Anal Retentive Developers: "Never validate an input field
>unless you *KNOW* what the rules are: assumption, belief, habit, urban
>legends, etc., don't count!" 
> 
Corollary:  Middleware shouldn't validate inputs beyond what the lowest
level does.  E.g. member names should be passed as-is to BLDL.  If
I can create it with Assembler I should be able to allocate it with JCL.

On Tue, 1 Mar 2022 19:13:21 +, Seymour J Metz wrote:

>When the field is 16 it's clear that they don't want the spaces, ...
>
That is not obvious to the casual eyeball at the first glance.  The
friendliest  systems either tolerate optional spaces or auto tab at
each 4 characters.

-- 
gil

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

Re: Fussy forms (was: ZAD ...)

2022-03-01 Thread Phil Smith III

Gil wrote, in part:

>Or a credit card space-separated in groups of four.  (The field is
>only 16 characters.) 

 

Yeah, just dumb. -1 for the limitation; -10 when they don't tell you before
you enter it; -100 when they don't tell you AFTER you enter it and make you
guess. There are plenty of pages that don't like, say, semicolons in text
fields, but just sit there and say "NO" if you use one. Nobody tests nothin'
no mo'. I blame (fr)Agile.

 

Of course card PANs will be going to 18 digits at some point. The brands
already tried to do that, and the issuers screamed, so now we have 8-digit
BINs. If any of you have had a Visa or Mastercard reissued with a new number
for no apparent reason lately, that's probably why: they clawed back some
6-digit BIN ranges that were underutilized and are reissuing them as 8-digit
BINs. So if you were an issuer and had Visa BINs:

41

42

43

but had only issued a few thousand cards in the 43 range, Visa may have
told you "You have to give 43 back and reissue those cards with some
other BIN". Then they'll issue 99 8-digit BINs in the range 4300 through
4399 to other issuers. In some cases I suppose it's possible that an
8-digit BIN will simply get converted to 8-digit-that is, if our putative
issuer above had issued their few thousand cards all in 4301, then they
might get told "OK, you can keep that BIN but don't use any others in the
43 range", though my guess is that the brands will not take the risk
that the issuer will get that wrong. Easier to just say "No more 43 for
a while".

 

Anyway, stay tuned for 18-digit BINs, coming soon(ish)! I didn't notice when
they went from 13 to 16, but I do remember a 13-digit Visa number of mine
from the 90s (yes, that's a *really useful* way to spend what's left of my
memory!).


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

Re: Fussy forms (was: ZAD ...)

2022-03-01 Thread Seymour J Metz

When the field is 16 it's clear that they don't want the spaces, but if they 
want everything abutted then why make the field longer, and why not at least 
state not to enter the punctuation?

"Stupidity above and beyond the call of duty"

Let me know if you need an alibi.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Paul Gilmartin [000433f07816-dmarc-requ...@listserv.ua.edu]
Sent: Tuesday, March 1, 2022 2:07 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Fussy forms (was: ZAD ...)

On Tue, 1 Mar 2022 10:29:57 -0800, Charles Mills wrote:

>.   ...
>There is so much HORRIBLE error diagnosis out there. I have been wrestling the 
>past week with the Google App Store. Would not take an e-mail address on a 
>particular page. Error message: "E-mail address is not valid." Huh? I get 
>e-mail there.  ...
>
Many sites reject my RFC 822-compliiant, copied from my Contacts:
"Paul Gilmartin "

*And* they case-convert the local part which RFC 822 specifies as-is.

Or my phone:
"(720) 382-"
("Numbers only!")

Or a credit card space-separated in groups of four.  (The field is
only 16 characters.)

--
gil

--
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: ZAD and C/C++ (was:: 2.5 Heads Up)

2022-03-01 Thread Seymour J Metz

There was an IBM employee with that surname who gave excellent diagnostic 
presentations at SHARE.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Charles Mills [charl...@mcn.org]
Sent: Tuesday, March 1, 2022 1:53 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ZAD and C/C++ (was:: 2.5 Heads Up)

> any ethnicity but their own

In my much younger days -- the first significant system I ever worked on --
I wrote a name-indexing scheme that assumed all surnames were at least three
characters long. This was of course back in the day when we worried
obsessively about bytes and CPU cycles.

Turned out that the client -- Blue Cross of Northern California -- had
hundreds of customers surnamed Ng.

Oops.

Charles


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Seymour J Metz
Sent: Tuesday, March 1, 2022 10:46 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ZAD and C/C++ (was:: 2.5 Heads Up)

Metz's Law of Anal Retentive Developers: "Never validate an input field
unless you *KNOW* what the rules are: assumption, belief, habit, urban
legends, etc., don't count!" The world is full of people that "validate"
names without having a clue about any ethnicity but their own and e-mail
addresses when the can't even spell RFC. "An e-mail address is invalid if it
uses characters hat I don't use in mine." or some such idiocy.

--
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

Fussy forms (was: ZAD ...)

2022-03-01 Thread Paul Gilmartin

On Tue, 1 Mar 2022 10:29:57 -0800, Charles Mills wrote:

>.   ...
>There is so much HORRIBLE error diagnosis out there. I have been wrestling the 
>past week with the Google App Store. Would not take an e-mail address on a 
>particular page. Error message: "E-mail address is not valid." Huh? I get 
>e-mail there.  ...
>
Many sites reject my RFC 822-compliiant, copied from my Contacts:
"Paul Gilmartin "

*And* they case-convert the local part which RFC 822 specifies as-is.

Or my phone:
"(720) 382-"
("Numbers only!")

Or a credit card space-separated in groups of four.  (The field is
only 16 characters.)

--
gil

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

Re: ZAD and C/C++ (was:: 2.5 Heads Up)

2022-03-01 Thread Charles Mills

> any ethnicity but their own

In my much younger days -- the first significant system I ever worked on --
I wrote a name-indexing scheme that assumed all surnames were at least three
characters long. This was of course back in the day when we worried
obsessively about bytes and CPU cycles.

Turned out that the client -- Blue Cross of Northern California -- had
hundreds of customers surnamed Ng.

Oops.

Charles


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Seymour J Metz
Sent: Tuesday, March 1, 2022 10:46 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ZAD and C/C++ (was:: 2.5 Heads Up)

Metz's Law of Anal Retentive Developers: "Never validate an input field
unless you *KNOW* what the rules are: assumption, belief, habit, urban
legends, etc., don't count!" The world is full of people that "validate"
names without having a clue about any ethnicity but their own and e-mail
addresses when the can't even spell RFC. "An e-mail address is invalid if it
uses characters hat I don't use in mine." or some such idiocy.

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

Re: ZAD and C/C++ (was:: 2.5 Heads Up)

2022-03-01 Thread Seymour J Metz

I believe that in current PL/I compilers, NULL is an address that z/OS 
guaranties to be invalid, i.e., no page frame assigned. Way back when, PL/I 
used zero, which caused the obvious problems.

--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Charles Mills [charl...@mcn.org]
Sent: Tuesday, March 1, 2022 1:47 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ZAD and C/C++ (was:: 2.5 Heads Up)

I see what you are asking. You are probably quoting the standard correctly.
I am speaking as a practical programmer, not as a standards writer:

- It is guaranteed to be consistent. If you pass me nullptr and I compare
what you pass to nullptr it will always compare equal, even if your code was
compiled differently from mine.
- It is never the address of any actual C "thing." There is no risk that you
pass me the address of some C "thing" and it turns out coincidentally to be
logically equal to nullptr. (Yes, if you pass me the address of the PSA that
logic will fail. I would say the PSA is not a "C thing.")
- It is in fact 0 on the three C's I care about: MS, gcc and xlc (and
probably Clang) -- and I am going to guess most other C's.

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Seymour J Metz
Sent: Tuesday, March 1, 2022 10:09 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ZAD and C/C++ (was:: 2.5 Heads Up)

Is nullptr an address of 0, or is it an address guarantied to not be valid?

"An integer constant expression with the value 0, or such an expression cast
to type void *, is called a null pointer constant. If a null pointer
constant is converted to a pointer type, the resulting pointer, called a
null pointer, is guaranteed to compare unequal to a pointer to any object or
function."

--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Charles Mills [charl...@mcn.org]
Sent: Tuesday, March 1, 2022 11:46 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ZAD and C/C++ (was:: 2.5 Heads Up)

C is a standardized language. IBM's main target market is programs ported
from other platforms. I have no idea what the standard is, but IBM *may*
simply be following it. fopen(NULL, ...) is pretty useless any way you slice
it.

I have no idea what (void I)"" would mean and I don't *think* it is valid C.
A quick test of auto foo = (void I)""; gives me a bunch of errors.

NULL is nothing special in C: it is just an alias for 0 (zero). That lead to
a somewhat astonishing behavior in a particular situation involving
overloaded functions, and the new (C++ only? Perhaps C also) language
standards include nullptr, which is specifically an *address* of zero, and
is a better usage than NULL if the meaning is "the address of nothing." That
is, "you are expecting me to pass you an address and I am telling you that I
have no address to give you."

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Paul Gilmartin
Sent: Tuesday, March 1, 2022 8:30 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: ZAD and C/C++ (was:: 2.5 Heads Up)

On Tue, 1 Mar 2022 13:28:01 +,  wrote:
>
>ZAD is not supported on z/OS under z/VM. ":-(
>Is there any SOD or RFE or the like for this?
>
>
Many releases ago, I saw a report the C RTL treatment of following a
NULL pointer was changing.  I tested open( NULL, ... ) with releases
before and after the change.  The earlier reported Invalid Pointer; the
later Invalid Filename.  I considered the earlier more precise and
correct.  I conjecture that IBM had fecklessly accommodated
programmers accustomed to misusing NULL instead of e.g. (void I)"".

There are probably still programs that follow null pointers. What will
become of them?

I favor strict error reporting.

-- gil

--
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

--
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

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to

Re: ZAD and C/C++ (was:: 2.5 Heads Up)

2022-03-01 Thread Seymour J Metz

I once had lust in my heart for the PEDANT license plate in the NSF garage. 
And, yes, some of these "minor" pedantic difference do have major practical 
consequences.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Paul Gilmartin [000433f07816-dmarc-requ...@listserv.ua.edu]
Sent: Tuesday, March 1, 2022 1:42 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ZAD and C/C++ (was:: 2.5 Heads Up)

On Tue, 1 Mar 2022 18:09:14 +, Seymour J Metz wrote:

>Is nullptr an address of 0, or is it an address guarantied to not be valid?
>
Ah, pedantry!  It depends on whether "invalid" is equivalent to "unequal
to a pointer to any object ..." (or whether one implies the other.). The
statement below does not constrain the storage representation of NULL
(as in type-punning).  I believe the behavior of "if ( NULL ) ..." (specified
elsewhere) requires that (intt) NULL be zero.

Cases to consider:
o a putative pointer to the interior of a multi-byte object
o an arbitrary int value cast to (void *)
o a pointer to a free()ed object.

>�An integer constant expression with the value 0, or such an expression cast 
>to type void *, is called a null pointer constant. If a null pointer constant 
>is converted to a pointer type, the resulting pointer, called a null pointer, 
>is guaranteed to compare unequal to a pointer to any object or function.�

--
gil

--
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: ZAD and C/C++ (was:: 2.5 Heads Up)

2022-03-01 Thread Charles Mills

I see what you are asking. You are probably quoting the standard correctly.
I am speaking as a practical programmer, not as a standards writer:

- It is guaranteed to be consistent. If you pass me nullptr and I compare
what you pass to nullptr it will always compare equal, even if your code was
compiled differently from mine.
- It is never the address of any actual C "thing." There is no risk that you
pass me the address of some C "thing" and it turns out coincidentally to be
logically equal to nullptr. (Yes, if you pass me the address of the PSA that
logic will fail. I would say the PSA is not a "C thing.")
- It is in fact 0 on the three C's I care about: MS, gcc and xlc (and
probably Clang) -- and I am going to guess most other C's.

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Seymour J Metz
Sent: Tuesday, March 1, 2022 10:09 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ZAD and C/C++ (was:: 2.5 Heads Up)

Is nullptr an address of 0, or is it an address guarantied to not be valid?

"An integer constant expression with the value 0, or such an expression cast
to type void *, is called a null pointer constant. If a null pointer
constant is converted to a pointer type, the resulting pointer, called a
null pointer, is guaranteed to compare unequal to a pointer to any object or
function."

--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Charles Mills [charl...@mcn.org]
Sent: Tuesday, March 1, 2022 11:46 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ZAD and C/C++ (was:: 2.5 Heads Up)

C is a standardized language. IBM's main target market is programs ported
from other platforms. I have no idea what the standard is, but IBM *may*
simply be following it. fopen(NULL, ...) is pretty useless any way you slice
it.

I have no idea what (void I)"" would mean and I don't *think* it is valid C.
A quick test of auto foo = (void I)""; gives me a bunch of errors.

NULL is nothing special in C: it is just an alias for 0 (zero). That lead to
a somewhat astonishing behavior in a particular situation involving
overloaded functions, and the new (C++ only? Perhaps C also) language
standards include nullptr, which is specifically an *address* of zero, and
is a better usage than NULL if the meaning is "the address of nothing." That
is, "you are expecting me to pass you an address and I am telling you that I
have no address to give you."

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Paul Gilmartin
Sent: Tuesday, March 1, 2022 8:30 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: ZAD and C/C++ (was:: 2.5 Heads Up)

On Tue, 1 Mar 2022 13:28:01 +,  wrote:
>
>ZAD is not supported on z/OS under z/VM. ":-(
>Is there any SOD or RFE or the like for this?
>
>
Many releases ago, I saw a report the C RTL treatment of following a
NULL pointer was changing.  I tested open( NULL, ... ) with releases
before and after the change.  The earlier reported Invalid Pointer; the
later Invalid Filename.  I considered the earlier more precise and
correct.  I conjecture that IBM had fecklessly accommodated
programmers accustomed to misusing NULL instead of e.g. (void I)"".

There are probably still programs that follow null pointers. What will
become of them?

I favor strict error reporting.

-- gil

--
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

--
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: ZAD and C/C++ (was:: 2.5 Heads Up)

2022-03-01 Thread Seymour J Metz

Metz's Law of Anal Retentive Developers: "Never validate an input field unless 
you *KNOW* what the rules are: assumption, belief, habit, urban legends, etc., 
don't count!" The world is full of people that "validate" names without having 
a clue about any ethnicity but their own and e-mail addresses when the can't 
even spell RFC. "An e-mail address is invalid if it uses characters hat I don't 
use in mine." or some such idiocy.

My other pet peeve for web sites is forms with long input fields and no 
explanation of the required syntax. Are blanks allowed, mandatory or 
prohibited? Ditto hyphens and slashes. Is a long ZIP code field 5 or 9? I can't 
think of any others off the top of my head, but I would bet that they exist.

Or take client-side scripts - please!

--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Charles Mills [charl...@mcn.org]
Sent: Tuesday, March 1, 2022 1:29 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ZAD and C/C++ (was:: 2.5 Heads Up)

Ah! (void *). I know what that means, but I am perhaps too dense to see what 
(void *)"" would accomplish. I "get" what it is doing -- casting a char* (or 
maybe a const char*) as a void* -- but other than for some obscure test I don't 
see the purpose.

Certainly open(NULL, ...) is a possible real-life mistake. You write a function 
that expects a passed file name; I call it thinking it is "smart" enough to 
know that a filename of NULL means don't use a file; you try to open what I 
pass.

Too lazy to test and see what happens. I certainly agree that "bad address" is 
a lot more useful than "no such file." "Address is NULL" would be even more 
useful, to distinguish this special case from the case of some random garbage 
pointer. The programmer could look for "how might I be passing NULL?" as 
opposed to looking for "what might have corrupted that address?"

There is so much HORRIBLE error diagnosis out there. I have been wrestling the 
past week with the Google App Store. Would not take an e-mail address on a 
particular page. Error message: "E-mail address is not valid." Huh? I get 
e-mail there. After hours of hacking it turned out to mean "that e-mail address 
is not associated with any gmail address." Another situation where it was 
rejecting an e-mail address, this time with the error "! Try reformatting". 
Well, gee, it was your basic e-mail format, som...@domain.com. No blanks or 
anything like that. Never did figure out what they wanted; got around the 
problem another way.

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Paul Gilmartin
Sent: Tuesday, March 1, 2022 9:48 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ZAD and C/C++ (was:: 2.5 Heads Up)

On Tue, 1 Mar 2022 08:46:35 -0800, Charles Mills  wrote:

>..., but IBM *may* simply be following it. fopen(NULL, ...) is pretty 
> useless any way you slice it.
>

On Mac OS:
printf ("%d\n",  open( "",   0  ) );
-1
No such file or directory

printf ("%d\n",  open( NULL, 0  ) );
-1
Bad address

I think both are optimal.  OpenGroup doesn't specify the latter/

>I have no idea what (void I)"" would
>
Typo for (void *).  Short finger?

--
gil

--
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

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

Re: ZAD and C/C++ (was:: 2.5 Heads Up)

2022-03-01 Thread Paul Gilmartin

On Tue, 1 Mar 2022 18:09:14 +, Seymour J Metz wrote:

>Is nullptr an address of 0, or is it an address guarantied to not be valid?
>
Ah, pedantry!  It depends on whether "invalid" is equivalent to "unequal
to a pointer to any object ..." (or whether one implies the other.). The
statement below does not constrain the storage representation of NULL
(as in type-punning).  I believe the behavior of "if ( NULL ) ..." (specified
elsewhere) requires that (intt) NULL be zero.

Cases to consider:
o a putative pointer to the interior of a multi-byte object
o an arbitrary int value cast to (void *)
o a pointer to a free()ed object.

>�An integer constant expression with the value 0, or such an expression cast 
>to type void *, is called a null pointer constant. If a null pointer constant 
>is converted to a pointer type, the resulting pointer, called a null pointer, 
>is guaranteed to compare unequal to a pointer to any object or function.�

-- 
gil

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

Re: ZAD and C/C++ (was:: 2.5 Heads Up)

2022-03-01 Thread Charles Mills

Well, I am not the C standard, but you can find it online. 

I believe nullptr is numerically equal to zero, but it is a pointer type. It
is perhaps equivalent to (void *)0

It is specifically not an integer, unlike NULL, which is another name for
the integer zero.

int foo = NULL;  // compiles
int bar = nullptr;  // generates an error 
void *sojack = nullptr;   // compiles

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Seymour J Metz
Sent: Tuesday, March 1, 2022 10:09 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ZAD and C/C++ (was:: 2.5 Heads Up)

Is nullptr an address of 0, or is it an address guarantied to not be valid?

"An integer constant expression with the value 0, or such an expression cast
to type void *, is called a null pointer constant. If a null pointer
constant is converted to a pointer type, the resulting pointer, called a
null pointer, is guaranteed to compare unequal to a pointer to any object or
function."

--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Charles Mills [charl...@mcn.org]
Sent: Tuesday, March 1, 2022 11:46 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ZAD and C/C++ (was:: 2.5 Heads Up)

C is a standardized language. IBM's main target market is programs ported
from other platforms. I have no idea what the standard is, but IBM *may*
simply be following it. fopen(NULL, ...) is pretty useless any way you slice
it.

I have no idea what (void I)"" would mean and I don't *think* it is valid C.
A quick test of auto foo = (void I)""; gives me a bunch of errors.

NULL is nothing special in C: it is just an alias for 0 (zero). That lead to
a somewhat astonishing behavior in a particular situation involving
overloaded functions, and the new (C++ only? Perhaps C also) language
standards include nullptr, which is specifically an *address* of zero, and
is a better usage than NULL if the meaning is "the address of nothing." That
is, "you are expecting me to pass you an address and I am telling you that I
have no address to give you."

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Paul Gilmartin
Sent: Tuesday, March 1, 2022 8:30 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: ZAD and C/C++ (was:: 2.5 Heads Up)

On Tue, 1 Mar 2022 13:28:01 +,  wrote:
>
>ZAD is not supported on z/OS under z/VM. ":-(
>Is there any SOD or RFE or the like for this?
>
>
Many releases ago, I saw a report the C RTL treatment of following a
NULL pointer was changing.  I tested open( NULL, ... ) with releases
before and after the change.  The earlier reported Invalid Pointer; the
later Invalid Filename.  I considered the earlier more precise and
correct.  I conjecture that IBM had fecklessly accommodated
programmers accustomed to misusing NULL instead of e.g. (void I)"".

There are probably still programs that follow null pointers. What will
become of them?

I favor strict error reporting.

-- gil

--
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

--
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: ZAD and C/C++ (was:: 2.5 Heads Up)

2022-03-01 Thread Charles Mills

Ah! (void *). I know what that means, but I am perhaps too dense to see what 
(void *)"" would accomplish. I "get" what it is doing -- casting a char* (or 
maybe a const char*) as a void* -- but other than for some obscure test I don't 
see the purpose.

Certainly open(NULL, ...) is a possible real-life mistake. You write a function 
that expects a passed file name; I call it thinking it is "smart" enough to 
know that a filename of NULL means don't use a file; you try to open what I 
pass.

Too lazy to test and see what happens. I certainly agree that "bad address" is 
a lot more useful than "no such file." "Address is NULL" would be even more 
useful, to distinguish this special case from the case of some random garbage 
pointer. The programmer could look for "how might I be passing NULL?" as 
opposed to looking for "what might have corrupted that address?"

There is so much HORRIBLE error diagnosis out there. I have been wrestling the 
past week with the Google App Store. Would not take an e-mail address on a 
particular page. Error message: "E-mail address is not valid." Huh? I get 
e-mail there. After hours of hacking it turned out to mean "that e-mail address 
is not associated with any gmail address." Another situation where it was 
rejecting an e-mail address, this time with the error "! Try reformatting". 
Well, gee, it was your basic e-mail format, som...@domain.com. No blanks or 
anything like that. Never did figure out what they wanted; got around the 
problem another way. 

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Paul Gilmartin
Sent: Tuesday, March 1, 2022 9:48 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ZAD and C/C++ (was:: 2.5 Heads Up)

On Tue, 1 Mar 2022 08:46:35 -0800, Charles Mills  wrote:

>..., but IBM *may* simply be following it. fopen(NULL, ...) is pretty 
> useless any way you slice it.
>

On Mac OS:
printf ("%d\n",  open( "",   0  ) );
-1
No such file or directory

printf ("%d\n",  open( NULL, 0  ) );
-1
Bad address

I think both are optimal.  OpenGroup doesn't specify the latter/

>I have no idea what (void I)"" would 
>
Typo for (void *).  Short finger?

-- 
gil

--
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: JES2, meaning of parameter value codes

2022-03-01 Thread Dana Mitchell

I found this in the Introduction section of the JES2 Init & Tuning Reference:

Table 1. Initialization Parameter Character Specifications and Their Meanings
Character Meaning
a Alphabetic (A-Z)
c All EBCDIC characters (except ,()-=)
n Numeric (0-9)
m Numeric (0-9)
h Hexadecimal (0-9 and A-F)
j Alphabetic (A-Z) and the special characters ($, #, @)
v Alphabetic (A-Z) and numeric (0-9)
x Alphabetic (A-Z), numeric (0-9), and the special characters ($, #, @


On Tue, 1 Mar 2022 08:38:37 -0800, Tom Brennan  
wrote:

>I was thinking j might mean alpha and national, and c might mean alpha,
>national, or numeric.
>
>On 3/1/2022 2:51 AM, Seymour J Metz wrote:
>> Neither the J nor the Cs have any significance; jccc is just a variable 
>> name , as is nn. I probably would have used the name ddname, but that's only 
>> six characters.
>>

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

Re: JES2, meaning of parameter value codes

2022-03-01 Thread Seymour J Metz

That's definitely a requirement for a ddname; whether it's the reason I have no 
way of determining.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Tom 
Brennan [t...@tombrennansoftware.com]
Sent: Tuesday, March 1, 2022 11:38 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: JES2, meaning of parameter value codes

I was thinking j might mean alpha and national, and c might mean alpha,
national, or numeric.

On 3/1/2022 2:51 AM, Seymour J Metz wrote:
> Neither the J nor the Cs have any significance; jccc is just a variable 
> name , as is nn. I probably would have used the name ddname, but that's only 
> six characters.
>
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
>
> 
> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
> Frank Swarbrick [frank.swarbr...@outlook.com]
> Sent: Tuesday, March 1, 2022 2:44 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: JES2, meaning of parameter value codes
>
> But what is the 'j' in 'jccc'?  Why not just ''?
> 
> From: IBM Mainframe Discussion List  on behalf of 
> Seymour J Metz 
> Sent: Monday, February 28, 2022 6:38 PM
> To: IBM-MAIN@LISTSERV.UA.EDU 
> Subject: Re: JES2, meaning of parameter value codes
>
> What is unclear? nn is any two digit number. jccc is any character string 
> that is a valid ddname. PROCnn or Jccc names a concatenation that can be 
> selected as the procedure library concatenation for a job, as specified by 
> JOBCLASS(v), JOBCLASS(STC), JOBCLASS(TSU) or  /*JOBPARM PROCLIB=ddname. You 
> need to look at the JES2 JCL, any PROCLIB(foo) statement in the 
> initialization member and any subsequent commands, e.g., $ADD PROCLIB, to see 
> what is in each concatenation.
>
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
>
> 
> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
> Frank Swarbrick [frank.swarbr...@outlook.com]
> Sent: Monday, February 28, 2022 7:21 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: JES2, meaning of parameter value codes
>
> https://www.ibm.com/docs/en/zos/2.5.0?topic=class-parameter-description-jobclassclassstctsu
>
> PROCLIB=nn|j|00
> Specifies the default 2-8 character procedure library name (jccc) or 
> procedure library number (0-99) which is to be used for this job class. It 
> allows you to specify procedure libraries for different job classes. In the 
> JES2 procedure, one DD statement must be named PROC00. If you specify 
> additional procedure libraries (jccc or 01-99), then you might associate 
> these libraries to a job class by replacing the jccc or nn of this 
> parameter with the appropriate procedure library name or number. All 
> cataloged procedure libraries to be used by jobs, time-sharing users, or 
> system tasks must be defined in the JES2 procedure.
>
> z/OS 2.5
>
> 
> From: IBM Mainframe Discussion List  on behalf of 
> Seymour J Metz 
> Sent: Monday, February 28, 2022 5:09 PM
> To: IBM-MAIN@LISTSERV.UA.EDU 
> Subject: Re: JES2, meaning of parameter value codes
>
> Please post example and release level.
>
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
>
> 
> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
> Frank Swarbrick [frank.swarbr...@outlook.com]
> Sent: Monday, February 28, 2022 6:31 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: JES2, meaning of parameter value codes
>
> I am looking at the JES2 Initialization and Tuning Reference.  There are 
> examples job parameters with codes such as "jxxx" and "jccc".  I 
> can't seem to find a table of their meanings.  Can someone point me in the 
> right direction?
> Thanks,
> Frank
>
> --
> 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
>
> --
> 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
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send

Re: ZAD and C/C++ (was:: 2.5 Heads Up)

2022-03-01 Thread Seymour J Metz

Is nullptr an address of 0, or is it an address guarantied to not be valid?

“An integer constant expression with the value 0, or such an expression cast to 
type void *, is called a null pointer constant. If a null pointer constant is 
converted to a pointer type, the resulting pointer, called a null pointer, is 
guaranteed to compare unequal to a pointer to any object or function.”

--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Charles Mills [charl...@mcn.org]
Sent: Tuesday, March 1, 2022 11:46 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ZAD and C/C++ (was:: 2.5 Heads Up)

C is a standardized language. IBM's main target market is programs ported from 
other platforms. I have no idea what the standard is, but IBM *may* simply be 
following it. fopen(NULL, ...) is pretty useless any way you slice it.

I have no idea what (void I)"" would mean and I don't *think* it is valid C. A 
quick test of auto foo = (void I)""; gives me a bunch of errors.

NULL is nothing special in C: it is just an alias for 0 (zero). That lead to a 
somewhat astonishing behavior in a particular situation involving overloaded 
functions, and the new (C++ only? Perhaps C also) language standards include 
nullptr, which is specifically an *address* of zero, and is a better usage than 
NULL if the meaning is "the address of nothing." That is, "you are expecting me 
to pass you an address and I am telling you that I have no address to give you."

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Paul Gilmartin
Sent: Tuesday, March 1, 2022 8:30 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: ZAD and C/C++ (was:: 2.5 Heads Up)

On Tue, 1 Mar 2022 13:28:01 +,  wrote:
>
>ZAD is not supported on z/OS under z/VM. ":-(
>Is there any SOD or RFE or the like for this?
>
>
Many releases ago, I saw a report the C RTL treatment of following a
NULL pointer was changing.  I tested open( NULL, ... ) with releases
before and after the change.  The earlier reported Invalid Pointer; the
later Invalid Filename.  I considered the earlier more precise and
correct.  I conjecture that IBM had fecklessly accommodated
programmers accustomed to misusing NULL instead of e.g. (void I)"".

There are probably still programs that follow null pointers. What will
become of them?

I favor strict error reporting.

-- gil

--
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

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

Re: S0C4 pic 4

2022-03-01 Thread Joseph Reichman

Just tried to recreate it wasn't able to you have to believe I spent hours 
looking at it will double check later

So Sorry ☹ 
-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Seymour J Metz
Sent: Tuesday, March 1, 2022 10:12 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: S0C4 pic 4

What was in

 The PSW
 The general registers
 The failing instruction


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Joseph Reichman [reichman...@gmail.com]
Sent: Tuesday, March 1, 2022 8:07 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: S0C4 pic 4

Just got a s0c4 pic 4

I was running under TESTAUTO did listpsw was in psw key 8

then before I did SPKA X'80' MODESET MODE=PROB did a ISVK on the offending
storage and got X'0088'

the program was linked to the storage was obtained by the invoker of the
link but everything is under the same TCB

--
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

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

Re: APAR closures

2022-03-01 Thread Paul Gilmartin

On Tue, 1 Mar 2022 11:38:24 -0500, Phil Smith III  wrote:

>Anyone got a complete list of APAR close statuses? Offhand I can think of
>things like FIN, IDOC, PTF (I think). I know there are more. It works, no
>point in reinventing that wheel.
> 
I finid:

Here is a direct link to that section of doc:
https://www-304.ibm.com/ibmlink/ast/helpFunctions.wss?lc=en=US#ASTTRACKINGLIST

The following is taken from this help panel:

The PTF closing codes

ACL Canceled while in test
CAN Canceled by submitter
COR Available from distribution
DUP Duplicate of another PTF
PER Available on a preventive service volume
REJ Rejected


The APAR closing codes are:

- ADM A partially closed APAR; can still be added to AST list;
contains administrative information only right now;
technical information will be added later
- CAN Canceled by person who submitted APAR
- DOC Documentation error
- DUA Duplicate of a resolved APAR closed for more than ten days
- DUB Duplicate of a resolved APAR closed for ten days or less
- DUU Duplicate of an unresolved APAR
- FIN Fixed in next release
- MCH Machine or microcode error
- PER Programming error
- PRS Permanent restriction
- REQ Requirement for Development's consideration
- RET Returned for additional information
- STD Open Systems Standards deficiency
- SUG Suggestion for product enhancement
- UR1 Programming error in the reported release; the problem has been
corrected in a release not yet available for distribution
- UR2 Same as UR1 but written against an unsupported release
- UR3 Programming error in the reported release. It does not exist in
the current release available for distribution
- UR4 Same as UR3 but written against an unsupported release
- UR5 Unable to reproduce on the reported release
- USE User error

-- 
gil

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

Re: APAR closures

2022-03-01 Thread Eric D Rossman

There are a few other APAR resolution codes that I have found defined in 
various public documents but I have never seen them:

ADM: Partially closed APAR; admin info; technical info to follow
MCH: Machine / microcode error
REQ: Requirement for future development
STD: Open Systems Standards deficiency

Eric Rossman, CISSP
ICSF Cryptographic Security Development
z/OS Enabling Technologies
edros...@us.ibm.com

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

Re: ZAD and C/C++ (was:: 2.5 Heads Up)

2022-03-01 Thread Paul Gilmartin

On Tue, 1 Mar 2022 08:46:35 -0800, Charles Mills  wrote:

>..., but IBM *may* simply be following it. fopen(NULL, ...) is pretty 
> useless any way you slice it.
>


On Mac OS:
printf ("%d\n",  open( "",   0  ) );
-1
No such file or directory

printf ("%d\n",  open( NULL, 0  ) );
-1
Bad address

I think both are optimal.  OpenGroup doesn't specify the latter/

>I have no idea what (void I)"" would 
>
Typo for (void *).  Short finger?

-- 
gil

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

Re: APAR closures

2022-03-01 Thread Eric D Rossman

I was actually just about to say FIN is really Fixed IF Next when your message 
came in.

I've never seen a RET, DU*, or USE. In general, our service folks don't 
actually open an APAR until we understand the issue. If we accidentally open 
one (or change our mind), we usually CANcel the APAR with an explanation that 
the APAR was opened in error.

Now that I think about it, I have seen SUG but never actually used it myself.

Eric Rossman, CISSP
ICSF Cryptographic Security Development
z/OS Enabling Technologies
edros...@us.ibm.com

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Phil Smith III
Sent: Tuesday, March 1, 2022 12:39 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Re: APAR closures

Ah, RET sounds like what I was (mis?)remembering as IDOC:
RET - Returned to the user for more documentation

 

Note that the page is not 100% correct (and yes, I saw its disclaimer), as it 
says:

FIN - Fixed in next release

and we all know that's "Fixed IF next release" because IBM does not preannounce!

 

(Yeah, that's probably sorta dead, but I remember IBM being VERY VERY clear 
about that in the years immediately after the consent decree.)

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

Re: APAR closures

2022-03-01 Thread Phil Smith III

Ah, RET sounds like what I was (mis?)remembering as IDOC:
RET - Returned to the user for more documentation

 

Note that the page is not 100% correct (and yes, I saw its disclaimer), as
it says:

FIN - Fixed in next release

and we all know that's "Fixed IF next release" because IBM does not
preannounce!

 

(Yeah, that's probably sorta dead, but I remember IBM being VERY VERY clear
about that in the years immediately after the consent decree.)


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

Re: APAR closures

2022-03-01 Thread Bill Johnson

I’ve never seen IDOC.


Sent from Yahoo Mail for iPhone


On Tuesday, March 1, 2022, 11:56 AM, Phil Smith III  wrote:

Bill Johnson wrote:
> 
https://www.mainframes.com/Apar.html

 

Thanks, that helps. It doesn't include statuses like IDOC, however-I guess
that's not a closure, maybe? But it must be: "I had this ABEND, cannot
reproduce, have no dump". I guess that could be one of the URx values, but
I'm pretty sure I've *seen* IDOC. Did I imagine that? Or is that perhaps
obsolete, replaced by URx? I haven't been on the front lines of reporting
bugs for many years (though back in the day at UofW, we had a queue of
several hundred VM bugs that we'd report five at a time, due to an agreement
with the IBM Support Centre that we would not dump 'em all at once.)


--
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: APAR closures

2022-03-01 Thread Phil Smith III

Bill Johnson wrote:
> 
https://www.mainframes.com/Apar.html

 

Thanks, that helps. It doesn't include statuses like IDOC, however-I guess
that's not a closure, maybe? But it must be: "I had this ABEND, cannot
reproduce, have no dump". I guess that could be one of the URx values, but
I'm pretty sure I've *seen* IDOC. Did I imagine that? Or is that perhaps
obsolete, replaced by URx? I haven't been on the front lines of reporting
bugs for many years (though back in the day at UofW, we had a queue of
several hundred VM bugs that we'd report five at a time, due to an agreement
with the IBM Support Centre that we would not dump 'em all at once.)


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

Re: ZAD and C/C++ (was:: 2.5 Heads Up)

2022-03-01 Thread Charles Mills

C is a standardized language. IBM's main target market is programs ported from 
other platforms. I have no idea what the standard is, but IBM *may* simply be 
following it. fopen(NULL, ...) is pretty useless any way you slice it.

I have no idea what (void I)"" would mean and I don't *think* it is valid C. A 
quick test of auto foo = (void I)""; gives me a bunch of errors.

NULL is nothing special in C: it is just an alias for 0 (zero). That lead to a 
somewhat astonishing behavior in a particular situation involving overloaded 
functions, and the new (C++ only? Perhaps C also) language standards include 
nullptr, which is specifically an *address* of zero, and is a better usage than 
NULL if the meaning is "the address of nothing." That is, "you are expecting me 
to pass you an address and I am telling you that I have no address to give you."

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Paul Gilmartin
Sent: Tuesday, March 1, 2022 8:30 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: ZAD and C/C++ (was:: 2.5 Heads Up)

On Tue, 1 Mar 2022 13:28:01 +,  wrote:
>
>ZAD is not supported on z/OS under z/VM. ":-(
>Is there any SOD or RFE or the like for this?
>
>
Many releases ago, I saw a report the C RTL treatment of following a
NULL pointer was changing.  I tested open( NULL, ... ) with releases
before and after the change.  The earlier reported Invalid Pointer; the
later Invalid Filename.  I considered the earlier more precise and
correct.  I conjecture that IBM had fecklessly accommodated
programmers accustomed to misusing NULL instead of e.g. (void I)"".

There are probably still programs that follow null pointers. What will
become of them?

I favor strict error reporting.

-- gil

--
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: APAR closures

2022-03-01 Thread Bill Johnson

https://www.mainframes.com/Apar.html




Sent from Yahoo Mail for iPhone


On Tuesday, March 1, 2022, 11:38 AM, Phil Smith III  wrote:

Anyone got a complete list of APAR close statuses? Offhand I can think of
things like FIN, IDOC, PTF (I think). I know there are more. It works, no
point in reinventing that wheel.


--
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

APAR closures

2022-03-01 Thread Phil Smith III

Anyone got a complete list of APAR close statuses? Offhand I can think of
things like FIN, IDOC, PTF (I think). I know there are more. It works, no
point in reinventing that wheel.


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

Re: JES2, meaning of parameter value codes

2022-03-01 Thread Tom Brennan

I was thinking j might mean alpha and national, and c might mean alpha, 
national, or numeric.


On 3/1/2022 2:51 AM, Seymour J Metz wrote:

Neither the J nor the Cs have any significance; jccc is just a variable 
name , as is nn. I probably would have used the name ddname, but that's only 
six characters.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Frank Swarbrick [frank.swarbr...@outlook.com]
Sent: Tuesday, March 1, 2022 2:44 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: JES2, meaning of parameter value codes

But what is the 'j' in 'jccc'?  Why not just ''?

From: IBM Mainframe Discussion List  on behalf of Seymour J 
Metz 
Sent: Monday, February 28, 2022 6:38 PM
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: JES2, meaning of parameter value codes

What is unclear? nn is any two digit number. jccc is any character string 
that is a valid ddname. PROCnn or Jccc names a concatenation that can be 
selected as the procedure library concatenation for a job, as specified by 
JOBCLASS(v), JOBCLASS(STC), JOBCLASS(TSU) or  /*JOBPARM PROCLIB=ddname. You 
need to look at the JES2 JCL, any PROCLIB(foo) statement in the initialization 
member and any subsequent commands, e.g., $ADD PROCLIB, to see what is in each 
concatenation.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Frank Swarbrick [frank.swarbr...@outlook.com]
Sent: Monday, February 28, 2022 7:21 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: JES2, meaning of parameter value codes

https://www.ibm.com/docs/en/zos/2.5.0?topic=class-parameter-description-jobclassclassstctsu

PROCLIB=nn|j|00
Specifies the default 2-8 character procedure library name (jccc) or 
procedure library number (0-99) which is to be used for this job class. It 
allows you to specify procedure libraries for different job classes. In the 
JES2 procedure, one DD statement must be named PROC00. If you specify 
additional procedure libraries (jccc or 01-99), then you might associate 
these libraries to a job class by replacing the jccc or nn of this 
parameter with the appropriate procedure library name or number. All cataloged 
procedure libraries to be used by jobs, time-sharing users, or system tasks 
must be defined in the JES2 procedure.

z/OS 2.5


From: IBM Mainframe Discussion List  on behalf of Seymour J 
Metz 
Sent: Monday, February 28, 2022 5:09 PM
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: JES2, meaning of parameter value codes

Please post example and release level.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Frank Swarbrick [frank.swarbr...@outlook.com]
Sent: Monday, February 28, 2022 6:31 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: JES2, meaning of parameter value codes

I am looking at the JES2 Initialization and Tuning Reference.  There are examples job parameters 
with codes such as "jxxx" and "jccc".  I can't seem to find a table of 
their meanings.  Can someone point me in the right direction?
Thanks,
Frank

--
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

--
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

--
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
.



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

ZAD and C/C++ (was:: 2.5 Heads Up)

2022-03-01 Thread Paul Gilmartin

On Tue, 1 Mar 2022 13:28:01 +,  wrote:
>
>ZAD is not supported on z/OS under z/VM. ":-(
>Is there any SOD or RFE or the like for this?
>
>
Many releases ago, I saw a report the C RTL treatment of following a
NULL pointer was changing.  I tested open( NULL, ... ) with releases
before and after the change.  The earlier reported Invalid Pointer; the
later Invalid Filename.  I considered the earlier more precise and
correct.  I conjecture that IBM had fecklessly accommodated
programmers accustomed to misusing NULL instead of e.g. (void I)"".

There are probably still programs that follow null pointers. What will
become of them?

I favor strict error reporting.

-- gil

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

Re: S0C4 pic 4

2022-03-01 Thread Seymour J Metz

What was in

 The PSW
 The general registers
 The failing instruction


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Joseph Reichman [reichman...@gmail.com]
Sent: Tuesday, March 1, 2022 8:07 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: S0C4 pic 4

Just got a s0c4 pic 4

I was running under TESTAUTO did listpsw was in psw key 8

then before I did SPKA X'80' MODESET MODE=PROB did a ISVK on the offending
storage and got X'0088'

the program was linked to the storage was obtained by the invoker of the
link but everything is under the same TCB

--
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: 2.5 Heads Up

2022-03-01 Thread Seymour J Metz

I assume that PR/SM still uses SIE, so the fundamental question is whether SIE 
supports second level ZAD.But, yes, regardless an RFE for z/VM should be the 
first step.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Peter Relson [rel...@us.ibm.com]
Sent: Tuesday, March 1, 2022 8:28 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: 2.5 Heads Up


ZAD is not supported on z/OS under z/VM. ":-(
Is there any SOD or RFE or the like for this?


That would have to be an RFE for z/VM (and conceivably also for the machine 
itself).  At least at the time this was introduced and z/OS exploited it, z/VM 
did not surface the ZAD capability to a guest. I do not know if that is still 
the case.

If it is surfaced, SLIP will allow it. So you could try and see if you get an 
acceptance vs rejection message. And if you get the former, please submit a pub 
update request.

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

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

Re: 2.5 Heads Up

2022-03-01 Thread Peter Relson


ZAD is not supported on z/OS under z/VM. ":-(
Is there any SOD or RFE or the like for this?


That would have to be an RFE for z/VM (and conceivably also for the machine 
itself).  At least at the time this was introduced and z/OS exploited it, z/VM 
did not surface the ZAD capability to a guest. I do not know if that is still 
the case.

If it is surfaced, SLIP will allow it. So you could try and see if you get an 
acceptance vs rejection message. And if you get the former, please submit a pub 
update request.

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

S0C4 pic 4

2022-03-01 Thread Joseph Reichman

Just got a s0c4 pic 4

I was running under TESTAUTO did listpsw was in psw key 8

then before I did SPKA X'80' MODESET MODE=PROB did a ISVK on the offending
storage and got X'0088'

the program was linked to the storage was obtained by the invoker of the
link but everything is under the same TCB   

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

Re: Solutions Not Problems - Dilbert Comic Strip on 2022-02-25 | Dilbert by Scott Adams

2022-03-01 Thread Ann Kelley

In my experience,  a bug is an opportunity  Usually an opportunity to 
insert 3 more bugs. :(

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

Re: JES2, meaning of parameter value codes

2022-03-01 Thread Seymour J Metz

Neither the J nor the Cs have any significance; jccc is just a variable 
name , as is nn. I probably would have used the name ddname, but that's only 
six characters.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Frank Swarbrick [frank.swarbr...@outlook.com]
Sent: Tuesday, March 1, 2022 2:44 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: JES2, meaning of parameter value codes

But what is the 'j' in 'jccc'?  Why not just ''?

From: IBM Mainframe Discussion List  on behalf of 
Seymour J Metz 
Sent: Monday, February 28, 2022 6:38 PM
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: JES2, meaning of parameter value codes

What is unclear? nn is any two digit number. jccc is any character string 
that is a valid ddname. PROCnn or Jccc names a concatenation that can be 
selected as the procedure library concatenation for a job, as specified by 
JOBCLASS(v), JOBCLASS(STC), JOBCLASS(TSU) or  /*JOBPARM PROCLIB=ddname. You 
need to look at the JES2 JCL, any PROCLIB(foo) statement in the initialization 
member and any subsequent commands, e.g., $ADD PROCLIB, to see what is in each 
concatenation.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Frank Swarbrick [frank.swarbr...@outlook.com]
Sent: Monday, February 28, 2022 7:21 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: JES2, meaning of parameter value codes

https://www.ibm.com/docs/en/zos/2.5.0?topic=class-parameter-description-jobclassclassstctsu

PROCLIB=nn|j|00
Specifies the default 2-8 character procedure library name (jccc) or 
procedure library number (0-99) which is to be used for this job class. It 
allows you to specify procedure libraries for different job classes. In the 
JES2 procedure, one DD statement must be named PROC00. If you specify 
additional procedure libraries (jccc or 01-99), then you might associate 
these libraries to a job class by replacing the jccc or nn of this 
parameter with the appropriate procedure library name or number. All cataloged 
procedure libraries to be used by jobs, time-sharing users, or system tasks 
must be defined in the JES2 procedure.

z/OS 2.5


From: IBM Mainframe Discussion List  on behalf of 
Seymour J Metz 
Sent: Monday, February 28, 2022 5:09 PM
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: JES2, meaning of parameter value codes

Please post example and release level.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Frank Swarbrick [frank.swarbr...@outlook.com]
Sent: Monday, February 28, 2022 6:31 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: JES2, meaning of parameter value codes

I am looking at the JES2 Initialization and Tuning Reference.  There are 
examples job parameters with codes such as "jxxx" and "jccc".  I can't 
seem to find a table of their meanings.  Can someone point me in the right 
direction?
Thanks,
Frank

--
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

--
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

--
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

47 matches

Mail list logo