IBM Support

OA54048: ABEND0C1 IGG019V8 WHEN USING ZEDC COMPRESSION SERVICES. RENDEZVOUS TOKEN WAS PREMATURELY CLEARED BY ZOS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The zEDC rendezvous token can be prematurely cleared in a
    multi step job where the CMRO task ends.  This will result
    in abend0C1 and the inability to continue using
    zEDC services.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users at HBB7790 and above using zEDC                        *
    * compression/decompression services.                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * zEDC normal task termination could                           *
    * delete an active Rendezvous token                            *
    * and LatchSetToken under another task                         *
    * when cleaning up the token and storage                       *
    * areas. This could result in an:                              *
    *  - ABEND0C1 when attempting to                               *
    *    use the RZVToken that was deleted                         *
    *    prematurely                                               *
    *  - Or, cause a hang in compression                           *
    *    processing when the LatchSetToken                         *
    *    is deleted prematurely.                                   *
    * (ZEDC/K)                                                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    zEDC normal task termination could delete an active Rendezvous
    token (RZVToken) that is active under another task when
    cleaning up the finished task.  This could result in an
    ABEND0C1 when attempting to use the RZVToken that was deleted
    prematurely.
    

Problem conclusion

  • zEDC task termination processing has been enhanced to only
    delete RZVTokens that are associated with the task being
    terminated.
    
     *******************************************************
     *                                                     *
     * Title: MVS Programming: Callable Services for       *
     *        High-Level Languages (SA23-1377-xx)          *
     *                                                     *
     *******************************************************
     ...
       FPZ4RZV:
        +----------------------------------------------------+
        | Table 34. Return and reason codes for the FPZ4RZV  |
        |           service                                  |
        +---------+----------+-------------------------------+
        |         |          |                               |
        | Hex RC  | Rsn Code | Meaning and action            |
        +---------+----------+-------------------------------+
        | ...     | ...      | ...                           |
        +---------+----------+-------------------------------+
     |  |         |          |                               |
     |  | 10      | 030C     | Too many latch sets requested |
     |  |         |          |                               |
        +---------+----------+-------------------------------+
        ....
    
       FPZ4RMR:
        +----------------------------------------------------+
        | Table 40. Return and reason codes for the FPZ4RMR  |
        |           service                                  |
        +---------+----------+-------------------------------+
        |         |          |                               |
        | Hex RC  | Rsn Code | Meaning and action            |
        +---------+----------+-------------------------------+
        | ...     | ...      | ...                           |
        +---------+----------+-------------------------------+
     |  |         |          |                               |
     |  | 10      | 030D     | Missing LatchSet Token        |
     |  |         |          |                               |
        +---------+----------+-------------------------------+
        ....
    
    
       FPZ4DMR:
        +----------------------------------------------------+
        | Table 43. Return and reason codes for the FPZ4DMR  |
        |           service                                  |
        +---------+----------+-------------------------------+
        |         |          |                               |
        | Hex RC  | Rsn Code | Meaning and action            |
        +---------+----------+-------------------------------+
        | ...     | ...      | ...                           |
        +---------+----------+-------------------------------+
        ....
       FPZ4ABC:
        +----------------------------------------------------+
        | Table 48. Return and reason codes for the FPZ4ABC  |
        |           service                                  |
        +---------+----------+-------------------------------+
        |         |          |                               |
        | Hex RC  | Rsn Code | Meaning and action            |
        +---------+----------+-------------------------------+
        | ...     | ...      | ...                           |
        +---------+----------+-------------------------------+
     |  |         |          |                               |
     |  | 10      | 030D     | Missing LatchSet Token        |
     |  |         |          |                               |
        +---------+----------+-------------------------------+
        ....
    
       FPZ4URZ:
        +----------------------------------------------------+
        | Table 51. Return and reason codes for the FPZ4URZ  |
        |           service                                  |
        +---------+----------+-------------------------------+
        |         |          |                               |
        | Hex RC  | Rsn Code | Meaning and action            |
        +---------+----------+-------------------------------+
        | ...     | ...      | ...                           |
        +---------+----------+-------------------------------+
        ...
     KEYWORDS: ZEDC/K
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

  • ×**** PE22/07/20 FIX IN ERROR. SEE APAR OA63554  FOR DESCRIPTION
    

APAR Information

  • APAR number

    OA54048

  • Reported component name

    PCIE SERVICES

  • Reported component ID

    5752SCIQP

  • Reported release

    790

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-09-28

  • Closed date

    2021-12-16

  • Last modified date

    2022-10-14

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

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

    UJ07431 UJ07432 UJ07433 UJ07434 UJ07435

Modules/Macros

  • FPZPRDMR FPZPRRMR FPZRATTM FPZPRABC FPZPRRZV FPZPRMBC FPZPRURZ
    

Publications Referenced
SA23137700    

Fix information

  • Fixed component name

    PCIE SERVICES

  • Fixed component ID

    5752SCIQP

Applicable component levels

  • R790 PSY UJ07435

       UP22/01/06 P F201 ¢

  • R7A0 PSY UJ07434

       UP21/12/29 P F112 ¢

  • R7D0 PSY UJ07433

       UP21/12/29 P F112 ¢

  • R7C0 PSY UJ07432

       UP21/12/29 P F112 ¢

  • R7B0 PSY UJ07431

       UP21/12/29 P F112 ¢

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":"BU011","label":"Systems - zSystems software"},"Product":{"code":"SG19O"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"790"}]

Document Information

Modified date:
14 October 2022