DSXchange

Search in DS_AUDIT, which can also tell you if the routine has been deleted.

There's no documented limit on the number of Job Activities in a job sequence. What is the setting of your inactivity timeout in Administrator for this project?

Bypass the startup macro when opening doc_tool.mdb. Hold down the Shift key when opening, or use F11. You need full copy of MS Access for this.

You create dynamic table definitions the same way you would in the database; that is, it's not possible without a lot of hacking.

No

What's its status in Director after this?

No, but I've never had to reinstall. We installed everything up front.

Tell us what's in the main job log.

Add more DSLogInfo debugging statements that tell you precisely what's happening.

Do it using a job sequence rather than in an after-job subroutine.

"phantom" is DataStage's term for "background process". 10819 is the process ID (user number) of the process reporting the error. The actual error message suggests what the problem is and a possible underlying reason that writeSocket() failed is that the listener on the other end of the socket (JobM...

Just guessing here. The import operator is used for most connections to persistent data - its task is to convert from external, human readable, formats into the internal formats used in Data Sets, for example from sequential files and File Sets. So my guess is that there's something wrong with this ...

They can be downloaded from the Ascential eServices web site. Search the forum; somewhere there's a direct link to where they are.

Orchestrate was the name of the parallel execution technology acquired when Ascential bought Torrent Systems.

Within the Transformer stage are you invoking any routines that perform I/O? This message often indicates incorrect usage of a file I/O statement, in particular the file variable.

These errors are most likely to occur with Link Collector or IPC stage types. It's an error trying to get the next row. Maybe there was a timeout caused by an inappropriate collection algorithm.
Search the forum for SPINTRIES for more information about tuning the wait for mutex locks.

Note that they are not log files - they are tables in the DataStage Repository database.
The appropriate mechanism for purging old entries manually is the Director client. Choose Clear Log from the Job menu having selected the job in question.

Something like to extract the first parameter. The result is available when setting the value of a job parameter in a subsequent Job Activity.