 |
ZDS Deploy Metrics®
Release 1.3 Build 675 : March 10, 2009
Maintenance Release
 | Fixed daylight savings time error. |
| Fixed type chart HeightPx error - customer settings were not overriding the default. |
| Modified type chart so that the greater of ListTop or ListPct is reported. |
| Fixed 'Errors By Reason' report alignment problem for strings with embedded html angle brackets. |
Release 1.3 Build 670 : January 16, 2009
Architecture
| The log tree traversal and handling logic has been completely replaced. The 1.3 package now runs between 3 and 10 times faster than v1.2 depending on the configuration. |
| Error trapping has been considerably extended. There are now 25 INFO, WARNING, or ERROR messages. |
| Environment execution (PKG_nnnnn_PKGL_nnnnn_BID_nnnnn_ENV_nnnnn.html) log files are now handled correctly. |
Charts: dplmetrics_type.html
| This new report provides time lapse visualization of the top 10 error types. |
Reports: dplmetrics_rpts.html
| The 'Errors by Type', 'Errors by Reason', and 'Errors by Object' reports are now sorted in descending order of error count. |
| Error string lines with zero error counts on the 'Errors by Reason' report can now be suppressed by a user configurable entry in the dplmetrics.ini file. |
| The placement of the output files can now be user set by an entry in the dplmetrics.ini file. |
| The display of 'Missing Package' warnings can now be suppressed by an user set entry in the dplmetrics.ini file. (Missing Package warnings are still logged to the dplmetrics.txt log.) |
| The audit control totals in the 'PACKAGE' and 'LOGS' sections have been revised. They can now be are directly related to the execution log tree properties. |
| A new 'PROGRAM' section reports internal errors. |
| A new 'THROUGHPUT' section reports various metrics to assist users to estimate run times. |
Logs: dplmetrics_logs.html
| Each migration line now lists the 'Destination Environment', 'Workflow Step', and 'Workflow'. |
| Users can now set a configuration entry in the dplmetrics.ini file to have successful migrations as well as failed migrations listed in the html file. This is useful during initial familiarization with the tool and for in-depth analysis of specific packages. |
| Migrations in the html file are now color coded:
Black to indicate that the execution is not in the requested period.
Green for migrations that PPM and the DM tool rate as successful.
Orange if PPM and the DM tool disagree about the migration's status.
Pink for migrations that were not attempted.
Red for migrations rated failures by PPM or by the DM tool. |
Bugs Fixed
| Percentages for entries with zero totals were sometimes displayed as an error string. |
PPM and Kintana are trademarks of Hewlett Packard.
|
