Hello,

How did using mACB affect your daily DBA life or how do you think it will affect it?

I was curious about this and, of course, played around with AI to get some ideas. I'm sharing the summary below. Do you relate to it?

It's true that I haven't been a hands-on DBA for many years. Is it correct that you can now make changes in production outside of maintenance windows?
I imagine that even if the technology allows it, procedures like change management might still block it.

Do you think there's a lot to learn about mACB?

Can you share your experience?

Here's what GPT came up with:

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 sharing a fun "DBA diary" in the comments.

------------------------------
Aysen Svoboda
Product Owner
Broadcom
Prague
------------------------------