It doesn't change (which is the problem...)  The QtmhCvtDB should read the
Environment variables and populate the corresponding DS fields which are
defined in an External DS.  It is changing all but the last one.  All
definitions are correct and all names match.  I recompiled the DS and the
program and recreated the program and the Activation Group before I sent the
original mail to the list, so I don't know what else it could be...

Thanks,

Joel R. Cochran
Director of Internet Services
VamaNet.com
(800)480-8810
mailto:webmaster@vamanet.com


> -----Original Message-----
> From: Buck Calabro [mailto:Buck.Calabro@commsoft.net]
> Sent: Monday, August 05, 2002 1:52 PM
> To: web400@midrange.com
> Subject: RE: [WEB400] Strange QtmhCvtDB problem
>
>
> >If the first time it is called it works
> >correctly, then I've had this problem when
> >using named AG's.
>
> This sounds like corrupted memory.  Check to see that all parms match
> between caller and callee - not just the 'failing' one, but ALL of the
> call/callp situations.  Also look for manipulating varying
> length strings
> past the end of their declared length, like move *blanks to a
> varying length
> field in a subprocedure.
>
> Put a watch on the variable and see when it gets changed.
>   --buck
> _______________________________________________
> 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.
>


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.