Developer Workflow Guide

Back Next

Conversion Behavior with the Command Task Import

Consider conversion behavior for importing the Command task when you use a semicolon or a backslash within a command.

The following scenarios show the conversion behavior with the Command task:

There are two commands in PowerCenter. The first command contains a semicolon at the end, such as

<c1;c2;>

and the second command is

<c3>

The import process converts the command with the following syntax:

“<C1;C2>”; “<C3>”

“<C1;C2>”&& “<C3>”

There are two commands in PowerCenter. The first command contains a backslash and a semicolon at the end, such as

<C1;C2\;>

and the second command is

<C3>

The import process converts the command with the following syntax:

“<C1;C2\;>”; “<C3>”

“<C1;C2\;>”&& “<C3>”

You have two commands in PowerCenter. The first command contains a backslash and two semicolons at the end as

“<C1;C2\;;>”

and the second command is

“<C3>”

The import process converts the command with the following syntax:

“<C1;C2\;>”; “<C3>”

“<C1;C2\;>”&& “<C3>”

Watch

Comments

0 COMMENTS

We’d like to hear from you! Log in to comment.