|
I don't specify anything, on the cpyffrm prompts I leave it as *dlm coming back in. I don't know where or how to define this flddfnfile, on client access you can define a file spec and store on the harddrive but how to I define one directly on the as400? Angela Wawrzaszek IT Supervisor awawrzaszek@xxxxxxxxxxxxxxx (315) 258-4205 -----Original Message----- From: Wilt, Charles [mailto:CWilt@xxxxxxxxxxxx] Sent: Wednesday, February 09, 2005 1:35 PM To: Midrange Systems Technical Discussion Subject: RE: Restoring a .txt file Angela, What are you specifying in the FLDDFNFILE parm of the CPYFRMIMPF? How are the fields specified in the FLDDFNFILE? Charles Wilt iSeries Systems Administrator / Developer Mitsubishi Electric Automotive America ph: 513-573-4343 fax: 513-398-1121 > -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx > [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Angela Wawrzaszek > Sent: Wednesday, February 09, 2005 12:39 PM > To: Midrange Systems Technical Discussion > Subject: Restoring a .txt file > > > Help! > > > > I have a .txt file that was saved from an as/400 > inventory file. It > was saved as a fixed format file. I now want to bring that .txt file > back to the as400 to run queries on it. However since it was fixed > there is not comma delimiters etc. So I copied it back to a > flat file > on the as400 and then tried using the cpyfrmimpf command to > copy it back > into its regular format. The problem occurs because there is numeric > data in the file. Therefore the copy crashes because I am trying to > copy 17.00 - which is beign treated as a character field to > a numberic > field. > > > > The command used to copy the data to the .txt file was: > > > > > > CPYTOIMPF FROMFILE(Mylib/MyFile) + > > TOSTMF('home/yearend/yearend2004/MyFile.t + > > xt') MBROPT(*REPLACE) + > > STMFCODPAG(*PCASCII) RCDDLM(*CRLF) + > > DTAFMT(*FIXED) STRDLM(*NONE) > > > > > > Can anyone help me to restore this to its original data formats? > > > > Thanks! > > > > > > > > Angela Wawrzaszek > > IT Supervisor > > awawrzaszek@xxxxxxxxxxxxxxx > > (315) 258-4205 > > > > -- > 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.