BMC AMI DevX solutions are primarily used for mainframe-based resources and application development, encompassing not only COBOL but also Workbench and VS Code for various purposes. Data management tools like File-AID enhance these capabilities, with features such as Host Manager allowing access to UNIX files on the mainframe, collectively serving as platform operations tools for developers. While I am aware of the possibility to integrate Git with BMC AMI DevX zAdviser, this integration does not fit within our solution landscape.
As the administrator of BMC AMI DevX Code Pipeline, I set up applications, pipelines, associations, flags, and deployment. BMC AMI DevX Code Pipeline's deployment process has three phases. The first phase moves the source code from ISPW's internal libraries to the production libraries. Then it performs the implementation phase, and the final phase is the activation phase. The activation phase moves the code and performs DB2 binds if DB2 is involved in the COBOL programs. During the activation phase, if there are any CICS modules, it performs new copies and phasing commands. It actually runs and kicks off those started tasks to handle the activation phase.
We do development for our customers and we use Topaz to do backend systems for some Latin American banks. It's for enterprise data. It runs on AWS. I'm working on performance testing to do batch performance tests doing step functions with AWS for processes running through the database.
BMC AMI DevX is a mainframe DevOps platform for IBM Z environments that helps development and platform engineering teams increase release velocity, reduce change risk, and build a sustainable mainframe developer workforce. Whether the priority is attracting the next generation of mainframe talent, safely evolving decades of business-critical code, accelerating release velocity, or demonstrating development ROI to leadership — BMC AMI DevX is designed to address all on a single platform. Teams...
BMC AMI DevX solutions are primarily used for mainframe-based resources and application development, encompassing not only COBOL but also Workbench and VS Code for various purposes. Data management tools like File-AID enhance these capabilities, with features such as Host Manager allowing access to UNIX files on the mainframe, collectively serving as platform operations tools for developers. While I am aware of the possibility to integrate Git with BMC AMI DevX zAdviser, this integration does not fit within our solution landscape.
As the administrator of BMC AMI DevX Code Pipeline, I set up applications, pipelines, associations, flags, and deployment. BMC AMI DevX Code Pipeline's deployment process has three phases. The first phase moves the source code from ISPW's internal libraries to the production libraries. Then it performs the implementation phase, and the final phase is the activation phase. The activation phase moves the code and performs DB2 binds if DB2 is involved in the COBOL programs. During the activation phase, if there are any CICS modules, it performs new copies and phasing commands. It actually runs and kicks off those started tasks to handle the activation phase.
We do development for our customers and we use Topaz to do backend systems for some Latin American banks. It's for enterprise data. It runs on AWS. I'm working on performance testing to do batch performance tests doing step functions with AWS for processes running through the database.