This read-write INTEGER (force(1)/noForce(2)) controls, per its source description, whether a potentially disruptive command should proceed despite warnings that it could adversely affect active connections; a command issued with noForce (or the object absent) that would be hazardous returns a warning instead of executing, requiring the admin to explicitly resubmit with force to override it. Admins use force only after deliberately deciding the disruption (e.g., dropped connections from a reset) is acceptable. For example, an admin performing an emergency reset on a card serving live connections would need to set this to force(1) after the initial noForce attempt returned a warning about active sessions.