Dialog Processing & Lock Management

When do dynamic work processes start and stop, and how many does the system add at startup?

Which OS command tests the message-server connection and lists available instances and logon groups?

When you define a lock object in the data dictionary, what gets generated automatically?

What does the _SCOPE parameter control on a lock, and what do values 1, 2, and 3 mean?

How can a single multi-screen transaction end up processed by several different dialog work processes?

What do the four ACID properties mean for an SAP LUW?

Where does the lock table physically exist?

Which parameter sets the lock table size on a modern system, and what replaced the old one?

What two jobs does an instance's dispatcher do for dialog processing, and what happens if it fails?

Which work processes handle dialog steps from active users, what's the minimum, and which parameter sets the count?

When does load balancing assign a user to an application server, and how long do they stay on it?

Because work processes aren't tied to a user session, what must happen to user context at the start and end of each dialog step?

When does an instance actually put a standby dialog work process to use rather than leaving it idle?

How are runtime limits for long-running dialog tasks set by request priority?

An old profile still sets rdisp/max_wprun_time — what does it override, and why must it go on S/4HANA 2020+?

Why separate dialog users into logon groups instead of letting all load types share the same work processes?

If the enqueue server fails, what happens to existing locks and the affected LUWs?

How are lock objects and their generated function modules named, and what must you never do to them?

When two transactions compete for the same record, what does each lock mode S, E, X, and O allow?

How are locks held by update processes preserved across an enqueue server restart?

What does enque/process_location default to, and what does that mean?

Where are lock entries managed, and what's the risk of forcibly removing one?

Before forcibly deleting a user's lock, what four things should you check first?

What OS-level tool can read, monitor, and even simulate enqueues, and how do you see service status?