|
|
SMFSUBSYS/SMFTYPE/SMFINTERVALL
configuration per summary report, just like an adabas-nucleus
Today, several reports are written to Rev-Switch datasets. This data must be continuously merged using UEXIT triggers, which trigger jobs in our scheduling env to add data to genDS. Once a day, the data of the whole day processed using Natural programs and displayed via the less common 3270 interface.
As part of our monitoring modernization, we want to consolidate these 12 different reports into 4 and "simply" distribute all data via SMF LogStreams (data targetting: Zappix|Prometheus|Alloy ... Grafana).
| Use Case | reporting details enhancement |
to make the stuff temporarily (dirty) configureable, you might use the wellknown classic "hidden SAG Parm" feature pattern:
as soon as history(Y|N) is 'X', SMF records will be created/written/sent and the other parms (Int, DBID, ...) are "misused"
- "Int" becomes SMF interval
- "DBID" becomes SMFTYPE
Danke, Ernst!
Kommst Du zur IUG in München 2026-Juni?
LG, Jürgen