VMS to WINDOWS approach ( set lang SQL - gen database...) ?
Whittall, Conrad
Conrad.Whittall@Cognos.COM
Thu, 10 Mar 2005 10:24:21 -0500
This is a multi-part message in MIME format.
------_=_NextPart_001_01C52584.CD5D0B1A
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
And if QSHOW did use the lowest level substructured item then of course
it would have to figure out what to do when the higher level item was
redefined and substructured a different way.
=20
Believe me, I have seen more than just one application do this in the PH
dictionary over the years...for example with dates, where the physical
item is stored as ZONED so that each segment -- year, month, and day can
be substructured as numbers -- but then the whole date is redefined as
CHARACTER and the year, month, and day substructured again so that they
can now be easily referenced as character items to be included in
messages and text labels.
=20
Each and every situation is going to be different, even within the same
dictionary, and so that is why it is probably impossible to have QSHOW
make these types of application design decisions.
=20
Just my 2-cents worth...
Conrad=20
________________________________
From: powerh-l-admin@lists.sowder.com
[mailto:powerh-l-admin@lists.sowder.com] On Behalf Of Deskin, Bob
Sent: Thursday 10 March 2005 08:55
To: PowerHouse List
Subject: RE: VMS to WINDOWS approach ( set lang SQL - gen database...) ?
I suspect that this "feature" was not planned for non-relational. Note
that you have to "fool" QSHOW by using GENERATE DATABASE even though the
target is a file (even IMAGE). I will look into exactly how it works and
how it should work. For example, I agree that generally a substructured
item should have the lowest level items generated. However, what happens
if there's a substructured index segment. In this case, I would think
that the segment as a whole would have to be generated because otherwise
you couldn't generate the index properly.
=20
Bob
-----Original Message-----
From: powerh-l-admin@lists.sowder.com
[mailto:powerh-l-admin@lists.sowder.com] On Behalf Of Tim Cummings
Sent: March 10, 2005 8:35 AM
To: PowerHouse List
Subject: RE: VMS to WINDOWS approach ( set lang SQL - gen
database...) ?
=09
=09
I was just surprised that the set lang sql did not generate the
lowest level items. =20
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=20
Ridgewood Corporate Center=20
1000 Summit Drive, Suite 200=20
Milford, Ohio 45150=20
tim.cummings@frequencymarketing.com=20
-----Original Message-----=20
From: Robert Edis [mailto:robeconsult@sbcglobal.net]=20
Sent: Wednesday, March 09, 2005 7:32 PM=20
To: PowerHouse List=20
Subject: RE: VMS to WINDOWS approach ( set lang SQL - gen
database...) ?=20
Tim=20
In general RDBMS's do not support nested columns or=20
arrays in tables. As you are generating SQL script I=20
assume it will be applied to a RDBMS and therefore=20
non-compliant schema constructs such as nested columns=20
will not be output.=20
Blue=20
--- Tim Cummings <tim.cummings@frequencymarketing.com>=20
wrote:=20
> I tried this on MPE and the only bad thing about it=20
> is if you have a column=20
> that is re-defined, it only creates the higher level=20
> item.=20
>=20
> Is there an option to get it to create columns for=20
> the lower level items?=20
>=20
>=20
> Timothy J Cummings=20
> Ridgewood Corporate Center=20
> 1000 Summit Drive, Suite 200=20
> Milford, Ohio 45150=20
> tim.cummings@frequencymarketing.com=20
>=20
>=20
> -----Original Message-----=20
> From: Joe Boyle [mailto:atla38@dsl.pipex.com]=20
> Sent: Wednesday, March 09, 2005 2:33 PM=20
> To: powerh-l@lists.sowder.com=20
> Subject: RE: VMS to WINDOWS approach ( set lang SQL=20
> - gen database...) ?=20
>=20
>=20
> I have been asked if this approach ( set lang SQL -=20
> gen database...) should=20
> work on PH7 on VMS; I then remembered that BobD told=20
> the list that he tested=20
> this and his words are pasted below -=20
>=20
> Well, this doesn't happen every day. This is a new=20
> one on me as well.=20
> I've tried it in 8.40D on OpenVMS and 8.41D on=20
> Windows. I'll make a bold=20
> assumption that UNIX works like Windows. On OpenVMS,=20
> the file created is=20
> named QSHOSQL.TXT. On UNIX and Windows the file is=20
> named qshogen.sql.=20
> The general syntax is...=20
>=20
> And if anyone cares, QSHOW on MPE/iX does the same,=20
> generating a file named=20
> QSHOSQL. And yes, it generates a table for each=20
> dataset in an IMAGE=20
> database.=20
>=20
> Regards, Joe.=20
>=20
>=20
> -----Original Message-----=20
> From: powerh-l-admin@lists.sowder.com=20
> [mailto:powerh-l-admin@lists.sowder.com] On Behalf=20
> Of Deskin, Bob=20
> Sent: 09 March 2005 15:33=20
> To: powerh-l@lists.sowder.com=20
> Subject: RE: Anyone have Moved from VMS to WINDOWS?=20
>=20
> Our recommendation when migrating from IMAGE/indexed=20
> to relational is to=20
> use Axiant. However, there is an undocumented=20
> feature (no I don't know=20
> why it's undocumented) of QSHOW that will let you=20
> generate a skeleton=20
> SQL table definition.=20
>=20
> In QSHOW:=20
>=20
> SET LANG SQL=20
> GENERATE DATABASE <indexed-file>=20
>=20
> Yes, I know it's a FILE and not a DATABASE, but you=20
> have to fool QSHOW=20
> into thinking it's dealing with relational.=20
>=20
> On Windows, this create a file named qshogen.sql=20
> with the basic table=20
> definition. If you generate all your files this way=20
> and put the results=20
> together, and add the constraints and so on, you can=20
> come up with a=20
> fairly complete database schema. It's not as good as=20
> Axiant but it's a=20
> start.=20
>=20
> Bob=20
>=20
> -----Original Message-----=20
> From: powerh-l-admin@lists.sowder.com=20
> [mailto:powerh-l-admin@lists.sowder.com] On Behalf=20
> Of Ken Langendock=20
> Sent: March 9, 2005 10:18 AM=20
> To: powerh-l@lists.sowder.com=20
> Subject: Re: Anyone have Moved from VMS to WINDOWS?=20
>=20
>=20
> I know there have been many conversations flying=20
> back=20
> and forth about how to convert from ISAM/KSAM/RMS to=20
> a database. And=20
> unless I didn't see the actually "final" message.=20
> There wasn't a nice=20
> way of doing this unless you are going Axiant.=20
>=20
> Mom always told me to never touched the stuff.=20
>=20
> When I converted from ISAM (or all of the above) I=20
> exported my file definitions in QSHOW to PDL.=20
>=20
> Then I started my Search and Replace routine.=20
> 1) change all the - to _=20
> 2) change all file names to sql sytax "create..."=20
> 3) changed all item statements to sql syntax.=20
> 4) etc.=20
> 5)....test/retest.=20
>=20
> Ken=20
>=20
>=20
> --- Othman <othman2@gmail.com> wrote:=20
> > how about the database migration.=20
> >=20
> > our system running with the following environment=20
> > -System: HP 3000/968 Rx=20
> > -OS : MPE / ix HP 31900=20
> > =20
> > -Reporting Quiz - Cognos PowerHouse 8.19.C4=20
> version.=20
> > =20
> > -Screen Designing QDESIGN - Cognos PowerHouse=20
> > 8.19.C4 version.=20
> > =20
> > -Transaction Processing QTP - Cognos PowerHouse=20
> > 8.19.C4 version.=20
> > =20
> > -Data Base Dictionary PDL - Cognos PowerHouse=20
> > 8.19.C4 version.=20
> >=20
> > what is the recommended path to migrate to NT ,MS=20
> > SQL=20
> >=20
> > On Wed, 9 Mar 2005 09:44:56 -0500 (EST), Ken=20
> > Langendock=20
> > <ken.langendock@rogers.com> wrote:=20
> > > I'm not sure what you mean by tool.=20
> > >=20
> > > I used a free ware search and replace tool that=20
> I downloaded from=20
> > > the net to fix the source.=20
> > >=20
> > > The last conversion was from DG ISAM to ISAM for=20
> > NT.=20
> > > So all I did there was export the file=20
> definitions=20
> > > from QSHOW on the UNIX box and cleaned them up=20
> for=20
> > NT.=20
> > >=20
> > > Most of the time I convert everything by search=20
> > and=20
> > > replace then do the rest by hand.=20
> > >=20
> > > By using my application as a building block. I=20
> > > converted a 100 program application within 2=20
> weeks=20
> > > (working at night). And that app was written=20
> back=20
> > in=20
> > > the early 80's, it was all crap code.=20
> > >=20
> > > Ken=20
> > >=20
> > > --- Othman <othman2@gmail.com> wrote:=20
> > > > what tool did you use for migration=20
> > > >=20
> > > >=20
> > > > On Wed, 9 Mar 2005 08:50:58 -0500 (EST), Ken=20
> > > > Langendock=20
> > > > <ken.langendock@rogers.com> wrote:=20
> > > > > I have converted an application from many=20
> > machines=20
> > > > to=20
> > > > > other lines.=20
> > > > >=20
> > > > > I started out on the VAX (in my opinion the=20
> > best=20
> > > > > machine still to this day), then to HP3000,=20
> > then=20
> > > > UNIX=20
> > > > > (HP, SUN, IBM, DG, etc) then to Powerhouse=20
> NT.=20
> > > > >=20
> > > > > I created a system management module that=20
> > takes=20
> > > > all of=20
> > > > > the O/S level code away from your=20
> application.=20
> > > > This=20
> > > > > allows me to convert from one platform to=20
> > another=20
> > > > > transparently to the User/Application.=20
> > > > >=20
>=20
=3D=3D=3D message truncated =3D=3D=3D=20
=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=20
Mailing list: powerh-l@lists.sowder.com=20
Subscribe: "subscribe" in message body to
powerh-l-request@lists.sowder.com=20
Unsubscribe: "unsubscribe <password>" in message body to
powerh-l-request@lists.sowder.com=20
http://lists.sowder.com/mailman/listinfo/powerh-l=20
This list is closed, thus to post to the list you must be a
subscriber.=20
=20
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.=20
------_=_NextPart_001_01C52584.CD5D0B1A
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns:eXclaimer =3D=20
"http://www.exclaimer.co.uk"><HEAD><TITLE>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2180" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><FONT face=3DVerdana color=3D#000080 =
size=3D2><SPAN=20
class=3D115481615-10032005>And if QSHOW did use the lowest level =
substructured=20
item then of course it would have to figure out what to do when the =
higher level=20
item was redefined and substructured a different =
way.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DVerdana color=3D#000080 =
size=3D2><SPAN=20
class=3D115481615-10032005></SPAN></FONT> </DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DVerdana color=3D#000080 =
size=3D2><SPAN=20
class=3D115481615-10032005>Believe me, I have seen more than just one =
application=20
do this in the PH dictionary over the years...for example with dates, =
where the=20
physical item is stored as ZONED so that each segment -- year, month, =
and day=20
can be substructured as numbers -- but then the whole date is redefined =
as=20
CHARACTER and the year, month, and day substructured again so that they =
can now=20
be easily referenced as character items to be included in messages and =
text=20
labels.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DVerdana color=3D#000080 =
size=3D2><SPAN=20
class=3D115481615-10032005></SPAN></FONT> </DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DVerdana color=3D#000080 =
size=3D2><SPAN=20
class=3D115481615-10032005>Each and every situation is going to be =
different, even=20
within the same dictionary, and so that is why it is probably impossible =
to have=20
QSHOW make these types of application design =
decisions.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DVerdana color=3D#000080 =
size=3D2><SPAN=20
class=3D115481615-10032005></SPAN></FONT> </DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DVerdana color=3D#000080 =
size=3D2><SPAN=20
class=3D115481615-10032005>Just my 2-cents =
worth...</SPAN></FONT></DIV><!-- Converted from text/rtf format -->
<P><SPAN lang=3Den-us><B><I><FONT face=3D"Times New Roman" =
color=3D#000080=20
size=3D6>Conrad</FONT></I></B><I></I></SPAN> </P><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> =
powerh-l-admin@lists.sowder.com=20
[mailto:powerh-l-admin@lists.sowder.com] <B>On Behalf Of </B>Deskin,=20
Bob<BR><B>Sent:</B> Thursday 10 March 2005 08:55<BR><B>To:</B> =
PowerHouse=20
List<BR><B>Subject:</B> RE: VMS to WINDOWS approach ( set lang SQL - gen =
database...) ?<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D470525313-10032005>I=20
suspect that this "feature" was not planned for non-relational. Note =
that you=20
have to "fool" QSHOW by using GENERATE DATABASE even though the target =
is a file=20
(even IMAGE). I will look into exactly how it works and how it should =
work. For=20
example, I agree that generally a substructured item should have the =
lowest=20
level items generated. However, what happens if there's a substructured =
index=20
segment. In this case, I would think that the segment as a whole would =
have to=20
be generated because otherwise you couldn't generate the index=20
properly.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D470525313-10032005></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D470525313-10032005>Bob</SPAN></FONT></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B>=20
powerh-l-admin@lists.sowder.com =
[mailto:powerh-l-admin@lists.sowder.com] <B>On=20
Behalf Of </B>Tim Cummings<BR><B>Sent:</B> March 10, 2005 8:35=20
AM<BR><B>To:</B> PowerHouse List<BR><B>Subject:</B> RE: VMS to WINDOWS =
approach ( set lang SQL - gen database...) ?<BR><BR></FONT></DIV>
<P><FONT size=3D2>I was just surprised that the set lang sql did not =
generate=20
the lowest level items. </FONT></P>
<P><FONT size=3D2>If I have a column in Image called FLAGS (4 bytes) =
and it is=20
defined in the PH dictionary as redefined by FLAG_A, FLAG-B, FLAG-C, =
FLAG-D=20
(each, one byte). I would have expected it to create the columns =
for=20
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=20
Center</FONT> <BR><FONT size=3D2>1000 Summit Drive, Suite 200</FONT> =
<BR><FONT=20
size=3D2>Milford, Ohio 45150</FONT> <BR><FONT=20
size=3D2>tim.cummings@frequencymarketing.com</FONT> </P><BR>
<P><FONT size=3D2>-----Original Message-----</FONT> <BR><FONT =
size=3D2>From:=20
Robert Edis [<A=20
=
href=3D"mailto:robeconsult@sbcglobal.net">mailto:robeconsult@sbcglobal.ne=
t</A>]</FONT>=20
<BR><FONT size=3D2>Sent: Wednesday, March 09, 2005 7:32 PM</FONT> =
<BR><FONT=20
size=3D2>To: PowerHouse List</FONT> <BR><FONT size=3D2>Subject: RE: =
VMS to WINDOWS=20
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>=20
<BR><FONT size=3D2>arrays in tables. As you are generating SQL =
script=20
I</FONT> <BR><FONT size=3D2>assume it will be applied to a RDBMS and=20
therefore</FONT> <BR><FONT size=3D2>non-compliant schema constructs =
such as=20
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=20
<tim.cummings@frequencymarketing.com></FONT> <BR><FONT=20
size=3D2>wrote:</FONT> </P>
<P><FONT size=3D2>> I tried this on MPE and the only bad thing =
about=20
it</FONT> <BR><FONT size=3D2>> is if you have a column</FONT> =
<BR><FONT=20
size=3D2>> that is re-defined, it only creates the higher =
level</FONT>=20
<BR><FONT size=3D2>> item.</FONT> <BR><FONT size=3D2>> =
</FONT><BR><FONT=20
size=3D2>> Is there an option to get it to create columns =
for</FONT>=20
<BR><FONT size=3D2>> the lower level items?</FONT> <BR><FONT =
size=3D2>>=20
</FONT><BR><FONT size=3D2>> </FONT><BR><FONT size=3D2>> Timothy =
J=20
Cummings</FONT> <BR><FONT size=3D2>> Ridgewood Corporate =
Center</FONT>=20
<BR><FONT size=3D2>> 1000 Summit Drive, Suite 200</FONT> <BR><FONT=20
size=3D2>> Milford, Ohio 45150</FONT> <BR><FONT size=3D2>> =
tim.cummings@frequencymarketing.com</FONT> <BR><FONT size=3D2>>=20
</FONT><BR><FONT size=3D2>> </FONT><BR><FONT size=3D2>> =
-----Original=20
Message-----</FONT> <BR><FONT size=3D2>> From: Joe Boyle [<A=20
=
href=3D"mailto:atla38@dsl.pipex.com">mailto:atla38@dsl.pipex.com</A>]</FO=
NT>=20
<BR><FONT size=3D2>> Sent: Wednesday, March 09, 2005 2:33 PM</FONT> =
<BR><FONT=20
size=3D2>> To: powerh-l@lists.sowder.com</FONT> <BR><FONT =
size=3D2>>=20
Subject: RE: VMS to WINDOWS approach ( set lang SQL</FONT> <BR><FONT=20
size=3D2>> - gen database...) ?</FONT> <BR><FONT size=3D2>> =
</FONT><BR><FONT=20
size=3D2>> </FONT><BR><FONT size=3D2>> I have been asked if this =
approach (=20
set lang SQL -</FONT> <BR><FONT size=3D2>> gen database...) =
should</FONT>=20
<BR><FONT size=3D2>> work on PH7 on VMS; I then remembered that =
BobD=20
told</FONT> <BR><FONT size=3D2>> the list that he tested</FONT> =
<BR><FONT=20
size=3D2>> this and his words are pasted below -</FONT> <BR><FONT =
size=3D2>>=20
</FONT><BR><FONT size=3D2>> Well, this doesn't happen every day. =
This is a=20
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=20
size=3D2>> Windows. I'll make a bold</FONT> <BR><FONT size=3D2>> =
assumption=20
that UNIX works like Windows. On OpenVMS,</FONT> <BR><FONT =
size=3D2>> the=20
file created is</FONT> <BR><FONT size=3D2>> named QSHOSQL.TXT. On =
UNIX and=20
Windows the file is</FONT> <BR><FONT size=3D2>> named =
qshogen.sql.</FONT>=20
<BR><FONT size=3D2>> The general syntax is...</FONT> <BR><FONT =
size=3D2>>=20
</FONT><BR><FONT size=3D2>> And if anyone cares, QSHOW on MPE/iX =
does the=20
same,</FONT> <BR><FONT size=3D2>> generating a file named</FONT> =
<BR><FONT=20
size=3D2>> QSHOSQL. And yes, it generates a table for each</FONT> =
<BR><FONT=20
size=3D2>> dataset in an IMAGE</FONT> <BR><FONT size=3D2>> =
database.</FONT>=20
<BR><FONT size=3D2>> </FONT><BR><FONT size=3D2>> Regards, =
Joe.</FONT>=20
<BR><FONT size=3D2>> </FONT><BR><FONT size=3D2>> =
</FONT><BR><FONT=20
size=3D2>> -----Original Message-----</FONT> <BR><FONT =
size=3D2>> From:=20
powerh-l-admin@lists.sowder.com</FONT> <BR><FONT size=3D2>> [<A=20
=
href=3D"mailto:powerh-l-admin@lists.sowder.com">mailto:powerh-l-admin@lis=
ts.sowder.com</A>]=20
On Behalf</FONT> <BR><FONT size=3D2>> Of Deskin, Bob</FONT> =
<BR><FONT=20
size=3D2>> Sent: 09 March 2005 15:33</FONT> <BR><FONT size=3D2>> =
To:=20
powerh-l@lists.sowder.com</FONT> <BR><FONT size=3D2>> Subject: RE: =
Anyone=20
have Moved from VMS to WINDOWS?</FONT> <BR><FONT size=3D2>> =
</FONT><BR><FONT=20
size=3D2>> Our recommendation when migrating from =
IMAGE/indexed</FONT>=20
<BR><FONT size=3D2>> to relational is to</FONT> <BR><FONT =
size=3D2>> use=20
Axiant. However, there is an undocumented</FONT> <BR><FONT =
size=3D2>> feature=20
(no I don't know</FONT> <BR><FONT size=3D2>> why it's undocumented) =
of QSHOW=20
that will let you</FONT> <BR><FONT size=3D2>> generate a =
skeleton</FONT>=20
<BR><FONT size=3D2>> SQL table definition.</FONT> <BR><FONT =
size=3D2>>=20
</FONT><BR><FONT size=3D2>> In QSHOW:</FONT> <BR><FONT =
size=3D2>>=20
</FONT><BR><FONT size=3D2>> SET LANG SQL</FONT> <BR><FONT =
size=3D2>>=20
GENERATE DATABASE <indexed-file></FONT> <BR><FONT size=3D2>>=20
</FONT><BR><FONT size=3D2>> Yes, I know it's a FILE and not a =
DATABASE, but=20
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=20
size=3D2>> </FONT><BR><FONT size=3D2>> On Windows, this create a =
file named=20
qshogen.sql</FONT> <BR><FONT size=3D2>> with the basic table</FONT> =
<BR><FONT=20
size=3D2>> definition. If you generate all your files this =
way</FONT>=20
<BR><FONT size=3D2>> and put the results</FONT> <BR><FONT =
size=3D2>>=20
together, and add the constraints and so on, you can</FONT> <BR><FONT=20
size=3D2>> come up with a</FONT> <BR><FONT size=3D2>> fairly =
complete=20
database schema. It's not as good as</FONT> <BR><FONT size=3D2>> =
Axiant but=20
it's a</FONT> <BR><FONT size=3D2>> start.</FONT> <BR><FONT =
size=3D2>>=20
</FONT><BR><FONT size=3D2>> Bob</FONT> <BR><FONT size=3D2>> =
</FONT><BR><FONT=20
size=3D2>> -----Original Message-----</FONT> <BR><FONT =
size=3D2>> From:=20
powerh-l-admin@lists.sowder.com</FONT> <BR><FONT size=3D2>> [<A=20
=
href=3D"mailto:powerh-l-admin@lists.sowder.com">mailto:powerh-l-admin@lis=
ts.sowder.com</A>]=20
On Behalf</FONT> <BR><FONT size=3D2>> Of Ken Langendock</FONT> =
<BR><FONT=20
size=3D2>> Sent: March 9, 2005 10:18 AM</FONT> <BR><FONT =
size=3D2>> To:=20
powerh-l@lists.sowder.com</FONT> <BR><FONT size=3D2>> Subject: Re: =
Anyone=20
have Moved from VMS to WINDOWS?</FONT> <BR><FONT size=3D2>> =
</FONT><BR><FONT=20
size=3D2>> </FONT><BR><FONT size=3D2>> I know there have been =
many=20
conversations flying</FONT> <BR><FONT size=3D2>> back</FONT> =
<BR><FONT=20
size=3D2>> and forth about how to convert from ISAM/KSAM/RMS =
to</FONT>=20
<BR><FONT size=3D2>> a database. And</FONT> <BR><FONT size=3D2>> =
unless I=20
didn't see the actually "final" message.</FONT> <BR><FONT =
size=3D2>> There=20
wasn't a nice</FONT> <BR><FONT size=3D2>> way of doing this unless =
you are=20
going Axiant.</FONT> <BR><FONT size=3D2>> </FONT><BR><FONT =
size=3D2>> Mom=20
always told me to never touched the stuff.</FONT> <BR><FONT =
size=3D2>>=20
</FONT><BR><FONT size=3D2>> When I converted from ISAM (or all of =
the above)=20
I</FONT> <BR><FONT size=3D2>> exported my file definitions in QSHOW =
to=20
PDL.</FONT> <BR><FONT size=3D2>> </FONT><BR><FONT size=3D2>> =
Then I started=20
my Search and Replace routine. </FONT><BR><FONT size=3D2>> 1) =
change all the=20
- to _</FONT> <BR><FONT size=3D2>> 2) change all file names to sql =
sytax=20
"create..."</FONT> <BR><FONT size=3D2>> 3) changed all item =
statements to sql=20
syntax.</FONT> <BR><FONT size=3D2>> 4) etc.</FONT> <BR><FONT =
size=3D2>>=20
5)....test/retest.</FONT> <BR><FONT size=3D2>> </FONT><BR><FONT =
size=3D2>>=20
Ken</FONT> <BR><FONT size=3D2>> </FONT><BR><FONT size=3D2>> =
</FONT><BR><FONT=20
size=3D2>> --- Othman <othman2@gmail.com> wrote: =
</FONT><BR><FONT=20
size=3D2>> > how about the database migration.</FONT> <BR><FONT=20
size=3D2>> > </FONT><BR><FONT size=3D2>> > our system =
running with the=20
following environment </FONT><BR><FONT size=3D2>> >=20
-System: HP 3000/968 Rx</FONT> <BR><FONT =
size=3D2>> >=20
-OS : MPE / ix HP 31900</FONT> <BR><FONT size=3D2>> > =
=20
</FONT><BR><FONT size=3D2>> > -Reporting Quiz - Cognos =
PowerHouse=20
8.19.C4</FONT> <BR><FONT size=3D2>> version.</FONT> <BR><FONT =
size=3D2>>=20
> </FONT><BR><FONT size=3D2>> > -Screen=20
Designing QDESIGN - Cognos PowerHouse</FONT> <BR><FONT =
size=3D2>>=20
> 8.19.C4 version.</FONT> <BR><FONT size=3D2>> > =
=20
</FONT><BR><FONT size=3D2>> > -Transaction=20
Processing QTP - Cognos PowerHouse</FONT> =
<BR><FONT=20
size=3D2>> > 8.19.C4 version.</FONT> <BR><FONT size=3D2>> =
>=20
</FONT><BR><FONT size=3D2>> > -Data Base=20
Dictionary PDL - Cognos =
PowerHouse</FONT>=20
<BR><FONT size=3D2>> > 8.19.C4 version.</FONT> <BR><FONT =
size=3D2>> >=20
</FONT><BR><FONT size=3D2>> > what is the recommended path to =
migrate to=20
NT ,MS</FONT> <BR><FONT size=3D2>> > SQL</FONT> <BR><FONT =
size=3D2>> >=20
</FONT><BR><FONT size=3D2>> > On Wed, 9 Mar 2005 09:44:56 -0500 =
(EST),=20
Ken</FONT> <BR><FONT size=3D2>> > Langendock</FONT> <BR><FONT =
size=3D2>>=20
> <ken.langendock@rogers.com> wrote:</FONT> <BR><FONT =
size=3D2>>=20
> > I'm not sure what you mean by tool.</FONT> <BR><FONT =
size=3D2>>=20
> > </FONT><BR><FONT size=3D2>> > > I used a free ware =
search and=20
replace tool that</FONT> <BR><FONT size=3D2>> I downloaded from=20
</FONT><BR><FONT size=3D2>> > > the net to fix the =
source.</FONT>=20
<BR><FONT size=3D2>> > > </FONT><BR><FONT size=3D2>> > =
> The=20
last conversion was from DG ISAM to ISAM for</FONT> <BR><FONT =
size=3D2>> >=20
NT.</FONT> <BR><FONT size=3D2>> > > So all I did there was =
export the=20
file</FONT> <BR><FONT size=3D2>> definitions</FONT> <BR><FONT =
size=3D2>>=20
> > from QSHOW on the UNIX box and cleaned them up</FONT> =
<BR><FONT=20
size=3D2>> for</FONT> <BR><FONT size=3D2>> > NT.</FONT> =
<BR><FONT=20
size=3D2>> > > </FONT><BR><FONT size=3D2>> > > Most =
of the time=20
I convert everything by search</FONT> <BR><FONT size=3D2>> > =
and</FONT>=20
<BR><FONT size=3D2>> > > replace then do the rest by =
hand.</FONT>=20
<BR><FONT size=3D2>> > > </FONT><BR><FONT size=3D2>> > =
> By=20
using my application as a building block. I</FONT> <BR><FONT =
size=3D2>> >=20
> converted a 100 program application within 2</FONT> <BR><FONT =
size=3D2>>=20
weeks</FONT> <BR><FONT size=3D2>> > > (working at night). And =
that app=20
was written</FONT> <BR><FONT size=3D2>> back</FONT> <BR><FONT =
size=3D2>>=20
> in</FONT> <BR><FONT size=3D2>> > > the early 80's, it =
was all crap=20
code.</FONT> <BR><FONT size=3D2>> > > </FONT><BR><FONT =
size=3D2>> >=20
> Ken</FONT> <BR><FONT size=3D2>> > > </FONT><BR><FONT =
size=3D2>>=20
> > --- Othman <othman2@gmail.com> wrote:</FONT> <BR><FONT =
size=3D2>> > > > what tool did you use for =
migration</FONT>=20
<BR><FONT size=3D2>> > > ></FONT> <BR><FONT size=3D2>> =
> >=20
></FONT> <BR><FONT size=3D2>> > > > On Wed, 9 Mar 2005 =
08:50:58=20
-0500 (EST), Ken</FONT> <BR><FONT size=3D2>> > > > =
Langendock</FONT>=20
<BR><FONT size=3D2>> > > > =
<ken.langendock@rogers.com>=20
wrote:</FONT> <BR><FONT size=3D2>> > > > > I have =
converted an=20
application from many</FONT> <BR><FONT size=3D2>> > =
machines</FONT>=20
<BR><FONT size=3D2>> > > > to</FONT> <BR><FONT =
size=3D2>> > >=20
> > other lines.</FONT> <BR><FONT size=3D2>> > > > =
></FONT>=20
<BR><FONT size=3D2>> > > > > I started out on the VAX =
(in my=20
opinion the</FONT> <BR><FONT size=3D2>> > best</FONT> <BR><FONT=20
size=3D2>> > > > > machine still to this day), then to=20
HP3000,</FONT> <BR><FONT size=3D2>> > then</FONT> <BR><FONT =
size=3D2>>=20
> > > UNIX</FONT> <BR><FONT size=3D2>> > > > > =
(HP, SUN,=20
IBM, DG, etc) then to Powerhouse</FONT> <BR><FONT size=3D2>> =
NT.</FONT>=20
<BR><FONT size=3D2>> > > > ></FONT> <BR><FONT =
size=3D2>> >=20
> > > I created a system management module that</FONT> =
<BR><FONT=20
size=3D2>> > takes</FONT> <BR><FONT size=3D2>> > > > =
all=20
of</FONT> <BR><FONT size=3D2>> > > > > the O/S level =
code away=20
from your</FONT> <BR><FONT size=3D2>> application.</FONT> <BR><FONT =
size=3D2>> > > > This</FONT> <BR><FONT size=3D2>> > =
> >=20
> allows me to convert from one platform to</FONT> <BR><FONT =
size=3D2>>=20
> another</FONT> <BR><FONT size=3D2>> > > > > =
transparently to=20
the User/Application.</FONT> <BR><FONT size=3D2>> > > > =
></FONT>=20
<BR><FONT size=3D2>> </FONT><BR><FONT size=3D2>=3D=3D=3D message =
truncated =3D=3D=3D</FONT>=20
</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>=20
<BR><FONT size=3D2>Mailing list: powerh-l@lists.sowder.com</FONT> =
<BR><FONT=20
size=3D2>Subscribe: "subscribe" in message body to=20
powerh-l-request@lists.sowder.com</FONT> <BR><FONT =
size=3D2>Unsubscribe:=20
"unsubscribe <password>" in message body to=20
powerh-l-request@lists.sowder.com</FONT> <BR><FONT size=3D2><A=20
href=3D"http://lists.sowder.com/mailman/listinfo/powerh-l"=20
=
target=3D_blank>http://lists.sowder.com/mailman/listinfo/powerh-l</A></FO=
NT>=20
<BR><FONT size=3D2>This list is closed, thus to post to the list you =
must be a=20
subscriber.</FONT> </P></BLOCKQUOTE></DIV>
<DIV> </DIV>
<DIV>
<P> <FONT face=3DArial =
size=3D2>This=20
message may contain privileged and/or confidential information. If =
you=20
have received this e-mail in error or are not the intended recipient, =
you may=20
not use, copy, disseminate or distribute it; do not open any =
attachments, delete=20
it immediately from your system and notify the sender promptly by e-mail =
that=20
you have done so. Thank you.</FONT> </P></DIV></BODY></HTML>
------_=_NextPart_001_01C52584.CD5D0B1A--