How are CA XCOM for z/OS destination members enabled?

Document ID : KB000025351
Last Modified Date : 14/02/2018
Show Technical Document Details

Question: 

The members found in the XCOMCNTL library, how are they loaded or enabled into XCOM storage? Can this be done automatically? I noticed some members in effect by issuing /F XCOM,LIST, GROUP/LU, and wondered how they were enabled.

Answer: 

There are two ways destination members may be loaded

  • At startup of the CA XCOM task.

  • With a modify command.
At Startup

In the default table or config member, there is a parameter START. This specifies the name of a special entry in the ...XCOMCNTL (control) dataset which contains a list of the members that should be enabled when the task comes up. For example,

 START=XCOMSTRT,

This is the default value.  You can specify a different name with this parameter.

The ...XCOMCNTL(XCOMSTRT) member looks like this (the comment is optional):

 *             START MEMBER FOR SERVERS
 SERVER2
 SERVER3
 ...

As you can see, it is just a list of the names of destination members.

You can see this happening at the beginning of the XCOMLOG:

 XCOMM0004I               START=XCOMSTRT

Then followed later by the list of destination members being enabled

 XCOMCNTL         XCOMM0559I SERVER2  ENABLED  SUCCESSFULLY
 XCOMCNTL         XCOMM0559I SERVER3  ENABLED  SUCCESSFULLY
 ...
With a MODIFY Command

Individual destination members may be enabled with the modify command:
/F XCOM,ENA,MEMBERNAME

where XCOM is the name used to start the CA XCOM server. This setting lasts until the server is brought down.

Individual destination members may be disabled (removed) with the modify command:
/F XCOM,DIS,MEMBERNAME

This setting lasts until the server is brought down. 

Additional Information:

For additional information and options, please refer to the XCOM z/OS 12.0 documentation - Section How to Enable and Disable a Destination Member.