|
No, the record is not locked previous. The only difference that we have made to the pgm is to convert it using IBM's CVTRPGSRC. It is a user exit, compiled with actgrp(*CALLER) and run in batch. The pgm performs a chain to a record, clears the data presently in the record and writes a new record to the file. I have never experienced this behavior and am simply trying to understand why the lock never affected the rpgIII version. Justin replied: Did you check to see if there was already a record lock on the file before you ran the program? -----Original Message----- We have a pgm that chains to a file w/ type Update. Under rpgIII it ran with no problems, but with rpgIV it throws an error for a locked record. We have added the (N) to the chain, but I'm wondering if there is a difference in the way chains are performed between rpgIII & IV. ***************************defiant************************************ This email and any files transmitted with it are intended solely for the use of the individual or agency to whom they are addressed. If you have received this email in error please notify the Navy Exchange Service Command e-mail administrator. This footnote also confirms that this email message has been scanned for the presence of computer viruses. messaging_support_team@nexnet.navy.mil **********************************************************************
As an Amazon Associate we earn from qualifying purchases.
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.