IBM Support

PM55686: using getProperties perm with -caching switch leaves invalid file lock in place

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • If you launch a client using the '-caching' command line switch,
    then run the getProperties() perm, a file lock will remain on
    the relevant module_attribute.dt file until you perform some
    other action (it seems almost any action involving DB
    communication).
    
    While the lock is in place other users will not be able to save
    the module, getting errors such as 'error reading/writing'
    though the exact error can vary.
    
    To recreate:
    
     - login using the '-caching' command line switch
     - run code such as the following, ensuring that the module
    name/path given is valid:
    
    '
    ModuleProperties mp
    ModuleVersion mv
    
    string mname = '/New Project/New Module'
    string s
    mv  = moduleVersion(module mname)
    
    print getProperties (mv, mp)
    
    
    for s in mp do {
    
     print s '\n'
    }
    
    AttrType at
    for at in mp do {
    
     print at.name '\n'
    }
    '
    
     - now run dbadmin listing locks e.g. using a command such as
    'dbadmin -data 36677@localhost -locklist'
     - observe a persistent lock on module_attributes.dt
    
    This was introduced between 9.1.0.3 and 9.2.0.1, assuming the
    server version isn't relevant.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If you launch a client using the "-caching" command line
    switch, then run the getProperties() perm, a file lock will
    remain on the relevant module_attribute.dt file until you
    perform some other action (it seems almost any action
    involving DB communication).
    

Problem conclusion

  • The code has been changed so that the file lock no longer
    remains longer than necessary.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM55686

  • Reported component name

    TLOGIC DOORS

  • Reported component ID

    5724V61DR

  • Reported release

    920

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-01-10

  • Closed date

    2012-09-05

  • Last modified date

    2012-09-05

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

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

Fix information

  • Fixed component name

    TLOGIC DOORS

  • Fixed component ID

    5724V61DR

Applicable component levels

  • R920 PSN

       UP



Document information

More support for: Rational DOORS

Software version: 9.2

Reference #: PM55686

Modified date: 05 September 2012