cliu/ci-server-engineer
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
ci-server-engineer/.claude/skills/history-management/tasks/history-checks.md
cliu 98035366a7 R1.05 V5 and V6: graphics files and history checks on the test server 
V5 (read-only): Layouts.readme and components identical; JCEF browser
component now loaded from tls\exe\lib\jcef; connectrdp.cmd present;
jwuiutl help identical; AOG_UAC_MethodArg_Call2 added, AOG_OPCUA_Methods
not installed; web trend DataSource.js re-enables the pen checks behind
ISS-041 (probably fixed, not tested).
V6 (read-only): hisdbg 1/20/6 as on R1.03; history and item start/stop
scripts differ only by the extension hooks.
ISS-092, 097, 100, 101 closed; notes on ISS-094, 096.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-09 11:20:38 +11:00

4.3 KiB
Raw Blame History

task: Check storage groups, units and history clients with hisdbg; force a rollover version: R1.05 (first written for R1.03) source: IM 36K10L20-01EN §2.1, §3.1 (4th Edition, Feb. 2026); IM 36K10C40-01EN §5.1 (5th Edition, Feb. 2026); practiced on the test system and CI-Eng-Sample 2026-10-01 status: verified on R1.03 (2026-10-01). R1.05 - the manual sections are unchanged and the hisdbg program is still installed (2026-10-08), but hisdbg was not run on the R1.05 test server (awaiting user verification, ISS-101; steps at the end) R1.05 (V6, 2026-10-09): hisdbg 1/20/6 and the start scripts verified read-only on the R1.05 test server.

History checks (hisdbg)

Interactive; pipe the answers from bash with a timeout. The first answer is the node (blank = local), the last -1 exits. Never send blank lines at the action prompt blindly (a blank repeats the previous action).

printf '\n1\n20\n6\n-1\n' | timeout 20 hisdbg
printf '\n21\n<GROUP>\n3\n\n-1\n' | timeout 20 hisdbg
Option Shows Safe
1 Statistics: group count, logged-in clients, unit starts / stops / rollovers / deletions since start yes
20 All groups: name, node,group number, history type (24 item, 21 alarm, 6 audit, 1058 report, 36 system log, 4 station statistics) yes
21 <name> Group info: path, next unit and file name, opt_type (1 1 Scan/Time, 2 2 Event/Item, 4 4 Aggregation), start, stop, first rollover, interval, life time (all GMT), GMT/LCT rollover, archiving yes
3 (then blank = this group) Units: unit, data, file, start, stop or --- active ---, delete time yes
6 Clients logged in at the history manager yes
11 Unknown history files yes
5 Force rollover of the current group (closes the active unit, starts the next) changes files — with approval
4, 8, 10, 12, 9 Delete unit / group, restore unit, delete unknown files, change schedule no — never without explicit approval

A rollover can also be forced with dssqld -m on HIS_GROUP_DF (NAME,FORCE_ROLLOVER = "<group>",1). A second forced rollover within 2 minutes is refused (DSI-E-ROLLDONE, Rollover already done in the last two minutes; verified 2026-10-01).

History files are in %TLS_ALLUSERS_PATH%\tls\his\ (path shown by option 21): h<node><group><unit><data>.his with base-32 digits, e.g. group 1,54 → h0101m….

What to look for

  • New group but no history: no active unit after loading → restart CI Server (ISS-006).
  • Unit start dates: the first unit of an Event/Item or Aggregation group is dated 2 days back (gap_time); history loaded before the first unit opened after the restart is dropped (see storage-groups.md §5).
  • After a CI Server restart the unit sequence increases (the start script runs hisrep).
  • Delete times = stop time + life time.

Verified (R1.03, 2026-10-01)

45 groups, 30 clients; CIENG_EVENT group 1,54, opt_type 2 2, daily GMT rollover, life 7 days; units 1,1 (created at load) → 3,1 after restart → forced rollover closed 3,1 at 12:05:26 and opened 3,2. CIENG_SCAN10S 1,55 1 1; CIENG_AGG 1,56 4 4 with extra h0101ozzz… files.

R1.05: awaiting user verification (ISS-101)

On the R1.05 test server, in a normal command prompt (read-only options only):

hisdbg

Answer the node prompt with Enter (local), then 1 (statistics), 20 (all groups), 6 (clients), and -1 to exit. Do not choose any other number. Expected: the same menu as R1.03 (-1 … 22), the system groups with history types 21, 6, 1058, 36, 4 (no item group unless the server has one), and clients such as ITH*, ALH, ADTSTO, LGHUMH, RPTMAN. Send the output.

R1.05 test server (V6, 2026-10-09, read-only)

  • hisdbg options 1, 20 and 6 give the same prompts and layout as on R1.03 (menu −1…22): statistics, the group list with the system groups of history types 21 (ALH), 6 (ADT), 1058 (report groups), 36 (SYS_LOG), 4 (STATION_STAT) plus type 24 item groups, and the logged-in clients (DSSSDA*, RPTMAN, EQPIOSTAT, ALH, the ITH processes …). ISS-101 closed.
  • history_start/stop.cmd and item_start/stop.cmd differ from R1.03 only by the call of ?*_history_start.cmd / ?*_item_start.cmd (and the stop variants) extension scripts at the end (change i12719, ISS-121). The processes started are unchanged. ISS-100 closed.