Anyone have Moved from VMS to WINDOWS?

[Ken Langendock]

DAMN

These undocumented features are a pain in the @@s

I just tried this and it worked beautifully. I could
have saved myself hours of work.

I think we need to start creating a new manual.
"Powerhouse, The Undocumented features".

Here are a couple more.

SET ASSUMED (Not to be used in critical situations)
DUMP filename (in quiz = access filename, report all,
go)


 --- "Deskin, Bob" <Bob.Deskin@cognos.com> wrote: 
> 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
> 
=== message truncated ===