---
name: system-management
description: >-
  CI Server R1.03 system management and command-line tools. Use when the user wants
  to stop CI Server, export or
  import dataset contents (dssqld), read or write item values (itmval), load or import history,
  check database consistency (dsschk), monitor processes/CPU/disk/network, back up or migrate
  a system, tune or debug CI Server, or plan a system layout (standalone, separate portal, HAC,
  host-to-host, enterprise) or time synchronization. Source IM 36K10J10-01EN.
---

# System management (R1.03)

Background for this area: `knowledge/manuals/IM36K10J10-01EN.md`. Known issues:
`knowledge/manuals/IM36K01A50-01EN.md`.

Rules for every task:
- Run the `system-check` skill first (version must be R1.03).
- CI Server tools live in `%TLS_ROOT_PATH%\tls\exe` (on `PATH`). Run them in a scratch folder,
  because they write output and listing files to the current directory.
- Starting/stopping CI Server and anything that writes to the system needs an elevated
  (administrator) session and, in this conversation, the user's chosen way of working
  (direct vs prepare only).

| Task | File | Status |
|---|---|---|
| Export dataset contents / dump the data dictionary | `tasks/export-dataset.md` | verified |