DSXchange

From the dsapi header file: /* Errors generated by the DataStage server */ #define DSJE_NOERROR 0 /* No error */ #define DSJE_BADHANDLE -1 /* Invalid JobHandle. */ #define DSJE_BADSTATE -2 /* Job is not in the right state (must be compiled & not running). */ #define DSJE_BADPARAM -3 /* P...

guysma - Don't mark your duplicate post as 'Resolved', simply delete it. You can do that by going in to 'Edit' it and checking the delete option - as long as there haven't been any replies to it, that is.

Tendentious? Great... you must be doing this on purpose. I don't remember the in person Wurlod being quite so obfuscatory.

This file:

/usr/local/Ascential/DataStage/Projects/<yourprojectname>/uvodbc.config

Define 'control job' and explain what you hope to achieve by invoking a Stored Procedure there?

Have a peek at the one in your specific Project you are trying to Import from. Bet it only mentions the one you see in your 'pull down menu'.

Dang, another Wurlod Word I had to look up.

http://en.wikipedia.org/wiki/Prolixity

kishoreramachandran wrote:THE file has got the following entries

THE file where? There's one in your $DSHOME directory and one in each Project, which one is this?

Not assigning 'fault' here and obviously I meant something other than that particular 'how'. I just don't see how you can say 'read my message again and follow the advice therein' when you know they couldn't read it in the first place.

My only sad little point here.

There ya go... yet another approach. Treat the file as 'tilde delimited' and then bust up the second 'column' as Ray notes.

ray.wurlod wrote:Read my previous post again, then follow the advice therein.

How exactly? They can't see the questions in your second post nor the query you posted in the first one, I'd wager.

Meaning you mark the job as 'Allow Multiple Instance' as noted. Since each Invocation ID you use must be unique across all running instances, why not leverage it to also control what happens in your job? In general, it could be a filename or table name or something you use to constrain a source quer...

I'd suggest you look into a multi-instance job where the InvocationID macro is used to control the partition being loaded. Then rather than running one large job with all the associated issues with restarting that you'd have, run multiple instances instead. Errors within a single partition can be de...

Yes, you need to figure out the logic needed to do that. Or are you just going to wait for someone to hand it to you on a silver platter? Perhaps one approach would be to treat each record as comma delimited and then parse the first field into two pieces around the tilde. Do you know what the maximu...

In other words, you'll need to build a single record from the multiple incoming records yourself via concatenation in stage variables. As noted, you can search the forum for many discussions on the subject of a 'vertical pivot' which is what that would be called when you do rows to columns. Columns ...