IBM Support

PI56328: HPC1113E DBRC API SEQUENCE ERROR ENCOUNTERED WHEN LOGS HAVE SAME START TIME

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • HPC1113E DBRC API SEQUENCE ERROR ENCOUNTERED
    received when two or more logs have the same start time.
    STARTIME timestamps are recorded in the format
    YYYY.MM.DD.HH.MM.SS.NNNNNN where NNNNNN is the millionth of a
    second. This is a very rare occurrence where two datasets from
    different members of a PLEX record log datasets with the same
    timestamp down to the six digit millions of a second.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of IMS Recovery Solution Pack:     *
    *                 IMS High Performance Change Accumulation     *
    *                 utility.                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: When IMS High Performance Change        *
    *                      Accumulation finds two log datasets     *
    *                      with the same START timestamp the job   *
    *                      fails with HPC1113E and USER COMPLETION *
    *                      CODE=3400 REASON CODE=00000046.         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    HPCA builds a verification table sequenced on START time.
    For each log dataset being used during the current execution
    of HPCA the log dataset is looked up in the START sequenced
    table.  Since two of the datasets had the same START timestamp
    the second was not included in the START timestamp sequenced
    table.  STARTIME timestamps are recorded in the format
    YYYY.MM.DD.HH.MM.SS.NNNNNN where NNNNNN is the millionth of a
    second.  This is a very rare occurrence where two datasets from
    different members of a PLEX record log datasets with the same
    timestamp down to the six digit millions of a second.
    
    HPC9991E SORT0001 PROC(ASCA0001) CAGRP(CRR225G1), not started:
    HPC1113E DBRC API sequence error encountered
    
    HPCADRIV COND: S000 U0020
    ABEND U3400-46,DUMP at HPCAMAIN+00003954  Task: HPCAMAIN
    GP Regs 00-03 00000110 2742A0D4 00000040 008CE9D4
            04-07 008CE9B0 008F8588 008B2FC8 00F99D00
            08-11 008C4F88 A7403680 27427E00 27401000
            12-15 A7400000 27429118 A7403928 00000000
    
    PSW AT ENTRY TO ABEND   078D1000  A74054F4  ILC  02  INTC  000D
    PSW LOAD MODULE           ADDRESS = 27400000  OFFSET = 000054F4
    NAME=HPCAMAIN
    

Problem conclusion

  • The High Performance Change Accumulation utility is changed to
    Include dataset name as part of the key into the timestamp
    sequenced table to ensure uniqueness of entries.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI56328

  • Reported component name

    IMS RCVR SOLUTN

  • Reported component ID

    5655V8600

  • Reported release

    110

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-01-29

  • Closed date

    2016-04-06

  • Last modified date

    2016-05-04

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

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

    UI36808

Modules/Macros

  • HPCAVETR
    

Fix information

  • Fixed component name

    IMS RCVR SOLUTN

  • Fixed component ID

    5655V8600

Applicable component levels

  • R110 PSY UI36808

       UP16/04/12 P F604

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":"1.1.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 May 2016