Preferences for the Dynamic Test Runner

Use the ZUnit (z/OS Automated Unit Testing Framework) preference page and the CICS Recording Service preference page set options for the Dynamic Test Runner.

ZUnit (z/OS Automated Unit Testing Framework) preferences

Capture file I/O: Enable capturing of file I/O transactions for the recording service. This option is enabled by default. If you want to use Setting file test type in Test Case Editor for SuperC Compare Utility, you need to disable this option. This option applies only to COBOL.
Note: If you select this option:
  • The Generate separate program for file I/O option is disabled. If you have existing test cases containing file I/O created by a previous version of the product, you must disable this option, or clean up the existing test case.
  • If you are using Developer for z/OS® 15.0.5 or earlier server versions, you must manually specify the customized LLEP in Batch Recording Service > Dynamic Test Runner libraries. For more information, see Extending Language Environment® and Setup for batch.

Batch Recording Service preferences

Dynamic Test Runner libraries: The Dynamic Test Runner libraries for batch recording service is configured in the host environment variable settings by default. ZUnit automatically retrieve the Dynamic Test Runner libraries when recording batch program if the environment variables have been defined on the host. If you are using Developer for z/OS 15.0.5 or earlier server versions, or if the environment variables have not been set in host settings, since the libraries are not configured by default, you must uncheck this option and specify the libraries manually in the Libraries field below.

Libraries: If you are using Developer for z/OS 15.0.5 or earlier server versions, since the libraries are not configured in host settings by default, you must specify the libraries manually in this field. The value should point to <HLQ>.SBZULOAD, <HLQ>.SBZURESL, and <HLQ>.SBZULLEP. Contact your system programmer for the actual library names.

Procedure library (PROCLIB): You can optionally specify the list of PDS names where catalog procedures are defined. Multiple PDS names should be separated by spaces. When ZUnit generates a JCL to record a batch application from an original JCL, it tries to resolve catalog procedures and include files
  1. by the JCLLIB statement in the original JCL,
  2. and additionally by the PDS names defined in this option.

CICS Recording Service preferences

These preferences define the recording service to use for recording test data.

Connection timeout (ms): Specify the timeout for connecting to the recorder. The default value is 20000 milliseconds, which is 20 seconds.

Read timeout (ms): Specify the timeout for retrieving data from the recorder. The default value is 20000 milliseconds, which is 20 seconds.

URL and credentials: A list of specified URLs that you can use when starting a recording process. Click the buttons beside this table to add, edit, or remove a URL.

To obtain this information, consult the system programmer who completed Dynamic Test Runner host customization at your site. For more information about defining the recording service for the Dynamic Test Runner, see the IBM® z/OS Dynamic Test Runner Host Configuration Guide, Support for CICS® applications.

Playback file preferences

These preferences define the default high-level qualifier to use for the playback file.

High-level qualifier: The high-level qualifiers for the playback file. The playback file is a sequential data set. The default qualifier is <HLQ>.ZUNIT.PB. <HLQ> is replaced with the HLQ of the referenced remote resource, for example, a remote test target source file, or a load module. In the case of an MVS™ subproject, <HLQ> is replaced by the value set in Info > Subproject > High-level qualifier. When no remote resources are involved, <HLQ> is replaced with your user ID. If you want to use your user ID as the prefix in all situations, use <USERID> instead of <HLQ> on the preferences setting page. When you record test data for a program, this high-level qualifier is concatenated with the name of the program being tested. If you are testing a program named ANAGRAM, for example, the playback file is named USERID.ZUNIT.PB.ANAGRAM.

Space units: The type of DASD storage units to allocate for the playback file. Select TRACKS, BLOCKS, or CYLINDERS.

Primary quantity: The number of units to allocate for the primary quantity of space units.

Secondary quantity: The number of units to allocate for the secondary quantity of space units.