BMC AMI Copy data sharing agent

BMC AMI Copy uses a data sharing agent to communicate information about the Db2 subsystems on a particular z/OS system for the SHRLEVEL CHANGE copy jobs.

The BMC AMI Copy job and the BMC AMI Copy data sharing agents communicate via XCF (the cross-system coupling facility). The data sharing agents must be active at the time that a copy job needs the information from it. The agent can be either a submitted job or a started task. The maximum number of concurrently running copy jobs that an agent can communicate with is 1024.

Related topic

Using-BMC-AMI-Copy-with-the-Db2-data-sharing-capability

Guidelines for establishing agents are:

  • If BMC AMI Copy issued a quiesce, the agent is not required to determine a registration point, but might be required for restart or other functions.
  • An agent is not required on the MVS executing the BMC AMI Copy job. The BMC AMI Copy job can communicate directly with the other agents.

Important

  • We recommend that an agent be established on each MVS with an active Db2.
  • Do not run two agents on the same MVS using the same XCF group name.

You must start the agents if you are using SHRLEVEL CHANGE in a data sharing environment. If BMC AMI Copy requires information from an MVS system that does not have an agent already running, BMC AMI Copy will issue a BMC160670I message to the MVS console alerting the operator that the BMC AMI Copy agent is required. The MVS system is identified in the last four positions of the agent name given in the message. Termination of the agents is optional.

Tip

We recommend that you add the commands to start and stop the BMC AMI Copy agent program to your Db2 initialization and termination procedures.

Note

If you specify RESETMOD NO with SHRLEVEL REFERENCE in a data sharing system, you must start BMC AMI Copy agents because these agents update the CLRSN on remote members.

For example, jobs to perform these tasks, see Sample-job-streams-for-BMC-AMI-Copy-data-sharing-agents.

The installation option, XCFGROUP, is the name to use for the XCF group. BMC AMI Copy generates its own member names within the group. The member name indicates the MVS name on which the agent is running and the BMC AMI Copy version. Another installation option, XCFWAIT, specifies the number of minutes the main copy job waits for an agent to join the group or for a response to a request to an agent. for more information about setting these options, see BMC-AMI-Copy-installation-options-for-data-sharing.

The agent program, ACPXSTC, needs the BMC AMI Copy load library to access the program and options module. ACPXSTC takes the installation options module as an optional parameter (PARM= OPTIONS_MODULE’) and will default to ACP$OPTS if not specified. ACPXSTC’s STEPLIB concatenation must be authorized on the MVS on which the agent is running. ACPXSTC writes status and event information to SYSPRINT to aid you and BMC AMI Copy technical support analysts in analyzing any issues that might occur.

You can have a single ACPXSTC per MVS to service all BMC AMI Copy jobs (such as test and production) even if you are running multiple versions of BMC AMI Copy.

This section contains the following topics:


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*