Empty outline

There shouldn't be a semi-colon at the end of the second line - the SQL statement continues for another 60 lines (three CTE's and then a select statement joining the results of the CTE's). I didn't include the rest of the SQL because it was so long and I assumed that the triangle would be displayed at or after the problem line(s), if there were any. I submitted a Service Request and Mike Hockings replied and confirmed that the issue is a defect in the release that I am using. The problem was fixed in later releases.
------------------------------

message: 3
date: Thu, 24 Jan 2019 19:08:27 -0500
from: "Edmund Reinhardt" <edmund.reinhardt@xxxxxxxxxx>
subject: Re: [WDSCI-L] Empty outline

Hi Terry

You are missing the ; at the end of the second EXEC SQL

Without that, the parser considers the rest of the file SQL instead of RPG.

HTH,
Edmund



From: Terry Hertel <T.Hertel@xxxxxxxxxxxxxxxxx>
To: "wdsci-l@xxxxxxxxxxxxxxxxxx" <wdsci-l@xxxxxxxxxxxxxxxxxx>
Date: 01/24/2019 03:15 PM
Subject: [WDSCI-L] Empty outline
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx>



I'm running RDi version 9.5.1.1 (on V7.1). Yes, I know I'm behind but there are several reasons why I haven't upgraded: 1) it has been a very stable and reliable version for the type of programming that we were doing, and 2) most development is on hold as we convert to a different ERP system. That being said, I have written an SQLRPGLE program to extract data from one file. There are three routines in the program that all use SQL statements to create a table in QTEMP, change the column labels, and then inserts data into the table. The program compiles without errors and runs without errors. I opened it today to add another option to the program and noticed that the outline is blank. There is a yellow triangle with an exclamation point to the left of the line number, but I am unsure what it doesn't like since it compiles with a 00 highest severity. The SQL pre-compile list contains the following errors:

SQL5066 0 136 Precompile option NAMING changed by SET OPTION
statement.
SQL5066 0 136 Precompile option COMMIT changed by SET OPTION
statement.
SQL5066 0 136 Precompile option DATFMT changed by SET OPTION
statement.
SQL5066 0 136 Precompile option CLOSQLCSR changed by SET OPTION
statement.
SQL5066 0 136 Precompile option NAMING changed by SET OPTION
statement.
SQL5066 0 136 Precompile option COMMIT changed by SET OPTION
statement.
SQL5066 0 136 Precompile option DATFMT changed by SET OPTION
statement.
SQL5066 0 136 Precompile option CLOSQLCSR changed by SET OPTION
statement.
SQL1103 10 181 Position 30 Column definitions for table SOQTESUMF in
QTEMP not found.
SQL0088 0 193 Position 14 DELETE applies to entire table.
SQL1103 10 193 Position 26 Column definitions for table SOQTESUMF in
QTEMP not found.
SQL1103 10 197 Position 26 Column definitions for table SOQTESUMF in
QTEMP not found.
SQL1103 10 300 Position 30 Column definitions for table SOQTECUSF in
QTEMP not found.
SQL0088 0 313 Position 14 DELETE applies to entire table.
SQL1103 10 313 Position 26 Column definitions for table SOQTECUSF in
QTEMP not found.
SQL1103 10 317 Position 26 Column definitions for table SOQTECUSF in
QTEMP not found.
SQL1103 10 422 Position 30 Column definitions for table SOQTESGLF in
QTEMP not found.
SQL0088 0 436 Position 14 DELETE applies to entire table.
SQL1103 10 436 Position 26 Column definitions for table SOQTESGLF in
QTEMP not found.
SQL1103 10 441 Position 26 Column definitions for table SOQTESGLF in
QTEMP not found.

The lines of code in the area where the triangle appears are (the triangle is on the second Exec Sql statement):
// Delete records from table in case it already existed
Exec Sql
Delete from qtemp/soqtecusf;

// Populate the file
Exec Sql
insert into qtemp/soqtecusf

Not sure where to go from here.