CA XCOM Data Transport for z/OS r11.6 Introduces the PLEXQ.

Document ID:  TEC582929
Last Modified Date:  07/06/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA XCOM Data Transport

Releases

  • CA XCOM Data Transport:Release:11.6
  • CA XCOM Data Transport:Release:12.0

Components

  • CA XCOM Data Transport for z/OS:XCMVS
Introduction:

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.

Question:

What is the PLEXQ and how does it work?

Answer:

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:

  • SCHEDULE
  • INQUIRE
  • HISTORY
  • OPER
  • RECOVER

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?

  • It is easier to implement and use than the XCOMPLEX
  • No complicated configuration as was needed with the XCOMPLEX
  • An ADMIN server is no longer needed
  • It uses less CPU and memory than XCOMPLEX
  • It enables XCOMJOB to communicate directly with PLEXQ-enabled servers
  • The number of member servers is limited only by SYSPLEX resources

How do I send to the PLEXQ?

  • For Batch Jobs:

    • Specify the STCPLEXQ parameter in the EXEC PARM for XCOMJOB instead of using the STCAPPL or STCIP/STCPORT parameters.
    • Specify PLQ for Protocol
  • For ISPF:

    • Specify the PLEXQ Group name for Local Server
    • Specify PLQ for Protocol

How do I monitor the PLEXQ?

  • STAT Command 

    F XCOM,STAT 

    Shows the task levels for servers in the PLEXQ group. The PLEXQ STAT command must be entered from a server in the PLEXQ group.

  • XSHOW Command 

    F XCOM,XSHOW 

    Displays locally initiated transfers for servers in the PLEXQ group. The PLEXQ STAT command must be entered from a server in the PLEXQ group.
  • XRSHOW Command 

    F XCOM,XRSHOW 

    Displays locally remotely transfers for servers in the PLEXQ group. The PLEXQ STAT command must be entered from a server in the PLEXQ group.

 

 

Additional Information:

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 CAI.CBXGJCL(XCOMJOQS)

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >