IT28240: SLM POLICY DOES NOT WORK WHEN CALLED FROM ANOTHER RULE IN MULTISTEP
Closed as program error.
When an SLM policy that monitors backend latency is called from another rule (for example, in a user-defined API Connect policy), then thresholds based on backend latency do not properly account for that latency and some requests are allowed that would otherwise trigger the threshold.
SLM rule inside user-defined policy wrapped by an error rule does not properly account for backend response latency.
Fix is available in 22.214.171.124 and 2018.4.1.4 For a list of the latest fix packs available, please see: http://www-01.ibm.com/support/docview.wss?uid=swg21237631
Reported component name
Reported component ID
NoSpecatt / Xsystem
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID