× 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 16-Apr-2015 11:38 -0500, Needles,Stephen J wrote:
Never have I seen this before. Type 18 isn't defined in the message.

This is happening on a new piece of production code.

I would be sure to try a fresh test, an invocation after a new signon, to be sure no issues with the compile\debug\actgrp activity in the same job might play any role in the origin for the error.


Here is a code snippet from the debugging session:


d SQLString s 500 inz('')
<<SNIP>>

It failed at the "prepare LogInsert from :SQLString"

SQLString = 'insert into remote_machine.local_db.local_table
values(?,?,?,?,?,?,?,?,?,?,?,?,?,?)'

<<SNIP>>


Is the actual LOG(4 0 *SECLVL) spooled joblog available, including from the request message that reveals the the program with the PREPARE of the dynamic SQL being invoked, up until the msgSQL0901 LT18 [RC18] with the [apparently uninitialized, with apparent string value " STU", and thus bogus\] unreasonable reason code value? Often times there will be an accompanying\previously-listed message, and even if not, the /context/ of a -904 condition might be more revealing than having no context from a spooled joblog; something might be inferred from the procedure+module+program names that issue the message or the program to which the message, though for the PREPARE all but the sending procedure might reveal nothing more than QSQPREP to confirm the failing statement.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.