I think you can use the substring command (it's probably called
something slightly different in the debugger) to see different parts of
a string. Another alternative is to write the SQL statement to the web
page you're trying to create.

Matt 

-----Original Message-----
From: web400-bounces+matt.haas=thomson.com@xxxxxxxxxxxx
[mailto:web400-bounces+matt.haas=thomson.com@xxxxxxxxxxxx] On Behalf Of
Mike
Sent: Friday, September 15, 2006 12:18 PM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Using WDSC 6 to debug CGI programs...

Right click on the object and debug | set service entry point.

Otherwise, if you look in the STRDBG help, there is a way to see longer
fields. I just don't remember it off the top of my head.

On 9/15/06, Shane_Cessna@xxxxxxx <Shane_Cessna@xxxxxxx> wrote:

Has anyone used WDSC 6 to debug a CGI program?  I have tried and tried
and
tried to do it but WDSC has NO helpful documentation on this in the
help
section...

Can someone point me in the right direction as to how to do this?

The reason I'm asking is because the native 400 debugger limits
character
fields to 1024 characters and I have a sql statement that is much
longer
than that...I need to see what the value of the entire statement is so
I
can see what's wrong with it in debug mode...

Does WDSC not have this same limitation to character fields or am I
wasting my time?

Shane Cessna
--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
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.