DSXchange

If you create a Job Sequence and compile it successfully, you can view the generated code on the Job Properties window Job Control tab.

It's a bit daunting because of all the name re-mappings and computer-generated variable names, but can be edifying nonetheless.

Also check the permissions on the directories where cron and at jobs are stored. Depending on the UNIX, these can be called cronjobs and atjobs or something similar. They are sometimes installed with "other" having no rights at all. To use at/cron, you need r-x permission on these directories.

In the Parallel Job Developer's Guide the page number is 57-130. You can also run jobs from the Director client. You can also schedule jobs from the Director client; the GUI is a front end to the operating system's at/cron scheduler. For information about these, see the Director Guide (dsopsgde.pdf)...

Visit the Ascential web site and look for Education under Services. There you will find the details of courses available and the schedule, at least for some countries. You can also take classes via "e-Learning".

There's no DSN for dwh1 in your odbc.ini file. You need, at a very minimum:
an entry for dwh1 in the [ODBC Data Sources] section
a section for [dwh1]

You have to declare to your job control that the user-defined routine exists and supply argument placeholders and catalog name. DEFFUN RoutineName(Arg1, Arg2, Arg3) Calling "DSU.RoutineName" The "DSU." prefix is DataStage's way of identifying user-written routines. You simply can n...

Your JobB is a job sequence lovingly hand-crafted. :D You've created job control code. All a Job Sequence is is a graphical user interface to doing exactly the same. Obviously hand-coding allows for maximum flexibility and flair, while using a Job Sequence allows for maximum ease of use, particularl...

# as an operator is one of four ways to express "is not equal to" in DataStage BASIC expressions. The others are:

<>
><
NE

@FALSE will prevent any row from being passed along this link. This is calculated before any output column derivations are executed, so that neither the incoming values, nor anything else, can affect that decision. So, in your design, there will be zero rows sent along the first three output links. ...

That is singularly dangerous advice. What about all the other locks that are held by that process? They are there for a reason. The only time that you can safely release ALL locks held by a process is when you can be 100% sure that that process cannot release them itself; that is, when that process ...

Rows per second is meaningless except to compare different runs of the same job processing exactly the same data and provided that there is a substantial volume of data. A job with 200-byte rows might achieve 3000 rows per second. The same job with 2000-byte rows would be expected to achieve about 3...

One workaround that I've used in the past is to use the DOS 8+3 names, which can never have spaces in them. Check also the !GET.PATHNAME and !MAKE.PATHNAME subroutines in the DataStage BASIC manual; these might help you to generate a value that OpenPath() can use. Ultimately, though, eschew spaces i...

Conversion from one parameter to another can be done, for example, in a Routine invoked from a Routine Activity in a Job Sequence. That Job Sequence can then start the job with the resolved values supplied as values for its parameters.

you can try using the DSSetParam with the DSJ.ME job handle in the job control section

This does not work. A running job is not permitted to change its own parameter values.

Welcome aboard! :D While I agree with the sentiment expressed by Ogmios, I will point out that there is a short piece on DataStage architectures in the FAQ forum. There are, in fact, four different architectures that you may need to consider, and that's without even contemplating connections to data...