RE: Reason not to go to V6R1

["Bradley V. Stone" <bvstone@xxxxxxxxxxxx>]

Any version should work.  :)  But that is a good point.  Then again, I do
only "support" the latest version.  And I try to make upgrading my software
as painless and seamless as possible.

Now the hardest part is getting customers to go to the FAQ page.  :)  Maybe
I'll stick something on every page with this particular question linking to
the FAQ.

 I'm sure in months to come this will easily be a FAQ... so I guess you
could call this a "pre-emptive FAQ".. lol!

Bradley V. Stone
BVSTools - www.bvstools.com
eRPG SDK - www.erpgsdk.com

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of rob@xxxxxxxxx
> Sent: Thursday, January 10, 2008 10:23 AM
> To: Midrange Systems Technical Discussion
> Subject: RE: Reason not to go to V6R1
>
>
> Good man!  More vendors should do that.  The only improvement might be
> what service level of your software you need to be at.
>
> Rob Berendt
> --
> Group Dekko Services, LLC
> Dept 01.073
> PO Box 2000
> Dock 108
> 6928N 400E
> Kendallville, IN 46755
> http://www.dekko.com
>
>
>
>
>
> "Bradley V. Stone" <bvstone@xxxxxxxxxxxx>
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 01/09/2008 08:48 PM
> Please respond to
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
>
>
> To
> "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
> cc
>
> Subject
> RE: Reason not to go to V6R1
>
>
>
>
>
>
> http://www.bvstools.com/faq.html#v6r1
>
> :)
>
>
> Bradley V. Stone
> BVSTools - www.bvstools.com
> eRPG SDK - www.erpgsdk.com
>
> > -----Original Message-----
> > From: midrange-l-bounces@xxxxxxxxxxxx
> > [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of rob@xxxxxxxxx
> > Sent: Tuesday, January 08, 2008 3:05 PM
> > To: Midrange Systems Technical Discussion
> > Subject: Re: Reason not to go to V6R1
> >
> >
> > I used some information from the mentioned redbook to find out
> > what can be
> > done about recalcitrant vendors.  Just today I too heard the line about
> > renewed efforts to get to the vendors, starting right before the
> holidays.
> > If you are a software vendor, lurking on this thread, check out Q10 and
> > Q11 at
> > http://www-03.ibm.com/systems/i/os/i5os/v6r1preview/conversion.html
> >
> > I think that's where I started to find out what to do about recalcitrant
> > vendors.
> >
> >
> > Rob Berendt
> > --
> > Group Dekko Services, LLC
> > Dept 01.073
> > PO Box 2000
> > Dock 108
> > 6928N 400E
> > Kendallville, IN 46755
> > http://www.dekko.com
> >
> >
> >
> >
> >
> > Al Barsa <barsa@xxxxxxxxxxxxxxxxxxx>
> > Sent by: midrange-l-bounces@xxxxxxxxxxxx
> > 01/08/2008 11:27 AM
> > Please respond to
> > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> >
> >
> > To
> > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> > cc
> >
> > Subject
> > Re: Reason not to go to V6R1
> >
> >
> >
> >
> >
> >
> >
> > Don,
> >
> > I think that the spool thing got thrown in with the rest of the stuff.
> The
> > only thing that matters (other than time, which is cheap now-a-days) is
> > the
> > "creation data" part of what used to be called "observability".  I'm
> > through that on one partition, but there are lots of vendors that have
> > issues, and given their (not-so) fast response to inquiries, I would say
> > that this release may be in trouble.
> >
> > A few facts:
> > o     The release is not yet G.A.ed.
> > o     IBM says that they have renewed the efforts to get to vendors,
> > although I can see no tangible evidence of this.
> >
> > We will see what happens as G.A. gets closer.  I don't think that IBM
> has
> > announced that date yet, but I get conflicting information from many
> > people.
> >
> > Al
> >
> > Al Barsa, Jr.
> > Barsa Consulting Group, LLC
> >
> > 400>390
> >
> > "i" comes before "p", "x" and "z"
> > e gads
> >
> > Our system's had more names than Elizabeth Taylor!
> >
> > 914-251-1234
> > 914-251-9406 fax
> >
> > http://www.barsaconsulting.com
> > http://www.taatool.com
> > http://www.systemiconnection.com/
> >
> >
> >
> >
> >              dr2@xxxxxxxx
> >              Sent by:
> >              midrange-l-bounce
> >       To
> >
> >              s@xxxxxxxxxxxx            "Midrange Systems Technical
> >                                        Discussion"
> >                                        <midrange-l@xxxxxxxxxxxx>
> >              01/08/2008 11:18
> >       cc
> >
> >              AM
> >
> >  Subject
> >
> >                                        Re: Reason not to go to V6R1
> >              Please respond to
> >              Midrange Systems
> >                  Technical
> >                 Discussion
> >              <midrange-l@midra
> >                  nge.com>
> >
> >
> >
> >
> >
> >
> >
> > 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
> > --
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> > list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> >
> > --
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> > list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> >
> >
> > --
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L)
> > mailing list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L)
> mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.