Re: EXTFILE not working if filename is DIBFIL

Chuck,

I should have known I could count on you. You are absolutely right; there
was an override in effect, but neither DSPOVR nor DSPJOB * OPTION(*FILOVR)
showed it. After I examined the call stack and found the culprit, I found
out that DSPOVR ACTGRP(<activation group>) does show it.

The file in question is being migrated from a centrally located file to a
distributed file. Hence there was a command processing program in the call
stack that still did the override to the first occurence in the library
list.

Thanks for the help.

Joep Beckeringh


rpg400-l-bounces@xxxxxxxxxxxx wrote on 11-06-2009 02:59:26:

Re: EXTFILE not working if filename is DIBFIL

CRPence

It seems possible that an incorrect conclusion for the claim that
"there are no overrides in effect" during the open may be the most
logical explanation for the described outcome; i.e. there may be an
OVRDBF DIBFIL DIBFIL ACTGRP() OVRSCOPE() that was activated at some
point in processing. Was DSPOVR issued within the job performing
the open, while stopped in debug just before the OPEN? Was WRKJOB
OPTION(*FILOVR) done against the job performing the open, while
stopped in debug just before the OPEN? I prefer the former to the
latter when possible [may be difficult; not so much for *CALLER],
because I think the WRKJOB overstates its capability in showing
overrides "at any active call level for the job"; i.e. I would
expect "for all active call levels for the job" but I am not sure
what I really would get, and I recall having difficulties to see
what I expected.

I do not recall exactly what the OPEN details are for trace data
in the TRCJOB output, but I seem to recall it shows an original name
and the resolved name [including member] that is opened. The trace
data may have something of value to review. The trace record is
produced by QDMCOPEN. A review of a trace record for the command
analyzer would show any incidents of OVRxxxF. The auditing of the
override command(s) could show the command string logged and then
review for any case of FILE(DIBFIL) or TOFILE(xxx/DIBFIL).

Regards, Chuck