DSXchange

One thing you could do is to preset the PATH environment variable and use an unqualified command name. Another thing you could do is to invoke a shell script that is passed the pathname of the command (including the resolved job parameter) and which invokes the command in question. Show us what you'...

It's also possible for server routines using global cataloging, but I don't want to go there. It's a maintenance nightmare.

If you are going to use the suggested approach then, yes, you would need as many Head stages as there are departments. If you are going to use a Transformer stage it doesn't change - you would need as many output links as there are departments (each constrained on the output row number).

And if, as you subject line suggests, there are different levels and there are repeating groups (arrays) then you MUST get information about these. A COBOL file definition is the easiest way - they can email it to you and you can import the table definition (record schema definition) from the COBOL ...

Check whether the password of the owner of the XMETA database (a user that is created by the installation process) has expired. The install script does not create this user with a "password never expires" setting, so it does expire after whatever expiry setting you are using in Windows user profiles.

Please explain the logic behind this suggestion, and why you believe that doing what you suggest will eliminate the particular warning.

Not true. The BASIC Transformer stage can run in parallel, though every node on which it executes must be on the (a) machine where the DataStage server engine is installed. You can also include server shared containers in parallel jobs, subject to certain restrictions that are documented in Chapter ...

"Consecutively" may be a better word here. They execute consecutively on each node in which the stage's operator is executing. ("Sequentially" implies a loss of parallelism.)

Your reject link needs to have sqlcode on it, then you need to look this up against a table of error codes. This could be a sparse lookup back to the DB2 error codes table (for example).

BIuser wrote:I am logging a case with HAL, and will let you know if we get anywhere with this.

Why not create a suite of DataStage jobs to synchronize the contents of the hashed files? Are the TEST and PROD environments on the same server? Whether you can successfully use operating system commands to move hashed files depends on how they were created. However, simply copying the PROD project ...

In one of the forthcoming training DVDs from DSXchange Learning Center this technique is shown.

Yes, you will need to install CA-FRENCH. This is done via the Administrator client or via the NLS.ADMIN menu in the UV account on the server.

What are the format properties in the Sequential File stage - in particular the Quote Character property?

I don't know why Fix() isn't doing what it's supposed to. You can use