cliu/ci-server-engineer
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
ci-server-engineer/.claude/skills/system-management/tasks/consistency-check.md
cliu 1c3558c37c Complete phase 1 and build the CI-Eng-Sample project 
Add verified system-management tasks (item read/write, quick load
records, history load, monitoring processes, consistency check, tuning
checks), the importable CI-Eng-Sample project with load/remove scripts,
the unlicensed 1-hour shutdown note, and the sample-project re-test
rule. Close ISS-002/003/004 and log ISS-005..007.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-30 14:01:33 +10:00

1.4 KiB
Raw Blame History

task version source status
Database consistency check (dsschk) R1.03 IM 36K10J10-01EN §4.1.1; practiced on the test system 2026-09-30 verified (check only)

Database consistency check (dsschk)

Needs CI Server running. Checking is read-only; repair (-r) changes the database: back up first and ask the user.

Check

dsschk -e -v > dsschk.out
  • -e extended check: also compares the duplicated datasets on this node (e.g. item definitions copied by ITEM and EQUIPMENT Services). This is the useful check on a single-node system.
  • -v verbose. Output lists DSSP-I-CDS_START / DSSP-I-CDS_END per dataset (228 on the test system) and any problems; the same messages go to %TLS_LOG_PATH%\umhlog.log.
  • -d <dataset> checks one dataset; -n <node> one node.
  • Plain dsschk (no -e) only compares copies between nodes, so on a single node it prints nothing.

Look for warnings or errors: search the output for -W-, -E- or -F-. None = consistent.

Repair (not yet practiced)

From IM 36K10J10 §4.1.1: run dsschk -r until no more inconsistencies are reported (or the same ones repeat), then dsschk -e, then dsschk -e -r (possibly twice). Read the output carefully; some problems need manual work.

ISAM files (not yet practiced)

ismchk <database file> checks one ISAM file; ismkfr [-c] [-r] [-s] [-d] <file> rebuilds key files. Both need the file name (without it: usage: ismchk data_base_name).