DSXchange

Have you taken this error to your DBA, discussed it with them?

Dual and a dummy row *is* a perfectly valid answer. That should only select one record and thus only run the procedure once. Or use a constraint to ensure that:

@OUTROWNUM=1

What "didn't work" about it for you?

If we only have a trigger for ok coming out of the job activity, and the job ends with warnings then the sequence will simply not call the following jobs and then finish "ok" - with no indication that its not done all its processing. No, it should not be working like that. What exact version are yo...

Any way other than what? Asking here? You could try searching the forums here as 'mutex errors' are not all that uncommon and have been discussed a number of times. You could call your Support provider, make them earn the money you pay them. Or wait for someone else to answer. Anyone can. Some of us...

Search the forums for the word 'Vista' and see what turns up. From what I recall, you'll find that not only is it not officially supported, DataStage just plain old doesn't work on it. Yet.

As Ernie notes, it's not that there is a disadvantage per se, more like there's no need for the XML Transformer. I only have a handful of jobs that use it and that's because they needed a custom XSLT to change complex ugly XML to another complex ugly form. So if you just want to flatten the XML and ...

Your other option - and how we handled our 'training' - is to spring for some consulting dollars and get a consultant onsite. Nice to have someone there - your jobs, your data, yada yada. Of course, a little more pricey than a singleton class seat, but perhaps an option for your organization.

First question would be - do you really need the XML Transformer in the job? The XML Input stage should be able to handle the vast majority of your parsing needs. The stage does have the option to write to a file. However, to output the data to your database, simply drag a link from the XML Transfor...

You probably don't want to know.

If it's like most systems I've seen, it could be - literally - anything.

Ok... as long as we're all on the same page. I just wasn't sure.

A little lost. Not sure what you mean by 'only file option is seen'... seen where? The ODBC stage would play the 'write the data to the database' role here from what I can tell. What is your database, by the way?

But as I said, it's never as simple as that.

Smith, Bobby Jo

Do you really want 'Jo' as the middle name or initial?

pxr87 wrote: Now I think I understand better . so Clients are not switchable .

That is not what I said.

2.Under "Enabled for this job" I tried to set number of days but I couldn't. You " couldn't " - in what sense? It wouldn't let you? You change it and it doesn't 'stick'? What? Switch it from Immediate to Auto Purge and that bottom section should become usable. Make sure 'Enabled for this job' is ch...

The Field function will do that for you automatically. It will only see two comma delimited values, so the space won't bother it. You could then use Field again on the 'first middle' value with a space as the delimiter to split it again... if only it was as simple as that.