Connection scope

A connection will either have task scope or address space scope. If the task that creates the connection has its own security environment (TCBSENV is nonzero), the connection has task scope. For a connection with task scope, the task that creates the connection is said to be the connector task. If the connection is created by an SRB, or by a task that does not have its own security environment (TCBSENV is zero), the connection has address space scope. In either case, the home address space of the work unit that creates the connection is said to be the connector address space.

The connector is deemed to be any work unit that has the same security environment as the work unit that created the connection. In all cases, the home address space of the work unit must be the connector address space. In addition:

For a connection with address space scope, the work unit must either be an SRB or it must be a task that does not have its own security environment.
For a connection with task scope, the work unit must be the connector task.

In particular, a connection with address space scope can have multiple work units qualify as the connector. For a connection with task scope, only the connector task qualifies as the connector.

The phrase "requester is the connector" is often used to denote a work unit that is recognized as being the connector. A connection token is always valid for use if the requester is the connector.

The connection scope, in conjunction with the usage classification, determine when a work unit can validly use a connection token. See Use of a connection token.