I am trying to run the job from command prompt and i am getting this.
Parameter file below is given correct path. Job has been kicked off but getting below error.
From command prompt
./dsjob -server SERVERNAME-user userid -password pwd -run -param ParameterFile="SrcDir/ETLParamFile.dat" -warn 5000 project JOBNAME
In director logs
JOBNAME..JobControl (fatal error from Msg): Could not create the file: /JOBNAME.wrn
No, the batch job is not working from director too.
The individual job runs fine in designer and from director. But when i try from batch job to invoke individual job it fails with the message described in my first post.
Another thing i learnt was, If the batch file is named as 'Batch::ProcessJob' it is not working. If i name it as 'ProcessJob' it works fine from director.
I am not creating any files. Looks like by default batch file execution causes the creation of the files at root and since my user id doesn't have access permission it is failing.
In execution wise how Batch:: is different from regular job execution?
Execution-wise Batch:: is just the same as a sequence job which, in turn, is the same as a server job that contains no stages but only a job control routine.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
I should be able to pass the parameters to a job from batch Job( can call this as batch job with out naming it as Batch::?) but when i try the same from sequencer to job i am not getting the parameters.
Am i suppose to be running it from some where else other than /dvl/etl/Ascential/DataStage/DSEngine/bin to avoid creating the log/warn files in root directory?
Please forget about the syntax problems here...this is display/copy paste issue. Otherwise it should have been thowing different syntax related issue.
The problem here is trying to kick off the job, but due to not able to create the .wrn or .log file it fails.