Specifying the target program parameters

As shown in the example above, another difference between IDF and TSO/E TEST is in the debugging of TSO command processors. With TSO/E TEST adding the option CP to the TEST command tells TSO/E TEST that the program being debugged is a TSO command processor. TSO/E TEST then prompts you for the command to be passed to the target in the form of a Command Processor Parameter List (CPPL). Under IDF, the COMMAND option instructs IDF that the parameter string is not a parameter for the target but is a command that should be executed when the target is first started (with the RUN or MRUN commands). If the command being executed is the target program, then you can debug a TSO command which is passed a CPPL. A few examples may help illustrate this:

If you wanted to debug a REXX/TSO function package, for example, RXLOCFN:
- Here is what you do using TSO TEST:
```
    TEST 'SYS1.LINKLIB(REXX)' CP
    EXEC REXTRY
    AT RXLOCFN.RXLOCFN.+0 DEFER
```
- Here is what you do using IDF:
```
    ASMIDF RXLOCFN (COMMAND/EXEC REXTRY
```
  once in IDF,
```
  BREAK (RXLOCFN).
```
- In this example IDF is not passing control to RXLOCFN but to EXEC and the parameter string that is passed as a CPPL is for EXEC.
If you wanted to debug a command processor, INVOKE in this case:
- Here is what you do using TSO TEST:
```
    TEST LOAD(INVOKE) CP
    INVOKE IEBGENER
```
- Here is what you do using IDF:
```
    ASMIDF INVOKE (COMMAND/INVOKE IEBGENER
```
- In this example IDF is passing control to INVOKE and the parameter string that is passed as a CPPL is for INVOKE.