[Bulk] set file command
Johnson, Harold A EDUC:EX
Harold.A.Johnson at gov.bc.ca
Fri Dec 9 12:58:50 CST 2005
Cool. Can you explain why this would make a process faster, if every
record has a mandatory link? There are cascading links as well, can this be
handled using this method?
-----Original Message-----
From: Ken Langendock [mailto:Ken at Langendock.com]
Sent: 2005 December 9 10:52 AM
To: Johnson, Harold A EDUC:EX; powerh-l at lists.sowder.com
Subject: RE: [Bulk] set file command
Harold. the file that you are trying to access as Read Only. Is it required
in the access statement to filter something? Or is it used to populate
something in the output phase?
If you are only using it to populate fields in the output phase you can open
the file in the output phase, this is much faster.
As in
OUTPUT readonlyfile &
ADD & ; this doesn't really add the record but it gets the
buffers to read once for every record complex.
UPDATE & ; this allows the record to be optional
VIA &
USING &
NOITEMS & ; don't initialize anything
IF 1 EQ 2 ; this stops the record from ever being updated
This allows you to have a much smaller record complex in the input phase,
thereby speeding up the Input and Sort phases.
Ken
-----Original Message-----
From: powerh-l-bounces+ken.langendock=rogers.com at lists.sowder.com
[mailto:powerh-l-bounces+ken.langendock=rogers.com at lists.sowder.com] On
Behalf Of Johnson, Harold A EDUC:EX
Sent: December 9, 2005 12:32 PM
To: powerh-l at lists.sowder.com
Subject: [Bulk] set file command
A question regarding the "set file" command in QTP. Recently, we were
running a new process in QTP which had a large number of links, but each
file was meantioned in a "set file xxx open read" statement. However,
during the run, this process caused a lock on a table! Is this syntax not
applicable anymore? If so, what syntax should we be using? ie: "set file
xxx open 1" ??
thnx
OpenVMS v7.3-2 RDB v7.1-241 PH v7.10.G1
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sowder.com/pipermail/powerh-l/attachments/20051209/1ae843ed/attachment.html
More information about the powerh-l
mailing list