Re: Reason not to go to V6R1 -- MIDRANGE-L

Subject: Re: Reason not to go to V6R1
From: Bruce Vining <bvining@xxxxxxxxxxxxxxx>
Date: Tue, 8 Jan 2008 09:19:56 -0800 (PST)
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Conversions happen all the time when upgrading from one release to another. I don't believe the spool conversion has anything to do with retranslation, other than both are taking place in the same release.

Bruce

dr2@xxxxxxxx wrote:

Al,

this is basically a Fast/400 buster wrapped up with a bunch of other
stuff... funny damn thing is that anyone still using Fast/400 most likely
isnt' going to be leaving that platform for a while...

I still can't get anyone to explain why SPOOL is undergoing conversion in
the same step/process as the MI level is undergoing conversion...

Don in DC

When we did CISC-to-RISC, IBM was in our publically faces about the
requirements for two years before. (I knew sometime before.) With V6R1,
they screwed up and kept it a state secret. Shame on IBM, cause this is
what happens.

Al

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.