General methods for generating and executing SQL statements

The following table describes the product’s general methods to execute the SQL statements contained in an existing file, and summarizes the High-speed Apply features that are available with each method.

For more information about High-speed Apply features that respond to SQL codes, see SQL code handling during SQL execution.

Method

Available High-speed Apply features

Online interface

Batch interface

EXEC SQL

This method creates a separate Execute SQL step (not part of a log scan step) within a new or existing work ID. For more information, see

Execution of SQL statements, plus

  • object mapping (translation of object names during generation, also called SQLXLAT, provided during the log scan step, not part of EXECSQL)

  • limited conflict rules (responding to SQL codes during execution, also called SQLCODES)

From the Main Menu, select Create or Edit Work IDs, and add an Execute SQL step to a work ID.

Statement: EXECSQL

Generated High-speed Apply JCL

This method creates a separate High-speed Apply JCL generation step (not part of a log scan step) within a work ID.

For more information, see Examples using generated High-speed Apply JCL.

All features of EXECSQL, plus

  • Object mapping (translation of object names during execution)

  • More extensive options for conflict rules

  • Multi-threaded execution of SQL statements (multiple agents)

  • Control over distribution of work between agents

  • Ability to defer SQL statements or units of work in a separate file

  • Control over frequency of commit actions (size of units of work)

  • More control over binding of High-speed Apply static plans

  • More control over retry actions in case of conflicts

From the Main Menu, select Generate High-speed Apply JCL.

Follow the sequence of panels to specify High-speed Apply configuration parameters. You can then generate JCL for a separate job that runs High-speed Apply using your parameters.

Not available

Independently coded High-speed Apply JCL

For more information, see Example 1: SQL code handling with independently coded High-speed Apply JCL.

All features of the High-speed Apply Engine, including the following features not available in generated High-speed Apply JCL:

  • Restart capability

  • Distribution to preserve original units of work

  • More High-speed Apply features

Not available

Code a separate job or job step that explicitly runs the High-speed Apply Engine. Specify configuration parameters either in a separate configuration file or in-stream in your JCL.

Was this page helpful? Yes No Submitting... Thank you

Comments