Enterprise Developer Build Tools for Windows enables you to perform all of the compiling, linking, building, and running operations that you can perform from a command prompt in Enterprise Developer.
Enterprise Developer Build Tools for Windows includes exactly the same support for mainframe subsystems that is included in Enterprise Developer. This means that if you have used Enterprise Developer to create applications that make use of features such as CICS, IMS, JCL, Assembler or PL/I, using Enterprise Developer Build Tools for Windows to compile, link, build, and run those applications will have exactly the same effect as if you had used Enterprise Developer.
Because Enterprise Developer Build Tools for Windows does not use the Eclipse IDE you cannot use Eclipse to debug a COBOL application with Enterprise Developer Build Tools for Windows in the way that you would with Enterprise Developer. Instead, Enterprise Developer Build Tools for Windows's lack of an IDE makes it perfectly suited for use in Docker containers, a CI/CD environment, or any other automated build and test system.
To debug a COBOL application in Enterprise Developer Build Tools for Windows you use the remote development functionality offered in Enterprise Developer to attach to and debug the application that is running in Enterprise Developer Build Tools for Windows.
The following sections summarize the different commands you use in Enterprise Developer Build Tools for Windows to carry out these operations, and provide links to other parts of this documentation where you can find detailed information on the commands available in Enterprise Developer Build Tools for Windows.