datastage error: User Id is a required stage property

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
Champa
Participant
Posts: 88
Joined: Wed Dec 14, 2005 1:44 pm

datastage error: User Id is a required stage property

Post by Champa »

Team,

in datastage director I am getting the following error while running my job.

User Id is a required stage property

Any suggestions.

Thanks.
Champa
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Pretty much exactly what it says: you have a stage in the job that requires a User ID - typically a Database stage - and you haven't supplied one. Shouldn't be all that hard to track down...
-craig

"You can never have too many knives" -- Logan Nine Fingers
Champa
Participant
Posts: 88
Joined: Wed Dec 14, 2005 1:44 pm

Post by Champa »

Team

I got rid of that error by changing my parameter UserId to something else.

Thx
Champa
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

No you didn't. You got rid of it by supplying either a value or a job parameter reference to the missing UserID property.

If you think the issue is resolved, please mark it so, to assist future searches.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
dsscholar
Premium Member
Premium Member
Posts: 195
Joined: Thu Oct 19, 2006 2:45 pm

Re: datastage error: User Id is a required stage property

Post by dsscholar »

Just wanted to know, how where you supplying the user id, was it a parameter or was it hard-coded...
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

It doesn't really matter; it has to be supplied
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Exactly... and it doesn't even need to be a legitimate value to make that particular error go away - it just needs to be non-blank. Of course, adding a bogus value will generate other errors... :wink:
-craig

"You can never have too many knives" -- Logan Nine Fingers
Champa
Participant
Posts: 88
Joined: Wed Dec 14, 2005 1:44 pm

Post by Champa »

Team,

I had a parameter UserId & supplied a value.

Job was working fine up untill I started getting this error.

I had not made any other chanhes.

My lead suggested changing the parameter from UserId to something else & it worked.

I cannot explain what happened.

Thanks
Champa
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

My guess is that UserId is used internally as a variable name therefore making it the name of a job parameter introduced ambiguity into usage of that particular variable.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply