DSXchange

s_boyapati wrote:Are we sure, we can use MQ series stage in both server jobs and PX jobs?

Someone else would have to answer that. Server jobs, sure, but I couldn't say for certain about PX. I would imagine you could, but... [shrug]

I was actually trying to write a routine to solve this problem.If I bring the spaces to a uniform single space delimeter how i am going to know about the last field which is separated by the double spaces?(as in the requirement). You haven't said if a single space is legitimate data that can be fou...

kumar_s wrote:BTW do we have dsenv in Server edition?

As noted, you have a dsenv file in both Server and PX... for UNIX installations. There is no such thing when dealing with Windows, however.

Simple enough - make it match!

Catch-22 from the novel of the same name by Joseph Heller.

That's true about single spaces as legitimate data, didn't think about that. If that can happen, then Trim will work against your goal and you'll have to get your hands dirty writing a more complex routine.

No need for User Defined SQL. The proper datatype choice will generate the appropriate SQL in the OCI stage automatically.

Use another function inline to count the number of delimiters in the data. Use that number + 1 as the instance of the field to extract: Field(YourField,' ',Count(YourField,' ')+1,1) That's off the top of my head, suggest you build a routine as a test harness to check it does what you...

Actually, you can solve it as (believe it or not) you're not the first person to see this message. Try an Exact Match search of the forums for 'the PWD environment variable is not defined' and you'll see what I mean.

See if anything it turns up helps.

You actually don't need to do anything special to 'convert' a Varchar to a Numeric field in Server, it all happens automatically. There is an assumption, however, that what data is in the Varchar field is appropriate for a numeric field. Your error indicates that it isn't, meaning there are characte...

The colon isn't valid in a Windows filename, it's part of a drive designator. As noted many many times here, rather than fight this before or during the job, best to create a static filename and then rename it 'after job' to suit your needs. A standardized UNIX script or DOS batch file could do the ...

It was. The contents of most of the forums moved over the IBM's developerWorks. We're not sure what happened to the contents of the File Library or if it will ever show up somewhere over there.

You probably already have this, but just in case:

http://www-128.ibm.com/developerworks/f ... forums.jsp

ADN doesn't exist anymore, which would probably explain your problem with finding anything there.

mohanraj wrote:hi

why no reply

Good Lord... you complain you've had no reply after an HOUR?

What was wrong with the KeyMgtGetNextValue() suggestion? That's one of the easiest way to do that in a DataStage job. If that won't work - as noted, tell us why not, make your needs clearer.

Either hard-code the path or use the Parameters box for those parts.