DSXchange

How is this post different from your other one? Double-posting won't make you any friends and won't get you a faster response.


Moderator - Please remove this duplicate post

Muriel,

even though it might not work correctly, you can edit the .dsx and change the line that reads ToolVersion "4" to version 3. I don't know if the DSJobReport uses functionality not available at Version 5 but I suspect that it will work.

You still need to print out the bad value in your routine; it obviously is getting a different one from what you expect. Another approach that you can take is to use the debugger in the designer to find out the invalid value. Or you can put an output link in your transform with the value of data_lin...

I've worked with offline systems before and have always used localhost as the hostname. You can test that by going to a DOS command window and typing "telnet localhost" and you should get a DataStage login prompt. Are you logging into to a domain or using workgroups? Perhaps you could try to force y...

Status() of 1 on an ICONV is that your first parameter, the value to be converted, is bad. If your test works then it will work in a job if the formats are the same.

The statement as you listed it, if entered on one line, should work. What error are you getting?

You should tell us what error message it failed with before you can get an answer. A common error is trying to write an empty key.

Please read the product documentation dealing with multi-instance jobs. You will need to use this to have the same job run at the same time from different sequences.

So you had DS create more than 1 data file and an explicit control file and it still failed? I am surprised that it failed and that you managed to reproduce it so quickly. It looked like a memory issue caused by getting too much data in one file. You can debug your core file to get a detailed cause;...

I am using the Oracle 8.1 Bulk Loader, which also comes with the product at version 7.1.
In your version 7 loader, specify a control file and 2 data files and see if they are generated; you can then run them from UNIX to see if you get a better error message.

Put calls to DSLogInfo() in your function to debug what values are actually being passed to your routine at runtime. The status of 1 means that your date string is invalid.

At Version 7.1 there is an automatic/manual option.(I have my 7.1 designer open at the screen that has it...)

As Craig has mentioned, switching modes in Oracle might make a difference or produce a better error message.

The Printer-memory-segment-removed message comes when a UNIX DataStage process is terminated abnormally and another process is generated with the same PID and attempts to allocate space in the engine. This is detected by DS and the prior process' printer segment is removed. The message itself is inf...

This is not a strange warning message. It is informating you that a background (phantom) process has finished. Where are you getting this error message?