DSXchange

It won't work in EE (unless you use a BASIC transform stage) but since you have the row-generation stage you don't need this functionality.

rockr - timestamp contains a time component. If your data doesn't have it you will need to add it, as DSGuru2B has already shown.

can you "ping" the DataStage server from the clients?

The Modify stage allows only one action to be done per column.

Does this occur on a data column or one that is generated in the SQL? If the latter, can't you CAST it to the appropriate datatype?

You are probably attaching to the job itself in the after-job routine. Instead of using DSAttachJob(), just use the mnemonic DSJ.ME for the job handle.

Talk to your UNIX system administrator and get permission to use and schedule jobs using "cron". Once that access is granted you will be able to schedule in DataStage.

If you use the same SELECT for the lookup several times then it is best to perform the database lookup once to a dataset or lookup and then use that for the 2nd and further lookups.
The point of the previous posts is that a "sparse" lookup into a table is to be avoided unless absolutely necessary.

I haven't seen that error message and am unclear how you could be generating it. The Before/After job routines have 2 parameters, the first is input to the subroutine and can contain whatever you wish while the 2nd is returned and contains the ErrorCode. If you wish to pass more than one value to a ...

Satadru,

The Search facility for keyword "-14" returns 240 threads on this subject. Add that to the 1-minute wait period and you have your answer.

No - as Ray already stated, if you use a database for a lookup the engine will load that result into a virtual dataset and do the reference from that.

The two messages are not related. Look at your function calls in the transform stage, there is an error in the logic that is not syntactical (which the compiler would have found) but does prevent execution. This could be something like a bad data type or a function called with incorrect number of ar...

The job is aborting because you have hit the 50 warning limit. Your two options are to increase that limit or to get rid of the warning message. Since the message is quite clear and easily fixed I would opt to correct the cause instead of hiding the symptoms. Do you know what the offending character...

If your lookup contains only 500 records then you are much better off using a normal lookup instead of a static one.

This means that the file is corrupt, for some reason. The quickest solution is to save-as another name, delete the bad job, then rename to the correct name. Do you have any idea what could have caused this corruption?