DSXchange

Start a new post. Include the details of your job and state your problem there.

Ok, now how about the rest of it?

As noted, use a Server job for this task.

You need to determine what that character actually is - the ASCII value. Do you have a hex editor/viewer on your server? Can you do an "od -x" (or something similar) on the file? Also, where do you see this "control character"? End of every record? Once at the end of the file? Something else entirely?

krishobby wrote:The jobs have been working fine till couple of days back and suddenly we are getting this issue

Find out what changed. Obviously something did.

1. Leave the Array Size at 1.
2. Use something other than DataStage, say a native Sybase tool.

mystuff wrote:a) But I am not able to cd (change directory) to &HOLD& or read the MyOutput file.

Why not? Is it because you are not escaping the "&" meta characters and so they send you into the background? Try:


as one way to get in there.

Ok, so it's the "only" message but is that the complete message? I can't believe it literally ends with "[ODBC SQL Serv..". Can you please try double-clicking on it to get an Event Detail dialog box, then clicking "Copy" and then paste the result into a post here?

Post the entire message. Double-click on it to see it.

Exactly... just pass in the Client or perhaps "Logic" number as an argument at runtime and have them all coded in. That's as dynamic as you're gonna get.

Put the child data into a hashed file with all three columns as Keys. Do two lookups against the hashed file using the parent data, one for "S" and one for "B". Construct the output based on the result.

All you needed to do was answer the question and then our dear Moderator would have moved the post, since it looks like the winning answer is "Server".

And you really shouldn't mark this as a "workaround" when it isn't anything of the sort.

ps. For anyone wanting to help, please do so here:

http://www.dsxchange.com/viewtopic.php?t=121104

Please verify job type - Server as marked or PX based on the forum we are in?

So now you know what changed, in spite of the DBAs saying nothing had - your user's grants.

TEXT data types are not officially supported and you must leave the array size at 1 to have a hope of it working. Transaction Size should be an even multiple of Array Size, not the other way 'round.