RE: Statement of readiness for V6R1

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

Thanks, Lukas.  Looks like all my stuff is ready to go.  :)

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 Lukas Beeler
> Sent: Monday, September 24, 2007 3:54 PM
> To: Midrange Systems Technical Discussion
> Subject: RE: Statement of readiness for V6R1
>
>
> The answer is here:
>
> www.redbooks.ibm.com/redpieces/pdfs/redp4293.pdf
>
> Another method for individual programs is to use the Display
> Program (DSPPGM) or Display Service Program (DSPSRVPGM) CL command to
> determine
> whether sufficient creation data exists. For ILE (service) programs, any
> value except *NO for
> 'All creation data' indicates enough creation data is available. For
> Original Program Model
> (OPM) programs, any value except *NONE for 'Observable information'
> indicates enough
> creation data is available.
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Bradley V. Stone
> Sent: Monday, September 24, 2007 10:48 PM
> To: Midrange Systems Technical Discussion
> Subject: RE: Statement of readiness for V6R1
>
> Is there any way looking at program objects (RPGLE, CL, CLLE, etc) to
> know
> if they are "ready" even if compiled on V4R5?  Sorry if this has been
> discussed before, I did a search and couldn't find much.  (Search engine
> just isn't as good as google's.  )
>
> 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: Monday, September 24, 2007 3:42 PM
> > To: Midrange Systems Technical Discussion
> > Subject: RE: Statement of readiness for V6R1
> >
> >
> > I appreciate your commitment to customer service by considering their
> > restore/conversion times.
> >
> > I think there are alternative ways of discovering this.   Basically by
> a
> > DSPOBJD to an output file and a little UDF that calls the program APIs
> to
> > determine if the program is acceptable.  Hmm, might have even
> > been used in
> > determining if ANZOBJCVN had "anomalies" that had to be worked out...
> >
> > And I think ANZOBJCVN will be getting some other ptfs very shortly.
> I,
> > for one, don't like the fact that the first page has all sorts of
> > summaries on time estimates, etc but not one line about how many
> programs
> > won't convert.  Currently you have to delve into the detail, or run a
> > suggested SQL statement.
> >
> > Rob Berendt
> > --
> > Group Dekko Services, LLC
> > Dept 01.073
> > PO Box 2000
> > Dock 108
> > 6928N 400E
> > Kendallville, IN 46755
> > http://www.dekko.com
> >
> >
> >
> >
> >
> > "Lukas Beeler" <l.beeler@xxxxxxxxxxx>
> > Sent by: midrange-l-bounces@xxxxxxxxxxxx
> > 09/24/2007 04:32 PM
> > Please respond to
> > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> >
> >
> > To
> > "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
> > cc
> >
> > Fax to
> >
> > Subject
> > RE: Statement of readiness for V6R1
> >
> >
> >
> >
> >
> >
> > Hi Rob,
> >
> > We intend to do this as soon as we can. ANZOBJCVN is not available for
> > us yet (we run Lang #2939), but we've been compiling for target
> release
> > V5R2 (current version) or V5R3 (next version).
> >
> > Something we will have to keep thinking about is releasing our
> software
> > - since we target primarily small business customers, we can't count
> on
> > 16 cpus being available to do conversions. This might mean that we
> need
> > to buy a machine running V6R1 just to create media which don't take
> > hours to restore.
> >
> > I don't think this is a bad move by IBM, but it doesn't make things
> > easier.
> >
> > (In case you or anyone else is wondering: the software I'm talking
> about
> > is http://www.dias-is.com/)
> >
> >
> > -----Original Message-----
> > From: midrange-l-bounces@xxxxxxxxxxxx
> > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
> > Sent: Monday, September 24, 2007 10:25 PM
> > To: midrange-l@xxxxxxxxxxxx
> > Subject: Statement of readiness for V6R1
> >
> > Any vendors issuing "Statements of readiness for V6R1" yet?  Granted,
> I
> > would be happy with a caveat that basically says something to the
> effect
> > of "... this statement should only be construed to mean that all of
> our
> > currently supported versions, with the appropriate service packs (and
> > these are...), have been determined to comply with ANZOBJCVN as per
> > http://www.redbooks.ibm.com/abstracts/redp4293.html  .  This statement
> > should not be construed to mean that there may not be other issues
> with
> > V6R1 that may need IBM's attention on ptf's, or some tweaking on our
> > part
> > to comply with new features or requirements."
> >
> >
> > Rob Berendt
> > --
> > Group Dekko Services, LLC
> > Dept 01.073
> > PO Box 2000
> > Dock 108
> > 6928N 400E
> > Kendallville, IN 46755
> > http://www.dekko.com
> >
> > --
> > 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.