DSXchange

Specify the delimiter as 009.

Read the Help (press F1 while in the Format page) to see how you specify non-printing delimiter characters.

Another way. Open the Multi Job Compile tool and check the "Select only uncompiled jobs" check box.

Open Director. Disable Show Categories in the View menu. Sort by Status. Find those Not compiled. They will be in a single group.

The control file is emplaced wherever you specify. So do the logs but, if you don't, they tend to be written to your scratch disk resource.

It usually means you are trying to access a component that was compiled with a UniVerse compiler rather than a DataStage compiler, or with an incompatible (later, or pre-6.0 and not converted) version of the DataStage compiler. Did you import this job from another project running an incompatible com...

What is your job design? What stage types are you using? Under what conditions do you need to assign a "high value"? Have you decided what "high value" means/is for each of the data types you are using?

You specify fixed width to disable the use of searching for delimiters. And you'd better make sure that data you are reading are of the field width indicated in your metadata, otherwise what you will be reading is garbage.

There's nothing wrong with the vertical pivot idea. Because it's done in memory, it will probably be faster than 100 update statements.

That suggests that you were not attached to the project directory when you executed the command that failed.

For example the CurrentDate() function is available directly as an expression element in a Transformer stage. What you clearly require is more learning. You can not legitimately pass yourself off as a DataStage developer if you're going to do everything in UNIX scripts - what happens if you're emplo...

carloseduardo wrote:is it possible to find the project/job owning this process?

You could browse through your job logs and status detail views trying to match the process IDs but the benefit would not be worth the cost.

Use a database stage and select one row. For example, using Oracle: SELECT '#CallDate#','#Name#','#ID#' FROM DUAL; (it happens that DUAL only has one row). Or use an External Source stage with a similar echo command. In the downstream stage in either case specify Entire partitioning so that the same...

Consult the manual for the Netezza stage. Does it describe the stage as being able to read from, or only to write to, Netezza? If it does say you can read, it will also tell you how. Otherwise use an ODBC Enterprise stage.

Is operator combination enabled? Try disabling it to see whether having separate operator per stage enables display of link row counts.

Try importing the table definition using Orchestrate orchdbutil facility. Compare the two table definitions to see whether there are any differences. Even if you can't see any, replace the table definition in the job with the one imported using orchdbutil , and see whether that solves the problem. T...