Batch file problem
#1
Batch file problem
Trying to run an ftp session via a batch file, it works fine when I log on and run it manually, however when I run it via Tivoli or as a SQL server job it conks out, the log doesnt appear at all in TWS but it does in SQL server, looks like this,
The files are named in a standard way, STABBDLXY, where the X denotes the origin of C:\WINNT\SYSTEM32>REM the data, i.e. Mainchain (UK and Jersey... Process Exit Code 1. The step failed.
Doesnt even get to the complicated bits.
The job fails at the top of the script which is just comments, I think it may be a user permission issue but the same account runs batch files on the same server.
Any ideas gratefully received.
(unless its buy a Unix server, already been suggested but you can't run Sql server on Unix !)
The files are named in a standard way, STABBDLXY, where the X denotes the origin of C:\WINNT\SYSTEM32>REM the data, i.e. Mainchain (UK and Jersey... Process Exit Code 1. The step failed.
Doesnt even get to the complicated bits.
The job fails at the top of the script which is just comments, I think it may be a user permission issue but the same account runs batch files on the same server.
Any ideas gratefully received.
(unless its buy a Unix server, already been suggested but you can't run Sql server on Unix !)
#2
Scooby Regular
Join Date: Nov 2001
Location: Leeds - It was 562.4bhp@28psi on Optimax, How much closer to 600 with race fuel and a bigger turbo?
Posts: 15,239
Likes: 0
Received 1 Like
on
1 Post
Send me the details via email and Ill help you out
It will be quicker and easier!!
david.wallis@callcredit.plc.uk
David
It will be quicker and easier!!
david.wallis@callcredit.plc.uk
David
Thread
Thread Starter
Forum
Replies
Last Post