ACE UtilitiesChange Management Utility (SMAC)
Source Management and Access Control (SMAC) is a "Change Management" software system designed to allow you to manage software development on your IBM AS/400 computer. SMAC allows you to be able to track and secure your source and objects through various stages of program development, with appropriate programmer and user testing, with the final approved set of programs being implemented in the production environment. The following table helps contrast the application situations where SMAC works best and where it does not work as well:
|What SMAC is||What SMAC is not|
|- Source Management||- Object Management|
|- Single System||- Multiple Systems|
|- AS/400||- PC|
|- Source member versioning||- Application Level versioning|
SMAC Main Menu
Production Source Security
Production source files are grouped into "Environments." Source members in production environments cannot be changed. To modify a source member, the programmer must "Promote" the members through SMAC into a "Development Environment". This check out process requires a "Request Number" which describes the reason for modification. Once modifications have been made and properly tested, the source members are promoted to either another development environment for further testing, or back into production.
Source Member Version Control, Archiving, & History Log
Each source member is assigned a "Version Number." This number is divided into three parts -- version, release and mod level -- which are separated by periods. (Example, 1.0.0). SMAC automatically increments the number whenever the source files are promoted from production to development. Users may decide which of the three segments changes. For example, production version 1.0.0 can become 1.0.1, 1.1.0 or 2.0.0 depending on the user's preference.
When a member is promoted back into production, the prior production version is not deleted, but rather "Archived" in a compressed format that can be retrieved at any time if necessary.
Production source members can also be stored in the archive file in a compressed format. Storage space can be reduced by 70 to 90 percent by using compression.
Archived members may be offlined to and retrieved from tape. Specific members to save or retrieve may be selected individually or by using a number of selection parameters.
All activity within SMAC is logged to a history file. This allows for inquiry and/or reporting of development activity on a wide range of parameters.
Check Out Screen
Staging allows you to execute commands of your own choosing at the completion of the promote process. This can include any combination of valid OS/400 commands. Commands can be invoked based on combinations of source library, file, type and member. Commands can have imbedded substitution parameters such as library, file, type, member, etc... similar to &l,&f,&n in PDM.
Some possible uses for staging include:
- Compilation of the source member.
- Setting proper authorities/ownership to the object.
- Running user written utility programs against the source member.
- Compiling or moving objects associated with the source member.
- Any number of valid OS/400 commands.