DSXchange

Create an external routine/script and use that routine to call DataStage jobs, passing values to that particular job variable.

Go to the UNIX prompt, and verify that the file exists on that directory.

ulimit -a. Verify that you (and dsadm) have the ability to create files that large.

It really sounds like you got yourself in a really nasty feedback loop somewhere. Hitting on my sources, there appears to be a lack of mention about this problem.

Hit up Ascential Support, even though I doubt they would be able to duplicate your problem. But then, you may get lucky.

Read up the Parallel Development Guide on 'Copy Stage' and 'Funnel Stage'. For Table 4 - Copy - 21 links -> Funnel -> output For Table 5 - Copy - 18 links -> Funnel -> output As for Table 2 and 3, the same thing above can be done, with a remove duplicate stage, or maybe a transformer, or other optio...

What does your source file use to say, 'This field is a null?'

1. Did you read the Install and Upgrade Guide document?

2. Are you installing using the root account?

Edit: Solaris 5.10? There is no such thing. The only supported version of Solaris for DataStage is 2.8 and 2.9 (8 and 9).

You also need to remember, not only ONE process is used for sorting, especially with multiple nodes. It is not a cumulative value, but an individual value you are setting there.

More information here:

http://gcc.gnu.org/

You can also do a google search for "GCC".

64 bit clients are NOT supported for use with DataStage at this time. There may be several client-specific releases that tentatively support that, but as far as I know, you must use 32 bit clients.

Sorry.

Are you using APT_IMPEXP_ALLOW_ZERO_LENGTH_FIXED_NULL? Or are you using a specific field information to define NULL values from input sequential file?

How do you identify whether the input data on a file is a null?

Could use Pivot Stage. Better off using Copy Stage -> Funnel.

And when you migrate your job with that environment variable to other platforms or projects that have different values, your job still have the default value preserved -- over-riding what the project/system/universe/everything/42 values are. This is why I advise all of my clients to not rely on proj...

Unfortunately, C++ is an ever-changing language, and not stabilized by any means. One version of a compiler on one platform can be entirely different than the same version on another platform. So the advice is to ONLY USE THE SUPPORTED COMPILER NOTED ON YOUR INSTALL GUIDE. In other words, you're not...

Please paste your SQL statement. I have a sneaking suspicion about something.