DSXchange

I guess your version doesn't support that syntax. Try this instead and see if it will take it:

Only because you'll probably fix your problem in the process. You really need to double-check everything in the stage - typical reason for a 'field does not exist' error is because (oddly enough) it doesn't exist. And it doesn't because you are not connecting to the table you think you are. Make no ...

What exact version of DataStage are you running?

It's one of the optional plug-ins, so it sounds like whomever did your Server installed decided not to install it.

Best to rerun the Server install, it will default to a 'maintenance' mode and allow you an option to install any missing plug-ins. This rather than the package installer.

What database?

if anything fails and we bring it in with new version and then u have to change the sequencer to pick up new version as Seq is not picking up new version by itself we tested it number of times. Are you SURE that you are linking the Job Activity stage to the unreleased job name? ? I would sure think...

Forget the whole 'releasing' thing. Yuck. Search the client cdrom and you will find Version Control there, install it on whomever's PC will be doing job promotions. In your version it won't show on the auto-run menu, from what I recall. You will then be able to mark jobs as 'Read Only' during the pr...

Releasing jobs is so old school, I haven't done that since Sequence jobs existed so not sure if they 'understand' them or not. I'm not even sure what advantages they bring anymore or how they could possibly outweigh the disadvantages of using them. From what I recall, back in the day you still just ...

Or you're not in the table you think you are. Double-check everything.

What database? Sometimes that's because it is a reserved word and you need to quote the field name in your sql.

Now you need to follow DSGuru's advice re: the @FM characters. If you are using a Sequence job and $CommandOutput to populate the parameter, try changing it to $CommandOutput<1> and see if that does the trick by itself.

In that case, it sounds like a bug. There is a patch on the IBM Information Integration Solutions Portal that may be what you need: User-defined SQL in Oracle OCI Stage ALL DataStage 7.5.1 05/26/2005 e73423_ALL_751.zip Description: Oracle OCI stage (ORAOCI9) incorrectly binds the lookup column value...

The three ODBC stages as mentioned connects to 3 different tables in an Oracle database and the output is given to a table in a different Oracle database. Doesn't really answer the job design question. Please list all of the stages used in the job. An 'ascii art' version can be posted if you use Co...

Sure. Just 'Load' it or drag the metadata to the link from the Repository Browser. Or 'Propagate' the column definitions through a Transformer.

Excellent. Let us know if you have any other questions while you work through this. If you get it worked out, we'd appreciate it if you could do two things:

1) Post your final solution, how you controlled the lists, for future searchers.

2) Mark the post as 'Resolved'.

Thanks!