DSXchange

I am still a bit unclear about what you are doing. I cannot see a way to use ICONV() in your case, the string function that I would use is FIELD() or, if the data is fixed width, just use the In.String[pos,len] syntax. Since you haven't shown what you are trying to get as output I don't know how we ...

shyju, The only difference that DataStage sees between a pipe and normal sequential file is that you specify the checkbox for "named pipe" in the stage and you have the option of changing the buffer size and timeout values. The job itself sees no difference at all. You need to have 2 processes conne...

I am not sure what you are trying to do, your source and target formats are the same....

Sounds very much like the UNIX permissions for dsdb2.so on your machine don't give your userid read access.

DataStage objects are stored in UniVerse, as you have correctly written. The file (i.e. Table) structure of the DataStage data is not officially documented by Ascential so that they continue to have the ability to change the structure of the system. The complete documentation for the underlying syst...

Rajeev,

the lookups will use up temporary disk space. If you use a temporary 1-node configuration file does the problem go away?

Have you checked disk space during execution of the job? If the error occurs after a bit of time then this might be the cause, if it happens right at the outset then you might have access issues.

Kumar_s,

they are written, not over-written. If you don't auto-purge log files to only their last run, your multi-instance logs will all be visible. It is just that all of those entries are actually stored in the main job's log.

Hello Kumar_s, normally all instances of a multi-instance job have their own log files visible from the Director. They are all stored in only one log file, so if you have auto purge settings set so that only the last run of a job is kept then it will, unfortunately, remove entries for prior multiins...

Jasper, the function INDEX is exactly identical to INSTR, the first parameter is the string to check, the second is the substring to search for. The optional 3rd parameter is the occurence number. It returns the position in the string where the substring is found. It functions the same way in Server...

It looks like you are declaring the same function twice with different numbers of parameters.

0006: extern int32 stripinvalidchars(string inpstr,string termstring);
0007: extern string stripinvalidchars(string inpstr,string termstring,string replace);

Jasper,

once you solve your problem, compare performance with the simple INDEX() function and perhaps you might be convinced that the solution is more efficient. Please remember to post your results here, I for one am very curious.

thebird,

could you tell us what the compiler error is?

Thanks - I missed that one.

Andal, you are talking 2 different types of issue. Firstly, DataStage can connect to the databases directly using various methods; this is the easy part. Secondly, connecting to PeopleSoft or JD Edwards systems and getting structured data. Since these systems have their own structures just reading t...