BMC AMI DevX Reviews and Ratings

Use Cases and Deployment Scope

we facilitate the BMC AMI Devx product usage across my company's developers

Likelihood to Recommend

Tool provides good functionalities, but recent upgrade had more issues which made the user experience to go down. It is main tool that our team provide application teams to work on but it failed with various issue, and it look longer for us to resolve due to support delays.

Likelihood to Recommend

Use Cases and Deployment Scope

BMC AMI DevX transforms mainframe developer experience, helping developers at all skill levels achieve seamless flow, low burnout, and higher job satisfaction.

Likelihood to Recommend

Assembler code development

Use Cases and Deployment Scope

BMC AMI DevX is used very widely in the organisation to view/edit flat and VSAM files. Developers rely heavily on the ability to see data in a formatted fashion and modify if needed.

Likelihood to Recommend

We only use BMC AMI DevX for viewing/editing files. We don't even use File Aid/DB2 too much.

Use Cases and Deployment Scope

This product makes day-to-day application development much easier.

Este produto facilita muito no dia a dia o desenvolvimento de aplicativos

Likelihood to Recommend

very good

<i>Parts of this review were originally written in Portuguese and have been translated into English using a third-party translation tool. While we strive for accuracy, some nuances or meanings may not be perfectly captured.</i>

Use Cases and Deployment Scope

We use the powerful tools of the BMC AMI DevX range, among others, to debug incidents that occur during program execution. Mainly in our development environments. This is really useful to see the content of the variables during execution. And it's very easy to configure either in batch mode or CICS mode.

Likelihood to Recommend

Code Debug is a very convinient tool in order to solve some issues , it's very quick to fix some problem with it. And it's better than coding display in the program (we have less work to do to obtain the result).

Use Cases and Deployment Scope

It is used by our COBOL Development for their Day-to-Day development, these could be bug fixes, feature changes or other changes like compliance changes.

Also, when there is a need to do some analysis on the code so that you can input onto a requirement Document or simply for knowledge sharing.

The whole of the development lifecycle is achieved via AMI DevX (Analysis, Code changes, Debug, Test and Deloy via Code pipeline.

Likelihood to Recommend

As a Developer this is a tool to use for my Day-to-day basic development activities (Code, Debug , Test , Deploy)

Use Cases and Deployment Scope

<div>The BMC AMI DevX products are used in our company for </div><div>

</div><div>- Mainframe Abend Analysis (Abend-AID, Abend-AID for CICS),

</div><div>- Mainframe Debugging (Code Debug for TSO, Code Debug for CICS, Code Coverage)</div><div>- Mainframe Performance Analysis (Strobe)</div><div>- Mainframe Data Management (File-AID/MVS, File-AID/RDX, File-AID/DB2, File-AID/Data Solutions)</div>

Likelihood to Recommend

All products give the developers and system programmers excellent support in their daily work. They are saving a lot of time when analysing any kind of problems (abends and dumps) or trying to improve performance of home grown software.

Use Cases and Deployment Scope

We are just starting our mainframe modernization effort. BMC AMI DevX is a fantastic toolbox to help with research, development, and improve our speed to market. Plus, it will be an advantage in attracting younger developers.

Likelihood to Recommend

I love these tools! However, my company has not yet transitioned from SCLM to a modern repository, and this is causing most of our developers to remain within TSO for all their development. It's been a slow adoption up to this point, but we are moving toward more modernization this year and next, so with any luck, we'll see usage pick up. Success depends on the speed at which your management is willing to move.

Use Cases and Deployment Scope

We are both new and old users of BMC AMI DevX tools within our organization. We are in the midst of cutting over from IBM's Software Configuration and Library Manager (SCLM) to BMC AMI DevX Code Pipeline and Workbench for Eclipse (that's the new) and we recently reinstalled Code Debug (formerly known as Xpediter) as well as Abend-AID and File-AID, all three of which we have used previously under the Compuware umbrella (that's the old). Our goal is to modernize the mainframe developer experience while establishing a solid base from which we can implement a fully integrated DevOps lifecycle that encompasses both our mainframe and our distributed platforms.

Likelihood to Recommend

The trick has always been to support "old school" mainframe developers in a cutting edge DevOps world. BMC AMI DevX manages to provide cross-platform interfaces and solutions that honor the past while serving the future. Change almost always involves a hit to productivity as developers unlearn old procedures and incorporate new ones. Eventually the new way of doing things should lead to higher productivity. Anyone introducing change seeks to have that "productivity dip" be as shallow as possible and last as short a time as possible. BMC AMI DevX accomplishes that well.