Previous Topic Next topic Print topic


APDB2IN

Controls SQL calls.
Restriction: This topic applies only when the AppMaster Builder AddPack has been installed, and applies only to Windows platforms.

File Contents:

Edit APDB2IN to control the following for SQL calls:

  • Comment generation; the default generates comments
  • EJECTs
  • Size of SQL calls accepted (default is 200 tokens, for example, items separated by spaces)
  • Generation of the IBM DCLGEN convention, DCLtablename, for host 01-level qualifiers
  • Automatic error processing, controlled by the variable &D2-AUTO-ERROR-HANDliNG (default is ON)
  • Customization of automatic error processing, including:
    • Modifying the AMB error processing paragraph &D2-ERROR-PARA, which resides in the rule $DB2-ERROR-SETUP
    • Modifying which status codes should be considered error conditions, in the rule $DB2-CHECK-RETURNS-AUX, and changing the status of a referential integrity constraint from an abnormal condition to an invalid key
  • The DB-PROCESS call loop limit flag, &DB2-LOOP-liMIT (default is 100); you can change the limit number or disable the check for the limit.
  • COMMIT generation for the DB-MODIFY, DB-STORE, DB-ERASE, and DB-CLOSE calls.
  • DB2 customization exits, which are program locations where you can write your own rules to customize AMB SQL calls.
  • Generated data names. You can:
    • Override the use of the IND-cursorname structure when generating indicator variables
    • Use an 01-level name instead of copylib-REC for DB2 record host-variable qualification
    • Modify generated data names used by $DB2-EPILOGUE, which is invoked after all DB2 calls have been processed
    • Use a table alias name instead of the table name
  • Comment generation for the AMB $DB2- calls, which are used by the SQL calls.
  • SQL Get Diagnostics generation and customization, including:
    • User Exit for adding user logic to handle multiple conditions.
    • Customization of which diagnostics information is returned.
    • Automatic generation of GET DIAGNOSTICS calls after each SQL statement if &D2-AUTO-GET-DIAGNOSTICS is set to YES (default is NO).
    • Macro $DB2-GET-DIAGNOSTICS, which you can customize. Invoke it after any SQL call to get SQL diagnostics information for that call. Indent user logic under $DB2-GET-DIAGNOSTICS for multiple-row condition information that is returned in a loop.
Previous Topic Next topic Print topic