IBM Support

PI84087: DEPENDENCY CONFLICT RESULTS IN CREATING AN EMPTY BUILD LIFE

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

  • If there is a dependency relationship such as the following
scenario:

Process A depends on Process B (with status success, pull)
Process A also depends on Process C (with status success, stamp
X, pull)
Process B depends on Process C (with status success, stamp Y,
pull)
With a condition of X != Y (example, X="build-515" and Y="build
516")

Triggering a build of Process A will cause a conflict of Process
C between build life 515 and 516 because B and A are enforcing
conflicting requirements of Process C.
The resulting build life of Process A ends up without an end
date or status. The aftermath of this is not being able to
delete or deactivate this defunct build life of Process A due to
the fact that it does not have an end date or a completed
status.

Local fix

  • 



Problem summary


    

  • ****************************************************************
* USERS AFFECTED:                                              *
* UCB 6.1.2/6.1.3.0                                            *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* Dependency conflict results in creating an empty build life  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************

    



Problem conclusion


    

  • Fix is included in UCB 6.1.3.1, and cumulative patches
6.1.3.0-927370 (for UCB 6.1.3.0) and 6.1.2.4-929084 (for UCB
6.1.2.x)

    



Temporary fix


    

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    PI84087
    • 

  • Reported component name
    URBANCODE BUILD
    • 

  • Reported component ID
    5725P5700
    • 

  • Reported release
    613
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt / Xsystem
    • 

  • Submitted date
    2017-07-06
    • 

  • Closed date
    2017-10-11
    • 

  • Last modified date
    2017-10-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
    URBANCODE BUILD
    • 

  • Fixed component ID
    5725P5700
    • 



Applicable component levels


    

  • R612  PSN
       UP
    • 

  • R612  PSY
       UP
    • 

  • R613  PSN
       UP
    • 

  • R613  PSY
       UP
    • 








      
              
                            

              

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

                          

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            11 October 2017
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback