Fw: Powerhouse - migrate/port from HP3000 MPE to UNIX or Windows
Philip Jackson
pj@icing-it.co.uk
Fri, 23 Apr 2004 14:32:43 +0100
This is a multi-part message in MIME format.
------=_NextPart_000_00C3_01C4293F.D6A4A790
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Powerhouse - migrate/port from HP3000 MPE to UNIX or WindowsI have just =
finished helping a client move several applications from =
HP3000/TurboIMAGE to HP-UX & C-ISAM.
We looked at moving to Oracle on HP-UX, but discounted it mainly because =
the primary application relied heavily on arrays and substructures - =
things that don't fit easily into a relational system. If we had been =
starting a new application then Oracle would probably have been used as =
the database, but the port was much easier from Image to C-ISAM. We =
didn't look at Eloquence as I don't think it was even in beta-test at =
the time we were looking at options.
The majority of the code moved over smoothly. Most recompiled without =
problems, and most PowerHouse code changes were to do with the order =
records were retrieved.
We did discover that several of our QTPs accidently created duplicate =
unique keys briefly while updating due to the order of updates - Image =
doesn't enforce unique keys on detail datasets so it never caused a =
problem before, whereas C-ISAM does it properly and would crash the QTP. =
However it was simple to fix once we figured out what was causing it.
Our biggest changes were, as you would expect, relating to interaction =
with the OS for things like printing and streaming jobs. I would =
recommend that you investigate the running/creating of scripts/jobs on =
the fly (if you do that) very carefully.
The HP-UX machine runs about twenty (thats 20) times faster! - of course =
it's a completely different type of machine and more powerful, but the =
speed increase was almost incidental and impressed even the most =
demanding users. In fact sometimes it was difficult to convince the =
users that the jobs that usually would take, say, 20 minutes to run were =
completed and printing in under a minute.
If you do anything at all fancy with printing, unix will fight you all =
the way. There is no inbuilt way to print a range of pages, or part of =
a file, or even resuming a jammed printout back a bit without cancelling =
and resubmitting the print. While it does nice banner pages and is fine =
for printouts that, well, just print and don't jam, adding a new printer =
for example stops and restarts all print jobs currently printing from =
the beginning (or if you're lucky just stops them). We tried a couple =
of third-party spooling products but quite frankly they were relying on =
a greater depth of knowledge of networks and unix than we had or wanted, =
and were really aimed at a mixed os printing environment. A few things =
were better, but by-in-large I consider printer handling on HP-UX =
'incomplete'.
Some of the more advanced users were used to using various line editors =
to write their own quizes. There was no way they could have handled vi =
on HP-UX - even some of the non-unix programmers spent days laughing =
hysterically over it - so we bought the new Qedit for HP-UX for them. =
There were other ways we could have done it - perhaps having shares on =
the unix boxes mapped in Windows so that they could have used Notepad or =
any other windows editor instead - but it was decided this was a better =
fit. And it helped some of the programmers too who were already feeling =
unloved by unix.
The standard users wouldn't have noticed the difference between it =
running on HP3000 or HP-UX, if it wasn't for the enormous speed =
increase. Quick screens handle just about identically, and they even =
continued using the same terminal emulators.
Hope this answers some of your questions, and reassures anyone else =
looking at doing PowerHouse HP3000 to HP-UX.
Can't advise with porting to PowerHouse on Windows, and as for =
converting to Cobol / Java, that would be a re-write rather than a =
'simple' port and therefore quite a different type of project. Maybe if =
you were going to be replacing an old PowerHouse application that no =
longer suited the business with a brand new =
better-stronger-faster-differently-featured one and you didn't want to =
stay with PowerHouse (shame!) then using a completely different language =
would make sense. But I can't see that porting between such very =
different languages would be a good use of your time and effort.
Philip.
----- Original Message -----=20
From: Fritsch, Peter-Robert=20
To: powerh-l@lists.sowder.com=20
Sent: Friday, April 23, 2004 10:54 AM
Subject: Powerhouse - migrate/port from HP3000 MPE to UNIX or Windows
Hi, what is the best way to port/migrate/run PowerHouse applications =
(with TurboIMAGE) from a HP 3000 / MPE to UNIX or Windows Servers.
Are there runtimes for Powerhouse on UNIX or Windows, which can be =
used for the applications developed for HP3000.=20
Are there porting or migration tools from PowerHouse to COBOL / JAVA.=20
What is the best way for the exchange of the environment, whereby the =
applications should be still working under UNIX or Windows.
Thanks a lot, regards Peter=20
Ing. Mag. Peter Robert Fritsch=20
Account Manager=20
Gesch=E4ftsfeld Informatik=20
Tel.: +43 1 797 50-231=20
Fax: +43 1 797 50-8008=20
Mobil: +43 676 765 66 31=20
Email: peter-robert.fritsch@beko.at=20
BEKO Ing. P. Kotauczek GmbH=20
A-1030 Wien=20
Modecenterstra=DFe 22/A1/6=20
www.beko-informatik.com=20
------=_NextPart_000_00C3_01C4293F.D6A4A790
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Powerhouse - migrate/port from HP3000 MPE to UNIX or =
Windows</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I have just finished helping a client =
move several=20
applications from HP3000/TurboIMAGE to HP-UX & C-ISAM.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>We looked at moving to Oracle on HP-UX, =
but=20
discounted it mainly because the primary application relied heavily =
on=20
arrays and substructures - things that don't fit easily into a =
relational=20
system. If we had been starting a new application then Oracle =
would=20
probably have been used as the database, but the port was much easier =
from Image=20
to C-ISAM. We didn't look at Eloquence as I don't think it was =
even in=20
beta-test at the time we were looking at options.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>The majority of the code moved over =
smoothly. =20
Most recompiled without problems, and most PowerHouse code changes were =
to do=20
with the order records were retrieved.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>We did discover that several of our =
QTPs accidently=20
created duplicate unique keys briefly while updating due to the order of =
updates=20
- Image doesn't enforce unique keys on detail datasets so it never =
caused a=20
problem before, whereas C-ISAM does it properly and would crash the =
QTP. =20
However it was simple to fix once we figured out what was causing=20
it.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Our biggest changes were, as you would =
expect,=20
relating to interaction with the OS for things like printing and =
streaming=20
jobs. I would recommend that you investigate the running/creating =
of=20
scripts/jobs on the fly (if you do that) very carefully.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>The HP-UX machine runs about twenty =
(thats 20)=20
times faster! - of course it's a completely different type of machine =
and more=20
powerful, but the speed increase was almost incidental and impressed =
even the=20
most demanding users. In fact sometimes it was difficult to =
convince=20
the users that the jobs that usually would take, say, 20 minutes to =
run=20
were completed and printing in under a minute.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>If you do anything at all fancy with =
printing, unix=20
will fight you all the way. There is no inbuilt way to print a =
range of=20
pages, or part of a file, or even resuming a jammed printout back a=20
bit without cancelling and resubmitting the print. While it =
does nice=20
banner pages and is fine for printouts that, well, just print and don't =
jam,=20
adding a new printer for example stops and restarts all print jobs =
currently=20
printing from the beginning (or if you're lucky just stops them). =20
We tried a couple of third-party spooling products but quite =
frankly they=20
were relying on a greater depth of knowledge of networks and unix =
than we=20
had or wanted, and were really aimed at a mixed os printing =
environment. A=20
few things were better, but by-in-large I consider printer handling on =
HP-UX=20
'incomplete'.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Some of the more advanced users were =
used to using=20
various line editors to write their own quizes. There was no way =
they=20
could have handled vi on HP-UX - even some of the non-unix programmers =
spent=20
days laughing hysterically over it - so we bought the new Qedit for =
HP-UX for=20
them. There were other ways we could have done it - perhaps having =
shares=20
on the unix boxes mapped in Windows so that they could have used Notepad =
or any=20
other windows editor instead - but it was decided this was a better =
fit. =20
And it helped some of the programmers too who were already feeling =
unloved by=20
unix.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>The standard users wouldn't have =
noticed the=20
difference between it running on HP3000 or HP-UX, if it wasn't for the =
enormous=20
speed increase. Quick screens handle just about identically, and =
they even=20
continued using the same terminal emulators.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Hope this answers some of your =
questions,=20
and reassures anyone else looking at doing PowerHouse HP3000 to=20
HP-UX.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Can't advise with porting to =
PowerHouse on=20
Windows, and as for converting to Cobol / Java, that would be a re-write =
rather=20
than a 'simple' port and therefore quite a different type of =
project. =20
Maybe if you were going to be replacing an old PowerHouse application =
that no=20
longer suited the business with a brand new=20
better-stronger-faster-differently-featured one and you didn't want to =
stay with=20
PowerHouse (shame!) then using a completely different language would =
make=20
sense. But I can't see that porting between such very different =
languages=20
would be a good use of your time and effort.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Philip.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV>----- Original Message ----- </DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A title=3DPeter-Robert.Fritsch@beko.at=20
href=3D"mailto:Peter-Robert.Fritsch@beko.at">Fritsch, Peter-Robert</A> =
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dpowerh-l@lists.sowder.com=20
=
href=3D"mailto:powerh-l@lists.sowder.com">powerh-l@lists.sowder.com</A> =
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Friday, April 23, 2004 =
10:54=20
AM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Powerhouse - =
migrate/port from=20
HP3000 MPE to UNIX or Windows</DIV>
<DIV><FONT face=3DArial size=3D2></FONT><FONT face=3DArial =
size=3D2></FONT><FONT=20
face=3DArial size=3D2></FONT><FONT face=3DArial size=3D2></FONT><FONT =
face=3DArial=20
size=3D2></FONT><FONT face=3DArial size=3D2></FONT><FONT face=3DArial=20
size=3D2></FONT><FONT face=3DArial size=3D2></FONT><FONT face=3DArial=20
size=3D2></FONT><BR></DIV><!-- Converted from text/rtf format --><BR>
<P><FONT face=3DArial size=3D2>Hi, what is the best way to =
port/migrate/run=20
PowerHouse applications (with TurboIMAGE) from a HP 3000 / MPE to UNIX =
or=20
Windows Servers.</FONT></P>
<P><FONT face=3DArial size=3D2>Are there runtimes for Powerhouse on =
UNIX or=20
Windows, which can be used for the applications developed for =
HP3000.</FONT>=20
<BR><FONT face=3DArial size=3D2>Are there porting or migration tools =
from=20
PowerHouse to COBOL / JAVA.</FONT> </P>
<P><FONT face=3DArial size=3D2>What is the best way for the exchange =
of the=20
environment, whereby the applications should be still working under =
UNIX or=20
Windows.</FONT></P>
<P><FONT face=3DArial size=3D2>Thanks a lot, regards Peter =
</FONT></P><BR>
<P><B><FONT face=3DTahoma size=3D2>Ing. Mag. Peter Robert =
Fritsch</FONT></B>=20
<BR><FONT face=3DTahoma size=3D2>Account Manager</FONT> <BR><FONT =
face=3DTahoma=20
size=3D2>Gesch=E4ftsfeld Informatik</FONT> </P>
<P><FONT face=3DTahoma size=3D2>Tel.: +43 1 797 =
50-231</FONT>=20
<BR><FONT face=3DTahoma size=3D2>Fax: +43 1 797 =
50-8008</FONT>=20
<BR><FONT face=3DTahoma size=3D2>Mobil: +43 676 765 66 31</FONT> =
<BR><FONT=20
face=3DTahoma size=3D2>Email: =
peter-robert.fritsch@beko.at</FONT> </P>
<P><B><FONT face=3DArial size=3D2>BEKO</FONT></B><FONT face=3DArial =
size=3D2></FONT>=20
<FONT face=3DTahoma size=3D2>Ing. P. Kotauczek GmbH</FONT> <BR><SPAN =
lang=3Dit><FONT=20
face=3DTahoma size=3D2>A-1030 Wien</FONT></SPAN> <BR><SPAN =
lang=3Dit><FONT=20
face=3DTahoma size=3D2>Modecenterstra=DFe 22/A1/6</FONT></SPAN> =
<BR><SPAN=20
lang=3Dit></SPAN><A href=3D"file://www.beko-informatik.com"><SPAN =
lang=3Dit><U><FONT=20
face=3DTahoma color=3D#0000ff=20
size=3D2>www.beko-informatik.com</FONT></U></SPAN></A><SPAN =
lang=3Dit></SPAN>=20
</P><BR></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_00C3_01C4293F.D6A4A790--