DSXchange

"Strip out all the characters" to me means replace the string with "", which is not (I suspect) what you mean. If you mean strip out all the alphabetic characters, the easiest solution is a Convert() function with all alphabetic characters as its first argument and "" a...

What were their previous values, who advised these changes, and (did they explain) why changing these values fixed the particular problem? For that matter, what was the real, underlying, original problem?

Douglas Adams wrote:If you try and take a cat apart to see how it works, the first thing you have on your hands is a non-working cat.

This is wrong. The first thing you'll have on your hands is a number of severe wounds from cat claws.

The startup script for DataStage is ${DSHOME}/sample/ds.rc - you could put a dsjob command into the end of that (checking, of course, that DataStage has successfully been started).

There is no relationship between the PX licensing and APT_CONFIG_FILE.
You can configure as many nodes as you wish. (The parallel engine must be accessible to each, of course.)

The license is related only to the number of processing cores in the machine(s).

Then, when you get to version 8, you will also have Connectors in the mix.

A1) Look more carefully at the output structure of each.
A2) Please advise in which manual you found the scenarios.
A3) No.

Then my solution will work for you.

Probably not ODBC, which requires that the SP be able to handle a record set. More likely Stored Procedure stage.

The token GET.DSNINFO suggests that DataStage is having a problem finding the DSN named in your job. Is the DSN properly configured and is the DSN properly recorded in the uvodbc.config file for the project?

That would be the ambiguous puzuma.

Almost certainly UniRPC if you're using that method.

Second silly question - what is the maximum number of characters (digits and sign) in a BigInt?

... but searching DSXchange for the SETFILE command will reveal all.

Well done for finding the problem. Please mark the thread as Resolved using the green button at the top of the page.