RE: Statement of readiness for V6R1

[Al Barsa <barsa@xxxxxxxxxxxxxxxxxxx>]

So far, the products that are not V6R1 ready are:

DBU                     They have been informed.
Target/400              Ditto
MIMIX                   A fix has been promised in the next service pack
which is scheduled for next week, but might be advanced to this.
TAA Tool - V5R3 only          A fix is available at the website.  V5R4 is
fine.  Previous releases are unsupported and won't work.

Note:                   The analysis PTFs only run on V5R3 and V5R4, and at
current course and speed do not run on V6R1.  My diagnosis is that it's
suicidal to attempt to do antics, and go from a previous release.

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.as400connection.com



                                                                       
             rob@xxxxxxxxx                                           
             Sent by:                                                  
             midrange-l-bounce                                          To
             s@xxxxxxxxxxxx            Midrange Systems Technical    
                                       Discussion                      
                                       <midrange-l@xxxxxxxxxxxx>     
             09/26/2007 08:22                                           cc
             AM                                                        
                                                                   Subject
                                       RE: Statement of readiness for V6R1
             Please respond to                                         
             Midrange Systems                                          
                 Technical                                             
                Discussion                                             
             <midrange-l@midra                                         
                 nge.com>                                            
                                                                       
                                                                       




That was basically the function of my UDF.  You'd SQL over the output from
DSPOBJD.  And the UDF would determine if the program, or service program,
had observability or was compiled at V5R1 or above.  The UDF used the
retrieve program information and the retrieve service program information
APIs.

> CREATE TABLE ROB/pgmlist AS (
  WITH T1 AS (
    SELECT ODLBNM, ODOBNM, ODOBTP, ODOBAT,
         RTVOBSINFUDF(ODLBNM, ODOBNM, ODOBTP, ODOBAT) AS OBSERVABILTY
    FROM ROUTINES/DSKDTL
    WHERE ODOBTP IN('*PGM', '*SRVPGM')
    ORDER BY ODLBNM, 5, ODOBNM)
  SELECT *
  FROM T1
  ORDER BY ODLBNM, OBSERVABILTY, ODOBNM)
  WITH DATA


> create function ROB/RTVOBSINFUDF (CHAR (10), CHAR (10), CHAR (8),
                                   CHAR (10))
    returns CHAR (1)
    language rpgle
    deterministic
    no sql
    returns null on null input
    no external action allow parallel
    simple call
    external name 'ROB/RTVOBSINF(RTVOBSINFUDF)'
  Function RTVOBSINFUDF was created in ROB.

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
09/24/2007 04:48 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






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.