I am trying to pass parameter filename thru dsjob command from unix shell script. dsjob command I wrote is
dsjob -run -param paramname="paramvalue" <projectname> <jobname>
it is giving the error -3 getting information for parameter
status code = -3 DSJE_BADPARAM
Please help.
passing parameter thru dsjob
Moderators: chulett, rschirm, roy
Welcome aboard! :D
That error means the parameter name you've supplied does not exist in the job. Make sure you've spelled it correctly - case and all. And you've got the right job!
That error means the parameter name you've supplied does not exist in the job. Make sure you've spelled it correctly - case and all. And you've got the right job!
Last edited by chulett on Thu Mar 22, 2007 4:44 pm, edited 1 time in total.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
padmaguntur
- Participant
- Posts: 2
- Joined: Thu Mar 22, 2007 2:40 pm
The parameter name you passed on the command line as paramname in your example cannot be correct or it would not have given you that error.
Whatever name you've assigned to the parameter in the job - name, not prompt or default value - is what you should be using here. And no, the command line will not recognize nor need the '#' signs.
Whatever name you've assigned to the parameter in the job - name, not prompt or default value - is what you should be using here. And no, the command line will not recognize nor need the '#' signs.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
ray.wurlod
- Participant
- Posts: 54595
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Parameter names are case sensitive. You won't get DSJE.BADPARAM (-3) if you spelled and cased it correctly. Check again.
You probably don't need the value in quotes, either.
You probably don't need the value in quotes, either.
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.
