CLLE模块兼程序中提交作业的OVRDBF命令失效问题咨询

Ah, I’ve run into this exact issue before when refactoring CLLE code into modules—super frustrating when things that worked suddenly break! Let’s break down why your OVRDBF is failing now and how to fix it.

The core problem boils down to differences in activation group context and command scope between standalone CLLE programs and CLLE modules. Here’s the detailed breakdown:

1. Activation Group Scope Mismatch #

When your code was a standalone CLLE program, it almost certainly ran in the default activation group (*DFTACTGRP). In this context, OVRDBF defaults to a job-level scope—meaning the file override persists for the entire job (until you explicitly delete it or the job ends).

But when you convert it to a module and bind it into a program, you’re likely using a named activation group or NEW activation group (the default for bound programs unless specified otherwise). In non-default activation groups, OVRDBF defaults to SCOPE(*ACTGRP)—so the override only exists within that specific activation group. If your job submission logic relies on the override being available outside that group (e.g., in a submitted child job or another program in a different activation group), it won’t see the override at all.

2. Submitted Jobs Don’t Inherit Parent Job Settings #

Even if you tweak the OVRDBF scope, remember: when you submit a job with SBMJOB, that’s an entirely separate process. It does not inherit any file overrides, activation group settings, or job-level variables from the parent job.

The reason it worked as a standalone program? Chances are you were submitting a job that directly called the standalone CLLE program (e.g., SBMJOB CMD(CALL PGM(MYCL))), so the OVRDBF ran inside the new job and took effect there. Now that it’s a module, you might be running OVRDBF in the parent job’s activation group first, then submitting a job that doesn’t include that module’s logic—so the override never gets created in the child job.

3. Module Binding Options Can Kill Overrides Early #

If you compiled your CLLE module with ACTGRP(*NEW), every time the module is called, it spins up a temporary activation group. Once the module finishes executing, that group is destroyed, taking the OVRDBF override with it. This is a common pitfall if you expected the override to persist after the module runs.

Option 1: Explicitly Set SCOPE(*JOB) in OVRDBF #

If you need the override to apply to the entire parent job (and don’t mind it persisting until deleted), modify your command to include:

OVRDBF FILE(MYFILE) TOFILE(MYLIB/MYFILE) SCOPE(*JOB)

Note: This won’t help for submitted child jobs—they still won’t inherit the override.

Option 2: Move OVRDBF Into the Submitted Job’s Logic #

To apply the override to the submitted job, ensure the OVRDBF runs inside that job. Instead of running the override in the parent job then submitting, submit a job that calls the bound program containing your module:

SBMJOB CMD(CALL PGM(MYBOUNDPGM)) JOB(MYJOB)

This way, the OVRDBF executes directly in the child job and takes effect there.

Option 3: Align Activation Groups With Your Standalone Setup #

Compile your CLLE module to use the caller’s activation group:

CRTCLMOD MODULE(MYLIB/MYCLMOD) SRCFILE(MYLIB/QCLLESRC) ACTGRP(*CALLER)

Then bind it into a program that uses the default activation group (matching your old standalone behavior):

CRTPGM PGM(MYLIB/MYBOUNDPGM) MODULE(MYLIB/MYCLMOD) ACTGRP(*DFTACTGRP)

This makes the module run in the same context as your original standalone program, so the override scope works as expected.

Option 4: Use a Persistent Named Activation Group #

If you prefer using a named activation group, bind all related programs to the same group to keep the override active. Compile your bound program with:

CRTPGM PGM(MYLIB/MYBOUNDPGM) MODULE(MYLIB/MYCLMOD) ACTGRP(MYACTGRP)

Ensure any programs that rely on the override are also bound to MYACTGRP—this keeps the override active as long as the activation group exists.

内容的提问来源于stack exchange，提问作者Susmitha