Scheduled, fleet-wide scans
Run the same vetted scan across the whole estate on a schedule - and never let one back-level LPAR rot silently.
A batch operator responsible for many LPARs
The trigger. “Run the security/config scans across all our LPARs every month and flag the exceptions, without babysitting each one.”
The old way
Every cycle, the dozen-step relay had to be run by hand on every LPAR. Version drift only gets worse at scale. The toolkit is reused on each LPAR, so it takes just one box that quietly fell behind to produce a bad file. That problem is then found weeks later, on each LPAR, one support ticket at a time.
The Flow way
Take the prebuilt scan template, add a Cron node to make it recurring, and clone it across the fleet. You can also parameterize the connection and HLQ per LPAR.
The toolkit is fetched fresh and version-pinned on every run, so no LPAR can drift on its own. When a new toolkit ships, you update the template once and the whole fleet picks it up on the next scheduled run. There is no need for N separate rediscoveries. Failures route to the spool-download branch automatically, so the operator reviews the exceptions rather than the runs that passed.
The same wiring, a CI/build step that feeds a scheduled mainframe action, also handles deploy-then-trigger hand-offs.
Payoff
| Old way | Flow way | |
|---|---|---|
| Effort per cycle | Manual relay multiplied by N LPARs | Scheduled; runs itself |
| Drift across fleet | Silent, per-box, found weeks later | Can’t drift; one central update |
| Operator attention | Every run | Exceptions only |