IBM Support

PQ50887: SORT MESSAGE "INCORE SORT CAPACITY EXCEEDED" RECEIVED BECAUSE DYNALLOC DEFAULT IS SET TO NO.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Sort message "INCORE SORT CAPACITY EXCEEDED".  Sort work
    datasets are not being allocated dynamically because the
    Sort default for DYNALLOC is set to No.  Rather than have
    users add sork work DDs or change DYNALLOC default, sort will
    be attached setting DYNALLOC to yes for the job.
    

Local fix

  • Change DYNALLOC default to yes, or manually override the
    DYNALLOC parameter for the job.
    Or, add sort work DD statements with DDnames of
    FxxxWKyy
    where xxx = 001 through the number of indexes being built
    and yy = 01 through the number of word datasets requested for
    each sort.  For example, if building 2 indexes and requested
    3 work datasets for each, add sort work DD statements for:
    F001WK01, F001WK02, F001WK03, F002WK01, F002WK02, F002WK03.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Index Builder V2 users who have their        *
    *                 system-installed DYNALLOC sort parameter set *
    *                 to a default of "NO".                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: The customer uses SYSNCSORT. Their      *
    *                      Index Builder job received a WER175A    *
    *                      INCORE SORT CAPACITY EXCEEDED error     *
    *                      message, which caused sort to abend     *
    *                      with ABENDS222.                         *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    The customer's Index Builder job contained sort work DD
    statements that were defined as SORTWKxx. Index Builder invokes
    sort using internally named DD statements.
    As the customer's DYNALLOC default was "NO", Index Builder did
    not dynamically allocate sort work DDs, so when the sort needed
    a sort work DD it failed.
    

Problem conclusion

  • Index Builder V2 was changed to include the DYNALLOC sort
    control parameter. This will ensure that regardless of how sort
    has been defined at installation and what DD names may be
    defined in a job's JCL, Index Builder will always
    dynanically allocate as many sort work DDs it needs using
    an internal naming convention.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PQ50887

  • Reported component name

    IMS INDEX BUILD

  • Reported component ID

    5655E2400

  • Reported release

    210

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2001-07-24

  • Closed date

    2001-08-03

  • Last modified date

    2001-09-06

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

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

    UQ56695

Modules/Macros

  •    IIUBSORT
    

Fix information

  • Fixed component name

    IMS INDEX BUILD

  • Fixed component ID

    5655E2400

Applicable component levels

  • R210 PSY UQ56695

       UP01/08/07 P F108

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.

[{"Line of Business":{"code":null,"label":null},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX89M","label":"IMS Index Builder"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"210"}]

Document Information

Modified date:
03 October 2020