powerh-l Digest, Vol 46, Issue 6
Pickering, John (NORBORD)
John.Pickering at norbord.com
Wed Mar 11 12:37:54 CDT 2009
I don't think so Vicki. Using FINAL or = won't make any difference in
this case. Guy and Jay both had it right earlier although Jay expressed
it more succinctly in his response when he suggested "You must have two
entries in your PMATRL file with the same PLANT-MAT-KEY value." QTP is
helpful enough to dump out the key information for the offending
duplicate.
Ron needs to first decide if it valid that there be multiple records in
PMATRL with the same PLANT-MAT-KEY. If it is not valid he should get rid
of one of the records and track down the source of it so it doesn't
reappear. If it is valid then the QTP should be changed to update
MATRL-STOCK at the key on which he is already sorting the data.
JWP
-----Original Message-----
From: powerh-l-bounces+john.pickering=norbord.com at lists.sowder.com
[mailto:powerh-l-bounces+john.pickering=norbord.com at lists.sowder.com] On
Behalf Of Alan and Vicki
Sent: Wednesday, March 11, 2009 1:22 PM
To: powerh-l at lists.sowder.com
Subject: Re: powerh-l Digest, Vol 46, Issue 6
I suspect it is because you are changing items in the file that are
being
referenced as source as well...the one that I'll use as an example is
ITEM WK-END-DATE(1) FINAL WK-END-DATE(2)
...
ITEM WK-END-DATE(2) FINAL WK-END-DATE(3)
Because you are using the "FINAL" option, QTP is re-evaluating the value
every time it is referenced - if you are changing a value of an item,
then
later change the value of the same item to something else (eg.
WK-END-DATE(2) is changing to WK-END-DATE(3)), then the value of
WK-END-DATE(1) isn't sure what to use any more. The order in which the
statements appear will not really matter when you use "FINAL" as they
are
evaluated once during the processing phase, then again at update, and by
that time, the value has changed during the processing phase.
To get around it, you may want to consider using '=' instead of FINAL on
the
output item statements so it only gets evaluated once during processing
and
not re-evaluated at update time when the record buffer has been changed
already. If that doesn't work, there are other messier workarounds, but
try
this one first.
That's my best suggestion - and good luck! This is one of those things
that
gets everybody at least once!
Vicki
----- Original Message -----
From: <powerh-l-request at lists.sowder.com>
To: <powerh-l at lists.sowder.com>
Sent: Wednesday, March 11, 2009 12:23 PM
Subject: powerh-l Digest, Vol 46, Issue 6
> 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. (lorcan-computers at fsmail.net)
> 2. RE: (Guy Werry)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 11 Mar 2009 16:14:47 +0100 (CET)
> From: lorcan-computers at fsmail.net
> To: powerhouse <powerh-l at lists.sowder.com>
> Message-ID: <1219486.2119361236784487794.JavaMail.www at wwinf3723>
> Content-Type: text/plain; charset="utf-8"
>
> Running the following QTP code on a HP3000, but keep getting the same
> error, any ideas on how to get around it
> Cheers
>
> Ron
> RUN STOCKS
> DISPLAY " ****** Program VS4002PS Version J.01.004 *******"
> SET PROCESS LIMIT 300000
> SET LOCK FILE UPDATE
> GLOBAL TEMPORARY GT-WK-END-DATE DATE
> GLOBAL TEMPORARY GT-WK-ST-DATE DATE
> REQUEST ONE
> ACCESS PMATRL LINK PLANT-MAT-KEY TO PLANT-MAT-KEY OF MATRL-STOCK OPT
>
> ITEM GT-WK-END-DATE = DATE(DAYS(WK-END-DATE(13))+7) &
> IF GT-WK-END-DATE = 0 ELSE GT-WK-END-DATE
> ITEM GT-WK-ST-DATE = WK-END-DATE(13) &
> IF GT-WK-ST-DATE = 0 ELSE GT-WK-ST-DATE
> SORT ON PLANT-MAT-KEY OF PMATRL
> OUTPUT MATRL-STOCK UPDATE ADD ON ERROR REPORT
> ITEM PLANT-MAT-KEY OF MATRL-STOCK FINAL PLANT-MAT-KEY OF PMATRL
> ITEM WK-END-DATE(1) FINAL WK-END-DATE(2)
> ITEM WK-RECEIVED(1) FINAL WK-RECEIVED(2)
> ITEM WK-USAGE(1) FINAL WK-USAGE(2)
> ITEM WK-USAGE-MORTAR(1) FINAL WK-USAGE-MORTAR(2)
> ITEM WK-USAGE-OTHER(1) FINAL WK-USAGE-OTHER(2)
> ITEM WK-ACT-CLSTOCK(1) FINAL WK-ACT-CLSTOCK(2)
> ITEM WK-END-DATE(2) FINAL WK-END-DATE(3)
> ITEM WK-USAGE(2) FINAL WK-USAGE(3)
> ITEM WK-USAGE-MORTAR(2) FINAL WK-USAGE-MORTAR(3)
> ITEM WK-USAGE-OTHER(2) FINAL WK-USAGE-OTHER(3)
> ITEM WK-RECEIVED(2) FINAL WK-RECEIVED(3)
> ITEM WK-ACT-CLSTOCK(2) FINAL WK-ACT-CLSTOCK(3)
> ITEM WK-END-DATE(3) FINAL WK-END-DATE(4)
> ITEM WK-USAGE(3) FINAL WK-USAGE(4)
> ITEM WK-USAGE-MORTAR(3) FINAL WK-USAGE-MORTAR(4)
> ITEM WK-USAGE-OTHER(3) FINAL WK-USAGE-OTHER(4)
> ITEM WK-RECEIVED(3) FINAL WK-RECEIVED(4)
> ITEM WK-ACT-CLSTOCK(3) FINAL WK-ACT-CLSTOCK(4)
> ITEM WK-END-DATE(4) FINAL WK-END-DATE(5)
> ITEM WK-USAGE(4) FINAL WK-USAGE(5)
> ITEM WK-USAGE-MORTAR(4) FINAL WK-USAGE-MORTAR(5)
> ITEM WK-USAGE-OTHER(4) FINAL WK-USAGE-OTHER(5)
> ITEM WK-RECEIVED(4) FINAL WK-RECEIVED(5)
> ITEM WK-ACT-CLSTOCK(4) FINAL WK-ACT-CLSTOCK(5)
> ITEM WK-END-DATE(5) FINAL WK-END-DATE(6)
> ITEM WK-USAGE(5) FINAL WK-USAGE(6)
> ITEM WK-USAGE-MORTAR(5) FINAL WK-USAGE-MORTAR(6)
> ITEM WK-USAGE-OTHER(5) FINAL WK-USAGE-OTHER(6)
> ITEM WK-RECEIVED(5) FINAL WK-RECEIVED(6)
> ITEM WK-ACT-CLSTOCK(5) FINAL WK-ACT-CLSTOCK(6)
> ITEM WK-END-DATE(6) FINAL WK-END-DATE(7)
> ITEM WK-USAGE(6) FINAL WK-USAGE(7)
> ITEM WK-USAGE-MORTAR(6) FINAL WK-USAGE-MORTAR(7)
> ITEM WK-USAGE-OTHER(6) FINAL WK-USAGE-OTHER(7)
> ITEM WK-RECEIVED(6) FINAL WK-RECEIVED(7)
> ITEM WK-ACT-CLSTOCK(6) FINAL WK-ACT-CLSTOCK(7)
> ITEM WK-END-DATE(7) FINAL WK-END-DATE(8)
> ITEM WK-USAGE(7) FINAL WK-USAGE(8)
> ITEM WK-USAGE-MORTAR(7) FINAL WK-USAGE-MORTAR(8)
> ITEM WK-USAGE-OTHER(7) FINAL WK-USAGE-OTHER(8)
> ITEM WK-RECEIVED(7) FINAL WK-RECEIVED(8)
> ITEM WK-ACT-CLSTOCK(7) FINAL WK-ACT-CLSTOCK(8)
> ITEM WK-END-DATE(8) FINAL WK-END-DATE(9)
> ITEM WK-USAGE(8) FINAL WK-USAGE (9)
> ITEM WK-USAGE-MORTAR(8) FINAL WK-USAGE-MORTAR (9)
> ITEM WK-USAGE-OTHER(8) FINAL WK-USAGE-OTHER (9)
> ITEM WK-RECEIVED(8) FINAL WK-RECEIVED(9)
> ITEM WK-ACT-CLSTOCK(8) FINAL WK-ACT-CLSTOCK(9)
> ITEM WK-END-DATE(9) FINAL WK-END-DATE(10)
> ITEM WK-USAGE(9) FINAL WK-USAGE(10)
> ITEM WK-USAGE-MORTAR(9) FINAL WK-USAGE-MORTAR(10)
> ITEM WK-USAGE-OTHER(9) FINAL WK-USAGE-OTHER(10)
> ITEM WK-RECEIVED(9) FINAL WK-RECEIVED(10)
> ITEM WK-ACT-CLSTOCK(9) FINAL WK-ACT-CLSTOCK(10)
> ITEM WK-END-DATE(10) FINAL WK-END-DATE(11)
> ITEM WK-USAGE(10) FINAL WK-USAGE(11)
> ITEM WK-USAGE-MORTAR(10) FINAL WK-USAGE-MORTAR(11)
> ITEM WK-USAGE-OTHER(10) FINAL WK-USAGE-OTHER(11)
> ITEM WK-RECEIVED(10) FINAL WK-RECEIVED(11)
> ITEM WK-ACT-CLSTOCK(10) FINAL WK-ACT-CLSTOCK(11)
> ITEM WK-END-DATE(11) FINAL WK-END-DATE(12)
> ITEM WK-USAGE(11) FINAL WK-USAGE(12)
> ITEM WK-USAGE-MORTAR(11) FINAL WK-USAGE-MORTAR(12)
> ITEM WK-USAGE-OTHER(11) FINAL WK-USAGE-OTHER(12)
> ITEM WK-RECEIVED(11) FINAL WK-RECEIVED(12)
> ITEM WK-ACT-CLSTOCK(11) FINAL WK-ACT-CLSTOCK(12)
> ITEM WK-END-DATE(12) FINAL WK-END-DATE(13)
> ITEM WK-USAGE(12) FINAL WK-USAGE(13)
> ITEM WK-USAGE-MORTAR(12) FINAL WK-USAGE-MORTAR(13)
> ITEM WK-USAGE-OTHER(12) FINAL WK-USAGE-OTHER(13)
> ITEM WK-RECEIVED(12) FINAL WK-RECEIVED(13)
> ITEM WK-ACT-CLSTOCK(12) FINAL WK-ACT-CLSTOCK(13)
> ITEM WK-END-DATE(13) FINAL GT-WK-END-DATE
> ITEM WK-USAGE(13) FINAL 0
> ITEM WK-USAGE-MORTAR(13) FINAL 0
> ITEM WK-USAGE-OTHER(13) FINAL 0
> ITEM WK-RECEIVED(13) FINAL 0
> ITEM WK-ACT-CLSTOCK(13) FINAL 0
> This is the section of the jobstream that shows the error
> 68 > USE VS4040PS.LVPHOUSE.EXE NOL
> 69 VS4040PS * Version H.01.003
> 70
> 71 10/03/2009 19:14 Hanson Aggregates
> 1
> 72
> 73 Run: VS4040PC
> 74 Request: ONE
> 75
> 76
> 77 Executing request ONE ...
>
>
----------------------------------------------------------------------
> 79 Record has been changed since you found
> ]
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 80 File: VS-ORDER
> 81 Linkitem: CUST-ACNO 0118 933066
> 82 Linkitem: ARC-ORDNO 644 200903100007
> 83 Linkitem: PLANT-DAY-REF 644 20090310
> 84 Linkitem: VS-JOB-REF 759R
> 85
> 86 Action Taken: Report and Continue.
>
>
----------------------------------------------------------------------
> 88
> 89 Records read:
> 90 VS-ORDER 394,902
> 91 VS-CUST-JOB 1,306
> 92 VS-CUST-MIX 1,285
> 93 LATEST-MIX 42,116
> 94
> 95 Transactions processed: 1,245
> 96
> 97 Records processed: Added Updated
Unchanged
> 98 VS-ORDER 0 127
1,117
> 99
> 00 Finished.
> 01
> 02 > EXIT
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
>
http://lists.sowder.com/pipermail/powerh-l/attachments/20090311/d4569b29
/attachment-0001.htm
>
> ------------------------------
>
> Message: 2
> Date: Wed, 11 Mar 2009 10:23:54 -0500
> From: "Guy Werry" <guy.werry at hbms.ca>
> Subject: RE:
> To: "powerhouse" <powerh-l at lists.sowder.com>
> Message-ID:
> <0ECD404B6909D0458968F14A7FF73BCB048740D0 at hbffc003.hbms.hudbay.corp>
> Content-Type: text/plain; charset="us-ascii"
>
> Ron,
>
> At the risk of insulting your intelligence, as I'm sure that you've
> already thought of this, the bottom-line answer is actually quite
> simple: you have input data that is linking to the SAME output record
> MULTIPLE times. This means that you are attempting to update the same
> output record more than once, causing the failure.
>
> I know, because I've had the same problem in the past.
>
> You'll need to optimize your linkage and/or processing logic somehow
so
> that you eliminate the multiple updates - that may mean multiple
passes
> to the input, or utilizing different keys on the output file.
>
> Hope this helps,
> Guy L. Werry
> Senior Systems Analyst
> Hudson Bay Mining & Smelting Co., Limited.
>
>
> ________________________________
>
> From: powerh-l-bounces+guy.werry=hbms.ca at lists.sowder.com
> [mailto:powerh-l-bounces+guy.werry=hbms.ca at lists.sowder.com] On Behalf
> Of lorcan-computers at fsmail.net
> Sent: Wednesday, March 11, 2009 10:15 AM
> To: powerhouse
> Subject:
>
>
>
> Running the following QTP code on a HP3000, but keep getting the same
> error, any ideas on how to get around it
>
> Cheers
>
>
>
> Ron
>
> RUN STOCKS
>
> DISPLAY " ****** Program VS4002PS Version J.01.004 *******"
>
> SET PROCESS LIMIT 300000
> SET LOCK FILE UPDATE
>
> GLOBAL TEMPORARY GT-WK-END-DATE DATE
> GLOBAL TEMPORARY GT-WK-ST-DATE DATE
>
> REQUEST ONE
>
> ACCESS PMATRL LINK PLANT-MAT-KEY TO PLANT-MAT-KEY OF MATRL-STOCK OPT
>
>
> ITEM GT-WK-END-DATE = DATE(DAYS(WK-END-DATE(13))+7) &
> IF GT-WK-END-DATE = 0 ELSE GT-WK-END-DATE
>
> ITEM GT-WK-ST-DATE = WK-END-DATE(13) &
> IF GT-WK-ST-DATE = 0 ELSE GT-WK-ST-DATE
>
> SORT ON PLANT-MAT-KEY OF PMATRL
>
> OUTPUT MATRL-STOCK UPDATE ADD ON ERROR REPORT
>
> ITEM PLANT-MAT-KEY OF MATRL-STOCK FINAL PLANT-MAT-KEY OF PMATRL
> ITEM WK-END-DATE(1) FINAL WK-END-DATE(2)
> ITEM WK-RECEIVED(1) FINAL WK-RECEIVED(2)
> ITEM WK-USAGE(1) FINAL WK-USAGE(2)
> ITEM WK-USAGE-MORTAR(1) FINAL WK-USAGE-MORTAR(2)
> ITEM WK-USAGE-OTHER(1) FINAL WK-USAGE-OTHER(2)
> ITEM WK-ACT-CLSTOCK(1) FINAL WK-ACT-CLSTOCK(2)
> ITEM WK-END-DATE(2) FINAL WK-END-DATE(3)
> ITEM WK-USAGE(2) FINAL WK-USAGE(3)
> ITEM WK-USAGE-MORTAR(2) FINAL WK-USAGE-MORTAR(3)
> ITEM WK-USAGE-OTHER(2) FINAL WK-USAGE-OTHER(3)
> ITEM WK-RECEIVED(2) FINAL WK-RECEIVED(3)
> ITEM WK-ACT-CLSTOCK(2) FINAL WK-ACT-CLSTOCK(3)
> ITEM WK-END-DATE(3) FINAL WK-END-DATE(4)
> ITEM WK-USAGE(3) FINAL WK-USAGE(4)
> ITEM WK-USAGE-MORTAR(3) FINAL WK-USAGE-MORTAR(4)
> ITEM WK-USAGE-OTHER(3) FINAL WK-USAGE-OTHER(4)
> ITEM WK-RECEIVED(3) FINAL WK-RECEIVED(4)
> ITEM WK-ACT-CLSTOCK(3) FINAL WK-ACT-CLSTOCK(4)
> ITEM WK-END-DATE(4) FINAL WK-END-DATE(5)
> ITEM WK-USAGE(4) FINAL WK-USAGE(5)
> ITEM WK-USAGE-MORTAR(4) FINAL WK-USAGE-MORTAR(5)
> ITEM WK-USAGE-OTHER(4) FINAL WK-USAGE-OTHER(5)
> ITEM WK-RECEIVED(4) FINAL WK-RECEIVED(5)
> ITEM WK-ACT-CLSTOCK(4) FINAL WK-ACT-CLSTOCK(5)
> ITEM WK-END-DATE(5) FINAL WK-END-DATE(6)
> ITEM WK-USAGE(5) FINAL WK-USAGE(6)
> ITEM WK-USAGE-MORTAR(5) FINAL WK-USAGE-MORTAR(6)
> ITEM WK-USAGE-OTHER(5) FINAL WK-USAGE-OTHER(6)
> ITEM WK-RECEIVED(5) FINAL WK-RECEIVED(6)
> ITEM WK-ACT-CLSTOCK(5) FINAL WK-ACT-CLSTOCK(6)
> ITEM WK-END-DATE(6) FINAL WK-END-DATE(7)
> ITEM WK-USAGE(6) FINAL WK-USAGE(7)
> ITEM WK-USAGE-MORTAR(6) FINAL WK-USAGE-MORTAR(7)
> ITEM WK-USAGE-OTHER(6) FINAL WK-USAGE-OTHER(7)
> ITEM WK-RECEIVED(6) FINAL WK-RECEIVED(7)
> ITEM WK-ACT-CLSTOCK(6) FINAL WK-ACT-CLSTOCK(7)
> ITEM WK-END-DATE(7) FINAL WK-END-DATE(8)
> ITEM WK-USAGE(7) FINAL WK-USAGE(8)
> ITEM WK-USAGE-MORTAR(7) FINAL WK-USAGE-MORTAR(8)
> ITEM WK-USAGE-OTHER(7) FINAL WK-USAGE-OTHER(8)
> ITEM WK-RECEIVED(7) FINAL WK-RECEIVED(8)
> ITEM WK-ACT-CLSTOCK(7) FINAL WK-ACT-CLSTOCK(8)
> ITEM WK-END-DATE(8) FINAL WK-END-DATE(9)
> ITEM WK-USAGE(8) FINAL WK-USAGE (9)
> ITEM WK-USAGE-MORTAR(8) FINAL WK-USAGE-MORTAR (9)
> ITEM WK-USAGE-OTHER(8) FINAL WK-USAGE-OTHER (9)
> ITEM WK-RECEIVED(8) FINAL WK-RECEIVED(9)
> ITEM WK-ACT-CLSTOCK(8) FINAL WK-ACT-CLSTOCK(9)
> ITEM WK-END-DATE(9) FINAL WK-END-DATE(10)
> ITEM WK-USAGE(9) FINAL WK-USAGE(10)
> ITEM WK-USAGE-MORTAR(9) FINAL WK-USAGE-MORTAR(10)
> ITEM WK-USAGE-OTHER(9) FINAL WK-USAGE-OTHER(10)
> ITEM WK-RECEIVED(9) FINAL WK-RECEIVED(10)
> ITEM WK-ACT-CLSTOCK(9) FINAL WK-ACT-CLSTOCK(10)
> ITEM WK-END-DATE(10) FINAL WK-END-DATE(11)
> ITEM WK-USAGE(10) FINAL WK-USAGE(11)
> ITEM WK-USAGE-MORTAR(10) FINAL WK-USAGE-MORTAR(11)
> ITEM WK-USAGE-OTHER(10) FINAL WK-USAGE-OTHER(11)
> ITEM WK-RECEIVED(10) FINAL WK-RECEIVED(11)
> ITEM WK-ACT-CLSTOCK(10) FINAL WK-ACT-CLSTOCK(11)
> ITEM WK-END-DATE(11) FINAL WK-END-DATE(12)
> ITEM WK-USAGE(11) FINAL WK-USAGE(12)
> ITEM WK-USAGE-MORTAR(11) FINAL WK-USAGE-MORTAR(12)
> ITEM WK-USAGE-OTHER(11) FINAL WK-USAGE-OTHER(12)
> ITEM WK-RECEIVED(11) FINAL WK-RECEIVED(12)
> ITEM WK-ACT-CLSTOCK(11) FINAL WK-ACT-CLSTOCK(12)
> ITEM WK-END-DATE(12) FINAL WK-END-DATE(13)
> ITEM WK-USAGE(12) FINAL WK-USAGE(13)
> ITEM WK-USAGE-MORTAR(12) FINAL WK-USAGE-MORTAR(13)
> ITEM WK-USAGE-OTHER(12) FINAL WK-USAGE-OTHER(13)
> ITEM WK-RECEIVED(12) FINAL WK-RECEIVED(13)
> ITEM WK-ACT-CLSTOCK(12) FINAL WK-ACT-CLSTOCK(13)
> ITEM WK-END-DATE(13) FINAL GT-WK-END-DATE
> ITEM WK-USAGE(13) FINAL 0
> ITEM WK-USAGE-MORTAR(13) FINAL 0
> ITEM WK-USAGE-OTHER(13) FINAL 0
> ITEM WK-RECEIVED(13) FINAL 0
> ITEM WK-ACT-CLSTOCK(13) FINAL 0
>
> This is the section of the jobstream that shows the error
>
> 68 > USE VS4040PS.LVPHOUSE.EXE NOL
> 69 VS4040PS * Version H.01.003
> 70
> 71 10/03/2009 19:14 Hanson Aggregates
> 1
> 72
> 73 Run: VS4040PC
> 74 Request: ONE
> 75
> 76
> 77 Executing request ONE ...
> 78
> ----------------------------------------------------------------------
> 79 Record has been changed since you found it.
> ]
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 80 File: VS-ORDER
> 81 Linkitem: CUST-ACNO 0118 933066
> 82 Linkitem: ARC-ORDNO 644 200903100007
> 83 Linkitem: PLANT-DAY-REF 644 20090310
> 84 Linkitem: VS-JOB-REF 759R
> 85
> 86 Action Taken: Report and Continue.
> 87
> ----------------------------------------------------------------------
> 88
> 89 Records read:
> 90 VS-ORDER 394,902
> 91 VS-CUST-JOB 1,306
> 92 VS-CUST-MIX 1,285
> 93 LATEST-MIX 42,116
> 94
> 95 Transactions processed: 1,245
> 96
> 97 Records processed: Added Updated
Unchanged
>
> 98 VS-ORDER 0 127
1,117
>
> 99
> 00 Finished.
> 01
> 02 > EXIT
>
>
>
> The information in this e-mail and any attachments is confidential and
may
> be subject to legal professional privilege. It is intended solely for
the
> attention and use of the named addressee(s). If you are not the
intended
> recipient, or person responsible for delivering this information to
the
> intended recipient, please notify the sender immediately. Unless you
are
> the intended recipient or his/her representative you are not
authorised
> to, and must not, read, copy, distribute, use or retain this message
or
> any part of it.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
>
http://lists.sowder.com/pipermail/powerh-l/attachments/20090311/b6308a37
/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 46, Issue 6
> ***************************************
>
--
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
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.
More information about the powerh-l
mailing list