DSXchange

Simultaneous Peripheral Operations OnLine.

Not that I actually knew that or anything.

Don't know. However, are you just trying to constrain a query to only return a certain number of rows? Something like: AND ROWNUM <= 10 A generic DataStage solution would be to put a constraint on the Transformer following the ODBC stage to say: @INROWNUM <= 10 Or, if this is for testing purposes, p...

The first question is - does it support Sybase? I don't recall - but I think the answer is no. Check the documentation, there should be a pdf file in the Docs folder where you installed the DataStage Client. If you want to use ODBC for this, then you'd need to use the ODBC stage. There are branded d...

What are you considering to be a 'custom' stage?

ray.wurlod wrote:Why are you using an ODBC stage at all? A Sequential File stage is by far to be preferred for reading CSV files.

I'm assuming because the file is not local to the DataStage server.

Sounds ok. If there does turn out to be an issue, let us know and we'll work through it.

Multiple readers are fine, it's multiple writers to the same sequential source that is a problem. So as long are your targets (if they are flat files) are unique you should be fine.

Oh. Dang. Sorry, I was under the impression you were writing out directly to a flat file and then pushing the flat file up into SAP with the BW plug-in thing. I've got no clue how that works, never having had the pleasure of working with SAP and DataStage. Hopefully someone can steer you in the righ...

Try enabling the 'Omit last new-line' option in the Sequential File stage and see if that solves it for you.

Edit: I don't see how that jibes with the "If I restrict the job to 10,000 records I dont have this issue!" comment. Still, curious to see if it helps.

You could always check with your SA, they should be able to provide it for you.

what happens to data that were commited partly in the table and the job got aborted. when we reset the job, it wont have any effect on the table. Please confirm if my assumption is right. Nothing happens to any committed data when a job aborts. It's the 'uncommited' data that you lose. Every job th...

The only other message on the Forum like yours I could find was this one. It mentions a couple of things to check. A more generic search for UVTEMP might help as well.

If you are sure you don't have a space issue, then perhaps a permissions problem?

Since the FTP stage is metadata driven it can hork up your data during the process if everything isn't exactly right. It sounds like somehow the FTP stage thinks it needs to add the zeroes for you. What is the delimiter setting you are using in the FTP stage itself? A 'trick' you might want to try w...

Kinda figured that much was obvious.

Because the defaults are different between the two tools. In either tool, click on 'Run' and then switch to the 'Limits' tab before actually running the job. You'll see that Designer typically defaults to Unlimited warnings and Directory defaults to Abort after 50 warnings. And then there's the comm...