Batch Time Creep

We were contacted through a work friend, basically word of mouth.  The customer was happy,

no real concerns with their application performance, but a specific overnight batch job started taking longer and longer.  They called us in to take a look.

The system was running a home-grown application on HPUX with about 100 users connected to the system.  The database was moderate size, about 80 GB at the time.  The overnight batch job used to take 1-2 hours to complete about a year before.  Now it was taking close to 8 hours and was running into the production day.

With OmegaServe consultants’ extensive expertise, memory allocation, recover log usage, and several other areas, including all startup parameters were analyzed.  Without making any coding changes, just configuration change to the OpenEdge deployment, the batch job went down from 8 hours to 20 minutes.  In addition, the user community of the application was shocked by how fast it was running.  Over the years, they just got used to how the application ran and never thought it could be improved.
This is an example of hidden issues in your OpenEdge deployment.