DSXchange

Almost anything involving a loop within one records contents requires writing a user defined routine, and this is no exception.

I must admit that I don't quite understand exactly what you intend to do, could you perhaps illustrate using one row from your source?

There is no utility to directly read hashed files from UNIX. You would need to invoke the dssh to get into the DataStage command environment, and then issue the appropriate LIST or SELECT clause. In a simplified form, you can attach to the correct project directory and issue something like dssh &quo...

Those extra files that aren't backed up by a full project export need to be handled from UNIX by whatever method you decide to use. I wouldn't bother with trying to understand uvbackup - it is a tool that allows DataStage/UniVerse hashed files to be saved while they are still open and users are modi...

As I suspected. The Search button above is your friend.

Look at this thread for an answer and explanation. If that is not enough, try doing a search for "will partition despite" to find even more threads and responses.

Suresh, there are two main approaches to backing up your DataStage installation: (a) do a full export of the project to a .dsx file Advantages : you can restore single jobs / routines Disadvantages : won't backup open / locked jobs (b) do a UNIX level backup of the project directory Advantage: quick...

Perhaps you could state what the message is? Normally, when you explicitly repartition you will not get any message at all.

changming - of course it cannot work. Which is why I am trying to get get the original poster to confirm his output.

hint: 1999-11-05 does not match the timestamp pattern 'yyyy-mm-dd hh:nn:ss'

karrisuresh wrote:...could you pls help me...

I'm trying to. Just do it bit by bit. What is the string output from my last post's suggestion? Is what you posted your result or just what you think the result ought to look like?

Try approaching it from a different angle. Try to read the excel file on a remote machine using your DSN from another tool, i.e. msquery. If it works then the error is in DataStage realm; if it doesn't work then you have an ODBC limitation (I believe that this is going to be the case).

Try doing things just one step at a time. What is the string output of for your data?

Use DateToString() to convert your Date into a String, then StringToTimeStamp() to convert that string into a timestamp.

Gosha - that is not only bad advice, it is wrong 1. NEVER use 'kill -9' in a DataStage context unless there is absolutely no other way and you either have DS/UV Administration rights and skills or you are prepared to reboot your DataStage server. 2. The process PID of a job run bears no relationship...

If the VarChar field has trailing spaces in it they will be written to the database, so you need to TRIM() those in your DataStage job or via the SQL (less efficient).

WorkString = "Hello World"
WorkString[3,3] = "123"

Now WorkString is "He123 World"

The answer is, unfortunately, no. You cannot apply the message handlers to any jobs but PX/EE ones.