DSXchange

We have a very odd scenario here that I cannot figure out and hope that someone here might solve it for us or point us in the correct direction. We've finally narrowed down the issue and think it has to do with mount points. We've installed DS on a new AIX machine and have created several projects a...

What do you mean by "job is not responding"?

What does the DBA say about DB/2 activity? Has the UNIX process stopped running? Has the Director log stopped updating after 4 million rows? Has this happened before? Has the job run successfully before?

This is a new feature at 7.5

Call up the multiple job compile from the manager, you can select sequences there.

Remove columns one by one until the error goes away. Then post what the column data type is and the value for the error.

No, there is no way to find out who manually cleared a log or which process triggered an autopurge, this information is not part of the audit trail.

DSExecute exists and works on both Windows and UNIX.

Can you not just use normal ">" and "<" conditions to check whether your search string is less than one and greater than the other?

I agree with Kim - DSLogFatal() should be used in your case. The warnings have more to do with having devlelopers avoid terminating jobs than with any side-effects involved in using the function.

A transform stage is not the place to do this type of work; it will get executed for each and every row. Your logic belongs in a job sequence and then you pass the information via parameters to your actual job.

In the BASIC language you can do this, but when using the construct in DataStage jobs the result of the IF-THEN-ELSE is assigned to a variable, i.e. it is the right side of an "=" statement. Because of this an IF clause must assign a value to both outcomes of the condition.

What do you mean by "propagate fileA"? You can issue a call to a SHell to see if a file is empty and use that true/false value in a job sequence to do a conditional branch.

Sudhakar,

The error message

Lookup_21,1: Failed a keylookup for record.

should mean something to you. This is not a DataStage problem but a data problem. Either add the key to your lookup or change your logic for failed lookups.

I have (in days past) used DataStage to read files directly from a UNIX SMTP system, but it is much better to use a script and someofficial mail reader program. You can issue a DSExecute to a shell and capture the output of the mails contents into a DataStage job.

This error does seem odd. Could you post the full error message from the log, perhaps we are missing something.