×
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.
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?
-- Ken
This e-mail and attachment(s) may contain information that is privileged, confidential, and/or exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copy of this message is strictly prohibited. If received in error, please notify the sender immediately and delete/destroy the message and any copies thereof. Although Associated Banc-Corp and/or its affiliates (collectively "Associated") attempt to prevent the passage of viruses via e-mail and attachments thereto, Associated does not guarantee that either are virus-free, and accepts no liability for any damage sustained as a result of any such viruses. Any federal tax advice contained in this communication (including any attachments) is not intended or written to be used or referred to in the promoting, marketing, or recommending of any entity, investment plan or agreement, nor is such advice intended or written to be used, and cannot be used, by a taxpayer for the purpose of avoiding penalties under the Internal Revenue Tax Code
As an Amazon Associate we earn from qualifying purchases.
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.