DCS12
asked on
iSeries Data Transfer error
I have a new Windows Pro 64bit pc with iSeries Access for Windows 5.9 installed that is getting an error when an exist transfer request is ran. (.dft)
The user originally installed it with PC5250 access only. After uninstalling and reinstalling you are able to run a transfer manually, but when it is double clicked you get the following error.
"The filename, directory name or volume label syntax is incorrect." Then if you click OK a second error reads Invalid file type or corrupted.
The file is set to open with C:\Program Files (X86)\IBM\Client Access\cwbtf.exe
Any suggestions on what to try?
The user originally installed it with PC5250 access only. After uninstalling and reinstalling you are able to run a transfer manually, but when it is double clicked you get the following error.
"The filename, directory name or volume label syntax is incorrect." Then if you click OK a second error reads Invalid file type or corrupted.
The file is set to open with C:\Program Files (X86)\IBM\Client Access\cwbtf.exe
Any suggestions on what to try?
ASKER
Yes it is valid. If I open the Data Transfer for System i, then click File-->Open, browse to the same file it opens now problem and transfers no problem.
It is only when I double click it or try to run it from the 5250 window using STRPCCMD.
It is only when I double click it or try to run it from the 5250 window using STRPCCMD.
Any chance your file associations are corrupted? You said "DFT", and it should be "DTF", I think. IF it is named with the wrong extension for some reason, that could certainly be a problem.
If that is not the issue, then I suspect that it is just something funky in the way the command that is eventually running is getting composed.
Do you have the full command that you are trying to execute through STRPCCMD that you can post here?
Looks like the path to the EXE has some spaces in it - does the path to the DTF or the target file have spaces in them? Also, I've seen problems like this when the final command was just too long due to long pathnames.
If so, just as a test, try moving the DTF to a simple, short folder name and changing the target filename to a simple folder name:
md c:\testxfer
then move the DTF to c:\testxfer, and update the DTF to put the target file in that same folder, and see if the same thing happens.
You might also want to consider trying the RTOPCB / RFROMPCB commands instead, which are designed specifically as command line utilities, unlike CWBTF, which is a GUi utility.
- Gary Patterson
If that is not the issue, then I suspect that it is just something funky in the way the command that is eventually running is getting composed.
Do you have the full command that you are trying to execute through STRPCCMD that you can post here?
Looks like the path to the EXE has some spaces in it - does the path to the DTF or the target file have spaces in them? Also, I've seen problems like this when the final command was just too long due to long pathnames.
If so, just as a test, try moving the DTF to a simple, short folder name and changing the target filename to a simple folder name:
md c:\testxfer
then move the DTF to c:\testxfer, and update the DTF to put the target file in that same folder, and see if the same thing happens.
You might also want to consider trying the RTOPCB / RFROMPCB commands instead, which are designed specifically as command line utilities, unlike CWBTF, which is a GUi utility.
- Gary Patterson
ASKER
The STRPCCMD is not the issue, because I get the same when I just run the .dtf by double clicking the file.
I does have something to do with file associations. Forgot to mention that somehow these files got changed and where trying to open with Excel and I had to change it back to CWBTF.
I have never used RTOPCB. Can it transfer PF directly to Excel format? This company has hundreds of these transfers already setup so it might be a lot of effort to change for one pc not acting right.
I does have something to do with file associations. Forgot to mention that somehow these files got changed and where trying to open with Excel and I had to change it back to CWBTF.
I have never used RTOPCB. Can it transfer PF directly to Excel format? This company has hundreds of these transfers already setup so it might be a lot of effort to change for one pc not acting right.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
For future reference, there is no "iSeries Access for Windows 5.9". Almost certainly you are referencing the version of the Personal Communications (PCCOMM) Workstation Program. PCCOMM is one component of iSeries Access.
To see the iSeries Access version navigate through Start-> Programs-> IBM iSeries Access for Windows-> Properties.
In addition to Gary's advice, you should also report here the version from Properties and the Service level that is shown next to it. Also, by "Windows Pro 64bit", you mean Windows XP Pro 64bit, right?
Tom
To see the iSeries Access version navigate through Start-> Programs-> IBM iSeries Access for Windows-> Properties.
In addition to Gary's advice, you should also report here the version from Properties and the Service level that is shown next to it. Also, by "Windows Pro 64bit", you mean Windows XP Pro 64bit, right?
Tom
Try to avoid using the short names like PROGRA~2, because this is sequential named and depending on the sequence you installed programs, it could be different per user.
Names with spaces also give problems with STRPCCMD
To be sure use long names and if spaces are included, quote the command:
C:\PROGRA~2\IBM\CLIENT~1\c
as
"C:\Program files\IBM\Client Access\cwbtf.exe %1"
or in some cases as
"C:\Program files\IBM\Client Access\cwbtf.exe" %1
You als can include "C:\Program files\IBM\Client Access" in your path setting or
make a substitute to this path with :
SUBST Q: "C:\Program files\IBM\Client Access"
In the last case, you can use Q:\cwbtf.exe %1
Names with spaces also give problems with STRPCCMD
To be sure use long names and if spaces are included, quote the command:
C:\PROGRA~2\IBM\CLIENT~1\c
as
"C:\Program files\IBM\Client Access\cwbtf.exe %1"
or in some cases as
"C:\Program files\IBM\Client Access\cwbtf.exe" %1
You als can include "C:\Program files\IBM\Client Access" in your path setting or
make a substitute to this path with :
SUBST Q: "C:\Program files\IBM\Client Access"
In the last case, you can use Q:\cwbtf.exe %1
ASKER
We never did resolve this, but thanks for the suggestions.
Open up the saved DFT and make sure the name of the target file location is valid.
- Gary Patterson