Understand an IBM i application before changing it
Abstract is listed in Fortra’s IBM i portfolio as a developer-productivity tool. Scope the enquiry around the application understanding needed for a particular change: dependencies, objects and the relationships that affect maintenance. The desired output is an accurate working map for the supported codebase, not a claim that every business rule has been discovered automatically.
Identify libraries, source availability, languages and the release or maintenance task driving the request. Confirm the current Abstract capabilities and supported environment with the manufacturer. Include application specialists who can validate whether the resulting relationships correspond to actual production use.
Use dependency evidence to plan a bounded change
Choose a representative program or object and compare documented relationships with known application behaviour. Record limitations where source is missing, generated or maintained elsewhere. If the analysis influences a change plan, validate the affected workflow in an approved test environment rather than assuming that a static relationship map predicts every runtime condition.
Handover should preserve the analysed boundary, configuration, known gaps and the method for refreshing information after code changes. MMC can scope tool setup and selected knowledge transfer; application redevelopment, functional testing and ownership of business rules remain separately agreed work.
Evidence to request for this scope
- Confirm supported languages, object types and source requirements for the intended analysis.
- Validate a known dependency with an application maintainer and document unresolved relationships.
- Record when the analysis must be refreshed and who approves change-impact conclusions.