EQAOPTS commands that have equivalent z/OS Debugger commands

Some EQAOPTS commands have equivalent z/OS® Debugger commands. Table 1 shows a few examples.

Table 1. Examples of EQAOPTS commands and their equivalent z/OS Debugger commands
EQAOPTS command	z/OS Debugger command
DEFAULTVIEW	`SET DEFAULTVIEW`
DYNDEBUG	`SET DYNDEBUG`
EXPLICITDEBUG	`SET EXPLICITDEBUG`
NAMES	`NAMES`

For these commands, specifying them as EQAOPTS commands or z/OS Debugger commands produces the same action. The timing (when these commands take effect) differs between EQAOPTS commands and z/OS Debugger commands.

z/OS Debugger processes z/OS Debugger commands after it processes the initial load module and creates the compile units contained in the initial load modules. z/OS Debugger processes EQAOPTS commands during z/OS Debugger initialization, prior to processing the initial load module. This means that when z/OS Debugger processes the initial load module, z/OS Debugger commands like NAMES are not in effect but the corresponding EQAOPTS commands are in effect and are applied to the initial load module.

EQAOPTS commands like DEFAULTVIEW provide a way of specifying a site- or group-wide default for the corresponding z/OS Debugger command. However, a better way to specify a site- or group-wide default for these types of commands is by putting the z/OS Debugger command in a global preferences file.