DSXchange

No, the arguments to Index() must be a string, another string and a positive integer. The third argument is an occurrence. You are searching for a substring within a string. The first occurrence of the substring, the second occurrence of the string, and so on. Searching for the -3rd occurrence does ...

Set the auto-start property in the dsdlockd.config file to 1. Restart DataStage - the deadlock daemon will start and remain logged in. It wakes every 15 minutes, or such other interval as is specified in the dsdlockd.config file. Releasing a job is the old-fashioned way of creating a versioned, read...

Or just change the Character Set property, at approximately line #4 in the DSX file, so that it is compatible.

1. No. The command to schedule anything is AT.
2. No. The arguments are not documented.
3. See 1 and 2.
4. Use the dsjob command.

I understood that these properties could only refer to the nodes/partitions in the current configuration file.

If it's to be a reusable reference table, a Lookup File Set may be preferable to a Data Set, as the index (hash table) on the key gets pre-built when the Lookup File Set is created.

That you've used a singular pronoun ("it") to describe your server rules out MPP.

But on Linux you do use gcc.

The easiest way to do it in DataStage would be to select that starting value from the target table in a reference input to a Lookup stage, with a constant key, and using Entire partitioning to get it onto every partition. SELECT 'X' AS DUMMYKEY, MAX(KeyCol) + 1 AS NEXTVAL FROM targettable Th...

What does the source "timestamp" look like? VarChar(16) is quite an unusual data type for a timestamp.

Verify that you're getting the correct source data and results by creating a small test job that sends its output to a text file, and investigate that file.

I'd use an Execute Command activity with the command test -z filename

The reason there's a 1MB upper limit on row buffers is that no-one figured anyone would need anywhere near that. The default limit for ODBC connections, for example, is 8KB per row.

Do you have the DataStage deadlock daemon running? This will periodically clear the locks held by redundant processes.

Did you look in and around line #272 of the RT_BP3988/JOB.1414850643.DT.1430025947.TRANS1 routine?

Welcome aboard. :D

Why do you assert that DataStage will only use 2GB of memory? How did you measure this? DataStage, running multiple jobs, will run multiple processes - did you count the memory consumption of all the uvsh or dssh processes, all the dsapi_server and dsapi_slave processes?