qkdriver not terminating
Peter Bateman
ppfb@hotmail.com
Sat, 14 Aug 2004 17:19:01 -0300
<html><div style='background-color:'><DIV class=RTE>
<P>Maeve:</P>
<P>Let us know what happens. I used to believe the way to decrease CPU usage and memory degradation when calling external programs is to call ALL externals from the main screen. </P>
<P>This would be something like a 'null' call just to get the procedure loaded. </P>
<P>A 'null' call has a parameter such 'mode' in each of the procedures. </P>
<P>In the procedure there is a line of code that says </P>
<P>if mode == 'null' then return. These 'null' calls would call the procedures</P>
<P>with the maximum parameter size. After these calls QUICK would just call the already</P>
<P>loaded procedures.</P>
<P>Regards,</P>
<P>Peter Bateman<BR><BR></P></DIV>
<DIV></DIV>>From: "Maeve Hooper" <mhooper@mhg.co.za>
<DIV></DIV>>To: "Leathers, Burton" <Burton.Leathers@cognos.com>
<DIV></DIV>>CC: <powerh-l@lists.sowder.com>
<DIV></DIV>>Subject: RE: qkdriver not terminating
<DIV></DIV>>Date: Fri, 13 Aug 2004 16:14:03 +0200
<DIV></DIV>>
<DIV></DIV>>Burton, that sounds like really good news!!! I'll give it a shot.
<DIV></DIV>>
<DIV></DIV>>-----Original Message-----
<DIV></DIV>>From: Leathers, Burton [mailto:Burton.Leathers@Cognos.COM]
<DIV></DIV>>Sent: Friday, August 13, 2004 4:08 PM
<DIV></DIV>>To: Maeve Hooper
<DIV></DIV>>Subject: RE: qkdriver not terminating
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>Maeve,
<DIV></DIV>>
<DIV></DIV>>We fixed a slow leak problem last year which, as it happens, had been lurking in the code for over a decade. I strongly suspect your problem would vanish were you to try using 8.43D.
<DIV></DIV>>
<DIV></DIV>>Burton
<DIV></DIV>>
<DIV></DIV>> _____
<DIV></DIV>>
<DIV></DIV>>From: Maeve Hooper [mailto:mhooper@mhg.co.za]
<DIV></DIV>>Sent: Friday, August 13, 2004 9:41 AM
<DIV></DIV>>To: Leathers, Burton
<DIV></DIV>>Subject: RE: qkdriver not terminating
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>Hi
<DIV></DIV>>
<DIV></DIV>>Thanks Burton. We are on 8.43.c on HP-UX 11.11
<DIV></DIV>>
<DIV></DIV>>-----Original Message-----
<DIV></DIV>>From: Leathers, Burton [mailto:Burton.Leathers@Cognos.COM]
<DIV></DIV>>Sent: Friday, August 13, 2004 3:37 PM
<DIV></DIV>>To: Maeve Hooper
<DIV></DIV>>Subject: RE: qkdriver not terminating
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>The problem behaviour described is characteristic of older releases. It is important to know with what release this is being seen. It is most likely that the motivation for process death would vanish if the latest PH release were being used. If this is being seen with the latest release, it would be best to log a call for a memory leak problem -- not a process termination issue.
<DIV></DIV>>
<DIV></DIV>>Burton
<DIV></DIV>>
<DIV></DIV>>Burton Leathers, Architect
<DIV></DIV>>Application Development Tools
<DIV></DIV>>Cognos Inc.
<DIV></DIV>>
<DIV></DIV>> _____
<DIV></DIV>>
<DIV></DIV>>From: powerh-l-admin@lists.sowder.com [mailto:powerh-l-admin@lists.sowder.com] On Behalf Of Maeve Hooper
<DIV></DIV>>Sent: Friday, August 13, 2004 9:14 AM
<DIV></DIV>>To: Deskin, Bob
<DIV></DIV>>Cc: powerh-l@lists.sowder.com
<DIV></DIV>>Subject: RE: qkdriver not terminating
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>Thanks Bob.
<DIV></DIV>>
<DIV></DIV>>The qkdriver process is only loading once per user. But I was wanting the process to die when the external call is complete. Then a new one to load when the next call is made. The reason for this is that the Unix memory allocated to this process grows too large. It does not seem to release any of the memory it uses per program.
<DIV></DIV>>
<DIV></DIV>>We are experiencing memory problems on our new HP-UX box. We have migrated from MPE. When I look in Glance, under the RSS memory column, the memory is about 40M for 1 qkdriver process. It starts at about 200k and builds up during the day. The memory regions recorded by Glance for this process show all the programs called during the day. I don't know how to get qkdriver to "release" this memory again.
<DIV></DIV>>
<DIV></DIV>>All our Cobol programs are dynamically linked modules. So I believe the users are all sharing the code - it would just be data or working storage areas that are unique per user?
<DIV></DIV>>
<DIV></DIV>>Hope this makes sense.
<DIV></DIV>>
<DIV></DIV>>Our application makes extensive use of Cobol programs called from Quick - in fact, I think every single screen calls at least 1 cobol prog.
<DIV></DIV>>
<DIV></DIV>>-----Original Message-----
<DIV></DIV>>From: Deskin, Bob [mailto:Bob.Deskin@Cognos.COM]
<DIV></DIV>>Sent: Friday, August 13, 2004 3:04 PM
<DIV></DIV>>To: Maeve Hooper; powerh-l@lists.sowder.com
<DIV></DIV>>Subject: RE: qkdriver not terminating
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>I'm not a UNIX expert but this sounds like something is not set up properly. The QKDRIVER should load once per user not once per external call. As well, external subroutines should not keep loading. I recall something similar happening on MPE/iX if the COBOL programs were not compiled to dynamically load. You had to compile with $CONTROL DYNAMIC or each time you called, a new instance would load, with obvious memory impact.
<DIV></DIV>>
<DIV></DIV>>And as far as I know, no one is having ongoing issues with external subroutines.
<DIV></DIV>>Bob Deskin
<DIV></DIV>>Senior Product Manager, Application Development Tools, Cognos Inc.
<DIV></DIV>>bob.deskin@cognos.com (613) 738-1338 ext 7268 FAX: (613) 727-1178
<DIV></DIV>>3755 Riverside Drive P.O. Box 9707 Stn. T, Ottawa ON K1G 4K9 CANADA
<DIV></DIV>>
<DIV></DIV>>-----Original Message-----
<DIV></DIV>>From: powerh-l-admin@lists.sowder.com [mailto:powerh-l-admin@lists.sowder.com] On Behalf Of Maeve Hooper
<DIV></DIV>>Sent: August 13, 2004 8:31 AM
<DIV></DIV>>To: powerh-l@lists.sowder.com
<DIV></DIV>>Subject: qkdriver not terminating
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>Hello
<DIV></DIV>>
<DIV></DIV>>Is there any way to get qkdriver to terminate after an external call from quick. We use a lot of Cobol programs called from Quick, and the qkdriver processes use more and more memory as the users work. The memory allocation for the qkdriver Unix process per user grows too large for comfort (+- 40 M). We are running on HP-UX.
<DIV></DIV>>
<DIV></DIV>>Thanks
<DIV></DIV>>
<DIV></DIV>>Maeve Hooper
<DIV></DIV>>Database Consultant
<DIV></DIV>>Metropolitan Health Group
<DIV></DIV>>Ph: (021) 480-6817
<DIV></DIV>>Cell: 083 6666 973
<DIV></DIV>>Fax: (021) 480 4932
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>> This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you.
<DIV></DIV>>
<DIV></DIV></div><br clear=all><hr>Free yourself from those irritating pop-up ads with <a href="http://g.msn.com/8HMBENCA/2734??PS=47575">MSN Premium: </a> Join now and get the first two months FREE*</html>