DSXchange

Just setup a symbolic link to point to the appropriately named file. This allows your job to have a fixed name, and the symbolic link switches between files. An alternative is to copy the landed file into a processing directory under the fixed name. What is a symbolic link (is it another stage) how...

The file is in the DSEngine directory but it's called ".odbc.ini" (it's a hidden file). If you do
in the DSEngine directory the file should appear.

Ogmios

Does anyone know a possible reason for the following error that sometimes appears in the files in the &PH& directory.
It doesn't seem to affect the jobs though.

Ogmios

Thanks, but I see licenses of people currently not working and there are more licenses in there than the number of "licensed" licenses we have.

Will keep it for now, we can still move to a terminal server on license problems to keep it official

Ogmios

If only used for development: export all jobs, put them in your favored version control tool and erase all DataStage jobs you don't currently need for development. DataStage gets remarkably slower with a higher number of jobs in a project. Other tricks are to use DataStage Manager instead of Directo...

What I see in one site is that with a client license of 3, at least 5 people can logon simultaneously without a problem (version 6.0.1). So I was kind of wondering whether anything is broken in their scheme, in this version. Only one kind of client cd/license key was ever used at that site. We were ...

Thanks Ogmios, what strategy did you ultimately implement when you encountered this problem? It depends. This would be called being creative to get around DataStage limitations. It usually ended up landing the data either to file or to temporary database tables and then using full refreshes or usin...

Does someone know how the DataStage licensing scheme actually works in version 6.x?

The server CPU limit is enforced on UNIX, but I'm getting a distinct feeling the client licenses are not really enforced. Are they supposed to be floating licenses, ...?

Ogmios

EmmaP wrote:Assumming we can put up with committing after every pair, does anybody know how/why this insert is committing prior to the update failing?

We've been there before, the easiest is to rethink your strategy altogether else peformance will really suck.

Ogmios

From the install guides of DataStage 6.x supports DB2 on AIX as follows "DB2 wire protocol UDB 6.1, UDB 7.1, UDB 7.2", so no UDB 8.0 Haven't been playing with DataStage 7.x yet. Going from DB2 stage to ODBC stage can be painful if you use the SQL After and SQL Before of the DB2 stage. Ogmios

If the input data is not too big the easiest would be to write a small BASIC DataStage job to cover your required functionality.

Ogmios

Now I'm trying to figure out how to automatically compile a job on the Client side (without going inside DataStage BASIC -- migrating this to all 100+ projects (and counting) within the entire corporate would be... painful. :) Not to mention the inevitable bug fixes...) Anyone know how? Install Com...

:o UNIX open source :D, tell that to HP and Sun. Most firms make the mistake in this area of buying a very expensive tool and then not catering for a proper training for the developers. Although I would like Ascential to stop promoting hash files as "silver bullet" to everything in their c...

Try debugging it a bit yourself, we all have to debug sometimes. And it's getting late here :wink: . Try to strip everything from it that is not required E.g. The following runs perfectly: MAX_RUN = 3 n=1 Loop While n <=MAX_RUN n+=1 Call DSLogInfo("Job Failed: V2NewTestTransitif2", "J...

Another known issue: You use Oracle in PX for 6.x? Just for fun, check out the scratch directories, and look for ora*.par files. Whoops, password is visible. Haven't test it with 7.0.1 to see if they fixed my open issue. -T.J. The DB2 Bulk Load Stage has the same problem, on the other hand since it...