|
Alas, you have this psyched out. Once you get the CPF0864 for end of file, you are dead! Your best solution is to break the program into two programs. One to launch/re-launch the process, and then to call a worker bee program to create the file, read it and return. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 "i" comes before "p", "x" and "z" e gads Our system's had more names than Elizabeth Taylor! 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com http://www.as400connection.com "Fiona Fitzgerald" <fiona.fitzgerald To @notes.royalsun.c Midrange Systems Technical om> Discussion Sent by: <midrange-l@xxxxxxxxxxxx> midrange-l-bounce cc s@xxxxxxxxxxxx Subject CL file pointer techniques? 10/05/2004 11:32 AM Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.com> 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.
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.