DSXchange

All the environment variables carry a small amount of Help text. Beyond that they're mostly listed in an appendix in the Parallel Job Advanced Developer's Guide which is one of the standard manuals.

Not at all, without hacking the Repository. This is not provided for in DataStage "out of the box".

Yuk, yuk, a thousand times yuk! Microsoft have chosen to use Char(128) to represent the Euro character; DataStage server jobs use it as the internal representation of NULL. Seriously consider running the file through a tr command to change the \x80 character to something else - anything else!

In a Routine activity in a job sequence you can get it using System(99), which returns the system time in number of seconds since midnight Greenwich Mean Time (GMT), January 1, 1970.

Welcome aboard.

What's in /opt/product/Ascential/DataStage/OnePercent/Scratch/ora.8497.14949d.2.log ?

Write a script, remotely execute it, and test its exit status.

Use an Execute Command activity to test the size of head -1 filename

Yes
Yes

Sometime later (8.2?) there will be an interface to source code control packages - expect ClearCase first, since IBM owns that.

Error code -4 typically relates to bad values being supplied to job parameters. Check the job log to determine what values were actually supplied in these cases.

Named COMMON is persistent until the process ends, and redefinition of the named COMMON area is illegal in the same session. You must totally disconnect the client after changing COMMON - after you re-connect the "problem" will magically have vanished, because you now have a completely different age...

Even better:

ExecDos
sqlplus -s oracle/oracle@BIODS.WORLD @#directory#\in\file.sql > #directory#\in\file_log.log
2>&1

Try recompiling the job. What was the job's status in the log after you killed the process? Did you properly kill the process tree (player processes, then section leader processes, then conductor processes)? If not, you may have some zombie processes that need to be cleaned up.

dsroci.sl is a shared library (associated with the OCI stage). Therefore the first place to check is your shared library search list environment variable (called SHLIB_PATH, LIBPATH or LD_LIBRARY_PATH depending on what kind of UNIX you have). You need to check (in the job log) what value this enviro...

I am just a poster here. It is not my site. Therefore I can not give you any discount. In any case, premium membership is less than 30c per day, and is 100% devoted to supporting the bandwidth charges that have to be paid to keep DSXchange alive.

Search the forum. It's almost certain that you lack "CREATE" privilege to the area in Teradata where the operator sync table must be created. Others have posted this in the past, so there are detailed answers to be found by searching.