DSXchange

I couldn't see an error in that log file output. If the server as well doesn't come up and run then the .net issue is further reaching and a complete reinstall might be the quickest way to resolve your problems.

I was going to refer you to the documentation, but I just did a complete search of the DS8 PDF documentation and only found minor reference to this powerful new functionality, at least with the term "usage analysis"; I then did a "find where used" and got a better reference, plea...

UVTEMP is where temporary files are placed. Where it is located on the system is not as important as making sure that there is sufficient temporary space available at that location. It is not a good idea to have it on the same partition as the DataStage server, since the DataStage engine is very sen...

Go to the stage before the join stage for all of your inputs and ensure that the column is present and declared with the same attributes everywhere.

A "Phantom" process is a term used to mean background processes or ones that aren't associated with a terminal. Historically this comes from the UniVerse implementation nomenclature on Prime hardware and PRIMOS, where the term was used.

What is the exact error? My guess is that the quickest solution is to reinstall your client software.

You will need to provide a bit more information in order to get a solution.
The process code you mentioned is computed or derived somehow in a job. How about writing this to a file, and then in a job sequence reading that value and using that to call up your actual job.

The contents of the &PH& subdirectory can be managed by creating an external process that deletes files. You can use cron to schedule a daily run of a command such as "find {path_to_&PH&} -mtime +1 -exec rm {} \;" to remove all files not modified (or created) in the past day.

"filescan" is not, to my knowledge, a standard UNIX command in any flavor I know of. Filescan is actually a utility used in Quality Stage to run on your datafiles to fix issues with fieldlengths. TIA Martina Oh my, shame on me... and it shows which parts of DS I will need to concentrate o...

Quoted from the DataStage BASIC Programmers Guide:

This function is only valid if the current job has issued a DSRunJob on the given JobHandle(s). It returns if the/a job has started since the last DSRunJob has since finished

That message comes from the log, right? Do you mean you cannot see any more messages in the log after that one?

:oops: I had forgotten to check that routine. I think it will only work if the job from which it is called is also the one which started the job in the first place, but that is worth checking into, since the resultant code would be a short: JobHandle = DSAttachJob('YourJob',DSJ.ERRNONE) Dummy = DSWa...

Ray - that is why I posted both %e and %E as those cover the 2 different commonly used first weekday definitions.

That means that while you have a path to the machine, there is no listener at port 1858 or that access to that port is blocked.

Try the telnet command from one of the workstations that can work and see if they can see that port.

The best way is not to call the job from a sequence until the precursors have completed. If that is not possible, then you can do as follows: Even in PX jobs the job control code is in BASIC. Thus, you could add code JobHandle = DSAttachJob('YourJob',DSJ.ERRNONE) Finished = 0 LOOP UNTIL Finished Job...