If you are strapped for systems resources QTP is not the way to go.
I've seen a complex QTP process bring a 987/200 to its knees,
especially with NM files.

The first unofficial rule of thumb for complex process is to do everything
you can in Quiz,
then save QTP for the updates and adds.

QTP is a massive resource hog, especially for large record complexes.

hth...

:-)

Mike Church
Technical Support Manager
Information Services
Our Lady of Bellefonte Hospital
Saint Christopher Drive
Ashland, Kentucky 41101
-----------------------------------
Phone : (606)833-3727
Pager : (606)327-0965
   Fax : (606)833-3342
-----------------------------------
   Alternate e-mail : [log in to unmask]
-----------------------------------
 MY URL: http://members.tripod.com/mike_church/
OLBH: http://www.olbh.com
-----------------------------------
Daily Quote: been there, done that, got the tee shirt, hat and coffee mug...


-----Original Message-----
From: Dave Knispel [mailto:[log in to unmask]]
Sent: Tuesday, April 18, 2000 12:39 PM
To: [log in to unmask]
Subject: QTP as a system hog


To all,

I'm working on an HP3000 using QTP version 8.19.C2.  I have a QTP process
that is reading a NM/KSAM file, doing a select, sorting, then writing out
two subfiles.  This process keeps taking over my system.  Even running in
the EQ it will take all available system resources so no one (even the folks
in a higher queue) can get any CPU time.

Has anyone seen this before?  Any help would be appreciated.

I'm posting this to both the HP3000-L and the Powerhouse-L.

David Knispel
[log in to unmask]
Phone: 513-248-5029
Fax: 513-248-2672