IBM Support

PI88865: COMPONENT PROCESS NEVER STARTS AFTER APPROVALS

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When running a component process directly from the components
tab of an application on an environment that requires approvals,
the component process will intermittently get stuck in the
"Waiting to start" state. An error will appear in the server
logs saying "User does not have read permission to a Component".

Local fix

  • Rerun the component process.

Problem summary

  • ****************************************************************
* USERS AFFECTED:                                              *
* All end users on all supported browsers.                     *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* When running a component process directly from the           *
* components                                                   *
* tab of an application on an environment that requires        *
* approvals,                                                   *
* the component process will intermittently get stuck in the   *
* "Waiting to start" state. An error will appear in the server *
* logs saying "User does not have read permission to a         *
* Component".                                                  *
****************************************************************
* RECOMMENDATION:                                              *
* Fixed in version 6.2.7.0                                     *
****************************************************************

Problem conclusion

  • Fix is provided in IBM UrbanCode Deploy 6.2.7.0

Temporary fix

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    PI88865
    • 

  • Reported component name
    UC DEPLOY
    • 

  • Reported component ID
    5725M5400
    • 

  • Reported release
    624
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt / Xsystem
    • 

  • Submitted date
    2017-10-13
    • 

  • Closed date
    2017-12-11
    • 

  • Last modified date
    2017-12-11
    • 





    

  • 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
    UC DEPLOY
    • 

  • Fixed component ID
    5725M5400
    • 



Applicable component levels


    

  • R600  PSN
       UP
    • 

  • R600  PSY
       UP
    • 

  • R601  PSN
       UP
    • 

  • R601  PSY
       UP
    • 

  • R610  PSN
       UP
    • 

  • R610  PSY
       UP
    • 

  • R611  PSN
       UP
    • 

  • R611  PSY
       UP
    • 

  • R612  PSN
       UP
    • 

  • R612  PSY
       UP
    • 

  • R613  PSN
       UP
    • 

  • R613  PSY
       UP
    • 

  • R620  PSN
       UP
    • 

  • R620  PSY
       UP
    • 

  • R621  PSN
       UP
    • 

  • R621  PSY
       UP
    • 

  • R622  PSN
       UP
    • 

  • R622  PSY
       UP
    • 

  • R623  PSN
       UP
    • 

  • R623  PSY
       UP
    • 

  • R624  PSN
       UP
    • 

  • R624  PSY
       UP
    • 

  • R625  PSN
       UP
    • 

  • R625  PSY
       UP
    • 








      
              
                            

              

              [{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS4GSP","label":"IBM UrbanCode Deploy"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"624","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
              

                          

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            11 December 2017
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback