CPU Load Full while RM/COBOL-85 v.6.10.02 in Win9x? 1

[Yojay]

Dear!<br><br>I have a serious problem <br>on running COBOL program for DOS on Windows 9x.<br>Any comments of you would be very helpful to me.<br><br>Here we go.<br><br>Our customer company had network application,<br>which consisted in COBOL program + C library.<br>Even until the previous year,<br>they had run that program on DOS environment.<br>Incredible, isn't it?<br><br>So, we upgraded that program to be runnable <br>on DOS window of Win9x.<br>However, there is one and very critical problem on it!<br>When running the appl. by RM/COBOL RUNTIME v.6.10.02,<br>CPU Load rises up 100%.<br>That may cause the execution of the appl. to be delayed,<br>and even worse be stopped.<br><br>I found that the CPU Load Full was caused by RUNTIME.<br>Although I ran the simple sample COBOL code using RUNTIME,<br>the CPU load went up 100%.<br><br>Is there anyone to tell me how I can make the CPU Load<br>down while running the appl. on DOS window of Win9x<br>by RM/COBOL Runtime?<br><br>I'd like to use RM/COBOL7.0,<br>but it will give me other programming load... <br><br>Thanks.<br>

 

[Crox]

Hi,<br><br>are you sure that you are realy using 100% cpu? Because I noticed under NT that it says sometimes that a DOS application is using 100% but at the same time it is running many other things, so the measuring is wrong. As we call it here: 'typical Micro-SOF' because SOF means something like bad luck and lots of people here hate the bad way the MicroSOFt operatingsystems are working. <br><br>On the other hand under NT there exists something like FORCEDOS, perhaps you can use something like that under '98? <br><br>When you create an ICON for a dos program, you can change the properties afterwards with all kind of possibilities. Perhaps you can try out some different settings?<br><br>Doesn't the old runtime environment works even better?<br><br>Good luck with this!

 

[tmorrison]

Just a guess here, but an educated guess.<br><br>If the application is waiting for user input, the MS-DOS way of doing that is polling.&nbsp;&nbsp;This is 100% CPU intensive! There is not much to be done about this in the DOS RM/COBOL runtime because MS-DOS is MS-DOS, not Windows NT.<br><br>The somewhat good news is that NT is a preemptive scheduler, so that the DOS window is just another task that can be preempted by a 32-bit application.&nbsp;&nbsp;The DOS window is just absorbing all the &quot;idle&quot; CPU time.<br><br>I understand that the application has a C library, which requires porting to the NT environment.&nbsp;&nbsp;I don't know what the C library was accomplishing, but it is possible that newer versions of RM/COBOL might provide COBOL-only ways to do the same things.<br><br>Best regards,<br>Tom Morrison<br>Liant Software Corporation