We recently upgraded to QAD eB2.1 with the .NET UI running Open Edge 10.1b.
The problem I am having is running our nightly batch jobs, we batch up our Invoice print & post along with several other jobs.
Someone/process is holding onto records and keeping the jobs from finishing, causing me headaches and sleepless nights baby sitting the batch.
Here is our setup:
+ HP UNX Server for progress database
+ Redhat Linux Server for the tomcat server for the QAD .NETUI interface
Webspeed is running on the HPUX machine as well. I even considered shutting the database down every night to clear the records, but have not found a clean way to do this, since if I bring down the database before tomcat I run into all kinds of problems.
How do others out there address batch jobs and record locks in a similar environment?
The problem I am having is running our nightly batch jobs, we batch up our Invoice print & post along with several other jobs.
Someone/process is holding onto records and keeping the jobs from finishing, causing me headaches and sleepless nights baby sitting the batch.
Here is our setup:
+ HP UNX Server for progress database
+ Redhat Linux Server for the tomcat server for the QAD .NETUI interface
Webspeed is running on the HPUX machine as well. I even considered shutting the database down every night to clear the records, but have not found a clean way to do this, since if I bring down the database before tomcat I run into all kinds of problems.
How do others out there address batch jobs and record locks in a similar environment?