Usage of DevX on our company (Code Pipeline, Workbench...)
July 16, 2024
Usage of DevX on our company (Code Pipeline, Workbench...)
Score 9 out of 10
Vetted Review
Verified User
Modules Used
- BMC AMI DevX Abend-AID
- BMC AMI DevX Code Pipeline
- BMC AMI DevX Code Debug
- BMC AMI DevX File-Aid
- BMC AMI DevX Workbench
Overall Satisfaction with BMC AMI DevX
We have been using the DevX product for a long time now. We have some problems to solve: young developers need to integrate, source code management needs to be done, production fallback needs to be met, release management needs to be met, and reporting on change needs to be done.
Pros
- Code Pipeline: integration of MF and non-MF type of object (COBOL, Java, zosconnect...). Deployment of objects coming from inside and outside the mainframe in the same way.
- Workbench for Eclipse: a must-have for working with Code Pipeline and the mainframe in the development context.
- Workbench for VS Code: They started developing VSCode, and the plugin works very well. There are a lot of things to add, but it's still very good. Young developers like it!
Cons
- Code Pipeline: Better integration of OMVS files. Some manual work still needs to be done.
- Better support of IMS/DL1/PL1 on their tooling (Code Insight, Total Test...)
- Control of source code change.
- Release management and usage control.
- Onboarding of young dev on the mainframe.
We can now modernize the developer desktop. They can use Eclipse or VSCode for their day-to-day work. Code Pipeline also provides a better overview of the ongoing change and the capability to fall back quickly in production.
Do you think BMC AMI DevX delivers good value for the price?
Yes
Are you happy with BMC AMI DevX's feature set?
Yes
Did BMC AMI DevX live up to sales and marketing promises?
Yes
Did implementation of BMC AMI DevX go as expected?
Yes
Would you buy BMC AMI DevX again?
Yes
Comments
Please log in to join the conversation