Sending and Receiving APDU Commands

The apdutool reads a script file containing Application Protocol Data Unit commands (APDUs) and sends them to the C-language Java Card RE (or other Java Card RE) or the Java Card WDE. Each APDU is processed and returned to apdutool, which displays both the command and response APDUs on the console. Optionally, apdutool can write this information to a log file.

Running apdutool

The file to invoke apdutool is a shell script (apdutool) on the Solaris or Linux platform, and a batch file (apdutool.bat) on the Microsoft Windows 2000 platform.

TABLE 35 – apdutool Command Line Options
Option	Description
`-h`	Specifies the host name on which the TCP/IP socket port is found. (See the flag `-p`.)
`-help`	Displays online documentation for this command.
`-noatr`	Suppresses outputting an ATR (answer to reset).
`-nobanner`	Suppresses all banner messages.
`-o`	Specifies an output file. If an output file is not specified with the `-o` flag, output defaults to standard output.
`-p`	Specifies a TCP/IP socket port other than the default port (which is 9025).
`-s` serialPort	Specifies the serial port to use for communication, rather than a TCP/IP socket port. For example, serialPort can be `COM1` on a Microsoft Windows 2000 system and `/dev/term/a` on a Solaris system. Currently, this option is not supported on the Linux platform. To use this option, the `javax.comm` package must be installed on your system. For more information on installing this package, see "Prerequisites for Installing the Binary Release". If you enter the name of a serial port that does not exist on your system, `apdutool` will respond by printing the names of available ports.
`-version`	Outputs the version information.
<inputFile`>`	Allows you to specify the input script (or scripts).

apdutool Examples

Directing Output to the Console

This command runs apdutool with the file example.scr as input. Output is sent to the console. The default TCP port (9025) is used.

Directing Output to a File

This command runs apdutool with the file example.scr as input. Output is written to the file example.scr.out.

Using APDU Script Files

An APDU script file is a protocol-independent APDU format containing comments, script file commands, and C-APDUs. Script file commands and C-APDUs are terminated with a semicolon (;). Comments can be of any of the three Java-style comment formats (//, /*, or /**).

APDUs are represented by decimal, hex or octal digits, UTF-8 quoted literals or UTF-8 quoted strings. C-APDUs may extend across multiple lines.

<CLA> :: ISO 7816-4 class byte.
<INS> :: ISO 7816-4 instruction byte.
<P1> :: ISO 7816-4 P1 parameter byte.
<P2> :: ISO 7816-4 P2 parameter byte.
<LC> :: ISO 7816-4 input byte count.
<byte 0> ... <byte LC-1> :: input data bytes.
<LE> :: ISO 7816- 4 expected output length byte. 0 implies 256.

TABLE 36 – Supported APDU Script File Commands
Command	Description
`delay <`Integer`>;`	Pauses execution of the script for the number of milliseconds specified by `<`Integer`>`.
`echo "`string`";`	Echoes the quoted string to the output file. The leading and trailing quote characters are removed.
`output off;`	Suppresses printing of the output.
`output on;`	Restores printing of the output.
`powerdown;`	Sends a powerdown command to the reader.
`powerup;`	Sends a power up command to the reader. A powerup command must be executed prior to sending any C-APDUs to the reader.

Chapter 13