Question & Answer
Question
When using z/OS Connect Enterprise Edition (EE) V2.0.3.0, some application programming interface (API) requests are resulting in an HTTP 404 and message BAQR7040E: Resource not found. Looking at the trace, I have discovered that the relative path is being truncated when I compare the path name in the trace with the API's relative path. This is causing the "Resource not found". Can you help me determine what is causing the truncation?
Answer
When reviewing the trace, it is found that the cause of this problem is that the text of the base path is being repeated.
For example, the trace shows that the requestURI is:
/customer/part1/v1/part2/records/customers
In the processing of this URI, the base path ("/customer") is removed from the rest of the URI.
z/OS Connect EE incorrectly removes any other instances of the base path string from the URI. In the example above, z/OS Connect EE has also removed the "/customer" from the end of the URI resulting in:
/part1/v1/part2/recordss
This bug was fixed in the z/OS Connect EE V2.0.4.0 and all subsequent releases. PTF UI41811 for APAR PI69668 provides the z/OS Connect EE V2.0.4.0 update. But, you will not see this problem mentioned in the APAR because the fix is part of continuous delivery. IBM recommends that you apply all current maintenance so that you will get this fix along with any other fixes that are available.
Product Synonym
zCEE
Was this topic helpful?
Document Information
Modified date:
14 February 2023
UID
dwa1401046