Examples of using commands and arguments

Specify the name of the user program and count of simulated PCBs. These arguments can be overridden by the PARM argument on the JCL EXECUTE statement.
```
<RUNNER:PROGRAM MODULE="MYPROG"/>
<RUNNER:PCBS COUNT="200"/>
```
Specify the location of the Associated Test Case exit point programs and that 2 tests are to run. Each of these tests are to use the recorded data starting from the beginning of the file. No program filtering is to occur.
```
<RUNNER:TESTCASE moduleName="*">
   <TEST name="MY TEST 1" entry="TESTCASE1_ENTRY" type="CICS" resetFile="TRUE"/>
   <TEST name="MY TEST 2" entry="TESTCASE2_ENTRY" type="CICS" resetFile="TRUE"/>
</RUNNER:TESTCASE>
```
Specify the location of the Associated Test Case exit point programs and that 2 tests are to run. These tests are to use the recorded data sequentially, without resetting. No program filtering is to occur.
```
<RUNNER:TESTCASE moduleName="*">
   <TEST name="MY TEST 1" entry="TESTCASE1_ENTRY" type="CICS"/>
   <TEST name="MY TEST 2" entry="TESTCASE2_ENTRY" type="CICS"/>
</RUNNER:TESTCASE>
```
Specify the location of the Associated Test Case exit point programs and that 2 tests are to run. Each of these tests are to use the recorded data starting from the beginning of the file. Program filtering is to occur and only data related to MYPROG and any EXEC CICS LINK programs that the filter program calls (either directly or indirectly) are to be used.
```
<RUNNER:TESTCASE moduleName="*">
   <TEST name="MY TEST 1" entry="TESTCASE1_ENTRY" type="CICS" PROGRAM="MYPROG" resetFile="TRUE"/>
   <TEST name="MY TEST 2" entry="TESTCASE2_ENTRY" type="CICS" PROGRAM="MYPROG" resetFile="TRUE"/>
</RUNNER:TESTCASE>
```
Specify the location of the Associated Test Case exit point programs and that 2 tests are to run. Each of these tests are to use the recorded data starting from the beginning of the file. Program filtering is to occur and only data related to MYPROG is to be used. No data related to any EXEC CICS LINK programs will be used, nor will those EXEC CICS LINKs execute the called programs.
```
<RUNNER:TESTCASE moduleName="*">
   <TEST name="MY TEST 1" entry="TESTCASE1_ENTRY" type="CICS" PROGRAM="MYPROG" resetFile="TRUE" STUBCALL="TRUE"/>
   <TEST name="MY TEST 2" entry="TESTCASE2_ENTRY" type="CICS" PROGRAM="MYPROG" resetFile="TRUE" STUBCALL="TRUE"/>
</RUNNER:TESTCASE>
```
Intercept program calls to MYPROG, recording 3 of 4 arguments, skipping over the 2nd argument. The first argument length is 100 bytes, the 3rd is 50 and the 4th is 320.
```
<RUNNER:INTERCEPT module="MYPROG" LENGTHS="100,0,50,320"/>
```
Intercept program calls to MYPROG, recording 3 of 4 arguments, skipping over the 2nd argument, preventing execution of the program. The first argument length is 100 bytes, the 3rd is 50 and the 4th is 320.
```
<RUNNER:INTERCEPT module="MYPROG" LENGTHS="100,0,50,320" STUB="TRUE"/>
```
Intercept program calls to MYPROG1 recording 3 of 4 arguments, skipping over the 2nd argument. The first argument length is 100 bytes, the 3rd is 50 and the 4th is 320. Intercept program calls to MYPROG2, recording 4 of 4 arguments. The first argument length is 80 bytes, the 2nd is 203, the 3rd is 1330 and the 4th is 108.
```
<RUNNER:INTERCEPT module="MYPROG1" LENGTHS="100,0,50,320"/>
<RUNNER:INTERCEPT module="MYPROG2" LENGTHS="80,203,1330,108"/>
```