IBM Support

PH30893: AFTER APAR PH05668 JOBS APPEAR IN MVS_ADDRSPACE_T TWICE. 1 WITH MVS_SYSTEM_ID FOR SYSTEM JOB RAN ON, 1 SYSTEM THAT PURGED JOB.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as unreproducible in next release.

Error description

  • AFTER APAR PH05668 JOBS APPEAR IN MVS_ADDRSPACE_T TWICE. ONE
    WITH MVS_SYSTEM_ID FOR SYSTEM JOB RAN ON, AND ONE WITH SYSTEM
    THAT PURGED JOB.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: IBM Z Decision Support or                    *
    *                 IBM Z Performance and Capacity Analytics     *
    *                 customers collecting data into the           *
    *                 MVS_ADDRSPACE_T Db2 table.                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: Multiple rows are stored in the Db2     *
    *                      table MVS_ADDRSPACE_T for a single      *
    *                      transaction when the MVS_SYSTEM_ID in   *
    *                      the SMF_06 and/or SMF_26 are different  *
    *                      to the MVS_SYSTEM_ID in the SMF_030.    *
    ****************************************************************
    * RECOMMENDATION: Apply the provided PTF(s).                   *
    ****************************************************************
    The MVS_SYSTEM_ID was added as a key field in the
    MVS_ADDRSPACE_T table to enable the table to be partitioned
    on the MVS_SYSTEM_ID. This resulted in additional rows being
    created in the table when the MVS_SYSTEM_ID in the SMF_06 or
    SMF_26 records did not match the MVS_SYSTEM_ID in the
    SMF_030 record with the same JOB_TIMESTAMP, JOB_NAME,
    and JOB_NUMBER.
    

Problem conclusion

Temporary fix

Comments

  • A view MVS_ADDRSPACE_TV based on the MVS_ADDRSPACE_T is created
    to combine the rows that have the same JOB_TIMESTAMP, JOB_NAME,
    and JOB_NUMBER but a different MVS_SYSTEM_ID. This gives the
    customer a view of the data as it was prior to the addition of
    the MVS_SYSTEM_ID to the key of the table.
    

APAR Information

  • APAR number

    PH30893

  • Reported component name

    TDS FOR Z/OS

  • Reported component ID

    569510100

  • Reported release

    901

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-10-26

  • Closed date

    2021-04-21

  • Last modified date

    2021-05-03

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

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

    UI75039 UI75040 UI75041

Modules/Macros

  • DRLIMVS  DRLJMTVK DRLTMVAS
    

Fix information

  • Fixed component name

    TDS FOR Z/OS

  • Fixed component ID

    569510100

Applicable component levels

  • R9A0 PSY UI75041

       UP21/04/28 P F104

  • RC01 PSY UI75039

       UP21/04/28 P F104

  • RCA0 PSY UI75040

       UP21/04/28 P F104

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":"LOB35","label":"Mainframe SW"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SS2DUM","label":"IBM Z Decision Support"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"901"}]

Document Information

Modified date:
04 May 2021