Code, discussions, and whitepapers related to deploying ABL applications including version changes, performance, etc.
This program reads log files for logentrytype dynobjects and produces an output of those log file entries where objects were created, but not deleted.
Reads output from a LOG-MANAGER:LOG-ENTRY-TYPE = "4GLTRACE:4" and reports the line number, date, time, statement elapsed time, total elapsed time, nesting level, action, action adjective, and remaining data in a columnar format
This tool helps the DBA to detect when the size limit for a storage area is approaching a physical (addressing) limit.
Many sites become concerned about the performance of their ABL application at some time in the history of the site. While a big performance boost can often be achieved by simply moving to newer (and probably cheaper) hardware, this is not always an option, either because a reasonably powerful machine is already in use or there isn't sufficient budget for a change. The following links have been collected to provide some help for those concerned with performance.
The logreader tool provides a means to read one or more Progress / OpenEdge related logs from one or more Progress / OpenEdge components (i.e.
Failover Clusters for release 10.1A requires the Windows DLL's contained in this ZIP file. These Microsoft DLL's provide .NET C++ runtime support required by the Failover Clusters product. For installation instructions refer to the README file contained in the ZIP file.
This tool helps the DBA to detect when the size limit for a storage area is approaching a physical (addressing) limit. The analysis done by the tool provides a conservative view of storage area usage, i.e. there is a built-in safety margin in the reporting. The margin comes from space internal to a storage area that is actually available for the case of deleted and reused record-ids.
The download includes instructions on how to run the tool and interpret its results as well as a white paper, Best Practices For Managing Records-Per-Block Settings, which describes how to set records per block to achieve optimal performance. For more information on size limits for storage areas, see Chapter 3, OpenEdge RDBMS Limits of the OpenEdge Data Management: Database Design handbook.
The information and tools provided herein are provided "as is" without warranty of any kind. Progress Software Corporation disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Progress Software Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Progress Software Corporation or its suppliers have been advised of the possibility of such damages. Some jurisdictions do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
added by:
DB Struct Tool
This code enables Crystal Reports to connect to a Progress AppServer, run 4GL code on that AppServer, and use the resulting TempTable as data for a report layout. It works with Progress 9 and 10 (OpenEdge), and with Crystal Reports 9 or 10. Minimum requirement is Crystal Reports Advanced, this offers a Java connection.
added by:
Kimberly Craven
This is a set of Job Templates for use in Progress' Fathom Management product version 2.0A and above. These templates comprise a set of utilities to manage After Imaging on a Progress Database. These jobs can either be invoked via the Jobs "Run Now" button, scheduled at regular intervals or used as the action for an Alert. Consult the Fathom Management online documentation for more details on Jobs and Job Templates for more information.
added by Brian Bowman
LogRead is a GUI utility to read, query, sort, merge and translate log files from all Progress components (e.g. AdminServer, AppServer, Messenger). It is provided as a diagnostic utility to assist in the analysis of log files. LogRead is a 4GL application that runs only on the Progress Windows Client. It is distributed as r-code, for 9.1E and 10.0B.
added by:
Garry Hall