DSXchange

Sometimes when you post to a thread posting.php times out. Do not Submit again - your post got there OK. The problem seems to be with updating something in the underlying database. Instead, use the Back button on your browser to return to your message (apparently unposted), then click on the link th...

I am unaware of any mechanism for preventing Transformer stage from generating warnings.

I had assumed, because you said "tried the following with Modify too" that you had a Modify stage in the job. Well, now you do. Leave it there - it doesn't eat much.

This looks like default value substitution. First, though, can you be certain that the substitution is occurring after the Join stage, not before? If so, can you check these fields' extended properties to determine whether a Default is specified for the particular data types? A "default default" suc...

Have you tried using a custom trigger based upon the routine's return value?
Or an explicit Failure trigger so that you're explicitly handling the "failure"?

Or, instead of the lcd, a UNIX cd command in the script but before the ftp command.
Or, instead of that, a UNIX cd command followed by the ftp command as the command to be executed from the stage.

The cd subcommand within the here script is still necessary; it changes directory on the remote machine. But a local cd needs to be done somewhere.

Arnd, please read Task 2 in the original post again. It is to that that I was reacting.

In the script you could include the cd command before the ftp command, or execute an FTP lcd subcommand once within the here script.

Add an extra Specification to the Modify stage. This new Specification contains the single word NOWARN.

echo as a Filter command will close the file and therefore break the pipe. You need to use echo in before/after subroutines, not in a Filter command.

COMMON is a reserved word. Can you try using a different name for your parameter set?

This is why we seek the output from DESCRIBE - to see what's really there.

Never assume anything, even that DataStage imports table definitions accurately every time. Particularly not via OCI plug-in.

Executing the cd command in a separate Execute Command stage is a waste of time and effort. It opens a new shell, executes the cd command in that shell, closes the shell, and returns. The cd command must be part of the command sequence that runs the script, or within the script itself. For example: ...

There are four major resources: CPU, memory, disk throughput and network throughput. Bottlenecks may also occur in database servers due, among other reasons, to locks. Do not concentrate solely on memory. A system that is CPU-bound may also be memory-bound, but you would not detect the latter until ...

Without a baseline set of measures from the "good times" it's not going to be a lot of help. Your system administrator will be able to brief you on the various tools and techniques; you might like to review the man pages for the following commands: top iostat vmstat netstat Of course it may have not...

Change your line terminator to DOS-style in the stage properties of the Sequential File stage.