Re: CLLE OVRPRTF and CPYF command

On 17-Mar-2016 10:00 -0500, Charles Wilt wrote:

On 17-Mar-2016 09:40 -0500, Steve Landess wrote:

On 17-Mar-2016 09:37 -0500, paultherrien wrote:

This is more of an FYI item than a question... but comments are
appreciated.

We ran into an issue changing a CL program to CLLE.
We use OVRPRTF and then CPYF to copy a database file to the
printer file referenced in the OVRPRTF.
We were surprised to find the the OVRPRTF did not affect the
CPYF command.
The CLLE is compiled to activation group QILE.
We _assumed_ that system commands in QSYS would somehow fall
into our activation group. This is not the case.
We were further surprised to find that the command processing
program for the CPYF command is an OPM program.

use OVRSCOPE(*JOB)

When converting from CL to CLLE, I look for any overrides and change
them to *JOB.

FWiW: Typically a more appropriate choice is to specify the Override Scope (OVRSCOPE) of Call Level (*CALLLVL). Otherwise, probably there should be coded, both a cancel handler and a cleanup procedure [e.g. invoked by that cancel handler] that is defined to effect the Delete Override (DLTOVR) for the LVL(*JOB) scoped override. That cleanup is required so as to prevent other\later references in the job to that same file name, from /accidentally/ being impacted by an override that was not removed as [likely would have been] expected when the program had ended abnormally; an override would have been removed implicitly by the Data Management feature for an abnormal termination of the program, if the override had been scoped only to the Call Level, per specification of the OVRSCOPE(*CALLLVL) instead of the more aggressive OVRSCOPE(*JOB).