DSXchange

vasu23 wrote:This is compilation problem,please compile the job and run

A job can't be run unless it has been successfully compiled, and this error is being thrown at run time. Therefore this is NOT a compilation problem.

Your question - which I answered - did not rule out interaction.

Have you ever heard of a "here script" (a shell scripting technique)?

Try using backslashes ( \ ) in the pathname of the configuration file. I know Windows usually tolerates forward slashes, but please try.

Can you also please dump detail of the Director log entry that shows the configuration file contents?

deepa_shenoy wrote:I meant instead of giving Null Field value which has 26 characters, is there any other approach?

For fixed-width, no.

Combinability mode governs the extent to which operators will be combined into fewer processes. By default DataStage does this aggressively, which may be sub-optimal. But it is not relevant to the question running in this thread. If you don't know where/how to compile in trace mode, then I daresay y...

Search for information about dsexport command.

Search also for information about istool command (IBM Information Server Manager) if you are running version 8.1 or later.

Some folders' fullness increases dramatically while jobs are running, particularly those designated as scratchdisk.

Another possibility is that the job has been compiled in trace mode with sequential mode execution enforced.

Not true. The operating system is AIX 5.3 (see subject). The supported C++ compiler on all AIX systems is xlC_r.

2p + 1p = 3 processes as reported in the final line.

Seems to me that it's fully explained at the top; the logs were obtained from tabs on the message box.

The most accurate way is to subtract years and multiply by 12, subtract months, and adjust depending on whether the anniversary of the base date has or has not already passed in the test date's year.

@DATE gives the better performance, because it's set when the job starts and does not change thereafter. Date(), on the other hand, accesses the system clock to give the current date - which may be different than when the job started, particularly in an "always running" job. So what is it ...

Any NLS map name ending in "-CS" is intended only for communication between DataStage client and DataStage server.

Try changing the map name to simply "MS1252".