Handling SQL codes with generated High-speed Apply Engine JCL

In addition to the SQL code responses available with EXECSQL, generated High-speed Apply Engine JCL provides the ability to:

  • Defer a statement or a unit of recovery, and write the deferred statements to a file for examination and subsequent execution
  • Retry a statement in response to SQL codes that indicate either 'time out' conditions or referential integrity (RI) conflicts

Related topic

SQL-code-handling-during-SQL-execution

  • Roll back a statement (as opposed to unit of recovery)
  • Skip a statement or a unit of recovery (normally used after a rollback)

For an example of how to use generated High-speed Apply Engine JCL for SQL code handling with the online interface, see Example-1-SQL-code-handling-with-generated-High-speed-Apply-Engine-JCL-in-the-online-interface. Using the online interface, you can specify an SQL code and a product action.

For example, an SQL code response could specify a code of -803, an action of DeferStatement, and an action of Continue. Notice that with High-speed Apply Engine, you can specify more than one action for each code. You can then generate JCL for a separate job that runs High-speed Apply Engine using your parameters.

Any responses that you define override the product’s default SQL code handling responses.

This section contains the following topics:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*