DSXchange

What else is the machine doing? This code is usually an indication that the machine is overloaded; either the number of processes exceeds the limit, or the total demand for resources hugely exceeds supply. Failure to start in a timely fashion can also be influenced by too small a value for the T30FI...

More information please Jonny. After you compile the jobs, does the status change to Compiled in Director? How are you trying to run the job - from Director, from dsjob, or by some other means? What symptom indicates that the job can not run? Are any events recorded in the job log?

You might try to repair DS_RESENU using fixtool or uvfixfile. Results are not, however, guaranteed. You might be better to restore a good one from backup. Rename or move the corrupted copy first. There is a separate DS_RESENU hashed file in each project, so you can also copy a good one from another ...

That's always a danger of using unsupported structures. However, since a lot of the server job code depends on these, particularly operation of the server Transformer stage (and, indeed, the BASIC Transformer stage in parallel jobs), I think you're on fairly safe ground with these two. See also rece...

Effectively what happens is filter_cmd | seq_source --> xfmr --> seq_target (yes, I DO mean stdout of the filter command)

Welcome aboard. :D If you use constructions like #string# it means you are making reference to a job parameter for the server job. However, this is mediated by a $ at the start of the parameter name (for example #$TMPDIR#) being a reference to an environment variable. My guess is that you have not g...

When you're using a filter, the Sequential File stage reads stdout from the filter directly (so you don't terminate the type command with a target file name, just type directly onto stdout). DataStage consumes these rows directly but must - for some strange reason - have the File Name property suppl...

What file name did you provide for the Sequential File stage to read?

Your DS_RESENU (resource) hashed file has become corrupted for some reason. This is highly unusual, as this file is completely used "read only" as far as I am aware.
Try this command and let us know what it says:

Timestamps have a minimum of 19 characters.

The whole point of having a graphical user interface (GUI) is so that you don't need to do any code-level programming, whether scripts or in an actual programming language. You should be able to do 90%-100% of what you need to do without ever writing any code (apart from things like derivation expre...

You can challenge any decision when you're in the right.

That fact that you challenge a foolish decision doesn't mean that the fools who made it will change their minds, but even getting them to think about it is a start.

Presumably one of the MQ Series manuals would have decoded that error code (2031) to mean incorrect user ID or password.

Thanks for that, it's not what I would have guessed. Maybe it's holding onto an entry in the Registry.

OK, managed to track it down (by accident, since I was looking at the generated OSH from UNIX level. There's a file called Local.msh for storing local message handlers for the job, in the RT_SCnnn directory, where nnn is the job number.