IBM Support

PI78965: FPECMAIN GETS "FPEC4035W MORE THAN 100000 UNIQUE LONG STRINGS QUALIFYING FOR UNIQUE NAME PROCESSING FOUND IN THE INPUT DATA"

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Customer running FPECMAIN to extract SMF records to load into
    DB2PMFACCT_GENERAL table sees truncation of data when receiving
    FPEC4035W  MORE THAN 100000 UNIQUE LONG STRINGS QUALIFYING FOR
    UNIQUE NAME PROCESSING FOUND IN THE INPUT DATA.
    .
    THIS CAN INDICATE AN INPUT DATA PROBLEM. UNIQUE NAME PROCESSING
    HAS BEEN SUSPENDED TO PREVENT PERFORMANCE DEGRADATION."
    .
    long names processing was stopped and after this short names
    were put in reports and FILE output instead of long ones.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM users of        *
    *                 Batch Reporting, PDB                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: FPEC4035W message may be issued in the  *
    *                      OMPE Batch Reporter JOB SUMMARY LOG     *
    *                      and unique name processing will be      *
    *                      suspended when it should not be.        *
    *                                                              *
    *                      Truncated or unique short names were    *
    *                      externalized to VARCHAR type fields     *
    *                      in the ACCOUNTING FILE instead of       *
    *                      using DB2 provided long names.          *
    *                                                              *
    *                      An ABEND0C4 can be encountered in       *
    *                      SQLACTIVITY REPORT processing using     *
    *                      NTH collected sequential file as the    *
    *                      INPUTDD.                                *
    *                                                              *
    *                      V540 Batch Reporter may issue FPEC9104S *
    *                      message when a correctly migrated V530  *
    *                      user-tailored layout is specified in    *
    *                      SYSIN.                                  *
    ****************************************************************
    * RECOMMENDATION: Apply the provided PTF.                      *
    ****************************************************************
    FPEC4035W message may appear in the OMPE Batch Reporter JOB
    SUMMARY LOG because the related counter is incremented in an
    attempt to register an already registered long name. That may
    cause truncated short names appear in the report instead of
    unique short names.
    
    Truncated or unique short names were externalized to VARCHAR
    type fields in the ACCOUNTING FILE instead of using the DB2
    provided long names. That may complicate the mapping of DB2
    aggregation short identifiers to their original long names
    as they were provided by DB2.
    
    An ABEND0C4 may occur during SQLACTIVITY REPORT processing
    using NTH collected sequential file as the INPUTDD because
    some variables were not properly initialized before reuse.
    
    V540 Batch Reporter may issue a FPEC9104S message when ae.
    correctly migrated V530 user-tailored layout is specified
    in SYSIN. The check for the new version identifier has been
    corrected.
    

Problem conclusion

  • The code was changed to fix the listed problems.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI78965

  • Reported component name

    OM XE DB2PE/PM

  • Reported component ID

    5655OPE00

  • Reported release

    540

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-03-28

  • Closed date

    2017-06-26

  • Last modified date

    2017-07-05

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

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

    UI48304

Modules/Macros

  •    DGOABLOG DGOAFBUF DGOAFDDF DGOAFGBP DGOAFGEN
    DGOAFISA DGOAFPCK DGOAPLLR DGOATOP4 DGOAWAIF FPECHE15 FPEUCBLD
    FPEUFLNS FPEUFLN2 FPEUIFCI FPEUIFC2
    

Fix information

  • Fixed component name

    OM XE DB2PE/PM

  • Fixed component ID

    5655OPE00

Applicable component levels

  • R540 PSY UI48304

       UP17/06/27 P F706

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":"SSAV2B","label":"IBM Db2 Buffer Pool Analyzer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.4.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCT4H5","label":"IBM Tivoli OMEGAMON XE for Db2 PE \/ PM \/ BPA"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.4.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
05 July 2017