RE: Clear File - error -- MIDRANGE-L

I got this to work. Now I am doing both RCLRSC as well as the RCLACTGRP (Since 
I am not sure which one to remove:).  This has eliminated my error and improved 
the performance also.

Thanks for all the help.
Sudha

-----Original Message-----
From: Ramanujan, Sudha
Sent: Wednesday, September 11, 2002 2:54 PM
To: midrange-l@midrange.com
Subject: RE: Clear File - error


I did have a RCLRSC only, I was doing it after clrpfm.  I will try changing 
this.
Thanks,
Sudha

-----Original Message-----
From: Mlpolutta@aol.com [mailto:Mlpolutta@aol.com]
Sent: Wednesday, September 11, 2002 2:29 PM
To: midrange-l@midrange.com
Subject: Re: Clear File - error


--
[ Picked text/plain from multipart/alternative ]
Try a RCLRSC before the CLRPFM - I believe this still convinces RPG programs
(not RPGLE) to totally shut down and close everything.

Michael


> Chris,
> Yes it is a QTEMP file.  It is possible that other program may not be
> setting on the LR.  But I cannot change this since the other pgms are used
> elsewhere for ILE and others and it is performance intensive.  I guess this
> is the problem.  But how do I close this?  Activation group when display
> the job is *DFTACTGRP.  Yes I want to share the file in the open data path.
>  Also this way, I don't have to open for each record but clear it for
> process and still share it.  Yes I am calling the QCMDEXEC to clear with
> QTEMP qualified for clear.  Also tried the dlcobj using QCMDEXEC.
> Iget the following :
> Function check. CPF3130 unmonitored by RPG1 at statement 4603,  instruction
> X'077C'.
>
> I put a LO indicator on qcmdexec and this skips the error but still I am
> getting wrong calcs now.
>
> Thanks,
> Sudha
>
> -----Original Message-----
> From: Chris Bipes [mailto:chris.bipes@cross-check.com]
> Sent: Wednesday, September 11, 2002 10:44 AM
> To: 'midrange-l@midrange.com'
> Subject: RE: Clear File - error
>
>
> 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
>

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

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