Maybe the behavior of ENDLINFMT is about the display, not the contents. That option suppresses any end-of-line characters, so it is raw. Or maybe there is some weird kind of character translation.

I'm not sure about QNTC - maybe you'd need to copy it first to another part of IFS, then from there to QNTC?


At 12:08 PM 10/27/2004, you wrote:

ENDLINFMT did something weird. It sort of put two lines on one. Strange.

CPY worked though, but can you use it to copy to QNTC? It didn't work on my
system, but CPYTOIMPF/CPYTOSTMF does. This isn't a show stopper, it'd just
be nice.



Mark D. Walter
Senior Programmer/Analyst
CCX, Inc.

|---------+-------------------------------> | | Vernon Hamberg | | | <vhamberg@xxxxxxxxxx| | | t> | | | Sent by: | | | midrange-l-bounces@m| | | | | | | | | | | | 10/27/2004 12:48 PM | | | Please respond to | | | Midrange Systems | | | Technical Discussion| |---------+------------------------------->

| |
| To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> |
| cc: |
| Subject: Re: cpytostmf/cpytoimpf |



Someone just mentioned this recently - a parameter on CPYTOSTMF can help
with this:

                End of line characters (ENDLINFMT) - Help
     The lines in the stream file are written as fixed length records.
     CR and LF characters are not added at the end of each line, trailing
     blanks are not removed from the end of each record.  The length of
     the stream file records equals the length of the database file

You might also look at the simple CPY command, which does raw copying, with

optional conversion.


At 09:45 AM 10/27/2004, you wrote:

>Is there a way, using either of these two commands, to retain the record
>length of a physical file even though there is only hex 40 in the last
>character? Right now it is truncating the data.
>Mark D. Walter
>Senior Programmer/Analyst
>CCX, Inc.

This thread ...


Return to Archive home page | Return to MIDRANGE.COM home page