Client Access file transfer TO AS/400

335 pts.
Tags:
AS/400
Client Access
iSeries Data Transfer
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.

Answer Wiki

Thanks. We'll let you know when a new response is added.

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

Discuss This Question: 2  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • vibgyor
    Can you please explain how to set up transfers from Iseries to the PC using client access.
    280 pointsBadges:
    report
  • ToddN2000
    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.
    11,025 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following