DSXchange

Reliable?

It works the same way every time.

That is a common definition of "reliable".

Does it actually prevent your job from running?

Prevention is better than cure. Write jobs that don't abort in the first place.

I would expect an error to be thrown if a 32-bit hashed file reaches 2GB.

I must confess that I have never seen Arabic or Hebrew presented left-to-right in server jobs. And the fact that it only occurs when run from a scheduler is even more mystifying. Please keep your support provider (GBM?) involved. For the moment all I can ask you to do is to look for ANY differences ...

Version Control no longer exists. There is, however, a new tool called Information Server Manager that performs similar tasks.

I can not guarantee that. Only the provider of the file can guarantee that.

You can certainly do that too, and I have done. The job sends zero rows into the hashed file.

Is CODE not nullable both on the input and on the output of the Modify stage? What is the data type of CODE ?

After the job is best; I wanted to establish you weren't trying to gather these statistics within the job itself. But beware that the timing still has statistical error for short durations. For a start it's only reported in whole seconds, so (for example) 1.0 means somewhere between 0.5 and 1.5 seco...

Was there any warning logged about export failing? Do you have a reject link on your Sequential File stage?

Ever think about validating the job first time you move into a new environment? This should create the hashed file without the inconvenience of processing any rows.

Welcome to DSXchange, sala'am.

Please compare the job logs when you run the job manually compared with when you run from a job sequence. In particular do you notice any difference in the environment variables or in the NLS settings for any stage?

You do not need a 64-bit platform to use 64-bit addressing within hashed files. DataStage is clever enough to manage it.

Please explain what a "config file" actually means in the context (that of a Sybase stored procedure executed from the command line, presumably). Do you mean a "script file"? Can you provide an example?