Re: Export data format question

Kind of what I was thinking was going on. At one point, using
CPYTOPCD, I chose *NOTEXT and had the CR/LF. Nice fixed length
record. Rejected solely due to lack of the dollar sign. Picky,
picky.

I just wondered if that made any sense to anybody else. Seems more
like belt-and-suspenders coding. Some years back, I worked on a COBOL
program that read variable length records from a tape cassette. The
encoding used the field separator and record separator characters. No
CR/LF.

Different methods to accomplish a task, I suppose.

John McKee

On Tue, Jan 10, 2012 at 6:53 PM, Mark S. Waterbury
<mark.s.waterbury@xxxxxxxxxxxxx> wrote:

Hi, John:

Sounds like they are processing the data on a PC DOS (or Windows) system
... the idea for adding a "$" (or any non-blank character) to the end of
the record is to preserve the "fixed length" fields -- otherwise, some
software blank trims trailing blanks when reading "lines" of data from a
text file (hence the requirement for the CR/LF)...

Does that help?

Mark S. Waterbury

 > On 1/10/2012 6:45 PM, jmmckee flinthills.com wrote:

A vendor wants a record with fixed length fields , followed by a
dollar sign AND a CR/LF.

Leave off either the CR/LF or the dollar sign, and record is rejected.

I don't know if the site uses SQL to parse out the data.  I'm just
curious if there could be some valid reason for a record delimiter and
the CR/LF sequence.

John McKee

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