DSXchange

Film yourself importing 8.7 components into 11.3, then replay the film backwards.

That's about the only way.

Yes.

These tables are in IADB (or whatever you have called your analysis database).

You can verify the table names from within IA using the Table Management feature.

You almost certainly don't. Backwards compatibility is not supported. You *may* be able to fudge it, if you have not used any 11.3 features, by fiddling with the version number in the export file header, but this is also not a supported approach. You would be officially advised to re-create the logi...

Use parameter set values files. Provide the name of the appropriate values file as the "value" of the parameter set at run time.

Since you're on Windows, the installer probably also requires that the user be a member of the local Administrators group.

What Taylor said.

Cross-project compare is available out of the box.

I would also check your entitlement document, so as to ensure that someone has not simply installed IIS "with the lot" irrespective of what you actually have licensed.

The drop-down list of projects is populated from XMETA, whereas the errors you are seeing come from the local DataStage project repository on the engine tier. It may be that your engine credentials are not properly set up; it may be that the engine tier is not properly installed. Can you connect usi...

Officially not possible.

In practice, if the developed objects contain no 9.1 functionality, you *might* get away with it, though you may need to change the version header in the export file.

In general I'd recommend against it. It certainly would not be supported.

Research "tagged subrecord types" both within IBM documentation and without.

Data Click was originally written with just one target in mind, Netezza (aka Pure Data). Just saying.

yimwai wrote:Is there any options for export command to export such items?

No.

No.

Attempting to Cleanup after ABORT is usually the last of three messages in the log, and merely advises that DataStage is attempting to clean up.

You need to look at the previous messages to get any idea of what the actual problem is/was.

As a general rule every stage on every node creates an osh process, and there is one extra osh process (the "section leader") per node per job, and one extra osh process (the "conductor") per job. The more nodes you have, and the more stages you have, the more osh processes you w...

US-ASCII