VMS to WINDOWS approach ( set lang SQL - gen database...) ?
Glenn Baxter
Glenn@baxterit.com.au
Fri, 11 Mar 2005 06:07:08 +1100
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_01C525A4.5AED90F0
Content-Type: text/plain
Hi Tim,
It may be better to simply move the redifined items out of the redefinition
in your Pdl. As as stated by Blue, they will need to become specific columns
under most {all?} Rdbs. We have ported to SQLServer from Hp3000 Image and
Ksam etc, having used the Axiant Migration Workbench, which recognises the
redinitions and creates separate low order columns, as per your question.
All code instances which address the higher level parent will need to be
addressed individually {manually} though throughout code migration.
Regards Glenn Baxter, Baxter IT
_____
From: Tim Cummings [mailto:tim.cummings@frequencymarketing.com]
Sent: Friday, 11 March 2005 12:35 AM
To: PowerHouse List
Subject: RE: VMS to WINDOWS approach ( set lang SQL - gen database...) ?
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
<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 <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
<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
<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
<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_01C525A4.5AED90F0
Content-Type: text/html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>RE: VMS to WINDOWS approach ( set lang SQL - gen database...) ?</TITLE>
<META content="MSHTML 6.00.2900.2604" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left>
<P><FONT size=2><SPAN class=671150919-10032005>Hi </SPAN>Tim, </FONT></P>
<P><FONT size=2>It may be better to simply move the redifined items out of the
redefinition in your Pdl. As as stated by Blue, they will need to become
specific columns under most {all?} Rdbs. We have ported to SQLServer from Hp3000
Image and Ksam etc<SPAN class=671150919-10032005>, having </SPAN>used <SPAN
class=671150919-10032005>the </SPAN>Axiant <SPAN
class=671150919-10032005>Migration Workbench, </SPAN>which recognises the
redinitions and creates separate <SPAN class=671150919-10032005>low order
</SPAN>columns<SPAN class=671150919-10032005>, as per your
question.</SPAN></FONT></P>
<P><FONT size=2>All code instances which address the higher level parent will
need to be addressed individually {manually} though<SPAN
class=671150919-10032005> throughout code migration.</SPAN><SPAN
class=671150919-10032005> </SPAN></FONT></P>
<P><FONT size=2><SPAN class=671150919-10032005>Regards </SPAN></FONT><FONT
size=2><SPAN class=671150919-10032005>Glenn Baxter, </SPAN></FONT><FONT
size=2><SPAN class=671150919-10032005>Baxter IT</SPAN><SPAN
class=671150919-10032005><FONT face=Tahoma
color=#0000ff> </FONT></SPAN></FONT></P>
<P><SPAN class=671150919-10032005> </SPAN></P>
<P>
<HR tabIndex=-1>
</P>
<P><FONT face=Tahoma size=2><B>From:</B> Tim Cummings
[mailto:tim.cummings@frequencymarketing.com] <BR><B>Sent:</B> Friday, 11 March
2005 12:35 AM<BR><B>To:</B> PowerHouse List<BR><B>Subject:</B> RE: VMS to
WINDOWS approach ( set lang SQL - gen database...) ?<BR></FONT><BR></P></DIV>
<DIV></DIV>
<P><FONT size=2>I was just surprised that the set lang sql did not generate the
lowest level items. </FONT></P>
<P><FONT size=2>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=2>Timothy J Cummings</FONT> <BR><FONT size=2>Ridgewood Corporate
Center</FONT> <BR><FONT size=2>1000 Summit Drive, Suite 200</FONT> <BR><FONT
size=2>Milford, Ohio 45150</FONT> <BR><FONT
size=2>tim.cummings@frequencymarketing.com</FONT> </P><BR>
<P><FONT size=2>-----Original Message-----</FONT> <BR><FONT size=2>From: Robert
Edis [<A
href="mailto:robeconsult@sbcglobal.net">mailto:robeconsult@sbcglobal.net</A>]</FONT>
<BR><FONT size=2>Sent: Wednesday, March 09, 2005 7:32 PM</FONT> <BR><FONT
size=2>To: PowerHouse List</FONT> <BR><FONT size=2>Subject: RE: VMS to WINDOWS
approach ( set lang SQL - gen database...) ?</FONT> </P><BR>
<P><FONT size=2>Tim</FONT> </P>
<P><FONT size=2>In general RDBMS's do not support nested columns or</FONT>
<BR><FONT size=2>arrays in tables. As you are generating SQL script
I</FONT> <BR><FONT size=2>assume it will be applied to a RDBMS and
therefore</FONT> <BR><FONT size=2>non-compliant schema constructs such as nested
columns</FONT> <BR><FONT size=2>will not be output.</FONT> </P>
<P><FONT size=2>Blue</FONT> </P>
<P><FONT size=2>--- Tim Cummings
<tim.cummings@frequencymarketing.com></FONT> <BR><FONT
size=2>wrote:</FONT> </P>
<P><FONT size=2>> I tried this on MPE and the only bad thing about it</FONT>
<BR><FONT size=2>> is if you have a column</FONT> <BR><FONT size=2>> that
is re-defined, it only creates the higher level</FONT> <BR><FONT size=2>>
item.</FONT> <BR><FONT size=2>> </FONT><BR><FONT size=2>> Is there an
option to get it to create columns for</FONT> <BR><FONT size=2>> the lower
level items?</FONT> <BR><FONT size=2>> </FONT><BR><FONT size=2>>
</FONT><BR><FONT size=2>> Timothy J Cummings</FONT> <BR><FONT size=2>>
Ridgewood Corporate Center</FONT> <BR><FONT size=2>> 1000 Summit Drive, Suite
200</FONT> <BR><FONT size=2>> Milford, Ohio 45150</FONT> <BR><FONT
size=2>> tim.cummings@frequencymarketing.com</FONT> <BR><FONT size=2>>
</FONT><BR><FONT size=2>> </FONT><BR><FONT size=2>> -----Original
Message-----</FONT> <BR><FONT size=2>> From: Joe Boyle [<A
href="mailto:atla38@dsl.pipex.com">mailto:atla38@dsl.pipex.com</A>]</FONT>
<BR><FONT size=2>> Sent: Wednesday, March 09, 2005 2:33 PM</FONT> <BR><FONT
size=2>> To: powerh-l@lists.sowder.com</FONT> <BR><FONT size=2>> Subject:
RE: VMS to WINDOWS approach ( set lang SQL</FONT> <BR><FONT size=2>> - gen
database...) ?</FONT> <BR><FONT size=2>> </FONT><BR><FONT size=2>>
</FONT><BR><FONT size=2>> I have been asked if this approach ( set lang SQL
-</FONT> <BR><FONT size=2>> gen database...) should</FONT> <BR><FONT
size=2>> work on PH7 on VMS; I then remembered that BobD told</FONT>
<BR><FONT size=2>> the list that he tested</FONT> <BR><FONT size=2>> this
and his words are pasted below -</FONT> <BR><FONT size=2>> </FONT><BR><FONT
size=2>> Well, this doesn't happen every day. This is a new</FONT> <BR><FONT
size=2>> one on me as well.</FONT> <BR><FONT size=2>> I've tried it in
8.40D on OpenVMS and 8.41D on</FONT> <BR><FONT size=2>> Windows. I'll make a
bold</FONT> <BR><FONT size=2>> assumption that UNIX works like Windows. On
OpenVMS,</FONT> <BR><FONT size=2>> the file created is</FONT> <BR><FONT
size=2>> named QSHOSQL.TXT. On UNIX and Windows the file is</FONT> <BR><FONT
size=2>> named qshogen.sql.</FONT> <BR><FONT size=2>> The general syntax
is...</FONT> <BR><FONT size=2>> </FONT><BR><FONT size=2>> And if anyone
cares, QSHOW on MPE/iX does the same,</FONT> <BR><FONT size=2>> generating a
file named</FONT> <BR><FONT size=2>> QSHOSQL. And yes, it generates a table
for each</FONT> <BR><FONT size=2>> dataset in an IMAGE</FONT> <BR><FONT
size=2>> database.</FONT> <BR><FONT size=2>> </FONT><BR><FONT size=2>>
Regards, Joe.</FONT> <BR><FONT size=2>> </FONT><BR><FONT size=2>>
</FONT><BR><FONT size=2>> -----Original Message-----</FONT> <BR><FONT
size=2>> From: powerh-l-admin@lists.sowder.com</FONT> <BR><FONT size=2>>
[<A
href="mailto:powerh-l-admin@lists.sowder.com">mailto:powerh-l-admin@lists.sowder.com</A>]
On Behalf</FONT> <BR><FONT size=2>> Of Deskin, Bob</FONT> <BR><FONT
size=2>> Sent: 09 March 2005 15:33</FONT> <BR><FONT size=2>> To:
powerh-l@lists.sowder.com</FONT> <BR><FONT size=2>> Subject: RE: Anyone have
Moved from VMS to WINDOWS?</FONT> <BR><FONT size=2>> </FONT><BR><FONT
size=2>> Our recommendation when migrating from IMAGE/indexed</FONT>
<BR><FONT size=2>> to relational is to</FONT> <BR><FONT size=2>> use
Axiant. However, there is an undocumented</FONT> <BR><FONT size=2>> feature
(no I don't know</FONT> <BR><FONT size=2>> why it's undocumented) of QSHOW
that will let you</FONT> <BR><FONT size=2>> generate a skeleton</FONT>
<BR><FONT size=2>> SQL table definition.</FONT> <BR><FONT size=2>>
</FONT><BR><FONT size=2>> In QSHOW:</FONT> <BR><FONT size=2>>
</FONT><BR><FONT size=2>> SET LANG SQL</FONT> <BR><FONT size=2>> GENERATE
DATABASE <indexed-file></FONT> <BR><FONT size=2>> </FONT><BR><FONT
size=2>> Yes, I know it's a FILE and not a DATABASE, but you</FONT> <BR><FONT
size=2>> have to fool QSHOW</FONT> <BR><FONT size=2>> into thinking it's
dealing with relational.</FONT> <BR><FONT size=2>> </FONT><BR><FONT
size=2>> On Windows, this create a file named qshogen.sql</FONT> <BR><FONT
size=2>> with the basic table</FONT> <BR><FONT size=2>> definition. If you
generate all your files this way</FONT> <BR><FONT size=2>> and put the
results</FONT> <BR><FONT size=2>> together, and add the constraints and so
on, you can</FONT> <BR><FONT size=2>> come up with a</FONT> <BR><FONT
size=2>> fairly complete database schema. It's not as good as</FONT>
<BR><FONT size=2>> Axiant but it's a</FONT> <BR><FONT size=2>>
start.</FONT> <BR><FONT size=2>> </FONT><BR><FONT size=2>> Bob</FONT>
<BR><FONT size=2>> </FONT><BR><FONT size=2>> -----Original
Message-----</FONT> <BR><FONT size=2>> From:
powerh-l-admin@lists.sowder.com</FONT> <BR><FONT size=2>> [<A
href="mailto:powerh-l-admin@lists.sowder.com">mailto:powerh-l-admin@lists.sowder.com</A>]
On Behalf</FONT> <BR><FONT size=2>> Of Ken Langendock</FONT> <BR><FONT
size=2>> Sent: March 9, 2005 10:18 AM</FONT> <BR><FONT size=2>> To:
powerh-l@lists.sowder.com</FONT> <BR><FONT size=2>> Subject: Re: Anyone have
Moved from VMS to WINDOWS?</FONT> <BR><FONT size=2>> </FONT><BR><FONT
size=2>> </FONT><BR><FONT size=2>> I know there have been many
conversations flying</FONT> <BR><FONT size=2>> back</FONT> <BR><FONT
size=2>> and forth about how to convert from ISAM/KSAM/RMS to</FONT>
<BR><FONT size=2>> a database. And</FONT> <BR><FONT size=2>> unless I
didn't see the actually "final" message.</FONT> <BR><FONT size=2>> There
wasn't a nice</FONT> <BR><FONT size=2>> way of doing this unless you are
going Axiant.</FONT> <BR><FONT size=2>> </FONT><BR><FONT size=2>> Mom
always told me to never touched the stuff.</FONT> <BR><FONT size=2>>
</FONT><BR><FONT size=2>> When I converted from ISAM (or all of the above)
I</FONT> <BR><FONT size=2>> exported my file definitions in QSHOW to
PDL.</FONT> <BR><FONT size=2>> </FONT><BR><FONT size=2>> Then I started my
Search and Replace routine. </FONT><BR><FONT size=2>> 1) change all the - to
_</FONT> <BR><FONT size=2>> 2) change all file names to sql sytax
"create..."</FONT> <BR><FONT size=2>> 3) changed all item statements to sql
syntax.</FONT> <BR><FONT size=2>> 4) etc.</FONT> <BR><FONT size=2>>
5)....test/retest.</FONT> <BR><FONT size=2>> </FONT><BR><FONT size=2>>
Ken</FONT> <BR><FONT size=2>> </FONT><BR><FONT size=2>> </FONT><BR><FONT
size=2>> --- Othman <othman2@gmail.com> wrote: </FONT><BR><FONT
size=2>> > how about the database migration.</FONT> <BR><FONT size=2>>
> </FONT><BR><FONT size=2>> > our system running with the following
environment </FONT><BR><FONT size=2>> > -System: HP
3000/968 Rx</FONT> <BR><FONT size=2>> > -OS : MPE / ix HP 31900</FONT>
<BR><FONT size=2>> > </FONT><BR><FONT size=2>> >
-Reporting Quiz - Cognos PowerHouse 8.19.C4</FONT> <BR><FONT size=2>>
version.</FONT> <BR><FONT size=2>> > </FONT><BR><FONT
size=2>> > -Screen Designing QDESIGN - Cognos
PowerHouse</FONT> <BR><FONT size=2>> > 8.19.C4 version.</FONT> <BR><FONT
size=2>> > </FONT><BR><FONT size=2>> >
-Transaction Processing QTP - Cognos PowerHouse</FONT>
<BR><FONT size=2>> > 8.19.C4 version.</FONT> <BR><FONT size=2>> >
</FONT><BR><FONT size=2>> > -Data Base
Dictionary PDL - Cognos PowerHouse</FONT>
<BR><FONT size=2>> > 8.19.C4 version.</FONT> <BR><FONT size=2>> >
</FONT><BR><FONT size=2>> > what is the recommended path to migrate to NT
,MS</FONT> <BR><FONT size=2>> > SQL</FONT> <BR><FONT size=2>> >
</FONT><BR><FONT size=2>> > On Wed, 9 Mar 2005 09:44:56 -0500 (EST),
Ken</FONT> <BR><FONT size=2>> > Langendock</FONT> <BR><FONT size=2>>
> <ken.langendock@rogers.com> wrote:</FONT> <BR><FONT size=2>> >
> I'm not sure what you mean by tool.</FONT> <BR><FONT size=2>> > >
</FONT><BR><FONT size=2>> > > I used a free ware search and replace
tool that</FONT> <BR><FONT size=2>> I downloaded from </FONT><BR><FONT
size=2>> > > the net to fix the source.</FONT> <BR><FONT size=2>>
> > </FONT><BR><FONT size=2>> > > The last conversion was from DG
ISAM to ISAM for</FONT> <BR><FONT size=2>> > NT.</FONT> <BR><FONT
size=2>> > > So all I did there was export the file</FONT> <BR><FONT
size=2>> definitions</FONT> <BR><FONT size=2>> > > from QSHOW on the
UNIX box and cleaned them up</FONT> <BR><FONT size=2>> for</FONT> <BR><FONT
size=2>> > NT.</FONT> <BR><FONT size=2>> > > </FONT><BR><FONT
size=2>> > > Most of the time I convert everything by search</FONT>
<BR><FONT size=2>> > and</FONT> <BR><FONT size=2>> > > replace
then do the rest by hand.</FONT> <BR><FONT size=2>> > >
</FONT><BR><FONT size=2>> > > By using my application as a building
block. I</FONT> <BR><FONT size=2>> > > converted a 100 program
application within 2</FONT> <BR><FONT size=2>> weeks</FONT> <BR><FONT
size=2>> > > (working at night). And that app was written</FONT>
<BR><FONT size=2>> back</FONT> <BR><FONT size=2>> > in</FONT> <BR><FONT
size=2>> > > the early 80's, it was all crap code.</FONT> <BR><FONT
size=2>> > > </FONT><BR><FONT size=2>> > > Ken</FONT>
<BR><FONT size=2>> > > </FONT><BR><FONT size=2>> > > ---
Othman <othman2@gmail.com> wrote:</FONT> <BR><FONT size=2>> > >
> what tool did you use for migration</FONT> <BR><FONT size=2>> > >
></FONT> <BR><FONT size=2>> > > ></FONT> <BR><FONT size=2>>
> > > On Wed, 9 Mar 2005 08:50:58 -0500 (EST), Ken</FONT> <BR><FONT
size=2>> > > > Langendock</FONT> <BR><FONT size=2>> > >
> <ken.langendock@rogers.com> wrote:</FONT> <BR><FONT size=2>> >
> > > I have converted an application from many</FONT> <BR><FONT
size=2>> > machines</FONT> <BR><FONT size=2>> > > > to</FONT>
<BR><FONT size=2>> > > > > other lines.</FONT> <BR><FONT
size=2>> > > > ></FONT> <BR><FONT size=2>> > > > >
I started out on the VAX (in my opinion the</FONT> <BR><FONT size=2>> >
best</FONT> <BR><FONT size=2>> > > > > machine still to this
day), then to HP3000,</FONT> <BR><FONT size=2>> > then</FONT> <BR><FONT
size=2>> > > > UNIX</FONT> <BR><FONT size=2>> > > > >
(HP, SUN, IBM, DG, etc) then to Powerhouse</FONT> <BR><FONT size=2>>
NT.</FONT> <BR><FONT size=2>> > > > ></FONT> <BR><FONT
size=2>> > > > > I created a system management module that</FONT>
<BR><FONT size=2>> > takes</FONT> <BR><FONT size=2>> > > > all
of</FONT> <BR><FONT size=2>> > > > > the O/S level code away from
your</FONT> <BR><FONT size=2>> application.</FONT> <BR><FONT size=2>> >
> > This</FONT> <BR><FONT size=2>> > > > > allows me to
convert from one platform to</FONT> <BR><FONT size=2>> > another</FONT>
<BR><FONT size=2>> > > > > transparently to the
User/Application.</FONT> <BR><FONT size=2>> > > > ></FONT>
<BR><FONT size=2>> </FONT><BR><FONT size=2>=== message truncated ===</FONT>
</P>
<P><FONT size=2>= = = = = = = = = = = = = = = = = = = = = = = = = = = =</FONT>
<BR><FONT size=2>Mailing list: powerh-l@lists.sowder.com</FONT> <BR><FONT
size=2>Subscribe: "subscribe" in message body to
powerh-l-request@lists.sowder.com</FONT> <BR><FONT size=2>Unsubscribe:
"unsubscribe <password>" in message body to
powerh-l-request@lists.sowder.com</FONT> <BR><FONT size=2><A
href="http://lists.sowder.com/mailman/listinfo/powerh-l"
target=_blank>http://lists.sowder.com/mailman/listinfo/powerh-l</A></FONT>
<BR><FONT size=2>This list is closed, thus to post to the list you must be a
subscriber.</FONT> </P></BODY></HTML>
------_=_NextPart_001_01C525A4.5AED90F0--