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



On 07-Apr-2015 12:25 -0500, Dan Rasch wrote:
CPYFRMSTMF ('/FILEIMPORTS/RAF/DirectMarketing_Shipped.txt')
TOMBR('/QSYS.LIB/ISMKLIB1.LIB/FILE55.FILE/FILE55.MBR')
MBROPT(*REPLACE) ENDLINFMT(*ALL) TABEXPN(*NO)

All I get is one record and it is not right.

CPYFRMIMPF looks much better, and gets the first record right,
but again, only one record.

CPYFRMIMPF FROMSTMF('/FILEIMPORTS/RAF/Retail_Shipped.txt')
TOFILE(ISMKLIB1/FILE55) RCDDLM(*ALL)

Anything jump out on either?


Presumably the stream data in the from-STMF does not include any of the supported\recognized Record Delimiter (RCDDLM) characters\character-combination [aka End Of Line Characters (ENDLINFMT), or sometimes the acronyms EOR or EOL] of Line-Feed (LF), Carriage-Return (CR), or either of the combined CRLF or LFCR? Perhaps that is because in lieu of EOR characters, the data is /packed/ as fixed-length; the Copy From Stream File (CPYFRMSTMF) I know supports an ENDLINEFMT(*FIXED) for that case. For the Copy From Import File (CPYFRMIMPF) feature, instead of using the RCDDLM specification, that type of from-STMF instead might be identified successfully using the Record Format Of Import File (DTAFMT) specification of *FIXED for which IIRC the additional input of a Field Definition File (FLDDFNFILE) is required thus also implying the record data also is not delimited?


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.