Re[2]: QTP rollback & commit

Fri, 18 May 2001 07:45:16 -0700

     Thanks for the reply, Bob, Charlie, and others. The requirement btw, 
     is to do some "corrective" data administration on the fly.  We have 
     used the subfile technique before and I just got to wondering if there 
     was some other method that was being overlooked.  It seems not (knot?) 
     ;=)

______________________________ Reply Separator _________________________________
Subject: RE: QTP rollback & commit 
Author:  "Deskin  Bob" <Bob.Deskin@Cognos.COM> at RDM-PO1
Date:    05/18/2001 8:51 AM

I don't know of any way to commit conditionally, but I'm curious as to the 
requirement. I would expect that if the data is correct and the update logic 
is correct that the processing would be correct and the commit should 
happen.

If it's otherwise, I'd suggest doing something with subfiles as output just 
to see the process works and if so, do the real thing.

Bob Deskin              
PowerHouse Web Product Manager, Application Development Tools, Cognos Inc. 
bob.deskin@cognos.com (613) 738-1338 ext 7268 FAX: (613) 727-1178
3755 Riverside Drive P.O. Box 9707 Stn. T, Ottawa ON K1G 4K9 CANADA

-----Original Message-----
From: GGrimm@pcc-structurals.com [mailto:GGrimm@pcc-structurals.com] 
Sent: Thursday, May 17, 2001 5:36 PM
To: powerh-l@lists.swau.edu
Subject: QTP rollback & commit

     I'm looking for a way to easily do a commit or a rollback in a 
     dynamically run QTP based on a visual review of the run statistics for 
     "reasonableness". Anybody have an idea how?  I have seen QTP do a 
     rollback when "badness" happens so know there is a way:=) I've tried a 
     COMMIT at RUN and then done a Ctrl Y which sometimes causes an abort 
     but nothing much happened. 
     (PowerHouse  8.13.D3)/Oracle 8.0.5.0.0/HP-UX B.11.00 
     See my simple code:

     > access *TA_one  link to TIME_ATTEND link to TIME_ATTEND_2 
     Access TIME_ATTEND viaindex TIME_ATTEND_EMPLOYEENO_1. 
     Access TIME_ATTEND_2 viaindex TIME_ATTEND_2_PK.
     > output TIME_ATTEND delete
     > output TIME_ATTEND_2 delete
     > go

     Executing request 1 ...

     Records read:
       TA_ONE                    1
       TIME_ATTEND             134
       TIME_ATTEND_2           134

     Transactions processed:   134

     Records processed:      Added  Updated Unchanged  Deleted
       TIME_ATTEND               0        0         0      134 
       TIME_ATTEND_2             0        0         0      134

     Finished.