DSXchange

A "node" is a PX/EE term and you cannot directly associate memory to it.

Do you mean you have a 2-CPU system with a total of 2Gb main memory?

The orchadmin command is used to access and manipulate datasets. One of the options is rm which removes the descriptor and component files. Read the documentation to confirm this. Or perhaps you could actually just try it and see if it works.

First convert your string to TimeStamp then use StringFromTimeStamp to create the strings in the two formats you wish.

From unix "orchadmin rm {dataset}" will do it.

It is not absolute. It depends upon your available memory, lookup source type, speed, performance expections, levels of parallelism and other factors.

There is no accurate formula to compute how many nodes to use in aa good configuration file. In fact, each job usually has an optimal setting. The only way to really do this is to run the job with 1,2,3,etc. nodes and measure which one gives the best performance. Throughput is such a complex issue i...

Doing a reset and looking at the log entries as already recommended by Craig will help most at present.

No, it doesn't. NLS is only necessary if you need to modify or otherwise manipulate data. In fact, having NLS and not doing it correctly is what usually causes the conversion errors you are seeing. Try this - read the data in DataStage and write it to a sequential file - is the Japanese data still c...

Then it would seem you do need to set your character set differently so that no conversion occurs in the ODBC stages.

Vinod - the non-premium part is enough; have you actually gone and tried the MP conversion with ICONV and OCONV? All you need to do is create a test routine in the Manager; shouldn't take more than 60 seconds including compile and run. You can try both OCONV and ICONV and actually see what the outpu...

ds_Sai - please go to the first response in this thread. It explains how you can check your configuration file.

You haven't explained how you are moving the data (and how DataStage is involved). If you are reading from and then writing to SQL Server with the same settings and no NLS it should work.

Kumar66 - You posted your call to DSGetLinkInfo() already, just place that into your after job subroutine.

Good call - I hadn't thought about the pivot.

That is a good message, it means the VOC is accessible. It also means that you have not declared your hashed file as a local one.