Command line error starting DSJOB !!

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
roosenr
Premium Member
Premium Member
Posts: 15
Joined: Thu Jan 16, 2003 2:33 am

Command line error starting DSJOB !!

Post by roosenr »

Hello,

we start up a datastagejob by automatically by calling a telnet session from within an Access application.

The command we use in during the telnet session is the following:
***********
dsjob -run -param sdate=20030101 -param edate=20031231 -param NP=NP -param NH=NH DSFINT SEQ1NPNHNV{ENTER}
***********

it gives the following error:

**********
Error -3 getting information for parameter 'sdate'

Status code = -3 DSJE_BADPARAM
**************

If we change the command without the parameters, everything runs ok, but it takes the default values ofcourse of the parameters defined in the job.

********
dsjob -run DSFINT SEQ1NPNHNV{ENTER}
********


Can anybody tell me what is wrong with the command (probably something to do with the parameter definition)...?


Thanks,

Rogier Roosen

PS:

sdate and edate are defined as integers and NP, NH are defined as strings...
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Sorry, have to ask... get the obvious out of the way first.

Parameters are case sensitive - are both 'sdate' and 'edate' the *names* of the parameters (not the prompt) and all lower case? [:)]

-craig
roosenr
Premium Member
Premium Member
Posts: 15
Joined: Thu Jan 16, 2003 2:33 am

Post by roosenr »

Already found it myself!

certain parameters where strings so they had to be put between quotes!!so: -param parametername="parametervalue"
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

The error message (and DSJE.BADPARAM code) should have alerted you to the fact that something was wrong with one or more parameters. That is reported the error for the sdate parameter is merely an artifact of that parameter being the first in your command line, it was the point at which the command parser gave up.


Ray Wurlod
Education and Consulting Services
ABN 57 092 448 518
Post Reply