---
task: BUS Service utilities - process checks, stopping single processes, message tools, adaptive queues
version: R1.03
source: IM 36K10L30-01EN §1, §5, §6, §10, §14; checked on the test system 2026-10-01
status: verified (durwfp, setup file checks, umhman, umhmsg, umhtestprog)
---

# BUS Service utilities

Background: `knowledge/manuals/IM36K10L30-01EN.md`.

## Is a CI Server process attached?

`durwfp -p <DUR name> -t 0` → exit code **0** = attached (running), **1** = not. Without
`-t 0` it waits up to 60 s for the process to appear; `-e` waits for it to go away. Verified:
`umh`, `opcman`, `durm_1` → 0; unknown name → 1. Bash: `durwfp -p opcman -t 0; echo $?`.
DUR names are those given with `-n` (e.g. `OPXCIENG`, `EQPCIENG`, `opxuas`).

## Stop or kill one process (only with the user's approval)

`durstp -m -p <name>` sends a stop message (clean stop); `durstp -m -k -t 10 -p <name>` stops,
then kills after 10 s. `*` wildcards stop many processes (`-p alm\*`). Never `durstp -k -p \*`
(kills `durtim` and leaves DUR memory locked). Restart a process by hand with
`<exe> -n <name>` from `tls\exe` or by restarting CI Server.

## Messages

- Message log: `%TLS_LOG_PATH%\umhlog.log` (`--> From: <PROCESS> (<node>) on <time>`, then
  `FAC-S-CODE, text` lines). `UMH Message Text Error: Message number <hex> (…)` = the text
  could not be formatted (e.g. `%` in a PRINT text, ISS-025).
- `umhman` (hex code → text): answers can be piped, e.g. `printf '8010008

' | umhman` →
  `DUR-W-NO_MSG_FND, No selected message found`; parameters in the text stay empty.
- `umhmsg <hex> [<var> <value>]…` logs that message from a script: it prints nothing; the
  message appears in `umhlog.log` from process `UMHMSG_<pid>`.
- `umhtestprog` runs its self-test (`TESTING UMH MESSAGES`, `TESTING ILLEGAL CODES`).
- On an **unlicensed** node these tools crash or stop with `license expired` once the licence
  time is nearly used up, while `dssqld`/`itmval` still work; restart CI Server (ISS-030).

## Adaptive queues (read-only check)

`tls\sup\dur.sup`, tab *Adaptive queues*: `ADAPTIVE_QUEUE_SETS = <process>, <percent>`
(wildcard `*` allowed, max 40 %). Installed: `ALM` 10, `ALH` 10, `WFLGDI` 20, `WFLCDI`,
`WFLIDI`, `WFLADI`, `ITHEIX`, `ITHSER` 2, `DSSSDA*`, `DSSEVT*`, `OPCEXE` 1. Add entries for
new busy processes (extra executors, equipment managers, custom processes); `OPCEXE` without
`*` may not cover the installed `OPCEXE1`…`4` (ISS-026). Changing `dur.sup` needs admin and a
restart (skill `portal-setup`). Queue use per process: health snapshots
(`tuning-checks.md`) or the performance monitor (*Minimum/Maximum/Current KB*, high queue
100 % = the queue had to grow → raise its size).

## Node links (MDUR)

`tls\sup\durm_<line>_udp.sup` and `tls\com\durm_start.cmd`; single-node installs still run
`durm_1` (`durm_1_udp.sup`: line 1, quality 500, port 17001). Multi-node set-up is in the L30
summary §2; not practiced (one node).