Install multiple instances of zDC/zRemote
If a single zRemote module handles all the communication between several zDC subsystems, it's at risk of overload. The number and type of transactions to be processed thereby determine how many zDC subsystems a single zRemote module can handle.
According to our Sizing guidelines, we recommend that you install a designated zRemote for every zDC subsystem with an extra-large transaction volume.
Additional zRemote module
Download and install an additional zRemote module.
To make sure that the new
oneagentzinstance is up and listening, issue a
netstat -ap |grep oneagentz tcp 0 0 0.0.0.0:8898 0.0.0.0:* LISTEN 8322/oneagentz
Additional zDC subsystem
On your z/OS LPAR, copy the current zDC startup JCL SYSIN member
ZDCSYSINto another name (for example,
Edit the new JCL SYSIN member by changing the following parameters:
name=<agentname>to a new zLocal reference.
zremoteagent=host:portto the new host and port of the new zRemote module.
DEFAULT(NO). The first zDC is designated as the default.
SUBSYSTEM_ID(xxxx)to another value. CICS will use this name to connect to the new zDC.
Make a copy of the current zDC Startup PROC and change the SYSIN to point to the new SYSIN member.
Start the new zDC and check the output to make sure that it correctly connects to the new zRemote.
Configure CICS code module to target the new zDC subsystem
Create a SIT override for some CICS regions to target the new zDC subsystem:bash
The value must match the ID from the new JCL SYSIN member.
To test the CICS region and check communication with the new zDC, issue a