Powerhouse HP3000 Migration

[Glenn Baxter]

Hi Luan, 
We are porting a Hp3000 environment to Windows2k for a Melbourne based
client.
We have chosen to use Axiant to enhance to users experience by way of user
interface.
We are using SqlServer2000 and will be deploying in Thin Client "mode", thus
executing all components {Quick, Qtp, Quiz} on the server. 
We have a range of workstations {by way of quality} and prefer the
reliability and performance offered 
by the server. {A dual Pentium 4, 2.2 with 2 gigabytes of memory, running a
Level 5 Raid Disc system for some 20-30 users}
We have found performance to be fantastic, albeit, we are still in Beta
testing with respect to the applications.

Many of the migration issues are common {databases, datatypes, indexes {vs
Automatic Masters under Image},
command files, environment variables for user and application etc}
regardless of the eventual user interface. I have only brief experience with
the DOS windows under Nt. We
had decided the enhanced interface offered by Axiant to be "worth" the
effort. The data migration effort was
only modest using the Axiant migration tools combined with some reasonable
SqlServer skills and application knowledge.
Axiant does provide a comprehensive multi-user IDE for developers also. We
are of course able to generate character based
forms for use with 8.41 Powerhouse from within Axiant in addition to the
Windows form overlay we currently
use.

Printers and Printing
Quiz can still only address {naturally} character based printing, that is,
any enhancements you may now have 
{escape character based font switching, portrait to landscape etc} remain
the same, but, you need to avoid the Windows Print subsystem, 
as it removes any "non-ascii" characters from the data-stream, and always
reverts to the target printers base 
font and orientation. We route all printed output to disc, then "Print" it
to printers which are appropriate 
for the reports. We have many 132 * 64 or 220 * 64 line reports. Routing to
disc is great as each user then has
a "spooler" folder of prior reports, viewable in notepad etc.

Command Files and "Parms"
An interesting area, particularly in Thin Client mode, where we are have
developed a form {VB Exe} which dynamically
populates a set of "parm prompt" fields, populates multi-select list boxes
using Sql to emulate Choose Statements or
provide "unbound" text boxes for other user parm/prompt values etc. 
This has involved "storing" the contents of all Hp Stream or Command files
within Sql, but has the advantage 
of making the construction and maintenance of command files a controlled
user interface driven task.

Where printed output is required we provide a Windows style printer
selection and copy quantity selection. 
This "stuff" is written to the server based command file {by application by
user by date & time} which is then submitted for execution 
by the calling screen. Quite a lot of work, but required for thin client.
And, the performance is great.

Our basis of staying with Powerhouse and moving to Nt was similar to yours,
where much of the application is highly
customised and very reliable {with respect to the Powerhouse "engine"}. Our
objective has beed to retain those
aspects and improve performance where possible. The clients "skill base" in
Powerhouse is still protected, and  the new
environment also provides leverage for extended use of the information. We
plan greater use of BI tools through
SqlServer etc over time.

I have noted the quiz performance comments from Blue. We haven't experienced
this yet. But as stated enhancing 
the quiz using embedded sql is an option. A windows report writer becomes an
option {Impromptu etc}.
We have some 600 reports, so weren't all that keen on redevelopment!!
{straight away}
Sincerely, 
Glenn Baxter
Baxter IT Solutions
==============================
15 Flora Grove Ivanhoe Victoria Australia 3079
==============================
telephone: 61-3-9499-8687
mobile: 0412-826-503
fax: 61-3-9499-8344
email: glenn@baxterit.com.au <mailto:glenn@baxterit.com.au> 
 
This e-mail message (and attachments) may contain information that is
confidential to Baxter IT Solutions. If you are not the intended recipient
you cannot use, distribute or copy the message or attachments. In such a
case, please notify the sender by return e-mail immediately and erase all
copies of the message and attachments. Opinions, conclusions and other
information in this message and attachments that do not relate to the
official business of Baxter IT Solutions are neither given nor endorsed by
it.

-----Original Message-----
From: lha@bigpond.net.au [mailto:lha@bigpond.net.au]
Sent: Wednesday, 2 July 2003 11:51 pm
To: powerh-l@lists.swau.edu
Subject: Powerhouse HP3000 Migration



One of my clients has a single PowerHouse app on an old HP3000 running 
MPE/iX v 7.0. The client is part of a large multi-national who want to 
move away from the HP3000 platform. However, we find that PH does the 
job well and the client is very reluctant to spend a whole heap of 
dollars re-writing the app which would end up doing what it does now 
but at higher cost and possibly lower reliability. Although it's a 
single app, it's a core system handling high revenue. One thought I 
have is to move to PH on a Windows NT/W2K server platform, possibly 
using the Eloquence database (PH version due late this year?).

My questions: what is your experience with running PH on Win NT/2K? I'm 
particularly interested in performance, reliability, interface to 
printers. What databases are you using?
The client is happy to continue with text-based screens - they 
currently use WQR Reflection which gives the users plenty of options 
for customising the display etc. Can the PH/Win NT combination also be 
customised in this way without going to Axiant or PH Web?
Any other observations or thoughts welcome!

Thanks,

Luan Ha
Principal Consultant, Padys Pty Ltd.

Email address : lha@bigpond.net.au

 


= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l@lists.swau.edu
Subscribe: "subscribe" in message body to powerh-l-request@lists.swau.edu
Unsubscribe: "unsubscribe <password>" in message body to
powerh-l-request@lists.swau.edu
http://lists.swau.edu/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.