IBM Support

PM82817: Batch Accounting SAVE fails with FPEA0700S RC=8 RSN=12

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When specific LOCALE value is set in DFSORT parms, SAVE
    function of PE batch report may fail with the following symptom
    
    FPEA0700S  VSAM PUT FUNCTION FAILED ON DDNAME ACSAVDD . VSAM
    RETURN CODE 8. REASON CODE 12
    FPEC6002E  ACCOUNTING FAILED DURING THE REPORT PROCESSING
    PHASE
    

Local fix

  • - Change LOCALE value to NONE if possible
    - Add "EXCLUDE(PRIMAUTH(PTXMAN))" for record with PRIMAUTH
    PTXMAN
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
    *                 users of component:                          *
    *                 -   Batch Reporting                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: 1. Batch Accounting SAVE fails with     *
    *                      message FPEA0700S VSAM PUT FUNCTION     *
    *                      FAILED ON DDNAME ddname VSAM RETURN     *
    *                      CODE 8. REASON CODE 12.                 *
    *                      If Accounting trace data is used that   *
    *                      contains threads with unspecified       *
    *                      ('BLANK') connection types beside of    *
    *                      known connection types then SAVE        *
    *                      fails with above message.               *
    *                                                              *
    *                      2. If a customer uses a LOCALE in       *
    *                      his sort application, the Batch         *
    *                      Accounting Report may fail. Other       *
    *                      Batch reports and PWH client are also   *
    *                      affected by this problem. Above         *
    *                      message is thrown.                      *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION: Apply this PTF                               *
    *                                                              *
    ****************************************************************
    PROBLEM SUMMARY:
    1. The processing of connection types has been changed with
    respect to a possible connection type which is not assigned by
    DB2.
    
    2. The OMPE internal sort parameters have been changed.
    Instead of using a character based sorting, the internal sort
    process sorts on a binary base which is independent from any
    LOCALE specifications.
    
    PROBLEM CONCLUSION:
    1. OMPE treates an unassigned connection type as a regular
    connection type, named 'BLANK'.
    
    2. The preparation of OMPE batch reports works independent
    from any LOCALE specifications. All reports are generated
    correctly, PWH does not fail due to the incorrect sort
    processing.
    

Problem conclusion

  • 1. OMPE treates an unassigned connection type as a regular
    connection type, named 'BLANK'.
    
    2. The preparation of OMPE batch reports works independent
    from any LOCALE specifications. All reports are generated
    correctly, PWH does not fail due to the incorrect sort
    processing.
    
    KEYWORDS : FPEA0700S CONNECTION TYPE SORT DFSORT SYNCSORT LOCALE
               BATCH  ACCOUNTING PWH
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM82817

  • Reported component name

    OM XE DB2PE/PM

  • Reported component ID

    5655OPE00

  • Reported release

    511

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2013-02-14

  • Closed date

    2013-03-08

  • Last modified date

    2017-06-21

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

    PM76016

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

    UK92380

Modules/Macros

  •    BPOQPRNT DGOAACUM DGOABLOG DGOABORD DGOABORE
    DGOACALC DGOACALX DGOACMER DGOACOMP DGOACREC DGOADIST DGOADNOR
    DGOAEXIT DGOAEX20 DGOAFDDF DGOAFGEN DGOAFORM DGOAIREC DGOAIREP
    DGOAMTRC DGOAPARC DGOARCAL DGOAREDB DGOAREDC DGOAREDD DGOAREDG
    DGOAREDI DGOAREDM DGOAREDP DGOAREDR DGOAREDX DGOARXIT DGOASAVE
    DGOATRAC DGOATREC DGOAZMER DGOAZREC DGOBGENL DGOETERM DGOFEDPM
    DGOFPDAT DGOFPDPM DGOFPECO DGOFPE15 DGOFPRIC DGOMGRDP DGOMTDDF
    DGOMTLCK DGOMTPOP DGOMTSQL DGOPACNV DGOPA920 DGORAEXT DGORIREP
    DGORPACC DGORRSQL DGORUACC DGORZREP DGOTBPRT DGOTPRNT DGOVSCT1
    DGOVSCT2 DGOVSDPM DGOVSUTL FPECHECO FPECHE15 FPECKECO FPECMDAT
    FPECQECO FPEUCBPR FPEUCBXT FPEUFOCR FPEUFOC2 FPEUFTDP FPEUFTP2
    FPEUFUDA
    

Fix information

  • Fixed component name

    OM XE DB2PE/PM

  • Fixed component ID

    5655OPE00

Applicable component levels

  • R511 PSY UK92380

       UP13/03/12 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":"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.1.1","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.1.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
21 June 2017