× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On 20-Mar-2014 08:45 -0700, Tarr, Kenneth wrote:
I have a CL program which has a defined field that is used to run SQL
strings through QShell. The field length is 2048. The compiler
recognizes it as a 2048 byte field, but when I try to view the same
field in RDi V9.0.1 in debug, it shows it as a 1024 byte field with a
piece of information at the right missing because it extends beyond
the 1024th byte. This is also causing my QShell command to fail
because it doesn't see the delimiter at the end. I'm using an INSERT
INTO in the SQL, and have other examples where this INSERT command
does work. But I find it odd about the field limitation. (Running
this without using RDi debug doesn't work either, which makes me
think it's an issue outside of RDi...but since it only shows a field
length of 1024 in RDi in debug, that might be a clue...)

Any guidance on this?

Little reason to remain beholden to only one means of debugging when a difficulty is encountered [with the preferred or chosen method]. Some other options to investigate the value of the CL variable include:

• Dump CL Program (DMPCLPGM); DSPSPLF QPPGMDMP SPLNBR(*LAST)
• Use a 5250 debug feature; STRDBG, ADDTRC, DSPPGMVAR, etc.
• Logging; e.g. SNDPGMMSG, SNDJRNE, etc.


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.