Remote debugging in standard mode

z/OS® Debugger obtains information (called debug information) it needs about a compilation unit (CU) by searching through the following sources:

For remote debugging in standard mode:

To debug Enterprise COBOL for z/OS V3.4 and V4 programs, specify the location of the listing files by adding the EQAV4LST DD name or the EQA_DBG_V4LIST environment variable. Adding either of those values makes the listing files available to the debugger. For example:
```
//EQAV4LST DD DSN=USER123.COBOL.LISTING,DISP=SHR
```
or
```
ENVAR("EQA_DBG_V4LIST=//'USER123.COBOL.LISTING'")
```
Note: EQAV4LST is only supported in batch.
To debug Enterprise COBOL for z/OS V6.2 programs with the debug information in side files, complete the following steps:
1. To generate the side files, compile the COBOL program with the TEST(SEPARATE) compiler option, and specify the SYSDEBUG DD name to store the generated side files.
2. Make the side files available to the debugger by specifying the location of the side files with the EQADEBUG DD name or the EQA_DBG_SYSDEBUG environment variable. For example:
```
//EQADEBUG DD DSN=USER123.COBOL.SYSDEBUG,DISP=SHR
```
  or
```
ENVAR("EQA_DBG_SYSDEBUG=USER123.COBOL.SYSDEBUG")
```
If you are using the Source view instead of the default Expanded Source view, make the source files available to the debugger by specifying the location of the source files with the EQASRCE DD name or the EQA_DBG_SRCE environment variable. This is used with data sets that contain only source files. For example:
```
//EQASRCE DD DSN=USER123.COBOL.SOURCE,DISP=SHR
```
or
```
ENVAR("EQA_DBG_SRCE=USER123.COBOL.SOURCE")
```
To debug z/OS C and C++, and 31-bit Enterprise PL/I for z/OS programs with separate side files, make the side files, which contain debugging information, available to the debugger by adding the EQADEBUG DD name to specify the location of the side files. For example:
```
//EQADEBUG DD DSN=USER123.PLI.DEBUG,DISP=SHR
```
To locate source files for C or C++ programs, add the EQASRCE DD name to specify the location of the application source files. For example:
```
//EQASRCE DD DSN=USER123.CPP.SOURCE,DISP=SHR
```
z/OS Debugger uses the source code compiled by 31-bit Enterprise PL/I for z/OS to display the source. Thus, that source code needs to be in a cataloged data set accessible to the debugger.
To debug 64-bit Enterprise PL/I for z/OS programs, z/OS debugger also uses the source code compiled by Enterprise PL/I for z/OS to display the source. If the source file no longer exists in the location that was provided as the input to the compiler, add the EQADEBUG DD to specify the location of the application source files. For example:
```
//EQADEBUG DD DSN=USER123.PLI64.SOURCE,DISP=SHR
```
To debug HLASM programs, specify the location of the SYSADATA files by adding the EQAADATA DD name or the EQA_DBG_SYSADATA environment variable. Adding either of those values makes the debugging information available to the debugger. For example:
```
//EQAADATA DD DSN=USER123.HLASM.SYSADATA,DISP=SHR
```
or
```
ENVAR("EQA_DBG_SYSADATA=//'USER123.HLASM.SYSADATA'")
```
z/OS Debugger uses the source code assembled by HLASM to display the source. Thus, that source code needs to be in a cataloged data set accessible to the debugger.

In the CICS® subsystem, you can specify an environment variable using ENVAR (as shown in the previous text, except remove any //) in one of the following ways:

In DTCN, specify the environment variable in the Any other valid Language Environment options field of the z/OS Debugger CICS Control - Menu 2 menu.
In CADP, specify the environment variable in the Other Language Environment Options section.