|
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. Thanks, Mark Mark D. Walter Senior Programmer/Analyst CCX, Inc. mwalter@xxxxxxxxxx http://www.ccxinc.com |---------+-------------------------------> | | Vernon Hamberg | | | <vhamberg@xxxxxxxxxx| | | t> | | | Sent by: | | | midrange-l-bounces@m| | | idrange.com | | | | | | | | | 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 | >------------------------------------------------------------------------------------------------------------------------------| Mark Someone just mentioned this recently - a parameter on CPYTOSTMF can help with this: End of line characters (ENDLINFMT) - Help *FIXED 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 records. You might also look at the simple CPY command, which does raw copying, with optional conversion. HTH Vern 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. > >Thanks, > >Mark > >Mark D. Walter >Senior Programmer/Analyst >CCX, Inc. >mwalter@xxxxxxxxxx >http://www.ccxinc.com > > >-- >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 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.