DSXchange

fork failed can also be that the process table has become full. Rare, but possible. And only partially to do with disk space.

binujnair2 wrote:Is there a way to bypass this pre-compilation error apart from changing anything at the parameter set level?

No. You actually have a duplicate parameter name. You must get rid of it.

What happens if you specify the IP address, or the shortened hostname, for the machine hosting the server?

On Windows NLS_LANG needs to be set, with other environment variables, via Control Panel on the server. Windows implementation of DataStage does not use a dsenv script.

Apart from that, what Arnd advised is correct.

You should really change UVTEMP (a value in uvconfig) as well.

Consider a separate job to read the link row counts from the completed job and put the row into the table.

Create a generic routine to read a link row count, given the job name, active stage name and link name.

Yes, but you've already marked the thread as Resolved, so why don't you tell us?

This will assist anyone who encounters the same problem in future.

Yes, it's a silly error, but we all make those, especially while we're learning. Don't be embarrassed about posting something that will help others.

Welcome aboard.

There's a Search option in the DSXchange main menu and, curiously, you're not the first to have reported this. May I suggest an exact search on "Cannot open executable job file RT_CONFIG" ?

May I suggest a couple of minor improvements? One is to use the special assignment operator (:=) which is more and more efficient the longer the string gets. The other is to use a fixed width format for each Unicode codepoint. FUNCTION UniConv(TextIn) TextLen= Len(TextIn) NewText = "" For ...

OK it can't find warning.gif - that may mean that warning.gif does not exist, which seems unlikely given that other clients can save reports, or that you may lack sufficient permission to get to or read warning.gif.

OK, what do you think might be wrong?

Does the word "locale" trigger any thoughts?

Hint: Check NLS settings.

Yes, in any form of UNIX (including Linux) the file name is /dev/null. It remains the case that you must append to it, not overwrite it.

The second question first. If the sequence is restartable then you don't need to do anything special - the code within the sequence looks after restarting skipping any checkpointed activities. There is no command line to give you all dependent items for a job. That information has to be extracted fr...

Not directly, but you can use a Sequential File stage to append to the file .\NUL (which exists in every folder).

Tip: don't try to overwrite .\NUL - you have to append to it.

... but not on a Windows server unless there's some kind of UNIX emulator, such as MKS Toolkit, available.