Setting the DB2I defaults

When you use the DB2® Interactive (DB2I) panels to prepare an application, you can specify the default values that DB2I is to use. These defaults values can include the default application language and default JCL JOB statement. Otherwise, DB2I uses the system default values that were set at installation time.

Procedure

To set the DB2I defaults:

As DB2I leads you through a series a panels, enter the default values that you want on the following panels when they are displayed.
Table 1. DB2I panels to use to set default values
If you want to set the following default values... Use this panel
  • subsystem ID
  • number of additional times to attempt to connect to DB2
  • programming language
  • number of lines on each page of listing or SPUFI output
  • lowest level of message to return to you during the BIND phase
  • SQL string delimiter for COBOL programs
  • how to represent decimal separators
  • smallest value of the return code (from precompile, compile, link-edit, or bind) that prevents later steps from running
  • default number of input entry rows to generate on the initial display of ISPF panels
  • user ID to associate with the trusted connection for the current DB2I session
 DB2I Defaults Panel 1 panel
  • default JOB statement
  • symbol used to delimit a string in a COBOL statement in a COBOL application
  • whether DCLGEN generates a picture clause that has the form PIC G(n) DISPLAY-1 or PIC N(n).
 DB2I Defaults Panel 2 panel
The following package and plan characteristics
  • isolation level
  • whether to check authorization at run time or at bind time
  • when to release locks on resources
  • whether to obtain EXPLAIN information about how SQL statements in the plan or package execute
  • whether you need data currency for ambiguous cursors opened at remote locations
  • whether to use parallel processing
  • whether DB2 determines access paths at bind time and again at execution time
  • whether to defer preparation of dynamic SQL statements
  • whether DB2 keeps dynamic SQL statements after commit points
  • the application encoding scheme
  • whether you want to use optimization hints to determine access paths
  • when DB2 writes the changes for updated group buffer pool-dependent pages
  • whether run time (RUN) or bind time (BIND) rules apply to dynamic SQL statements at run time
  • whether to continue to create a package after finding SQL errors (packages only)
  • when to acquire locks on resources (plans only)
  • whether a CONNECT (Type 2) statement executes according to DB2 rules (DB2) or the SQL standard (STD). (plans only)
  • which remote connections end during a commit or a rollback (plans only)
 Defaults for Bind Package panel

Defaults for Bind Plan panel