1.How would you characterize your organization's current approach to modernization?

Reactive — We modernize when something breaks or we are forced by circumstance (end of support, compliance, vendor pressure, etc.)

Ongoing/continuous — Modernization is a standing program, not a project

Ad hoc — Occasional initiatives, no consistent cadence

Strategic/planned — Multi-year roadmap with defined milestones

2.Where does your organization stand on using AI tools for modernization work (code conversion, documentation, refactoring)?

Not using AI tools; no plans currently

Evaluating/piloting AI tools

Using AI tools for specific tasks (e.g., code analysis, documentation)

AI tools are integrated into our regular modernization workflow

3.What is the biggest factor driving your modernization efforts?

Keeping pace with security/compliance requirements

Hardware/software end-of-support or refresh cycles

Competitive pressure / business agility needs

Staffing — Modernizing to reduce dependency on scarce legacy skills

Nothing specific driving it right now

Other (please specify)

4.How is your organization handling the modernization of legacy IBM i documents and forms (invoices, POs, shipping documents, etc.)?

Fully modernized – We generate digital, styled PDFs/forms using modern tools that pull directly from IBM i spool files or data. -

Hybrid approach – We use some modern tools, but still rely on legacy methods for certain forms.

Legacy methods only – We still use AFP/AFPDS, pre printed stock, or plain text spool files.

Outdated third party software – We use a forms package that is old, unsupported, or difficult to maintain.

In transition – We are actively evaluating modernization tools this year.

Not applicable – We no longer generate forms on IBM i.

5.When your team needs to update or design a business form on IBM i, what is your biggest challenge?

Legacy skill gaps – Updating forms requires older technical knowledge (AFP, DDS, RPG) that few team members have.

Complex or slow tools – Form changes take too long or require coding that slows down the process.

Dependency on one expert – Only one or two people know how to update forms, creating bottlenecks.

Decentralized or scattered design tools – Form templates live on PCs/Windows servers instead of being centrally managed.

Governance issues – No standardized process for versioning, approvals, or deployment.

No major challenges – Our current form design/update process works smoothly.

6.Would you like to be entered into a drawing for a $50 Visa gift card for completing this survey? (If "yes," please provide name and email below.)

Yes

No

7.Please provide your name and email address