Managing Content

Provides tools to add, update, or remove programming objects, database entities, and related resources.

In MDVisual, managing content refers to maintaining the internal components that make up a repository. Each repository contains an analyzed collection of source-level and system-level elements — programs, service programs, modules, SQL routines, and database files — and MDVisual provides several tools to help you keep this content accurate, updated, and consistent.

Once a repository is created, it represents a snapshot of the libraries or directories from which it was built. Over time, as application components change or new source members are added, repositories can be rebuilt, or extended to ensure the information they contain remains up to date.

Adding New Content

When new programs, files, or routines are introduced in your IBM i environment, MDVisual allows you to include them by performing a repository build.
This process re-analyzes the connected libraries and detects any new or modified objects.

If a completely new application area needs to be analyzed, a new repository can be created and associated with its corresponding library through Add action.

You can Add/Change the libraries on which the repository should be based through Libraries option.

Updating Existing Content

Updating repository content ensures that the stored structure accurately reflects the current state of the system.
Whenever a program, module, or SQL routine is modified on the IBM i system, those changes can be incorporated into the repository through a Build action.

Removing Content

In certain cases, outdated or deprecated objects must be removed from the repository to prevent confusion.
MDVisual provides a Delete option, which allows you to permanently remove an obsolete repository.

If a repository is deleted, all associated analysis data — including object relationships and visual diagrams — is cleared.
This ensures that the workspace only contains relevant and active repositories.

For objects or elements within a repository, removal typically occurs automatically during rebuild/build if those elements are no longer found in the underlying libraries.

Backup and Version Management

Before performing large-scale changes or cleanup activities, MDVisual supports creating backup repositories.
A backup preserves the original structure, content, and relationships, allowing developers to restore or compare versions later.
This is especially useful when analyzing the impact of system migrations, refactoring, or large application updates.

Backups and copies also serve as safe checkpoints in environments where multiple users or teams work with the same repository data.

NOTE

• Refresh repositories regularly to view current status of the repository.
• Build repositories regularly to maintain consistency with your source libraries.
• Create backups before major updates or structural changes.
• Use meaningful names and descriptions for repositories to identify their purpose easily.
• Keep repositories clean by deleting obsolete or unused ones.