[Bulk] arghh, the dreaded Record has been changed since
Richard Witkopp
RWitkopp at phxa.com
Mon Jan 25 12:29:23 CST 2010
Yeah, I was hoping the second OUTPUT would do it's first retrieval
immediately before executing the item, and then writing it back.
Oh well, I put it in it's own request and everything is dandy.
-----Original Message-----
From: Bob Deskin [mailto:Bob.Deskin at ca.ibm.com]
Sent: Sunday, January 24, 2010 7:14 AM
To: Richard Witkopp
Cc: PowerHouse List; powerh-l-bounces+bob.deskin=ca.ibm.com at lists.sowder.com
Subject: RE: [Bulk] arghh, the dreaded Record has been changed since
I have not really been following this so I don't know what else has been
discussed, but just in terms of what QTP is doing:
You're ACCESSing an OUTPUT file (INVESTMENT) so QTP reads all of the input
and writes it to an intermediate file. That file is then read in the
Output Phase. QTP calculates checksums when it reads the file to make sure
that nothing changes between the input and output.
You're updating the same file twice: Once as INVESTMENT and again as
INVEST_CUR_BOOK. The first OUTPUT statement will use the record that was
accessed and is in the intermediate file. That initialization occurs at
the start of detail processing (since the OUTPUT is at detail time). It
will be re-retrieved just before output to ensure that nothing has
changed.
The other OUTPUT statement retrieves a record during initialization. It is
the first record that fits the criteria. Again, QTP calculates a checksum
on retrieval, re-retrieves the record just before output and checks to see
if nothing has changed.
If both OUTPUT statements update the same record, you'll have problems due
to the timing of things. If you let the OUTPUTs go through (by using the
NOCHECK option), you'll lose the first update contents because the update
will be based on the value first retrieved.
Bob
From:
Peter Bateman <peterbateman808 at hotmail.com>
To:
Richard Witkopp <rwitkopp at phxa.com>, PowerHouse List
<powerh-l at lists.sowder.com>
Date:
2010-01-23 07:54 AM
Subject:
RE: [Bulk] arghh, the dreaded Record has been changed since
Sent by:
powerh-l-bounces+bob.deskin=ca.ibm.com at lists.sowder.com
Hi Richard:
I think the GET on INVEST_CUR_BOOK is occuring before the PUT
on INVESTMENT so when QTP attempts the PUT on VEST_CUR_BOOK
it finds the record has changed.
QTP trace should be able to confirm this for you.
Regards,
Peter Bateman
> From: RWitkopp at phxa.com
> To: powerh-l at lists.sowder.com
> Subject: RE: [Bulk] arghh, the dreaded Record has been changed since
> Date: Fri, 22 Jan 2010 14:24:21 -0800
>
> Okay, that didn't work either. I think I'm trying to do something that
can't
> (or shouldn't) be done.
>
> I think I'll just put this task in a request of its own.
>
> Thanks
>
> -----Original Message-----
> From: powerh-l-bounces+rwitkopp=phxa.com at lists.sowder.com
> [mailto:powerh-l-bounces+rwitkopp=phxa.com at lists.sowder.com] On Behalf
Of
> Richard Witkopp
> Sent: Friday, January 22, 2010 11:46 AM
> To: 'Knox, Dave (Carrollton, TX)'; powerh-l at lists.sowder.com
> Subject: RE: [Bulk] arghh, the dreaded Record has been changed since
>
> I don't think I can do that. There's a bunch of complexity (including
> another alias of investment that didn't come into play) and dozens of
item
> statements that I trimmed out of the example for brevity's sake.
>
> There was never a problem before with another aliased investment output
> statement. It physically appears before the un-aliased output. Maybe by
some
> quirk that matters. I'll give that a try.
>
> -----Original Message-----
> From: powerh-l-bounces+rwitkopp=phxa.com at lists.sowder.com
> [mailto:powerh-l-bounces+rwitkopp=phxa.com at lists.sowder.com] On Behalf
Of
> Knox, Dave (Carrollton, TX)
> Sent: Friday, January 22, 2010 11:01 AM
> To: powerh-l at lists.sowder.com
> Subject: RE:[Bulk] arghh, the dreaded Record has been changed since
>
> Timing issue when it retrieves aliased output records on update (to the
> same file)...
>
> Why not one OUTPUT?
>
>
> OUTPUT INVESTMENTS UPDATE IF T_BATCH_AP_AD = "N" or &
> T_DO_ESCROW = "Y"
>
> ITEM INVESTMENT_STATUS OF INVESTMENT =
> &
> "1"
> &
> IF T_BATCH_AP_AD = "N" AND T_DO_ESCROW = "Y"
> &
> ELSE "E" IF T_BATCH_AP_AD = "N"
>
> IF T_DO_ESCROW = "Y"
>
> ITEM CUR_BOOK_VALUE OF INVEST_CUR_BOOK FINAL
> &
>
> TOT_CAP_DTL OF SF$INFO &
> IF T_DO_ESCROW = "Y"
>
>
>
> -----Original Message-----
> From: powerh-l-bounces+knoxda01=unisourcelink.com at lists.sowder.com
> [mailto:powerh-l-bounces+knoxda01=unisourcelink.com at lists.sowder.com] On
> Behalf Of powerh-l-request at lists.sowder.com
> Sent: Friday, January 22, 2010 12:36 PM
> To: powerh-l at lists.sowder.com
> Subject: powerh-l Digest, Vol 56, Issue 13
>
> Send powerh-l mailing list submissions to
> powerh-l at lists.sowder.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.sowder.com/mailman/listinfo/powerh-l
> or, via email, send a message with subject or body 'help' to
> powerh-l-request at lists.sowder.com
>
> You can reach the person managing the list at
> powerh-l-owner at lists.sowder.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of powerh-l digest..."
>
>
> Today's Topics:
>
> 1. RE:[Bulk] arghh, the dreaded Record has been changed since
> you f ound it. (Richard Witkopp)
> 2. RE:[Bulk] arghh, the dreaded Record has been changed since
> you f ound it. (Peter Bateman)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 22 Jan 2010 10:24:47 -0800
> From: "Richard Witkopp" <RWitkopp at phxa.com>
> Subject: RE: [Bulk] arghh, the dreaded Record has been changed since
> you f ound it.
> To: "'Ken at Langendock.com'" <Ken at Langendock.com>,
> powerh-l at lists.sowder.com
> Message-ID:
> <FF5DC4E9EF39AB489EC56BBC4962CA8202EB6402 at p28exch1.phxa.com>
> Content-Type: text/plain; charset="us-ascii"
>
> Yes, it's one to one. It updated one INVESTMENT record and the error
> message
> occurred on the INVEST_CUR_BOOK record. Transaction processed was 1.
>
>
>
> _____
>
> From: Ken Langendock [mailto:ken.langendock at rogers.com]
> Sent: Friday, January 22, 2010 5:34 AM
> To: Richard Witkopp; powerh-l at lists.sowder.com
> Subject: RE: [Bulk] arghh, the dreaded Record has been changed since you
> found it.
>
>
>
> Are you sure your record complex is only retrieving ONE to ONE record
> complex or does your link create a ONE to MANY relationship?
>
>
>
> You could always move the reading of sf$INFO to an output phase read to
> be
> sure.
>
>
>
> OUTPUT Sf$INFO &
>
> ADD &
>
> UPDATE &
>
> NOITEMS &
>
> IF 1 EQ 2 &
>
> VIAINDEX SUBSCRIPTION &
>
> USING FUND_#, INVESTMENT_#
>
>
>
>
>
> Ken
>
>
>
> 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 Richard Witkopp
> Sent: January 21, 2010 9:35 PM
> To: 'powerh-l at lists.sowder.com'
> Subject: [Bulk] arghh, the dreaded Record has been changed since you
> found
> it.
>
>
>
> I'm getting this error in QTP. I could have sworn I've used this
> structure
> before to dodge it.
>
> The T_ variables are global temps.
>
> I'm getting the error on invest_cur_book. I know that investment is
> getting
> updated because investment_status is getting updated. Fund_#,
> investment_#
> are unique in each file.
>
> I cannot just put the if condition for t_batch_ap_ad on the item
> statement
> for invest_cur_book because it's actually a lot more complex than this
> and
> I've cut it down for brevity. I pretty much need two separate outputs
> for
> the investment file.
>
> 8.40.E on VMS.
>
> Pseudo-code:
>
> ACCESS BATCH_DTL
> &
>
> LINK FUND_# OF BATCH_DTL,
> &
>
> INVESTMENT_# OF BATCH_DTL
> &
>
> TO FUND_#,
> &
>
> INVESTMENT_# OF INVESTMENT
> &
>
> LINK FUND_# OF INVESTMENT,
> &
>
> INVESTMENT_# OF INVESTMENT
> &
>
> VIAIND SUBSCRIPTION TO *SF$INFO
> &
>
> CHOOSE BATCH_# SYSTEM SYM "T_BATCH_NBR"
>
> OUTPUT INVESTMENT UPDATE
> &
>
> IF T_BATCH_AP_AD = "N"
>
> ITEM INVESTMENT_STATUS OF INVESTMENT =
> &
>
> "1"
> &
>
> IF T_DO_ESCROW = "Y"
> &
>
> ELSE "E"
>
> OUTPUT INVESTMENT UPDATE
> &
>
> ALIAS INVEST_CUR_BOOK
> &
>
> VIA FUND_# OF INVEST_CUR_BOOK,
> &
>
> INVESTMENT_# OF INVEST_CUR_BOOK
> &
>
> USING FUND_# OF BATCH_DTL,
> &
>
> INVESTMENT_# OF BATCH_DTL
> &
>
> IF T_DO_ESCROW = "Y"
>
> ITEM CUR_BOOK_VALUE OF INVEST_CUR_BOOK FINAL
> &
>
> TOT_CAP_DTL OF SF$INFO
>
> NOTICE: The information contained in this e-mail and any attachments is
> confidential and may be privileged or otherwise protected from
> disclosure.
> This e-mail is intended solely for the use of the named addressee. Any
> other
> use, printing, copying, disclosure or dissemination may be subject to
> legal
> restriction. If you are not the intended recipient, please contact the
> sender and delete all copies including any attachments.
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 9.0.730 / Virus Database: 271.1.1/2637 - Release Date: 01/21/10
> 14:34:00
>
>
> NOTICE: The information contained in this e-mail and any attachments is
> confidential and may be privileged or otherwise protected from
> disclosure.
> This e-mail is intended solely for the use of the named addressee. Any
> other
> use, printing, copying, disclosure or dissemination may be subject to
> legal
> restriction. If you are not the intended recipient, please contact the
> sender and delete all copies including any attachments.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.sowder.com/pipermail/powerh-l/attachments/20100122/cbad9ccc
> /attachment-0001.htm
>
> ------------------------------
>
> Message: 2
> Date: Fri, 22 Jan 2010 14:35:21 -0400
> From: Peter Bateman <peterbateman808 at hotmail.com>
> Subject: RE: [Bulk] arghh, the dreaded Record has been changed since
> you f ound it.
> To: Richard Witkopp <rwitkopp at phxa.com>, PowerHouse List
> <powerh-l at lists.sowder.com>
> Message-ID: <BAY133-W15B614C2DB3C6C57AFE2EFF9620 at phx.gbl>
> Content-Type: text/plain; charset="windows-1252"
>
>
> Hi All:
>
>
>
> I believe 8.40 has the QTP Trace facility I would fire that up to see
> what is going on.
>
>
>
> Regards,
>
> Peter
>
>
>
> From: RWitkopp at phxa.com
> To: Ken at Langendock.com; powerh-l at lists.sowder.com
> Subject: RE: [Bulk] arghh, the dreaded Record has been changed since you
> f ound it.
> Date: Fri, 22 Jan 2010 10:24:47 -0800
>
>
>
>
>
>
>
> Yes, it?s one to one. It updated one INVESTMENT record and the error
> message occurred on the INVEST_CUR_BOOK record. Transaction processed
> was 1.
>
>
>
>
>
> From: Ken Langendock [mailto:ken.langendock at rogers.com]
> Sent: Friday, January 22, 2010 5:34 AM
> To: Richard Witkopp; powerh-l at lists.sowder.com
> Subject: RE: [Bulk] arghh, the dreaded Record has been changed since you
> found it.
>
> Are you sure your record complex is only retrieving ONE to ONE record
> complex or does your link create a ONE to MANY relationship?
>
> You could always move the reading of sf$INFO to an output phase read to
> be sure.
>
> OUTPUT Sf$INFO &
> ADD &
> UPDATE &
> NOITEMS &
> IF 1 EQ 2 &
> VIAINDEX SUBSCRIPTION &
> USING FUND_#, INVESTMENT_#
>
>
> Ken
>
>
>
> 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 Richard Witkopp
> Sent: January 21, 2010 9:35 PM
> To: 'powerh-l at lists.sowder.com'
> Subject: [Bulk] arghh, the dreaded Record has been changed since you
> found it.
>
> I'm getting this error in QTP. I could have sworn I've used this
> structure before to dodge it.
>
> The T_ variables are global temps.
>
> I'm getting the error on invest_cur_book. I know that investment is
> getting updated because investment_status is getting updated. Fund_#,
> investment_# are unique in each file.
>
> I cannot just put the if condition for t_batch_ap_ad on the item
> statement for invest_cur_book because it's actually a lot more complex
> than this and I've cut it down for brevity. I pretty much need two
> separate outputs for the investment file.
>
> 8.40.E on VMS.
>
> Pseudo-code:
>
> ACCESS BATCH_DTL
> &
>
> LINK FUND_# OF BATCH_DTL,
> &
>
> INVESTMENT_# OF BATCH_DTL
> &
>
> TO FUND_#,
> &
>
> INVESTMENT_# OF INVESTMENT
> &
>
> LINK FUND_# OF INVESTMENT,
> &
>
> INVESTMENT_# OF INVESTMENT
> &
>
> VIAIND SUBSCRIPTION TO *SF$INFO
> &
>
> CHOOSE BATCH_# SYSTEM SYM "T_BATCH_NBR"
>
> OUTPUT INVESTMENT UPDATE
> &
>
> IF T_BATCH_AP_AD = "N"
>
> ITEM INVESTMENT_STATUS OF INVESTMENT =
> &
>
> "1"
> &
>
> IF T_DO_ESCROW = "Y"
> &
>
> ELSE "E"
>
> OUTPUT INVESTMENT UPDATE
> &
>
> ALIAS INVEST_CUR_BOOK
> &
>
> VIA FUND_# OF INVEST_CUR_BOOK,
> &
>
> INVESTMENT_# OF INVEST_CUR_BOOK
> &
>
> USING FUND_# OF BATCH_DTL,
> &
>
> INVESTMENT_# OF BATCH_DTL
> &
>
> IF T_DO_ESCROW = "Y"
>
> ITEM CUR_BOOK_VALUE OF INVEST_CUR_BOOK FINAL
> &
>
> TOT_CAP_DTL OF SF$INFO
>
> NOTICE: The information contained in this e-mail and any attachments is
> confidential and may be privileged or otherwise protected from
> disclosure. This e-mail is intended solely for the use of the named
> addressee. Any other use, printing, copying, disclosure or dissemination
> may be subject to legal restriction. If you are not the intended
> recipient, please contact the sender and delete all copies including any
> attachments.
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 9.0.730 / Virus Database: 271.1.1/2637 - Release Date: 01/21/10
> 14:34:00
>
>
> NOTICE: The information contained in this e-mail and any attachments is
> confidential and may be privileged or otherwise protected from
> disclosure. This e-mail is intended solely for the use of the named
> addressee. Any other use, printing, copying, disclosure or dissemination
> may be subject to legal restriction. If you are not the intended
> recipient, please contact the sender and delete all copies including any
> attachments.
>
> _________________________________________________________________
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.sowder.com/pipermail/powerh-l/attachments/20100122/78c1b3a8
> /attachment.htm
>
> ------------------------------
>
> --
> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> Mailing list: powerh-l at lists.sowder.com
> Subscribe: "subscribe" in message body to
> powerh-l-request at lists.sowder.com
> Unsubscribe: "unsubscribe <password>" in message body to
> powerh-l-request at lists.sowder.com
> http://lists.sowder.com/mailman/listinfo/powerh-l
> This list is closed, thus to post to the list you must be a subscriber.
> Add 'site:lists.sowder.com powerh-l' to your search terms to search the
> list archive at Google.
>
> End of powerh-l Digest, Vol 56, Issue 13
> ****************************************
>
>
> --
> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> Mailing list: powerh-l at lists.sowder.com
> Subscribe: 'subscribe' in message body to
powerh-l-request at lists.sowder.com
> Unsubscribe: 'unsubscribe <password>' in message body to
> powerh-l-request at lists.sowder.com
> http://lists.sowder.com/mailman/listinfo/powerh-l
> This list is closed, thus to post to the list you must be a subscriber.
> Add 'site:lists.sowder.com powerh-l' to your search terms to search the
list
> archive at Google.
>
> NOTICE: The information contained in this e-mail and any attachments is
> confidential and may be privileged or otherwise protected from
disclosure.
> This e-mail is intended solely for the use of the named addressee. Any
other
> use, printing, copying, disclosure or dissemination may be subject to
legal
> restriction. If you are not the intended recipient, please contact the
> sender and delete all copies including any attachments.
>
> --
> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> Mailing list: powerh-l at lists.sowder.com
> Subscribe: 'subscribe' in message body to
powerh-l-request at lists.sowder.com
> Unsubscribe: 'unsubscribe <password>' in message body to
> powerh-l-request at lists.sowder.com
> http://lists.sowder.com/mailman/listinfo/powerh-l
> This list is closed, thus to post to the list you must be a subscriber.
> Add 'site:lists.sowder.com powerh-l' to your search terms to search the
list
> archive at Google.
>
> NOTICE: The information contained in this e-mail and any attachments is
> confidential and may be privileged or otherwise protected from
disclosure.
> This e-mail is intended solely for the use of the named addressee. Any
other
> use, printing, copying, disclosure or dissemination may be subject to
legal
> restriction. If you are not the intended recipient, please contact the
> sender and delete all copies including any attachments.
>
> --
> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> Mailing list: powerh-l at lists.sowder.com
> Subscribe: 'subscribe' in message body to
powerh-l-request at lists.sowder.com
> Unsubscribe: 'unsubscribe <password>' in message body to
powerh-l-request at lists.sowder.com
> http://lists.sowder.com/mailman/listinfo/powerh-l
> This list is closed, thus to post to the list you must be a subscriber.
> Add 'site:lists.sowder.com powerh-l' to your search terms to search the
list archive at Google.
--
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l at lists.sowder.com
Subscribe: 'subscribe' in message body to
powerh-l-request at lists.sowder.com
Unsubscribe: 'unsubscribe <password>' in message body to
powerh-l-request at lists.sowder.com
http://lists.sowder.com/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.
Add 'site:lists.sowder.com powerh-l' to your search terms to search the
list archive at Google.
NOTICE: The information contained in this e-mail and any attachments is
confidential and may be privileged or otherwise protected from disclosure.
This e-mail is intended solely for the use of the named addressee. Any other
use, printing, copying, disclosure or dissemination may be subject to legal
restriction. If you are not the intended recipient, please contact the
sender and delete all copies including any attachments.
More information about the powerh-l
mailing list