Thanks to all who replied. Gives me some ideas. But maybe if I explained
more I can get some more focussed answers.

What I am looking for is an "GUI" screen writer for applications written in
COBOL. Applications to run on the HP3000. Sort of a VPlus replacement. (For
an  explanation of why we would want to replace some the perfectly good
VPlus screens we already have read on).

I am somewhat familiar with some of the transition tools which re-write
VPlus screens into GUI's on other platforms. Our twist is this is for the
same thing but on an HP3000 platform.

Why?

History: We had replaced just a portion of our HP3000 applications with an
HP9000 application several years ago. The HP9000 portion is GUI screens.
(Oracle, etc.). The users of the HP9000 application are used to GUI. They
are insisting on GUI for the future. They are passionately resisting any
change back to VPlus style screens.

The future: All applications, both HP9000 and HP3000 are being replaced by
corporate mandated "synergy" systems - third party apps which are supposed
to look the same throughout Domtar. This is happening in two main phases.
The first phase late 2003, early 2004. The second grouping of apps will be a
couple of years later converted in the 2006 time frame.

Problem: The first phase is replacing 80% of our current HP9000 apps. But we
need to figure out what to do with the remaining 20% that we need to keep
alive for a couple of years until the second phase. 99% of current HP3000
apps are staying until second phase in 2006.

It appears it will not make sense to keep the remaining 20% on the HP9000.
That 20% is highly interfaced to the HP3000 apps and leaving it on the
HP9000 would require a three way, seven failure point interface. To get
everything talking HP3000 apps <-> Remaining 20% HP9000 <-> New Synergy apps
would be a real mess. Plus there is the huge cost of maintaining an Oracle
license for the same number of users but only 20% of the functionality.

We still have the old code on the HP3000 from before the HP9000 application
was brought up. It appears to make a lot more sense to revive the HP3000
code for the 20% we need to keep from the HP9000. So it is all on one
machine. Simpler interfaces. No Oracle.

But the users are mentally stuck on GUI screens. If we can revive the old
code and simply replace the screens with a GUI interface, the users will
probably be satisfied for the couple of years we need to keep this mess
alive.

So I am looking for a tool to help us go back to the HP3000 and sideways to
GUI screens while hopefully not ending up with my head up my a..

Timothy Atwood
Holtenwood Computing
http://www.holtenwood.bc.ca/computing/
for Domtar Vancouver Mill
(Opinions expressed are mine and do not reflect Domtar)


>  -----Original Message-----
> From:         Atwood, Tim (DVM)
> Sent: Thursday, June 19, 2003 11:50 AM
> To:   HP3000-L (E-mail)
> Subject:      GUI <-> HP3000 Image Tools
>
> We are looking for a GUI interface to HP3000 Image databases. I would
> appreciate hearing about people's experience with the multiple tools
> currently available. Ease of development, efficiency, overhead,
> look-and-feel, price and support are all factors. Plus probably other
> criteria I have not thought of yet.
>
> I am happy to hear from vendors. However, I ask that you please state
> clearly you are a vendor representing the product. If replying to the list
> also, the standard <plug> notation would be appropriate. Please note any
> sales pitches disguised as objective opinion will immediately remove the
> offending vendor from consideration.
>
>

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *