PM96550: Rational Developer for System z 9.0 CARMA Endevor ADD ELEMENT UI takes minutes to display after 'Add to Endevor' request

Rational Developer for System z 9.0.1
Rational Developer for System z Fix Pack 1 (9.0.1.1) for 9.0.1
Rational Developer for System z Fix Pack 2 (9.0.1.2) for 9.0.1
Rational Developer for System z Interim Fix 1 for 9.0.1.2
Rational Developer for System z Interim Fix 3 for 9.0.1.2 - IBM Java Platform Standard Edition 7 SR6 FP1 iFixes (IX90136+IX90137+IV39749)
Rational Developer for System z Fix Pack 3 (9.0.1.3) for 9.0.1
Rational Developer for System z Interim Fix 1 for 9.0.1.3
Rational Developer for System z Fix Pack 4 (9.0.1.4) for 9.0.1
Rational Developer for System z Interim Fix 1 for 9.0.1.4
Rational Developer for System z Interim Fix 2 for 9.0.1.4
Rational Developer for System z Interim Fix 3 for 9.0.1.4
Rational Developer for System z Fix Pack 5 (9.0.1.5) for 9.0.1
Rational Developer for System z Fix Pack 6 (9.0.1.6) for 9.0.1
Rational Developer for System z Interim Fix 1 for 9.0.1.6
Rational Developer for System z Interim Fix 2 for 9.0.1.2
Rational Developer for System z Fix Pack 7 (9.0.1.7) for 9.0.1

APAR status

• Closed as program error.

Error description

• Rational Developer for System z 9.0 - RDz - CARMA Endevor ADD
  ELEMENT User Interface screen takes minutes to display following
  'Add to Endevor' request.
  
  With the RDz v9 client, you can ADD an ELEMENT to Endevor from
  Remote Systems view by right-clicking on .cbl/.pli file
  (program/element) and select 'Add to Endevor' from the context
  menu.  The first time this is done following host/CARMA
  connection, the ADD Element UI screen can take several minutes
  to be displayed.  This response time is related to the number of
  Processor Groups defined in your Endevor environment.  The LIST
  PROCESSOR GROUP Endevor API call below took almost 8 minutes to
  complete due to the number of Processor Groups defined and this
  call needs to complete before ADD Element UI screen is
  displayed.  Subsequent 'ADD' requests done during the same CARMA
  connection, perform very fast (LIST PROCESSOR GROUP call is not
  performed).
  
  07:01:54  API0101I  BEGINNING OF API ACTION PROCESSING
            API0100I  LIST PROCESSOR GROUP
            API0100I     TO DDNAME: EXT1ELM
            API0100I     MESSAGE DDNAME: MSG3FILE
            API0100I     ENVIRONMENT: *
            API0100I     STAGE ID: *
            API0100I     SYSTEM: *
            API0100I     TYPE: *
            API0100I     PROC GROUP: *
            API0100I     OPTIONS
            API0100I             PATH: P  RETURN: A  SEARCH: N
            API0100I
            API0100I  API ACTION REQUEST DATA SUCCESSFULLY PRINTED
            API0100I
  07:01:54  API0102I  DISPATCHING API ACTION
  07:09:33  API0000I  RETURNED COUNT=00410390, SELECTED
  COUNT=00410390
  07:09:33  API0000I  PROCESSING COMPLETE - RC=00000 REASON=00000
  
  Local Fix:
  
  You should be able to improve the performance on your 'ADD'
  requests by doing a 'Custom - Add Element' request from CARMA
  Repositories view.  To limit the number of records returned by
  Endevor on the LIST PROCESSOR GROUP call, expand the Endevor ENV
  tree all the way down to the 'TYPE' (COBOL/PLI/...) container
  where you want to add element.  Right-click on 'TYPE' container
  and select Custom - Add Element from context menu.
  

Local fix

Problem summary

• The list of processor groups was always being obtained using
  wildcard characters for the Environment, System and Type
  identifiers.  This approach caused the server code to always
  return the complete list of processor groups.  If the complete
  list included a large number of items, then it took several
  minutes for the request to complete.
  

Problem conclusion

• The logic was modified to only request a list of processor
  groups if the Environment, System and Type information is known.
  This approach will significantly reduce the number of processor
  groups returned and cached on the client for a particular
  request.
  
  The problem listed in this APAR has been resolved with
  IBM Rational Developer for System z V9.0.1 Refresh Pack which
  is available from the Recommended Fixes support download page:
  http://www-1.ibm.com/support/docview.wss?rs=2294&uid=swg27006335
  

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

  RATL DEV FOR SY

• Fixed component ID

  5724T0700

Applicable component levels

• R901 PSY

     UP