Search results

  1. E

    Memory leak in Progress 9.1C

    We are encountering what appears to be a memory leak with one of our Progress batch programs that are running on our UNIX db server (HP-UX), Progress version 9.1C. Essentially the process errors out with the following error message: ** stget: out of storage; the current -hs value is 2000. Try a...
  2. E

    Monitor DB Locks that cause a lock wait timeout

    We are running Syteline 5.00.3 with Progresss 9.1c. Our configuration is multi-db/multi-site. We occasionally have users (and sometimes processes) that cause record locks with some of our mission critical apps for an extended period of time. Currently we are configured such that if a record...
  3. E

    Syteline 5.00.3 Migration to Progress 9.1E or 10.1

    I've also posted this in the Symix section. Not sure which would be better. We are currently running Syteline ERP 5.00.3 on Progress 9.1C. We would like to migrate to a newer version of Progress (either 9.1E or possibly 10.1) and at the same time stay on Syteline 5.00.3. As I understand it...
  4. E

    Syteline 5.00.3 Migration to Progress 9.1E or 10.1

    We are currently running Syteline ERP 5.00.3 on Progress 9.1C. We would like to migrate to a newer version of Progress (either 9.1E or possibly 10.1) and at the same time stay on Syteline 5.00.3. As I understand it, Syteline 5.00.3 is only certified for Progress 9.1C. An obvious solution to...
  5. E

    Using asynchronous option in Run statements

    I'm trying to execute a series of programs from a main program that will run and not wait for the previous program to finish before the next one starts. From what I can tell, using the asynchronous option in Progress is the way to do this. So far nothing has worked. I keep getting errors...
  6. E

    Progress 9.1C UNIX memory issues

    I'm posting this here and in the Development section. I'm not sure which is more appropriate. Recently, we have encountered the following errors on some of our batch processes that are running on our UNIX db server: ** There is not enough memory to allocate a sort buffer. (538) ** stget: out...
  7. E

    Progress 9.1c UNIX memory issues

    I'm posting this here and in the Database Administration section. I'm not sure which is more appropriate. Recently, we have encountered the following errors on some of our batch processes that are running on our UNIX db server: ** There is not enough memory to allocate a sort buffer. (538)...
  8. E

    Progress System Error - Cannot Fork

    Our ERP is Syteline, which written in Progress 9.1C, our DB server is UNIX, running HP-UX. We run a fair amount of batch programs directly on the DB server as well as several Windows clients that interact with the DB. That being said, for the past several months we have been encountering the...
  9. E

    Outputing directly to printer Failure

    I'm trying to output information directly to a networked printer using the following code: OUTPUT STREAM rpt-job TO VALUE(jobprt.print-destination) PAGED PAGE-SIZE 55. Where jobprt.destination is a fully qualified UNC pathway to a printer. For example, \\syt\HP4000. Occasionally we get the...
  10. E

    Searching for Progress .p files with Windows XP

    One thing that came up recently is that when searching for Progress programs that contained a particular text string, the Windows XP search didn't kick up anything. However, when the same search was done using a Windows 2000 box, about 40 files kicked up. As it turns out, Microsoft...
  11. E

    For Statement Scoping of Records

    OK, Here is a situation that I encounter frequently and have never been able to get a straight answer to. Background: A client application is writing records to table x. At the same time, a batch process which cycles every 5 minutes is reading records from table x utilizing the progress "For...
  12. E

    Incomplete/missing db dumps using proutil

    We were doing a db dump & load recently and encounterd 2 problems during the dump process. First, one table didn't dump completely. It should have dumped about 270,000 records and only dumped about 135,000. Second, a table that should have been dumped was not dumped at all. The dumps were...
Top