DSXchange

If you want to take a backup, you can close the job and export its design to a file. You can also take a copy of it (if it is closed) via the right mouse click menu in Designer's Repository view or (if it is open) via "Save As".

mnvihol wrote:RCP is enabled for the project but in this job RCP option is not checked in any stage.

Is "use project defaults" checked for RCP?

You need to be using the 32-bit libraries. DataStage is a 32-bit application. Make sure that, at least for your DataStage processes, the 32-bit libraries precede the 64-bit libraries in your shared library search path.

BLOB (binary large object) is not a supported data type.

I'm further guessing that you implemented a "continuously running job" rather than a "starting on demand" job.

You'd best contact support for the exact cause. I'm guessing that an environment variable such as PWD or PATH is not set, or contains an invalid pathname separator character.

Remember that a hashed file is simply a means of implementing a database table. You can use DataStage/SQL (or a UV stage) to delete rows from a hashed file using SQL DELETE statement (with appropriate WHERE clause if you only want to delete a subset of the rows). From a TCL command (via the Administ...

It is not certified for Windows XP and therefore not supported. You are on your own, but it can be gotten to work. XP Professional only, however; it will not even install on XP Home.

No.

Almost always when some users can and some users can not do something the issue is one of permission. Is the user who can not connect to the project in the group associated with the project, and to which Developer role has been allocated? Can this user connect to a different project? Does DS_JOBS re...

Server job stage tracing goes into &PH& into files whose names end in ".trace". I'd be looking there as a first guess.

There's nothing in DataStage. Ask your SAP BW experts whether there's anything that end.

No, I meant the NAME column in the source file.

With versions back to 6.0 you could only create parallel jobs; you could neither compile nor execute them.

For less than $1 per week you can remedy this lack.