DSXchange

In Modify stage, it's substring[ startpos , length ]( string ) In Transformer stage, choose Substrings from the operator menu in the Expression Editor - it's the conventional square bracket notation also used in server jobs. For more detail search in Parallel Job Developer's Guide (parjdev.pdf) for ...

Not sure what you're asking. There is no limit to the number of environment variables. There is no limit to the number of job parameters, whether they are environment variables or not. But the more you have the longer it will take to load them all. The correct number is "just the ones you need".

So?

Trim trailing white space if that's necessary.

"12345" can be converted to an integer whether it's left- or right-justified.
Trim("12345 ") can also be happily converted to an integer.

Status 0 means "running".
All the status codes are documented in JOBCONTROL.H, which you will find in a subdirectory called dsinclude in your project.

Use ODBC stage. Method is Stored Procedure. Column definitions must match recordset used/generated by Stored Procedure.

First run of the day, run the "clear file" job first. On subsequent runs, don't. It's that easy!

Near the end of the job sequence's log is an entry containing "summary of job sequence run". Most of what you need will be in that entry.

See immediately preceding post. You create ONE job. You check the Allow Multiple Instance check box in its job properties. Recompile. When you run the job there is a new field, InvocationID. That's where you tag it if running from Director. If running from dsjob, use the "dot" notation mentioned ear...

DSD.UVOpen Unable to open file Hash#NUMBER#. The fact that a job parameter reference appears in the error message means that the job parameter has not been resolved. Try a View Data on the Hashed File stage output link. Does this parameter get prompted for? If not, it means either that the job para...

It's not necessarily the number of jobs. It's the number of processes (whether DataStage processes or not) that can cause this. It can also be abnormal amounts of time waiting for a resource (for example, a database instance may be extremely busy, not have enough listeners, or simply not be started)...

That explains the restriction to SMP. The DataStage Engine run machine (which runs BASIC things) exists on that machine, and is globally accessible by any process on that machine. In a cluster you would have to have the DataStage Engine installed on every machine, which could not be guaranteed.

Are there a lot of other processes on the system when this error occurs? The not enough space message may relate to the process table. Check also to determine whether your inode table is full for the file system in question.

On the link between the Transformer stage and the BASIC Transformer stage is there a "collection" (fan in) icon? Or is there a "preserve partitioning" icon? This will tell you whether the BASIC Transformer stage runs in parallel or sequentially.

If it's the same job it must be capable of multiple-instance running, and you must start the three instances with unique instance IDs. An instance ID can be any string, so you can make it meaningful within your overall scheme of things.

I note that you are using version 4.x. Since then there have been many major changes; release 8 is just around the corner. Visiting Ascential's home page is one place where you can search for press releases for the intervening releases, and you may be able to request that they send you the readme fi...