Anyone have Moved from VMS to WINDOWS?

[Othman]

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.
> > >
> >
>