to the poor user may overshadow
the technical issues.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
Phil Smith
Sent: Monday, March 19, 2012 4:13 PM
To: IBM-MAIN@bama.ua.edu
Subject: Theology question
In our configuration data set, you
Phil Smith p...@voltage.com wrote in message
news:b870629719727b4ba82a6c06a31c291232410ad...@hqmailsvr01.voltage.com
...
In our configuration data set, you can specify a default, global value
for something. Specific entries in the configuration can override that
global value. However, there are
Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] För Phil Smith
Skickat: den 19 mars 2012 22:13
Till: IBM-MAIN@bama.ua.edu
Ämne: Theology question
In our configuration data set, you can specify a default, global value for
something. Specific entries in the configuration can override
I'd say it is a very bad idea to use an asterisk to represent don't use any
value. The fact your debating it shows it will probably lead to confusion.
The previous suggestion of NULL sounds like a good idea to me, or maybe OFF or
DISABLE.
* to me means any value, not no value.
Regards
paulgboul...@aim.com
To: IBM-MAIN@bama.ua.edu
Date: 03/19/2012 06:58 PM
Subject:Re: Theology question
Sent by:IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu
On Mon, 19 Mar 2012 17:43:45 -0400, Gord Tomlin wrote:
IMHO using '*' to represent null violates the Principle of Least
On Tue, 20 Mar 2012 10:54:50 +0100, Thomas Berg wrote:
The only alternative (as seen from the principle of least astonishment) I can
think of is using the explicit option NULL - assuming that value is never a
real option.
In some contexts, such an option is unjustified. Designs should
I should have noted that NULL, NONE, et al. are valid, so we can't really use
any of them. Something like *NONE would work, but is also pretty ugly.
--
...phsiii
Phil Smith III
p...@voltage.commailto:p...@voltage.com
Voltage Security, Inc.
www.voltage.comhttp://www.voltage.com
(703) 476-4511
Of
Steve Conway
Sent: Tuesday, March 20, 2012 7:50 AM
To: MVS List Server 1
Subject: Re: Theology question
I find myself in the delightfully strange position of unambiguously
agreeing with Paul Gilmartin.
Must be spring fever or something... :-)
Cheers,,,Steve
Steven F. Conway, CISSP
LA Systems
z
-Ursprungligt meddelande-
Från: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] För Paul
Gilmartin
Skickat: den 20 mars 2012 15:45
Till: IBM-MAIN@bama.ua.edu
Ämne: Re: SV: Theology question
On Tue, 20 Mar 2012 10:54:50 +0100, Thomas Berg wrote:
The only alternative (as seen
Ämne: Re: Theology question
I should have noted that NULL, NONE, et al. are valid, so we can't really use
any of them. Something like *NONE would work, but is also pretty ugly.
--
...phsiii
Phil Smith III
p...@voltage.commailto:p...@voltage.com
Voltage Security, Inc.
www.voltage.comhttp
Thanks to all who responded. I'm convinced. quote quote it is!
--
...phsiii
Phil Smith III
p...@voltage.commailto:p...@voltage.com
Voltage Security, Inc.
www.voltage.comhttp://www.voltage.com
--
For IBM-MAIN subscribe / signoff
That that is is that that is not is not...
In a message dated 3/20/2012 3:35:49 P.M. Central Daylight Time,
p...@voltage.com writes:
quote quote it is!
--
For IBM-MAIN subscribe / signoff / archive access instructions,
On 20 March 2012 11:33, Phil Smith p...@voltage.com wrote:
I should have noted that NULL, NONE, et al. are valid, so we can't really use
any of them. Something like *NONE would work, but is also pretty ugly.
Not least because it looks like something from an AS/400, uh, I mean IBM i.
Tony H.
In our configuration data set, you can specify a default, global value for
something. Specific entries in the configuration can override that global
value. However, there are cases where you *must* specify a null value on a
specific entry, as if you had no default, global value.
Our internal
I feel the asterisk should mean use the global default and the '' should mean
don't use
any value.
/Tom Kern
On 3/19/2012 17:12, Phil Smith wrote:
In our configuration data set, you can specify a default, global value for
something. Specific entries in the configuration can override that
IMHO using '*' to represent null violates the Principle of Least
Astonishment. '*' is often used in masking to represent anything,
which is a long way from null.
How about using NULL to represent null, e.g.,
thing3(option1,NULL) /* This would define another thing and say even
if you have a
Seems retro to me like when I wrote my first CLIST back in 1976. Sort of
depends on the called program and how it's gonna parse the entries-DEBUG(Y).
In a message dated 3/19/2012 4:16:20 P.M. Central Daylight Time,
p...@voltage.com writes:
Based on the collective wisdom of the
Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On
Behalf Of Thomas Kern
Sent: Monday, March 19, 2012 2:41 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Theology question
I feel the asterisk should mean use the global default and the '' should
mean don't use
any value.
/Tom Kern
On 3/19
On Mon, 19 Mar 2012 17:43:45 -0400, Gord Tomlin wrote:
IMHO using '*' to represent null violates the Principle of Least
Astonishment. '*' is often used in masking to represent anything,
which is a long way from null.
How about using NULL to represent null, e.g.,
thing3(option1,NULL) /* This
19 matches
Mail list logo
