IBM Support

PI70498: REPLICATION LOGGING ONE VSAM SPHERE FOR MULTIPLE NON-CICS ADDRESS SPACES

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as unreproducible in next release.

Error description

  • When a long-running address space opens a VSAM cluster,
    performs some updates and then closes the VSAM cluster
    another non-CICS address space may open the same VSAM cluster.
    However, if this VSAM cluster is defined for replication logging
    the logging fails with DWW252I with return code 24 and reason
    code 717053CB and DWW280I with return code 8 and reason
    code 71725319.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: This APAR affects CICS VR 5.1 and 5.2 users  *
    *                 that exploit VSAM replication logging.       *
    ****************************************************************
    * PROBLEM DESCRIPTION: Currently replication logging for a     *
    *                      VSAM sphere is not supported            *
    *                      simultaneously from multiple non-CICS   *
    *                      address spaces.                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    This APAR provides an enhancement for VSAM batch replication
    logging:
    If a VSAM sphere is defined for VSAM batch replication logging
    only (without forward recovery or batch backout logging,i.e. as
    LOGREPLICATE,FRLOG(NONE)), CICS VR will disconnect the sphere
    from the replication log at VSAM CLOSE operations, not at end
    of job step. This allows a second job to perform replication
    logging once the first job has completed the CLOSE even though
    the first job has not yet completed. It is still the case that
    only one job at a time can have the file open with replication
    logging active.
    In this scenario, the logstream contains only replication log
    records for use by the IIDR for VSAM for z/OS product. It
    cannot be used by CICS VR forward recovery and batch backout
    utilities.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PI70498

  • Reported component name

    CICS VSAM RECOV

  • Reported component ID

    5655Y2400

  • Reported release

    510

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-10-11

  • Closed date

    2016-11-21

  • Last modified date

    2016-12-01

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

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

    UI42778 UI42779

Modules/Macros

  • DWWBLOPC DWWBLVBB DWWBLVBL DWW1RMAT DWW1SEOX DWW1SVER DWW3GCLO
    DWW3GCON DWW3GLOG DWW3GMAT DWW3GSDC HCCV510J HCCV520J
    

Fix information

  • Fixed component name

    CICS VSAM RECOV

  • Fixed component ID

    5655Y2400

Applicable component levels

  • R510 PSY UI42778

       UP16/11/24 P F611

  • R520 PSY UI42779

       UP16/11/24 P F611

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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSQJMU","label":"CICS VSAM Recovery for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 December 2016