DSXchange

A separate Transformer stage for each lookup would be overkill, IMHO, but would certainly ease the confusion as to which lookup failed. But I really don't see the confusion. Each lookup can be checked individually for success or failure. As noted, each will have its own unique NOTFOUND link variable...

Not really as that's not alot of information to go on. Do you have an xsd for your target xml? Have you imported the metadata for your xml target into DataStage so that it generated the proper XPath expressions for you or did you whip them up yourself? Doing that (letting DS generate the XPath expre...

Ideally, yes - it can be as simple as sending both output links to the same OCI stage, properly ordered. It's not a 100% guarantee of error free operation, however. I generally populate parent tables first and then child tables using separate jobs. However, when you do both in the same job that 'one...

Even worse - unless something has changed recently, Operators can only see released jobs. I haven't released a job in years, not since the advent of Version Control.

You can't install the DataStage Client on XP Home any more, you'd need to upgrade to XP Pro first.

I've run the client on 256MB systems and it works 'fine'. More is obviously better but you'll survive. Same with the processor, I would think a Celeron would be 'fine' as well.

To me, the best answer here is to do a Server reinstallation. It will recognize the fact that you already have the version installed, and will default to maintenance mode. One option there is to install new plug-in stages. Doing it there will get the 'Template' project as well so that new projects w...

Ok, that would have been good to know in your first post. The WFF stage is simple to use, read the Help available on it. Since you really don't want to 'wait' for a file but rather check to see if it exists or not, do that by specifying a zero wait time as I mentioned earlier. Then two triggers from...

No, not really. Help us out here... Now my question is when my lookup fails due to any link then it gives the same warning message as the last lookup is failing as my last lookup is ok. I really don't understand what you are saying here. Can you provide some examples of these 'warning messages' you ...

I would guess that the DB2 and DRS stages want DB2 date fields in different formats.

It is always a good practice to execute any script on unix that is called from DS jobs. Good practice, yes - but don't make the mistake that just because it runs from the command prompt that it must work fine from a DataStage job! All of the above issues apply that could cause one way to work and t...

Throw some light on which issue? The 'may be being monitored' one? An exact search of the forum using that message will turn up plenty of light.

Is the stage generating the sql or did you type it in by hand? I'm guessing the later or you shouldn't be having this issue. Make sure all three columns are defined in the stage, the 'C' column is marked as a Key (the other two must not be) and see if that fixes it.

EOR means 'End Of Record'. As Ken notes, a record was either short or DataStage thought it was short because it ran into an embedded CR/LF. Fixed width records must always have the same number of bytes in each record, hence the name. Check to see if any are short. The other thing that trips people ...

Examples?

No, but my wife has The Tao of Pug around here somewhere I believe. Not so useful for finding the path, but perhaps it can help with the pooh^h.