DSXchange

Sainath, my motorcycle isn't working; can you help me too?

Just declare the column as type "float" and DataStage converts it and you can use it in your job.

Does the query create columns through expressions? If not too complex or involved, perhaps you could post the query there.

Ray - that's what I thought at first, but I did a quick test program on a sequential file and it turns out that PX will do this automatically.

Declare the column as "float" and DataStage will automagically perform your conversion from scientific notation to internal format.

Unless your server is an old 386SX processor with the turbo switch turned off, or it is extremely overloaded with other process then 3 transforms and 3 lookups shouldn't take that long!

As in my earlier response to datiseq, please measure your system loads to see if you can identify the bottleneck.

datisaq - I use the windows taskmgr to see the client PC usage and have sometimes seen the local CPU and particularly the I/O go up significantly during compiles, this is because parts of the compilation are actually done on the PC and not on the server and much data can be passed between the two, h...

udayk answered your question very well

The "Parameter specified but not used in flow: DSPXWorkingDir..." message is just a warning and not the cause of the failed transform compile. What other messages do you get?

Normally that message only occurs if, indeed, the job was not recompiled after the shared container was modified and saved. But I am in a project where at present we have 3-4 people working on jobs that all use a common shared container which I am still constantly making changes to; and in the past ...

How about getting rid of the warning to see if that might be triggering your problem? What data types do you have in your query (i.e., anything out of the ordinary char,varchar,number types)?

Those "$" signs might be coming from your terminal emulator, since the line breaks are continued on the next line. How about using "vi" to see if the data is correct? If the first line is column names, then look at line 2 in vi and at position 153, does that correspond to the err...

Good one Craig, that is probably it.

I'd add an echo of the runtime value for $file or of the whole command line for debugging purposes.

Varchar datatype, but what width does that column have?