cliu/ci-server-engineer
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
ci-server-engineer/.claude/skills/item-engineering/tasks/block-item.md
cliu dc4d97bb61 Issue review: test ISS-011, ISS-020, ISS-022, ISS-025; unlicensed shutdown after 1 h 10 min 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-01 17:52:25 +10:00

1.3 KiB
Raw Permalink Blame History

task version source status
Block / unblock an item and write to a blocked item R1.03 IM 36K10G10-01EN §3.3, §3.4; practiced with CI-Eng-Sample 2026-09-30 verified

Block / unblock an item

A blocked item is not updated (e.g. during device maintenance). Blocking can be done per item, sub-item or section; sub-items of a blocked item keep working. Changes live behaviour: follow the user's chosen way of working.

Block (BLOCKED 1) or unblock (BLOCKED 0) with an update file and dssqld -m:

@FIELDS
NAME,BLOCKED

@ITEM_DF
"<Section>.<Tag>",1

dssqld -m block.qli -l block.qlo

(Engineering Module: right-click the item or section › Block/Unblock.)

Behaviour (verified on CI-Eng-Sample.TANK1.INFLOW)

  • Blocked: option flag blk appears in itmval -g; the status number is unchanged (stayed 9).
  • itmval -p -n <item> -v <value> on a blocked item is silently ignored (exit code 0, no message, value unchanged); so is dssqld -m on ITEM_VAL.ITEM_VALUE (reports Modified, 0 errors). Check blk in itmval -g before writing (knowledge/issues.md ISS-011). Add -o to overwrite: itmval -p -n <item> -v <value> -o.
  • After unblocking, blk is gone but ublk (option bit 16, updated blocked) remains: the item was written by an application (itmval -o) while it was blocked (IM 36K10C10 §3.5, ISS-001).