RUNSQLSTM failure

HI,

I've got a software installation problem that has got me pulling out what little hair I have left.
As a step in a software installation process (which runs interactively, not in batch), a CL program executes a RUNSQLSTM, as follows..

RUNSQLSTM  SRCFILE(QSQLSRC) SRCMBR(&PROCNAME) +
           COMMIT(*NONE) ERRLVL(20) TGTRLS(&TGTRLS) +
           CLOSQLCSR(*ENDMOD) USRPRF(*OWNER) +
           DYNUSRPRF(*OWNER)

The SQL statements in the source member create a stored procedure. The RUNSQLSTM command fails, but does not produce a list of the SQL procedure statements. Instead it produces a list of the C+ code that the OS generates for the stored procedure. And the error it describes is apparently a problem with the Include statements generated in the C code.

* * * * *  E N D  O F  S O U R C E  * * * * *
5770SS1 V7R1M0 100423               Run SQL Statements             BIOLOG
Record  *...+... 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 ...+... 7 ...+..
MSG ID  SEV  RECORD TEXT
SQL0104  30       1  Position 1 Token #INCLUDE was not valid. Valid tokens: (
                     CL END GET SET CALL DROP FREE HOLD LOCK OPEN WITH ALTER.
                    Message Summary
  Total     Info   Warning      Error   Severe Terminal
      1        0         0          0        1 0
30 level severity errors found in source

Here are the first few generated C code statements in the list produced...

5770SS1 V7R1M0 100423               Run SQL Statements BIOLOG
Record  *...+... 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 ...+... 7 ...
      1 #include "qsys/qasqh/stdlib"
      2 #include "qsys/qasqh/stdio"
      3 #include "qsys/qasqh/string"
      4 #include "qsys/qasqh/decimal"
      5 #include "qsys/qasqh/wcstr"

There's nothing wrong with the source member SQL statements themselves as I can interactively execute the RUNSQLSTM command on the source member and it runs perfectly.
When it fails I can immediately execute the RUNSQLSTM command manually, so there isn't anything wrong with the library list. Since I can run it manually these generated include statements must not REALLY be missing.

Any ideas?