04-Oct-2007

Remote Development
This evening I started the IDE-serrver, but only after I changed the startup procedure to use the classic VM, not the FAST one. It slows down the program, but will allow other processes to work nicely, without too much intervention by the java garbage collector. at least, that’s the hope.
Of course, a number of processes get swapped out, but less than when using the FAST VM.

The installation of the modules was no problem, but connecting to the server takes time. I got some trouble with login, settings etcetera. But after a few logicals were set, and I could wait, the connection was there. It’s faster that version 1 – a lot faster, so very workable. The only thing I have to do is set up a logical environment in which compilation and link can take place. It’s not unlikely i have to create a procedure to set all logicals and than do the compilation.
It’s a pity not all files are handled properly. Include files in the project are typed “.BLK” or “.INT”, and the project’s message file (.MSG extension) are not properly recognized and not treated as text file. So it seems, at least. Not is the .MSG file formatted, but that is not really a problem – it can be handled.

It works nicely, it’s just that the server needs to be started in advance, and , preferably be shutdown after use.

For the rest, the system is running nicely. paging is not as excessive as I feared, nor are CPU usage and disk IO. I may try the FAST engine tomorrow.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.