Classic first, templates where useful

Modernize the IBM i screens that benefit, not everything at once.

PristineScreen400 starts with a working Classic terminal. Add exact-screen templates to selected workflows while RPG or COBOL logic, host validation, function keys, and Db2 transactions remain on IBM i.

Review a workflow Read the no-rewrite guide

Direct answer

Can you modernize an IBM i green screen without rewriting RPG?

Yes, when the goal is to improve the presentation of selected 5250 workflows rather than replace the application architecture. PristineScreen400 maps approved browser components to exact fields on a matching live host screen. The original program continues to validate input and commit business transactions.

Two independent layers

Branding is not templating, and templating is not a rewrite.

A deployment can use the default product, apply a Brand Kit while every terminal remains Classic, or add published Presentation Profiles to exact users and IBM i grants.

Brand the browser entry while the IBM i application remains entirely Classic.

Brand Kit

Make the doorway yours.

Apply your product identity without changing the host application or requiring a screen template.

Product name, logo, and favicon
Login heading and instructions
Approved color palette
Support and legal content
Assignment to exact user and IBM i grants

Closed template model

Modern components bind to reviewed host geometry.

MATCH

Exact screen fingerprint

A recipe matches rows, columns, literal anchors, and declared field geometry. It does not accept regular expressions or guessed screens.

PRESENT

Bounded components

Headings, values, fields, selects, cards, layout elements, and buttons come from a closed declarative component set.

ACT

Approved host actions

A button may send one approved terminal key. It cannot contain a command, SQL statement, macro, script, or arbitrary operation.

FALLBACK

Safe Classic return

If no recipe matches the current screen, PristineScreen400 renders Classic. Users can also switch back while a template is active.

VERSION

Published revisions

Drafts are previewed before publication. Active workspaces pin the version selected when the workspace begins.

ASSIGN

Exact presentation scope

A published profile can be the installation default or apply to an exact application user and IBM i identity grant.

Frequently asked questions

Template behavior to confirm

Does a screen template copy business logic into the browser?

No. The template presents current redacted fields and sends bounded changes through the existing workspace. Host validation and database transactions remain in the IBM i application.

Must every 5250 screen be modernized?

No. Classic access is the complete starting point. Teams can prioritize frequent or customer-facing workflows and leave the rest unchanged.

Is this the same as RPG Open Access or a full rewrite?

No. Those approaches can remove or redesign deeper architectural dependencies. PristineScreen400 templates are a presentation layer over a live 5250 session, suited to incremental interface improvement.

Choose the first screen

Start with one representative IBM i workflow.

We will review the live 5250 behavior, identify exact screens that benefit, and preserve Classic fallback throughout the evaluation.

Review a workflow