IBM Support

PI20381: DFSILTA0 OUTPUT SHOWS SIX ASTERISKS "******" AT "TOTAL SSSST" AND*ABENDED WAS DISPLAYED WRONGLY IN SPITE OF NORMAL COMPLETED

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DFSILTA0 OUTPUT SHOWS SIX ASTERISKS "******" AT "TOTAL SSSST"
    and *ABENDED was displayed wrongly in spite of normal
    transaction completed.
    .
    <<DFSILTA0 (PI09188 current) wrong
    /*ABEND and TOTAL SSSST value '******' >>
      TRANS :  P   PGM     DR SMB*ENQ:IN Q   PROC   OUT Q  TOTAL
      CODE  :  T   NAME    ID HHMMSST:SSSST  SSSST  SSSST  SSSST
    --------:------------------------:--------------------------
    TNDXA53 :  A *ABENDED  31  832366:    0     26            26
    TDAR20  :  A *ABENDED   9  833269:    0      3      0 ******
            :    ========                                 ======
                 Incorrect!!!                         Incorrect!!!
                 (PROBLEM1)                            (PROBLEM2)
    .
    .
    Problem1 : TDAR20 was not abended and it was normal terminated
               with 33/36 log records, so *ABENDED was wrong!!!
               And also 07 log DLRCOMP was 00000000.
    Problem2 : 36/33 log record exists, but TOTAL SSSST '*******'
               was displayed!!!
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All IMS V11 users                            *
    ****************************************************************
    * PROBLEM DESCRIPTION: Transaction incorrectly shown as        *
    *                      abnormally terminated.                  *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    When DFSILTA0 encounters a type07 record with a non-zero
    completion code for the region, it marks the existing region
    processing as abnormally terminated.  Region processing blocks
    have a key composed of the IMS id, the PST number, and the
    clock value from the associated record.  DFSILTA0 builds a
    temporary key using the 07 record time and then searches for
    the region processing block with the largest key that is less
    than the temporary key.  The problem occurs when the 07 record
    is the first record encountered for the region.  DFSILTA0
    usually finds a region processing block for a different region
    and marks it as being abnormally terminated.  This causes the
    erroneous line in the report.
    

Problem conclusion

  • GEN:
    KEYWORDS:
    
    *** END IMS KEYWORDS ***
    DFSILTA0 has been changed to ignore region processing blocks
    unless the IMS id and region number match.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI20381

  • Reported component name

    IMS V11

  • Reported component ID

    5635A0200

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-06-19

  • Closed date

    2014-07-18

  • Last modified date

    2014-08-04

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

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

    PI21543 PI21545 UI19767

Modules/Macros

  •    DFSILTA0
    

Fix information

  • Fixed component name

    IMS V11

  • Fixed component ID

    5635A0200

Applicable component levels

  • R100 PSY UI19767

       UP14/07/22 P F407

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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPH2","label":"IBM Information Management System (IMS)"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"100","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
14 December 2020