DSXchange

You may need to use the VERIFY.SQL command, if what Arnd suggested does not work, to remove the entries pertaining to the improperly deleted project from the system tables that describe that project.

osh (Orchestrate shell) is the underlying architecture required for parallel execution. It lives in a directory called something like /.../DataStage/PXEngine/bin Its parent directory must be visible on all machines mentioned in the configuration file. The configuration file's pathname is specified b...

Or don't put it in your Palette at all. You can drag any stage from the Stage Types branch of the Repository directly into your job design.

Moderator: please move to parallel forum

I believe that you should always strive to create jobs that do not abort. There is no direct equivalent to UtilityAbortToLog() in parallel jobs. But you could write your own using the C-callable DataStage API.

There are thousands of them, and you can customise the environment to create more. Are you really sure you need to know ALL of them?!! There will be years of learning involved.

It's not possible in a parallel job (without adding stages). Prefer a job sequence with a single Execute Command activity.

Then look in Director, under the Tools menu (Options) to learn that the default warning limit is 50.

Nope. BCI emulates the ODBC API. The mechanisms for setting device width and length are SET.TERM.TYPE and TERM (the former is preferred). Setting column width is done in the query itself (like the FMT qualifier I used earlier.) There is no URL with UniVerse HELP, however the UniVerse manuals are all...

And it's only in unqualified help - the List Command works properly in, for example, HELP SQL or HELP BCI. If you want just a list of help topics you can execute a query. SELECT @ID HELP_TOPIC FMT '40L' FROM SYS.HELP ORDER BY 1; Note that this is UniVerse help - not all of the commands are used by D...

I don't know.

I couldn't, because I refuse to use Runtime Column Propagation.

Why not try it, and let us know?

Can somebody help me in resolving this issue. I've no clue first of all that why Data Stage are creating 2 connection per Sybase OC or ODBC relational connections into the database. Let me guess: your configuration file specifies two processing nodes. Each processing node does all the work you've d...

Designer (I believe) ignores anything you give in Job Run Options and uses the defaults (set using Tools menu in Director). There does not appear to be any mechanism in Director for recovering the run and warning limits with which a job was run, even when non-default values are given. If you really ...

EXACTLY the same way you would do it in sqlplus or TOAD.

From a DataStage perspective, a view must be accessed via some kind of SQL-using stage, which a stored procedure must be accessed only via ODBC or Stored Procedure stages. A view is a combination of rows and columns from one or more tables. A stored procedure is an object in the database that can pe...

Please re-read my third paragraph and advise whether your experience is the same.