OA25988: IDCAMS DEFINE OF A LINEAR WITH A CISIZE OF LARGER THAN 4K AND SPACE SPECIFED IN RECORDS DOES NOT ALLOCATE THE CORRECT SPACE

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as fixed if next.

Error description

  • An IDCAMS define of a linear data set with a cisize greater than
    4096 and space specified in records will not allocate the
    correct amount of space. The space should be calculated using
    the cisize times the number of records, but it is currently
    using a value of 4096 times the number of records. For example a
    32K cisize will produce a data set with 1/8th the expected
    amount of space.
    

Local fix

  • If possible, use tracks or cylinders when defining a linear data
    set with a cisize larger than than 4096.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: This problem will in fixed in future         *
    *                 release with PTM K1B0501 and K1B0502.        *
    ****************************************************************
    * PROBLEM DESCRIPTION: AMS currently does not support the      *
    *                      DEFINE of a linear data set with CISIZE *
    *                      greater than 4K.  With this apar, AMS   *
    *                      will set the CISIZE as the value        *
    *                      specified in the DEFINE.  But when the  *
    *                      CISIZE is 32K, CATALOG failed the       *
    *                      allocation with RC=192 and RS=0.  So to *
    *                      have a completed solution for this      *
    *                      support.  Catalog needs to be changed   *
    *                      to check to see if the data set being   *
    *                      defined is linear data set, if so, set  *
    *                      the overhead required to zero as linear *
    *                      data set does not have any record       *
    *                      overhead.  As a results, 2 PTMs are     *
    *                      open to fix this problem:               *
    *                      K1B0501 (CAT)                           *
    *                      K1B0502 (AMS)                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    This apar closed FIN with 2 PTMS :
    K1B0501 (CAT)
    K1B0502 (AMS)
    

Problem conclusion

Temporary fix

Comments

  • CONTROL NUMBER:K1B0501 K1B0502
    
    The solution for this was delivered in z/OS 1.11 as part of
    the base code for FMID HDZ1B10. RB10
    

APAR Information

  • APAR number

    OA25988

  • Reported component name

    ACCESS METHOD S

  • Reported component ID

    5695DF103

  • Reported release

    190

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / Pervasive

  • Submitted date

    2008-07-25

  • Closed date

    2008-09-29

  • Last modified date

    2010-01-04

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

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

Fix information

Applicable component levels

  • R190 PSN

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

z/OS family

Software version:

190

Operating system(s):

MVS, z/OS

Reference #:

OA25988

Modified date:

2010-01-04

Translate my page

Machine Translation

Content navigation