Argument Not Optional --- Director closes after this error

vcannadevula · Post by **vcannadevula** » Mon Dec 12, 2005 8:16 am

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 · Post by **kcbland** » Mon Dec 12, 2005 8:38 am

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)

vcannadevula · Post by **vcannadevula** » Mon Dec 12, 2005 8:51 am

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 · Post by **kcbland** » Mon Dec 12, 2005 9:04 am

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.

vcannadevula · Post by **vcannadevula** » Mon Dec 12, 2005 9:21 am

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 · Post by **kcbland** » Mon Dec 12, 2005 9:40 am

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

salil · Post by **salil** » Mon Dec 12, 2005 11:19 pm

Is it regarding a parallel job or a server one?