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



Hmm...

If you have an RPG program that reads a generic internally described file
with a record length great enough to accommodate any of the record lengths
you need to read, you can have a cl driver that loops through the list of
files and does an override for each one and calls the RPG.  You can either
do a dspffd to an outfile or use the api whose name I forget to find the
names of the character fields and their lengths and offsets in the record.
You should then be able to scan each character field.

If you're going to be sending ascii text files, cpytoimpf to a tab delimited
file gets around most of the embedded delimiter problems.

> -----Original Message-----
> From: Ray, Adam [mailto:ARay@WIPFLI.com]
> Sent: Thursday, November 08, 2001 8:10 AM
> To: 'rpg400-l@midrange.com'
> Subject: RE: process a list of files
>
>
> What gets done with the *'s once they are found has yet to be
> decided. The
> reason I need to find them all is because the * (or any
> special character)
> can be used as a delimiter when sending files electronically.
> Any field
> containing an * will cause whatever program is processing the
> data to think
> it's the end of a field when it really isn't. Using a
> different delimiter
> has been discussed, but whatever we decide to use, we have to
> scan for that
> character in all our files.
> Keep the ideas coming. I'm willing to try just about anything.
> -Adam
>


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.