Program is not enabled

CICS configuration problems — definitions pointing at wrong programs, disabled resources, region differences — are environmental.

What it means

• Transactions, programs, files and connections are all defined resources; a wrong definition breaks the transaction.
• Test and production regions drift apart over time.

Common causes

• Transaction points to the wrong program version.
• Program defined but not enabled.
• Deployed load module not NEWCOPYed.
• Resource definitions differ between regions.

How to diagnose

• CEMT INQUIRE on the transaction/program/file.
• Compare definitions across regions.
• Check DFHRPL for the load module.

How to fix it

• Correct the definition and reinstall it.
• NEWCOPY after deploying modules.
• Promote definitions with the release.

Example: Verify definitions with CEMT

CEMT shows the live truth about definitions.

Interview tip

• Q: How would you troubleshoot a Program is not enabled in production?
• A: I would inquire on the live definitions, compare with test region, correct and reinstall, then NEWCOPY.

Prevention checklist

• Promote definitions with code releases.
• Audit region differences regularly.