IBM Support

PM83106: DBD MAPPER ISSUES INCORRECT MESSAGE WHEN USING DBD FOR A LOGICAL DATABASE AND THE REFERRED DBD WITHOUT THE REFERRED SEGMENT

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When DBD mapper processes a DBD for a logical database which has
    multiple occurrence for SEGM SOURCE= statement and the first
    referred DBD is found, but the referred segment does not exist
    in the DBD, unnecessary FABM0004W with incorrect DB name is
    issued.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: IMS Library Integrity Utilities for z/OS,    *
    *                 Version 2 Release 1 (FMID=H27P210) users     *
    *                 who use DBD/PSB/ACB Mapper utilities.        *
    ****************************************************************
    * PROBLEM DESCRIPTION: DBD mapper issues an incorrect message  *
    *                      when using a DBD for a logical database *
    *                      which has a concatenated segment and    *
    *                      the referred DBD without the source     *
    *                      segment.                                *
    ****************************************************************
    * RECOMMENDATION: Apply the maintenance for this APAR.         *
    ****************************************************************
    When DBD mapper processes a DBD for a logical database which has
    a concatenated segment by specifying multiple occurrence for
    SEGM SOURCE= statement and the following conditions met,
    unnecessary FABM0004W with incorrect DB name is issued. It also
    potentially abends depends on the condition of the internal work
    area of the DBD mapper.
    
     - The DBD which is specified as the first occurrence of the
       concatenated segment is found
     - The source segment does not exist in the DBD
    

Problem conclusion

  • The following modules and macros have been changed to fix the
    above problem:
    
     - FABMDBD4
     - FABMDMAP
     - FABMPMAP
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM83106

  • Reported component name

    IMS LIBR INTEG

  • Reported component ID

    5655I4200

  • Reported release

    210

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2013-02-19

  • Closed date

    2013-03-01

  • Last modified date

    2013-04-02

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

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

    UK92117

Modules/Macros

  • FABMDMAP FABMPMAP
    

Fix information

  • Fixed component name

    IMS LIBR INTEG

  • Fixed component ID

    5655I4200

Applicable component levels

  • R210 PSY UK92117

       UP13/03/06 P F303

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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.1.0","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX89N","label":"IMS Library Integrity Utilities"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.1.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 April 2013