DSXchange

Converting dates from one output format to another requires two steps - first into internal format and then back out in the desired external format: OCONV(ICONV(READ.DATE, "D/MDY"), "D-YMD[4,2,2]") You only took the first input step - but you used the date mask ne...

If you open up the Manager and look at the Transforms branch, you should see a number of predefined transforms that (typically) are used to make calls to underlying functions "easier" to understand. So, under the 'Built-In/String' sub-cat you'll see three - one of which is DIGITS and which does exac...

AKA the DIGITS transform.

Titto, it would have been good to know you meant a numeric field in a database table - we could have given you a little more targetted advise.

What do you mean by "at the command line"? If all you are doing is typing a sort command at your operating system command line, pressing return and getting a core dump, not sure how anyone here can help. Contact your UNIX admins and let them know what's going on. If you are running scripts from Data...

Actually doesn't matter - just move it.

short responce: Can't.

The Wait For File stage is for waiting on files being pushed to the DataStage server, while the OP needs to go get a file from a remote server.

Are you using User Defined SQL and does it include a semi-colon at the end? If so, that would be your 'invalid character' that works when you view data but not when you run the job.

Oh dear, now we are mixing politics and DataStage... and not even Tasmanian politics at that. How 'bout "I need to drink a glass of water when Paul Lennon scratches his ear". In there after the rolly eyes bit is an actual suggestion: unless someone is going to do something to let you know the file i...

Appending like that would be a valid solution when you have an unknown number of values you are working with. I was under the impression that Neeraj had a finite number of last name columns to work with - three to be exact. That's why I suggested the hashed file approach with one key field (the firs...

Sorry, not exactly a constructive comment, but I found something amusing in the concept that you make the job more efficient and shorten the runtime by aborting it.

I guess that's as opposed to letting it continue to run when you know things are going south and will need to be rerun.

True - but that's pretty much "Killing Processes in UNIX 101" and not anything specific to DataStage.

Hmm... didn't notice that the project name had a space in it. Didn't think that was allowed, or if allowed, perhaps not prudent. Curious if that turns out to be the sum total of the problem.

Unfortunately, 'performance' is a relative term and you haven't given us alot of information about what you are doing to go on. First question would be related to the reference lookups - are they using ODBC as well? If so, first order of business would be to convert them into hashed file lookups. It...

Search for exact matches on DS_AUDIT and you'll turn up posts like this one which should help.

but first of all I won't prefer kill -9 command. because this is very dangerous command. Well, then don't use it in your example. Many people will just look at an example and run with it without reading any of the dire warning that follow. Also, if one wants to kill off leftover running job process...