Preparing an application to run on DB2 for z/OS

To prepare and run applications that contain embedded static SQL statements or dynamic SQL statements, you must precompile, compile, link-edit, and bind them.

About this task

You can perform these steps by using one of the following methods:

Productivity hint: To avoid rework, first test your SQL statements using SPUFI. Then compile your program without SQL statements, and resolve all compiler errors. Finally, proceed with the preparation and the DB2® precompiler or with the host compiler that supports that DB2 coprocessor.
The following types of applications require different methods of program preparation:
  • Applications that contain ODBC calls
  • Applications in interpreted languages, such as REXX
  • Java applications, which can contain JDBC calls or embedded SQL statements

For information about running REXX programs, which you do not prepare for execution, see Running a DB2 REXX application.

Steps in program preparation

The following topics provide details on preparing and running a DB2 application:

Binding a package is not necessary in all cases. These instructions assume that you bind some of your DBRMs into packages and include a package list in your plan.

If you use CICS®, you might need additional steps; see:

For more information about when to bind a package, see DB2 program preparation overview.

Preparing applications by using JCL procedures

A number of methods are available for preparing an application to run. You can:
  • Use DB2 interactive (DB2I) panels, which lead you step by step through the preparation process.
  • Submit a background job using JCL (which the program preparation panels can create for you).
  • Start the DSNH CLIST in TSO foreground or background.
  • Use TSO prompters and the DSN command processor.
  • Use JCL procedures added to your SYS1.PROCLIB (or equivalent) at DB2 installation time.
  • For C and C++ only, you can invoke the coprocessor from UNIX System Services and, if the DBRM is generated in a HFS file, you can use the command line processor to bind the resulting DBRM. Optionally, you can also copy the DBRM into a partitioned data set member by using the oput and oget commands and then bind it by using conventional JCL.

This topic describes how to use JCL procedures to prepare a program.

For information about using the DB2I panels, see Preparing an application to run on DB2 for z/OS.

Preparing applications by the DB2 Program

If you develop programs using TSO and ISPF, you can prepare them to run by using the DB2 Program Preparation panels. These panels guide you step by step through the process of preparing your application to run. Other ways of preparing a program to run are available, but using DB2 Interactive (DB2I) is the easiest because it leads you automatically from task to task.

Important: If your C++ program satisfies both of the following conditions, you must use a JCL procedure to prepare it:
  • The program consists of more than one data set or member.
  • More than one data set or member contains SQL statements.
To prepare an application by using the DB2 Program Preparation panels:
  1. If you want to display or suppress message IDs during program preparation, specify one of the following commands on the ISPF command line:
    TSO PROFILE MSGID
    Message IDs are displayed
    TSO PROFILE NOMSGID
    Message IDs are supressed
  2. Open the DB2I Primary Option Menu.
  3. Select the option that corresponds to the Program Preparation panel.
  4. Complete the Program Preparation panel and any subsequent panels. After you complete each panel, DB2I automatically displays the next appropriate panel.

Preparation guidelines for DL/I batch programs

Use the following guidelines when you prepare a program to access DB2 and DL/I in a batch program:
  • 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.
  • Processing SQL statements
    The first step in preparing an SQL application to run is to process the SQL statements in the program. To process the statements, use either the DB2 precompiler or the DB2 coprocessor. During this step, the SQL statements are replaced with calls to DB2 language interface modules, and a DBRM is created.
  • Compiling and link-editing an application
    If you use the DB2 precompiler, your next step in the program preparation process is to compile and link-edit your program. As with the precompile step, you have a choice of methods.
  • The bind process
    The bind process establishes a relationship between an application program and its relational data. This process is necessary before you can execute your program.
  • Binding an application
    Start of changeYou must bind the DBRM that is produced by the SQL statement processor to a package before your DB2 application can run. End of change
  • Rebinding an application
    You need to rebind an application if you want to change any bind options. You also need to rebind an application when you make changes that affect the plan or package, such as creating an index, but you have not changed the SQL statements.
  • Specifying the rules that apply to SQL behavior at run time
    You can specify whether DB2 rules or SQL standard rules apply to SQL behavior at run time.
  • DB2 program preparation overview
    Before you can run an application program on DB2 for z/OS, you need to prepare it. To prepare the program, create a load module, possibly one or more packages, and an application plan.
  • Input and output data sets for DL/I batch jobs
    DL/I batch jobs require an input data set with DD name DDITV02 and an output data set with DD name DDOTV02.
  • DB2-supplied JCL procedures for preparing an application
    You can precompile and prepare an application program using a DB2-supplied JCL procedure.
  • DB2I panels that are used for program preparation
    DB2I contains a set of panels that let you prepare an application for execution.
  • DB2I panels that are used to rebind and free plans and packages
    A set of DB2I panels lets you bind, rebind, or free packages.
Related concepts:
Command line processor
TSO attachment facility
Related reference:
The DB2I primary option menu
DSNH (TSO CLIST)