RE: The FDF file on a transfer

[Joel Fritz <JFritz@xxxxxxxxxxxxxxxx>]

The FDF should contain a data map.  

You need to download the receiver file from the 400.  The file should have
defined fields that correspond to the columns of the spreadsheet.  You'll
get best results if the file has at least one record in it.  This will
create the FDF.  Then you should be able to upload your Excel file.

I've found .prn files to be a problem unless you format the columns with an
explicit length, which is hard to maintain and easy to forget.  If you save
the file as comma delimited, .csv, you may have better luck  

If you're using CA Express, it has a utility to create files on the 400
based on a PC text file.  On the Tools menu, select "Create AS/400 Database
File."  It's kind of clunky, but it does work.  You may have to redefine the
data mapping that it will guess for you. Depending on how complex your
receiver file is, it may be easier to create DDS and do the download then
upload procedure.  



> -----Original Message-----
> From: Dan Rasch [mailto:drasch@mail.win.org]
> Sent: Monday, May 01, 2000 8:57 AM
> To: MIDRANGE-L@midrange.com
> Subject: Re: The FDF file on a transfer
> 
> 
> 
> I have had limited success using the methods offered here (and I
> appreciate the help), but still need a map to the fields.  
> 
> The particulars:
> 
> 1. Saved the Excel file as .PRN and transferred as ASCII.  
>    This method sent all the data for all the records,
>    but did not map the fields correctly. Environment:
>    a. saved spreadsheet as .PRN
>    b. transferred from PC to 400 using 
>        PC file name = the .PRN file,
>        400 file name = lib/file
>    c, details:
>        (not checked) use PC file descr file 
>        file type = ASCII text, 
>        translate = (ASCII checked)
>        create = Yes, both file and member      
>        record length = 600
> 
> 2. Transferred backwards from 400 to PC and created a FDF file,  
>    but must be doing something wrong on the back end, because I  
>    only get one record, and it has 6 bytes of garbage 
> followed by spaces.
>    The environment:
>    a. transferred my 400 file to the PC and created C:\TRANSFER.FDF
>    b. transferred from PC to 400 using
>        PC file name = (Excel spreadshhet file name)
>        AS/400 file name = (lib/file)
>    c. details:
>        (checked) Use PC File descr
>        file description file C:\TRANSFER.FDF
>        translate = (ASCII checked) 
>        AS/400 file Create = No, replace member only
>    Under the 'desperate times' theory, I also tried checking 
> the ANSI to
>    decimal instead of ASCII, but had the same basic result.
> 
> 
> Dan Rasch - because if the human species concentrated on the really 
> important things in life, there would be a shortage of fishing poles!
> 
> 
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---