What are some common commands and how is XCOM configured?

Common commands include TRANSFER to initiate file transfers, LIST to view transfer queues, and MODIFY to alter transfer parameters. Configuration is primarily managed through configuration files.

What types of APIs does XCOM expose and what protocols are used?

XCOM exposes APIs for integration, including options for REST and potentially native APIs depending on the specific platform. Communication protocols include SNA and TCP/IP.

How is XCOM administered and how is user management handled?

XCOM uses configuration files and platform-specific interfaces for configuration. User management is handled through the operating system's user management tools and XCOM's internal security settings.

What business value does XCOM provide?

XCOM enables secure and reliable file transfer, reducing the risk of data loss or corruption. It supports automation of file transfer processes, improving efficiency and reducing manual effort.

How does XCOM help reduce costs and improve productivity?

By automating file transfers and integrating with existing systems, XCOM helps reduce operational costs and improve overall productivity.

What authentication methods are supported and what access control model is used?

XCOM supports authentication methods such as LDAP, Kerberos, and X.509 certificates. It employs an access control model based on role-based access control (RBAC).

What encryption is used and what audit/logging capabilities exist?

XCOM uses encryption protocols such as TLS/SSL to secure data in transit. Audit logging capabilities provide detailed records of file transfer activities.

What administrative interfaces are available and what monitoring capabilities exist?

Administrative interfaces include a command-line interface (CLI) and potentially a web-based console, depending on the platform. Monitoring capabilities include logging to system logs and dedicated monitoring tools.

What are the main configuration parameters and what logging capabilities exist?

Key configuration parameters include transfer parameters, security settings, and network configuration. XCOM provides logging capabilities for monitoring file transfer activities and troubleshooting issues.

Share Your Product Experience

Help the community by sharing your experience with mainframe products. Your insights help others make informed decisions.

Share Your Experience

XCOM

Name: XCOM
Availability: InStock

Broadcom Active z/OS z/VM zVSE/VSEn

File Transfer

Vendor

Broadcom

Product Overview

XCOM's architecture includes several key components: the XCOM server, which manages file transfer requests; the transfer engine, which handles the actual data transfer; and communication modules, which support SNA and TCP/IP protocols. These components communicate via internal APIs and network protocols. Data is stored in files and databases, depending on the platform.

509 certificates. It employs an access control model based on role-based access control (RBAC). Encryption protocols such as TLS/SSL are used to secure data in transit.

The system uses configuration files for setup. Common commands include TRANSFER, LIST, and MODIFY. Competing products like IBM Connect:Direct and Globalscape EFT offer similar functionality, but XCOM's architecture is specifically designed for robust mainframe integration.

XCOM's architecture also allows for flexible deployment options, supporting both centralized and distributed configurations.

Frequently Asked Questions

What is XCOM and what does it do?

XCOM is a file transfer solution that facilitates peer-to-peer data exchange between mainframe systems and other platforms like Windows, UNIX, and Apple. It supports both SNA and TCP/IP protocols for communication.

What platforms does XCOM support?

XCOM supports various platforms including z/OS, z/VM, and zVSE/VSEn for mainframe environments, as well as Windows, UNIX, and Apple operating systems.

What is the history of XCOM?

XCOM was initially developed by Proginet in the late 1980s, later acquired by Spectrum Concepts, then Legent, CA, and finally Broadcom.

Help Improve This Directory

Notice outdated information? Have insights about this product? Help the mainframe community stay informed with accurate, current data.

Report Issue Suggest Product Share Event

Are You a Vendor? Claim Your Listing

Take control of your product listings. Add verified information, showcase updates, and unlock a Claimed Vendor badge across the directory.

Claim Your Listing Now

Share Your Product Experience

XCOM

Product Overview

Frequently Asked Questions

What is XCOM and what does it do?

What platforms does XCOM support?

What is the history of XCOM?

What are some common commands and how is XCOM configured?

What types of APIs does XCOM expose and what protocols are used?

What are the main system components and how do they communicate?

How is XCOM administered and how is user management handled?

What business value does XCOM provide?

How does XCOM help reduce costs and improve productivity?

What authentication methods are supported and what access control model is used?

What encryption is used and what audit/logging capabilities exist?

What administrative interfaces are available and what monitoring capabilities exist?

What are the main configuration parameters and what logging capabilities exist?

Related Products

More from Broadcom

AcceleREXX

ACF2

Allocate DASD Space and Placement

Auditor for z/OS

Automation Point

Bind Analyzer for Db2

Similar Products

3770Link

3780Link

Auto Trans

Auto/FT

Axway Transfer CFT

Barr Host Communications Suite

Help Improve This Directory

Are You a Vendor? Claim Your Listing