DSXchange

That looks about right.
The -8 is to convert it to your local timezone. All timestamps in XMETA are in UMT.

This is the real issue.
Working out *when* you should take it out is harder than working out *how* to take it out.

Are you saying you have the name of a branch office included in the company name?

If you can find it, you can move it somewhere safe and then push the rest of the name through the rest of the name parse/stan.

Off the top of my head, I'm thinking transformer loop, Field, reconstruct with dedupe inside the loop, push out on end of loop.

Have you tried the Planning, Installation and Configuration Guide? Look to the 11.3.1 doco specifically. 11.3.0 only supported DB2 and 11.3.1 added the other DBs. IIRC, in previous versions you have to install to a single node in the RAC and then update the configuration afterwards to point to the R...

You need to create the DB and set up the repository for it. Follow the same procedure you would use for a non-DB2 install.
This is covered in the Planning Installation and Configuration guide, IIRC.

Hang on: version 6?

The best you could probably get is compile time info. You might be able to find what parameter was assigned to a property (and if it has a default value), but not what was actually used. Where I am right now, this wouldn't work: it's all framework'ed and dynamic. If you have DSODB set up, I'd try lo...

Look in ASCLMODEL_XMETAGEN_USERB1C497CE for DB2 and presumably SQL Server. Oracle will be similar but abbreviated in some way because of the 30 character table name limit. It has the basic stuff you were asking for, except the password. I never bothered to look for the password. I was more intereste...

Pfft: 100 points is easy. Just post a few pages of log file.
It's the 4-5 pointers of pure gold that should be worth more

Surely a sort with keychange followed by a filter would be simpler, quicker, etc?

ray.wurlod wrote:Resist stupid requirements! ...

Should be a t-shirt.

Whoever came up with this requirement needs to be... um... reminded... that you can't invent detail.

Ray was saying that published IA rule definitions can be used in the Data Rules stage in DataStage jobs. You take a published rule definition, bind it to the relevant data available to the job, select your outputs and run the job. You can also set up the results to go to the DQ Console if you have y...

Take the lead and try it out. Let us know how it goes.

I'd say your project is too big and the JVM ran out out of memory trying to import it all. Either split it up and do it in a couple of blocks, or there may be a way to increase the size of the JVM. I once came across an article to get around the same sort of thing when you tried to use IAAdmin -getO...