webhook not reporting consumptions
Article ID: 111877
Updated On:
Products
Application Lifecycle Conductor
Issue/Introduction
z/OS MF file space had run out and I was getting failures (but these weren't all reported by the Endevor action event processing).
Environment
Release: ALMCON99000-3.0-Application Lifecycle-Conductor
Component:
Component:
Resolution
Actually, when z/OS MF file space ran out of memory, it created the Endevor event files with a tempname:
TEMPNAME.D48D67C2.2BD22782
TEMPNAME.D48D78EB.8661A782
TEMPNAME.D48D78ED.29D94E82...
The reason that webhook didn't report the consumption or report of these elements is that the system looks for files with a specific naming convention.
The files to be consumed by webhook server must have at least an application type (ELM or PKG) and an action type (ADD, UPDATE)... Consequentially, these elements were "ignored" by webhook server.
However, if the other elements were not consumed by webhook server in this specific scenario, then we have a defect to resolve:
2018061418380936ELMTESTJIM___GENERA
2018061421330305ELMSTEVE2____ADD
2018062521050108ELMACOPY002__UPDATE
2018062617082650ELMSTEVE_____RETRIE
2018062617084573ELMSTEVE_____RETRIE
TEMPNAME.D48D67C2.2BD22782
TEMPNAME.D48D78EB.8661A782
TEMPNAME.D48D78ED.29D94E82...
The reason that webhook didn't report the consumption or report of these elements is that the system looks for files with a specific naming convention.
The files to be consumed by webhook server must have at least an application type (ELM or PKG) and an action type (ADD, UPDATE)... Consequentially, these elements were "ignored" by webhook server.
However, if the other elements were not consumed by webhook server in this specific scenario, then we have a defect to resolve:
2018061418380936ELMTESTJIM___GENERA
2018061421330305ELMSTEVE2____ADD
2018062521050108ELMACOPY002__UPDATE
2018062617082650ELMSTEVE_____RETRIE
2018062617084573ELMSTEVE_____RETRIE
Feedback
Yes
No
Powered by
