DSXchange

The message is only an alert, informing you that the non-key column's default attributes are being mapped to the output link. You don't need to worry about it. If you like, you can demote the message to informational using a local message handler.

DataStage uses its own malloc(), not the standard UNIX one - it overloads the function. Be extremely careful making any assumptions about how malloc() works in a DataStage context. Indeed, it's better that you don't make any assumptions at all.

Once you place a reject link on the Oracle Enterprise stage, DataStage will automatically manage writing sqlcode (the error code) to that reject link. Which errors are you claiming are not captured?

Yes, if you need a reference input then you need a stream input in the Transformer stage. Consider using a Trans() function to lookup up the hashed file. To do this you will, however, need a VOC pointer to the hashed file. Trans("hashedfilename",keyvalue,field_number_to_return,"X&...

... having first licensed SOA Edition of course, and learned all the WISD/WISL acronyms.

The only capability in DataStage is "snap to grid". The rest is up to you.
You can, of course, re-size stage icons to get your links always running vertically or horizontally, which makes them easier to label clearly.

Take a look at the job score. Your Lookup stage generates a "composite operator" (two operators called LUT_CreateOp and LUT_ProcessOp). The first of these loads data from your table into a virtual Data Set and builds an index on it. The second actually performs the lookups, via the index, into the v...

ProfileStage is not a stage in DataStage, it's a separate product like AuditStage, MetaStage and QualityStage. As ltsaur notes, ProfileStage per se no longer exists; it is replaced with a tool called Information Analyzer which is mainly the old ProfileStage plus a small amount of the investigation c...

Your last sentence is completely erroneous - whether or not a job is multi-instance enabled has no bearing whatsoever on whether it can be reset successfully. To be reset successfully a job must simply be not in a runnable state and contain no quirks that prevent its being reset. DSPrepareJob() - th...

As author, you will see Edit/Delete This Post in the menu.

Yes, the way I suggested.

Premium membership is one of the ways that the hosting and bandwidth costs incurred by DSXchange are met. At less than 30c (Rs12) per day, it is definitely a worthwhile investment for anyone claiming to be a DataStage practitioner.

Define "performance" in an ETL context.

Try writing to a text file, and using a customized sqlldr control file to load into Oracle from that. For example, get the buffer sizes right (rather than defaulting to 256 for every field), use parallel load capabilities, and so on.

Please delete your duplicate post.

The only other ways to control job versions are:
(a) to change the version number manually at each edit
(b) to change the version number within the DSX file
(c) to "release" the job for production

Welcome aboard. The data type Timestamp is specified, in ISO 8601 and elsewhere, to contain seconds. If your data type must be Timestamp, you must live with the seconds. Even if your data type is Time you must live with the seconds. Wherever they are stored, you can elect not to display the seconds ...