DSXchange

Check the DataStage NLS locale setting for server edition. Find this in the Administrator client, project properties, NLS tab.

The site where I am currently working is not using XMETA as the database name, but that decision was made prior to installation.

All DataStage developers should have a umask of 002 and/or the setgid bit should be set on the project directory.

More specifically, is TPT installed on the DataStage server?

Look in the referenced Transformer stage. You've used an ACos() function. ACos() argument may only be between -1 and 1.

No idea at all. I have not seen your data, I have not seen your business rules that make those data "bad". So how am I expected to be able to know how to "fix" them? A totally unreasonable request.

Is SubMasterLoad a sequence? Does it have a Notification Activity?

Select Notification Activity from the Stage Types branch of the Repository and perform a Where Used analysis. Filtering to just jobs will make the query finish faster.

Usually there is no record delimiter and no field delimiter. The bytestream containing the data is defined (implicitly) to be fixed width, and the character count defines the record boundary.

Remove the record delimiter property or set it to None.

How did your ETL process the date? That is, precisely what transformations were effected?

Please mark this thread as Resolved using the green button at the top.

What's wrong with what you did?

Is RCP enabled in all stages?

Adding to what Vincent posted (with which I fully agree) you can make use of values files in parameter sets and the special $PROJDEF designator for environment variable parameters to make switching of sets of default values even easier.

With premium membership gooogle will be able to read my entire post.

Premium membership is not expensive, at less than 30c/day. These funds help to defray the hosting and bandwidth costs that DSXchange incurs. So, by taking up a premium membership, you're helping to keep DSXchange alive.

Good luck with that! You will need to re-configure WAS first, because it is in WAS that the primary source of data about projects resides. How to change all the extant project-related metadata from XMETA might be too detailed a task - you might be better to engage IBM services to do that for you. A ...

I suspect that this is different enough to warrant a separate thread.