dsjob -run -param file
Moderators: chulett, rschirm, roy
dsjob -run -param file
Im trying to run my job from command line through the command "dsjob"
1.I have created my job params file under location-
IBM/InformationSerer/Server/DSEngine/dsparams1.txt'
2. Im trying to run it with the syntax -
dsjob -run -mode NORMAL -param file='IBM/InformationSerer/Server/DSEngine/dsparams1.txt' GlobalSales_DEV CeilTest
Im running into error-
Error -3 getting information for parameter 'file'
Status code = -3 DSJE_BADPARAM
Any help with the correct syntax is appreciated.
Thanks!
1.I have created my job params file under location-
IBM/InformationSerer/Server/DSEngine/dsparams1.txt'
2. Im trying to run it with the syntax -
dsjob -run -mode NORMAL -param file='IBM/InformationSerer/Server/DSEngine/dsparams1.txt' GlobalSales_DEV CeilTest
Im running into error-
Error -3 getting information for parameter 'file'
Status code = -3 DSJE_BADPARAM
Any help with the correct syntax is appreciated.
Thanks!
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Your job does not have a job parameter called "file". This is what is generating the error when you use this syntax, which is referring to a job parameter called "file".
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 334
- Joined: Fri Dec 01, 2006 5:17 am
- Location: Texas
You want to run the job through command line, the command you are using is perfect but the problem is syntax.
When you give the command 'dsjob -run' the following error occurs:
Invalid arguments: dsjob -run
[-mode <NORMAL | RESET | VALIDATE>]
[-param <name>=<value>]
[-warn <n>]
[-rows <n>]
[-wait]
[-opmetadata <TRUE | FALSE>]
[-disableprjhandler]
[-disablejobhandler]
[-jobstatus]
[-userstatus]
[-local]
[-useid]
<project> <job|jobid>
Status code = -9999 DSJE_DSJOB_ERROR
The commands mention in the square bracket ([) are optional,while the other one's are compulsary, so inorder to run the job you have to use the following command..and the job will run....
dsjob -run PROJECT_NAME JOB_NAME
eg: dsjob -run DS_dev Customer_status_job
When you give the command 'dsjob -run' the following error occurs:
Invalid arguments: dsjob -run
[-mode <NORMAL | RESET | VALIDATE>]
[-param <name>=<value>]
[-warn <n>]
[-rows <n>]
[-wait]
[-opmetadata <TRUE | FALSE>]
[-disableprjhandler]
[-disablejobhandler]
[-jobstatus]
[-userstatus]
[-local]
[-useid]
<project> <job|jobid>
Status code = -9999 DSJE_DSJOB_ERROR
The commands mention in the square bracket ([) are optional,while the other one's are compulsary, so inorder to run the job you have to use the following command..and the job will run....
dsjob -run PROJECT_NAME JOB_NAME
eg: dsjob -run DS_dev Customer_status_job
To me, it looks to be as Kim mentioned - a bunch of parameter values in a file and an attempt to simply pass the filename to the job in the hope that somehow it will magically know what to do with them all. The syntax used was perfectly valid, it just was saying that there is no parameter who's name is 'file' in the job being run.
As our good friend notes, it ain't that easy.
As our good friend notes, it ain't that easy.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
dsjob -file /tmp/serv.txt Domain Server -Command Project
Step 1: I first successfully listed the projects on our server.
This required setting up a /tmp/serv.txt file.
$ cd /IBM/InformationServer/Server/DSEngine
$ . ./dsenv
$ cd bin
$ ./dsjob -file /tmp/serv.txt ANTARES:9080 AURIGA:31801 -lprojects
Where the /tmp/serv.txt file contains:
ANTARES:9080,AURIGA:31801,dsadm,***pwd**
~
"serv.txt" [Read only] 1 line, 43 characters
(Domain,Server,UID,PWD)
Step 2: I then successfully executed a job then a sequence using dsjob.
Note: This required setting up a /tmp/serv.txt file (done in step 1).
$ cd /IBM/InformationServer/Server/DSEngine
$ . ./dsenv
$ cd bin
$ ./dsjob -file /tmp/serv.txt ANTARES:9080 AURIGA:31801 -run -wait -mode NORMAL -warn 0 HMKSandboxv801 rpcE1XA570
./dsjob -file /tmp/serv.txt ANTARES:9080 AURIGA:31801 -run -wait -mode NORMAL -warn 0 HMKSandboxv801 rpcE1XA570_EtlrunTest
This required setting up a /tmp/serv.txt file.
$ cd /IBM/InformationServer/Server/DSEngine
$ . ./dsenv
$ cd bin
$ ./dsjob -file /tmp/serv.txt ANTARES:9080 AURIGA:31801 -lprojects
Where the /tmp/serv.txt file contains:
ANTARES:9080,AURIGA:31801,dsadm,***pwd**
~
"serv.txt" [Read only] 1 line, 43 characters
(Domain,Server,UID,PWD)
Step 2: I then successfully executed a job then a sequence using dsjob.
Note: This required setting up a /tmp/serv.txt file (done in step 1).
$ cd /IBM/InformationServer/Server/DSEngine
$ . ./dsenv
$ cd bin
$ ./dsjob -file /tmp/serv.txt ANTARES:9080 AURIGA:31801 -run -wait -mode NORMAL -warn 0 HMKSandboxv801 rpcE1XA570
./dsjob -file /tmp/serv.txt ANTARES:9080 AURIGA:31801 -run -wait -mode NORMAL -warn 0 HMKSandboxv801 rpcE1XA570_EtlrunTest
Last edited by cundyp on Wed Oct 24, 2007 1:51 pm, edited 1 time in total.
Pete Cundy
Leawood, Kansas
Leawood, Kansas
Response??
I'm not sure if i responded where i shouldn't have but it looked like one of the issues was the dsjob -file $File etc command. I had a case opened with IBM on this an thought it applied to this posting and also posted my results previously on DSXchange.
I'm not really sure what you were trying to tell me??
I'm not really sure what you were trying to tell me??
Pete Cundy
Leawood, Kansas
Leawood, Kansas
Sometimes we get other people on the same team jumping in and continuing a thread, wasn't sure if that was what was going on here. No worries.
Actually, it wasn't an issue with the "-file" option for dsjob. If you look at the original post, you'll see it was a "-param" option for a parameter named "file" that was the issue.
Actually, it wasn't an issue with the "-file" option for dsjob. If you look at the original post, you'll see it was a "-param" option for a parameter named "file" that was the issue.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Answer Clerification
Here is the original post:
2. Im trying to run it with the syntax -
dsjob -run -mode NORMAL -param file='IBM/InformationSerer/Server/DSEngine/dsparams1.txt' GlobalSales_DEV CeilTest
Response:
The IIS 8.0.1 syntax is:
dsjob -file domain server -run -warn -mode project jobname
file = serv.txt containing: domain,server, userid, password
I was just trying to clerify the point that his dsjob -run won't cut it in IIS 8.0.1
2. Im trying to run it with the syntax -
dsjob -run -mode NORMAL -param file='IBM/InformationSerer/Server/DSEngine/dsparams1.txt' GlobalSales_DEV CeilTest
Response:
The IIS 8.0.1 syntax is:
dsjob -file domain server -run -warn -mode project jobname
file = serv.txt containing: domain,server, userid, password
I was just trying to clerify the point that his dsjob -run won't cut it in IIS 8.0.1
Pete Cundy
Leawood, Kansas
Leawood, Kansas
No, the specific problem here is with the "-param" option, his syntax is technically fine.
dsjob -run -mode NORMAL -param file='IBM/InformationSerer/Server/DSEngine/dsparams1.txt' GlobalSales_DEV CeilTest
It found the job, interrogated it for parameters and didn't find one named "file" so threw the error noted above.Error -3 getting information for parameter 'file'
Status code = -3 DSJE_BADPARAM
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers