Skip to content
Coordinator DB
View as Markdown
View as Markdown

Validate an s390x distribution ​

Validate the executable and its application-facing results on the intended s390x environment. Record the operating system, target machine and whether the check uses emulation. Treat this as evidence for that environment rather than a guarantee for every system with the same architecture name.

Follow the current installation procedure, then start the executable with an isolated database and the supplied configuration files.

Check values before byte-level output ​

sh
./coordinator client --database data --query "SELECT 65536 AS value, 'sample' AS label FORMAT csv"

Expect 65536,"sample". This establishes a readable baseline before testing the binary formats used by an integration.

Verify the adapter's format contract ​

For binary output, decode with a reader for the selected documented format. Compare typed values and nulls with the text baseline. Do not reinterpret bytes using the application's host memory layout or assume that native TCP framing is the same as a row format.

Keep any byte-for-byte fixture tied to an explicit format and schema. Include negative cases for truncated input in the integration's tests and record whether the server accepted or rejected the request. See native result formats.