DSXchange

OLEDB

It's all bad news, there are no-o-o transition tools.

You can preserve table definitions if relevant, but the rest will need re-doing from scratch.

Use the opportunity to do the things you needed in OS390 but never got around to doing!

Or you could put a huge annotation onto the design canvas. Annotations go behind stage types, so your design would still be seen. Change the color setting of this annotation. Hmm...

That message only ever means that Oracle is being shut down. There is no way the other jobs could have finished successfully in this case.

Not possible in version 5. And not totally possible even in version 7.5 (the current version). Train your people to notice the project name in the title bar. Or use roles to prevent them from getting at production at all!

Could that be a DETLA (doubly extended three letter acronym)?

It's not so much DS-legal as ODBC-legal. ODBC is very strict about adherence to standards. One of these is that column names containing "illegal" characters (including space) must be quoted. The standard specifies double-quote, but the Access driver ignores this and uses backquotes instead. Aren't s...

It's probably not common practice, but it's certainly legal. DSParams is a text file that, among other things, validates functions and system variables for the expression editor, and stores project-wide defaults (for example for log purge) and user-defined environment variables.

It's telling you that, for this column, one of the following is true.

The input column is not null but the output column is null.

The input column is null but the output column is not null.

The options for specifying sorted input are in the Columns grid in server job Aggregator stages.

In parallel stages, sorting of input is managed as a property of the input link; I don't have access to PX at the moment to give you specifics, but it's certainly possible.

In your situation the lock on the routine is held by a defunct process, specifically the disconnected import process.

You do not unlock from UNIX. You must enter the dssh environment and use its tools to free the lock. To do so you will require administrative privileges.

&PH& is in use if any job is running from that project.
&COMO& is used by some administrative processes, such as server side tracing, clean account.
&SAVEDLISTS& is open if there is any client or any telnet process connected to the project.

Hence the directory (folder) name &PH&, where phantom processes keep log files of their activities.

Since QualityStage is INTEGRITY with a new badge, that part of it goes as smoothly as promised. The extras you get are a different look and feel, everything's renamed (operators become "stages"), and the ability to invoke from DataStage. It's definitely worth looking at the readme file and the new Q...

The best way is to have developer discipline. Enforced if necessary.