IBM Support

PI56257: ABEND0C4 IN IPISDLOC NEAR X'A2C'

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • ABENDS0C4 in IPISDLOC+A2C.
    When the first IMS x'67FF' record processed by the DEADLOCK
    report is a continuation record, the following messages are
    written to the DEADLOCK report DD:
     INPUT DID NOT START WITH THE BEGINNING OF A DATA ELEMENT.
     ELEMENT STARTING ADDRESS IS ASSUMED TO BE 0.
     START OF THIS DATA ELEMENT IS PROBABLY ON THE PRIOR LOG DATASET
    
    After producing these messages no further processing should
    occur as the full record cannot be reconstructed, instead the
    DEADLOCK report processor attempts to process the record as if
    it were complete. This will cause unpredictable results,
    including invalid report output and possible S0Cx abends.
    
    S0C4 ABEND0Cx ABENDS0Cx
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of IMS Performance Analyzer V4.4       *
    ****************************************************************
    * PROBLEM DESCRIPTION: Abend S0C4 in IPISDLOC+A2C.             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When the first IMS x'67FF' record processed by the DEADLOCK
    report is a continuation record, the following messages are
    written to the DEADLOCK report DD:
    
    INPUT DID NOT START WITH THE BEGINNING OF A DATA ELEMENT.
    ELEMENT STARTING ADDRESS IS ASSUMED TO BE 0.
    START OF THIS DATA ELEMENT IS PROBABLY ON THE PRIOR LOG
    
    After producing these messages no further processing should
    occur, as the full record cannot be reconstructed, instead
    the DEADLOCK report processor attempts to process the record
    as if it were complete. This will cause unpredictable
    results, including invalid report output and possible S0Cx
    abends.
    

Problem conclusion

  • After producing the messages indicating that required IMS
    x'67FF' starting element was not found, the record is
    discarded and processing continues with the next record.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI56257

  • Reported component name

    IMS PERF ANALYZ

  • Reported component ID

    5655E1500

  • Reported release

    440

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-01-28

  • Closed date

    2016-02-04

  • Last modified date

    2016-03-02

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

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

Modules/Macros

  • IPISAPAR IPISDLOC
    

Fix information

  • Fixed component name

    IMS PERF ANALYZ

  • Fixed component ID

    5655E1500

Applicable component levels

  • R440 PSY UI35071

       UP16/02/09 P F602

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":"4.4.0","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX8A2","label":"IMS Performance Analyzer"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.4.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 March 2016