For basic information about OMVS and USS Files with XCOM, please refer to these sections in the CA XCOM Data Transport for z/OS - 12.0
documentation online. OMVS Requirements
Ensure the value set for the BPX PARMLIB parameter MAXPROCUSER handles the number of processes that CA XCOM tasks use. CA XCOM functions run at the subtask level. Each subtask is considered a process due to the new version of ETPKI that is distributed with this release. The new version of ETPKI requires a POSIX environment.
Functions that run as a subtask:
- TCPIP transfers
- Setting SECURITY=SAF
- SNA transfers
- USS file transfers
- Inquiry for transfers (TYPE=INQUIRE)
- History requests (TYPE=HISTORY or using ISPF)
Consider setting the value for MAXPROCUSER by using the following formula:
MAXPROCUSER value = MAXTASK x 2 + nn
The number nn is the number of active TCP/IP listeners.
Security Considerations for USS Files
USS support enforces SAF security for all transfers that involve a USS file, regardless of the SECURITY= parameter in the default table, config member or EXEC statement. USS Files
This section in our online documentation describes special considerations for handling USS files, including HFS, ZFS, and TFS files.