HOUSE/290 is normally started through the H290.EXE executable which displays a splash screen and loads the main program (H290MAIN.EXE) and communications engine (CP290CE.EXE). If you write your own custom REXX program to access the Comm Engine, you may start CP290CE.EXE by itself. To run the Comm Engine alone, the following minimum files are required to be present: CP290CE.EXE, CP290.INI, CP290CE.HLP, RXASYNC.DLL, X10CPDLL.DLL and REXXUTIL.DLL.

Problem:

You may experience a growth in swap file under the following circumstances: You run another Vispro/REXX compiled program at the same time as HOUSE/290 (or Comm Engine) AND Object REXX is active. If you repeatedly start and exit HOUSE/290 while another Vispro/REXX program is running, the swap file keeps growing. You may have to start and exit HOUSE/290 (or Comm Engine) 5-10 times before you see a growth. The memory is not released until both Vispro/REXX-compiled programs are closed. If you close both programs, the swap file will return to it's original size. I have been able to duplicate this problem with UPS Monitor for OS/2 and the HOUSE/290 main and Comm Engine program. This memory leak may not be specific to these programs as the source of the problem points to Object REXX. If you use classic REXX, this problem will not occur.