Also check to ensure that columns 1-5 of the source do not contain any
"invisible" non-blank characters. I've seen all sorts of SQL errors
caused by this happening, where simply re-typing spaces in these columns
fixes the issue.
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael Schutte
Sent: Wednesday, January 08, 2014 8:26 AM
To: Midrange Systems Technical Discussion
Subject: Re: SQL Strangeness
Is any line of your SQL going past column 80?
On Tue, Jan 7, 2014 at 11:52 PM, CRPence <CRPbottle@xxxxxxxxx> wrote:
Mark Murphy on Tuesday, January 07, 2014 2:14 PM wrote:
This should be a very simple SQL, but it is not working out that
way. Can anyone see what I am not?
RPGLE Free Form, V7.1 TR6
osnam, osad1, osad2, osadx, osad3, ossta, oszip, tscst
Error is SQL1105: Position 63 Object TSCST in *LIBL not found.
Error on line directly above from saysv100.
Strange thing is if I remove the tscst field from that line, the
error shifts to oszip, and so on until the line is gone, and then it
SQL0117: Statement contains wrong number of values.
when I run the program, I get:
Message ID: SQL0206 <<SNIP>>
Message: Column or global variable TSCST not found.
Cause: TSCST was not found as a column of table *N in *N and was
not found as a global variable in *N. If the table is *N, TSCST
is not a column of any table or view that can be referenced.
This makes no sense. If I remove columns osnam through tscst in both
the insert column list, and the select column list, all is well, and
the program runs properly. If I cut and paste into green screen SQL,
it works as expected.
Note: The original message never appeared in the newsgroup, so I
/borrowed/ a reply to respond to... but the quoted message above is
apparently [though snipped\edited] the original.
Prior releases did not have /SQL variable/ support, so I have no
access to the message text to know if the text for the -1105 error is
appropriate; its text on v5r3 seems inappropriate in that context
[except if as other suggest, some extraneous characters like () are at
the end of the line out of the visual presentation are]. The "Object
not found" may seem inappropriate at first glance, but would be valid
for an assumption by the SQL that the reference could be a variable vs
column; similar to how SQL0206 was expanded from only referring to a
The SQL1105 could be effectively the same as a -206, but for a
delayed prepare or pre-compile, whereby the error can be ignored until
run-time. I can not find the description\text of the error in the
That all of those columns get the same error, and that the -117
occurs only after all of those names are removed, and that the
-206 occurs, are all very consistently suggesting that the unqualified
table-reference in the "FROM saysv100" is missing those columns. I
suggest library-qualifying the table-reference, and then if the error
persists, DSPFFD of that specific file and review for those column
names. Perhaps that [VIEW] database file was intended to have its
column-list expanded, but it was never updated; e.g. as a VIEW,
the underlying TABLE was expanded to have those additional columns,
the VIEW was not updated by a DROP and the CREATE VIEW to include
FWiW: The "*N in *N" in the SQL0206 seems questionable, because the
file table-reference saysv100 conspicuously must have been located;
obviously the SQL knows the other columns are there. By its name, the
file is likely a VIEW, and thus apparently is a "view that can be
referenced", so why its name does not appear in the replacement text
the SQL0206 may be a defect. Not sure about the second-level and
replacement text for the SQL1105; specifying the *SECLVL option for
pre-compile per OPTION(*SECLVL) should get the full text for the
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives