RE: FW: QtmhCvtDb trouble

Changing from named ag to *new ag solved my problem.  I
don't know what length is the magic number.

I didn't use the cgiparse api because this is for a V4R4
box and I wasn't sure if there were issues with it at
that release, and didn't want to find out the hard way.

Phil
> At what point in size does this "feature" raise it's ugly head -
> I have all my programs using CvtDb, but my file is only 2,036
> bytes long, though I have 749 fields in the file.
>
> So far I have not had any issues, and realistically do not see
> adding more size to it in the near future.
> I just don't want to get caught off guard in the future
> when I have forgotten this post.
>
> Though due to the dynamics of our web CGI work here, I do
> not do the *INLR on, but I do compile all to be activation
> group *NEW, and thus far no performance issues and it took
> care of a couple of very "weird" issues I was having.
>
> TIA
>
> Mark
>
> -----Original Message-----
> From: web400-admin@midrange.com [mailto:web400-admin@midrange.com]On
> Behalf Of Bob Cozzi
> Sent: Friday, June 21, 2002 12:22 PM
> To: web400@midrange.com
> Subject: RE: [WEB400] FW: QtmhCvtDb trouble
>
>
> I've heard of this bug. The best thing to do if you want to continue to
> use CvtDb is to make sure you set on *INLR before the CGI program ends.
>
> The best thing you can do if you want it to work in the future, is to us
> QzhbCgiParse and get he fields one at a time.
> Mel Beckman's zhbGetVar (in CGIDEV2) wraps QzhbCgiParse so that normal
> humans can actually use it. It's the only thing I use nowadays. I used
> the be in love with CvtDb, but there's too many issues with it to make
> it worth the effort anymore.
>
> Bob Cozzi
>
>
> > -----Original Message-----
> > From: web400-admin@midrange.com
> > [mailto:web400-admin@midrange.com] On Behalf Of Phil
> > Sent: Thursday, June 20, 2002 7:52 PM
> > To: WEB400
> > Subject: [WEB400] FW: QtmhCvtDb trouble
> >
> >
> > All,
> >
> > I am having trouble with this API.  The value of stdin when
> > this api is called is correct - reflects what the user
> > entererd in.  But when the api is called, it returns data
> > from the first time the api was called.  This seems only to
> > be happening where the pf used for the external ds is long,
> > and only on the right most fields.  The left most fields
> > contain the correct data.
> >
> > This as400 is v4r4.  The file is 5,163 bytes long and has 25 fields.
> >
> > Is this a known issue?
> >
> > Thanks,
> >
> > Phil
> >
> >
> > _______________________________________________
> > This is the Web Enabling the AS400 / iSeries (WEB400) mailing
> > list To post a message email: WEB400@midrange.com To
> > subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/cgi-bin/listinfo/web400
> > or email: WEB400-request@midrange.com
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/web400.
> >
> >
>
> _______________________________________________
> This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
> To post a message email: WEB400@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/web400
> or email: WEB400-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/web400.
>
>
> _______________________________________________
> This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
> To post a message email: WEB400@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/web400
> or email: WEB400-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/web400.
>