DSXchange

The next object does the guts of the work. It creates a shared container called DataStageJobLogContent. Note that within the shared container, a couple of hash files are used. Prior to running the job, it would pay to check whether their names clash with any existing hash files in your project. If s...

This next object is a routine named JobLogGet that obtains the job log details for a given job.
Edit (2005-10-07): Corrected a couple of bugs in the routine and replaced original code with resulting code.

Edit (2006-03-04): Code replaced with updated version at the end of this post.

The purpose of the first three objects is to create something from nothing! There is a generic version, a Unix version and a Windows version. The premise of providing three objects is that whichever O/S your DS server is, take a copy of the O/S specific version and rename it to be SingleRow. The cur...

I've been working on a client site whose DS jobs have required some serious diagnosis in order to work out which jobs have been major culprits in terms of poor performance. One of the actions I undertook was to perform an end-of-processing dump of the Job Log to enable analysis of which jobs are con...

Using DataStage Administrator to analyse a hash file ("analyze.file blarg STATS"), it returns sufficient information to enable a dynamic hash file to be "right sized" via HFC. If X represent the average data size and Y represent the average record id returned by the analysis, whe...