Just a WAG but SELECT is an opcode & it's likely that the outline parser
is getting confused as to the usage of SELECT as a variable rather than an
opcode. Which is just one of the many reasons that I do not use reserved
words or opcode as variable names.
From: Gerald Kern <jp2558@xxxxxxxxx>
To: WDSCi <wdsci-l@xxxxxxxxxxxx>
Date: 05/30/2014 10:37 AM
Subject: [WDSCI-L] Another Outline Oddity?
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>
I have a project that consists of four RPGLE and three SQLRPGLE source
The outline is available for all but one source member which is a free
SQLRPGLE (V7R1 btw)
that is showing 'unexpected token(s) ignored' tags which I think is
disabling the outline altogether. It's occurring in two places in the code
and both are where an SQL string is being composed similar to the one
String_SQL = Select + Where +
Q_TXRSTAT + QUOTE + Active + QUOTE +
And + Q_TXACODE + QUOTE + p_TXACODE +
QUOTE + And + Q_TXCHGDT + Today;
Not a show stopper as the program verifier shows no errors and it
Just odd that the outline for this one program is not available.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2022 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
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.