Back-level versions of monitored servers that are not on current maintenance may not generate statistics records correctly if they generate them at all.
This causes issues with IBM® Sterling Control Center Monitor events, and as a result, IBM Sterling Control Center Monitor may not have the information needed to match specified SLC parameters. For example, when monitoring transfers of files to GDGs, the dataset name in the process step start event must match the dataset name in the process step end event, or SLCs do not work correctly. If the server being monitored is not on current maintenance, a known (and resolved) issue causes the dataset name in the Process step start event not to be fully resolved. That is, instead of the destination dataset name in the process step start event being, for example, XYZZY.GDG.G0001V00, it is XYZZY.GDG(+1), while the dataset name in the Process step end event is fully resolved. If this occurs the SLC will not “work.” Even if the match criteria for the SLC is triggered by the dataset name in the step start event, because the dataset name in the step end event is different (the dataset name in the step end event is always the fully resolved GDG dataset name), the SLC logic does not recognize it as the terminating event.
You can tell if this issue is causing problems by closely examining the statistics records for the Process and seeing whether or not the dataset name in the step start and step end events match.