DSXchange

The error message you are receiving is odd, particularly as the data transfer is successful.

If you FTP this file using the command line program, does it generate any warnings or errors?

The Convert() function will not have an effect on the order of columns in a record. If you are using the pipe symbol as a column delimiter and you are changing the whole string then it might have that effect.

The TimeStampFromSecondsSince() will help you. There are 60*60*24 seconds in a day.

Are you communicating between host and UNIX? Is this a text or a binary transfer and is the file large? Does the error always happen or just sometimes?

Yes, you can run multiple instances of DataStage on a given machine.

Check the script, most of the commands set and export environment variables. What other commands do you have that might be generating this error message?

Does that mean you get the error message from the "dsenv" script?

what options did you use during install? What is the UNIX system language set to? What does "env | grep NLS" return?

Not quite sure what the rule is, what is the formula and answer for this age:

Date1 27/06/2008
Date2 01/06/2008

Check out this post for one way to do this.

The vertical tab ASCII character is 11, not 13.

Many conversions from VarChar() to other types, particularly numeric ones, can be done implicitly. You will need to use the StringToDate() function for the date conversion if your job uses transform stages, otherwise the modify stage does conversions as well, but uses other function names and a diff...

We just installed the "namespace" patch (Which also addresses end-of-wave issues) and it works like a charm.

There are many system calls and many ways to interrupt them. Most system calls block out interrupts they can't or don't want to handle. What system call and what interrupt is it in your case? Which stage?

should do the trick for you.