sap-os-executableslisted

# SAP executables at the OS boundary Three tools, grouped because each one is where the **operating system and the SAP system meet** — and each is therefore a **privilege boundary** worth treating carefully. | Tool | Direction | What it is | |---|---|---| | **`sapevt`** | OS → SAP | Raise a background-processing **event** from outside the system | | **`sapxpg`** | SAP → OS | The **external program controller** that actually runs SM49/SM69 commands | | **`sapinst`** | — | The **installation engine** underneath SWPM | Marks: **[V]** verified, **[G]** cited but not read in full. --- ## 0. These are also the fallback path when the system is jammed Beyond their everyday use, two of these tools matter because they **do not need a free ABAP work process**: | Tool | Out-of-band role | |---|---| | **`sapevt`** | **Trigger work without logging in.** It talks to the message server / background scheduler, not to a dialog work process — so it can release a job when SAP GUI cannot log on | | **`sapinst`** | Irrelevant during an incident — listed here only so the boundary is clear | | **`sapxpg`** | ⚠️ **Not a fallback.** It is *driven by* the ABAP system (SM49/SM69/`SXPG_COMMAND_EXECUTE`), so a jammed ABAP stack means `sapxpg` cannot be invoked either | > **Do not reach for `sapxpg` during a jam.** It is the SAP → OS direction and needs a working work > process to start it. The out-of-band *diagnostic* channel is `sapcontrol` and `dpmon` > (see **`sap-health-triage` §0**); `sapevt`