|
|
|
During startup, servers which have a PLEXQ parameter defined connect to (or JOIN) a SYSPLEX Signaling Services GROUP. Servers which are to connect to a PLEXQ can be started in any order, as PLEXQ servers are peers in functionality.
Exchanges of data and information are routed through the IBM SYSPLEX Signaling Services. Member servers themselves process work or command requests that are made to a PLEXQ directly. Servers in a PLEXQ are polled and the XCOMJOB utility selects the server to receive the work that is being initiated based on the responses received. When scheduling a transfer, consideration is made as to the current workload within each server.
Note: CA XCOM Data Transport PLEXQ services provide functionality similar to the deprecated XCOMPLEX. Transfer workload is balanced based on the current activities in each PLEXQ member server. In a PLEXQ environment, there is no ADMIN server. Requests are made to the PLEXQ group itself, and individual servers interact directly with the XCOMJOB batch utility. This interaction provides superior performance, and reduced resource utilization when performing the same tasks as compared to an XCOMPLEX environment.
| Copyright © 2012 CA. All rights reserved. |
|