× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



you probably want this instead:
OVRDBF FILE(MYFILE) POSITION(*END)  


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Lim Hock-Chai
Sent: Tuesday, October 05, 2004 10:45 AM
To: Midrange Systems Technical Discussion
Subject: RE: CL file pointer techniques?


I think you can just use OVRDBF to reposition the file pointer:
OVRDBF FILE(MYFILE) POSITION(*START)  

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Fiona Fitzgerald
Sent: Tuesday, October 05, 2004 10:32 AM
To: Midrange Systems Technical Discussion
Subject: CL file pointer techniques?



I have a CL which creates a file in QTEMP, populates it,
then reads it in a loop. So far so good.

Then it delays x seconds & repeats the process.
This time, no processing occurs within the loop,
because although the file is repopulated,
the pointer is stuck at end-of-file at this stage.
As you might guess, this was not the plan!

I considered using OPNDBF with POSDBF.
But from what I've read, RCVF won't share its ODP,
so that's out.

Do I have to resort to generating a new QTEMP file,
suppressing level check, overriding to it
& calling an RPG just to get the pgm to start again from the top
every time I repopulate the file?
I don't want to use RPG because most of the functions
performed are CL functions, perfect for a CL pgm.

Or should I delete & recreate the file each time - will that reposition it?
All suggestions gratefully received, hope someone knows the theory
better than I do : )

Thanks,
Fiona



__________________________________

Notice of Confidentiality 

This transmission contains information that may be confidential and that may 
also be privileged. Unless you are the intended recipient of the message (or 
authorised to receive it for the intended recipient) you may not copy, forward, 
or otherwise use it, or disclose it or its contents to anyone else. If you have 
received this transmission in error please notify us immediately and delete it 
from your system.

Email: internet.mail@xxxxxxxxxxxxxxxx

--
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 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.



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.