What WinQ is
WinQ is the host-interaction component shipped with the UTS eXpress Enterprise SDK. It lets a developer or power user drive a UTS session programmatically — opening screens, transmitting input, scraping output, and reacting to host events — from scripts and Windows applications.
Where WinQ fits
- Inside an eXpress Enterprise screen — record a script, refine it in WinQ, and replay it as a macro.
- From a standalone Windows process — drive UTS sessions to integrate legacy data with desktop tools.
- From an InfoQuest or eQuate workflow — orchestrate host steps that don't have a native API.
Typical session
- Open a session against a configured route / virtual destination.
- Wait for the host to present a known screen or prompt.
- Transmit fields and function keys; check the response screen.
- Capture data from the screen buffer for downstream processing.
- Close the session cleanly so the gateway frees the station name.
Designing reliable scripts
- Always wait for a known screen state — never send input on a fixed timer.
- Use station-name pools or HGS-generated station names to avoid collisions when scripts run in parallel.
- Bracket destructive actions with read-back checks; the host's last screen tells you whether the transaction committed.
- Centralise connection details in eXpress Connect so script files stay environment-agnostic.
- Log to the transport trace folder during development; switch to the higher-level terminal trace for production support.
Packaging for end users
Distribute scripts together with the eXpress Enterprise configuration that defines the routes they reference. The Administrator's configuration lock keeps end users from re-pointing connections out from under a script.