PI12988: TRYING TO IMPORT/EXPORT AN APPLICATION WITH A RESOURCE TAG RESULTS IN AN ERROR

IBM UrbanCode Deploy Fix Pack 4 (6.0.1.4) for 6.0.1
IBM UrbanCode Deploy Interim Fix 1 for 6.0.1.4
IBM UrbanCode Deploy Fix Pack 5 (6.0.1.5) for 6.0.1
IBM UrbanCode Deploy Fix Pack 6 (6.0.1.6) for 6.0.1
IBM UrbanCode Deploy Fix Pack 7 (6.0.1.7) for 6.0.1
IBM UrbanCode Deploy Fix Pack 8 (6.0.1.8) for 6.0.1
IBM UrbanCode Deploy Fix Pack 9 (6.0.1.9) for 6.0.1
IBM UrbanCode Deploy Fix Pack 10 (6.0.1.10) for 6.0.1
IBM UrbanCode Deploy Fix Pack 11 (6.0.1.11) for 6.0.1
IBM UrbanCode Deploy Fix Pack 12 (6.0.1.12) for 6.0.1
IBM UrbanCode Deploy iFix 1 for 6.0.1.9

APAR status

• Closed as program error.

Error description

• To recreate:
  
  1. Make sure you have an application and environment with a
  resource in it.
  2. Create a tag on the resource.
  3. Create a component and a component process
  4. Call the component process from the application process and
  set the tag using "limits to tags".
  5. Export the application.
  6. Import the application to another server which doesn't have
  the resource tag defined.
  
  RESULT:
  
  You can't import the application.  It complains that the tag
  does not exist.
  
  7. On any resource in the target server, assign the same
  resource tag.  Try the import again.  It should pass import.
  8. Try to export the application from the target server.
  
  RESULT:
  
  You get the following kind of error:
  
  No tag exists with ID 31d67d0b-7392-4fa6-9550-898b3b18fabd.
  

Local fix

• There is no known workaround at this time.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Any                                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Steps to reproduce:                                          *
  *                                                              *
  *                                                              *
  * 1. Make sure you have an application and environment with a  *
  * resource in it.                                              *
  * 2. Create a tag on the resource.                             *
  * 3. Create a component and a component process                *
  * 4. Call the component process from the application process   *
  * and                                                          *
  * set the tag using "limits to tags".                          *
  * 5. Export the application.                                   *
  * 6. Import the application to another server which doesn't    *
  * have                                                         *
  * the resource tag defined.                                    *
  *                                                              *
  * RESULT:                                                      *
  *                                                              *
  * You can't import the application.  It complains that the tag *
  * does not exist.                                              *
  *                                                              *
  * 7. On any resource in the target server, assign the same     *
  * resource tag.  Try the import again.  It should pass import. *
  * 8. Try to export the application from the target server.     *
  *                                                              *
  * RESULT:                                                      *
  *                                                              *
  * You get the following kind of error:                         *
  *                                                              *
  * No tag exists with ID 31d67d0b-7392-4fa6-9550-898b3b18fabd.  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• Fixed in 6.0.1.4
  

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

  UC DEPLOY

• Fixed component ID

  5725M5400

Applicable component levels

• R600 PSN

     UP

• R600 PSY

     UP

• R601 PSN

     UP

• R601 PSY

     UP