RE: Question on Validity Checking

[Al Barsa <barsa@xxxxxxxxxxxxxxxxxxx>]

We refresh TAA Tools about every 8 to 12 weeks.  The first RTVCMDSRC came
out on 6/01/02.  It used the IBM supplied APIs, and did a less than perfect
job.
A refreshed version came out on 7/15/03.  If you have a license, you can
get a refreshed version (e.g.: same OS/400 release and license tier) for
$30.

Just for historical clarification purposes, we raised the issue with IBM
that there first set of API's were less than perfect (hey, there had to be
a first time for that!), and so they improved them.  (This is something
that they do when someone brings up a legitimate requirement.  Sometimes
the API's get improved at a release boundary, or else via PTF.)  Although
the API's were improved using the PTF method, it is not clear to me if they
improved the documentation mid release, or will wait until the next release
to do such.  I suspect that they will wait for the next release.  As usual,
I have no idea and don';t even want to guess what that release will be
called:-))))))

Al

Al Barsa, Jr.
Barsa Consulting Group, LLC

400>390

914-251-1234
914-251-9406 fax

http://www.barsaconsulting.com
http://www.taatool.com


midrange-l-bounces@xxxxxxxxxxxx wrote on 07/23/2003 08:54:51 PM:

> I think there's a rtvcmdsrc utility in TAATools. How about it Al?
>
> At 16:30 07/23/2003, you wrote:
> >I've never understood why IBM won't publish the complete parameter
> >definition list for every command, just like they do the Escape
messages.
> >You should be able to hit F1 and see both.... Why is it such a secret?
Users
> >have been given the ability to write validity checking programs but IBM
> >makes it really hard to do so! I just don't get it...
> >
> >Al ... You should get on their case about this!  <smile>
> >
> >Kenneth
> >--
> >********************************
> >Kenneth  E.  Graap
> >IBM Certified Specialist
> >AS/400 Professional
> >System Administrator
> >NW Natural - Information Services
> >System Services
> >Phone 503 226 4211 X5537
> >FAX   603 849 0591
> >keg@xxxxxxxxxxxxx
> >********************************
> >
> >
> >-----Original Message-----
> >From: Buck [mailto:buck.calabro@xxxxxxxxxxxx]
> >Sent: Wednesday, July 23, 2003 2:22 PM
> >To: midrange-l@xxxxxxxxxxxx
> >Subject: Re: Question on Validity Checking
> >
> >
> > > am trying to write one for the WRKUSRJOB
> > > command and keep getting errors that the
> > > parameters do not match those in  my
> > > program.
> >
> >There is a program called RTVCMDSRC floating round somewhere; try
Google?
> >Failing that, write a CL program, declare a hundred parameters and
inspect
> >each one via DMPCLPGM.  By putting unique data into each element on the
> >command, you should be able to tell something about the results.  Of
course,
> >you'll go through it all over again at V5R3?...
> >
> >Better is to write your own command, put it in a library above QSYS and
do
> >your processing there.  When done, call the genuine command.
> >
> >You can also look into the command exit points, but I haven't had a
reason
> >to dabble there yet.
> >   --buck
> >
> >
> >
> >_______________________________________________
> >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.
>
> Pete Hall
> pbhall@xxxxxxxxxxxxx
> http://www.pbhall.us/
>
> _______________________________________________
> 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.
>