DSXchange

This looks like a temporary file name used when invoking the Metadata Delivery service to save the job into Information Server database. Find out where you've configured storage of temporary files, and check that you have write permission there and its file system is not full.

What is difference between this environment and the one where it is running successfully? ("Nothing" clearly is not the correct answer.)

Time to mark the thread as Resolved.

Do you mean the DSJobController macro? It returns the name of the job that started the current one (if any).

Any kind of "hang" usually means waiting for a resource. Next time this occurs check to see if any kind of lock is held on the job sequence or controlled activity that appears to be hanging. Also check to see that there's plenty of free space in the file systems /tmp and those identified by the UVTE...

You also need read and execute permission to the file's parent directory. Do you have these? What error message is emitted when you try to "view the file in editor" or to "remove file from box"?

It's hashed file, not hash file. Performance is fine. It's the meaningless figures that are the issue here. Ignore them. Data flow rapidly into the write cache. Then, while no more rows are flowing but the cache is being dumped to disk, the clock keeps running, so that the rows/sec figure keeps fall...

Is this latest incarnation a server job or a parallel job? The original post was a server job; your description suggests parallel to me. If so please start your new thread in the Parallel forum.

They are enabled if your Update Action specifies user-defined SQL.

I suspect that that's just the way Fix() is. There's nothing obvious in the documentation (the DataStage BASIC manual). You could always use Fmt() or Oconv() to do your rounding.

Welcome aboard.

No, you don't need to change the PAT file. The right file to change is the classification table for xxAREA, so that it includes the city names.

You could, of course, use rule overrides, but adding city names to the classification table xxAREA.cls is the better approach.

What do you believe the second and third arguments of Fix() actually do?

For version 8, the vendor advises 2GB for the client alone.

Therefore the answer is likely to be less than 1.

MKS Toolkit (which I'm using this week) for one. (OK, it's not really UNIX.) I believe that, under some circumstances (relative pathnames?) AIX can also throw a hissy fit with // in a pathname.

None of which I'm aware but I still haven't played with version 8. Have you tried selecting a Link object from the General folder on the Palette?