Client Access file transfer TO AS/400
Hi Gang, I have and end user who indicates nothing has changed...famous last words. A file transfer was set up by a former IT person on the endusers PC That transfered a TXT file from her PC to the aAS400 but now when she tries to transfer the data to the iseries....she is getting CWBTF0023(???) I normally set up transfers from Iseries to the PC...but I have not set up a transfer to iseries. If this has worked but now it does not....can anyone give me some ideas as to what and how to troubleshoot this issue? I appreaciate any and all suggestions.
Software/Hardware used:
Software/Hardware used:
ASKED:
January 15, 2009 3:40 PM
UPDATED:
April 27, 2012 2:14 PM
Answer Wiki:
Client Access Transfer is looking for an ".FDF" file - This describes the transfer information.
Either it's been moved or erased on the client machine.
You can create an FDF file during a download to the client machine.
So reverse the normal process - download to the pc from the desired AS/400 file
with the PC spec's like you would latter upload and select the box - create FDF
you will need atleast one record in the AS/400 file. And take care not to overwrite the good client data file.
Once the FDF is recreated you should be able to upload.
Here's another discussion of this subject.
http://www.mcpressonline.com/index.php?option=com_fireboard&Itemid=558&catid=179&func=fb_pdf&id=26685&lang=en
To see all answers submitted to the Answer Wiki: View Answer History.
Can you please explain how to set up transfers from Iseries to the PC using client access.
Another possible issue could be that the target data library is different.
When we have a software release upgrade we need to changes all of our .DTF to point to the ne library.
If the target library has not changed I’d reccomend scaning the PC for .FDF files and see if something looks familiar. You can open them with a text editor and see what file / library is being used.