On 13 Aug 2013 13:08, Stone, Joel wrote:
PGMA reads a file sequentially and prints a report.

I would like to add an OPNQRYF cmd in front of the PGMA call as follows:

Ovrdbf inputFile share(*YES)

OPNQRYF inputFile QRYSLT(SpecialCode = "A")
CALL PGMA

The resulting report should have only records which satisfy the QRYSLT.

Unfortunately PGMA is using commitment control and I receive the
following error:

Commitment control not valid for open of member PCCOMM.
OPEN failed because file cannot be placed under commitment control CPF4293, CPF4326, CPF4327, CPF4328, CPF4329.

It would be much clearer if the spooled joblog form of the messages was given above, instead of a copy\paste from a joblog. At least the message identifiers could have been provided, or at least to clarify that the prior two lines were the messages; albeit I recognize the first as the U.S. English version of CPF4293, so...

Did you read the cause and recovery for the CPF4293?

The query ODP created by the OPNQRYF intended to be shared by the PGMA must be created _compatible_ with the requirements of the PGMA. There are some parameters available on the Open Query File command to effect that compatibility.

It appears that it is complaining that the inputFile is NOT
journalled (even though the underlying PF is journalled).

Huh? Can you explain the means by which that was the inference? The referenced file data is apparently already journaled, else the PGMA would not have been able to use the COMIT kwd on the F-Spec irrespective of having inserted an OPNQRYF request.?

Is there a workaround?

Should I use CPYFRMQRYF and then journal the output file? Then delete
it?

Probably just properly creating a compatible ODP and sharing that ODP is all that is required to resolve the issue.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.