DSXchange

The first connection is the metadata mismatch check. I don't know whether it checks for whether the table is partitioned at that time, though it would make sense to do so.

If you only need this change for DataStage processes, set HOME in the dsenv script. All DataStage processes read this script.

The logic is correct, and you can accumulate the XML as a single string in a stage variable. Output it once the closing tag has been processed (that is, if the input value is "</Request>").

Why do you believe you need to change HOME ? This is typically set by your login process.

Your SysAdmin should know about at.allow and cron.allow files. If not, get a competent SysAdmin.

What was your working directory at the time? The executable's parent directory needs to be findable in your command search list (PATH environment variable) or its pathname needs to be specified. Unix 101.

There's a Metadata Workbench Essentials class at IBM Singapore Thursday and Friday of this week. It's not too late to enrol. I'm the presenter. Contact Learning Services at IBM Singapore for more information.

Does the tutorial ask you to specify the -cm option? Try some other option instead.

Note, however, if there ARE common metadata elements, these should always be imported before elements of any other class.

Your question is not clear. ALL DataStage processes run as background processes.

(The word "phantom" in DataStage context means "background process".)

1. Use a one-node configuration file.

or

2. Add a single node node group and constrain stages to run in that.

or

3. Change the execution mode of stages to "Sequential".

or

4. Change the default execution mode environment variable.

just off the top of my head.

Explanation? What you need is what you need. Define a DataStage job to give effect to your need.

Not really.

It's not marked as resolved, nor is there any indication that U (one of our posters) had any involvement at all.

The second person personal pronoun in English is spelled "you".

SYSIBM.SYSTABLES isn't partitioned, so the SELECT is sequential. If it were partitioned, and you specify the Partition Table property, then the stage will execute in parallel mode.

There are lots of others. .mjb is mainframe job.