IBM Support

PI07304: RECORD/BLOCK WITH BAD BLOCK SIZE IS WRITTEN TO A BATCH IMS LOG.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Under unique circumstances, cause a bad block size to be written
    to a batch IMS log.The block size x'181B exceeds the LCD block
    size, x'1800.
    We're trying to write a block whose BDW is larger than the block
    size. From their storage alteration SLIP dump, we're trying to
    write a 4802 record to pad out the current buffer, but the
    amount of space left in the buffer is less than what's required
    for the 4802 record.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: IMS V13 users who run DL/I batch             *
    ****************************************************************
    * PROBLEM DESCRIPTION: Under certain circumstances, the last   *
    *                      block of an IMS batch log can have an   *
    *                      invalid block size, causing an I/O      *
    *                      error if it is attempted to be read.    *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    If the ending type06 record that indicates that the IMS batch
    job is terminating is at the end of a block, it can be written
    with an invalid block size, a size larger than the block size of
    the log. This happens if there is not enough room for its record
    as well as a minimum length type48 record.
    

Problem conclusion

  • GEN:
    KEYWORDS:
    
    *** END IMS KEYWORDS ***
    Subroutine LPADBTCH is used to make this determination, but the
    size of the record passed to it is incorrect. The EQUate ACLLEN
    is used to represent the size of the record, but since a LOAD
    instruction is used prior to the subroutine call rather than a
    LOAD ADDRESS, then the value in R0 is incorrect upon calling
    LPADBTCH.
    
    This APAR changes the two places in DFSFLLG0 where this value
    is incorrectly loaded.
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    PI07304

  • Reported component name

    IMS V13

  • Reported component ID

    5635A0400

  • Reported release

    300

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2013-12-03

  • Closed date

    2014-02-14

  • Last modified date

    2014-03-03

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

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

    UI15170

Modules/Macros

  • DFSFLLG0
    

Fix information

  • Fixed component name

    IMS V13

  • Fixed component ID

    5635A0400

Applicable component levels

  • R300 PSY UI15170

       UP14/02/18 P F402 ¢

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"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"300","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
14 December 2020