RD: Embedded SQL issue

IBM got back to me on this so here's the issue so it can be found in the
archives.

The factors that come into play are:
a) we compile on one server and deploy and run to another
b) the view SDW_V/VIP_SOURCE does not have short names assigned to the
columns and the system-created names are different on each server
c) we were using static SQL in our RPGLE program
d) we are referencing the long column names in our statements

When using static SQL the long name/short name info is bound in at compile
time. Running the statement manually or switching to dynamic SQL fixes it
because the columns are resolved at run time.

IBM is looking into a permanent fix that doesn't require code to be changed
but for now, we are all set.

I've got a weird SQL problem. A static SQL statement in an RPG program

returns

an SQLSTATE of 02000 but when run from STRSQL (or run SQL statements) I

get a result.