DSXchange

I believe you need to use both the functions. First to truncate your decimal to a precision of 2 and then convert it to dfloat. Specify a stage variable with length that is equal to the length of your float target field. Set the precision to 2. Specify the derivation for this stage variable say Trun...

head and tail commands would work on a unix box and not on a windoze box, unless MKSToolkit is installed.

Nothing out of the box to add months. You can add days but not month. You can, however, create your own C routine to do that. It should'nt be hard.

satyanarayana wrote:Filterstage as good performance compare to Trans..

That statement does not hold true for versions 7.5 and higher.

There is also AddMonth() routine by Ray. Search will turn it up.

O ok. O yea, thats right, all present sequence jobs will remain unchanged and new ones will be affected. Thanks for the correction Craig.

Are there any other error/warning messages?
Have you ever successfully compiled a job with a transformer in it? Its more than likely that your C compiler is not set up. I dont see any reason why a transformer cannot sit between an STP and sequential file stage.

Wrong syntax. There is no "fix_zero" in DecimalToDecimal(). Just give the "trunc_zero".

In that case the routines and your jobs may not have design info and just executables.

What routines specifically? I just double checked and all my routines have visible code.
As for your second error, search on the error message. This has been discussed before.

Use DecimalToDFloat() or DecimalToDecimal() with "trunc_zero" specification and set the precision to 2.

"" is not a NULL and certainly not a valid timestamp and hance your error. Use SetNull() in transformer or make_null() in modify stage.

Doing it in the Administrator will set all sequence jobs as 'restartable'. If only the current/few sequences need to be restartable, then you can do it by checking the same option in the job properties of the sequence job.

Yes. SQL will be surrounded by hashes ofcourse telling the engine that it is a parameter.

I doubt it. If you are really eager to get rid of 10 jobs and keep one then you can get away with it by maintaining two jobs. Job1 will load your source file into a temp table. Job2 will take in user defined sql that joins the tables and spits out the result to a flat file. You can parametrize the u...