Your needs
Web-enable my 5250 screens,
without rewriting my RPG code
You want to get your users off the green screen. It can be done, and in more than one way: three solutions, depending on how far you want to go. None of them touches your RPG code, which remains your foundation.
Questions we get asked
Does this sound like your situation?
Hover over a card to see the answer, and the product that addresses it.
Web access
“I just want my teams to reach the IBM i from a browser, without installing an emulator on every workstation.”
See the answer
It is the first step, and the simplest. Your screens become accessible from a browser, anywhere, with no thick client and nothing to install on workstations. The screen doesn’t look any different yet, but it is no longer locked inside an emulator.
Without the source code
“The application comes from a software vendor; I don’t have the source code.”
See the answer
That is exactly the case PHL 5250 handles. Program, command or query: the application is called as it is, with no modernisation and no rewrite. Where web-enablement needs your source code, the web emulator needs none.
Automatic transformation
“Web access isn’t enough: the screen is still green. I want it to look modern, without reworking every screen one by one.”
See the answer
Here, the look is transformed automatically, at run time. The green disappears across the whole application, with no screen-by-screen work and without changing a single line of your source code.
Business-driven web-enablement
“Our users go through several 5250 screens for a single task. I want to bring all of that together on one page.”
See the answer
This is full web-enablement: the interface is redesigned around the business process rather than the screen. Users no longer jump from screen to screen; they see their work brought together in the right place — and your RPG programs stay in control of the dialogue.
On your current machine
“We are on the P05 software tier. I don’t want to change machines or move up a tier.”
See the answer
You don’t have to. PHL tools are designed to stay lightweight and run on your current machine, where other solutions force you to upgrade. You modernise on what you already have.
Timing
“I don’t have a big development team. How long does it take?”
See the answer
It depends on the step: almost immediate go-live for web access and automatic transformation, a few weeks for business-driven web-enablement. And you are not on your own: our development and support teams help with the integration and then throughout the project.
Three solutions
One starting point: your RPG code
What changes is how far you take the screen.
PHL 5250
Web access
Your screens accessible from a browser, with no emulator and nothing to install on workstations.
Who it’s for
Getting out of the emulator quickly and simply — even without the source code.
PHL Revamp
Automatic transformation
The green screen becomes a modern graphical interface, at run time, with no screen-by-screen rework.
Who it’s for
Modernising the look of an entire application estate with minimal effort.
PHL Web
Business-driven web-enablement
The interface redesigned around the process, with screens built for the business.
Who it’s for
Rethinking the experience where productivity is at stake.
How we move forward
Nothing forces you to do everything at once
01
Start light
Browser access is set up without a project: you measure the effect on users before committing to anything.
02
Step up when the need arises
Automatic transformation applies to the whole estate. Nothing is locked in, and nothing from the previous step is lost.
03
Redesign where it matters
The most-used screens deserve a real business redesign. The others stay as they are: you invest where there is a return.