- Summary of IM 36K10C10 (Engineering Module - I/O Processes), checked against dssana.sup, itm.sup and the default datasets - New skill authorization: users and authorization groups by quick load - item-engineering: string item limits (1-200, holds length - 1) and the integration granule (itm_int_secs), both tested on CI-Eng-Sample - CI-Eng-Sample: read-only authorization group CIENG_VIEWER - Closed ISS-001 (uoff/ublk option bits), ISS-010, ISS-019; new ISS-018, ISS-020 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.2 KiB
1.2 KiB
| 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
blkappears initmval -g; the status number is unchanged (stayed 9). itmval -p -n <item> -v <value>on a blocked item is silently ignored (no error, value unchanged;knowledge/issues.mdISS-011). Add-oto overwrite:itmval -p -n <item> -v <value> -o.- After unblocking,
blkis gone butublk(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).