Configuring an Enterprise Server Region for Debugging

Restriction: The MFASM debugger is unable to open a window for debugging on any enterprise server region started via ESCWA, as Microsoft has permanently disabled access to the user desktop from any application started in the background and owned by "SYSTEM".

To debug any application containing one or more Assembler modules, with the exception of an application consisting of a standalone Assembler program, you must have an enterprise server available to run the application.

You configure an enterprise server to run an Assembler or an Assembler/COBOL application in much the same way as you would for any COBOL application. Depending on the type of application, be sure to include the path to your Assembler programs on the appropriate path specifications as follows:
  • JCL - JES Program Path
  • CICS - Transaction Path
  • CICS - File Path
  • IMS - TM Application Path

The ES_SERVER_CONSOLE=YES variable must be specified in the enterprise server configuration for the server that will be used to debug Assembler modules.

Non-CICS applications that contain both Assembler and COBOL require that you turn on (check) Allow Dynamic Debugging in the enterprise server configuration.

CICS applications require that you also set the environment ES_MFASM_SUPPORT=YES variable in the Configuration Information field in the enterprise server configuration:
[ES-Environment]
ES_MFASM_SUPPORT=YES
ES_SERVER_CONSOLE=YES