DSXchange

Karthikgk0705,

If you keep the interview question numbers in your posts it makes it easier to keep track.

Mb/Minute isn't shown directly, you need to compute it from the number of rows * bytes-per-row and then divide that into the total runtime in minutes. The longer the runtimes the bette the results and the lower standard deviation you get.

I'm not sure what you mean by a batch job (sometimes that term is used to denote sequences). A sequence can call other DataStage objects but can also start external shell commands on both UNIX and Windows platforms. So I think that the answer to your question is yes.

Most likely the first time it failed the user had read but not write access to the file and the second time, when it work, either the user's profile had changed or the access rights to the file.

At least it is now a relatively simple test case for support. Please keep us informed on this thread so that someone with the same problem in the future can use this instead of going through the headaches that you are.

The only version of DataStage you can use for this is 7.5x2. Do you have this and the Microsoft Visual Studio.

You cannot solve your problem with the quote character defined as a ".
This is because the line is not well-formed due to unbalanced quotes. You will need to specify another quote character or delimiter to avoid this.

The Transforms and Routines are DataStage server objects and not PX ones.

Although both are written in BASIC code a transformation is a one-line piece of code that is replaced at compile-time into the job. A routine is a separately compiled program that is called as a function [it takes n-arguments and returns 1 value].

Unless you have 7.5x2 installed you will not be able to compile any PX jobs. Also, Windows XP is not an officially supported platform although it does work.

Can you distill this problem into a simple job with a row generator with just one column defined as CHAR(7) and with generated value of "profile" and going straight to your DB? If this still truncates then you can submit it to IBM/Ascential as a bug report.

That is really sad - he was a charismatic and outspoken personage!

Umm, now I am confused. If you declare this column as CHAR(8) and assign it the value "profile " it gets truncated to "profil "?

Craig - I missed that line! Good catch.

Add AND WHERE DSRID = "{your routine}" to the query.