This tech doc describes the PLEXQ. It includes a basic summary of how it works and new parameters that were introduced and answers a few basic questions.
What is the PLEXQ and how does it work?
The PLEXQ is the replacement for the XCOMPLEX. It balances workload among its member servers. Transfer requests are sent to PLEXQ, and individual servers submit their own batch transfers. This interaction provides superior performance, and reduced resource utilization when performing the same tasks as compared to an XCOMPLEX environment.
Each PLEXQ Group is given a unique name. All of the servers in the PLEXQ specify the same name for the PLEXQ parameter in the default options/CONFIG member or the EXEC PARM override. During startup, servers which have a PLEXQ parameter defined connect to a SYSPLEX Signaling Services GROUP. Servers which connect to a PLEXQ can be started in any order, as PLEXQ servers are equal in functionality. Transfer requests are sent to the PLEXQ group.
. It supports these transfer requests:
Can I still use the XCOMPLEX?
Yes. The PLEXQ can co-exist with the XCOMPLEX while you are testing the PLEXQ. As of r12.0, the existing XCOMPLEX facility has been deprecated. All new installations should use the new PLEXQ implementation. Existing XCOMPLEX users should migrate to the PLEXQ infrastructure for their XCOMPLEX functionality.
What are the Benefits of using the PLEXQ?
How do I send to the PLEXQ?
How do I monitor the PLEXQ?
Please refer to the CA XCOM for z/OS - 12.0 documentation starting with section Understanding the PLEXQ.
In addition, there is Sample JCL for the PLEXQ feature in