IBM Support

PI13968: DB2 SUBSYSTEM TERMINATION REQUESTED - REASON=00F30420

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DB2TERM defects 171154 d171154 pi13968 dpi13968
    Abend "DB2 SUBSYSTEM TERMINATION REQUESTED - REASON=00F30420"
    if a Stop Accelerator Mode Force command happens to be entered
    while an accelerator related thread is already in the process
    of terminating.
    ***************************************************************
    Additional Symptoms and Keywords:
     ABEND04F AB04F S004F 04F 04F-00F30420 00F30420 RC00F30420
     IDAA DB2IDAA
      IDAAV2R1/K   - for IDAA V2
      IDAAV3R1/K   - for IDAA V3
      IDAAV4R1/K   - for IDAA V4
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users who     *
    *                 use IBM DB2 Analytics Accelerator.           *
    ****************************************************************
    * PROBLEM DESCRIPTION: The -STOP ACCEL MODE(FORCE) command     *
    *                      may cause DB2 subsystem termination     *
    *                      with RC00F30420.                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The -STOP ACCEL MODE(FORCE) command asynchronously cancels any
    DB2 thread that has, or had, accelerator related resources.
    However, if a thread is already in termination processing, the
    asynchronous cancel may interrupt thread termination processing
    which may lead to a DB2 subsystem termination.
      DB2 SUBSYSTEM TERMINATION REQUESTED - REASON=00F30420
    

Problem conclusion

  • DB2 STOP ACCEL MODE(FORCE) command processing has been changed
    to consider that an accelerator related thread may already be
    in termination processing, in which case an additional
    asynchronous cancel is not necessary.
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    PI13968

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-03-18

  • Closed date

    2014-04-21

  • Last modified date

    2014-06-03

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

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

    UI17213 UI17214

Modules/Macros

  • DSNX8STO
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UI17213

       UP14/05/06 P F405 ½

  • RB10 PSY UI17214

       UP14/05/06 P F405 ½

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":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
03 June 2014