EQA_STARTUP_KEY

The EQA_STARTUP_KEY is an environment variable. The format for specifying this environment variable is as follows: ENVAR("EQA_STARTUP_KEY=ACTION").

The values for the ACTION parameter are as follows:

CC
An unattended z/OS® Debugger Code Coverage session is requested. In this case, an interactive debug session is not launched.
DCC
A combined z/OS Debugger session and Code Coverage session is requested. This allows the developer to have a debug session and concurrently create code coverage data. If you use this option and change the program logic path by using the GOTO and JUMPTO commands, the observation is flagged indicating that the debug override is ON.

z/OS Debugger uses the EQA_STARTUP_KEY environment variable and TEST runtime options to determine whether to activate an interactive debug session and code coverage session or not. The following table shows different combinations of the environment variable and TEST runtime options, and the resultant session activation.

Note: There are two different code coverage sessions: z/OS Debugger code coverage session and IBM® Developer for z/OS code coverage session. z/OS Debugger handles the z/OS Debugger code coverage session. IBM Developer for z/OS handles the IBM Developer for z/OS code coverage session. The code coverage data format and presentation are different in the two sessions.
EQA_STARTUP_KEY z/OS Debugger session device z/OS Debugger interactive debug session z/OS Debugger code coverage session IBM Developer for z/OS code coverage session
CC MFI (no 3270 terminal available1) No Yes No
CC TCPIP/DBMDT No No Yes
DCC MFI/VTAM (target 3270 terminal provided) Yes Yes No
DCC TCPIP/DBMDT Yes Yes No
Notes:
  1. For CICS, the "no 3270 terminal available" restriction is bypassed if you follow the example in Generating code coverage for CICS transactions.

Examples:

  • '/TEST(ALL,*,PROMPT,MFI:*),ENVAR("EQA_STARTUP_KEY=CC")'
    • Using DT MFI, and specifying CC.
    • Code Coverage observations are collected.
  • '/TEST(ALL,*,PROMPT,VTAM%userid:*),ENVAR("EQA_STARTUP_KEY=DCC")'
    • Using z/OS Debugger MFI with the Terminal Interface Manager, and specifying DCC.
    • An interactive debug session is started and Code Coverage observations are collected while it is running.
  • '/TEST(ALL,*,PROMPT,TCPIP&nn.nn.nn.nn%8001:*),ENVAR("EQA_STARTUP_KEY=DCC")'
    • Using z/OS Debugger TCPIP with IBM Developer for z/OS, and specifying DCC.
    • An interactive debug session is started, and Code Coverage observations are collected while the debug session is running.