|
First of all display the job and verify that it actually has the qtemp file open. Second, does any of the programs that get called end with a return and NOT setting on LR? If so, they may still have the file open. Are any of the programs running in different activation groups. I have old stuff that is be changed to ILE and move out of the default activation group, thus throwing off overrides and holding locks. By overriding with share no, each program called gets their own Open Data Path, the file is still shared, is that really your intention? How are you clearing the file with in the rpg, calling APIs or calling QCMDEXC? Are you fully qualifying the CLRPFM command? Just so thoughts, Christopher K. Bipes mailto:Chris.Bipes@Cross-Check.com Operations & Network Mgr mailto:Chris_Bipes@Yahoo.com CrossCheck, Inc. http://www.cross-check.com 6119 State Farm Drive Phone: 707 586-0551 x 1102 Rohnert Park CA 94928 Fax: 707 586-1884 -----Original Message----- From: SRamanujan@sungardfutures.com I must be missing something here.. I have an old RPG program that opens a work file in QTEMP with user open. This is actually a flat file that has been overridden in the CL with a SHARE(*NO) SEQONLY(*YES 204). The RPG inturn calls other programs where the file is used for updates and calculations. Once the process returns to the calling RPG, it tries to clean up by clearing the member. The logic does CLOSE on the file (using the overriden name). Clears the member for next process. But the clear option on the file throws an error 'Member already in use'. I even tried to add a dlcobj on the original flat file but in vain. Strangely, other flat files with similar logic do not have this problem. Could you kindly help me resolve this? Thanks in advance, Sudha
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.