|
|
|
When the CA-L-Serv started task that runs the file server also runs the communications server, the file server communicates with other systems through the communications server in its own address space.
When a CA-L-Serv started task does not provide its own communications services, you must identify the started task that provides these services to the file server. You can do this by including extra information on the ATTACH command that starts the file server, as shown here:
ATTACH FILESERVER SERVERTYPE(type) COMMSERVERSSN(ssname)
The COMMSERVERSSN(ssname) parameter provides the subsystem name for the CA-L-Serv started task that provides communications services.
For example, suppose you are running a test copy and a production copy of the file server and you want both copies to use the communications server running in the LSVP address space.
To do this, issue the following command to the test copy of CA-L-Serv:
ATTACH FILESERVER SERVERTYPE(type) COMMSERVERSSN(LSVP)
Sharing a Communications Server between a number of CA-L-Serv regions is particularly useful to limit the number of VTAM definitions or XCF groups in large complexes where many systems run multiple copies of CA-L-Serv.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |