IBM Support

PI92166: IBM RATIONAL DEVELOPER FOR Z SYSTEMS (RDZ/IDZ) USING REFRESH KEY ON THE CARMA ENDEVOR SEARCH VIEW MAY FAIL

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • IBM Rational Developer for System z - RDz - v9.1.1.5
    IBM Developer for z Systems - IDz - v14
    
    Using the refresh key multiple times on the CARMA Endevor Search
    View may fail with this error:
    !ENTRY com.ibm.ca.endevor.packages
    !MESSAGE CRRZC2122E Could not execute Custom Command:
    CRRZC2200E An error was received from the CARMA Host[zOS host]
    [500] 500: RETURN CODE: 0020 REASON CODE: 0033 ERROR MESSAGE:
    
    Steps to recreate:
    Connect to the zOS host
    Connect to the CARMA server
    Perfrom an Endevor Search for checked out Members
    In the Search View, refresh 4 or 5 times.
    
    The error below will appear in the user's RSECOMM.log:
    INFO: com.ibm.carma.rse.server.transport.command.
               CustomActionCommand: Processing CARMA Response Body
    INFO: com.ibm.carma.rse.server.transport.command.
      CustomActionCommand: Completed processing CARMA Response Body
    ERROR: com.ibm.carma.rse.server.miners.CARMAMiner:
                      CARMA error occured during command processing
    ERROR: com.ibm.carma.rse.server.transport.
      CARMACommandBase.processCARMAError(CARMACommandBase.java:296)
    ERROR: com.ibm.carma.rse.server.transport.CARMACommandBase.
                       readCARMAResponse(CARMACommandBase.java:287)
    ERROR: com.ibm.carma.rse.server.transport.CARMACommandBase.
                                 execute(CARMACommandBase.java:159)
    ERROR: com.ibm.carma.rse.server.miners.CARMAConnectionManager.
              executeCommandNoRetry(CARMAConnectionManager.java:276)
    ERROR: com.ibm.carma.rse.server.miners.CARMAConnectionManager.
                     executeCommand(CARMAConnectionManager.java:240)
    ERROR: com.ibm.carma.rse.server.miners.CARMAMiner.
                             handleCARMACommand(CARMAMiner.java:310)
    ERROR: com.ibm.carma.rse.server.miners.CARMAMiner.
                                   handleCommand(CARMAMiner.java:94)
    ERROR: org.eclipse.dstore.core.miners.Miner.command
                                                    (Miner.java:336)
    ERROR: org.eclipse.dstore.core.miners.Miner.handle
                                                    (Miner.java:244)
    ERROR: org.eclipse.dstore.core.model.Handler.run
                                                  (Handler.java:135)
    
    INFO: com.ibm.carma.rse.server.miners.CARMAMiner:
              Setting Return Status [C_PERFORM_ACTION]: DataElement
    {
        Type:    status
        Name:    done
        Value:    error
        ID:    1729325722status
        Source:    500|500: RETURN CODE: 0020
         REASON CODE: 0033 ERROR MESSAGE:
        Depth:    1
        isSpirit:    false
        DataStore:    server_host
    }
    

Local fix

  • Disconnect from the CARMA Server/ reconnect and perform a new
    search
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: 01.RDz users who access the CA Endevor       *
    *                    repository using the IBM supplied RDz     *
    *                    Endevor RAM.                              *
    *                 02.RDz users who access the CA Endevor       *
    *                    repository using the IBM supplied RDz     *
    *                    Endevor RAM.                              *
    *                 03.RDz users who access the CA Endevor       *
    *                    repository using the IBM supplied RDz     *
    *                    Endevor RAM.                              *
    *                 04.RDz users who access the CA Endevor       *
    *                    repository using the IBM supplied RDz     *
    *                    Endevor RAM.                              *
    *                 05.RDz users who access the CA Endevor       *
    *                    repository using the IBM supplied RDz     *
    *                    Endevor RAM.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: 01.Using the refresh key multiple       *
    *                         times on the CARMA Endevor Search    *
    *                         results in an error dialog being     *
    *                         shown stating that the request has   *
    *                         failed.                              *
    *                      02.In Rational Developer for z Systems  *
    *                         (RDz) v9.5.1.4, in a z/OS project    *
    *                         that is associated with a CARMA      *
    *                         repository, some members lose their  *
    *                         association with the CARMA           *
    *                         repository after restarting RDz.     *
    *                      03.There were several Endevor API       *
    *                         errors issued while retrieving       *
    *                         number of dependencies from element  *
    *                         component list. This causes          *
    *                         dependency list processing to fail   *
    *                         leading to return code 4038.         *
    *                      04.When performing a "View Cast         *
    *                         Report" action (LIST PACKAGE CAST    *
    *                         REPORT), CARMA is not properly       *
    *                         handling blank spaces within         *
    *                         package ID name.                     *
    *                      05.When in the CARMA orpositories and   *
    *                         Search Results view, if multiple     *
    *                         element are selected, and a custom   *
    *                         action is performed on the selected  *
    *                         elements, only the fist element is   *
    *                         processed by the action.             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    01.When invoking the search request, if the storage area used
       for the response is not initialized, this may cause errors
       when processing the request. The subsequent requests may
       fail as a result.
    02.When the repository association is changed at the subproject
       level, the child processes also lose the association. In
       some cases,this may happen when the member got moved in the
       repository.
    03.When invoking the search request, if the storage area used
       for the response is not initialized, this may cause errors
       when processing the request. The subsequent requests may
       fail as a result.
    04.When processing the search request, if the package name has
       embedded blanks, the name is truncated to first part of the
       name up to the first space. This causes the package not to
       be located.
    05.When selecting multiple elements, only the first element is
       processed for custom actions.
    

Problem conclusion

  • 01.The IBM IDz Endevor integration has been changed to
       initialize the response area prior to each request.
    02.The IBM IDz Endevor integration has been changed to allow
       the elements to re-associate with the repository.
    03.The IBM IDz Endevor integration has been changed to
       initialize the response area prior to each request.
    04.The IBM IDz Endevor integration has been changed to properly
       handle package names with embedded blanks.
    05.The IBM IDz Endevor integration has been changed to properly
       handle multiple element selections for custom actions.
    

Temporary fix

Comments

  • ×**** PE18/05/16 PTF IN ERROR. SEE APAR PI98018  FOR DESCRIPTION
    

APAR Information

  • APAR number

    PI92166

  • Reported component name

    ID/Z HOST

  • Reported component ID

    5724T0723

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-01-08

  • Closed date

    2018-05-11

  • Last modified date

    2018-05-16

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

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

Modules/Macros

  • CRARNDVR CRARPKGS
    

Fix information

  • Fixed component name

    ID/Z HOST

  • Fixed component ID

    5724T0723

Applicable component levels

  • R910 PSY UI55786

       UP18/05/16 I 1000

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.



Document information

More support for: Rational Developer for System z

Software version: 9.1

Reference #: PI92166

Modified date: 16 May 2018