cliu f24e617a70 Add phase 5 equipment and ITEM Service summaries

- Summaries of IM 36K10L40 (EQUIPMENT utilities), L41 (EQUIPMENT
  configuration: lines, stations, conversion types, Modbus master/slave,
  driver table), L35 (ITH) and L36 (ITM), checked against the installed
  start scripts, setup files and datasets
- tuning-checks: read-only itmdbg / eqpdbg via piped answers
- New ISS-021 (STATION_STAT empty), ISS-022 (itmval -f crashes),
  ISS-023 (install differs from ITEM manuals, closed); ISS-006 updated

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-09-30 17:15:14 +10:00

2.6 KiB

Raw Blame History

task	version	source	status
Tuning checks (read-only)	R1.03	IM 36K10J10-01EN §5.5.1; practiced on the test system 2026-09-30	verified (read-only checks)

Tuning checks (read-only)

Checks whether CI Server needs tuning. Nothing here changes the system. Changing the limits means editing setup files and restarting CI Server: ask the user first.

Limits in setup files (`%TLS_ROOT_PATH%\tls\sup\`)

Read the active (non-!) lines:

File	Keyword	Meaning	Test system
`dur.sup`	`dur_max_proc`	Max processes (default 250)	250
`dur.sup`	`pool_kbytes`	DUR message pool	250000
`itm.sup`	`pool_kbytes`	Item common memory pool	650000
`database_start.cmd` (`tls\com`)	`-u` / `-f`	Max database users (default 2K) / files (default 1,200)	not checked

Live values: automatic health snapshots

CI Server's system monitor (smdmon) writes debugger snapshots about every 10 minutes to %TLS_LOG_PATH%\smd_<node>_<debugger>_*.log (e.g. smd_UNLICENCED_LOW_itmdbg_all.log). Read the newest entries:

File	What to check	Target (IM 36K10J10 §5.5.1)
`*_itmdbg_all.log`	`common size` / `free size`	Free above 10 %, usage below 75 %
`*_smdsnp_process.log`	Per process: `queue_size`, `queue_used`, `queue_high`	No requests waiting (`queue_used` 0); enlarge a queue that stays in use
`*_ismdbg_all.log`	`Total number of lock collisions`, users, files	Collisions not rising above 250/s; entries below 80 % of max users
`*_smdsnp_process.log`	Number of processes	Well below `dur_max_proc`

Test system (2026-09-30): common memory 665.6 MB, free 665.3 MB; queues empty; 3 lock collisions in total.

Live values from the interactive debuggers (read-only)

The debuggers ask for a code; pipe the answers in and end with -1 (exit). Use only the read-only codes listed in the manual summaries:

Command	Shows	Reference
`printf '2\n-1\n' \| itmdbg`	item common size/free, number of items, integration granule, update counters	`knowledge/manuals/IM36K10L36-01EN.md` §4
`printf '1\n-1\n' \| eqpdbg 0 <EQP process>`	equipment manager: lines attached, scan tick, slave count, line load %	`knowledge/manuals/IM36K10L40-01EN.md` §3

Verified 2026-09-30 (bash). Other codes change the running system (delete items, unlock, update scan status); do not use them without the user's approval.

Not yet practiced

Debug launchers (jwuipoi_debug, jhmiset_debug, …), other debuggers (opcdbg, ithdbg, …), and per-process debug settings; see knowledge/manuals/IM36K10J10-01EN.md §5.5.2.

2.6 KiB Raw Blame History