Good CMS for traditional IBM i development
Use Cases and Deployment Scope
We use Rocket Aldon for managing IBM i development in SQL, CL, RPG, etc. This helps us manage our changes and makes sure we don't overlook related objects when making changes. It is used only by IT. Rocket Aldon helps us keep a history of software changes and is useful for classifying the reason for the change.
Pros
- Software Change Management
- IBM i development
- Object relationships
Cons
- SQL object promotions
- User interface
- Incomplete error checking
- Fragmented promotion logs
Likelihood to Recommend
Rocket Aldon is perfect for simple changes to traditional IBM i development using RPGLE, CL, and DDS. It is great for finding related objects that are referenced in many locations and helping recompile all of these objects.
However, Aldon has a particularly hard time with SQL views. For some reason, it is determined to lock every table related to a view even though this is not required by the operating system. Whenever one view references another view, you are always in danger of losing a view permanently if you didn't check it out and promote it. To clarify, imagine you created a view CUSTOMER_INFO. Then you make another view called CUSTOMER_SHIPMENTS that joins the CUSTOMER_INFO to a shipping table. If you ever change CUSTOMER_INFO and then promote it, there is a good chance that Aldon will delete the CUSTOMER_SHIPMENTS view and you will not get a single warning. It doesn't happen every time but when it does you are going to have a real mess on your hands.
