DSXchange

That message can indicate that you've used the variable name ANS rather than the name Ans. Variable names are case sensitive. It can also mean that there is a path through your code in which the Ans variable is not set at all - maybe you failed to open the "table" (directory) or to read the "record"...

The 'Execute Command' stage runs fine. But nothing happens really.

What's wrong with this picture?

Does it run really fast?

I could not find uvwalk in the bin directory,if searched in /ds/Ascential/DataStage/DSEngine/bin should i have to find it any where else (i cant stop rolling my eys) regards kumar If you tell me how you can get to a DOS prompt on your UNIX machine I will revert with where you can find uvwalk on tha...

Christina, please check this post for an explanation. In your case it's not exactly the same, but your working directory for you is not the same as the working directory for a DataStage process. To make this really clear to you, set up a before-job or before-stage or after-stage or after-job subrout...

As my apple-cheeked old grandmother used to say, "courtesy costs nothing".

I discovered an answer to this one accidentally, fortuitously in a class that Vipin was attending. The problem was that the Repository title bar was parked behind the toolbar, and could not be accessed. Curiously, making the toolbar disappear via the View menu didn't help, and making the Ascential b...

Not until you tell us what's in /home/dsadm/Ascential/DataStage/Scratch/ora.4195.879789.1.log file.

You use job parameter references in a WHERE clause just like you use them in any passive stage, the job parameter name - correctly spelled and correctly cased - surrounded by "#" characters. The examples earlier illustrate the technique.

Welcome aboard! :D
From memory (I'm not presently working in the EE environment) there are two generic environment variables you need. One is APT_COMMIT_ROWS (or something like that), the other is APT_COMMIT_INTERVAL.
Check the Parallel Job Developer's Guide for full details.

Do use Search. This has been explained in deep detail already on this forum.

You can split the original source into multiple rows using, for example, a Copy stage or a Transformer stage. Then performing separate lookups on separate streams is straightforward.

Setting a default value explicitly for this column should cause the warning to disappear.

Curiously, perhaps, a re-boot will not help in this circumstance. A DataStage records its status periodically in a table in the Repository. So do some of its active stages and "resources". This information is read by the Director client. When people report that a job is not terminating, it usually m...

It is a partitioned table? If so, have you specified the Partition Table property in the Oracle Enterprise stage?

I notified "them" some time back, and continue to await the courtesy of a reply.