DSXchange

Design objects, whether for server, parallel or mainframe jobs or job sequences, are all stored in the same location, namely DS_JOBOBJECTS. Similarly, routines whether server or (interludes to) parallel routines, are all stored in one place, namely DS_ROUTINES. The point is that index corruption can...

Only by passing a reference to an encrypted parameter.

You will find the BASIC Transformer stage in the Stage Types branch of the Repository. It was intended not to put it on the Palette by default, though you can of course customize your Palette.

Don't push. Folks post as and when they can. If you want rapid support you can buy it from a support provider.

Not if RCP is enabled. That's the raison d'etre of RCP.

PX isn't really geared to non equijoin lookups. None of the Lookup, Join or Merge stages supports any technique other than exact key match. The string_lookup_from_int32 function for the Modify stage also does an exact key match. How are the source data stored? Possibly your best solution would be to...

This problem is coming from your attempt to move the file. Maybe it's still in use? Maybe your UNIX does not permit mv between file systems, so you have to use cp followed by rm?

That kind of checkpointing is not automatic; you have to design it in. Keep track (maybe in a hashed file, which is destructively overwritten, maybe by tagging each inserted record) of what has been committed, so that when you need to restart you can determine how far you got last time. Remember tha...

You can adjust the memory available with the shared memory offset parameters in uvconfig. However, you still can't load more maps than your maximum shared memory segment size (usually 2MB, configured by shmmax kernel parameter in UNIX) allows.

You can try changing the internal version number in the dsx file (from 50 to 36 for example) to correspond to the internal version number in jobs in each version. Most things will then import, though with warnings (the new functionality will necessarily be discarded). No guarantees, and you may need...

Note that the date pattern components (a) are case sensitive and (b) are enclosed in (specifically) double quotes.

Or DROP Col1 if you don't need it.

There remain areas within DeveloperWorks that you will find you can not access without a maintenance licence.

Fix your ODBC data source name definitions using the ODBC Administrator (odbcad32.exe).

No, but only because it's illegal SQL (not a DataStage issue). You need HAVING instead of WHERE. That said, your metadata (table definition) requires one Integer column whose derivation is COUNT(*) and four other columns to match the other columns in your query. Note that, in some databases, Count(C...