IBM Support

OA58430: IGW031I PDSE ++ LOCK LOCAL DIRECTORY SHARED CONTENTION THAT REMAINS OUTSTANDING ACROSS MULTIPLE PDSE/PDSE1 MONITOR INTERVALS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • PDSE data set lock contention, as reported in IGW031I messages,
    that displays the same data set lock being held across multiple
    SMSPDSE or SMSPDSE1 monitor intervals. Sample message:
    IGW031I PDSE ANALYSIS  Start of Report(SMSPDSE1)
    ---------data set name---------------------- -----vsgt-------
    ............................................ 01-XYZ123-004517
    <<< multiple message lines omitted for clarity >>>
    
    ++ Lock LOCAL DIRECTORY SHARED
       held for at least 99.75 Minutes
       Hl1b:7DBFE5F0 HOLDER(0AAA:07F88888)
       Holding Job:HOLDJOB
    
    Note that the data set name is not resolved which is an
    indication that initial PDSE connect processing is being being
    performed. This is an important consideration for this issue.
    
    In this situation the output from a D GRS,C,E will display the
    following:
    ISG343I 11.17.30 GRS STATUS 873
    
    S=SYSTEMS SYSZIGW0  XYZ123 á I
    
    SYSNAME        JOBNAME         ASID     TCBADDR   EXC/SHR
    STATUS
    SYSTEM1     SMSPDSE1           0009       007FEE88 EXCLUSIVE
    OWN
    SYSTEM2     SMSPDSE1           0009       007FEE88   SHARE
    WAIT
    SYSTEM3     SMSPDSE1           0009       007FEE88   SHARE
    WAIT
    SYSTEM4     SMSPDSE1           0009       007FEE88   SHARE
    WAIT
    NO REQUESTS PENDING FOR ISGLOCK STRUCTURE
    
    where " XYZ123 á" is an EBCDIC representation of the VSGT field
    from the IGW031I message.
     XYZ123
    0EEEFFF041
    1789123057
    
    
    
    ANALYSIS:
    Identifying the PDSE from the VSGT in IGW031I message.
    
    1) obtain a dump of the SMSPDSE1 address space on the LPAR that
    holds the exclusive ENQ.
    
    2) issue the following IPCS command against the dump:
    
    IP VERBX IGWFPMAN 'F(HL1BSUMM) COMP(CLM) JOBNAME(SMSPDSE1)'
    
    and search the resulting report for the the VSGT as seen in the
    IGW031I message. This will position you to a point where the
    next "DataSetName:" field will identify the PDSE data set.
    
    KNOWN IMPACT:
    The PDSE data set represented by the VSGT in the IGW031I message
    cannot be accessed for READ (INPUT) or WRITE (OUTPUT) access.
    

Local fix

  • RECOVERY ACTION:
    Restart the SMSPDSE1 address space that holds the exclusive
    enqueue.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All PDSE users.                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Opening a PDSE member for UPDATE while                       *
    * the PDSE is open on another member in                        *
    * the sysplex may put the PDSE in an                           *
    * inconsistent lock state on the system                        *
    * where the UPDATE request was rejected.                       *
    * This can result in the inability for                         *
    * other sysplex members to read from the                       *
    * PDSE for while the inconsistency                             *
    * exists.                                                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    See DESCRIPTION.
    

Problem conclusion

  • Resolved the lock state inconsistency when processing the logic
    for locking a PDSE member for UPDATE access.
     KEYWORDS: PDSE/K
    

Temporary fix

  • *********
    * HIPER *
    *********
    FOR V2R2, APPLY AA58430
    FOR V2R3, APPLY BA58430
    FOR V2R4, APPLY CA58430
    

Comments

APAR Information

  • APAR number

    OA58430

  • Reported component name

    EXTENDED DATA S

  • Reported component ID

    5695DF115

  • Reported release

    230

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-10-03

  • Closed date

    2019-11-05

  • Last modified date

    2020-01-03

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

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

    UJ01266 UJ01275 UJ01290

Modules/Macros

  • IGWLGRP0
    

Fix information

  • Fixed component name

    EXTENDED DATA S

  • Fixed component ID

    5695DF115

Applicable component levels

  • R240 PSY UJ01275

       UP19/12/10 P F912 ¢

  • R230 PSY UJ01266

       UP19/12/10 P F912 ¢

  • R220 PSY UJ01290

       UP19/12/10 P F912 ¢

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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"230","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
03 January 2020