DSXchange

....or Quality Stage

You can write an external script to prefix field name to the values.

In the transformer, you can split them and check the value. Column name will be the leading part of the value.

To do this, you need to have correct metadata.

It appears to be an issue with your Library Path.

Did you bounce the server ?

Remember seeing this in ODBC connectivity in Windows.

Try to access the ODBC using some other software - like BO or query tools.

Where is the data sourced from?

If the source is a database, you may be able to do this.

For sequential files, you may have to reference the metadata by position or other means.

Maybe you can obtain the source with column name prefix and use it in the job.

Use an aggregator to get the distinct timeZone count and set those with > 1 as NULL.

I will doubt that may cause the failure.

As Craig usually says, you need to post the 'unedited error message'.

Those appear to be for the PX version of the tool.

As Craig already mentioned, you need to check with your Control-M developers about that.

Is this the first project your company using Control-M ? Do you have any support agreement with them ?

elias.shaik wrote:But the job is giving different kind of errors.

What kind of errors ?

Post the unedited error so others can assist.

I thought we have been through this.

What have you gathered so far? What more are you looking?

If you have any logic for encrypting, you can write your own function to do so.

Look for delimiter String.

Why don't you try it and let us know !?