Preparing DB2 Application Plans › Generating Packages › Impact Report

Impact Report

The report produced by the generation process has three parts:

• The components of the package definition and the programs involved in the package.
• The generated BIND command text, including the DBRM.
• Error and completion messages.

You can produce this report without actually doing the BIND or updating the plan tables by using the VERIFY option on the PRINT PACKAGE command. (For the complete syntax, see the Command Reference Guide.)

The first section of the report shows the package information entered in the package definition. It is identical to the information produced by a PRINT PACKAGE command.

IDEAL APPLICATION PLAN/PKG REPORT
          RELEASE:  11         DATE: March 9, 2006      TIME: 17:11:00
                        GENERATE APPLICATION PLAN/PKG DB2PKG
 IDEAL Application Plan/Pkg DB2PKG        March 9, 2006      17:11:00
          DB2PKG ________                  VERSION:  __   STATUS: PROD
                   PKG  DB2PKG
                   Created:        09/29/04               By $ID
                   Last Modified:  11/01/04 at 09:29      By $ID
                   Short Description:  test
                   Description:
                        ________________________________________________________
                        ________________________________________________________
 IDEAL Application Plan/Pkg DB2PKG        March 9, 2006      17:11:00
          DB2PKG ________                  VERSION:  __   STATUS: PROD
              Collection Id: COLLID
              Bind Options:
              Owner: TESTID        Qualifier:               Location: _____
                   Action:    R (R=Replace, A=Add)  Replver: ______________
                   Retain:    Y (Y=Yes, N=No)
                   Validate:  R (R=Run, B=Bind)
                   Isolation: C (R=Repeatable Read, C=Cursor Stability)
                   Flag:      I (I=InformationalWarningErrorCompletion,
                                 W=WarningErrorCompletion, E=ErrorCompletion
                                 C=Completion only)
                   Acquire    U (U=Use, A=Allocate)
                   Release    C (C=Commit, D=Deallocate)
                   Explain    N (Y=Yes, N=No)
                   Prepare    N (N=Nodefer, D=Defer)
                   Currentdata:  Y (Y=Yes, N=No)
                   SQLerror:     N (N=NoPackage, C=Continue)
                   Enable/Disable:
                   DISABLE (IMS,BATCH,DLIBATCH)
 IDEAL Application Plan/Pkg DB2PKG        March 9, 2006      17:11:00
          DB2PKG ________                  VERSION:  __   STATUS: PROD
                  ------    --------  ----  ---   ----   -------------------
                  SEQ       PROGRAM   VER   SYS   TYPE   COMMENTS
                  ------    --------  ----  ---   ----   -------------------
                  001200    TABSPACE  0001  $ID   PGM
DEAL Application Plan/Pkg DB2PKG        March 9, 2006      17:11:00
                         Application Plan/Pkg Impact Report

SQL MOD   PROGRAM   SYS  VER   TYPE  LANG    SQL STMTS  STATUS  ERROR IND
--------  --------  ---  ----  ----  ------  ---------  ------  -----------
Impact Report Abbreviations:
TYPE:   APPL   - Application (program with all its subprograms)
        PROG   - Program without its subprograms
        SPGM   - Subprogram belonging to an above application
Application Plan/Pkg Statistics:
01     SQL modules are included in this Plan/Pkg
001    Programs are included in this Plan/Pkg
000003 SQL statements are in this Plan/Pkg
IDEAL Application Plan/Pkg DB2PKG        March 9, 2006      17:11:00
                      Authorization ID Assignment Report
       No Authorization ID Assignments are in effect for this Plan/Pkg

The list of programs is shown under the static I/O module name and includes:

• Program name
• System ID
• Program version
• Type (application, program, or subprogram)
• Program language
• Number of SQL statements in the program
• Resource status (the first three are warnings; the rest are fatal errors that terminate the process):
  • DUPLIC-Program already included in the package
  • NOSQL-Program does not contain any SQL
  • EXCLIM-Number of SQL statements exceeds the maximum
  • NOTFND-Program not found (for example, not compiled or not defined to the dictionary)
  • NOTAVL-Program not available (busy)
  • DIFVER-Program already included with a different version
  • HIST-Program in history status
  • INCREL-Program compiled with an incompatible (higher) CA Ideal release

The second section of the report shows the generated BIND command text. It displays all DB2 BIND options selected. The MEMBER list includes the DBRM generated by package generation.

IDEAL Application Plan/Pkg DB2PKG        March 9, 2006      17:11:00
                     Application Plan/Pkg BIND command
DSN SYS (DEVL)
BIND PACKAGE (COLLID) OWNER (TESTID) MEMBER (DB2PKG@) LIBRARY ('IDLD.D-
B2.DBRMLIB') ACTION (REPLACE) VALIDATE (RUN) ISOLATION (CS) FLAG (I)-
RELEASE (COMMIT) EXPLAIN (NO) CURRENTDATA (YES) DISABLE (IMS,BATCH,DLI-
BATCH)


End of Application Plan/Pkg Generation Report

Note: The summary message shows that CA Ideal's package generation process is complete. It does not show the status of the DB2 BIND.