IBM Support

PM91601: ADBTEP2 --#SET MAXERROR DOES NOT BEHAVE LIKE DSNTEP2 / DSNTEP4.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The DB2 Administration Tool for z/OS' Batch Restart program
    ADBTEP2 does not process the --SET# MAXERROR directive in the
    same way as the DB2 for z/OS SQL execution program DSNTEP2 /
    DSNTEP4.
    
    ADBTEP2 will fail after the first unsuccessful statement while
    DSNTEP2 will continue processing upto the limit set by MAXERROR.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of the DB2 Administration Toolfor      *
    *                 z/OS who use the Batch Restart Program       *
    *                 ADBTEP2 to ignore some SQLCODES for SQL      *
    *                 statements during execution.                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: The DB2 Administration Tool for z/OS    *
    *                      Batch Restart Program ADBTEP2 only      *
    *                      applies --#SET ACCEPT_RC to the single  *
    *                      SQL statement following the --#SET      *
    *                      ACCEPT_RC statement. This makes         *
    *                      ignoring certain or all SQLCODEs for    *
    *                      one or multiple statements more         *
    *                      difficult.                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The DB2 Administration Tool for z/OS' Batch Restart Program
    ADBTEP2 only applies --#SET ACCEPT_RC to the single SQL
    statement following the --#SET ACCEPT_RC statement. This
    makes ignoring certain or all SQLCODEs for one or multiple
    statements more difficult.
    

Problem conclusion

  • The following enhancement to the function --#SET ACCEPT_RC
    statement is delivered:
    
    1. Keep the use of --#SET ACCEPT_RC m n to accept the maximum
    five SQLCODEs for the following single SQL statement as
    original.
    
    Example: Accept SQLCODEs -204 and -672 for only DROP TABLE
    statement:
    
    --#SET ACCEPT_RC -204 -672
    DROP TABLE schema.tablename;
    CREATE TABLE schema.tablename;
    
    2. Extend the use that only using the start marker
    --#SET ACCEPT_RC can accept all SQLCODEs for the following
    single SQL statement.
    
    Example: Accept all SQLCODEs for only DROP TABLE statement:
    
    --#SET ACCEPT_RC
    DROP TABLE schema.tablename;
    CREATE TABLE schema.tablename;
    
    3. Extend the use that using --#SET ACCEPT_RC ON m n can accept
    the maximum five SQLCODEs for the following multiple statements,
    next --#SET ACCEPT_RC OFF occurred.
    
    Example: Accept SQLCODEs -204 and -672 for DROP TABLE and
    CREATE TABLE statements which are before --#SET ACCEPT_RC OFF
    statement:
    
    --#SET ACCEPT_RC ON -204 -672
    DROP TABLE schema.tablename;
    CREATE TABLE schema.tablename;
    --#SET ACCEPT_RC OFF
    SELECT * FROM schema.tablename;
    
    4. Extend the use that only using the start marker
    --#SET ACCEPT_RC ON can accept all SQLCODEs for the
    following multiple statements, until the next --#SET
    ACCEPT_RC OFF occurs.
    
    Example: Accept all SQLCODEs for DROP TABLE and CREATE
    TABLE statements which are before the --#SET ACCEPT_RC OFF
    statement:
    
    --#SET ACCEPT_RC ON
    DROP TABLE schema.tablename;
    CREATE TABLE schema.tablename;
    --#SET ACCEPT_RC OFF
    SELECT * FROM schema.tablename;
    
    5. Note that there is an embedded capability for --#SET
    ACCEPT_RC (ON/OFF) statements.
    
    Example: You can see --#SET ACCEPT_RC -204 statement is
    embedded in --#SETACCEPT_RC ON/OFF statements.  In this case,
    besides the DROP TABLE statement, the Batch Restart Program
    ADBTEP2 will also accept all SQLCODEs for CREATE TABLE
    statement because CREATE TABLE is embedded in--#SET ACCEPT_RC
    ON/OFF statements:
    
    --#SET ACCEPT_RC ON
    DROP TABLE schema.tablename;
    --#SET ACCEPT_RC -204
    CREATE TABLE schema.tablename;
    --#SET ACCEPT_RC OFF
    SELECT * FROM schema.tablename;
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM91601

  • Reported component name

    DB2 ADMIN TOOL

  • Reported component ID

    568851500

  • Reported release

    A20

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-06-21

  • Closed date

    2013-11-13

  • Last modified date

    2013-12-02

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UI12470 UI12472

Modules/Macros

  •    ADBTEPA  ADBTEPR  ADBTEP2  ADB2WVL
    

Fix information

  • Fixed component name

    DB2 ADMIN TOOL

  • Fixed component ID

    568851500

Applicable component levels

  • RA10 PSY UI12470

       UP13/11/15 P F311

  • RA20 PSY UI12472

       UP13/11/15 P F311

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSCVQTD","label":"IBM Db2 Administration Tool for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.2.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
02 December 2013