Distribution Lists
You can use the Platform Server batch client to specify a list of remote nodes to which you want to send a dataset.
The list capability works similarly to the way the remote nodes are defined. Each remote system list is defined in the
CONFIG member the same way that an individual remote node is defined. A separate member must be created to include a list of remote systems.
By defining a list, a user of the batch client can reference it and the transfer can be sent to all of the remote systems that are included in the list.
To define a list, you can use the following parameter. This parameter specifies that this member is a list and not an individual node.
TYPE=LIST
You can specify up to 2048
NODE,
IPADDR or
IPNAME definitions. You can also override
IPPORT at any time in the list by specifying the
IPPORT statement.
See the following list definition for your reference:
TYPE=LIST NODE=CHICAGO1,NEWYORK2,DENVER4, *Points to node definition.* IPADDR=192.192.1.200,192.192.1.201,192.192.1.202 *Uses GLOBAL TCPIPPORT* IPNAME=acct.companya.com,payroll.companya.com, *Uses GLOBAL TCPIPPORT* IPPORT=2500 IPADDR=192.200.1.200,192.200.1.201,192.200.1.202 *Uses 2500 as port* IPNAME=acct.companyb.com,payroll.companyb.com, *Uses 2500 as port* IPPORT=46464 IPADDR=192.220.1.200,192.220.1.201,192.220.1.202 *Uses 46464 as port* IPNAME=acct.companyc.com,payroll.companyc.com, *Uses 46464 as port* NODE=BOSTON,WASHDC,ORLANDO *Points to node definition*
See the following sample of a remote nodes list in member
DISTRIB:
******************************************************************* * THIS IS WHERE YOU WILL SPECIFY A LIST OF NODES THAT DATA WILL * * BE DISTRIBUTED TO. * ******************************************************************* TYPE=LIST NODE=NTLU001,WIN95LU7 NODE=NTLU002 IPADDR=192.192.1.200,192.192.1.201,192.192.1.202 IPNAME=acct.companya.com,payroll.companya.com IPPORT=2500 IPADDR=192.200.1.200,192.200.1.201,192.200.1.202 IPNAME=acct.companyb.com,payroll.companyb.com