PH14783: AUTO-RESOLVE NOT WORKING

APAR status

• Closed as program error.

Error description

• Background of the Issue:
  
  According to the client, when he is creating independent
  packages in the same model, the natural conflict is not able to
  be resolved by using the auto-resolve option. It used to work
  and continues to work in other components of the stream and in
  other streams.
  
  It is requiring a "manual" resolution but even that says that
  there are no conflicts. The customer has provided a document
  that describes the scenario.
  
  Please also note that they have mentioned that there were
  patches done for their implementation when they migrated from
  9.1.1 to 9.6.1 that involved compare merge plugins.
  
  Support Info :
  
  We have suggested for the customer to update to v9.6.1.3 since
  there have been some compare-merge defects resolved in that
  version. Also clarified the what is the repository system that
  they are using and what version.
  
  Once they have upgraded, we asked the client to check if the
  issue happened again and then from there, we'll do further
  checking.
  
  
  Customer's Response:
  
  Customer confirmed that they are using RTC 6.0.3 as their
  repository along with RSAD for WebSphere 9.6.1.
  
  He added that they are already looking into upgrading to 9.7 but
  there are still issues, like the swagger file capabilities.
  He assumed that all defect fixes noted for versions 9.6.1 will
  be included on the 9.7.
  
  The client replied that they do not have 9.6.1.3 but they have
  9.7.0. They tested different scenario using RSAD for WS 9.7 with
  RTC 6.0.3 and mentioned that they results were the same.
  
  Here are the summary of the tests they performed and I will just
  quote his reply,
  
  1). We forced a conflict in the API Management model in the
  RESTModels component of the REST interface modeling stream. It
  would not auto-resolve. I had to go to the compare/conflict
  editor which indicated 0 conflicts. I accepted all
  non-conflicting changes, saved and resolved as merged. All
  changes were merged correctly.
  
  2). We forced a conflict by working in the same diagram on
  different elements. The diagram was located in the EDB_IIB
  component also in the REST interface modeling stream.
  Auto-resolved worked correctly and both change sets were
  correctly merged.
  
  3). We forced conflict in a component of a different stream, by
  creating independent packages in the same object (this is
  similar to test 1 above). Auto-resolved again worked correctly
  and the changes were correctly merged.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * -                                                            *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Auto-resolve fails when duplicate dependency links are       *
  * present in the model.                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• Auto-resolve works fine even when duplicate dependency links are
  present in the model.
  This was done in 9.7.0.2
  

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

  SW ARCHITECT WI

• Fixed component ID

  5724I7001

Applicable component levels