# Validate an ARM distribution

Identify the exact ARM target before sharing a verification result. A machine's operating system, architecture and execution environment are part of the result; a successful check on one device does not establish support for every ARM device.

Use [installation](https://coordinatordb.com/docs/get-started/setup/install) for the current procedure. If an executable is prepared elsewhere, run the checks on the machine that will actually serve the application.

## Check startup and numeric results

Start the executable with the supplied configuration in an isolated directory. Then run:

```sh
./coordinator client --database data --query "SELECT 2147483647 AS value, 12.5 AS measurement FORMAT csv"
```

Expect `2147483647,12.5`. This small result checks the connection and an application's handling of representative numeric output. Add larger integers, nullable columns and the actual data formats your adapter uses to its own test cases.

## Include file operations

Verify client-side input from a file on the target, especially when the distribution changes directory permissions or launch accounts. Keep native and HTTP results separate. Document whether any compatibility environment was involved and retain exact errors rather than silently omitting failed cases. See [batch inserts](https://coordinatordb.com/docs/concepts/features/operations/insert/bulkinserts) and [format verification](https://coordinatordb.com/docs/resources/develop-contribute/native-protocol/format).