 |
| MDCMS Workflow Client |
|
|
Manage Projects and Workflow
- Central Web-based tool for the business user or team leader to enter project or issue requests
- Track project/issue requests by programmer, status, due date, etc.
- Centrally approve, schedule, and track object migrations
- References all objects modified or commands performed for a request
- Project information automatically syncs across all systems
- Report generator provides various online, paper, or electronic reports
|
|
Workflow: Object Modification and Distribution
|
Step 1: Open Change Request
|
Step 2: Select objects to be modified or migrated and make the modifications within the programmer environment.
Step 3: The impacts of the planned changes will be analyzed (impact analysis).
Step 4: The impacted objects, programs, commands, etc., are referenced in the Change Request.
|
MDXREF is included in MDCMS, allowing the developer to easily and quickly navigate through the objects of an application:
- Search for objects, files, file fields or queries
- File references
- Process flow
- Complete Journal analysis to find and present transactions.
- Efficient comparison tools to search for differences on library-, object- or data level.
|
Step 5: Plan releases knowing the amount and the impact of planned changes (assign the changes to packages).
Step 6: Install the changes according to the Change Request. The MDCMS reservation system prevents version conflicts within a team.
Step 7: Archive source code and objects (up to 99 versions per object).
|
MDCMS ensures that source code and objects are always treated in the same, correct way (locations, object authorities, compilation parameters, etc.). It handles all IBM i object types, including IFS directories and stream files, message descriptions and data records.
Objects in libraries delivered from external vendors can be quickly selected for migration into your environment.
When a file is to be modified, all dependant files, programs, queries, etc, may also be automatically selected for modification or recompilation.
|
|
Step 8: Pre-Installation Checker validates the object package and warns if any conflicts, missed objects, etc., exist.
Step 9: Scheduler for hands-free installation while users are not on the system (e.g., evenings or weekend). If an installation cannot be completed, it is automatically rolled back and detailed error reporting is provided.
|
-
If necessary, part or all of an object package may be rolled back at any time in the future.
-
Data in modified files are mapped to new format and all logical access paths are rebuilt.
-
All necessary object authorities are applied.
-
Commands may be defined to run before or after the installation is complete.
|
Step 10: Simultaneously distribute object packages to unlimited machines or partitions via FTP, SNA, or tape.
|
|
