PI99133: API GETENABLEDENTITYDEFS RETURNS NULL IF NO RESULTS ARE RETURNED, IT SHOULD RETURN AN EMPTY SET OF ENTITYDEFS INSTEAD

Rational ClearCase Fix Pack 4 (9.0.1.4) for 9.0.1
Rational ClearQuest Fix Pack 4 (9.0.1.4) for 9.0.1
Rational ClearQuest Fix Pack 5 (9.0.1.5) for 9.0.1
Rational ClearCase Fix Pack 5 (9.0.1.5) for 9.0.1
Rational ClearCase Fix Pack 6 (9.0.1.6) for 9.0.1
Rational ClearQuest Fix Pack 6 (9.0.1.6) for 9.0.1
Rational ClearQuest Fix Pack 7 (9.0.1.7) for 9.0.1
Rational ClearCase Fix Pack 7 (9.0.1.7) for 9.0.1
Rational ClearCase Fix Pack 8 (9.0.1.8) for 9.0.1
Rational ClearQuest Fix Pack 8 (9.0.1.8) for 9.0.1
Rational ClearQuest Fix Pack 9 (9.0.1.9) for 9.0.1
Rational ClearCase Fix Pack 9 (9.0.1.9) for 9.0.1
Rational ClearCase Fix Pack 10 (9.0.1.10) for 9.0.1
Rational ClearCase Fix Pack 11 (9.0.1.11) for 9.0.1
Rational ClearCase Fix Pack 12 (9.0.1.12) for 9.0.1
Rational ClearCase Fix Pack 13 (9.0.1.13) for 9.0.1

APAR status

• Closed as program error.

Error description

• If you use an ALIAS for a different user than the original owner
  of the database you will get the error below showing in a
  ClearQuest Web tracing:
  
  API GetEnabledEntityDefs returns null if no results are
  returned, it should return an empty set of EntityDefs instead
  
  
  Steps to Reproduce the behavior:
  
  1. Create 2 DB2 databases using a database owner like for
  example "userA" (on DB2ADMNS group).
  
  2. Create the Schema Repository connection and update the
  database properties on ClearQuest Maintenance Tool and
  ClearQuest Designer to connect with "userA" that is the database
  owner for those databases.
  
  3. ClearQuest Web will work without any issues.
  
  3. Create a new user "userB" and add it to the DB2ADMNS group.
  
  4. Run a script to create an User Alias for the "userB" in the
  User Database tables.
  
  5. Change the User Database properties to use "userB" instead of
  "userA".
  
  Note: Probably you will see an error in regarding user
  permissions to update tables. Running the "db2 grant dataaccess
  on database to user <userB>" command, should resolve this
  permission issue and you are able to update the User Database
  properties to user "userB".
  
  6. Now, when using ClearQuest Web you will start to see the
  error when tracing ClearQuest Web and the ClearQuest will became
  slow, unresponsive and throwing errors (Eg.: when running a
  query, open a record, trying to submit a new record).
  
  Note: The issue with the API only becomes significant because of
  a table ownership issue which causes problems loading metadata.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * ClearQuest API                                               *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * The ClearQuest API GetEnabledEntityDefs can return a null    *
  * value if there are no entity defs selected by the call.  It  *
  * should return an empty set of entitydefs instead.  This can  *
  * cause performance and other problems for consumers of the    *
  * API such as CQ Web, especially if the ClearQuest database    *
  * table ownership was not configured correctly.                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• A fix is available in ClearQuest 9.0.1.4
  The ClearQuest API GetEnabledEntityDefs now returns an empty set
  of entitydefs in all cases when there are no entitydefs returned
  by the call.
  

Temporary fix

Comments

APAR Information

• 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

  CLEARQUEST WIN

• Fixed component ID

  5724G3600

Applicable component levels

• R901 PSY

     UP