DSXchange

Welcome aboard. "Unable to determine current working directory" suggests that the rsh user ID does not have a home directory on the other machine. Perhaps you could include a CD in the script, so that the "current directory" environment variable gets set.

DSR_NLS is not used by the user. It checks aspects of NLS in the DataStage project when particular requests are made from the client.

Right click and choose Validate Derivation. Let the machine do the work!

You can't trigger that from within the job while rows are being processed. You need to detect, afterwards, that 0 rows were processed, and update the audit table with that information. This may require another small job (to update the audit table) and a routine to detect the link row count.

Never switched off "View Category" in Director?

Not directly. You can query the DS_JOBS table using DataStage SQL, which can be invoked from a shell script or BAT file. For example (assuming you have an environment variable called DSHOME set to the location of the DataStage installation directory): CD $project_dir %DSHOME%\bin\dssh "SELECT N...

3. enter TCL in the master account ("bin/dssh") (no leading "/" in the pathname)

Search the forum to find a fast method for performing the pivot on the comma-delimited field using an intermediate sequential file. Follow this with a Transformer stage to do the lookup. Voila!

What do you mean by "sequential sort"?

That would create an "always running" job sequence. Don't forget to design in a clean way to notify it to shut down. There are many possibilities.

If you export with job executables you do not even need to recompile. That said, recompiling isn't a bad idea, if only to check that you have not missed any dependent components. And, of course, don't forget to license server as well as enterprise when installing Enterprise Edition.

What link, where?
There is insufficient information in your question.

Get more memory on your client machine!

The syntax is OK. Where are you executing this command, and what do you believe is the problem with it?

There are at least 14 different ways that Japanese characters are encoded, including Shift-JIS. You need to find out how the data are encoded, and set the DataStage NLS map to that. You may also need to set environment variables such as NLS_LANG.