On Dec 6, 2007, at 1:46 PM, Bob Shannon wrote:
I grant you that untrammeled access to source code _can_ result in
disasters.
Any example ?
Sure. The thousands of in-stream usermods that were written prior
to XA, and which greatly inhibited subsequent upgrades. I certainly
agree that in th
Radoslaw Skorupka said:
> Open code does *NOT* mean "open for update". Of course if you want,
you can modify it, but then it is *your* code, and you are expected to
support it. Ergo, the rules, what is allowed for customer to modify, and
what is locked could remain the same as in OCO.
The issue
Veilleux, Jon L wrote:
Bob Shannon wrote:
Some, such as logical swap, were incorporated into MVS. Others, such as
the dual master catalog mod at a large US insurance company, proved to
be a nightmare to maintain and an even worse nightmare to remove.
AMEN Bob. Although usermods did have their
ttp://www.garlic.com/~lynn/2007u.html#6 Open z/Architecture or Not
as before the vmshare archives are at
http://vm.marist.edu/~vmshare/
old vmshare post about the original source maint infrastructure,
originally developed on cp67
http://vm.marist.edu/~vmshare/read?fn=HISTORY&ft=MEMO&lin
The following message is a courtesy copy of an article
that has been posted to bit.listserv.ibm-main,alt.folklore.computers as well.
[EMAIL PROTECTED] (Bob Shannon) writes:
> Sure. The thousands of in-stream usermods that were written prior to
> XA, and which greatly inhibited subsequent upgrades
In a message dated 12/6/2007 1:23:55 P.M. Central Standard Time,
[EMAIL PROTECTED] writes:
OK, I'am aware of one: Wide open code could mean more holes/errors
disclosed. It also could mean more errors FIXED. Not to mention more
suggestions to enhance it. What's better ?
>>
Back when th
Bob Shannon wrote:
>Some, such as logical swap, were incorporated into MVS. Others, such as
the dual master catalog mod at a large US insurance company, proved to
be a nightmare to maintain and an even worse nightmare to remove.
AMEN Bob. Although usermods did have their up side, especially the
ca
On 6 Dec 2007 11:23:52 -0800, [EMAIL PROTECTED] (R.S.)
wrote:
>> I grant you that untrammeled access to source code _can_ result in disasters.
>
>Any example ?
>
>OK, I'am aware of one: Wide open code could mean more holes/errors
>disclosed. It also could mean more errors FIXED. Not to mention mo
>>> On Thu, Dec 6, 2007 at 2:53 PM, in message
<[EMAIL PROTECTED]>, "McKown,
John" <[EMAIL PROTECTED]> wrote:
-snip-
> But isn't that a managerial failure, rather than a technical failure?
I don't see that as a failure of either group involved. At the time, many of
those mods were necessary, a
> -Original Message-
> From: IBM Mainframe Discussion List
> [mailto:[EMAIL PROTECTED] On Behalf Of Bob Shannon
> Sent: Thursday, December 06, 2007 1:46 PM
> To: IBM-MAIN@BAMA.UA.EDU
> Subject: Re: [spam] Open z/Architecture or Not
>
>
> >> I grant you
>> I grant you that untrammeled access to source code _can_ result in
>> disasters.
>Any example ?
Sure. The thousands of in-stream usermods that were written prior to XA, and
which greatly inhibited subsequent upgrades. I certainly agree that in the
early days usermods were written to overcome
On Thu, 6 Dec 2007 20:23:21 +0100, R.S. wrote:
>Phil Payne wrote:
>>
>>I grant you that untrammeled access to source code _can_ result
>>in disasters.
>
>Any example ?
I think the key words in Phil's post are "untrammeled" and "can". He went on
to describe the benefits.
--
Tom Marchant
Phil Payne wrote:
Belated birthday greetings.
Hmm.
I grant you that untrammeled access to source code _can_ result in disasters.
Any example ?
OK, I'am aware of one: Wide open code could mean more holes/errors
disclosed. It also could mean more errors FIXED. Not to mention more
suggestions
Belated birthday greetings.
Hmm.
I grant you that untrammeled access to source code _can_ result in disasters.
But - IMO - user access to source code made ASP/JES3 (thanks, e.g., to
Rolls-Royce and Rank
Xerox) and many other products into what they are today. Would JES2/MAS have
been availabl
Hi,
I have followed the "T3 Sues IBM To Break its Mainframe Monopoly" and seen
how it has changed from commentary on that issue to a dissertation on the
merits or otherwise of having ready access to z/OS and possible it's source
as in the pre-MVS days.
For its worth my observation is that the iss
15 matches
Mail list logo
