Sftp put problem
-
- Posts: 40
- Joined: Thu Jun 01, 2017 9:15 am
Sftp put problem
Hello,
We putfiles from host to windows.
When we put files windows,the other system take the file and delete it.
as I understood COZ checks the file after put file,that's why we get error rc=exitcode=1 even files transfer succesfully (because other system delete it)
cozsftp> put '//xxx.xxx.xxx' /test/test1.txt
Uploading //xxx.xxx.xxx to /test/test1.txt
ZosSettings$I¨: Transfer options: clientcp=IBM-1026,linerule=crlf,mode=text,serv
ZosDataset$I¨: Opening dataset xxx.xxx.xxx for rea
$56.366¨ remote open(Ütest/test1.txtÜ): No such
ZosDataset$I¨: Closing dataset //xxx.xxx.xxx - 0 r
CoZBatch$I¨: returning rc=exitcode=1
is there any settings close control or can coz lock the file?
Regards
Cagatay
We putfiles from host to windows.
When we put files windows,the other system take the file and delete it.
as I understood COZ checks the file after put file,that's why we get error rc=exitcode=1 even files transfer succesfully (because other system delete it)
cozsftp> put '//xxx.xxx.xxx' /test/test1.txt
Uploading //xxx.xxx.xxx to /test/test1.txt
ZosSettings$I¨: Transfer options: clientcp=IBM-1026,linerule=crlf,mode=text,serv
ZosDataset$I¨: Opening dataset xxx.xxx.xxx for rea
$56.366¨ remote open(Ütest/test1.txtÜ): No such
ZosDataset$I¨: Closing dataset //xxx.xxx.xxx - 0 r
CoZBatch$I¨: returning rc=exitcode=1
is there any settings close control or can coz lock the file?
Regards
Cagatay
-
- Posts: 40
- Joined: Thu Jun 01, 2017 9:15 am
Re: Sftp put problem
is there any update?
Re: Sftp put problem
Your messages seem to be truncated, but this:
$56.366¨ remote open(Ütest/test1.txtÜ): No such
means that the remote server returned a failure because there was no such directory and it could not open the file.
This is a problem with the file/directory name or with the remote server.
$56.366¨ remote open(Ütest/test1.txtÜ): No such
means that the remote server returned a failure because there was no such directory and it could not open the file.
This is a problem with the file/directory name or with the remote server.
-
- Posts: 40
- Joined: Thu Jun 01, 2017 9:15 am
Re: Sftp put problem
The process
host->central sftp server<->biztalk server
host sends the file central sftp server. and biztalk server cut the file from there.
we can see file biztalk server after job finished with exit code=1
is there any comment?
host->central sftp server<->biztalk server
host sends the file central sftp server. and biztalk server cut the file from there.
we can see file biztalk server after job finished with exit code=1
is there any comment?
Re: Sftp put problem
The error message shows that Co:Z SFTP send an "FX_OPEN" packet to the remote SFTP server and that it returned an error "No such file".
This is a problem with the remote server, or maybe the directory is simply not found. It is not a Co:Z SFTP server.
This is a problem with the remote server, or maybe the directory is simply not found. It is not a Co:Z SFTP server.
-
- Posts: 40
- Joined: Thu Jun 01, 2017 9:15 am
Re: Sftp put problem
There is file and folder, it is certain. we checked it.
coz sftp batch after send the file remote machine, check the file?
we get error jcl even file transfer is succesful.
Regards
Cagatay
coz sftp batch after send the file remote machine, check the file?
we get error jcl even file transfer is succesful.
Regards
Cagatay
Re: Sftp put problem
The log that you posted only shows that it *tried* to upload a file but the remote file open failed, so I don't see any evidence (in the log that you supplied) that a file was sent.
Please rerun this, but add tracing/logging options to the beginning of your script:
export COZ_LOG=T
sftp_options="$sftp_options -vvv "
Then, download entire output from the job and email it along with the input JCL and script to info@dovetail.com and we will review it.
Please rerun this, but add tracing/logging options to the beginning of your script:
export COZ_LOG=T
sftp_options="$sftp_options -vvv "
Then, download entire output from the job and email it along with the input JCL and script to info@dovetail.com and we will review it.
-
- Posts: 40
- Joined: Thu Jun 01, 2017 9:15 am
Re: Sftp put problem
can we take logs specied for this job?
I known that if I add all jobs "$sftp_options -vvv "it increases sftp time
I known that if I add all jobs "$sftp_options -vvv "it increases sftp time
Re: Sftp put problem
I suggest that you only modify one job and run a test with tracing on.
You can test with a small data set if you are concerned about the amount of tracing output.
You can test with a small data set if you are concerned about the amount of tracing output.
-
- Posts: 40
- Joined: Thu Jun 01, 2017 9:15 am
Re: Sftp put problem
the problem accuar again
cozsftp> cd /Folder/Folder2
cozsftp> put '//xxx.xxx.xxx' test1.txt
Uploading //xxx.xxx.xxx to /Folder/Folder2/test1.txt
ZosDataset$I¨: Opening dataset xxx.xxx.xxx for rea......
remote open(Ü/Folder/Folder2/test1.txtÜ): No such file or directory
this is certain that , there is folder on remote folder
application server delete folder which put from host
host -> windows sftp server -> application server
is that about it?
regards
Cagatay
cozsftp> cd /Folder/Folder2
cozsftp> put '//xxx.xxx.xxx' test1.txt
Uploading //xxx.xxx.xxx to /Folder/Folder2/test1.txt
ZosDataset$I¨: Opening dataset xxx.xxx.xxx for rea......
remote open(Ü/Folder/Folder2/test1.txtÜ): No such file or directory
this is certain that , there is folder on remote folder
application server delete folder which put from host
host -> windows sftp server -> application server
is that about it?
regards
Cagatay
Re: Sftp put problem
This message:
remote open("/Folder/Folder2/test1.txt"): No such file or directory
means that Co:Z SFTP sent an FXP_OPEN command to the remote server and that the server returned an error "No such file or directory".
Check the server logs for the failing cause or reason.
remote open("/Folder/Folder2/test1.txt"): No such file or directory
means that Co:Z SFTP sent an FXP_OPEN command to the remote server and that the server returned an error "No such file or directory".
Check the server logs for the failing cause or reason.