Re: CPYFRMQRYF

David FOXWELL wrote:

<sniff> After CPYFRMQRYF I think you must use POSDBF if you still
want to read the file resulting from the OPNQRYF. After issuing
OVRDBF SHARE(*YES), DSPJOB shows no override in place.

Didn't find this information in the infocenter on CPYFRMQRYF. </sniff>

Generally after OPNQRYF and then CPYFRMQRYF, a request to POSDBF to position to *START can be used to enable the open data path to be read again from the beginning. One exception is when the open is not /permanent/ and an error [after the open, before the next pass] effects an implicit reclaim resources [RCLRSC] which then closes the shared open data path [ODP]. Be aware that changed data could be available in the second pass of the data if the data path accesses live versus static data.

An override will not show in DSPJOB if either it was scoped to the activation group [and the DSPJOB OPTION(*FILOVR) is not made from within that activation group] or it was scoped to a higher call level; in the latter case, the override is implicitly deleted when returning to the lower call level [so no DLTOVR is required].

The concept of shared\reusable open data path should be in the Database and\or Data Management documentation. The Copy From Query File feature is consistent with that, such that no special commentary would be required to describe the effect of CPYFRMQRYF on the ODP.

Regards, Chuck