VMS to WINDOWS approach ( set lang SQL - gen database...) ?
Tim Cummings
tim.cummings@frequencymarketing.com
Wed, 9 Mar 2005 14:43:44 -0500
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C524E0.4D8B0D80
Content-Type: text/plain;
charset="iso-8859-1"
I tried this on MPE and the only bad thing about it is if you have a column
that is re-defined, it only creates the higher level item.
Is there an option to get it to create columns for the lower level items?
Timothy J Cummings
Ridgewood Corporate Center
1000 Summit Drive, Suite 200
Milford, Ohio 45150
tim.cummings@frequencymarketing.com
-----Original Message-----
From: Joe Boyle [mailto:atla38@dsl.pipex.com]
Sent: Wednesday, March 09, 2005 2:33 PM
To: powerh-l@lists.sowder.com
Subject: RE: VMS to WINDOWS approach ( set lang SQL - gen database...) ?
I have been asked if this approach ( set lang SQL - gen database...) should
work on PH7 on VMS; I then remembered that BobD told the list that he tested
this and his words are pasted below -
Well, this doesn't happen every day. This is a new one on me as well.
I've tried it in 8.40D on OpenVMS and 8.41D on Windows. I'll make a bold
assumption that UNIX works like Windows. On OpenVMS, the file created is
named QSHOSQL.TXT. On UNIX and Windows the file is named qshogen.sql.
The general syntax is...
And if anyone cares, QSHOW on MPE/iX does the same, generating a file named
QSHOSQL. And yes, it generates a table for each dataset in an IMAGE
database.
Regards, Joe.
-----Original Message-----
From: powerh-l-admin@lists.sowder.com
[mailto:powerh-l-admin@lists.sowder.com] On Behalf Of Deskin, Bob
Sent: 09 March 2005 15:33
To: powerh-l@lists.sowder.com
Subject: RE: Anyone have Moved from VMS to WINDOWS?
Our recommendation when migrating from IMAGE/indexed to relational is to
use Axiant. However, there is an undocumented feature (no I don't know
why it's undocumented) of QSHOW that will let you generate a skeleton
SQL table definition.
In QSHOW:
SET LANG SQL
GENERATE DATABASE <indexed-file>
Yes, I know it's a FILE and not a DATABASE, but you have to fool QSHOW
into thinking it's dealing with relational.
On Windows, this create a file named qshogen.sql with the basic table
definition. If you generate all your files this way and put the results
together, and add the constraints and so on, you can come up with a
fairly complete database schema. It's not as good as Axiant but it's a
start.
Bob
-----Original Message-----
From: powerh-l-admin@lists.sowder.com
[mailto:powerh-l-admin@lists.sowder.com] On Behalf Of Ken Langendock
Sent: March 9, 2005 10:18 AM
To: powerh-l@lists.sowder.com
Subject: Re: Anyone have Moved from VMS to WINDOWS?
I know there have been many conversations flying back
and forth about how to convert from ISAM/KSAM/RMS to a database. And
unless I didn't see the actually "final" message. There wasn't a nice
way of doing this unless you are going Axiant.
Mom always told me to never touched the stuff.
When I converted from ISAM (or all of the above) I
exported my file definitions in QSHOW to PDL.
Then I started my Search and Replace routine.
1) change all the - to _
2) change all file names to sql sytax "create..."
3) changed all item statements to sql syntax.
4) etc.
5)....test/retest.
Ken
--- Othman <othman2@gmail.com> wrote:
> how about the database migration.
>
> our system running with the following environment
> -System: HP 3000/968 Rx
> -OS : MPE / ix HP 31900
>
> -Reporting Quiz - Cognos PowerHouse 8.19.C4 version.
>
> -Screen Designing QDESIGN - Cognos PowerHouse
> 8.19.C4 version.
>
> -Transaction Processing QTP - Cognos PowerHouse
> 8.19.C4 version.
>
> -Data Base Dictionary PDL - Cognos PowerHouse
> 8.19.C4 version.
>
> what is the recommended path to migrate to NT ,MS
> SQL
>
> On Wed, 9 Mar 2005 09:44:56 -0500 (EST), Ken
> Langendock
> <ken.langendock@rogers.com> wrote:
> > I'm not sure what you mean by tool.
> >
> > I used a free ware search and replace tool that I downloaded from
> > the net to fix the source.
> >
> > The last conversion was from DG ISAM to ISAM for
> NT.
> > So all I did there was export the file definitions
> > from QSHOW on the UNIX box and cleaned them up for
> NT.
> >
> > Most of the time I convert everything by search
> and
> > replace then do the rest by hand.
> >
> > By using my application as a building block. I
> > converted a 100 program application within 2 weeks
> > (working at night). And that app was written back
> in
> > the early 80's, it was all crap code.
> >
> > Ken
> >
> > --- Othman <othman2@gmail.com> wrote:
> > > what tool did you use for migration
> > >
> > >
> > > On Wed, 9 Mar 2005 08:50:58 -0500 (EST), Ken
> > > Langendock
> > > <ken.langendock@rogers.com> wrote:
> > > > I have converted an application from many
> machines
> > > to
> > > > other lines.
> > > >
> > > > I started out on the VAX (in my opinion the
> best
> > > > machine still to this day), then to HP3000,
> then
> > > UNIX
> > > > (HP, SUN, IBM, DG, etc) then to Powerhouse NT.
> > > >
> > > > I created a system management module that
> takes
> > > all of
> > > > the O/S level code away from your application.
> > > This
> > > > allows me to convert from one platform to
> another
> > > > transparently to the User/Application.
> > > >
> > > > The problems you are going to encounter are:
> > > > 1) Quiz does not run in compiled form (at
> least it
> > > > didn't work correctly at the time of
> > > implementation).
> > > > Not a big problem since every user has their
> own
> > > CPU,
> > > > they do not notice.
> > > > 2) There is no real Batch Queue. Everything is
> run
> > > > interactively. I didn't have time to create
> one
> > > and
> > > > the client didn't care as the performance was
> 10
> > > times
> > > > faster.
> > > > 3) Printing is a little more difficult to set
> up.
> > > The
> > > > printers have to be set up on the network
> server.
> > > My
> > > > system management module took care of this,
> but
> > > the
> > > > testing was a bitch.
> > > > 4) I used strictly Powerhouse, no COBOL, etc.
> That
> > > may
> > > > be a problem for you, depends on what you are
> > > doing in
> > > > there.
> > > >
> > > > Hope this helps.
> > > > Ken@langendock.com
> > > >
> > > > = = = = = = = = = = = = = = = = = = = = = = =
> = =
> > > = = =
> > > > Mailing list: powerh-l@lists.sowder.com
> > > > Subscribe: "subscribe" in message body to
> > > powerh-l-request@lists.sowder.com
> > > > Unsubscribe: "unsubscribe <password>" in
> message
> > > body to powerh-l-request@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.
> > > >
> > >
> >
>
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l@lists.sowder.com
Subscribe: "subscribe" in message body to
powerh-l-request@lists.sowder.com
Unsubscribe: "unsubscribe <password>" in message body to
powerh-l-request@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.
This message may contain privileged and/or confidential information.
If you have received this e-mail in error or are not the intended recipient,
you may not use, copy, disseminate or distribute it; do not open any
attachments, delete it immediately from your system and notify the sender
promptly by e-mail that you have done so. Thank you.
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l@lists.sowder.com
Subscribe: "subscribe" in message body to powerh-l-request@lists.sowder.com
Unsubscribe: "unsubscribe <password>" in message body to
powerh-l-request@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.
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l@lists.sowder.com
Subscribe: "subscribe" in message body to powerh-l-request@lists.sowder.com
Unsubscribe: "unsubscribe <password>" in message body to
powerh-l-request@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.
------_=_NextPart_001_01C524E0.4D8B0D80
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.45">
<TITLE>RE: VMS to WINDOWS approach ( set lang SQL - gen database...) =
?</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>I tried this on MPE and the only bad thing about it =
is if you have a column that is re-defined, it only creates the higher =
level item.</FONT></P>
<P><FONT SIZE=3D2>Is there an option to get it to create columns for =
the lower level items?</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Timothy J Cummings</FONT>
<BR><FONT SIZE=3D2>Ridgewood Corporate Center</FONT>
<BR><FONT SIZE=3D2>1000 Summit Drive, Suite 200</FONT>
<BR><FONT SIZE=3D2>Milford, Ohio 45150</FONT>
<BR><FONT SIZE=3D2>tim.cummings@frequencymarketing.com</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Joe Boyle [<A =
HREF=3D"mailto:atla38@dsl.pipex.com">mailto:atla38@dsl.pipex.com</A>]</F=
ONT>
<BR><FONT SIZE=3D2>Sent: Wednesday, March 09, 2005 2:33 PM</FONT>
<BR><FONT SIZE=3D2>To: powerh-l@lists.sowder.com</FONT>
<BR><FONT SIZE=3D2>Subject: RE: VMS to WINDOWS approach ( set lang SQL =
- gen database...) ?</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>I have been asked if this approach ( set lang SQL - =
gen database...) should</FONT>
<BR><FONT SIZE=3D2>work on PH7 on VMS; I then remembered that BobD told =
the list that he tested</FONT>
<BR><FONT SIZE=3D2>this and his words are pasted below -</FONT>
</P>
<P><FONT SIZE=3D2>Well, this doesn't happen every day. This is a new =
one on me as well.</FONT>
<BR><FONT SIZE=3D2>I've tried it in 8.40D on OpenVMS and 8.41D on =
Windows. I'll make a bold</FONT>
<BR><FONT SIZE=3D2>assumption that UNIX works like Windows. On OpenVMS, =
the file created is</FONT>
<BR><FONT SIZE=3D2>named QSHOSQL.TXT. On UNIX and Windows the file is =
named qshogen.sql.</FONT>
<BR><FONT SIZE=3D2>The general syntax is...</FONT>
</P>
<P><FONT SIZE=3D2>And if anyone cares, QSHOW on MPE/iX does the same, =
generating a file named</FONT>
<BR><FONT SIZE=3D2>QSHOSQL. And yes, it generates a table for each =
dataset in an IMAGE</FONT>
<BR><FONT SIZE=3D2>database.</FONT>
</P>
<P><FONT SIZE=3D2>Regards, Joe.</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: powerh-l-admin@lists.sowder.com</FONT>
<BR><FONT SIZE=3D2>[<A =
HREF=3D"mailto:powerh-l-admin@lists.sowder.com">mailto:powerh-l-admin@li=
sts.sowder.com</A>] On Behalf Of Deskin, Bob</FONT>
<BR><FONT SIZE=3D2>Sent: 09 March 2005 15:33</FONT>
<BR><FONT SIZE=3D2>To: powerh-l@lists.sowder.com</FONT>
<BR><FONT SIZE=3D2>Subject: RE: Anyone have Moved from VMS to =
WINDOWS?</FONT>
</P>
<P><FONT SIZE=3D2>Our recommendation when migrating from IMAGE/indexed =
to relational is to</FONT>
<BR><FONT SIZE=3D2>use Axiant. However, there is an undocumented =
feature (no I don't know</FONT>
<BR><FONT SIZE=3D2>why it's undocumented) of QSHOW that will let you =
generate a skeleton</FONT>
<BR><FONT SIZE=3D2>SQL table definition.</FONT>
</P>
<P><FONT SIZE=3D2>In QSHOW:</FONT>
</P>
<P><FONT SIZE=3D2>SET LANG SQL</FONT>
<BR><FONT SIZE=3D2>GENERATE DATABASE <indexed-file></FONT>
</P>
<P><FONT SIZE=3D2>Yes, I know it's a FILE and not a DATABASE, but you =
have to fool QSHOW</FONT>
<BR><FONT SIZE=3D2>into thinking it's dealing with relational.</FONT>
</P>
<P><FONT SIZE=3D2>On Windows, this create a file named qshogen.sql with =
the basic table</FONT>
<BR><FONT SIZE=3D2>definition. If you generate all your files this way =
and put the results</FONT>
<BR><FONT SIZE=3D2>together, and add the constraints and so on, you can =
come up with a</FONT>
<BR><FONT SIZE=3D2>fairly complete database schema. It's not as good as =
Axiant but it's a</FONT>
<BR><FONT SIZE=3D2>start.</FONT>
</P>
<P><FONT SIZE=3D2>Bob</FONT>
</P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: powerh-l-admin@lists.sowder.com</FONT>
<BR><FONT SIZE=3D2>[<A =
HREF=3D"mailto:powerh-l-admin@lists.sowder.com">mailto:powerh-l-admin@li=
sts.sowder.com</A>] On Behalf Of Ken Langendock</FONT>
<BR><FONT SIZE=3D2>Sent: March 9, 2005 10:18 AM</FONT>
<BR><FONT SIZE=3D2>To: powerh-l@lists.sowder.com</FONT>
<BR><FONT SIZE=3D2>Subject: Re: Anyone have Moved from VMS to =
WINDOWS?</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>I know there have been many conversations flying =
back</FONT>
<BR><FONT SIZE=3D2>and forth about how to convert from ISAM/KSAM/RMS to =
a database. And</FONT>
<BR><FONT SIZE=3D2>unless I didn't see the actually "final" =
message. There wasn't a nice</FONT>
<BR><FONT SIZE=3D2>way of doing this unless you are going =
Axiant.</FONT>
</P>
<P><FONT SIZE=3D2>Mom always told me to never touched the stuff.</FONT>
</P>
<P><FONT SIZE=3D2>When I converted from ISAM (or all of the above) =
I</FONT>
<BR><FONT SIZE=3D2>exported my file definitions in QSHOW to PDL.</FONT>
</P>
<P><FONT SIZE=3D2>Then I started my Search and Replace routine. </FONT>
<BR><FONT SIZE=3D2>1) change all the - to _</FONT>
<BR><FONT SIZE=3D2>2) change all file names to sql sytax =
"create..."</FONT>
<BR><FONT SIZE=3D2>3) changed all item statements to sql syntax.</FONT>
<BR><FONT SIZE=3D2>4) etc.</FONT>
<BR><FONT SIZE=3D2>5)....test/retest.</FONT>
</P>
<P><FONT SIZE=3D2>Ken</FONT>
</P>
<BR>
<P><FONT SIZE=3D2> --- Othman <othman2@gmail.com> wrote: =
</FONT>
<BR><FONT SIZE=3D2>> how about the database migration.</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> our system running with the following =
environment </FONT>
<BR><FONT SIZE=3D2>> -System: HP =
3000/968 Rx</FONT>
<BR><FONT SIZE=3D2>> -OS : MPE / ix HP 31900</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> -Reporting Quiz - Cognos =
PowerHouse 8.19.C4 version.</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> -Screen Designing =
QDESIGN - Cognos PowerHouse</FONT>
<BR><FONT SIZE=3D2>> 8.19.C4 version.</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> -Transaction =
Processing QTP - Cognos =
PowerHouse</FONT>
<BR><FONT SIZE=3D2>> 8.19.C4 version.</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> -Data Base Dictionary PDL - Cognos =
PowerHouse</FONT>
<BR><FONT SIZE=3D2>> 8.19.C4 version.</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> what is the recommended path to migrate to NT =
,MS</FONT>
<BR><FONT SIZE=3D2>> SQL</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> On Wed, 9 Mar 2005 09:44:56 -0500 (EST), =
Ken</FONT>
<BR><FONT SIZE=3D2>> Langendock</FONT>
<BR><FONT SIZE=3D2>> <ken.langendock@rogers.com> wrote:</FONT>
<BR><FONT SIZE=3D2>> > I'm not sure what you mean by tool.</FONT>
<BR><FONT SIZE=3D2>> > </FONT>
<BR><FONT SIZE=3D2>> > I used a free ware search and replace tool =
that I downloaded from </FONT>
<BR><FONT SIZE=3D2>> > the net to fix the source.</FONT>
<BR><FONT SIZE=3D2>> > </FONT>
<BR><FONT SIZE=3D2>> > The last conversion was from DG ISAM to =
ISAM for</FONT>
<BR><FONT SIZE=3D2>> NT.</FONT>
<BR><FONT SIZE=3D2>> > So all I did there was export the file =
definitions</FONT>
<BR><FONT SIZE=3D2>> > from QSHOW on the UNIX box and cleaned =
them up for</FONT>
<BR><FONT SIZE=3D2>> NT.</FONT>
<BR><FONT SIZE=3D2>> > </FONT>
<BR><FONT SIZE=3D2>> > Most of the time I convert everything by =
search</FONT>
<BR><FONT SIZE=3D2>> and</FONT>
<BR><FONT SIZE=3D2>> > replace then do the rest by hand.</FONT>
<BR><FONT SIZE=3D2>> > </FONT>
<BR><FONT SIZE=3D2>> > By using my application as a building =
block. I</FONT>
<BR><FONT SIZE=3D2>> > converted a 100 program application within =
2 weeks</FONT>
<BR><FONT SIZE=3D2>> > (working at night). And that app was =
written back</FONT>
<BR><FONT SIZE=3D2>> in</FONT>
<BR><FONT SIZE=3D2>> > the early 80's, it was all crap =
code.</FONT>
<BR><FONT SIZE=3D2>> > </FONT>
<BR><FONT SIZE=3D2>> > Ken</FONT>
<BR><FONT SIZE=3D2>> > </FONT>
<BR><FONT SIZE=3D2>> > --- Othman <othman2@gmail.com> =
wrote:</FONT>
<BR><FONT SIZE=3D2>> > > what tool did you use for =
migration</FONT>
<BR><FONT SIZE=3D2>> > ></FONT>
<BR><FONT SIZE=3D2>> > ></FONT>
<BR><FONT SIZE=3D2>> > > On Wed, 9 Mar 2005 08:50:58 -0500 =
(EST), Ken</FONT>
<BR><FONT SIZE=3D2>> > > Langendock</FONT>
<BR><FONT SIZE=3D2>> > > <ken.langendock@rogers.com> =
wrote:</FONT>
<BR><FONT SIZE=3D2>> > > > I have converted an application =
from many</FONT>
<BR><FONT SIZE=3D2>> machines</FONT>
<BR><FONT SIZE=3D2>> > > to</FONT>
<BR><FONT SIZE=3D2>> > > > other lines.</FONT>
<BR><FONT SIZE=3D2>> > > ></FONT>
<BR><FONT SIZE=3D2>> > > > I started out on the VAX (in my =
opinion the</FONT>
<BR><FONT SIZE=3D2>> best</FONT>
<BR><FONT SIZE=3D2>> > > > machine still to this day), then =
to HP3000,</FONT>
<BR><FONT SIZE=3D2>> then</FONT>
<BR><FONT SIZE=3D2>> > > UNIX</FONT>
<BR><FONT SIZE=3D2>> > > > (HP, SUN, IBM, DG, etc) then to =
Powerhouse NT.</FONT>
<BR><FONT SIZE=3D2>> > > ></FONT>
<BR><FONT SIZE=3D2>> > > > I created a system management =
module that</FONT>
<BR><FONT SIZE=3D2>> takes</FONT>
<BR><FONT SIZE=3D2>> > > all of</FONT>
<BR><FONT SIZE=3D2>> > > > the O/S level code away from =
your application.</FONT>
<BR><FONT SIZE=3D2>> > > This</FONT>
<BR><FONT SIZE=3D2>> > > > allows me to convert from one =
platform to</FONT>
<BR><FONT SIZE=3D2>> another</FONT>
<BR><FONT SIZE=3D2>> > > > transparently to the =
User/Application.</FONT>
<BR><FONT SIZE=3D2>> > > ></FONT>
<BR><FONT SIZE=3D2>> > > > The problems you are going to =
encounter are:</FONT>
<BR><FONT SIZE=3D2>> > > > 1) Quiz does not run in compiled =
form (at</FONT>
<BR><FONT SIZE=3D2>> least it</FONT>
<BR><FONT SIZE=3D2>> > > > didn't work correctly at the =
time of</FONT>
<BR><FONT SIZE=3D2>> > > implementation).</FONT>
<BR><FONT SIZE=3D2>> > > > Not a big problem since every =
user has their</FONT>
<BR><FONT SIZE=3D2>> own</FONT>
<BR><FONT SIZE=3D2>> > > CPU,</FONT>
<BR><FONT SIZE=3D2>> > > > they do not notice.</FONT>
<BR><FONT SIZE=3D2>> > > > 2) There is no real Batch Queue. =
Everything is</FONT>
<BR><FONT SIZE=3D2>> run</FONT>
<BR><FONT SIZE=3D2>> > > > interactively. I didn't have =
time to create</FONT>
<BR><FONT SIZE=3D2>> one</FONT>
<BR><FONT SIZE=3D2>> > > and</FONT>
<BR><FONT SIZE=3D2>> > > > the client didn't care as the =
performance was</FONT>
<BR><FONT SIZE=3D2>> 10</FONT>
<BR><FONT SIZE=3D2>> > > times</FONT>
<BR><FONT SIZE=3D2>> > > > faster.</FONT>
<BR><FONT SIZE=3D2>> > > > 3) Printing is a little more =
difficult to set</FONT>
<BR><FONT SIZE=3D2>> up.</FONT>
<BR><FONT SIZE=3D2>> > > The</FONT>
<BR><FONT SIZE=3D2>> > > > printers have to be set up on =
the network</FONT>
<BR><FONT SIZE=3D2>> server.</FONT>
<BR><FONT SIZE=3D2>> > > My</FONT>
<BR><FONT SIZE=3D2>> > > > system management module took =
care of this,</FONT>
<BR><FONT SIZE=3D2>> but</FONT>
<BR><FONT SIZE=3D2>> > > the</FONT>
<BR><FONT SIZE=3D2>> > > > testing was a bitch.</FONT>
<BR><FONT SIZE=3D2>> > > > 4) I used strictly Powerhouse, =
no COBOL, etc.</FONT>
<BR><FONT SIZE=3D2>> That</FONT>
<BR><FONT SIZE=3D2>> > > may</FONT>
<BR><FONT SIZE=3D2>> > > > be a problem for you, depends on =
what you are</FONT>
<BR><FONT SIZE=3D2>> > > doing in</FONT>
<BR><FONT SIZE=3D2>> > > > there.</FONT>
<BR><FONT SIZE=3D2>> > > ></FONT>
<BR><FONT SIZE=3D2>> > > > Hope this helps.</FONT>
<BR><FONT SIZE=3D2>> > > > Ken@langendock.com</FONT>
<BR><FONT SIZE=3D2>> > > ></FONT>
<BR><FONT SIZE=3D2>> > > > =3D =3D =3D =3D =3D =3D =3D =3D =
=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D</FONT>
<BR><FONT SIZE=3D2>> =3D =3D</FONT>
<BR><FONT SIZE=3D2>> > > =3D =3D =3D</FONT>
<BR><FONT SIZE=3D2>> > > > Mailing list: =
powerh-l@lists.sowder.com</FONT>
<BR><FONT SIZE=3D2>> > > > Subscribe: "subscribe" =
in message body to</FONT>
<BR><FONT SIZE=3D2>> > > =
powerh-l-request@lists.sowder.com</FONT>
<BR><FONT SIZE=3D2>> > > > Unsubscribe: "unsubscribe =
<password>" in</FONT>
<BR><FONT SIZE=3D2>> message</FONT>
<BR><FONT SIZE=3D2>> > > body to =
powerh-l-request@lists.sowder.com</FONT>
<BR><FONT SIZE=3D2>> > > ></FONT>
<BR><FONT SIZE=3D2>> <A =
HREF=3D"http://lists.sowder.com/mailman/listinfo/powerh-l" =
TARGET=3D"_blank">http://lists.sowder.com/mailman/listinfo/powerh-l</A><=
/FONT>
<BR><FONT SIZE=3D2>> > > > This list is closed, thus to =
post to the list</FONT>
<BR><FONT SIZE=3D2>> you</FONT>
<BR><FONT SIZE=3D2>> > > must be a subscriber.</FONT>
<BR><FONT SIZE=3D2>> > > ></FONT>
<BR><FONT SIZE=3D2>> > ></FONT>
<BR><FONT SIZE=3D2>> ></FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =
=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D</FONT>
<BR><FONT SIZE=3D2>Mailing list: powerh-l@lists.sowder.com</FONT>
<BR><FONT SIZE=3D2>Subscribe: "subscribe" in message body =
to</FONT>
<BR><FONT SIZE=3D2>powerh-l-request@lists.sowder.com</FONT>
<BR><FONT SIZE=3D2>Unsubscribe: "unsubscribe =
<password>" in message body to</FONT>
<BR><FONT SIZE=3D2>powerh-l-request@lists.sowder.com</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://lists.sowder.com/mailman/listinfo/powerh-l" =
TARGET=3D"_blank">http://lists.sowder.com/mailman/listinfo/powerh-l</A><=
/FONT>
<BR><FONT SIZE=3D2>This list is closed, thus to post to the list you =
must be a subscriber. </FONT>
<BR><FONT SIZE=3D2> </FONT>
<BR><FONT SIZE=3D2> This message =
may contain privileged and/or confidential information.</FONT>
<BR><FONT SIZE=3D2>If you have received this e-mail in error or are not =
the intended recipient,</FONT>
<BR><FONT SIZE=3D2>you may not use, copy, disseminate or distribute it; =
do not open any</FONT>
<BR><FONT SIZE=3D2>attachments, delete it immediately from your system =
and notify the sender</FONT>
<BR><FONT SIZE=3D2>promptly by e-mail that you have done so. =
Thank you. </FONT>
<BR><FONT SIZE=3D2> </FONT>
</P>
<P><FONT SIZE=3D2>=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =
=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D</FONT>
<BR><FONT SIZE=3D2>Mailing list: powerh-l@lists.sowder.com</FONT>
<BR><FONT SIZE=3D2>Subscribe: "subscribe" in message body to =
powerh-l-request@lists.sowder.com</FONT>
<BR><FONT SIZE=3D2>Unsubscribe: "unsubscribe =
<password>" in message body to</FONT>
<BR><FONT SIZE=3D2>powerh-l-request@lists.sowder.com</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://lists.sowder.com/mailman/listinfo/powerh-l" =
TARGET=3D"_blank">http://lists.sowder.com/mailman/listinfo/powerh-l</A><=
/FONT>
<BR><FONT SIZE=3D2>This list is closed, thus to post to the list you =
must be a subscriber.</FONT>
</P>
<P><FONT SIZE=3D2>=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =
=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D</FONT>
<BR><FONT SIZE=3D2>Mailing list: powerh-l@lists.sowder.com</FONT>
<BR><FONT SIZE=3D2>Subscribe: "subscribe" in message body to =
powerh-l-request@lists.sowder.com</FONT>
<BR><FONT SIZE=3D2>Unsubscribe: "unsubscribe =
<password>" in message body to =
powerh-l-request@lists.sowder.com</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://lists.sowder.com/mailman/listinfo/powerh-l" =
TARGET=3D"_blank">http://lists.sowder.com/mailman/listinfo/powerh-l</A><=
/FONT>
<BR><FONT SIZE=3D2>This list is closed, thus to post to the list you =
must be a subscriber.</FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C524E0.4D8B0D80--