How did using mACB affect your daily DBA work? Or how do you think it will affect it?
I was curious about this and played around with AI to get some ideas. I'm sharing the summary below. Does it match your experience?
I haven't been a hands-on DBA for many years, so I'd like to sanity-check some of these points.
Is it really possible to make changes in production outside of maintenance windows now?
I imagine that even if the technology allows it, procedures like change management might still slow things down.
Do you think there's a lot to learn about mACB?
Can you share your experience?
Here is what gpt says:
Life After mACB – DBA's Quick Notes
What I Had to Learn
-
IMS Catalog concepts – structure, versioning, active definition tracking
-
Dynamic load & activation – when IMS picks up new PSBs/DBDs and how to roll back
-
DevOps integration – connecting Catalog updates to CI/CD pipelines (Git, Jenkins, etc.)
-
New troubleshooting skills – interpreting Catalog/mACB-related messages and conflicts
What Changed in My Work
-
No more static ACBLIB builds for every change
-
Faster deployments – changes can go live the same day
-
Less downtime & weekend work – updates happen during business hours
-
Multiple versions in parallel – easier A/B testing and phased rollouts
-
Closer collaboration with application teams
What We Can Do Now That We Couldn't Before
-
Deploy new transactions without planned outages
-
Run parallel PSB versions in production
-
Provide sandbox environments quickly for developers
-
Support rapid prototyping directly against IMS data
I'm also posting a "DBA diary" version in the comments for fun.
------------------------------
Aysen Svoboda
Product Owner
Broadcom
Prague
------------------------------