Argument Not Optional --- Director closes after this error

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
vcannadevula
Charter Member
Charter Member
Posts: 143
Joined: Thu Nov 04, 2004 6:53 am

Argument Not Optional --- Director closes after this error

Post by vcannadevula »

We installed the 7.5.1 recently. I am trying to run a job from director using the dsadm user, iam getting the following error

Run-time error '449'
Argument Not Optional


This is a sequence job with one job parameter. When i copy and paste the parameter and try to run, i am getting this error and later the director is closing.

If i validate the job and then run, it is running fine

Any one has any thoughts, why this is happening
kcbland
Participant
Posts: 5208
Joined: Wed Jan 15, 2003 8:56 am
Location: Lutz, FL
Contact:

Post by kcbland »

I don't know if the job matters.

Can any other users run jobs? (Identifies if it's a userid issue)

Is this the first job being run in this new install? (Identifies installation issue)

Does any other project work? (Identifies if it's a project or permissions issue)

Can you start the job using dsjob command line interface? (Identifies if it's a client issue)
Kenneth Bland

Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
vcannadevula
Charter Member
Charter Member
Posts: 143
Joined: Thu Nov 04, 2004 6:53 am

Post by vcannadevula »

kcbland wrote:I don't know if the job matters.

Can any other users run jobs? (Identifies if it's a userid issue)

Is this the first job being run in this new install? (Identifies installation issue)

Does any other project work? (Identifies if it's a project or permissions issue)

Can you start the job using dsjob command line interface? (Identifies if it's a client issue)



I gave the dsadm Production Manager. I am having this issue. If i make it a Datastage developer, i am able to run fine
kcbland
Participant
Posts: 5208
Joined: Wed Jan 15, 2003 8:56 am
Location: Lutz, FL
Contact:

Post by kcbland »

Did you read the rest of the questions? You haven't isolated it to a project or all projects? If it's the setup on a project, then you can fix it. If it's all projects for dsadm, that suggests a permissions problem.
Kenneth Bland

Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
vcannadevula
Charter Member
Charter Member
Posts: 143
Joined: Thu Nov 04, 2004 6:53 am

Post by vcannadevula »

kcbland wrote:Did you read the rest of the questions? You haven't isolated it to a project or all projects? If it's the setup on a project, then you can fix it. If it's all projects for dsadm, that suggests a permissions problem.

I have read and it is nailed down to permissions issue.
kcbland
Participant
Posts: 5208
Joined: Wed Jan 15, 2003 8:56 am
Location: Lutz, FL
Contact:

Post by kcbland »

Cool, what permissions needed fixing, the dsadm userid setup or did you have to fix project/file permissions?
Kenneth Bland

Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
salil
Participant
Posts: 46
Joined: Thu Oct 13, 2005 5:41 am

Post by salil »

Is it regarding a parallel job or a server one?
A printer consists of 3 main parts: the case, the jammed paper tray and the blinking red light.
Post Reply