A CA OPS/MVS Started Task(STC) is not triggering an End of Job (EOJ) rule after completion.

Document ID : KB000005095
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

We have created an EOJ Rule to check the Maximum Completion Code of a started task (STC), but the rule doesn't appear to be working when the started task (STC) ends.  We have verified that all the parameters are set to implement EOJ Rules: INITSMF = YES, EOJRULES = YES, BROWSEEOJ = YES and EOSRULES = YES.

The IEFACTRT Exit has been enabled: SUBSYS(STC,EXITS(IEFACTRT)) -- PARMLIB

Cause:

The "D PROG,ExIT,EXITNAMe=SYSSTC.IEFACTRT" command did not show the OPS OPMVACEX exit was loaded.

Resolution:

To correct this problem, we had the customer issue the reload command:
F OPSS,RELOAD(OPMVACEX)
This command will cause the dynamic exit interface in OPSMAIN to check for exits and ADD them if needed.
Once the exit was available, the EOJ rule ran successfully.


Additional Information:

END-OD-Job Rules