IBM Support

PM63362: Execution time taken to set access rights to views via set() access DXL perm will not be proportionate to the number of views

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Execution time taken to set access rights to views via set()
    access DXL perm will not be proportionate to the number of
    views.
    
    Steps to reproduce
    ------------------
    
    1. Create three new modules named A50, A150, and A600 for
    reference.
    
    2. Use a simple DXL and create 50, 150, and 600 views in the
    above modules (according to their names).
    
    3. Run the following script (before running the script replace
    the groupname with any actual group's name in the DOORS DB) on
    each of the above modules.
    
    ********************************
    Module m = current
    ModName_ md = module(fullName(m))
    string vName
    View v
    int nCnt = 0
    int nTimeSet = 0
    int n3
    Permission ps = read|create|modify|delete|control
    string sAdminGroupName = 'group name'   //use a name of an
    existing group
    
    int n1 = getTickCount_()
    for vName in views m do
    {
     v = view(vName)
     if (!canControl(md, v))
      continue
     v = view(vName)
     n3 = getTickCount_()
     set(v, ps, sAdminGroupName)
     nTimeSet += (getTickCount_()-n3)
     nCnt++
    }
    int n2 = getTickCount_()
    print nCnt '\t' (n2-n1) '\t' nTimeSet '\n'
    **********************************
    
    Though Views in the these modules are in a ratio of 1:3:12, the
    execution times of the above scripts will not be proportional to
    the number of views.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Customer DXL code is taking longer as the number of views
    increases;  but not in a direct ratio to the number of
    views.
    

Problem conclusion

  • The DXL code loops through every view in the module, and
    then the internal function (called from that inner loop)
    loops through every view again. So the time take increases
    in a non-linear fashion.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM63362

  • Reported component name

    TLOGIC DOORS

  • Reported component ID

    5724V61DR

  • Reported release

    930

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-04-26

  • Closed date

    2013-03-18

  • Last modified date

    2013-03-18

  • 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

  • R930 PSN

       UP



Document information

More support for: Rational DOORS

Software version: 9.3

Reference #: PM63362

Modified date: 18 March 2013