IBM Support

PI37417: ABEND UFFD-00000090 on DDF startup when LE POSIX is enabled at system level prior to DB2 DDF startup

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DB2DDF DB2HANG defect pi37417 dpi37417
    ABEND ABNDUFFD-00000090 M=DSNVEUS3 is issued for the DIST
    asid on DB2 startup when POSIX(ON) has been set at the system
    level prior to DB2 or DDF being started.
    DB2 startup may show "complete" but DB2 may hang if DDF
    automatically starting due to DDF initialization not
    
    
    ABNDUFFD is an abend U4093.
    The Dump failing psw will point into LE module CEEPIPI
    
    An example of the command to set POSIX(ON) would be
    SETCEE CEEDOPT,POSIX(ON)
    If this SETCEE is done with DB2 already started and active,
    there is no impact.
    ***************************************************************
    Additional Symptoms and Keywords:
     POSIX
     Abend ABENDUFFD  ABNDUFFD  ABENDFFD  ABNDFFD  UFFD  FFD
           ABENDU4093 ABNDU4093 ABEND4093 ABND4093 U4093 4093
      ABNDUFFD-00000090 00000090 RC00000090
     ABEND0C4 AB0C4 S00C4 0C4
      0C4-00000010 00000010 RC00000010
       DSNLTRTP DSNLTRTP+04C8 04C8 OFFSET04C8
     ABEND04E AB04E S004E 04E
      04E-00F3040B 00F3040B RC00F3040B
       DSN3SSTM DSN3SSTM+03EE 03EE OFFSET03EE
    

Local fix

  • local workaround/fix: If POSIX(ON) has been set at the lpar
    level, disable POSIX(ON) prior to starting DB2. Allow DB2
    startup and DDF initialization to complete before enabling
    POSIX(ON) at the lpar level.
    Command SETCEE CEEDOPT,POSIX(OFF) can be used
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
    ****************************************************************
    * PROBLEM DESCRIPTION: Abend FFD-00000090 during DDF start     *
    *                      processing if LE POSIX system level     *
    *                      default is enabled.                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The user has enabled LE POSIX as the system level default via
    the LE "SETCEE CEEDOPT,POSIX(ON)" command.
    This causes an LE abend U4093 with reason 00000090 during DDF
    start processing and DDF start processing will not complete.
    If DDF start processing is automatically initiated as part of
    DB2 start processing, DB2 start processing will also not
    complete.  Once this condition occurs, DDF cannot be stopped or
    restarted because it's still in a starting state (message
    DSNL023I).  DB2 must be abnormally terminated (ex: via MVS
    "Cancel ssnmDIST" command) in order to get back into a state
    where DDF (and DB2) can be started.
    The user must first disable LE POSIX as the system level
    default via the LE "SETCEE CEEDOPT,POSIX(OFF)" command in order
    for the DDF start to succeed.
    DDF start processing must initialize an LE environment into
    internal (TCB based) system tasks.  DB2/DDF does not require an
    LE POSIX environment for these tasks and therefore makes no
    effort to clean up unwanted resources that might otherwise
    exist relative to an LE POSIX environment.  However, DB2 does
    not explicitly specify that POSIX is not required and therefore
    did not consider that an LE POSIX environment may have been
    initialized anyway as a result of a system level default.  As a
    result, LE detects an abend 4093-00000090 condition when
    DB2/DDF attempts to initialize an LE environment into the
    second system task.
    

Problem conclusion

  • For system tasks that do not require an LE POSIX environment,
    DDF start processing has been changed to explicitly specify
    that a POSIX environment is not required, thereby avoiding any
    conflict with the system level default.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI37417

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-03-19

  • Closed date

    2015-03-31

  • Last modified date

    2015-05-04

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

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

    UI26410 UI26411

Modules/Macros

  • DSNLILE
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UI26410

       UP15/04/15 P F504

  • RB10 PSY UI26411

       UP15/04/15 P F504

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:
04 May 2015