UBS Log Tracker, release 2.1 is available now. The new release makes a point of its user friendliness. The ISPF based user interface has been completely redesigned, following CUA guidelines, thus streamlining ULT4DB2′s appearance and look-and-feel with the other UBS Hainer products. The idea behind the product’s new user guidance gears to allow intuitive creation of new log tracking tasks. Meanwhile the experienced user is still able to work ‘batch-oriented’ and profits from ULT4DB2′s optimized restart capacities.
Enhanced Data Propagation
Data propagation has two components: initial load and continuous propagation. After first providing the entire data volume to the target environment (initial load), the continuous propagation process must start seamlessly – and further propagations must always continue seamlessly exactly where the previous propagation chunk ended. Start and re-synchronization of data propagation and auditing are now automated extensively in ULT4DB2.
A ULT4DB2 task is now represented by a job chain. This makes it much simpler to reenact single working steps. The new history function documents every usage of ULT4DB2, including all options, data base objects, and files that have been used.
New User Interface
The user interface has been completely redesigned. Now, even for inexperienced users, it is much easier to create log tracking tasks. For each working mode – propagation, auditing, correction (un-do, re-do), undrop, analysis – there is a specifically adjusted user guidance that leads to creating the job chain for the desired log tracking function. The generated JCL is enabled to be executed in a job scheduler, of course.
Although thankfully rare, ‘un-dropping’ an accidentially deleted DB2 table space is not a trivial task. Most DB2 administrators are not familiar with this complex task and so the efficient help provided by the above mentioned revamped user interface will be surely welcome.
Definitions at One Single Place
Now it is sufficient to keep ULT4DB2′s task definitions in one single place, i.e. in one single DB2 subsystem.
General Log Analysis
Former ULT4DB2 releases always expected the user to specify DB2 object names and analyzed the log, based on such object selections. Now it is also possible to specify a time interval, inspect the log for events during the interval and – for example – thus determine DB2 tables that have been modified during that time frame.