DSXchange

If you use shell scripts and cron then you might as well schedule the jobs in the director, since that is the scheduler used by default in DataStage.

Let's take a step back and deal with the rpc questions later. If you can login to the project using the graphical tools (Designer, Director, Manager and Administrator) then your connectivity is set up correctly and you don't need to delve into the internals of how DS communicates between client and ...

If you only see one row, does it contain just the data for the first row in the correct format? Have you set your final delimiter to <cr>?

Have you set your view data options to limit to 1 row?

Are you viewing the data in the output sequential stage? If so, perhaps your aggregator only output one row?

Yes, the Director has a number of files open but it won't have several log files open concurrently. Also remember that these file units are shared across all users, so if you have several directors and running jobs open using the same hashed files they share units.

1) DataStage will pass the data through unchanged unless you explicitly modify it - so the contents, if encrypted, will remain so. 2) As far as I understand it, ICSF encryption software has numerous user exits, so you need to identify the appropriate routine(s) you need to use and write your own cal...

Good work, DSguru2B!!!!

What is OutDate.DATE defined as and with what precision?

phanee_k already pointed out your error. Check your datatype for sv2; it is an integer (or date) and you are assigning a string to it.

It is very difficult to predict disk usage and memory usage accurately. Luckily, much of it is unimportant. If you look at the stages you can see that you have a lot of control of memory by controlling the buffering. Temporary disk space is under less control - in many cases any temporary usage will...

That is hard to say, as it depends on your implementation. In some cases it is better to create hashed lookup files for this and changing the lookup from a range to a simple unique keyed one [at the cost of making the data volume much larger]

Hashed file lookups do not support a BETWEEN type of lookup. You can use the SQL query on a hashed file (ODBC or UniVerse stages), but the performance is going to be abyssmal (full table scan for each row). There are a number of solutions for better performance to this type of problem that have been...

Round robin will work at the output stage, but the entire partitioning you specified earlier in the data stream has corrupted your data (except for cases where you have only 1 node in your APT_CONFIG file). Correct that error and don't change partitioning schemes unless you need to. Why not do a rou...

Perhaps a spelling or case difference. Load the dataset column metadata from the dataset in the manager, then use load that into your dataset stage in the job instead of typing the field name.