Unit Test tab

Select the JCL to be used for executing the Virtualized Tests (Unit Tests) and specify the load libraries when using the dynamic JCL skeletons.

Execution JCL location

gives you a choice which Execution JCL to use for this test execution:

Use the JCL skeleton configured for the selected host

Select this option to use the dynamic JCL skeleton defined for the selected Environment Connection as defined in the Repository or the TotalTestConfiguration Project project when Use Repository server is not selected.

Use JCL defined in the project

(Default for Virtualized Test scenarios created prior to Release 20.04.01) Select the JCL to use for the test execution from the JCL file list. The list includes all JCL files stored for the current Unit Test project. See also Create JCL Template for more information.
Make sure your steplib DD points at your site's Enterprise Common Components (ECC) Release 17.02 or newer load library (CPWR.MLCXnnn.SLCXLOAD), for example hlq.CPWR.MLCX170.SLCXLOAD. For more details, see the Enterprise Common Components Installation and Configuration Guide for Release 17.02 or newer. The variable ${TOTALTEST_JOBCARD} in the JCL will load the default jobcard specified in Window > Preferences > BMC > .

Use JCL based on the Runner.jcl for tests that do not use live Db2 or live IMS BMP.

If your test case includes live DB2, use JCL based on the RunnerDB2.jcl template.
If your test case includes live IMS BMP, use JCL based on the RunnerBmp.jcl template.
If your test case includes both live DB2 and live IMS BMP, use JCL based on the RunnerBmpDB2.jcl template.

Important

When using the dynamic JCL skeleton, then DEBUG(ON) is set automatically when the Logging level is set to DEBUG, TRACE or ALL. When using hardcoded JCL, it will use what you coded in that. That can be changed if you replace the DEBUG(ON) or DEBUG(OFF) in their JCL with DEBUG(${runtime.usedebug}).

Load Libraries

Specify the TTTRunner load libraries for Virtualized Test (Unit Test) elements. If the test cases were generated from a Code Debug session (starting with Release 20.04.01), this field is prefilled with the load libraries collected during test case generation.

Important

The Execution Options in the Project Properties (Use Stubs, Delete Temporary Files, and Test Aids) only apply when using the classic Test Run dialog. If you don't want to use stubs, remove selected or all stubs from Selected column in the Stubs tab in the test scenario editor (see Stubs). Logging level ALL will not delete temporary files.