Providing EQAOPTS commands at run time

You can provide EQAOPTS commands to z/OS® Debugger at run time. You must save the commands in a data set with 80-byte, fixed-length records. The following list describes the methods of specifying this data set to z/OS Debugger:

  • In CICS®, include the EQAOPTS commands through DTCN.
  • In UNIX System Services, specify the name of the data set containing the EQAOPTS commands through the EQA_OPTS_DSN environment variable.
  • In IMS and Db2®, specify the name of the data set containing the EQAOPTS commands in the Language Environment® user exit or debug profile by using DTU option 6 or B, Terminal Interface Manager, or the z/OS Debugger Profiles view in the Eclipse IDE or the z/OS Debugger Profiles view provided with Z Open Debug.
  • In other environments, specify the name of the data set containing the commands through the EQAOPTS DD statement.

The following example shows what the data set might contain:

EQAXOPT MDBG,YES
EQAXOPT NODISPLAY,QUITDEBUG
EQAXOPT NAMES,EXCLUDE,LOADMOD,USERMOD1
EQAXOPT NAMES,EXCLUDE,LOADMOD,USERMOD7
EQAXOPT END

The instructions in Creating EQAOPTS load module contain examples with specifications for CSECT, AMODE, RMODE, and END (without EQAXOPTS) statements. Do not include these specifications if you provide EQAOPTS command at run time.