The implementation of CA SOLVE:FTS in a network usually implies the movement of bulk data across a telecommunications network rather than between channel-linked CPUs only. The bandwidth available between the various sites determine the speed that files are transmitted. Capacity planning involves considerations of available bandwidth, operational requirements for multiple concurrent transmissions, and the effect of high-volume batch data on existing network traffic.
When a transmission is in progress, CA SOLVE:FTS does not attempt to pace the rate of data transfer. For example, if a transmission is occurring across a T1 link, in the absence of other network traffic, CA SOLVE:FTS drives the link at a very high percentage of its capacity.
Because such a network link is likely to carry interactive traffic in addition to CA SOLVE:FTS traffic, it is important to prevent CA SOLVE:FTS traffic from interfering with interactive response times. Data flow control in the network is a function of the network software being used and various techniques are available to reduce the priority and impact of high volume batch traffic passing through the network.
When using VTAM as the underlying transport mechanism, you can allocate a low transmission priority to CA SOLVE:FTS INMC sessions by using an appropriate Class of Service table entry. Alternatively, you can use VPACING on the APPL statements to pace the traffic, although this can lead to severe degradation in performance.