VMS to WINDOWS approach ( set lang SQL - gen database...) ?
Tim Cummings
tim.cummings@frequencymarketing.com
Thu, 10 Mar 2005 08:35:29 -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_01C52576.06B522B0
Content-Type: text/plain;
charset="iso-8859-1"
I was just surprised that the set lang sql did not generate the lowest level
items.
If I have a column in Image called FLAGS (4 bytes) and it is defined in the
PH dictionary as redefined by FLAG_A, FLAG-B, FLAG-C, FLAG-D (each, one
byte). I would have expected it to create the columns for FLAG-A ... FLAG-D
not create the column called FLAGS.
Timothy J Cummings
Ridgewood Corporate Center
1000 Summit Drive, Suite 200
Milford, Ohio 45150
tim.cummings@frequencymarketing.com
-----Original Message-----
From: Robert Edis [mailto:robeconsult@sbcglobal.net]
Sent: Wednesday, March 09, 2005 7:32 PM
To: PowerHouse List
Subject: RE: VMS to WINDOWS approach ( set lang SQL - gen database...) ?
Tim
In general RDBMS's do not support nested columns or
arrays in tables. As you are generating SQL script I
assume it will be applied to a RDBMS and therefore
non-compliant schema constructs such as nested columns
will not be output.
Blue
--- Tim Cummings <tim.cummings@frequencymarketing.com>
wrote:
> 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.
> > > > >
>
=== message truncated ===
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
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_01C52576.06B522B0
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 was just surprised that the set lang sql did not =
generate the lowest level items. </FONT>
</P>
<P><FONT SIZE=3D2>If I have a column in Image called FLAGS (4 bytes) =
and it is defined in the PH dictionary as redefined by FLAG_A, FLAG-B, =
FLAG-C, FLAG-D (each, one byte). I would have expected it to =
create the columns for FLAG-A ... FLAG-D not create the column called =
FLAGS.</FONT></P>
<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: Robert Edis [<A =
HREF=3D"mailto:robeconsult@sbcglobal.net">mailto:robeconsult@sbcglobal.n=
et</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Wednesday, March 09, 2005 7:32 PM</FONT>
<BR><FONT SIZE=3D2>To: PowerHouse List</FONT>
<BR><FONT SIZE=3D2>Subject: RE: VMS to WINDOWS approach ( set lang SQL =
- gen database...) ?</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Tim</FONT>
</P>
<P><FONT SIZE=3D2>In general RDBMS's do not support nested columns =
or</FONT>
<BR><FONT SIZE=3D2>arrays in tables. As you are generating SQL =
script I</FONT>
<BR><FONT SIZE=3D2>assume it will be applied to a RDBMS and =
therefore</FONT>
<BR><FONT SIZE=3D2>non-compliant schema constructs such as nested =
columns</FONT>
<BR><FONT SIZE=3D2>will not be output.</FONT>
</P>
<P><FONT SIZE=3D2>Blue</FONT>
</P>
<P><FONT SIZE=3D2>--- Tim Cummings =
<tim.cummings@frequencymarketing.com></FONT>
<BR><FONT SIZE=3D2>wrote:</FONT>
</P>
<P><FONT SIZE=3D2>> I tried this on MPE and the only bad thing about =
it</FONT>
<BR><FONT SIZE=3D2>> is if you have a column</FONT>
<BR><FONT SIZE=3D2>> that is re-defined, it only creates the higher =
level</FONT>
<BR><FONT SIZE=3D2>> item.</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Is there an option to get it to create columns =
for</FONT>
<BR><FONT SIZE=3D2>> the lower level items?</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><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>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><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</FONT>
<BR><FONT SIZE=3D2>> - gen database...) ?</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> I have been asked if this approach ( set lang =
SQL -</FONT>
<BR><FONT SIZE=3D2>> gen database...) should</FONT>
<BR><FONT SIZE=3D2>> work on PH7 on VMS; I then remembered that BobD =
told</FONT>
<BR><FONT SIZE=3D2>> the list that he tested</FONT>
<BR><FONT SIZE=3D2>> this and his words are pasted below -</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Well, this doesn't happen every day. This is a =
new</FONT>
<BR><FONT SIZE=3D2>> one on me as well.</FONT>
<BR><FONT SIZE=3D2>> I've tried it in 8.40D on OpenVMS and 8.41D on</=
FONT>
<BR><FONT SIZE=3D2>> Windows. I'll make a bold</FONT>
<BR><FONT SIZE=3D2>> assumption that UNIX works like Windows. On =
OpenVMS,</FONT>
<BR><FONT SIZE=3D2>> the file created is</FONT>
<BR><FONT SIZE=3D2>> named QSHOSQL.TXT. On UNIX and Windows the file =
is</FONT>
<BR><FONT SIZE=3D2>> named qshogen.sql.</FONT>
<BR><FONT SIZE=3D2>> The general syntax is...</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> And if anyone cares, QSHOW on MPE/iX does the =
same,</FONT>
<BR><FONT SIZE=3D2>> generating a file named</FONT>
<BR><FONT SIZE=3D2>> QSHOSQL. And yes, it generates a table for =
each</FONT>
<BR><FONT SIZE=3D2>> dataset in an IMAGE</FONT>
<BR><FONT SIZE=3D2>> database.</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Regards, Joe.</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><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</FONT>
<BR><FONT SIZE=3D2>> 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>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Our recommendation when migrating from =
IMAGE/indexed</FONT>
<BR><FONT SIZE=3D2>> to relational is to</FONT>
<BR><FONT SIZE=3D2>> use Axiant. However, there is an =
undocumented</FONT>
<BR><FONT SIZE=3D2>> feature (no I don't know</FONT>
<BR><FONT SIZE=3D2>> why it's undocumented) of QSHOW that will let =
you</FONT>
<BR><FONT SIZE=3D2>> generate a skeleton</FONT>
<BR><FONT SIZE=3D2>> SQL table definition.</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> In QSHOW:</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> SET LANG SQL</FONT>
<BR><FONT SIZE=3D2>> GENERATE DATABASE <indexed-file></FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Yes, I know it's a FILE and not a DATABASE, but =
you</FONT>
<BR><FONT SIZE=3D2>> have to fool QSHOW</FONT>
<BR><FONT SIZE=3D2>> into thinking it's dealing with =
relational.</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> On Windows, this create a file named =
qshogen.sql</FONT>
<BR><FONT SIZE=3D2>> with the basic table</FONT>
<BR><FONT SIZE=3D2>> definition. If you generate all your files this =
way</FONT>
<BR><FONT SIZE=3D2>> and put the results</FONT>
<BR><FONT SIZE=3D2>> together, and add the constraints and so on, =
you can</FONT>
<BR><FONT SIZE=3D2>> come up with a</FONT>
<BR><FONT SIZE=3D2>> fairly complete database schema. It's not as =
good as</FONT>
<BR><FONT SIZE=3D2>> Axiant but it's a</FONT>
<BR><FONT SIZE=3D2>> start.</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Bob</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><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</FONT>
<BR><FONT SIZE=3D2>> 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>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> I know there have been many conversations =
flying</FONT>
<BR><FONT SIZE=3D2>> back</FONT>
<BR><FONT SIZE=3D2>> and forth about how to convert from =
ISAM/KSAM/RMS to</FONT>
<BR><FONT SIZE=3D2>> a database. And</FONT>
<BR><FONT SIZE=3D2>> unless I didn't see the actually =
"final" message.</FONT>
<BR><FONT SIZE=3D2>> There wasn't a nice</FONT>
<BR><FONT SIZE=3D2>> way of doing this unless you are going =
Axiant.</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Mom always told me to never touched the =
stuff.</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><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>
<BR><FONT SIZE=3D2>> </FONT>
<BR><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>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Ken</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><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</FONT>
<BR><FONT SIZE=3D2>> 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</FONT>
<BR><FONT SIZE=3D2>> 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</FONT>
<BR><FONT SIZE=3D2>> definitions</FONT>
<BR><FONT SIZE=3D2>> > > from QSHOW on the UNIX box and =
cleaned them up</FONT>
<BR><FONT SIZE=3D2>> 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</FONT>
<BR><FONT SIZE=3D2>> weeks</FONT>
<BR><FONT SIZE=3D2>> > > (working at night). And that app was =
written</FONT>
<BR><FONT SIZE=3D2>> 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</FONT>
<BR><FONT SIZE=3D2>> 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</FONT>
<BR><FONT SIZE=3D2>> 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>> </FONT>
<BR><FONT SIZE=3D2>=3D=3D=3D message truncated =3D=3D=3D</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_01C52576.06B522B0--