MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » August 2013

Re: committment control in RPG or COBOL pgm: can I limit file input records using OPNQRYF?



fixed

AFAIK, the only reason to use commitment control on an input-only file is
to provide for isolation. Your program doesn't want to see uncommited
records.

Charles


On Tue, Aug 13, 2013 at 4:51 PM, Stone, Joel <Joel.Stone@xxxxxxxxxx> wrote:

I agree 100%. It was written by a fellow named Dick Salvatore on an IBM
4300 in September of 1982 and is still running. If Mr Salvatore can read
this, please let us know WHY commitment control is being used when all
files (except the printer file) are INPUT ONLY?



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark S Waterbury
Sent: Tuesday, August 13, 2013 3:48 PM
To: Midrange Systems Technical Discussion
Subject: Re: committment control in RPG or COBOL pgm: can I limit file
input records using OPNQRYF?

Joel:

If this is really just a "batch report" type of program that reads a
file and prints a report, then WHY IS IT USING COMMITMENT CONTROL? =-O

Mark S. Waterbury

> On 8/13/2013 4:08 PM, 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 appears that it is complaining that the inputFile is NOT journalled
(even though the underlying PF is journalled).

Is there a workaround?

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

Thanks!



______________________________________________________________________
This outbound email has been scanned for all viruses by the MessageLabs
Skyscan service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


________________________________________________________________________
This inbound email has been scanned for all viruses by the MessageLabs
SkyScan
service.
________________________________________________________________________

______________________________________________________________________
This outbound email has been scanned for all viruses by the MessageLabs
Skyscan service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.







Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact