AWS Transform for Mainframe Now Finds Business Functions at Field-Level Precision

Hi everyone, Shii-chan here! Today I'm covering an update to AWS Transform for mainframe.

AWS What's New aws.amazon.com

What was announced?

AWS What's New says the assess and reimagine workflow in AWS Transform for mainframe has been improved in two ways:

• It discovers business functions with field-level precision
• It generates a new requirements coverage report

It targets z/OS COBOL and PL/I workloads.

The story so far

Before, business functions that used the same table or file were grouped together.

And if you wanted traceability reporting, you had to build it yourself from AWS Transform artifacts.

What changes

• Grouping is more precise: business functions are grouped only when they affect the same data fields. They now include screens and queues, and have clearer names and descriptions
• A coverage report is included: you can check requirements coverage without assembling traceability yourself

You can start modernizing from a more accurate catalog of business functions.

Dive Deep

The requirements coverage report shows:

• Every line of source code, classified by how it was handled
• Every business rule, linked to the exact lines it came from
• Every requirement, backed by the business rules that support it

You can review coverage from the full portfolio down to a single line, then move into forward engineering in Kiro and other IDEs. That means you can verify coverage before you build.

It's available in all AWS Regions where AWS Transform for mainframe is available. See the product page and documentation for details.

Wrap-up

• Business function discovery is now field-level
• Screens and queues are included, with clearer names and descriptions
• The coverage report links source lines, business rules, and requirements
• You can verify coverage before forward engineering in Kiro and other IDEs

This one is for teams modernizing z/OS COBOL and PL/I assets!