Re: Efective Error Trapping
Please read documentation:
https://winscp.net/eng/docs/guide_automation#results
https://winscp.net/eng/docs/guide_automation#results
- martin
Post a reply
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
Topic review
- Arvada Joe
Efective Error Trapping
Hi Prikryl,
I want to be able to see what my error is in a script. If I get an FTP connection I know the code is 0, if not it's 1.
Here is my simple bat file:
copy d:\ears_extracts\icr\out\*.csv
copy d:\ears_extracts\icr\out\*.csv d:\ears_extracts\icr\holding_area\*.csv
WinSCP.exe /console /script=abie.txt
del csp*.csv
del d:\ears_extracts\icr\out\*.csv
What would be an effective way to trap the error code so I can see what it is and put out a sucsess or failure message to a logfile?
Thanks
I want to be able to see what my error is in a script. If I get an FTP connection I know the code is 0, if not it's 1.
Here is my simple bat file:
copy d:\ears_extracts\icr\out\*.csv
copy d:\ears_extracts\icr\out\*.csv d:\ears_extracts\icr\holding_area\*.csv
WinSCP.exe /console /script=abie.txt
del csp*.csv
del d:\ears_extracts\icr\out\*.csv
What would be an effective way to trap the error code so I can see what it is and put out a sucsess or failure message to a logfile?
Thanks