Components (z/OS)

A component is either a broker or a User Name Server.

A broker processes messages and a User Name Server extracts information from a security product and makes it available to brokers and the workbench. A broker consists of a controller and the component (broker or User Name Server). When the controller address space is started, the component is started automatically. This behavior can be changed by an optional start parameter in the started task. You only need a User Name Server if you are using Publish/Subscribe security. This User Name Server can exist anywhere in the network, including z/OS.

Each component has its own runtime environment in UNIX System Services and needs its own WebSphere MQ queue manager, although a broker and User Name Server can share a single queue manager. A broker component also needs access to DB2. Refer to Contents of Customization Input File for further details.

Related concepts
z/OS customization
Component directory
Component name
Related reference
Contents of Customization Input File