IBM Support

PM49696: using specific() perm on object without access to modify parent produces save error

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • If you have parent and child objects, and a user has admin
    access to the child, but only read access to the parent, if the
    user uses the specific() perm on the child object, then saves
    the module, an error will be given stating:
    
    '
    error is reading/writing ?module name?
    Unable to save the module - data structure is incorrect.
    
    Please manually copy or export and data you require and discard
    changes in the module.
    consult you system administrator
    '
    
    To recreate:
    
     - setup a parent and child object
     - assign read-only access for a user to the parent
     - assign full admin access for a user to the child
     - open the module as the user in exclusive edit mode and run
    the following DXL (assumes the child has absolute number 2)
    
    '
    Module m = current
    Object o = object 2
    
    specific (o)
    save m
    '
    
    Workaround:
    
     - use the isAccessInherited() perm to determine if there is
    actually any point in using the specific() perm, where access is
    not inherited there is no point.
    
    
    Introduced in either 9.3.0.0 or 9.3.0.1
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    On using the perm specific() for child object on which user
    has admin access but only read access on parent, DOORS was
    displaying error message that was not clear to user.
    

Problem conclusion

  • The code has been changed so that the error no longer
    appears in this scenario
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM49696

  • Reported component name

    TLOGIC DOORS

  • Reported component ID

    5724V61DR

  • Reported release

    920

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-10-10

  • Closed date

    2012-06-06

  • Last modified date

    2012-06-06

  • 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 #: PM49696

Modified date: 06 June 2012