VSAM files that are managed by CA-L-Serv are managed by a single CA-L-Serv.

Each VSAM file is accessed through CA-L-Serv or directly by TPX, but not both.

Implement a security package to restrict access to the VSAM files.

Ensure that the LSERVDSN, SYSVSAM, and SYSDSN ENQs are propagated as necessary.

CA-L-Serv startup parameters match those in sample CA-L-Serv startup members, after any required customization for your site.

The CA-L-Serv that is managing the product files is defined as host if you are cross-system sharing or local if you are not.

All CA-L-Servs defined as remote have the same z/OS subsystem name as the host CA-L-Serv

The CA-L-Serv file server is active on each CA-L-Serv system.

If your site is performing file sharing with more than one CA-L-Serv, the CA-L-Serv communications server is active on each CA-L-Serv system.

Each CA-L-Serv communication server has the correct VTAM applid.

All VSAM files that are managed by CA-L-Serv have VSAM sharing options of (1,3) or (2,3).

An ADDFILE command is present for each file that CA-L-Serv is managing.

Each file that CA-L-Serv is managing has a DD statement specifying DISP=OLD in the startup procedure of the local or host CA-L-Serv.

The CA-L-Serv subsystem name specified in the startup procedure matches that of the CA-L-Serv system with which the product must communicate.

The ddname prefix specified in the startup procedure matches that used in the CA-L-Serv ADDFILE commands.

A DD statement is present for each VSAM file that is to be accessed directly by TPX

.The Intercommunications System Name (ICSN), which identifies each component to CA-L-Serv, is correct.