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 83af63ab53 R1.05 re-check batch 2: graphics, history, portal, system-management, items 
Full manual diffs (C50, R30, C60, L20, C40, L35, R10, R20, J10, L30, L50,
P30, G10, C10) and read-only checks on the shared R1.05 test server where
the permission system allowed them. Skills and summaries moved to R1.05.
Issues ISS-092..129 (gaps 104-107, 114-115, 130-131 unused); ISS-074
closed (manual and software agree), ISS-091 corrected by ISS-119.
version-differences: unlisted manual changes and installed-only changes.
r105-verification: V5-V9 and new not-tested rows.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-08 19:29:15 +11:00

1.7 KiB
Raw Blame History

task version source status
Database consistency check (dsschk) R1.05 (first written for R1.03) IM 36K10J10-01EN §4.1.1 (5th ed., Feb. 2026); IM 36K10L50-01EN §5; practiced on the test system 2026-09-30 (R1.03) verified (check only) on R1.03 (2026-09-30) and on the R1.05 test server (2026-10-08, `dsschk -e -v`, usage text unchanged); repair not practiced

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 R1.03 test system, 231 on the R1.05 test server) 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 (R1.05 test server, 2026-10-08: none).

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).