Embed SQL statements in RPG/400 applications that use SQL

SQL statements coded in an RPG/400^® program must be placed in the calculation section.

This requires that a C be placed in position 6. SQL statements can be placed in detail calculations, in total calculations, or in an RPG/400 subroutine. The SQL statements are run based on the logic of the RPG/400 statements.

The keywords EXEC SQL indicate the beginning of an SQL statement. EXEC SQL must occupy positions 8 through 16 of the source statement, preceded by a / in position 7. The SQL statement may start in position 17 and continue through position 74.

The keyword END-EXEC ends the SQL statement. END-EXEC must occupy positions 8 through 16 of the source statement, preceded by a slash (/) in position 7. Positions 17 through 74 must be blank.

Both uppercase and lowercase letters are acceptable in SQL statements.

• Example: Embed SQL statements in RPG/400 applications that use SQL
  An UPDATE statement coded in an RPG/400 program might be coded as this example shows.
• Comments in RPG/400 applications that use SQL
  In addition to SQL comments (--), RPG/400 comments can be included within SQL statements wherever a blank is allowed, except between the keywords EXEC and SQL.
• Continuation for SQL statements in RPG/400 applications that use SQL
  When additional records are needed to contain the SQL statement, positions 9 through 74 can be used. Position 7 must be a + (plus sign), and position 8 must be blank.
• Include code in RPG/400 applications that use SQL
  SQL statements and RPG/400 calculation specifications can be included by embedding the SQL statement.
• Sequence numbers in RPG/400 applications that use SQL
  The sequence numbers of the source statements generated by the SQL precompiler are based on the *NOSEQSRC/*SEQSRC keywords of the OPTION parameter on the CRTSQLRPG command.
• Names in RPG/400 applications that use SQL
  Any valid RPG variable name can be used for a host variable and is subject to the following restrictions.
• Statement labels in RPG/400 applications that use SQL
  A TAG statement can precede any SQL statement. Code the TAG statement on the line preceding EXEC SQL.
• WHENEVER statement in RPG/400 applications that use SQL
  The target for the GOTO clause must be the label of the TAG statement. The scope rules for the GOTO/TAG must be observed.