IBM Support

PM11897: SRB LOOP IN DB2 WHEN RUNNING IVP JOB DSNTEJ1 AFTER ENABLING VERSION 9.1 NEW-FUNCTION MODE WITH UK54618 (FIXES PK97316)

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • After applying PTF UK54618 (fixes APAR PK97316), customers who
    have migrated to DB2 for z/OS Version 9.1 can encounter a DB2
    looping problem when running the V9 installation verification
    procedure (IVP) job DSNTEJ1.
    
    The error occurs only if the V8 DSN8EAE1 sample editproc module
    is resident in DB2 when the V9 IVP jobs are executed.  This
    situation can occur if the V8 EMP table is modified (causing
    the V8 sample edit proc module to be loaded by DB2), and
    subsequently the V9 IVP jobs are run before DB2 is stopped
    and restarted.
    
    Only customers who are in the process of enabling V9
    new-function mode are affected by this problem.  Such
    customers can avoid the problem completely by stopping
    and restarting DB2 immediately before running job DSNTEJ1.
    
    DB2MIGV9/K
    

Local fix

  • Before running the V9 DSNTEJ1 job, stop and restart DB2.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users who run job DSNTEJ1 after          *
    *                 migrating to DB2 Version 9.1 new-function    *
    *                 mode are affected by this change.            *
    ****************************************************************
    * PROBLEM DESCRIPTION: After migration to DB2 V9 new-function  *
    *                      mode, an SRB (service request block)    *
    *                      loop occurs when running sample job     *
    *                      DSNTEJ1, job step PH01S13.              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    After applying PTF UK54618 (fixes APAR PK97316), customers who
    have migrated to DB2 for z/OS Version 9.1 can encounter a DB2
    looping problem when running the V9 installation verification
    procedure (IVP) job DSNTEJ1.
    
    The error occurs only when all three of the following
    conditions are met:
    (1) In your customized copy of job DSNTEJ1, job step PH01S02
        creates the sample table DSN8910.EMP with an edit proc
        named DSN8EAE9 -and- job step PH01S07 creates the DSN8EAE1
        load module with an alias of DSN8EAE9.
    (2) The V8 DSN8EAE1 sample edit proc module is resident in DB2
        when the V9 DSNTEJ1 job is executed.  This situation can
        occur if the V8 EMP table is modified (causing the V8
        DSN8EAE1 edit proc load module to be loaded by DB2).
    (3) You subsequently run the V9 DSNTEJ1 job without having
        first stopped and restarted DB2.
    

Problem conclusion

  • To prevent DSNTEJ1 from causing DB2 to enter an SRB loop, the
    installation CLIST is modified so that in ENFM mode only it
    edits IVP job DSNTEJ1 as follows:
    - In job step PH01S02, the create statement for the DSN8910.EMP
      table continues to be edited to specify EDITPROC DSN8EAE9
      instead of EDITPROC DSN8EAE1.
    - In job step PH01S07, the link edit plan for module DSN8EAE1
      is now edited to create a module called DSN8EAE9 with alias
      DSN8EAE1.  This change ensures that DB2 does attempt to
      reload module DSN8EAE1 in order to process table DSN8910.EMP.
    - A new job step PH01S07D is inserted during editing of DSNTEJ1
      to reside directly before job step PH01S07.  When executed,
      step PH01S07D deletes any existing module or alias called
      DSN8EAE1 in order to permit step PH01S07 to successfully
      define DSN8EAE1 as an alias of DSN8EAE9.
    These changes, which are in effect only when you have migrated
    to DB2 V9 new-function mode:
    (1) Force DB2 to load the V9 DSN8EAE1 edit proc module (as
        DSN8EAE9), even if the V8 DSN8EAE1 edit proc module is
        already loaded.
    (2) Provide the alias of DSN8EAE1 for possible future use by
        applications that reference the V8 sample emp table.  This
        is fine because the V9 DSN8EAE1 edit proc module works with
        the V8 sample EMP table as well as the V9 sample EMP table.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM11897

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-04-09

  • Closed date

    2010-05-07

  • Last modified date

    2011-02-19

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

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

    UK56789

Modules/Macros

  •    DSNTEJ1  DSNTIJNX DSNTIJOC DSNTIJOM DSNTIJOS
    DSNTINST DSNTINS1 DSNTINS2 DSNTINS3
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • R910 PSY UK56789

       UP10/05/11 P F005

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.



Document information

More support for: DB2 for z/OS

Software version: 9.1

Reference #: PM11897

Modified date: 19 February 2011


Translate this page: