To prepare a containerized native COBOL application for debugging on Enterprise Server

To be able to debug a containerized native COBOL application that is running on Enterprise Server, you must have configured the container so that:

• The Web Services and J2EE listener are running on fixed ports (which will be published automatically by Visual COBOL). Additionally, any other listener ports that you need to communicate with in order to interact with your application (such as TN3270) must be running on fixed ports and you must publish those ports manually using the -p or -P option when running the container.

  See To set a fixed port in a listener endpoint address for information on setting a fixed port for listeners, and Docker: Docker run reference for information on using the -p or -P option to the docker run or podman run to publish the port when running the container.

• The environment configuration of the enterprise server defines the ES_DDBG_PORT_RANGE environment variable and specifies the port that Visual COBOL will use to connect to the container. For example:

  [ES-Environment]
  ES_DDBG_PORT_RANGE=08000,00001

  See To Set Environment Variables from ESCWA and Environment variables in alphabetical order for more information.

  See Docker: Docker run reference for information on using the -p or -P option to the docker run or podman run to publish the port when running the container.

• The container contains the debug information (.idy) files for the application to be debugged.

  You might want to store these files in the same directory as the executable files, to simplify the container's configuration.