IBM Support

PH23110: ARSSOCKD ABENDS IF AN INDEX IS ADDED TO AN EXISTING NON-UTS TABLESPACE. ALSO, MAXPARTITIONS MAYBE CALCULATED INCORRECTLY.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • For an application group, if a new index field is added or if
    an existing filter field is changed to an index field ARSSOCKD
    will abend under the following two conditions:
    1) The existing tablespaces are non-UTS.
    2) ARSMVS_DB_DSSIZE=n in ars.cfg
    
    Also, its possible that the tablespace could be incorrectly
    created with 1 for MAXPARTITIONS. Note: This APAR will only
    specify the correct MAXPARTITONS for new table spaces. The
    arstblsp commmand can be used to close the existing table and
    cause a new tablespace. Alternatively, an ALTER TABLESPACE
    can be used to increase the MAXPARTITIONS.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Content Manager OnDemand for z/OS 10.1   *
    ****************************************************************
    * PROBLEM DESCRIPTION: Abend S0C9 in ARGSEG when adding an     *
    *                      index to an existing applgrp data       *
    *                      table. The applgrp data table will be   *
    *                      in a non-UTS tablespace created by      *
    *                      a CMOD at 9.0 or lower.                 *
    ****************************************************************
    ARGSEG has two space calculations for indexes, one for an index
    on tablespaces that dont specify MAXPARTITION (non-UTS) and
    one for an index tablespaces that specify MAXPARTITION. ARGSEG
    tried to use the MAXPARTITION calculation for tables created by
    CMOD 9.0 and below, leading to an ABEND S0C9.
    

Problem conclusion

  • ARGSEG is changed to use the correct calculation for the index
    for non-UTS table spaces.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH23110

  • Reported component name

    CM OD Z/OS, OD/

  • Reported component ID

    5655H3900

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-03-09

  • Closed date

    2020-08-12

  • Last modified date

    2020-09-01

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

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

    UI71038 UI71039

Modules/Macros

  • ARGSEG   ARNSEG
    

Fix information

  • Fixed component name

    CM OD Z/OS, OD/

  • Fixed component ID

    5655H3900

Applicable component levels

  • RA10 PSY UI71038

       UP20/08/17 P F008

  • RA50 PSY UI71039

       UP20/08/17 P F008

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":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSQHWE","label":"Content Manager OnDemand for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A10","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
02 September 2020