PH21577: There is inconsistent behavior between deploying z/OS Connect EE .aar or .ara files and .sar files in an HA environment.

APAR status

• Closed as unreproducible in next release.

Error description

• In a high availability configuration, with 2 z/OS Connect EE
  servers running from a shared zFS, the update behaviour between
  AARs and ARAs and SARs is inconsistent.
  
  In this scenario, the .sar file already exists on zFS and is
  also deployed in both servers. In the first z/OS Connect EE
  server the service is deployed using the API toolkit. In the
  second server, the service is deployed using a RESTful
  Administration POST. The service is deployed.
  
  When deploying an API or API requester to the z/OS Connect EE
  servers in the same scenario, the RESTful Administration POST
  returns a 409 conflict error.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of z/OS Connect EE V3.0.           *
  ****************************************************************
  * PROBLEM DESCRIPTION: There is inconsistent behavior between  *
  *                      deploying z/OS Connect EE .aar or .ara  *
  *                      files and .sar files in an HA           *
  *                      environment.                            *
  ****************************************************************
  When a API or API requester was deployed using the RESTful
  Administration API, a check was made to see whether the API or
  API requester already existed on the file system. If it did,
  the deployment was cancelled. The equivalent check was not
  made for services, resulting in the reported inconsistency.
  

Problem conclusion

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

  Z/OS CONNECT EE

• Fixed component ID

  5655CE300

Applicable component levels