NODISPLAY

In the following two situations, in which a user can request a specific user interface, that interface might not be available:

Full-screen mode using the Terminal Interface Manager. If the terminal is not available:
- When you record or replay data by using IBM Dynamic Test Engine, the program will run without z/OS® Debugger, and IBM Dynamic Test Engine will run in batch mode.
- Otherwise, the program being debugged terminates with a U4038 abend.
Remote debugger. If the remote debugger is not available:
- When you record or replay data by using IBM Dynamic Test Engine, the program will run without z/OS Debugger, and IBM Dynamic Test Engine will run in batch mode.
- Otherwise, z/OS Debugger will use full-screen mode if the user is running under TSO. If the user is not running under TSO, z/OS Debugger will use batch mode.

In both cases, Write To Operator (WTO) messages also appear.

You can modify these behaviors by specifying the EQAOPTS NODISPLAY command so either:

z/OS Debugger continues processing as if the user immediately entered a QUIT DEBUG command. This modification prevents any forced abend or prevents the debugger from starting.
IBM Dynamic Test Engine will not do any recording or replay.

The following diagram describes the syntax of the NODISPLAY command:

DEFAULT: z/OS Debugger follows the default behavior.
QUITDEBUG: z/OS Debugger displays a message that indicates that z/OS Debugger will quit, and that the user interface could not be used. z/OS Debugger processing continues as if the user entered a QUIT DEBUG command. IBM Dynamic Test Engine will not do any recording or replay.
QUITDTR: IBM Dynamic Test Engine will not do any recording or replay. z/OS Debugger follows the remaining default behavior.

Example

EQAXOPT NODISPLAY,QUITDEBUG