Manual Xcom J025731e

Unicenter
CA-XCOM
Data
Transport
for Windows NT
Server/Professional
Administrator Guide
r11

J02573-1E

This documentation and related computer software program (hereinafter referred to as the Documentation) is for
the end users informational purposes only and is subject to change or withdrawal by Computer Associates
International, Inc. (CA) at any time.
This documentation may not be copied, transferred, reproduced, disclosed or duplicated, in whole or in part, without
the prior written consent of CA. This documentation is proprietary information of CA and protected by the copyright
laws of the United States and international treaties.
Notwithstanding the foregoing, licensed users may print a reasonable number of copies of this documentation for
their own internal use, provided that all CA copyright notices and legends are affixed to each reproduced copy. Only
authorized employees, consultants, or agents of the user who are bound by the confidentiality provisions of the
license for the software are permitted to have access to such copies.
This right to print copies is limited to the period during which the license for the product remains in full force and
effect. Should the license terminate for any reason, it shall be the users responsibility to return to CA the reproduced
copies or to certify to CA that same have been destroyed.
To the extent permitted by applicable law, CA provides this documentation as is without warranty of any kind,
including without limitation, any implied warranties of merchantability, fitness for a particular purpose or
noninfringement. In no event will CA be liable to the end user or any third party for any loss or damage, direct or
indirect, from the use of this documentation, including without limitation, lost profits, business interruption,
goodwill, or lost data, even if CA is expressly advised of such loss or damage.
The use of any product referenced in this documentation and this documentation is governed by the end users
applicable license agreement.
The manufacturer of this documentation is Computer Associates International, Inc.
Provided with Restricted Rights as set forth in 48 C.F.R. Section 12.212, 48 C.F.R. Sections 52.227-19(c)(1) and (2) or
DFARS Section 252.227-7013(c)(1)(ii) or applicable successor provisions.
2005 Computer Associates International, Inc.
All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

Contents

Chapter 1: Unicenter CA-XCOM Data Transport
Configuration Preliminaries
Upgrading or Reinstalling ..................................................................... 1-1
Deleting the Queue........................................................................ 1-1
Backing Up Files .......................................................................... 1-2
Saving Your Trusted Registry Entries ....................................................... 1-2
Uninstalling CA-XCOM Data Transport ........................................................ 1-3
Considerations............................................................................ 1-4
Uninstalling Advantage CA-XCOM Data Transport Version 3.0 ............................... 1-5
Uninstalling Advantage CA-XCOM Data Transport Version 3.1 or Higher...................... 1-6
XCOMD Advantage CA-XCOM Scheduler Service ........................................... 1-6
Advantage CA-XCOM Data Transport API Files ............................................. 1-6
Advantage CA-XCOM Data Transport Configuration Files.................................... 1-7
Advantage CA-XCOM Data Transport Conversion Tables .................................... 1-7
Advantage CA-XCOM Data Transport Executable, Queue, and Trace Files ..................... 1-7
Installing or Upgrading ....................................................................... 1-9
Creating a Common Group for Unicenter CA-XCOM Data Transport .......................... 1-9
Changing the Local LU Alias ............................................................... 1-9
Configuring SNA for Unicenter CA-XCOM Data Transport ...................................... 1-10
Procedure ............................................................................... 1-10
Security Considerations ...................................................................... 1-11
User Rights.............................................................................. 1-11
File Access .............................................................................. 1-11
Jobs and Scripts .......................................................................... 1-12
Trusted Security ......................................................................... 1-12
User ID and Passwords ................................................................... 1-12
Security Parameters ...................................................................... 1-13
Parameter Format for Encryption.......................................................... 1-14
Security of Passwords in Traces and XCOM Files........................................ 1-14
Contents iii

Chapter 2: Configuring Unicenter CA-XCOM Data Transport
Using the GUI to Modify Configuration Files .................................................... 2-1
Configuring and Customizing Unicenter CA-XCOM Data Transport ............................... 2-1
Configuration Files ........................................................................ 2-2
Considerations ............................................................................ 2-2
Editing the Parameter Files ................................................................. 2-3
Parameter Format for Command Prompt and Scripts ......................................... 2-3
How the Parameters Are Described ......................................................... 2-4
XCOM.GLB Parameters........................................................................ 2-4
AGE_TIME ............................................................................... 2-4
ATOE_FILENAME ........................................................................ 2-5
CODETABL............................................................................... 2-5
CONVERT_CLASSES...................................................................... 2-5
CREATE_DIRECTORIES................................................................... 2-5
DAEMON_TIMEOUT ..................................................................... 2-6
DATACLAS .............................................................................. 2-6
DEBUG_FLAG............................................................................ 2-6
DOMAIN................................................................................. 2-6
DSNTYPE ................................................................................ 2-7
EOL_CLASSES ............................................................................ 2-7
ETOA_FILENAME ........................................................................ 2-7
EXPIRATION_TIME....................................................................... 2-8
FILE_ACCESS_PASSWORD................................................................ 2-8
FILE_ACCESS_USERNAME................................................................ 2-8
IMPLICIT_PACKING...................................................................... 2-8
INTERNAL_CONVERSION_TABLES ....................................................... 2-9
LCLNTFYL ............................................................................... 2-9
MAIL_PASSWORD........................................................................ 2-9
MAIL_USERNAME ....................................................................... 2-9
MAX_QUEUE_ENTRIES.................................................................. 2-10
MAX_SESSIONS_ENTRIES ............................................................... 2-10
METACODE_CLASSES ................................................................... 2-10
MGMTCLAS............................................................................. 2-10
PORT ................................................................................... 2-11
PROTOCOL ............................................................................. 2-11
QUEUE_PATH........................................................................... 2-11
RMTNTFYL.............................................................................. 2-12
REMOVE_TRAIL_BLANKS ............................................................... 2-12
SECURE_SOCKET........................................................................ 2-12
SESSIONS_FILE.......................................................................... 2-13
iv Administrator Guide

SHELL_CMD............................................................................ 2-13
SOCK_DELAY........................................................................... 2-13
SOCK_RCV_BUF_SIZE................................................................... 2-14
SOCK_SEND_BUF_SIZE ................................................................. 2-14
STORCLAS.............................................................................. 2-14
STAT_FREQUENCY ..................................................................... 2-15
TCP_CMD .............................................................................. 2-15
TEMPDIR ............................................................................... 2-15
TP_CMD................................................................................ 2-15
TRACE_PATH........................................................................... 2-16
TXPI_BUF_SIZE ......................................................................... 2-16
TXPI_RECEIVE_TIMEOUT ............................................................... 2-16
TXPI_SEND_CHECK_FREQ .............................................................. 2-16
TXPI_TERM_TIMEOUT .................................................................. 2-17
WRITE_EOF............................................................................. 2-17
XCOM_CONFIG_SSL .................................................................... 2-17
XCOM_PASSWORD ..................................................................... 2-17
XCOM_SHOW_CIPHER.................................................................. 2-18
XCOM_USERID ......................................................................... 2-18
XENDCMD ............................................................................. 2-18
XLOGFILE .............................................................................. 2-19
XLPCMD................................................................................ 2-19
XNOTIFYCMD .......................................................................... 2-19
XPPCMD................................................................................ 2-19
XPRECMD .............................................................................. 2-20
XTRACE ................................................................................ 2-20
Session Control Parameters ................................................................... 2-21
XCOM.SES .............................................................................. 2-21
Session Control Statements ............................................................... 2-21
Transfers Using SNA ................................................................. 2-22
Transfers Using TCP/IP .............................................................. 2-22
XCOM.CNF Parameters ...................................................................... 2-23
ALLOCATION_TYPE .................................................................... 2-23
BLKSIZE ................................................................................ 2-23
CARRIAGE_CONTROL_CHARACTERS................................................... 2-24
CARRIAGE_FLAG....................................................................... 2-24
CHECKPOINT_COUNT.................................................................. 2-25
CLASS .................................................................................. 2-25
CODE_FLAG............................................................................ 2-26
CODETABL ............................................................................. 2-26
COMPRESS ............................................................................. 2-27
Contents v

CONTROL............................................................................... 2-28
COPIES.................................................................................. 2-28
DATACLAS ............................................................................. 2-28
DEN .................................................................................... 2-28
DESTINATION .......................................................................... 2-29
DESTINATION_TYPE .................................................................... 2-29
DISPOSITION............................................................................ 2-29
DSNTYPE ............................................................................... 2-30
EXPDT .................................................................................. 2-30
FCB ..................................................................................... 2-31
FILE_ACCESS_USERNAME............................................................... 2-31
FILE_OPTION ........................................................................... 2-31
FILE_OPTION_RF........................................................................ 2-33
FORM................................................................................... 2-34
HOLDFLAG ............................................................................. 2-34
LABEL .................................................................................. 2-35
LABELNUM............................................................................. 2-35
LCLNTFYL .............................................................................. 2-36
LOCAL_FILE ............................................................................ 2-36
LOCAL_FILE_RF......................................................................... 2-36
LOCAL_FILE_SJ ......................................................................... 2-37
LOCAL_FILE_SR......................................................................... 2-37
LOCAL_NOTIFY......................................................................... 2-37
LRECL .................................................................................. 2-38
MAXRECLEN............................................................................ 2-38
MGMTCLAS............................................................................. 2-38
NOTIFY_NAME ......................................................................... 2-39
NOTIFYL................................................................................ 2-39
NOTIFYR................................................................................ 2-39
NOTIFY_TERM .......................................................................... 2-40
NUM_OF_DIR_BLOCKS.................................................................. 2-40
NUMBER_OF_RETRIES .................................................................. 2-41
PASSWORD ............................................................................. 2-41
PORT ................................................................................... 2-41
PRIMARY_ALLOC ....................................................................... 2-41
PRIORITY ............................................................................... 2-42
PROTOCOL ............................................................................. 2-42
QUEUE.................................................................................. 2-43
RECORD_FORMAT ...................................................................... 2-43
REMOTE_FILE........................................................................... 2-45
REMOTE_FILE_RF ....................................................................... 2-45
vi Administrator Guide

REMOTE_SYSTEM....................................................................... 2-45
REMOTE_SYSTEM_RF ................................................................... 2-46
REMOTE_SYSTEM_SJ.................................................................... 2-46
REMOTE_SYSTEM_SR ................................................................... 2-46
REMOVE_TRAIL_BLANKS............................................................... 2-47
REPORT_TITLE ......................................................................... 2-47
RESTART_SUPPORTED.................................................................. 2-47
RETPD.................................................................................. 2-48
RETRY_TIME............................................................................ 2-48
RMTNTFYL ............................................................................. 2-48
SECONDARY_ALLOC................................................................... 2-49
SECURE_SOCKET ....................................................................... 2-49
SPACE.................................................................................. 2-50
SPOOL_FLAG........................................................................... 2-50
START_DATE ........................................................................... 2-50
START_TIME............................................................................ 2-51
STORCLAS.............................................................................. 2-51
TAPE ................................................................................... 2-51
TRANSFER_ID .......................................................................... 2-51
TRANSFER_TYPE ....................................................................... 2-52
TRANSFER_USR_DATA ................................................................. 2-52
TRUNCATION .......................................................................... 2-52
TRUSTED............................................................................... 2-53
UNIT ................................................................................... 2-53
UNITCT ................................................................................ 2-53
UNIT_RF................................................................................ 2-53
USER_DATA............................................................................ 2-53
USERID................................................................................. 2-54
VERSION ............................................................................... 2-54
VOLCT ................................................................................. 2-54
VOLSQ ................................................................................. 2-54
VOLUME ............................................................................... 2-55
VOLUME_RF............................................................................ 2-55
XCOM_CONFIG_SSL .................................................................... 2-55
XIDEST ................................................................................. 2-55
XLUNAME.............................................................................. 2-55
XMODE................................................................................. 2-56
XNODESPEC............................................................................ 2-56
XTRACE ................................................................................ 2-56
Creating the CA-XCOM-Batch-Interactive Group ............................................... 2-57
Contents vii

Starting and Stopping the XCOMD Unicenter CA-XCOM Scheduler Service ....................... 2-58
XCOMD Unicenter CA-XCOM Scheduler Service............................................ 2-58
Considerations ........................................................................... 2-58
Starting XCOMD Unicenter CA-XCOM Scheduler Service .................................... 2-59
Stopping XCOMD Unicenter CA-XCOM Scheduler Service................................... 2-60
Tracing Unicenter CA-XCOM Data Transport Scheduler Service .............................. 2-61
Chapter 3: Using Unicenter CA-XCOM Data Transport with
TCP/IP
What You Need ............................................................................... 3-1
TCP/IP Worksheet ............................................................................ 3-3
Using TCP/IP Protocols with Unicenter CA-XCOM Data Transport................................ 3-4
Specifying Protocols Using the Command Line ............................................... 3-4
Specifying Protocol and Port in the GUI ..................................................... 3-5
Protocol Defaults .......................................................................... 3-5
Procedure - Protocol/Port .................................................................. 3-6
Specifying the Remote System .............................................................. 3-7
TCP/IP Name Resolution .................................................................. 3-7
Changing Global Values in Properties Dialog Pages .............................................. 3-8
Properties Dialog Pages .................................................................... 3-8
Changing the Local System Port Value ...................................................... 3-8
Other TCP/IP Parameters .................................................................. 3-9
Chapter 4: Operating Environment
Unicenter CA-XCOM Data Transport Global Variables............................................ 4-1
Considerations ............................................................................ 4-1
Transfer Protocols ..................................................................... 4-2
Default Paths and Directories ............................................................... 4-2
The Unicenter CA-XCOM Data Transport Server Architecture Illustrated........................... 4-3
Using Unicenter CA-XCOM Data Transport Parameters .......................................... 4-4
Parameter Values Used in the GUI .......................................................... 4-4
Parameter Values Used at the Command Prompt ............................................. 4-5
Parameter Format for Command Prompt and Scripts ......................................... 4-5
Syntax ................................................................................ 4-6
Example .............................................................................. 4-6
Guidelines ................................................................................ 4-6
Example .............................................................................. 4-6
viii Administrator Guide

Parameter Format for Encryption........................................................... 4-7
Syntax ............................................................................... 4-7
The XCOMD Unicenter CA-XCOM Scheduler Service ............................................ 4-7
Considerations............................................................................ 4-8
Tracing Transfers ............................................................................. 4-9
Tracing Locally Initiated Transfers ............................................................. 4-9
Tracing All Transfers ...................................................................... 4-9
Tracing Different Components from the GUI ................................................... 4-10
Global Parameters ........................................................................... 4-10
XCOM.GLB ............................................................................. 4-11
Setting Session Control Parameters ............................................................ 4-12
XCOM.SES .............................................................................. 4-12
Transfers Using SNA ................................................................. 4-12
Transfers Using TCP/IP .............................................................. 4-13
Managing the Unicenter CA-XCOM Data Transport Queue ...................................... 4-14
XCOMQM .............................................................................. 4-14
Syntax .............................................................................. 4-14
Options ................................................................................. 4-14
Transfer Failure in Starting State....................................................... 4-15
ERRORLEVEL Return Codes from xcomqm.exe......................................... 4-16
Using the Pre-allocation Exit .................................................................. 4-16
xcompre ................................................................................ 4-16
xcompre Options......................................................................... 4-17
Sample Script ........................................................................ 4-17
Using Unicenter CA-XCOM Data Transport Scripts ............................................. 4-20
Provided Scripts ......................................................................... 4-20
Interacting with the Window Station and Desktop .......................................... 4-20
Modifying Post Processing Scripts............................................................. 4-20
XCOMPP................................................................................ 4-21
Sample Script ........................................................................ 4-21
Post Transfer Script .......................................................................... 4-24
XCOMEND ............................................................................. 4-24
Sample Script ........................................................................ 4-24
Modifying the Printing Script ................................................................. 4-29
XCOMLP................................................................................ 4-29
Print Command in XCOMLP.............................................................. 4-30
Sample Script ........................................................................ 4-30
Customizing the Notification Script ........................................................... 4-33
XCOMNTFY ............................................................................ 4-33
Sample Script ........................................................................ 4-33
Contents ix

Setting Up Trusted Access .................................................................... 4-34
Trusted Transfers to and from Windows .................................................... 4-34
Trusted Access File ....................................................................... 4-34
Starting the Trusted Access Interface ....................................................... 4-34
Trusted Access Parameters ................................................................ 4-35
Domain.............................................................................. 4-35
Group Name ......................................................................... 4-35
Password ............................................................................ 4-35
System Name ........................................................................ 4-35
User Name........................................................................... 4-36
Using the Trusted Access Interface ......................................................... 4-36
Chapter 5: Generating SSL Certificates
Using SSL Mode .............................................................................. 5-1
Creating the CA Certificate..................................................................... 5-2
Setting Expiration ............................................................................. 5-2
Creating the Server Certificate .................................................................. 5-3
Creating the Client Certificate .................................................................. 5-3
Configuring Unicenter CA-XCOM Data Transport SSL Server ..................................... 5-4
Configuring the Unicenter CA-XCOM Data Transport Client ...................................... 5-5
Chapter 6: Troubleshooting
Diagnostic Procedures ......................................................................... 6-2
Collecting Diagnostic Data ................................................................. 6-3
Interpreting Diagnostic Data................................................................ 6-3
Contacting Customer Support .................................................................. 6-4
Product Releases and Maintenance.............................................................. 6-4
Index

x Administrator Guide

Chapter
1
Unicenter CA-XCOM Data
Transport Configuration
Preliminaries

This chapter describes what you need to do before configuring Unicenter

CA-XCOM
Data Transport
. This includes upgrading or reinstalling your

product, and uninstalling the current version if necessary.
Upgrading or Reinstalling
In all situations, if you are upgrading or reinstalling your product, all CA-XCOM
Data Transport processes must be turned off. Before you upgrade or reinstall,
you must do the following:
Coordinate with users for the best time to perform the upgrade.
Stop the Scheduler service.
Ensure that no active transfers are running.
Turn off any CA-XCOM tracing.
Uninstall the current version of your product if necessary. For more
information, see Uninstalling CA-XCOM Data Transport in this chapter.
Deleting the Queue
When performing an upgrade, remove existing queue entries by issuing the
following command at the command line:
XCOMQM -R*
If you do not uninstall your current CA-XCOM Data Transport, you must select
to install the same components that were installed originally. For example, if you
originally had both the SNA Component and the TCP/IP Component installed,
you must upgrade or reinstall them both from the distribution CD.
Unicenter CA-XCOM Data Transport Configuration Preliminaries 11
Upgrading or Reinstalling
Backing Up Files
Back up the following files to a different directory if you have edited them.
(These files are listed with their default directory locations, but your system may
have them installed in directories other than the defaults.)
\XCOMNT\CONFIG\XCOM.CNF
\XCOMNT\CONFIG\XCOM.GLB
\XCOMNT\CONFIG\XCOM.SES
\XCOMNT\CONFIG\XCOM.TID
\XCOMNT\XCOMLP.BAT
\XCOMNT\XCOMNTFY.BAT
\XCOMNT\XCOMPP.BAT
\XCOMNT\XCOMEND.BAT *1
\XCOMNT\XCOMPRE.BAT *2
Notes:
*1 The XCOMEND.BAT file was not available prior to Advantage

CA-XCOM
Data Transport
Version 3.0.
*2 The XCOMPRE.BAT file was not available prior to Advantage CA-XCOM
Data Transport Version 3.1 Service Pack 1.
In addition, if you have customized the following files, you should save them as
well:
\XCOMNT\CONVTAB\ATOE.TAB
\XCOMNT\CONVTAB\ETOA.TAB
You may also wish to back up your configuration files.
After Unicenter CA-XCOM Data Transport is installed, you can compare the
values in these backed up files to the new files, and revise the new files, if
necessary.
Saving Your Trusted Registry Entries
If you have implemented the Trusted Access Interface (see Setting Up Trusted
Access in the chapter Operating Environment), you should save the trusted
registry entries. To do this, the registry entry must be exported before CA-XCOM
is uninstalled, and then imported after CA-XCOM is reinstalled.
To export the registry entry, follow these steps:
1. Initiate REGEDIT from the RUN window.
2. Drill down to RemoteSystemTS and highlight the folder, which is located at:
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates
\XCOM\RemoteSystemTS
3. Return to the top left and click the File tab.
12 Administrator Guide
Uninstalling CA-XCOM Data Transport
4. Choose EXPORT from the pull-down box.
Another pull-down box is produced.
5. Direct where you want to store the Registry entry, for example, C:\tmp.
The file is saved as a .reg file.
To import the registry entry, when you have uninstalled CA-XCOM and
reinstalled r11, follow these steps:
1. RUN -regedit
2. Drill down to XCOM and highlight folder XCOM, which is located at:
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\XCOM)
3. Go back up and click on File.
A pull-down box is produced.
4. Choose IMPORT from the pull-down box.
5. Choose the file location from where you exported the file earlier.
6. Open the file.
The RemoteSystemTS subdirectory and the specific entry that you opened
are created.
You must uninstall your current product before upgrading from Advantage
CA-XCOM Data Transport Version 3.0 or 3.1 to Unicenter CA-XCOM Data
Transport r11.
You must uninstall Unicenter CA-XCOM Data Transport r11 before reinstalling
it, if any of the following apply to your installation:
Unicenter CA-XCOM Data Transport will be upgraded or reinstalled into a
different directory.
Different components of Unicenter CA-XCOM Data Transport will be
installed. For example, if you originally had both the SNA Component and
the TCP/IP Component installed and you are now choosing to install only
the TCP/IP Component.
You would like to have the Scheduler service rebuilt using the default
settings.
Note: Advantage CA-XCOM Data Transport Version 3.0 and Advantage
CA-XCOM Data Transport Version 3.1 use different procedures to uninstall the
product and its components. These procedures are described in the following
sections.
When you have uninstalled your product, continue with the installation
instructions described in the Getting Started.
Considerations
Before starting the uninstall procedure, back up the following files to a different
directory if you have edited them. (These files are listed with their default
directory locations, but your system may have them installed in directories other
than the defaults.)
\XCOMNT\XCOMLP.BAT
\XCOMNT\XCOMPP.BAT
\XCOMNT\XCOMEND.BAT
\XCOMNT\XCOMPRE.BAT
When you reinstall Unicenter CA-XCOM Data Transport you can compare the
values in these backed up files to the new files, and revise the new files if
necessary.
Notes:
The XCOMEND.BAT file was not available prior to Advantage CA-XCOM
Data Transport Version 3.0.
The XCOMPRE.BAT file was not available prior to Advantage CA-XCOM
Data Transport Version 3.1 Service Pack 1.
In addition, if you have customized the following files, you should save them as
well:
You may also wish to back up your configuration files and the CA-XCOM Data
Transport log file.
Important! If you have implemented the Trusted Access Interface (see Setting Up
Trusted Access in the chapter Operating Environment), you should save the trusted
registry entries. For information about doing this, see Saving Your Trusted Registry
Entries in this chapter.
Uninstalling Advantage CA-XCOM Data Transport Version 3.0
To uninstall Advantage CA-XCOM Data Transport Version 3.0, select Start,
Programs, Uninstall CA-XCOM.
The CA-XCOM Uninstall Program dialog displays, allowing you to specify the
path for Advantage CA-XCOM Data Transport. The field is initialized with the
value of the XCOM_HOME system variable that was created during installation.
You can use the browse button to select the path through the Browse
XCOM_HOME Path window.
You can selectively uninstall the following facilities of Advantage CA-XCOM
Data Transport Version 3.0:
XCOMD Advantage CA-XCOM Scheduler service
Advantage CA-XCOM Data Transport Configuration Files
Advantage CA-XCOM Data Transport Conversion Tables
Advantage CA-XCOM Data Transport Executable, Queue, and Trace Files
If you decide not to uninstall Advantage CA-XCOM Data Transport at this time,
choose Cancel. This exits the uninstall process, leaving Advantage CA-XCOM
Data Transport unaffected.
To uninstall the facilities of Advantage CA-XCOM Data Transport that have
been selected, choose Uninstall. If the XCOM path you entered does not match
the value of the XCOM_HOME system variable you will receive a warning
message. You will also receive a final warning that you are about to uninstall
Advantage CA-XCOM Data Transport. Choosing NO to either one of these
warnings will abort the uninstall process and return to the Advantage
CA-XCOM Data Transport Uninstall Program window.
The facilities that are uninstalled with Advantage CA-XCOM Data Transport
Version 3.0 are described below.
Important! Once you uninstall any facilities, Advantage CA-XCOM Data Transport,
will become unstable and you need to reinstall the product to regain functionality.
Note: If your current version of Advantage CA-XCOM Data Transport for
Windows NT is earlier than Version 3.0.0105 sp3, use the uninstall program
xcomunin.exe supplied on your Unicenter CA-XCOM Data Transport r11 media
to remove all the files.
Uninstalling Advantage CA-XCOM Data Transport Version 3.1 or Higher
To uninstall Advantage CA-XCOM Data Transport Version 3.1 or higher:
From the desktop of your Windows NT machine, select Start, Settings,
Control Panel, Add/Remove programs.
Highlight Advantage CA-XCOM Data Transport, then click Add/Remove.
When the Install shield wizard displays, select the appropriate radio button
and click Next.
If you chose to uninstall Advantage CA-XCOM Data Transport Version 3.1, the
program and all its facilities will be removed from the machine, as described in
the following sections.
Note: See your Windows 2000, Windows 2003, or Windows/XP documentation
for uninstall procedures specific to those platforms.
XCOMD Advantage CA-XCOM Scheduler Service
The following are removed:
XCOMD Advantage CA-XCOM Scheduler service
All Advantage CA-XCOM Data Transport associated registry entries
The XCOM_HOME system variable
Advantage CA-XCOM Data Transport API Files
The following files are removed.
Notes:
These files are listed with their default directory locations, but your system
may have them installed in directories other than the defaults.
These files were not available prior to Advantage CA-XCOM Data Transport
Version 3.1 Service Pack 1.
\XCOMNT\APISRC\APISNA.MAK
\XCOMNT\APISRC\APITCP.MAK
\XCOMNT\APISRC\APITEST.C
\XCOMNT\APISRC\CARD3LOG.LIB
\XCOMNT\APISRC\CATO3XPI.LIB
\XCOMNT\APISRC\COMPAPI.LIB
\XCOMNT\APISRC\QAPISNA.MAK
\XCOMNT\APISRC\QAPITCP.MAK
\XCOMNT\APISRC\QAPITEST.C
\XCOMNT\APISRC\STARTST.H
\XCOMNT\APISRC\XCOM.LIB
\XCOMNT\APISRC\XCOMAPI.H
\XCOMNT\APISRC\XCOMSNA.LIB
\XCOMNT\APISRC\XCOMTCP.LIB
The following directory is removed if empty:
\xcomnt\apisrc
Advantage CA-XCOM Data Transport Configuration Files
The following files will be removed. (These files are listed with their default
than the defaults.)
The following directory will be removed if empty.
\XCOMNT\CONFIG
Advantage CA-XCOM Data Transport Conversion Tables
The following files will be removed. (These files are listed with their default
than the defaults.)
The following directory will be removed if empty:
\XCOMNT\CONVTAB
Advantage CA-XCOM Data Transport Executable, Queue, and Trace Files
The following files will be removed. These files are listed with their default
than the defaults.
Note: The following list of files includes both server and workstation specific
files so there may be files that do not exist on your particular system.
\XCOMNT\CARD3.BAT
\XCOMNT\CARD3LOE.EXE
\XCOMNT\CARD3LOF.EXE
\XCOMNT\CARD3LOG.DLL
\XCOMNT\CARD3LOG.EXE
\XCOMNT\CAREGLOG.LOG
\XCOMNT\CATO3XPI.DLL
\XCOMNT\CAXCGSVI.EXE
\XCOMNT\CAXCGSVR.EXE
\XCOMNT\CAXCNTMA.EXE
\XCOMNT\CAXCNTMB.DLL
\XCOMNT\CAXCNTWA.EXE
\XCOMNT\CAXCNTWB.DLL
\XCOMNT\CAXCNTSA.EXE
\XCOMNT\CAXCNTSB.DLL
\XCOMNT\CAXCNTSW.EXE
\XCOMNT\CAXCNTWT.EXE
\XCOMNT\CAXCXGA.DLL
\XCOMNT\CLEANLOG.EXE
\XCOMNT\LEAK.IT
\XCOMNT\LU6RECV.EXE
\XCOMNT\LU6SEND.EXE
\XCOMNT\README.TXT
\XCOMNT\README.HTML
\XCOMNT\RELAY.DLL
\XCOMNT\SDSNOTE.EXE
\XCOMNT\SETVAR.EXE
\XCOMNT\SRVINST.EXE
\XCOMNT\SRVRM.EXE
\XCOMNT\TPSETUP.EXE
\XCOMNT\VGAL3.DLL
\XCOMNT\VGALAXY2.VR
\XCOMNT\XCOM.LOG
\XCOMNT\XCOM62.EXE
\XCOMNT\XCOMD.EXE
\XCOMNT\XCOMENCR.EXE
\XCOMNT\XCOMEND.BAT
\XCOMNT\XCOMLP.BAT
\XCOMNT\XCOMPRE.BAT *1
\XCOMNT\XCOMMNT.EXE *1
\XCOMNT\XCOMMAIL.EXE
\XCOMNT\XCOMNT.CNT
\XCOMNT\XCOMNT.EXE
\XCOMNT\XCOMNT.HLP
\XCOMNT\XCOMNT.VR
\XCOMNT\XCOMPOP.EXE
\XCOMNT\XCOMPP.BAT
\XCOMNT\XCOMQM.EXE
\XCOMNT\XCOMRECV.EXE
\XCOMNT\XCOMSEND.EXE
\XCOMNT\XCOMTCP.EXE
\XCOMNT\XCOMTP.EXE
\XCOMNT\XCOMTRST.EXE *1
\XCOMNT\XCOMTRST.HLP *1
\XCOMNT\XCOMUNIN.EXE
\XCOMNT\Q\*.*
\XCOMNT\TMP\*.*
\XCOMNT\TRACE\*.*
*1 These files did not exist prior to Advantage CA-XCOM Data Transport
Version 3.1 Service Pack 1.
The following directories are removed.
\XCOMNT\Q
\XCOMNT\TMP
\XCOMNT\TRACE
The Advantage CA-XCOM Data Transport program group is removed.
Installing or Upgrading
Installing or Upgrading
For information about installing Unicenter CA-XCOM Data Transport, see the
Unicenter CA-XCOM Data Transport for Windows NT Server/Professional Getting
Started.
Creating a Common Group for Unicenter CA-XCOM Data Transport
Creation of the Program Group for CA-XCOM Data Transport is based on your
response to the prompt Install this application for: on the customer
information screen. If you select:
Install this application for anyone who uses the computer (all users); the
installation process creates a Common Program Group for Unicenter
CA-XCOM Data Transport.
Install this application for only me (username); the installation process
creates a Personal Program Group for Unicenter CA-XCOM Data Transport.
Changing the Local LU Alias
For SNA configurations, if you need to change the local LU alias specified
during Unicenter CA-XCOM Data Transport installation, use the TPSETUP
program provided with Unicenter CA-XCOM Data Transport.
To start this program from the Desktop, select Start, then select Run, then specify
C:\XCOMNT\TPSETUP.EXE in the Command Line field of the Run window,
and click OK.
When the TPSETUP program starts, the Invokable TP Setup window is
displayed. To change your local LU alias, fill in the fields of the Invokable TP
Setup window and click OK. When you click OK, you are asked to indicate
whether the existing TP name can be overwritten.
Configuring SNA for Unicenter CA-XCOM Data Transport
Configuring SNA for Unicenter CA-XCOM Data Transport
This section contains the procedures required to configure SNA for Unicenter
CA-XCOM Data Transport after Unicenter CA-XCOM Data Transport is
installed on either the NT Server or NT Professional.
In your SNA configuration file you must modify the MODE, specify Transaction
Programs (TP) and configure CPI-C Symbolic destination names.
Procedure
To modify your SNA configuration file for use with either Unicenter CA-XCOM
Data Transport for Windows NT Server or Unicenter CA-XCOM Data Transport
Windows NT Professional, follow these steps:
1. Specify a valid mode, such as XCOMMODE, for the mode name.
2. Create CPI-C Side Information records for each partner. The CPI-C Side
Information record associates a set of parameters (communications
properties) with a symbolic destination name, which the CPI-C program
uses to initialize a conversation.
3. During the installation process of Unicenter CA-XCOM Data Transport, the
following TPs should have been created and added to the NT registry. If
cancel was selected during a new install, then the TPSETUP program will
need to be run again so that these TPs get added:
LU6RECV
LU6SEND
XCOMRECV
XCOMSEND
Security Considerations
This is a summary of security information presented in the Unicenter CA-XCOM
Data Transport for Windows NT Manual set. For more information, see the
Unicenter CA-XCOM Data Transport for Windows NT Server/Professional User
Guide.
User Rights
Users with user rights to start and stop Windows NT services can start and stop
the XCOMD Unicenter CA-XCOM Scheduler service. Other users are normally
given user rights to perform transfers and check the status of the queue.
Unicenter CA-XCOM Data Transport uses two sets of credentials to access the
logthose assigned to the XCOMD Unicenter CA-XCOM Scheduler service in
the SERVICES applet of the Control Panel and the credentials that are passed in
the transfer (USERID). The user ID performing the transfer must have change
access for the log, or Unicenter CA-XCOM Data Transport will not be able to
update the xcom.log with transfer information.
File Access
You can control access to directories and files on drives formatted for NTFS with
the security features of Windows NT.
You can control access to all files on a Windows system by setting permissions
on a directory or file. The access rights of the user ID on the remote system
determine the actions permitted for the transfer. Users cannot use a directory or
file unless they have been granted the appropriate permissions.
Passwords are case sensitive. This is particularly important to consider when
transfers to Windows NT originate with mainframe partners.
Jobs and Scripts
All jobs and scripts received by Unicenter CA-XCOM Data Transport are
submitted to the operating system by creating a new process. The new process
runs in the security context of the user receiving the transfer that caused the
process to be created. Unicenter CA-XCOM Data Transport adds an access
control entry to the window station and desktop to allow the process to interact
with the user. Once the process is complete the entry point is removed from the
window station and desktop. If the process created by the transfer creates an
additional process, this additional process will not have access to the window
station or desktop after Unicenter CA-XCOM Data Transport has removed the
entry control point created by the original process.
Trusted Security
The Trusted Access feature allows a transfer from a remote system to be sent
without requiring the user ID and password to be specified in a Unicenter
CA-XCOM Data Transport transfer. In addition, a group user ID can be set up so
that only one user ID can be used for multiple users sending into this system.
Trusted Access has a GUI interface, making it easy to build a list of trusted
partners, which resides in the Windows NT Registry. For more information, see
the section Setting up Trusted Access in the chapter Operating Environment.
User ID and Passwords
In general, a remote system requires a password and user ID before Unicenter
CA-XCOM Data Transport can perform transfers. The access rights of the user ID
on the remote system determine the actions permitted for the transfer.
For transfers coming into CA-XCOM for Unicenter CA-XCOM Data Transport
for Windows NT Server/Professional and associated files, access is governed by
the security policies that are in effect for your Windows environment.
Security Parameters
The following security parameters may be defined in the XCOM.GLB
configuration file and using the security tab in the GUI:
FILE_ACCESS_USERNAMEName of user accessing local files. Used for
locally initiated transfers only.
FILE_ACCESS_PASSWORDPassword for access to local files. Used for
locally initiated transfers only.
Note: For local file access, specify the FILE_ACCESS_USERNAME and
FILE_ACCESS_PASSWORD parameters for the following:
To access a file on a server to which you are not already attached.
To access a file using a user name that is different from the one you used
to attach to the server.
MAIL_USERNAMESpecify a value here to use for your messaging system
profile name.
XCOM_USERIDThe default user ID for remotely-initiated transfers.
XCOM_PASSWORDThe default password for remotely-initiated transfers.
XCOM_TRUSTED_OVRSpecifies if the user is permitted to override the
user ID using the USERID parameter for locally initiated trusted transfers.
DOMAINThe Windows domain name for use in authenticating the user
ID and password.
The following parameters may be defined in a .cnf configuration file or on the
command line:
USERIDThe user ID for a locally-initiated transfer. This parameter is
passed to the remote CA-XCOM partner for checking security on that
system.
PASSWORDThe password associated with the user ID on the remote
system.
TRUSTEDAllows the user to request a trusted transfer.
Parameter Format for Encryption
Unicenter CA-XCOM Data Transport allows encryption of parameter values in
configuration files. This format is generated by running XCOMENCR.EXE at the
command line with a configuration file, or it is generated automatically by the
GUI, when appropriate. This feature is primarily for encrypting the values of
security parameters. This format indicates to Unicenter CA-XCOM Data
Transport that the parameter value is encrypted. Unicenter CA-XCOM Data
Transport recognizes the parameter value as encrypted and decrypts it before
using it for transfers. If this format is not used, the value is treated as normal
text.
For further information about encrypting parameters and running
XCOMENCR.EXE, see Encrypting Parameter Values in Existing Configuration
Files in the chapter The Command Line Interface in the Unicenter CA-XCOM
Data Transport for Windows NT Server/Professional User Guide.
Security of Passwords in Traces and XCOM Files
Unicenter CA-XCOM Data Transport automatically encrypts passwords in
transfers, traces, and queue files.


Chapter
2
Configuring Unicenter CA-XCOM
Data Transport

Most of the information in this chapter applies to the editing of configuration
files using the command line interface.
Using the GUI to Modify Configuration Files
Using the GUI, you can create or open specific configuration files. You can create
any number of these transfer configuration files for different transfer situations.
You can edit a configuration on-screen, save it under another name and modify
it for your own use, or add and delete transfers to create different configuration
files. Or you can simply modify the default values on-screen for a selected
transfer.
The commonly used XCOM.GLB parameters, as described below, should be
modified using the Properties Dialog pages of the GUI. For information about
using the GUI, see the chapter Using Unicenter CA-XCOM Data Transport in
the Unicenter CA-XCOM Data Transport for Windows NT Server/Professional User
Guide.
Configuring and Customizing Unicenter CA-XCOM Data
Transport
The set of files downloaded by the Unicenter CA-XCOM Data Transport
installation program includes three configuration files, XCOM.CNF, XCOM.GLB
and XCOM.SES, which are collections of parameters representing the various
operational features of Unicenter CA-XCOM Data Transport. For some
parameters, a predefined default value is provided while others have been left
undefined. You need to review the parameter definitions contained in these files
and edit them, if necessary, to meet your installations specific operating
conditions and requirements.
Configuring Unicenter CA-XCOM Data Transport 21
Configuring and Customizing Unicenter CA-XCOM Data Transport
Configuration Files
The parameter definitions contained in the files XCOM.CNF and XCOM.GLB are
used to control the performance of transfers. The information contained in the
XCOM.CNF file is relevant only to the performance of locally initiated transfers
from the command line whereas the information contained in the XCOM.GLB
file applicable to the performance of both locally and remotely initiated transfers.
The XCOM.GLB file is kept open at all times. The XCOM.CNF file, on the other
hand, is re-opened every time a transfer occurs.
If changes are made in the XCOM.GLB file, the XCOMD Unicenter CA-XCOM
Scheduler service must be stopped and restarted for the changes to become
effective. This is not necessary when modifying the XCOM.CNF file. For
information about modifying default values in XCOM.GLB using the GUI, see
Using the Properties Dialog Pages in the chapter Using Unicenter CA-XCOM
Data Transport in the Unicenter CA-XCOM Data Transport for Windows NT
Server/Professional User Guide.
For locally initiated command line transfers, the parameters defined in
XCOM.CNF override those defined in XCOM.GLB.
The XCOM.CNF parameters, in turn, can be overridden by parameters supplied
on the command line.
The XCOM.SES file contains information about the maximum number of parallel
sessions that can be used by locally initiated scheduled transfers for each remote
system. This information is conveyed in the form of standard assignment
statements used in the other configuration files to assign values to parameters. In
the XCOM.SES file, the left side of each assignment statement always specifies
the remote system (for example, remote system name, CPI-C symbolic
destination name, IP address) while the right side identifies the number of
sessions the local system can establish with the given remote system. Values for
XCOM.SES can be modified with any text editor
Considerations
Before Unicenter CA-XCOM Data Transport can be configured, the following
tasks must be completed:
Installation of Unicenter CA-XCOM Data Transport for Windows NT
For using SNA/APPC protocols, installation and configuration of the SNA
APPC
For using TCP/IP protocols, installation and configuration of TCP/IP
capability
Configuring and Customizing Unicenter CA-XCOM Data Transport
For a description of installing Unicenter CA-XCOM Data Transport for Windows
NT, see the Unicenter CA-XCOM Data Transport for Windows NT
Server/Professional Getting Started guide. For information about configuring SNA,
see Configuring SNA for Unicenter CA-XCOM Data Transport in this chapter.
For information about using Unicenter CA-XCOM Data Transport to perform
transfers using TCP/IP, see the chapter Using Unicenter CA-XCOM Data
Transport with TCP/IP. For more information about TCP/IP, see the Microsoft
Windows System Guide.
Editing the Parameter Files
Each parameter file can be opened for editing in any text editor that generates
ASCII text. In addition, the XCOM.CNF file can be accessed through the File
menu in the GUI. Certain XCOM.GLB parameters can be edited using the GUI.
WARNING! The parameters in the XCOM.GLB files and the values of the options on
the Properties dialog pages in the GUI should only be changed by authorized Unicenter
CA-XCOM Data Transport administrators. Most users will not need to change these
values. The values should not be changed or deleted unnecessarily, and parameters
should not be deleted from XCOM.GLB unnecessarily. If any of these values or
parameters were deleted unnecessarily, the results are unpredictable.
Note: The installation process installs XCOM.GLB with parameters used for
TCP/IP transfers. Even if you are not using TCP/IP, you should not delete these
parameters from XCOM.GLB.
Parameter Format for Command Prompt and Scripts
When the installation program downloads the parameter files, the parameters in
them appear in either of the following formats:
PARAMETER NAME=parameter value
PARAMETER NAME=
The first format is used with parameters which have a predefined (default)
valuefor instance, EXPIRATION_TIME=6000, where EXPIRATION_TIME is a
parameter (name) and 6000 is the value assigned to this parameter. The equal
sign (=) used in a parameter statement is an assignment operator, which assigns
a value to a parameter. If the value assigned to a parameter does not meet the
requirements of your Unicenter CA-XCOM Data Transport installation, you may
assign the parameter a new value.
The second format is used with parameters which have no predefined default
valuefor instance, NOTIFY_NAME=, which consists of a parameter name and
the assignment operator. Depending on the requirements of your installation,
you may or may not have to assign a value to the parameter.
XCOM.GLB Parameters
How the Parameters Are Described
The parameters contained in the different parameter files are described in the
following format:
The parameter names are placed in the left margin of the page.
Next to each parameter name is one or more paragraphs of text providing a
description of the parameters purpose and other relevant information.
A table with two columns labeled Value and Description or a paragraph
labeled Range explains what can be specified as the parameters value.
A paragraph labeled Default identifies the parameters default value.
The default values listed here are based on the defaults as supplied in the
sample files XCOM.GLB and XCOM.CNF that come with Unicenter
CA-XCOM Data Transport.
In this guide, C:\XCOMNT is indicated as the default path. However, your
installation may have Unicenter CA-XCOM Data Transport under a different
path or on a different drive. If this default is changed during the installation
of Unicenter CA-XCOM Data Transport, the default values in the
XCOM.GLB file will reflect this change by use of the XCOM_HOME
environmental variable %XCOM_HOME%.
Use this variable to define the Unicenter CA-XCOM Data Transport home
directory in both the XCOM.GLB and XCOM.CNF files.
A paragraph labeled Example provides an example of the parameters use.
XCOM.GLB Parameters
The parameters contained in the XCOM.GLB file are used to set global defaults
for Unicenter CA-XCOM Data Transport transfers.
AGE_TIME
The number of seconds before waiting queue entries are removed from the
queue. If the value is 0, the waiting queue entries never age and are never
removed from the queue.
Range 0 to 86313600 (999 days)
Default 432000 (5 days)
XCOM.GLB Parameters
ATOE_FILENAME
The name of the file containing the ASCII-to-EBCDIC character conversion table.
This is a custom file used only for creating custom translation tables from ASCII
to EBCDIC, if needed.
Range 1 to 256 characters
Default C:\XCOMNT\CONVTAB\ATOE.TAB
CODETABL
The prefix to the file names, atoe.tab and etoa.tab, that contain the external
ASCII-to-EBCDIC and EBCDIC-to-ASCII custom character conversion tables that
determine which external translation tables will be used. This parameter is valid
only if INTERNAL_CONVERSION_TABLES=NO.
Default None
CONVERT_CLASSES
A character string containing print classes for which EBCDIC to ASCII
conversions will be performed. For incoming report transfers only.
Default None
CREATE_DIRECTORIES
Indicates whether a new directory should be created to accommodate incoming
file transfers. CREATE_DIRECTORIES=YES causes a new directory to be
created.
Range YES or NO
Default YES
XCOM.GLB Parameters
DAEMON_TIMEOUT
Specifies the number of minutes Unicenter CA-XCOM Data Transport will wait
for a response from a partner before aborting a session. This ensures a transfer
does not hang indefinitely waiting for a response.
DAEMON_TIMEOUT can only be set in the xcom.glb file. It cannot be set from
the Properties Dialog Pages of the GUI.
Range 10 to 1440
Default 60
DATACLAS
Specifies the name of the data class to use when allocating a new SMS-managed
data set.
Note: This parameter applies only to mainframe SMS data sets.
Default None
DEBUG_FLAG
Indicates whether to print trace data to STDERR.
Range YES or NO
Default NO
DOMAIN
The Windows domain name for use in authenticating the user ID and password
Default None
XCOM.GLB Parameters
DSNTYPE
Specifies the data set definition.

Value Description
LIBRARY Defines a PDSE
PDS Defines a partitioned data set
Note: These values are IBM standards for SMS processing.
Default None
EOL_CLASSES
A character string containing print classes for which an ASCII new line character
will be appended to each record. For incoming report transfers only.
Default None
ETOA_FILENAME
The name of the file containing the EBCDIC-to-ASCII character conversion table.
This is a custom file used only for creating custom translation tables from
EBCDIC to ASCII, if needed.
Default C:\XCOMNT\CONVTAB\ETOA.TAB
XCOM.GLB Parameters
EXPIRATION_TIME
The maximum time, in seconds, that a transaction is held in the transfer queue
after it is executed. When the maximum time is reached, all references to the
transaction are removed from the queue, including trace files and temporary
files.
Note: If EXPIRATION_TIME is set to no value in XCOM.GLB, the program
default of 6000 is used.
Range 0 to 32767
Default 6000
FILE_ACCESS_PASSWORD
Password for access to local files. This is used for locally initiated transfers only.
Default None
FILE_ACCESS_USERNAME
Name of user accessing local files. This is used for locally initiated transfers only.
Default None
IMPLICIT_PACKING
Indicates whether TCP/IP should always use packing.
Range YES or NO
Default YES
XCOM.GLB Parameters
INTERNAL_CONVERSION_TABLES
Indicates whether internal or external conversion tables should be used for
ASCII-to-EBCDIC conversion and EBCDIC-to-ASCII conversion. The external
conversion files may be customized to meet your needs. For the appropriate
directory and file name, see ATOE_FILENAME and ETOA_FILENAME in this
chapter.
Range The range of values is listed in the following table:

Value Description
YES Use internal conversion tables.
NO Use the external tables contained in ATOE_FILENAME and
ETOA_FILENAME.
Default YES
LCLNTFYL
Specifies the local user notification level.

Value Description
A or ALL NOTIFY on transfer completion.
W or WARN NOTIFY only if the transfer received a warning or error.
E or ERROR NOTIFY only if the transfer received an error.
Default ALL
MAIL_PASSWORD
If NOTIFYR is set to MAIL, specify your messaging system profile password.
MAIL_USERNAME
If NOTIFYR is set to MAIL, specify your messaging system profile name.
XCOM.GLB Parameters
MAX_QUEUE_ENTRIES
The maximum number of entries allowed in the transfer queue. Once the
maximum number of queue entries is reached, Unicenter CA-XCOM Data
Transport rejects subsequent transfer attempts.
Note: This value depends on the memory available when Unicenter CA-XCOM
Data Transport is started.
Range 0 to n
The value of n is the maximum allowed memory segment divided by 512.
Default 50
MAX_SESSIONS_ENTRIES
The maximum number of partners that can be described in the XCOM.SES file.
Range 1 to 999
Default 50
METACODE_CLASSES
Classes of print jobs that will be saved in metacode format, a variable length
record format. For incoming report transfers only.
Default None
MGMTCLAS
Specifies the name of the management class to use when allocating a new
SMS-managed data set.
Default None
XCOM.GLB Parameters
PORT
The number of the TCP/IP port on the remote Unicenter CA-XCOM Data
Transport server. Used for TCP/IP transfers only.
Range 1 to 65535
Default 8044
PROTOCOL
The type of communication protocols to use.

Value Description
SNA For transfers using SNA/APPC communication protocols
TCPIP For transfers using TCP/IP communication protocols
Default SNA
Note: If only the TCP/IP Component is installed with the base components of
Unicenter CA-XCOM Data Transport, the default value is TCPIP.
QUEUE_PATH
Directory containing the transfer queue data files.
Default C:\XCOMNT\Q
XCOM.GLB Parameters
RMTNTFYL
Specifies the remote user notification level when sending data to a remote
system.

Value Description
Default ALL
REMOVE_TRAIL_BLANKS
Indicates whether or not to remove the blanks at the end of each record when
receiving a text file.
Range YES or NO
Default NO
SECURE_SOCKET
Specifies whether to use an OpenSSL socket or non-OpenSSL socket for transfers.

Value Description
YES Performs secure transfer.
The transfer uses an OpenSSL socket and must to connect
to a SSL listener on the remote partner.
NO Performs non-secure transfer.
The transfer uses a non-OpenSSL socket.
Default NO
XCOM.GLB Parameters
SESSIONS_FILE
The path name of the XCOM.SES file. This file tells Unicenter CA-XCOM Data
Transport the number of parallel sessions available for locally initiated transfers
for each remote system.
Default C:\XCOMNT\CONFIG\XCOM.SES
SHELL_CMD
Name of the command that runs jobs, reports, notification scripts, and post
processing scripts on the local system.
Default CMD.EXE /C
SOCK_DELAY
TCP/IP Socket option TCP_NODELAY. Refers to the Nagle algorithm for send
coalescing. By default, small sends may be delayed, but should have no impact
for normal Unicenter CA-XCOM Data Transport record sizes. Used for TCP/IP
transfers only.
Note: Socket options affect the way Unicenter CA-XCOM Data Transport uses
the TCP/IP stack implementation.

Value Description
YES Small sends may be delayed. (Does not disable the Nagle algorithm.)
NO All sends are immediate. (Disables the Nagle algorithm.)
Default YES
XCOM.GLB Parameters
SOCK_RCV_BUF_SIZE
TCP/IP Socket option SO_RCVBUF. The buffer size for receives. Use zero for the
default size provided by the socket implementation. The value for
SOCK_RCV_BUF_SIZE can be smaller than the value for TXPI_BUF_SIZE. Used
for TCP/IP transfers only.
Range 0 to 65536
Default 0
SOCK_SEND_BUF_SIZE
TCP/IP Socket option SO_SNDBUF. The buffer size for sends. Use zero for the
default size provided by the socket implementation. The value for
SOCK_SEND_BUF_SIZE can be smaller than the value for TXPI_BUF_SIZE.
Used for TCP/IP transfers only.
Range 0 to 65536
Default 0
STORCLAS
Specifies the name of the storage class for a new SMS-managed data set.
Default None
XCOM.GLB Parameters
STAT_FREQUENCY
Indicates the frequency with which transfer statistics are made available to
XCOMQM and the GUI. Intended for tuning high-speed links. Longer values
help performance but byte/record counts in XCOMQM and the GUI may be
slightly behind the actual counts.
Range 1 to 9999
Default 1
TCP_CMD
Path and name of the Unicenter CA-XCOM Data Transport program started by
the XCOMD Unicenter CA-XCOM Scheduler service that is used for transfers
that use TCP/IP protocols.
Range 0 to 256
Default C:\XCOMNT\XCOMTCP.EXE
TEMPDIR
Indicates the directory in which temporary files for jobs and reports can be
created.
Default C:\XCOMNT\TMP
TP_CMD
Path and name of the Unicenter CA-XCOM Data Transport program started by
the XCOMD Unicenter CA-XCOM Scheduler service that is used for transfers
that use SNA/APPC protocols.
Default C:\XCOMNT\XCOMTP.EXE
Unicenter CA-XCOM Data Transport, there will be no default value.
XCOM.GLB Parameters
TRACE_PATH
The directory containing the trace data files.
Default C:\XCOMNT\TRACE
TXPI_BUF_SIZE
For TCP/IP transfers, the internal buffer size for sends and receives. The default
size allows multiple Unicenter CA-XCOM Data Transport records to be received
in a single socket call. With this default, if your Unicenter CA-XCOM Data
Transport record size is less than 32K, Unicenter CA-XCOM Data Transport will
attempt to receive multiple records in a single socket call. Used for TCP/IP
transfers only.
Range 0 to 65536
Default 32768
TXPI_RECEIVE_TIMEOUT
Maximum wait time, in seconds, after a TCP/IP failure is detected before a
socket error is generated. This defaults to zero and should remain at zero unless
it becomes necessary for a broken connection to generate a retryable error.
Changing this parameter from zero invokes the TCP/IP function "select", which
adds a measure of connection detection, but sacrifices some performance. This
parameter is for TCP/IP only.
Range 0 to 1200 seconds
Default 0 seconds
TXPI_SEND_CHECK_FREQ
Indicates the frequency that Unicenter CA-XCOM Data Transport checks to see if
incoming error information is available when sending data. For example, if the
value is 5, a check is made every fifth time that data is sent, to determine if data
is available for receiving. Larger values give better performance. Smaller values
minimize the sending of data after the partner reports an error. Used for TCP/IP
transfers only.
XCOM.GLB Parameters
Range 0 to 9999
Default 10
TXPI_TERM_TIMEOUT
Maximum wait time, in seconds, for the partner to terminate TCP/IP
communications. If a transfer terminates normally, both sides of the conversation
coordinate the termination, and there should be no need to wait. This timeout
will occur only during an error in the termination of the connection. Used for
TCP/IP transfers only.
Range 0 to 999 seconds
Default 20 seconds
WRITE_EOF
When receiving a text file, set to YES to have the end of file character (CTRL + Z)
written at the end of the file.
Range YES or NO
Default NO
XCOM_CONFIG_SSL
This parameter specifies the value of the configssl.cnf file path and file name.
Default C:\XCOMNT\configssl.cnf
XCOM_PASSWORD
The default password for remotely initiated transfers.
Default None
XCOM.GLB Parameters
XCOM_SHOW_CIPHER
Specifies whether to display encryption algorithms in the Unicenter CA-XCOM
Data Transport queue detailed information, which is used for transfers.

Value Description
NO Do not display encryption algorithms in the queue detail
information.
YES Display encryption algorithms in the queue detail
information.
Default NO
XCOM_USERID
The default user ID for remotely initiated transfers. If this value begins with a
blank or is set to no value, Unicenter CA-XCOM Data Transport will not require
remotely initiated transfers to specify a user ID. The transfer will run under the
same security level as the XCOMD Unicenter CA-XCOM Scheduler service.
Default XCOM
XENDCMD
The name of the post processing command optionally invoked by the Unicenter
CA-XCOM Data Transport transfer program after any type of transfer is
finished, whether successful or not. Invoked after partner communications have
ended. A sample command file is provided in C:\XCOMNT\XCOMEND.BAT.
Default None
XCOM.GLB Parameters
XLOGFILE
The name of the file where Unicenter CA-XCOM Data Transport logs activity. If
you do not specify this parameter, the system-wide log file
C:\XCOMNT\XCOM.LOG is used. If you specify this parameter with a different
file name, the logging information is only sent to the specified file.
Note: Specify the full path name if QUEUE=YES.
Default C:\XCOMNT\XCOM.LOG
XLPCMD
Name of the post-processing command used to send print jobs to the spooler.
For incoming reports only.
Default C:\XCOMNT\XCOMLP.BAT
XNOTIFYCMD
Path name of the command that Unicenter CA-XCOM Data Transport uses to
notify users on the local system of the completion of a transfer. This is normally a
shell script that composes a message and invokes mail or write as appropriate.
Default C:\XCOMNT\XCOMNTFY.BAT
XPPCMD
The name of the command used for user-defined post-processing.
Default C:\XCOMNT\XCOMPP.BAT
XCOM.GLB Parameters
XPRECMD
Path name of the command used for user-defined pre-allocation processing, for
both locally and remotely initiated transfers. Specify this parameter in
XCOM.GLB to invoke the pre-allocation exit xcompre.
Default None
XTRACE
Indicates the level of desired execution tracing.

Value Description
0 No tracing.
1 to 8 Levels of tracing from 1 (lowest) to 8 (highest).
9 Show the contents of the data buffers.
10 Includes levels 1 through 9, plus some additional detailed technical
information.
Default 0
Session Control Parameters
Use XCOM.SES to limit the number of parallel sessions available for locally
initiated transfers for each remote system.
Use any editor that generates ASCII text to modify XCOM.SES.
XCOM.SES
XCOM.SES is a file used by the XCOMD Unicenter CA-XCOM Scheduler service
to control the maximum number of sessions available for locally initiated
transfers for each remote system.
When Unicenter CA-XCOM Data Transport is installed, the XCOM.SES file is
placed in the directory C:\XCOMNT\CONFIG.
You can set a maximum number of partners that can be described in this file by
specifying a number in the MAX_SESSIONS_ENTRIES global parameter. For
example, if you specify MAX_SESSIONS_ENTRIES=50, you can have up to 50
lines in this file, each one specifying the name of the remote system.
You limit the number of sessions available for Unicenter CA-XCOM Data
Transport transfers by setting a number in the XCOM.SES file for each remote
system. If a session is not available for immediate use, the transfer is queued for
subsequent execution.
To specify a remote system, as indicated in the example in this section, replace
connection_profile with the destination address or name specified by the user in
the remote system parameter (REMOTE_SYSTEM, REMOTE_SYSTEM_RF,
REMOTE_SYSTEM_SJ, or REMOTE_SYSTEM_SR).
Note: Unicenter CA-XCOM Data Transport reserves memory for information
about the number of sessions for each destination based upon the
connection_profile entries in this file.
Session Control Statements
The XCOM.SES file consists of one or more session control statements of the
following format:
connection_profile=number_of_sessions_allowed
Transfers Using SNA
For transfers using SNA, the parameter name connection_profile represents the
CPI-C symbolic destination name of the remote system to which the session limit
is applied. The value for the parameter should be between one and the
maximum number of sessions allowed for the partner mentioned in the
associated CPI-C record. The maximum number of sessions allowed is equal to
the lowest value from among the maximum number of sessions supported in the
following properties:
The local LU
The Log Mode (XCOMMODE, the recommended mode name, or whatever
name you are using)
The remote LU
The platform of the remote Unicenter CA-XCOM Data Transport partner
(Applies particularly to PC-DOS and OS/2 partners)
Transfers Using TCP/IP
For transfers using TCP/IP, specify the format of the remote system that is
consistent with your sites use of the remote system parameters. If the IP address
is used, specify connection_profile in the form of 123.123.78.91. If host names or
domain names are used in the remote system parameter, specify
connection_profile in the appropriate form of the name.
You may specify a connection_profile for each form of address or name that is
used. Note that if the XCOM.SES file does not have an entry for the host name or
domain name, the value of the connection_profile will default to one.
Example
In the following XCOM.SES example, scheduled locally initiated transfers can
use up to 8 sessions to XCOMA and up to 4 sessions to XCOMB:
XCOMA=8
XCOMB=4
XCOM.CNF Parameters
XCOM.CNF Parameters
The parameters contained in the XCOM.CNF file are used for locally initiated
command line transfers. If no parameter file is specified on the command line,
the parameters defined in XCOM.CNF override the parameters defined in the
XCOM.GLB file. If a parameter file other than XCOM.CNF is specified on the
command line, then the parameters specified in that file override those specified
in XCOM.CNF.
ALLOCATION_TYPE
Indicates the unit of storage allocation for a data set created on an IBM
mainframe.

Value Description
CYL Cylinders
TRK Tracks
BLK Blocks
Default None
Note: Version 2 parameter.
BLKSIZE
Specifies the block size of a data set created on an IBM mainframe.
Note: Used when FILE_OPTION=CREATE
Range 0 to 32767

If the format is Then the block size must be
Fixed or fixed block record A multiple of the record length
Variable record 4 bytes larger than the record length
Undefined record Larger than the largest record length
Default 800
XCOM.CNF Parameters
CARRIAGE_CONTROL_CHARACTERS
This indicates the type, if any, of printer carriage-control codes that are included
in the report file.
Note: For report transfers only.

Value Description
ASA ASA control codes in column 1.
IBM IBM Machine Characters (valid only for IBM mainframes).
BYPASSASA If data is already in ASA format, bypass conversion.
OTHER No carriage-control codes are used.
Default OTHER
CARRIAGE_FLAG
Specifies the type of file being transferred and some special characteristics of the
conversion done during the transfer.

Value Description
YES Indicates that the transferred file is a text file and a new-line
character should be added to the end of incoming records. Also,
new-line characters are removed from the ends of lines before an
outgoing record is sent.
When the TCP/IP protocol is specified, YES will be changed to
XPACK automatically, if the value of MAXRECLEN is less than
31K. If the value of MAXRECLEN is greater than or equal to 31744,
this value will not be changed automatically.
NO Indicates no special processing.
MPACK Indicates a text file with record packing. Uses 2K pack buffer.
When the TCP/IP protocol is specified, MPACK will be changed to
XPACK automatically, if the value of MAXRECLEN is less than
31K. If the value of MAXRECLEN is greater than or equal to 31744,
this value will not be changed automatically.
XCOM.CNF Parameters
Value Description
VLR Indicates a binary file of variable-length records with a field of 4
bytes preceding each record. Applies to local initiated transfers
only.
XPACK Indicates a text file with record packing. Uses 31K pack buffer.
Note: MPACK does not support a MAXRECLEN (actual record length) over 2K.
XPACK does not support a MAXRECLEN (actual record length) over 31K.
Default YES
CHECKPOINT_COUNT
Defines how often (based on record count) the sending system requests a
checkpoint to be taken. The value 0 indicates no checkpointing.
Note: Setting the CHECKPOINT_COUNT affects performance. Each time a
checkpoint is taken, the output buffers on the receiving system are written to the
disk. On Token Ring, Ethernet, and other high-speed networks, the
CHECKPOINT_COUNT should be set 0 or to the highest allowable value. The
CHECKPOINT_COUNT should not be set for small files.
Range 0 to 9999
Default 1000
CLASS
The print class assigned to a report transferred to a remote system.
If the remote system is an IBM mainframe, this field designates the JES SYSOUT
class.
Note: For report transfers only.
Example Enter B to print the report through SYSOUT=B.
Range 1 character
Default None
XCOM.CNF Parameters
CODE_FLAG
Used to identify the type of data being transferred.

Value Description
ASCII An ASCII file is being transferred. This indicates that the
incoming file is assumed to be ASCII format, and is not
translated. Therefore the file on the remote system should be
in ASCII format before it is transferred.
BINARY A binary file, such as an executable file, is being transferred.
This indicates to a remote system not to translate the data it is
exchanging with your system.
EBCDIC An EBCDIC file is being transferred. The transferred data is
translated from EBCDIC to ASCII format when the local
system receives the data, and from ASCII to EBCDIC format
when the local system sends the data.
Default ASCII
CODETABL
Specifies the 1- to 3-character prefix to the file names, ATOE.TAB and
ETOA.TAB, that contain the external ASCII-to-EBCDIC and EBCDIC-to-ASCII
custom character conversion tables on the Unicenter CA-XCOM Data Transport
for Windows NT and the Unicenter CA-XCOM Data Transport for UNIX
platforms. These custom character conversion tables determine which external
translation tables will be used when a transfer is sent to these platforms.
This parameter is valid only if INTERNAL_CONVERSION_TABLES=NO is set
on the receiving platform and the platforms are at r11 or above.
Range: 1 to 3 characters
Default: None
XCOM.CNF Parameters
COMPRESS
Indicates the compression type. When communicating with an IBM mainframe,
if the data file contains any empty lines, COMPRESS must be set to YES.
Note: All compression types are not supported on all platforms. For supported
compression types, see the partner platform documentation.

Value Description
COMPACT RJE compaction algorithm optimized for uppercase English
text.
LCOMPACT RJE compaction algorithm optimized for lowercase English text.
LZLARGE Activates LZ compression to search back 32K in the data stream
for a matching string.
LZMEDIUM Activates LZ compression to search back 16K in the data stream
LZRW3 General-purpose algorithm that runs fast and gives reasonable
compression.
LZSMALL Activates LZ compression to search back 4K in the data stream
NO Indicates no compression.
RLE Run length encoding.
YES Indicates run length encoding of binary zeros and blanks only.
ZLIB(n) Greater compression than LZRW3 but less than LZSMALL,
LZMEDIUM, and LZLARGE. The optional n value can be 1
through 9.
Note: The LZ values enable LZ (Lempel-Ziv) compression to replace sequences
of data bytes that occur more than once in a data stream with a code value.
Default YES
XCOM.CNF Parameters
CONTROL
For multiple transfers. Use the syntax for performing a single transfer and then
separate parameters for different transfers in the same configuration file by
using this parameter.
Range NEWXFER or NONE
Default NEWXFER
COPIES
The number of copies that are to be sent. If this parameter is not specified, the
remote system queues one copy of the report to the systems default printer. For
report transfers only.
Range 1 to 999
Default 1
DATACLAS
Specifies the name of the data class to use when allocating a new SMS-managed
data set.
Default None
DEN
Specifies the density used in creating a tape on the remote system. Valid values
are the same as those for the DEN parameter in JCL
Range 1 to 4
Default None
XCOM.CNF Parameters
DESTINATION
Identifies the printer or other device on the remote system where the report is to
be sent. If this parameter is not specified, the remote system sends the report to
the system's default printer. For report transfers only.

Value Description
0 to 16 characters For indirect transfers and when XCOM Version 1 protocol
is used.
0 to 21 characters For transfers that are not indirect and when XCOM
Version 2 protocol is used.
Default None
DESTINATION_TYPE
The type of target system.
Range HOST, MIDRANGE, or OTHER
Default OTHER
DISPOSITION
Indicates what the remote system does with the report file after the report has
been printed. For report transfers only.
Note: This field is not used when the remote system is an IBM mainframe.
Range

If the value is Then after printing the report is
DELETE Deleted
KEEP Kept
HOLD Held
Default DELETE
XCOM.CNF Parameters
DSNTYPE
Specifies the data set definition.

Value Description
LIBRARY Defines a PDSE
PDS Defines a partitioned data set
Note: These values are IBM standards for SMS processing.
Default None
EXPDT
Specifies the expiration date to be placed on the tape data set being created.

Value Definition
yyddd Specifies an expiration date for the tape data set as a two-digit
designation for the year and a three-digit designation for the day of
the year. For example, in the expiration date 03021, 03 is the year
(namely, 2003) and 021 is the 21st day of that year. The tape data set
will expire on January 21, 2003.
yyyy/ddd Specifies an expiration date for the tape data set in terms of a four-
digit designation for the year and a three-digit designation for the
day of the year. For example, in the expiration date 2004/021, 2004
is the year and 021 is the 21st day of that year. The tape data set will
expire on January 21, 2004.
Note: EXPDT and RETPD are mutually exclusive; specify one or the other.
XCOM.CNF Parameters
FCB
Identifies the FCB JCL parameter when sending the report file to an IBM
mainframe, defining print density, lines per page, and so forth. For report
transfers only.
Default None
FILE_ACCESS_USERNAME
Name of user accessing local files.
Default None
FILE_OPTION

Indicates how the transferred data is to be processed by the receiving system. For
file transfers only.

Value Description
CREATE Create a new file on the receiving system.
APPEND Append the transferred data to an existing file on the receiving
system.
REPLACE Replace an existing file on the receiving system.
XCOM.CNF Parameters
For library-type transfers, the range of values is as follows:

Value Description
CREATE Creates the PDS on the receiving system and adds the
transferred members. If the PDS already exists, the transfer will
fail. If the directory does not exist the reaction depends on the
value of CREATE_DIRECTORIES in the global file:
If CREATE_DIRECTORIES=YES , the transfer will create the
directory and add the transferred members.
CREATE_DIRECTORIES=NO, the transfer will fail
ADD
APPEND
Adds or replaces transferred members on the receiving system. If
the PDS does not exist, the transfer will fail. The value of
CREATE_DIRECTORIES will also determine the outcome of the
transfer on the remote system.
If CREATE_DIRECTORIES=YES and the directory does not
exist then the directory will be created and the transfer
members will be added to this directory. If the directory does
exist, the transfer members will be added to this existing
directory.
If CREATE_DIRECTORIES=NO and the directory does not
exist, then the transfer will fail. If the directory does exist,
then the transfer will add the transfer members to the
directory.
REPLACE Adds or replaces transferred members. If the directory does not
exist the reaction depends on the value of
CREATE_DIRECTORIES in the global file:
If CREATE_DIRECTORIES=YES, the transfer will create the
CREATE_DIRECTORIES=NO, the transfer will fail
Note: The DirTree feature does not support SUSPEND and RESUME transfers
using wildcards.
Default CREATE
Note: When creating a file on an IBM mainframe system, some additional
information may be necessary. For more information, see RECORD_FORMAT,
BLKSIZE, VOLUME, and UNIT in this chapter.
XCOM.CNF Parameters
FILE_OPTION_RF
Indicates how the transferred data is to be processed by the receiving system.
Used when the transfer type is Retrieve File. If no value is specified, then the
value defaults to CREATE.

Value Description
CREATE Create a new file on the receiving system.
APPEND Append the transferred data to an existing file on the
receiving system.
REPLACE Replace an existing file on the receiving system.
For library-type transfers, the range of values is as follows:

Value Description
CREATE Creates the PDS on the receiving system and adds the
transferred members. If the PDS already exists, the transfer will
fail. If the directory does not exist the reaction depends on the
value of CREATE_DIRECTORIES in the global file:
CREATE_DIRECTORIES=NO, the transfer will fail.
ADD
APPEND
Adds or replaces transferred members on the receiving system.
If the PDS does not exist, the transfer will fail. The value of
CREATE_DIRECTORIES will also determine the outcome of the
transfer on the remote system.
If CREATE_DIRECTORIES=YES and the directory does not
exist then the directory will be created and the transfer
members will be added to this directory. If the directory does
exist, the transfer members will be added to this existing
directory.
If CREATE_DIRECTORIES=NO and the directory does not
exist, then the transfer will fail. If the directory does exist,
then the transfer will add the transfer members to the
directory.
XCOM.CNF Parameters
Value Description
REPLACE Adds or replaces transferred members. If the directory does not
exist the reaction depends on the value of
CREATE_DIRECTORIES in the global file:
CREATE_DIRECTORIES=NO, the transfer will fail.
Note: The DirTree feature does not support SUSPEND and RESUME transfers
using wildcards.
Default CREATE
FORM
The type of form that should be used to print the report. Since Unicenter
CA-XCOM Data Transport places the print job in the remote system's print
queue, the print control functions depend on the remote system. The user must
verify beforehand that the requested form is available at the remote site. For
Note: When sending a report to a VAX computer, leave this parameter blank
unless you are certain that this is a valid form type. VMS interprets this to mean
that no special form is being requested.
Default None
HOLDFLAG
Indicates whether a transferred report file is to be placed on HOLD on the
remote system or is to be printed immediately. For report transfers only.
Range YES or NO
Default NO
XCOM.CNF Parameters
LABEL
Indicates the type of label associated with a tape data set.
Range The following table lists the valid values for this parameter:

Value Definition
Processing type:
AL, AUL, BLP, LTM,
NL, NSL, SL, SUL
Represent the types of processing to be applied to data
sets on tape.
Default: none
Note: Unicenter CA-XCOM Data Transport for z/OS supports only standard
label tapes.
Example: LABEL=BLP
The type of processing to be applied to this data set is BLP.
Default SL
LABELNUM
Indicates the sequence number of the data set on the tape.
Range The following table lists the valid values for this parameter:

Value Definition
sequence number
(1 to 9999)
This value identifies the sequence number of a data set on
tape.
Example: LABELNUM=2
This specification refers to the second data set on the tape.
Default 1
XCOM.CNF Parameters
LCLNTFYL
Specifies the local user notification level.

Value Description
Default ALL
LOCAL_FILE
The name of the file on the local system that is being transferred. At the
command prompt or in a script, if this variable is null or unset, standard input is
read. In this manner, Unicenter CA-XCOM Data Transport commands can be
used in a pipeline or with redirection. All Windows and UNC file naming
conventions apply.
Note: If QUEUE=YES, user must specify full path name.
Default None
LOCAL_FILE_RF
The file name that is created, appended, or replaced on the local system when it
receives a file. At the command prompt or in a script, if this value is null or
unset, then Unicenter CA-XCOM Data Transport writes to the standard out file.
All Windows and UNC file naming conventions apply.
Default None
XCOM.CNF Parameters
LOCAL_FILE_SJ
Indicates the name of the file on the local system to be sent as a job. At the
command prompt or in a script, if this variable is null or unset, standard input is
read. All Windows and UNC file naming conventions apply.
Default None
LOCAL_FILE_SR
Local file name to be sent as a report to the remote system. At the command
prompt or in a script, if this value is null or unset, then Unicenter CA-XCOM
Data Transport reads the standard input file. All Windows and UNC file naming
conventions apply. For report transfers only.
Default None
LOCAL_NOTIFY
Specifies the user on the local system who is to be notified that Unicenter
CA-XCOM Data Transport has completed a transfer. Unicenter CA-XCOM Data
Transport uses the NOTIFYL parameter to determine the type of notification to
use.
Default None
XCOM.CNF Parameters
LRECL
Specifies the actual or maximum length, in bytes, of a logical record.
Corresponds to the JCL LRECL subparameter.
Range 0 to 32767

If the format is Then the maximum length of a logical record
must be equal to the
Variable blocked record Maximum record length plus 4
Fixed or fixed block record Constant record length
Default 160
MAXRECLEN
For Windows and UNIX systems, the locally initiating Unicenter CA-XCOM
Data Transport system determines the values for MAXRECLEN, TRUNCATION,
and LRECL, for send and receive operations. When the local Unicenter
CA-XCOM Data Transport system initiates a transfer of a text file, this parameter
designates the length, in bytes, of the largest record, which can be transferred. If
a record length is longer than this value, Unicenter CA-XCOM Data Transport
uses the value in the TRUNCATION parameter on the initiating side to
determine whether to terminate the transfer or to truncate the record and
continue the transfer. When Unicenter CA-XCOM Data Transport transfers
binary files, this value indicates the length of the records that are transferred. On
a receive operation, MAXRECLEN is set to whatever the LRECL value is on the
initiating side.
Range 1 to 32767
Default 1024
MGMTCLAS
Specifies the name of the management class to use when allocating a new SMS-
managed data set.
Default None
XCOM.CNF Parameters
NOTIFY_NAME
The user on the remote system who is to be notified when Unicenter CA-XCOM
Data Transport completes a transfer.
Note: If the remote system is an IBM mainframe, Unicenter CA-XCOM Data
Transport uses the value of NOTIFYR to determine the type of notification to
deliver.
Default None
NOTIFYL
The local user notification flag.

Value Description
WRITE A message is displayed on the workstation where the user is logged
in.
MAIL A MAIL message is sent to the user.
NONE No notification is sent.
ALL A message is displayed on the local Windows system console.
Default NONE
Note: The L in NOTIFYL indicates that the local system governs the processing
of the resulting notification on that system.
NOTIFYR
Specifies the remote user notification type when sending data to a remote
system.

Value Description
WRITE A message is displayed on the screen.
MAIL A mail message is sent to the user.
XCOM.CNF Parameters
Value Description
TSO The specified TSO user is notified.
WTO Unicenter CA-XCOM Data Transport writes to the log only (WTO).
CICS The specified CICS user is notified (not used for Version 1 type
transfers).
LU The specified Logical Unit is notified (not used for Version 1 type
transfers).
ALL A message is displayed on the remote Windows system console.
NONE No notification is sent.
ROSCOE Notify Advantage CA-Roscoe user.
Default NONE
Note: The R in NOTIFYR indicates that the remote system governs the
processing of the resulting notification on that system.
NOTIFY_TERM
Specifies terminals to write if NOTIFYL=WRITE. If NOTIFY_TERM is not set, all
users specified in LOCAL_NOTIFY will be notified at the first terminal where
they are logged in as found in the system table.
Default None
NUM_OF_DIR_BLOCKS
Specifies the number of directory blocks to allocate for a data set created on an
IBM mainframe.
Range 0 to 32767
Default 0
XCOM.CNF Parameters
NUMBER_OF_RETRIES
Indicates the maximum number of retries before a transfer is logged as failed. If
the value is 0, the transfer will not be retried.
Range 0 to 255
Default 1
PASSWORD
The password associated with the user ID on a remote system.
Default None
PORT
The number of the TCP/IP port on the remote Unicenter CA-XCOM Data
Transport server. Used for TCP/IP transfers only.
Range 1 to 65535
Default 8044
PRIMARY_ALLOC
Identifies primary storage allocation for a data set created on an IBM mainframe.
Range 0 to 99999
Default 1
XCOM.CNF Parameters
PRIORITY
Indicates the priority that Unicenter CA-XCOM Data Transport uses for
scheduling a transfer. If two transfers are scheduled for the same time, the one
with the high priority is processed before one with a normal or low priority.

Value Description
HIGH Set high priority.
NORMAL Set medium priority.
LOW Set low priority.
Default NORMAL
PROTOCOL
The type of communication protocols to use.

Value Description
SNA For transfers using SNA/APPC communication protocols
TCPIP For transfers using TCP/IP communication protocols
Default SNA
Unicenter CA-XCOM Data Transport, the default value is TCPIP.
XCOM.CNF Parameters
QUEUE
Indicates whether to execute the transmission request immediately or to allow
the request to be queued. If the user does not specify a .cnf file, and has not
changed a .cnf file, the default value is "YES."
Note: If NO is specified and the remote system is unavailable, the request aborts.
If YES is specified, START_TIME and START_DATE are read.

Value Description
YES The transfer request goes into a queue and executes depending on
the traffic in the queue and START_DATE and START_TIME.
NO The transfer starts immediately.
Default YES
RECORD_FORMAT
Specifies the record format of a data set created on an IBM mainframe. This
corresponds to the JCL RECFM subparameter. This field is unique to the Edit
Transfer - Send File Window.

Value Description Record
Length
Comment
F Fixed
unblocked
The same
length as the
data set

FA Fixed
unblocked
ANSI
The same
length as the
data set
Contains ISO/ANSI/FIPS control
characters
FB Fixed blocked Fixed Fixed record length with multiple
records per block
FBA Fixed blocked
ANSI
Fixed Multiple records per block where
these records contain
ISO/ANSI/FIPS control characters
FBS Fixed blocked
spanned
Fixed Multiple records per block written
as standard blocks
XCOM.CNF Parameters
Value Description Record
Length
Comment
FM Fixed
unblocked
machine
The same
length as the
data set
Contains machine code control
characters
FS Fixed
unblocked
spanned
The same
length as the
data set
Written as standard blocks where
these records do not contain any
truncated blocks or unfilled tracks
U Undefined Undefined
V Variable
unblocked
Variable
VA Variable
unblocked
ANSI
Variable Contains ISO/ANSI/FIPS control
characters
VB Variable
blocked
Variable Multiple records per block
VBA Variable
blocked ANSI
Variable Multiple records per block where
these records contain
ISO/ANSI/FIPS control characters
VBM Variable
blocked
machine
Variable Multiple records per block where
these records contain machine code
control characters
VBS Variable
blocked
spanned
Variable May have multiple records per
block where these records can span
more than one block
VM Variable
unblocked
machine
Variable Contains machine code control
characters
VS Variable
unblocked
spanned
Variable A record can span more than one
block
Default VB
XCOM.CNF Parameters
REMOTE_FILE
Indicates the file on the remote computer to which the transferred data is being
written. If you are creating the file (FILE_OPTION=CREATE), the file name must
be consistent with the file naming conventions of the remote system. The local
Unicenter CA-XCOM Data Transport system does not validate this name. The
remote I/O system determines whether the file name is valid.
Note: For send file transfers only.
Default None
REMOTE_FILE_RF
Indicates the name of the file to be retrieved from the remote system.
Note: For retrieve file transfers only
Default None
REMOTE_SYSTEM
The name of the remote system that receives a file, job or report.
For SNA/APPC protocols, the name is the symbolic destination name from the
CPI-C side information record.
For TCP/IP protocols, the value can be the remote systems IP address, host
name, or domain name.
Default None
XCOM.CNF Parameters
REMOTE_SYSTEM_RF
The name of the remote system that sends a file on a receive file operation.
Default None
REMOTE_SYSTEM_SJ
The name of the remote system to which a job is sent.
Default None
REMOTE_SYSTEM_SR
The name of the remote system to which a report is sent.
Default None
XCOM.CNF Parameters
REMOVE_TRAIL_BLANKS
Indicates whether or not to remove the blanks at the end of each record when
receiving a text file.
Range YES or NO
Default NO
REPORT_TITLE
Used by Unicenter CA-XCOM Data Transport on remote systems in the
following ways:

System Uses the REPORT_TITLE
AS/400 To assume this to be the printer file name.
z/OS To interpret a non-blank value in this field as specifying the
generation of a separator (banner) page for this value.
VAX/VMS To print with the report.
UNIX To allow Unicenter CA-XCOM Data Transport to pass this
field to the LP spooler as a title field.
Other systems As a descriptive comment only and does not print it as part
of the report.
Range 0 to 21 alphanumeric or blank characters
Default None
RESTART_SUPPORTED
Specifies whether automatic restart is to be supported on a transfer.
Range YES or NO
Default YES
XCOM.CNF Parameters
RETPD
Specifies the number of days that the tape data set being created is to be retained.
Range 1 to 9999
Default None
Note: RETPD and EXPDT are mutually exclusive; specify one or the other.
RETRY_TIME
The number of seconds between retries of unsuccessful transfers. If the value is
0, the transfer is retried without delay.
Range 0 to 99999
Default 1
RMTNTFYL
Specifies the remote user notification level when sending data to a remote
system.

Value Description
Default ALL
XCOM.CNF Parameters
SECONDARY_ALLOC
Identifies secondary storage allocation for a data set created on an IBM
mainframe.
Range 0 to 99999
Default 1
SECURE_SOCKET
Specifies whether to use an OpenSSL socket or non-OpenSSL socket for transfers.

Value Description
YES Performs secure transfer.
The transfer uses an OpenSSL socket and must to connect
to a SSL listener on the remote partner.
NO Performs non-secure transfer.
The transfer uses a non-OpenSSL socket.
Default NO
XCOM.CNF Parameters
SPACE
The unit of storage allocation for the remote file.

Value Description
CYL Cylinders
TRK Tracks
BLK Blocks
Specify by:
Primary allocation space for the remote file
Secondary allocation for the remote file
Directory blocks for the remote file
Default CYL
SPOOL_FLAG
Indicates whether the report is to be spooled to disk or printed immediately. For
Note: If the remote system is an IBM mainframe, this parameter has no effect on
the transfer.
Range YES or NO
Default YES
START_DATE
Indicates the date on which the transfer becomes eligible for execution. The
format is mm/dd/yy. If this field is blank, the current date is used.
Example A value of 02/21/03 indicates February 21, 2003 as the start date.
Range mm/dd/yy
Default None
XCOM.CNF Parameters
START_TIME
Indicates the time when the transfer becomes eligible for execution. The military
format of hh:mm:ss is used. If this field is blank, then the current time is used.
Example A value of 14:00:00 indicates 2 p.m. as the start time.
Range hh:mm:ss
Default None
STORCLAS
Specifies the name of the storage class for a new SMS-managed data set.
Default None
TAPE
Indicates to the remote system whether the volume is a tape volume or a disk
file.

Value Definition
YES Indicates that the transfer is to a tape volume and that mounts are
allowed when performing dynamic allocation.
NO Indicates that the transfer is to a disk file.
Default None
TRANSFER_ID
Allows the user to enter information to identify the file transfer request.
Default None
XCOM.CNF Parameters
TRANSFER_TYPE
Generated by the graphical user interface to specify the type of transfer to
initiate.
Can also be used in a configuration file that has multiple transfers in it, to specify
a different transfer type from the default value.
Range 1 to 4

Value Description
1 Send job
2 Send report
3 Send file
4 Receive file
Default 3
Note: The functionality of this parameter is similar to using the -cNUMBER
command with XCOM62 or XCOMTCP at the command line. However, the
values used to indicate the type of transfer are different.
TRANSFER_USR_DATA
An open field where a user can specify any text associated with the transfer.
Default None
TRUNCATION
Indicates whether Unicenter CA-XCOM Data Transport truncates excess
characters in the source file if the record exceeds the maximum record length as
indicated by the MAXRECLEN parameter. If NO is selected, and the maximum
record length is exceeded, Unicenter CA-XCOM Data Transport aborts the
transfer. This parameter is ignored if CARRIAGE_FLAG=NO.
Note: Truncation is not applicable to binary data.
Range YES or NO
Default NO
XCOM.CNF Parameters
TRUSTED
To allow the user to request a trusted transfer.
Range YES, NO, Y, or N
Default None
UNIT
Specifies to a remote system (primarily an IBM mainframe) the unit on which a
dataset is to be created.
Default None
UNITCT
Specifies the number of units to be allocated on the remote system.
Range 1 to 20
Default None
UNIT_RF
Specifies the unit from which a data set is to be retrieved from an IBM
mainframe.
Default None
USER_DATA
An open field where a user can specify any text associated with the transfer.
Default None
XCOM.CNF Parameters
USERID
The user ID which the security system on a remote system checks before
granting access for the file transfer.
Default None
VERSION
Indicates the version of the Unicenter CA-XCOM Data Transport protocol to be
used for this transfer. For using TCP/IP, only a value of 2 is valid.
Range 1 or 2
Default 2
VOLCT
Specifies the maximum number of volumes to be used in processing a
multivolume output tape data set on the remote system.
Range 1 to 225
Default None
VOLSQ
Specifies the sequence number of the first volume of a multivolume remote data
set to be used.
Range 1 to 225
Default None
XCOM.CNF Parameters
VOLUME
Specifies the volume on which a dataset is to be created on an IBM mainframe.
Default None
VOLUME_RF
Specifies the volume from which a data set is to be retrieved from an IBM
mainframe.
Default None
XCOM_CONFIG_SSL
This parameter specifies the value of the configssl.cnf file path and file name.
Default C:\XCOMNT\CONFIGSSL.CNF
XIDEST
Specifies the name of the remote system on the intermediate destination that is
designated for store-and-forward transfers. If this variable is null or unset, then a
direct connection to a remote system is attempted.
Note: For store-and-forward transfers only.
Default None
XLUNAME
Indicates the name of the local LU. This name must match the remote LU name
on the remote system.
XCOM.CNF Parameters
Default None
Note: Not used in Unicenter CA-XCOM Data Transport for RS/6000 SNA
Services or RS/6000 SNA Server.
XMODE
Indicates the mode name associated with the SNA/APPC configuration for the
XLUNAME-Remote LU name pair. This name must match the mode name
defined on the remote system.
Default XCOMMODE
XNODESPEC
Required for Brixton and SunLink APPCs. Indicates the name of the node that
specifies the gateway to use for the transfer. Does not apply to other APPCs.
Default None
XTRACE
Indicates the level of desired execution tracing.

Value Definition
0 No tracing.
1 to 8 Levels of tracing from 1 (lowest) to 8 (highest).
9 Show the contents of the data buffers.
10 Includes levels 1 to 9, plus some additional detailed technical
information.
Default 0
Creating the CA-XCOM-Batch-Interactive Group
Creating the CA-XCOM-Batch-Interactive Group
We strongly recommend creating the CA-XCOM-Batch-Interactive group. Not
creating this group can result in dll initialization failures as well as affecting
sendjobs and pre- and post-processing scripts. All jobs and scripts received by
Unicenter CA-XCOM Data Transport are submitted to the operating system by
creating a new process. The new process will run in the security context of the
user receiving the transfer that caused the process to be created. Unicenter
CA-XCOM Data Transport adds an access control entry to the window station
and desktop to allow the process to interact with the user. Once the process is
complete the entry point is removed from the window station and desktop. If the
process created by the transfer creates an additional process, this additional
process will not have access to the window station or desktop after Unicenter
CA-XCOM Data Transport has removed the entry control point created by the
original process.
To allow this additional process to interact with the user, create a local group
named CA-XCOM-Batch-Interactive and include the user receiving the transfer
in it. Unicenter CA-XCOM Data Transport will add an access control point to the
window station and desktop that will not be removed when the initial process
completes.
In Windows, use the Administrative Tools, User Manager dialog to create the
CA-XCOM-Batch-Interactive group.
In Windows 2000, 2003 or XP, use the Computer Management, Local Users, and
Groups dialog to create the CA-XCOM-Batch-Interactive group.
Enter the group name as CA-XCOM-Batch-Interactive. Click the Add button to
add users to the group. Consider the following points when creating this group:
Any user whose Unicenter CA-XCOM Data Transport transfer starts a
background job that interacts with the window station or desktop must be a
member of this group.
The only access permitted by this group is to the window station and
desktop.
Local group names are case-sensitive.
Starting and Stopping the XCOMD Unicenter CA-XCOM Scheduler Service
Starting and Stopping the XCOMD Unicenter CA-XCOM
Scheduler Service
Use the Windows control panel and the Services icon to start and stop the
XCOMD Unicenter CA-XCOM Scheduler service.
XCOMD Unicenter CA-XCOM Scheduler Service
The XCOMD Unicenter CA-XCOM Scheduler service runs as a background
process to control file transfers and manage Unicenter CA-XCOM Data
Transport resources. The XCOMD Unicenter CA-XCOM Scheduler service:
Schedules and synchronizes transfer requests
Controls shared memory for transfers
Establishes the default parameter values by reading the parameter file,
XCOM.GLB
Controls the automatic restart of locally initiated transfers
Writes queue information out to disk periodically
Deletes aged entries from the queue
Notifies a local user by executing the XCOMNTFY script when
LOCAL_NOTIFY is required
Communicates with active or pending transfers to terminate a transfer
Considerations
When Unicenter CA-XCOM Data Transport is installed, only administrative
users with user rights to start and stop Windows services can start and stop the
XCOMD Unicenter CA-XCOM Scheduler service. Other users are normally
The XCOMD Unicenter CA-XCOM Scheduler service must be running before
you can do any transfers.
A transfer runs as an application under the control of the XCOMD Unicenter
CA-XCOM Scheduler service. If XCOMD Unicenter CA-XCOM Scheduler
service is running, the user does not have to be logged on for a scheduled
transfer to be processed. That is, you can schedule a transfer and log off, and it
will run as scheduled. Likewise, a remotely initiated transfer can be processed
without the local user being logged on, as long as the XCOMD Unicenter
CA-XCOM Scheduler service is running.
Starting XCOMD Unicenter CA-XCOM Scheduler Service
Important! For information about stopping services on Windows NT, Windows 2003,
and Windows XP, see your Windows documentation.
To start the XCOMD Unicenter CA-XCOM Scheduler service on Windows 2000,
do the following:
1. From the Windows Start menu, select Settings, Control Panel,
Administrative Tools, Computer Management.
2. From the Computer Management explorer, select Services and Applications,
Services.
A list of services is displayed in the right panel similar to the one displayed
here:

3. Scroll through the list of services, highlight XCOMD Unicenter CA-XCOM
Scheduler.
4. Do one of the following:
Select Start from the Actions Menu.
OR
Double-click the XCOMD Unicenter CA-XCOM Scheduler service name
and click the Start button on the resulting panel.
Note: To have the XCOMD Unicenter CA-XCOM Scheduler service start
automatically when the system boots up, you change the Startup type
option to Automatic on this panel.
5. Close the Services window and the Control Panel window.
If you attempt to start the service and a service-specific error number is
displayed, the number refers to a Unicenter CA-XCOM Data Transport error
message. If the service-specific error number 650 is displayed, you did not reboot
the system after installing Unicenter CA-XCOM Data Transport. For installation
changes to take effect, you must shut down and restart the system.
For a list of XCOMD Unicenter CA-XCOM Scheduler service-specific messages,
see Service-Specific Messages in the appendix Messages in the Unicenter
CA-XCOM Data Transport for Windows NT Server/Professional User Guide.
Stopping XCOMD Unicenter CA-XCOM Scheduler Service
To stop the XCOMD Unicenter CA-XCOM Scheduler service on Windows 2000,
do the following:
1. From the Windows Start menu, select Settings, Control Panel,
Administrative Tools, Computer Management.
2. From the Computer Management explorer, select Services and Applications,
Services.
A list of services is displayed in the right panel similar to the following one:

3. Highlight XCOMD Unicenter CA-XCOM Scheduler.
4. Do one of the following:
Select Stop from the Actions Menu.
Double-click the XCOMD Unicenter CA-XCOM Scheduler service name
and click the Stop button on the resulting panel.
5. Close the Services window and the Control Panel window.
Tracing Unicenter CA-XCOM Data Transport Scheduler Service
The following steps assume C:\xcomnt is the directory location where Unicenter
CA-XCOM Data Transport is installed and where the DOS prompt path is
currently logged into. If this is not the case, then it will be necessary to change
the drive and path to where Unicenter CA-XCOM Data Transport is installed at
your site.
1. Enter the following command at the prompt:
card3 on
The following message is displayed, indicating that the trace facility is
enabled:
CA-XCOM daemon trace facility now enabled.
2 Stop the XCOMD Unicenter CA-XCOM Scheduler service if it is currently
running. See Stopping XCOMD Unicenter CA-XCOM Scheduler Service in
this chapter.
3. For Windows NT 4.0, select XCOMD Unicenter CA-XCOM Scheduler service
and enter -d9 in the Startup Parameters field.
For Windows 2000, 2003, or XP, select Action from the menu bar, and then
select Properties. Enter d9 in the Start parameters field.
4. Restart the XCOMD Unicenter CA-XCOM Scheduler service.
Note: The CA Trace icon appears in the TaskBar.
5. Stop the XCOMD Unicenter CA-XCOM Scheduler service.
Note: The CA Trace icon disappears from the TaskBar.
A trace file is created in C:\xcomnt\trace\trace.trc (if you select the default
directory).
6. Enter the following command at the prompt:
card3 off
The following message is displayed, indicating that the trace facility is
disabled.
CA-XCOM daemon trace facility now disabled.
Note: Setting trace options may generate large files of trace data.

Chapter
3
Using Unicenter CA-XCOM Data
Transport with TCP/IP

To use TCP/IP protocols with Unicenter CA-XCOM Data Transport, note the
following:
Your computer must be configured for TCP/IP for you to use TCP/IP
protocols with Unicenter CA-XCOM Data Transport.
You must log on as a member of the Administrators group to change
network settings for TCP/IP.
Unicenter CA-XCOM Data Transport must be installed and running before
you can perform transfers using TCP/IP.
Note: If your computer is not configured for TCP/IP, check with your network
administrator for the appropriate values and see the Microsoft Windows System
Guide for more information.
What You Need
To configure Unicenter CA-XCOM Data Transport for using TCP/IP you need to
know the following information. Check with your network administrator, and
refer to the TCP/IP worksheet for these values.
The IP address of your computer.
If you are using host names and domain names, you need to know these
names for your system as well.
Before performing a file transfer, you need the IP address, the host name, or
the domain name of the remote system.
Unicenter CA-XCOM Data Transport must be configured with the
appropriate Port and Protocol specifications. For further information about
Port and Protocol, see Using TCP/IP Protocols with Unicenter CA-XCOM
Data Transport in this chapter.
Using Unicenter CA-XCOM Data Transport with TCP/IP 31
What You Need
In addition, if your system is not configured for TCP/IP, you need the following:
The Subnet Mask for your network adapter.
The IP address of the default Gateway or IP router. This is the IP address of
the local gateway.
Check with your network administrator for these values.
TCP/IP Worksheet
TCP/IP Worksheet
Use the following worksheet to collect information for use in configuring
Unicenter CA-XCOM Data Transport to perform transfers using TCP/IP.
Note: When specifying a remote system for a Unicenter CA-XCOM Data
Transport transfer using TCP/IP, you can use the remote systems IP address,
host name, or domain name.

Term/Concept Values for
Configuring Your
Computer
Values for Specifying
the Remote System
IP address
A unique number for a
particular computer, used to
identify the computer on the
TCP/IP network. IP
addresses are in the dotted
decimal notation format.
Example:
123.123.78.91

Host name
The host name of a particular
computer.
Example:
GOODSYS

Domain name
The Domain Name Service
(DNS) name. Identifies the
computers group in the DNS
hierarchy. The host name and
the domain name make up
the fully qualified domain
name of the computer.
Example:
GOODSYS.GOODSITE.COM
GOODSYS is the name of the
computer, and it is in the
GOODSITE.COM domain.

Using TCP/IP Protocols with Unicenter CA-XCOM Data Transport
Using TCP/IP Protocols with Unicenter CA-XCOM Data
Transport
If you want to use TCP/IP protocols for a Unicenter CA-XCOM Data Transport
transfer, Unicenter CA-XCOM Data Transport must have the following:
The Port specification for the remote system
An indication that you wish to use TCP/IP protocols
If the transfer you are performing uses a protocol value for SNA/APPC or
TCP/IP that is different from the default value, you must know which protocol
to use.
If you are performing a TCP/IP transfer that requires a port value for the remote
system that is different from the default value, you must know that port value.
The port of the remote system is specified by the PORT parameter or in the GUI.
The default value in the XCOM.GLB file should be valid for most remote hosts.
For more information, see Specifying Protocol and Port in the GUI in this
chapter. For information about modifying the local systems port value, see
Changing the Local System Port Value in this chapter.
The choice of protocol to use is indicated by the PROTOCOL parameter. This can
be specified in the GUI, at the command line, in a configuration file, or in the
XCOM.GLB file, depending upon your installations needs. If the protocol is not
specified at the command line or changed in the GUI, the defaults specified in
the configuration file or in XCOM.GLB are used.
Specifying Protocols Using the Command Line
When using the XCOM62 or XCOMTCP commands, the choice of protocol to use
is indicated by the PROTOCOL parameter. This can be specified at the command
line, in a configuration file, or in the XCOM.GLB file, depending upon your
installations needs. If the protocol is not specified at the command line, the
defaults specified in the configuration file or in XCOM.GLB are used.
Example In the following example, the XCOMTCP command is used to queue a file for a
send file transfer, using TCP/IP. The configuration file is MYCONFIG.CNF, the
local file is named TESTA.AAA, and the remote file is named TESTB.BBB. The
remote system is indicated by the host name GOODSYS in the
REMOTE_SYSTEM parameter. QUEUE is set to YES, so the transfer is queued.
TCP/IP is indicated by the value TCPIP in the PROTOCOL parameter. The port
is determined by the value of the PORT parameter in the XCOM.GLB file.
XCOMTCP -c1 -f MYCONFIG.CNF LOCAL_FILE=TESTA.AAA
REMOTE_FILE=TESTB.BBB REMOTE_SYSTEM=GOODSYS
QUEUE=YES PROTOCOL=TCPIP
Note: The example above appears on more than one line here but is to be typed
at the command prompt as a continuous command. Press ENTER only after you
have typed in all of your command information.
For more examples, see the Unicenter CA-XCOM Data Transport for Windows NT
Specifying Protocol and Port in the GUI
When specifying protocol and port values to initiate a transfer in the GUI, use
the Version 2 option dialog. Access the Version 2 option dialog from the Options
group box on any Edit Transfer window. This displays the Protocol and Port
options that can be modified as indicated in the following procedure.

For complete information about performing transfers and using the GUI
interface of Unicenter CA-XCOM Data Transport, see the Unicenter CA-XCOM
Protocol Defaults
The protocol default depends on which components of Unicenter CA-XCOM
Data Transport have been installed with the base components of the product.

If you install The Default Protocol is
The SNA component and the
TCP/IP component
SNA
The SNA component only SNA
The TCP/IP component only TCP/IP
Procedure - Protocol/Port
Use the following procedure to modify the values for initiating transfers with a
remote system for either Protocol or Port or both, if you are changing the default
values.
To access the Version 2 window, follow these steps:
1. With Unicenter CA-XCOM Data Transport active, open an existing
configuration file, or click the Add option button to create a new transfer.
2. Highlight the transfer entry on the Main window that you wish to modify,
and then double-click the transfer entry.
3. Click the Version 2 option button to display the Version 2 window.
To modify the values for Protocol or Port, or both, follow these steps:
1. Select the SNA/APPC option button for a transfer using SNA/APPC, or
select the TCP/IP option button for a transfer using TCP/IP.
The protocol is specified. If you selected TCP/IP, the Port option becomes
available.
Note: If the SNA/APPC option is selected, the Port option is dimmed, and is
unavailable.
2. If you are required to change the Port for the remote system, specify the port
number in the Port option box.
The Port is specified for a TCP/IP transfer.
Note: The default value for Port should be valid for most remote hosts.
3. Click OK.
The options are specified and the Edit Transfer window is displayed.
Specifying the Remote System
When using TCP/IP, the remote system can be specified in different ways. For
example, you can use the following forms:
By host name:
REMOTE_SYSTEM=GOODSYS
By fully qualified domain name:
REMOTE_SYSTEM=GOODSYS.GOODSITE.COM
By IP address:
REMOTE_SYSTEM=123.123.78.91
Using the IP address is the most efficient method to use when specifying a
remote system location.
Note: The examples above use the REMOTE_SYSTEM parameter, but the usage
applies to REMOTE_SYSTEM_RF, REMOTE_SYSTEM_SJ, and
REMOTE_SYSTEM_SR, and to the remote system options on the GUI as well.
TCP/IP Name Resolution
If you use a host name or domain name, your system must have a way to resolve
that name to an IP address.
You can use any symbolic name that can be mapped to an IP address, such as a
host name or a domain name. Your system must be set up to resolve the name to
an IP address. Check with your network administrator for further information
about your systems use of names.
If you are relying on name resolution to resolve names to IP addresses, this
capability must be installed and configured on your system. There are many
ways to implement name resolution, including the Domain Name Service (DNS),
and the use of host files.
For more information about name resolution, see the Microsoft Windows System
Guide.
Changing Global Values in Properties Dialog Pages
The Global parameters option of the Tools menu can be used to access the
Unicenter CA-XCOM Data Transport for Windows NT Properties dialog pages
to modify the default values of global parameters.
WARNING! The values of the options on the Properties dialog pages should be changed
by authorized Unicenter CA-XCOM Data Transport administrators only. Most users
will not need to change these values. The values should not be changed or deleted
unnecessarily. If any of these values are deleted unnecessarily, the results are
unpredictable.
For more information about the Properties dialog pages, see Using the Properties
Dialog Pages in the chapter Using Unicenter CA-XCOM Data Transport in the
Unicenter CA-XCOM Data Transport for Windows NT Server/Professional User
Guide.
Properties Dialog Pages
From the Unicenter CA-XCOM Data Transport for Windows NT Main window,
select the Tools menu, and then the Global parameters option to display the
Unicenter CA-XCOM Data Transport for Windows NT Properties dialog.
Changes made to these system parameters affect the values in XCOM.GLB and
in the Windows NT Registry. While you can make changes directly to the
XCOM.GLB file and to the Registry, we recommend that you modify these
values when necessary by using the Unicenter CA-XCOM Data Transport for
Windows NT Properties window.
Note: After making changes to the values on the Properties dialog pages, you
will have to stop and start XCOMD Unicenter CA-XCOM Scheduler Service for
the changes to take effect.
Changing the Local System Port Value
If you have a port conflict on the local machine, you can change the value of the
local systems port for incoming transfers, as follows:
From the Unicenter CA-XCOM Data Transport for Windows NT Main window,
select the Tools menu, and then the Global parameters option. When the
Unicenter CA-XCOM Data Transport for Windows NT Properties dialog is
displayed, select the TCP/IP tab. In the Server Settings group box of the TCP/IP
page, the Port Number option box is used to specify the port of the local
machine. Note that the default value in the XCOM.GLB file should be valid for
most local systems. After you specify the value in the Port Number option box,
click OK or Apply to update the values. The values are updated in the
XCOM.GLB file and in the Windows NT Registry.
Other TCP/IP Parameters
Unicenter CA-XCOM Data Transport also uses other parameters for TCP/IP
functionality. These parameters will be of interest to system administrators for
tuning and performance considerations, and they can be modified from the
Properties dialog pages. These parameters include the following:
SOCK_DELAY
SOCK_RCV_BUF_SIZE
SOCK_SEND_BUF_SIZE
TXPI_BUF_SIZE
TXPI_SEND_CHECK_FREQ
TXPI_RECEIVE_TIMEOUT
TXPI_TERM_TIMEOUT
For a description of these parameters, see XCOM.GLB Parameters in the chapter
Configuring Unicenter CA-XCOM Data Transport. For a list of these
parameters, see the appendix Logical Units in the Unicenter CA-XCOM Data
Transport for Windows NT Server/Professional User Guide.

Chapter
4
Operating Environment

The components discussed in this chapter are used for scheduling transfers,
handling files, and managing Unicenter CA-XCOM Data Transport resources.
The topics covered are the global parameters, the XCOMD Unicenter CA-XCOM
Scheduler service, the session control parameters, the queue, and the use of
Unicenter CA-XCOM Data Transport scripts. This chapter is primarily of interest
to Unicenter CA-XCOM Data Transport administrators.
Unicenter CA-XCOM Data Transport Global Variables
A substantial portion of a users ability to control Unicenter CA-XCOM Data
Transport comes from the use of files to set variables that govern the system's
behavior. These files are XCOM.GLB and XCOM.CNF. These files can be
modified with any text editor that generates ASCII text. In addition, commonly
used XCOM.GLB parameters can be modified using the Properties Dialog pages
of the GUI. We recommend that user rights to these files be controlled by an
administrator.
Considerations
Before modifying components and global parameters of Unicenter CA-XCOM
Data Transport you should see File Name, PATH, and Directory Considerations
in the chapter Using Unicenter CA-XCOM Data Transport in the Unicenter
CA-XCOM Data Transport for Windows NT Server/Professional User Guide. In
addition, administrators should be aware of the following:
Be sure that the XCOM_HOME environment variable is set to the directory
where Unicenter CA-XCOM Data Transport is installed.
For Windows NT, environment variables can be found by right-clicking
on My Computer and selecting Properties. Choose the Environment tab
to view the System Variables.
For Windows 2000, 2003, and XP, environment variables can be found
by right-clicking on My Computer and selecting Properties. Choose the
Advanced Tab, and then click Environment Variables to view the System
Variables.
Operating Environment 41
Unicenter CA-XCOM Data Transport Global Variables
Your PATH variable should include the directory where Unicenter
CA-XCOM Data Transport is installed. The default directory is
C:\XCOMNT.
The C:\XCOMNT directory is the default repository for the subdirectories
that Unicenter CA-XCOM Data Transport uses for log and configuration
files.
Transfer Protocols
Unicenter CA-XCOM Data Transport supports transfer protocols, such as
Ethernet, SDLC, Token Ring, TCP/IP, and X.25.
SNA/APPC Protocols For SNA/APPC protocols, support is based on the capabilities provided by the
particular APPC vendor. For example, if the APPC for your platform supports
X.25 protocols, then Unicenter CA-XCOM Data Transport works with X.25.
For SNA/APPC, Unicenter CA-XCOM Data Transport requires an active LU 6.2
session to transfer files. When an LU 6.2 session is established, local users can
begin using Unicenter CA-XCOM Data Transport to initiate transfers.
TCP/IP Protocols The TCP/IP component of Unicenter CA-XCOM Data Transport supports
TCP/IP protocols for performing transfers between Unicenter CA-XCOM Data
Transport Version 3.x or r11 platforms using TCP/IP.
Default Paths and Directories
In this guide we indicate C:\XCOMNT as the default path. Your installation may
have Unicenter CA-XCOM Data Transport under a different path or on a
different drive. If this default is changed during the installation of Unicenter
CA-XCOM Data Transport, the default values in the XCOM.GLB file reflect this
change.
For more information about PATH and directory defaults, see the appendix
Unicenter CA-XCOM Data Transport Parameters in the Unicenter CA-XCOM
The Unicenter CA-XCOM Data Transport Server Architecture Illustrated
The Unicenter CA-XCOM Data Transport Server Architecture
Illustrated
The following diagram illustrates the Unicenter CA-XCOM Data Transport
server architecture:

The diagram is a general representation of the Unicenter CA-XCOM Data
Transport server architecture. Some elements may not apply to specific releases
or platforms. The following table describes some of the components in the
illustration:

Component Definition
XCOMD Unicenter
CA-XCOM
Scheduler service
The hub that controls file transfers and manages Unicenter
CA-XCOM Data Transport resources
XCOMNT Unicenter CA-XCOM Data Transports GUI interface for
Windows
XCOMQM Unicenter CA-XCOM Data Transports command line
queue manager
Using Unicenter CA-XCOM Data Transport Parameters
Use parameter values to control the variables that govern Unicenter CA-XCOM
Data Transports behavior. The parameter values can be set through the
Graphical User Interface, from the command prompt, in configuration files or in
a script. For a full list of Unicenter CA-XCOM Data Transport parameters, see
the appendix Unicenter CA-XCOM Data Transport Parameters in the Unicenter
CA-XCOM Data Transport for Windows NT Server/Professional User Guide.
Parameter Values Used in the GUI
Parameter values can be defined to Unicenter CA-XCOM Data Transport when
using the GUI as indicated in the following table. The values take precedence
depending on where they are specified. The order in which parameter values
take precedence is as follows:

Order Parameter
Value
Specified in
Explanation
1. Fields and
options
on-screen in
the GUI and in
an open
configuration
file
If the user specifies a value for a parameter on-screen
through the GUI, this overrides every other specification
in an open configuration file that has not been saved,
and overrides any values in the program.
If a configuration file is open, the unchanged values
specified in that file are used and they override the
values in the XCOM.GLB file.
Note: When the configuration file is saved, the file is
updated with the values that have been specified in the
GUI.
2. XCOM.GLB If the value is specified in the XCOM.GLB file, it
overrides the value in the program. The values specified
in XCOM.GLB are system-wide defaults that are
generally specified by the system administrator for use
with Unicenter CA-XCOM Data Transport when it is
started.
3. Program
defaults
If a value is not specified anywhere, the program has its
own (hard-coded) defaults.
Parameter Values Used at the Command Prompt
Parameter values can be defined to Unicenter CA-XCOM Data Transport from
the command prompt or in a script as indicated in the following table. The
values take precedence depending on where they are specified. The order in
which parameter values take precedence is as follows:

Order Parameter Value
Specified in
Explanation
1. Command prompt If the user specifies a value for a parameter at the
command prompt, this overrides every other
specification in the configuration files or the
program.
2. XCOM.CNF or
filename.CNF
If the value is specified in the XCOM.CNF file, or
in a user-customized configuration file specified
on the command line (for example, filename.CNF)
it overrides the value in the XCOM.GLB file.
3. XCOM.GLB If the value is specified in the XCOM.GLB file, it
overrides the value in the program. The values
specified in XCOM.GLB are system-wide defaults
that are generally specified by the system
administrator for use with Unicenter CA-XCOM
Data Transport when it is started.
4. Program defaults If a value is not specified anywhere, the program
has its own (hard-coded) defaults.
Parameter Format for Command Prompt and Scripts
When using Unicenter CA-XCOM Data Transport from the command prompt or
with a script, and when editing configuration files, the Unicenter CA-XCOM
Data Transport parameters consist of assignment statements. The format for
assignment statements is as follows:
PARAMETER_NAME (Always all uppercase, with underscore character (_)
when indicated)
An equal sign (=)
A character string terminated by a new-line
Note: Parameter values are always in uppercase. However, when specifying
directories, file names, user IDs and passwords, you may use uppercase and
lowercase.
Syntax
The syntax for assignment statements is as follows:
PARAMETER_NAME=VALUE
Example
In the following example, the parameter EXPIRATION_TIME is set to a value of
6000 seconds.
EXPIRATION_TIME=6000
This controls the maximum time in seconds that a transaction is held in the
transfer queue after execution.
Guidelines
Use the following list of guidelines for using Unicenter CA-XCOM Data
Transport parameters:
When you type trailing spaces and tabs from the command prompt as part
of a parameter value, they are stripped by the command prompt processor.
When you type trailing spaces and tabs into a file or script with an editor,
using any editor that generates ASCII text, they are treated as part of a
parameter value. In most cases these trailing spaces and tabs should be
removed. If they are not removed they can cause confusion and/or
undesirable results.
Empty lines and lines beginning with a pound sign (#) are discarded.
Example
In the following examples, the spacespacespace represents trailing spaces.
If you type the following at the command prompt, the trailing spaces are
ignored:
XCOM62 -c1 LOCAL_FILE=XYZspacespacespace
If you type the following into any configuration file using an editor, the
spacespacespace would be treated as part of the name of the LOCAL_FILE.
LOCAL_FILE=XYZspacespacespace
The XCOMD Unicenter CA-XCOM Scheduler Service
Parameter Format for Encryption
Unicenter CA-XCOM Data Transport uses the following syntax for encrypted
parameter values in configuration files. This format is generated by running
XCOMENCR.EXE at the command line with a configuration file, or it is
generated automatically by the GUI when appropriate. This feature is primarily
for encrypting the values of security parameters. This format indicates to
Unicenter CA-XCOM Data Transport that the parameter value is encrypted.
Unicenter CA-XCOM Data Transport will recognize it as encrypted and will
decrypt it before using it for transfers. If this format is not used, the value is
treated as normal text.
Syntax
The syntax for parameter encryption is as follows:
PARAMETER_NAME.ENCRYPTED=ENCRYPTEDVALUE
For more information about encrypting parameters and running
XCOMENCR.EXE, see Encrypting Parameter Values in Existing Configuration
Files in the chapter The Command Line Interface in the Unicenter CA-XCOM
The XCOMD Unicenter CA-XCOM Scheduler service runs as a background
process to control file transfers and manage Unicenter CA-XCOM Data
Transport resources. The XCOMD Unicenter CA-XCOM Scheduler service:
Schedules and synchronizes transfer requests
Controls shared memory for transfers
Establishes the default parameter values by reading the parameter file
XCOM.GLB
Controls the automatic restart of locally initiated transfers
Writes queue information out to disk periodically
Deletes aged entries from the queue
Notifies a local user by executing the XCOMNTFY script when
LOCAL_NOTIFY is required
Communicates with active or pending transfers to terminate a transfer
Considerations
When Unicenter CA-XCOM Data Transport is installed, only administrative
users with user rights to start and stop Windows services can start and stop the
XCOMD Unicenter CA-XCOM Scheduler service. Other users are normally
The XCOMD Unicenter CA-XCOM Scheduler service must be running before
you can do any transfers. For information about starting and stopping the
XCOMD Unicenter CA-XCOM Scheduler service, see the following:
The chapter Configuring Unicenter CA-XCOM Data Transport
The Unicenter CA-XCOM Data Transport for Windows NT Server/Professional
Getting Started
A transfer runs as an application under the control of the XCOMD Unicenter
CA-XCOM Scheduler service. If XCOMD Unicenter CA-XCOM Scheduler
service is running, the user does not have to be logged on for a scheduled
transfer to be processed. That is, you can schedule a transfer and log off, and it
will run as scheduled. Likewise, a remotely initiated transfer can be processed
without the local user being logged on, as long as the XCOMD Unicenter
CA-XCOM Scheduler service is running.
Notes:
If you are requested to set a trace of the XCOMD Unicenter CA-XCOM
Scheduler service, enter -d9 in the Startup Parameters option of the Services
window. This will create a trace file, as specified on the Trace Properties Tab
page. For more information about trace files, see Tracing Unicenter
CA-XCOM Data Transport Scheduler Service in the chapter Configuring
Unicenter CA-XCOM Data Transport.
Setting trace options may generate large files of trace data.
Tracing Transfers
Tracing Transfers
Unicenter CA-XCOM Data Transport generates an individual trace file for each
transfer. The trace files are written into the \xcomnt\trace directory and have
the format tid.tra, where tid is the six-digit transfer ID number. These traces and
their corresponding queue entries are deleted when the EXPIRATION_TIME
specified in the XCOM.GLB has passed, making it important to promptly copy
the traces.
Tracing must be enabled before use. From a command prompt, in the xcomnt
directory start Cardlog3:
Card3 onTo start the Cardlog3 trace facility
Card3 offTo stop the Cardlog3 trace facility
Ensure that you see the CA TRACE icon on the task bar, which tells you that
tracing is enabled. Delete all files from the \xcomnt\trace directory before you
start. Once the needed traces have been captured, be sure to turn off all tracing.
Tracing Locally Initiated Transfers
You may trace a single locally initiated transfer by specifying XTRACE=10 in the
.cnf file used for the transfer, or by specifying it on the command line or GUI.
Tracing All Transfers
Tracing for all transfers is turned on by specifying XTRACE=10 in the
XCOM.GLB and stopping and starting the xcomd service to pick up that
parameter. When you turn on tracing for transfers, all incoming and outgoing
transfers will be traced.
Tracing Different Components from the GUI
Tracing Different Components from the GUI
The following procedure will set and capture detailed tracing for each
CA-XCOM component. Specifying different file names for all the traces is not
necessary, but you can do that.
From the CA-XCOM GUI, select:
Tools
Global Parameters
Trace: Xtrace=10
Component: Choose each component and set it for detailed tracing.
Note: Ensure the trace detail is on for each component. It automatically
turns off every time you select a different component.
TXPI Trace Detail
XCOM Admin Property sheets Trace Detail
XCOM Communication Server Trace Detail
XCOM Service Trace Detail
XCOM Transfer Trace detail
Note: Test using a small one-record file.
Reproduce the problem and collect all the traces from the directory
xcomnt\trace.
Global Parameters
For a full list of Unicenter CA-XCOM Data Transport parameters, see the
appendix Unicenter CA-XCOM Data Transport Parameters in the Unicenter
CA-XCOM Data Transport for Windows NT Server/Professional User Guide. For an
explanation of parameters and defaults, see Using Unicenter CA-XCOM Data
Transport Parameters earlier in this chapter.
Use XCOM.GLB to set default parameters for Unicenter CA-XCOM Data
Transport transfers. Use any editor that generates ASCII text to modify
parameters. You can also use the Unicenter CA-XCOM Data Transport
Properties dialog pages to modify the default values of global parameters, which
is the preferred method. For more information about using the GUI to modify
global values, see the Unicenter CA-XCOM Data Transport for Windows NT
Global Parameters
WARNING! The parameters in the XCOM.GLB files and the values of the options on
the Properties dialog pages in the GUI should only be changed by authorized Unicenter
CA-XCOM Data Transport administrators. Most users will not need to change these
values. The values should not be changed or deleted unnecessarily, and parameters
should not be deleted from XCOM.GLB unnecessarily. When any of these values or
parameters are deleted unnecessarily, the results are unpredictable.
Note: The installation process installs XCOM.GLB with parameters used for
TCP/IP transfers. Even if you are not using TCP/IP, you should not delete these
parameters from XCOM.GLB.
XCOM.GLB
The XCOM.GLB file lets you set defaults independently of the execution
environment. This file is created as part of the installation process.
The parameters in XCOM.GLB are a superset of the parameters in XCOM.CNF.
Any parameters set in XCOM.CNF can be set in XCOM.GLB. However, the
parameters that are specific to XCOM.GLB cannot be set in XCOM.CNF. If there
are any changes made to the XCOM.GLB file, the XCOMD Unicenter CA-XCOM
Scheduler service must be stopped and restarted.
Note: XCOM.GLB parameters apply to remotely initiated and locally initiated
transfers unless they are overridden. XCOM.CNF parameters override those in
XCOM.GLB for locally initiated transfers if the transfer is started from the
command prompt and no configuration file is specified. The parameters in
XCOM.GLB are used for remotely initiated transfers.
For descriptions of XCOM.GLB parameters, see the chapter Configuring
Setting Session Control Parameters
Use XCOM.SES to limit the number of parallel sessions available for locally
initiated transfers for each remote system. Use any editor that generates ASCII
text to modify XCOM.SES.
XCOM.SES
XCOM.SES is the configuration file used by XCOMD Unicenter CA-XCOM
Scheduler service to limit the number of parallel sessions available for locally
initiated transfers for each remote system. A default file is placed in
C:\XCOMNT\CONFIG\XCOM.SES by the installation procedure.
You can set a maximum number of partners that can be described in this file by
specifying a number in the MAX_SESSIONS_ENTRIES global parameter. For
example, if you specify MAX_SESSIONS_ENTRIES=50, you can have up to 50
lines in this file, each one specifying the name of the remote system.
You limit the number of sessions available for Unicenter CA-XCOM Data
Transport transfers by setting a number in the XCOM.SES file for each remote
system. If a session is not available for immediate use, the transfer is queued for
subsequent execution.
To specify a remote system, as indicated in the example in this section, replace
connection_profile with the destination address or name specified by the user in
the remote system parameter (REMOTE_SYSTEM, REMOTE_SYSTEM_RF,
REMOTE_SYSTEM_SJ, or REMOTE_SYSTEM_SR).
Note: Unicenter CA-XCOM Data Transport reserves memory for information
about the number of sessions for each destination based upon the
connection_profile entries in this file.
Transfers Using SNA
For transfers using SNA, the parameter name connection_profile represents the
CPI-C symbolic destination name of the remote system to which the session limit
is applied. The value for the parameter should be between one and the
maximum number of sessions allowed for the partner mentioned in the
associated CPI-C record. The maximum number of sessions allowed is equal to
the lowest value from among the maximum number of sessions supported in the
following properties:
The local LU
The Log Mode (XCOMMODE, the recommended mode name, or whatever
name you are using)
The remote LU
The platform of the remote Unicenter CA-XCOM Data Transport partner
(Applies particularly to PC-DOS and OS/2 partners)
Transfers Using TCP/IP
For transfers using TCP/IP, specify the format of the remote system that is
consistent with your sites use of the remote system parameters. If the IP address
is used, specify connection_profile in the form of 123.123.78.91. If host names or
domain names are used in the remote system parameter, specify
connection_profile in the appropriate form of the name.
You may specify a connection_profile for each form of address or name that is
used. Note that if the XCOM.SES file does not have an entry for the host name or
domain name, the value of the connection_profile will default to one.
Example XCOM.SES File
In the following example, a sample XCOM.SES file of session control parameters
for Unicenter CA-XCOM Data Transport partners is shown. It indicates that a
maximum of 8 sessions can be used at any one time for locally initiated transfers
to a remote system identified as XCOMQA3 and a maximum of 4 sessions can be
used at any one time for locally initiated transfers to a remote system identified
as XCOMQA4. For a transfer to a remote system using TCP/IP, a session using
an IP address is also shown.
# connection_profile=number_of_sessions_allowed
#
XCOMQA3=8
XCOMQA4=4
123.123.78.91=4
For SNA, the connection_profile represents the CPI-C side record of the remote
system. For Windows, this is the CPI-C Symbolic Destination Name of the
remote system.
Managing the Unicenter CA-XCOM Data Transport Queue
Use XCOMQM at the command line to control the activity of the Unicenter
CA-XCOM Data Transport transfer queue, including stopping transfers and
displaying the status of a transfer.
XCOMQM
The XCOMQM command lets you maintain the Unicenter CA-XCOM Data
Transport queue from the command prompt. This command lets you delete
entries from the queue, suspend transfers, resume suspended transfers, put
scheduled transfers on hold, release held transfers, display the list of entries in
the queue and display detailed information about the queue entries.
Syntax
The syntax for XCOMQM is as follows:
XCOMQM [option] [option] . . .
You can use more than one option on a command line. You can also use the same
option more than once. Each option must be separated by a space. These options
can be listed in any order, but note that when the shell encounters options such
as the -r option, it will perform the command and exit XCOMQM without
reading the rest of the command line.
Options
The following table explains the options for XCOMQM:

Option Function
-r Display the release level of XCOMQM and exit.
-Aentryname Release a held transfer.
-Centryname Get a trace of a transfer.
-Dentryname Display details about a queue entry.
-Hentryname Hold a scheduled transfer.
-L[a] List your queued transfers. Use -La for all queued transfers.
-Rentryname Remove a queue entry.
Option Function
-Rfentryname Force an entry to be removed from the queue, even if the
entrys status does not allow you to remove it. Use this
command only as a last resort when a transfer does not
respond to the -T or -Tf commands.
-R* Remove all completed or scheduled entries from the queue.
If you use this option on an active transfer, it will interrupt the
transfer.
-Tentryname Terminate an active transfer.
-T[f]entryname Force termination of the transfer. Use this command only as a
last resort to terminate a transfer if it does not respond to the
-T command.
Note: When using SNA/APPC protocols, the TP will abend
and it may be necessary to restart the underlying SNA
software. When using TCP/IP, XCOMTCP will abend.
-Sentryname Suspend a transfer.
-Eentryname Resume a suspended transfer.
-d Display debugging information.
no option Display the help information.
Note: entryname represents the Transaction ID, which is the six-digit name of the
transfer entry in the queue.
Transfer Failure in Starting State
When a queued transfer is initiated, it is entered into the transfer queue. Then,
when it is scheduled to run, it goes into the starting state. If for some reason the
transfer fails to go beyond this state within 10 minutes and does not go into the
started state (where the transfer connection has been initialized and the transfer
of information begins), it is treated as an abend. The transfer is attempted again,
depending on the values in the Version 2 window for Number of retries and
Retry interval. The corresponding parameters are RESTART_SUPPORTED and
RETRY_TIME.
Using the Pre-allocation Exit
ERRORLEVEL Return Codes from xcomqm.exe
When executing the command-line program xcomqm.exe, the ERRORLEVEL
indicates successful or failed processing. An ERRORLEVEL set to ZERO
indicates successful operation and termination. An ERRORLEVEL set to
NON_ZERO values indicates program processing was not successful, and that
the program has terminated.
Use the xcompre exit to validate all locally and remotely initiated transfers
before they begin, and to customize parameters for that transfer as indicated
below. This exit is invoked by specifying the XPRECMD parameter in xcom.glb:
XPRECMD=%XCOM_HOME%\xcompre.bat
If XPRECMD is set when the XCOMD Unicenter CA-XCOM Scheduler service is
invoked, the pre-allocation exit will be active for locally and remotely initiated
transfers. This gives the system administrator additional capabilities to control
access, such as allowing only a particular user to perform a transfer, or only
allowing transfers to or from a particular directory.
Customization is useful where the remote user does not specify the true file
name, and the local system uses a database to map the specified name to the true
local name as in certain e-mail applications. For example, an incoming transfer
specifies a certain file name, but the administrator of the local system that is
receiving the file wants to place the data into a different file, depending on the
user ID of the sender. The script retrieves parameter values and sends the
relevant information to standard output, and if desired, changes the values using
the -p option.
xcompre
An xcompre sample script, xcompre.bat, is provided with the installation of
Unicenter CA-XCOM Data Transport. This optional exit is run on the local
system before a transfer starts and can be tailored to meet individual user
requirements. The xcompre exit passes transfer ID (tid) information to xcomqm,
along with the parameter values specified by the available option -p.
Note: The -p option, as shown in the sample script, is intended only for use with
the xcompre exit and is not supported with the xcomqm command line options.
The pre-allocation exit is invoked after Unicenter CA-XCOM Data Transport
receives the Unicenter CA-XCOM Data Transport header from the partner, but
before the transfer commences.
xcompre Options
The following is the available option for xcompre and its associated parameters:

Option Function
-p Changes the values for the following parameters based upon the
specified transfer ID (tid) and applies them to the transfer:
FILE_OPTION
LOCAL_FILE
REMOTE_FILE
Sample Script
In this sample xcompre script:
The only LOCAL file transfers permitted are ones that do not specify
%XCOM_HOME%\config\xcom.reject.
The only REMOTE file transfers permitted are ones that do not have
xcomv31 in USERID.
If %XCOM_HOME%\config\xcom.force is in the LOCAL_FILE, the -p option is
used to specify the values to use for LOCAL_FILE, REMOTE_FILE, and
FILE_OPTION.
@echo off
REM xcompre.bat
REM This procedure is invoked by the Unicenter CA-XCOM Data Transport
REM transaction program for all locally and remotely initiated transfers before
they
REM begin.

REM For production version, disable the ECHO and PAUSE statements
REM by changing YES to NO in the following set command.

REM echo on

set use_echo=YES
set xcomqm="%XCOM_HOME%\xcomqm"

set local_reqno=%1
rem local request number/tid (000000 if unassigned)

shift
set initiator=%1
rem LOCAL or REMOTE

shift
set transfer_type=%1
rem JOB, REPORT or FILE

shift
set direction=%1
rem SEND or RECEIVE

shift
set restarting=%1
rem RESTARTING or FIRST_TRY

shift
set start_time=%1
rem transfer start date/time

shift
set end_time=%1
rem transfer end date/time

shift
set remote_system=%1
rem remote system id

shift
set remoteuser=%1
rem Remote user

shift
set remote_reqno=%1
rem Remote request Number

shift
set group=%1
rem REMOTE initiated only: transferGroup name

shift
set sysdata=%1
rem REMOTE initiated UNIX only: System Dependent User Data

shift
set xferdata=%1
rem REMOTE initiated UNIX only: Transfer Dependent User Data

shift
set ident=%1
rem REMOTE initiated UNIX only: Ident

shift
set tmp_file=%1
rem Local temporary file name

shift
set file=%1
rem Local file name

shift
set remote_file=%1
rem Remote file name

shift

set carriage_flag=%1
rem Carriage return / packing flag

shift
set code_flag=%1
rem Code flag

shift
set compression=%1
rem Compression flag

if NOT /%use_echo%/ == /YES/ GOTO SKIP_ECHO
echo xcompre
echo Common parameters:
echo local_reqno: %local_reqno%
echo initiator: %initiator%
echo transfer_type: %transfer_type%
echo direction: %direction%
echo restarting: %restarting%
echo start_time: %start_time%
echo end_time: %end_time%
echo remote_system: %remote_system%
echo remoteuser: %remoteuser%
echo remote_reqno: %remote_reqno%
echo group: %group%
echo sysdata: %sysdata%
echo xferdata: %xferdata%
echo ident: %ident%
echo tmp_file: %tmp_file%
echo file: %file%
echo remote_file: %remote_file%
echo carriage_flag: %carriage_flag%
echo code_flag: %code_flag%
echo compression: %compression%
pause
:SKIP_ECHO

rem PREPROCESS HERE !

if /%initiator%/ == /"LOCAL"/ GOTO XCOMPRE_LOCAL
if /%initiator%/ == /"REMOTE"/ GOTO XCOMPRE_REMOTE

GOTO XCOMPRE_END

:XCOMPRE_LOCAL
if /%use_echo%/ == /YES/ echo XCOMPRE_LOCAL

rem The following two if statements are case-sensitive. To make them not case-
sensitive
rem a "/I" must follow the word "if" as if /I /%file%/ == ......

if /%file%/ == /"%XCOM_HOME%\config\xcom.reject"/ GOTO XCOMPRE_REJECT
if NOT /%file%/ == /"%XCOM_HOME%\config\xcom.force"/ GOTO XCOMPRE_END
%xcomqm% -p%local_reqno% LOCAL_FILE=c:\xcomnt\config\xcom.glb
REMOTE_FILE=c:\temp\test.txt FILE_OPTION=CREATE
GOTO XCOMPRE_END

:XCOMPRE_REMOTE
if /%use_echo%/ == /YES/ echo XCOMPRE_REMOTE

rem The following two if statements are case-sensitive. To make them not case-
sensitive
rem a "/I" must follow the word "if" as if /I /%file%/ == ......

if /%remoteuser%/ == /"xcomv31"/ GOTO XCOMPRE_REJECT
if NOT /%file%/ == /"%XCOM_HOME%\config\xcom.force"/ GOTO XCOMPRE_END
%xcomqm% -p%local_reqno% LOCAL_FILE=c:\tmp\test.txt
REMOTE_FILE=c:\xcomnt\config\xcom.glb FILE_OPTION=CREATE
GOTO XCOMPRE_END

:XCOMPRE_REJECT
if /%use_echo%/ == /YES/ echo XCOMPRE_REJECT
%xcomqm% -p%local_reqno% TRANSFER=REJECT

Using Unicenter CA-XCOM Data Transport Scripts
:XCOMPRE_END
if /%use_echo%/ == /YES/ echo XCOMPRE_END
pause
exit
Using Unicenter CA-XCOM Data Transport Scripts
Use these scripts to handle processing after you have received a file. They are
used for controlling print-spooling, for managing notification facilities, and for
additional processing of incoming files after a successful incoming file transfer is
completed.
Provided Scripts
These scripts are provided with Unicenter CA-XCOM Data Transport as sample
scripts, in batch files (.bat) and they are available online. They can be tailored to
meet individual user requirements, if necessary.
Interacting with the Window Station and Desktop
Some scripts create new processes that must continue running after the script is
returned to the transfer partner. To prevent the new process from being
terminated you must include the user in the CA-XCOM-Batch-Interactive group.
For more information, see Creating the CA-XCOM Batch-Interactive Group in
the chapter Configuring Unicenter CA-XCOM Data Transport.
Modifying Post Processing Scripts
To modify a post processing script, follow these steps:
1. Open any editor that can handle ASCII text and open the script you wish to
modify.
2. Go to the bottom of the script.
3. Add the desired commands to the end of the script.
Note: If the script ends with an exit statement, enter your commands above
the exit.
4. Save the file as ASCII text and exit the editor.
XCOMPP
XCOMPP is a script that contains commands for post processing of a file. After a
successful file transfer is completed, XCOMPP will get invoked automatically. It
is only invoked for incoming file transfers. It is not invoked for job or report
transfers.
The sample XCOMPP scripts sets up the environment variables that correspond
to the appropriate Unicenter CA-XCOM Data Transport parameters.
You can reference the environment variables in XCOMPP by putting commands
at the end of the script. XCOMPP does not take any visible actions if no
modifications are made to the sample script.
Sample Script
The following is the sample XCOMPP script:
echo off
rem This procedure is invoked by the Unicenter CA-XCOM Data Transport
rem transaction program after the transfer is finished before the
rem conversation is terminated.
rem Not every argument will be populated;
rem the values contained in the arguments depend on those provided by the
rem remote system.

rem For a production version, disable the echo and pause statements
rem by setting use_echo to NO in the following SET command.
rem For a debug version, enable the echo and pause statements
rem by setting use_echo to YES in the following SET command.

set use_echo=YES

set compression=%1

shift
set notify_flag=%1
rem Notify flag

shift
set notify_name=%1
rem Notify Name

shift
set remoteuser=%1
rem Notify User

shift
set filetype=%1
rem File type (Always '3' for file)

shift
set fileaction=%1
rem File action (Create, replace or append)

shift
set datasettype=%1
rem Dataset type

shift
rem Carriage return flag

shift
set code_flag=%1
rem Code flag

shift
set recfm=%1
rem Record format

shift
set lrecl=%1
rem Logical record length

shift
set remote_reqno=%1

shift
set local_reqno=%1
rem Local Request number

shift
set group=%1
rem Group name

shift
set sysdata=%1
rem System Dependent User Data

shift
set xferdata=%1
rem Transfer Dependent User Data

shift
set ident=%1
rem Ident

shift
set truncation_flag=%1
rem Truncation flag

shift
set tmp_file=%1

shift
set file=%1
rem Local file name

shift
set remote_file=%1

echo xcompp
echo notify_flag: %notify_flag%
echo notify_name: %notify_name%
echo filetype: %filetype%
echo fileaction: %fileaction%
echo datasettype: %datasettype%
echo recfm: %recfm%
echo lrecl: %lrecl%
echo groupname: %group%
echo ident: %ident%
echo truncation_flag: %truncation_flag%
echo local file: %file%
pause

:SKIP_ECHO

rem POSTPROCESS HERE !
Example
The example below shows how you can copy a temporary file to a new file by
adding the following to the end of the XCOMPP script:
COPY %tmp_file% C:\USER\XCOM\INCOMING\FILE01A.TXT
This will copy the temporary file Unicenter CA-XCOM Data Transport uses for
transfers to the directory C:\USER\XCOM\INCOMING and name it
FILE01A.TXT.
Note: You must type a % sign before and after the variable to reference the
variable in the XCOMPP script.
Post Transfer Script
Use the XCOMEND script for all types of transfers, after a transfer is finished
and partner communications have ended, whether the transfer completed
successfully or not.
XCOMEND
XCOMEND.BAT is a batch file that is invoked by an Unicenter CA-XCOM Data
Transport transfer program. This script can be used as provided, or it can be
used by system administrators to modify printing commands and parameters to
provide additional information about all types of transfers (remote and local;
send and receive; successful or failed). Different arguments are passed
depending on whether the transfer is a file, job, or report. This script can be used
to define the context of the transfer, such as indicating that a remotely initiated
send transfer failed with a particular message.
Sample Script
The following is the sample XCOMEND script:
@echo off
rem This procedure is invoked by the Unicenter CA_XCOM Data Transport
rem transfer program after the transfer is finished (whether
rem successful or not) and partner communications have ended.
rem Different arguments are passed depending on whether the
rem transfer is a file, job or report.

rem For a production version, disable the echo and pause statements
rem by changing YES to NO in the following SET command.

set use_echo=YES

rem The following parameters are supplied for all transfer types:

set local_reqno=%1
rem local request number/tid (000000 if unassigned)

shift
set initiator=%1
rem LOCAL or REMOTE

shift
set transfer_type=%1
rem JOB, REPORT or FILE

shift
set direction=%1
rem SEND or RECEIVE

shift
set restarting=%1
rem RESTARTING or FIRST_TRY

shift
set start_time=%1
rem transfer start date/time

shift
set end_time=%1
rem transfer end date/time

shift
set remote_system=%1
rem remote system id

shift
set status=%1
rem transfer status

shift
set error=%1
rem XCOM file transfer numeric error code

shift
set errmsg=%1
rem error code translated to message text

shift
set statusmsg=%1
rem status message / remote partner message

shift
set remoteuser=%1
rem Remote user

shift
set remote_reqno=%1

shift
set group=%1
rem REMOTE initiated only: transferGroup name

shift
set sysdata=%1
rem REMOTE initiated UNIX only: System Dependent User Data

shift
set xferdata=%1
rem REMOTE initiated UNIX only: Transfer Dependent User Data

shift
set ident=%1
rem REMOTE initiated UNIX only: Ident

shift
set tmp_file=%1

shift
set file=%1
rem Local file name

shift
set remote_file=%1

shift

rem Carriage return / packing flag

shift
set code_flag=%1
rem Code flag

shift
set compression=%1

shift
set file_recs=%1
rem file records read/written

shift
set file_bytes=%1
rem file bytes read/written

shift
set blocks=%1
rem blocks sent/received

shift
set bytes=%1
rem bytes send/received

if NOT /%use_echo%/ == /YES/ GOTO SKIP_ECHO_1
echo xcomend
echo Common parameters:
echo initiator: %initiator%
echo transfer_type: %transfer_type%
echo direction: %direction%
echo restarting: %restarting%
echo start_time: %start_time%
echo end_time: %end_time%
echo remote_system: %remote_system%
echo status: %status%
echo error: %error%
echo errmsg: %errmsg%
echo statusmsg: %statusmsg%
echo group: %group%
echo ident: %ident%
echo file: %file%
pause
echo file_recs: %file_recs%
echo file_bytes: %file_bytes%
echo blocks: %blocks%
echo bytes: %bytes%
:SKIP_ECHO_1

if /%transfer_type%/ == /"JOB"/ GOTO PARMS_JOB
if /%transfer_type%/ == /"REPORT"/ GOTO PARMS_REPORT
if /%transfer_type%/ == /"FILE"/ GOTO PARMS_FILE

echo invalid transfer type %transfer_type%
pause
:SKIP_ECHO_2

GOTO END

rem =========

:PARMS_JOB

rem =========

rem There are no additional parameters for remote jobs

rem >>>>> Insert job processing here <<<<<

GOTO END

rem =========

:PARMS_REPORT

rem =========

shift
set jobname=%1
rem Job name field from JES

shift
set jobnumber=%1
rem Job number field from JES

shift
set tclass=%1
rem print class

shift
set copies=%1
rem Number of copies to print

shift
set form=%1
rem Type of form to print this job on.

shift
set recfm=%1
rem Record format of incoming print job.

shift
set lrecl=%1
rem Logical record length of incoming report.

shift
set blksize=%1
rem Block size of incoming report.

shift
set ucs_name=%1
rem Name of UCS to be used for this print job.

shift
set fcb=%1
rem Name of FCB (form control block) for this report.

shift
set room_num=%1
rem Room number field from JES.

shift
set pgmr_name=%1
rem Programmer name field from JES.

shift
set tso_ntfy=%1
rem TSO notify field from JES.

shift
set dest=%1
rem Destination printer specification.

shift
set crg_cntl=%1
rem Type of carriage control characters being used.

shift
set title=%1
rem Report title.

echo Print parameters:
echo jobname: %jobname%
echo jobnumber: %jobnumber%
echo tclass: %tclass%
echo copies: %copies%
echo form: %form%
echo recfm: %recfm%
echo lrecl: %lrecl%
echo blksize: %blksize%
echo ucs_name: %ucs_name%
echo fcb: %fcb%
echo room_num: %room_num%
echo pgmr_name: %pgmr_name%
echo tso_ntfy: %tso_ntfy%
echo dest: %dest%
echo crg_cntl: %crg_cntl%
echo title: %title%
pause
:SKIP_ECHO_3

rem >>>>> Insert report processing here <<<<<

GOTO END

rem ==========================================================

:PARMS_FILE

rem ==========================================================

shift
set fileaction=%1
rem File action: C (create),R (replace) or A (append)

shift
set datasettype=%1
rem Dataset type

shift
set recfm=%1
rem Record format

shift
Modifying the Printing Script
set lrecl=%1
rem Logical record length

shift
set remote_reqno=%1
rem remote transfer request number

shift
set truncation_flag=%1
rem Truncation flag

echo File parameters:
echo fileaction: %fileaction%
echo datasettype: %datasettype%
echo recfm: %recfm%
echo lrecl: %lrecl%
echo truncation_flag: %truncation_flag%
pause
:SKIP_ECHO_4

rem >>>>> Insert file processing here <<<<<
rem ==========================================================

:END

rem ==========================================================
Use this script after a print job is received from a remote system. This script can
be used as provided or it can be used by system administrators to modify
printing commands and parameters.
XCOMLP
XCOMLP.BAT is a batch file that is invoked by a Unicenter CA-XCOM Data
Transport transfer program.
Notes:
For transfers using SNA/APPC protocols, this may be XCOMSEND,
XCOMRECV, LU6SEND, LU6RECV.
For transfers using TCP/IP, the program is XCOMTCP.
The contents of the parameters passed to XCOMLP depend on what is supplied
on the initiating side of the transfer. The sample procedure prints a report to the
destination printer.
Print Command in XCOMLP
The print command at the end of the sample XCOMLP.BAT file should be
validated separately from Unicenter CA-XCOM Data Transport before it is used
with Unicenter CA-XCOM Data Transport.
Due to the 21-byte limit of the destination value for the printer sent from the
remote system, it may be necessary to specify a portion of the destination as
fixed text in the batch file, immediately before the variable %dest%.
Notes:
If there are errors in the values in the print command in this script, problems
can arise that can cause the command to hang. This then can cause the
Unicenter CA-XCOM Data Transport transfer to hang and/or time out.
The Unicenter CA-XCOM Data Transport considers a send report transfer to
be successful even if the print command is not successful. The batch file does
not supply a return code to Unicenter CA-XCOM Data Transport.
You may also encounter a situation, especially when sending a report to
NetWare, where a print command might fail because you have exceeded the
number of concurrent logons to the print server. Depending on trace levels, the
command may fail without a message being displayed.
Example
In the following example, the print command specifies a fixed print server
named SERVERX, and uses the destination value (received from the remote
system) to specify a printer connected to that server.
print /d:\\SERVERX\%dest% %file%
Sample Script
The following is the sample XCOMLP script:
@echo off
rem transfer programs after an incoming print request is received.
rem Not every argument will be populated;
rem the values contained in the arguments depend on those provided by the
rem remote system. The most general case is that of a host partner that uses
rem the user exit EXIT02 to extract and transmit the JES parameters for the
rem print job.

rem In all cases, the file and copies parameters will be valid.

rem For a test version, enable the echo and pause statements
rem by changing NO to YES in the following SET command.

set use_echo=YES

set rluname=%1
rem Remote lu name

shift
set jobname=%1
rem Job name field from JES

shift
set jobnumber=%1
rem Job number field from JES

shift
set tclass=%1
rem print class

shift
set copies=%1
rem Number of copies to print

shift
set form=%1
rem Type of form to print this job on.

shift
set recfm=%1
rem Record format of incoming print job.

shift
set lrecl=%1
rem Logical record length of incoming report.

shift
set blksize=%1
rem Block size of incoming report.

shift
set ucs_name=%1
rem Name of UCS to be used for this print job.

shift
set fcb=%1
rem Name of FCB (form control block) for this report.

shift
set room_num=%1
rem Room number field from JES.

shift
set pgmr_name=%1
rem Programmer name field from JES.

shift
set tso_ntfy=%1
rem TSO notify field from JES.

shift
set file=%1
rem Name of temporary file into which XCOM 6.2 has placed report

shift
set dest=%1
rem Destination printer specification.

shift
set nodespec=%1
rem connection profile name

shift
set crg_cntl=%1
rem Type of carriage control characters being used.

shift
set title=%1
rem Report title.

if %dest%=="xcomntlpt" set dest="\\usprde02\uspr201"

rem =================================================
if /%use_echo%/ == /YES/ echo on
echo xcomlp
print /d:%dest% %file%
@echo off
rem =================================================


pause
echo rluname: %rluname%
echo jobname: %jobname%
echo jobnumber: %jobnumber%
echo tclass: %tclass%
echo copies: %copies%
echo form: %form%
echo recfm: %recfm%
echo lrecl: %lrecl%
echo blksize: %blksize%
pause
echo ucs_name: %ucs_name%
echo fcb: %fcb%
echo room_num: %room_num%
echo pgmr_name: %pgmr_name%
echo tso_ntfy: %tso_ntfy%
echo file: %file%
echo dest: %dest%
echo nodespec: %nodespec%
echo crg_cntl: %crg_cntl%
echo title: %title%
pause

:SKIP_ECHO
Customizing the Notification Script
Customizing the Notification Script
The XCOMNTFY script is used, when notification is requested, to notify users
that a transfer has completed successfully. System administrators can modify
this script to customize notification procedures, if necessary. For any other post-
processing modifications, we recommend that you use XCOMPP.
XCOMNTFY
XCOMNTFY uses XCOMMAIL.EXE to read the queue entry to determine the
user id and password to use for logging in to the MAPI (Messaging Application
Programming Interface) subsystem.
Sample Script
The following is the XCOMNTFY script:
echo off
rem transaction program when notification is requested, to notify users
rem that a transfer has completed successfully.
rem
rem The arguments passed to the xcomntfy procedure are:
rem
rem -q q_entryname
rem
rem -h how
rem
rem -u who
rem
rem Note:
rem 1. The order of the arguments is important
rem 2. Other information about the transfer can be extracted
rem from the output of xcomqm -D%q_entryname% command, if needed

set q_entryname=%2
set how=%4
set who=%6
set xcomqm="%xcom_home%\xcomqm"
set xcommail="%xcom_home%\xcommail"
set xcompop="%xcom_home%\xcompop"

rem The following would pop up a message on the screen
if .%how%==.W %xcomqm% -D%q_entryname% | %xcompop%
if .%how%==.A %xcomqm% -D%q_entryname% | %xcompop%

rem The following would send a mail message
if .%how%==.T %xcomqm% -D%q_entryname% | %xcommail% %q_entryname% %who%
if .%how%==.R %xcomqm% -D%q_entryname% | %xcommail% %q_entryname% %who%
if .%how%==.L %xcomqm% -D%q_entryname% | %xcommail% %q_entryname% %who%
if .%how%==.M %xcomqm% -D%q_entryname% | %xcommail% %q_entryname% %who%
if .%how%==.C %xcomqm% -D%q_entryname% | %xcommail% %q_entryname% %who%

rem Put user defined notification, if any, here
rem exit 0
Setting Up Trusted Access
The Trusted Access feature allows a transfer to be sent to a remote partner
without actually specifying the user ID and password in the transfer. Trusted
Access transfers may be sent to and from Windows NT as well as a number of
other partners.
Trusted Transfers to and from Windows
To Windows It is necessary to set up a Trusted access file on the receiving Windows partner.
This file is kept in the Windows Registry and contains information such as a list
of remote systems, group user IDs, domains, user IDs, and passwords. A partner
can send a trusted transfer to NT if the remote system and the user ID of the
incoming transfer match what is defined in this file. The user ID specified in this
file must match the user ID of the person logged onto the initiating system.
It is also possible to define a group user ID so that a matching user ID does not
have to be defined on the remote system for each user initiating a transfer.
From Windows When initiating a transfer from Unicenter CA-XCOM Data Transport for
Windows NT, the TRUSTED parameter must be set to yes to indicate to the
receiving system that this transfer is a trusted transfer. Trusted access must be
configured on the remote partner. The TRUSTED parameter is supported only
by other systems running Advantage CA-XCOM Data Transport Version 3.1 or
Unicenter CA-XCOM Data Transport r11. To verify this support, see the remote
systems documentation.
Trusted Access File
The Windows Registry maintains a list of remote systems, group user IDs,
domains, user IDs and passwords. The easy-to-use Trusted Access user interface
allows you to set up and maintain this list of systems, user IDs, and passwords.
Starting the Trusted Access Interface
You can start Trusted Access interface in two ways:
From the Unicenter CA-XCOM Data Transport User Interface, select Trusted
Access from the Tools menu.
From the Windows Start menu, select Programs, Unicenter CA-XCOM Data
Transport, Unicenter CA-XCOM Data Transport Trusted Administrator.
Trusted Access Parameters
This section describes the fields found on the Trusted Access interface windows.
Domain
The Windows domain name for use in authenticating the group user ID and
password. This field is required only if Group Name is specified.
Range 1 to 15 characters.
Default None
Group Name
The user ID of the group associated with the remote system. This field is
optional.
Default None
Password
The password associated with the group user ID. This field is required only if
Group Name is specified.
Default None
System Name
The name of a remote system for which you want to give trusted access to
initiate transfers.
Default None
User Name
The user ID of the user you want to associate with the remote system you are
defining.
Cannot contain the following characters / \ [ ] : ; | = , + * ? < >
Default None
Using the Trusted Access Interface
For information about filling in the fields for this interface, see the online help.

Chapter
5
Generating SSL Certificates

This chapter describes how to generate certificates that can be used with
For more information on using OpenSSL, see Network Security with OpenSSL by
John Vega, Matt Messier, and Pravir Chandra (OReilly & Associates).
Using SSL Mode
Unicenter CA-XCOM Data Transport uses SSL in client/server mode. In
client/server mode, certificates are required for both the local (initiating) and
remote (receiving) Unicenter CA-XCOM Data Transport partners. SSL considers
the local Unicenter CA-XCOM Data Transport partner to be the client and the
remote Unicenter CA-XCOM Data Transport partner to be the server.
When establishing the SSL connection, the server sends the server certificate to
the client for verification. After the client verifies the server certificate, the client
sends the client certificate to the server for verification. Both the client and the
server must verify the CA certificate from the other.
Setting up SSL for Unicenter CA-XCOM Data Transport involves the following
tasks:
1. Create the CA Certificate.
2. Set the expiration for the CA Certificate.
3. Create the server certificate.
4. Create the client certificate.
5. Configure the Unicenter CA-XCOM Data Transport SSL server.
6. Configure the Unicenter CA-XCOM Data Transport client.
Generating SSL Certificates 51
Creating the CA Certificate
Creating the CA Certificate
Use the following procedure to create the CA certificate:
1. Create a configuration file that is used as input to the openssl utility. A
sample file, named cassl.conf, was installed (in the ssl subdirectory of the
Unicenter CA-XCOM Data Transport installation directory). Edit the section,
[root_ca_distinguished_name], changing the values as appropriate for your
system.
Note: Verify that the directory path for dir is set to where Unicenter
CA-XCOM Data Transport is installed. The default dir is c:\xcomnt\ssl.
2. From the command prompt, issue the makeca script file to generate the
certificate.
This script uses the cassl.conf file to generate a certificate and key file. The
certificate, cassl.pem, is saved in the certs subdirectory. The key file,
generated as casslkey.pem, is saved in the private subdirectory.
3. From the command prompt, run the listca script:
listca
This script displays the CA certificate and the information stored in the
package.
Setting Expiration
When generating a CA certificate, the default_days parameters in cassl.conf that
controls the expiration of server and client certificates is not used for CA
certificates. The certificate is generated with a default expiration of 30 days.
Use the following procedure to change the default expiration:
1. Add days nnn to the makeca script line. The following line is an example of
how the makeca script is shipped:
Openssl req x509 newkey rsa out ./certs/cassl.pem outform PEM
2. To change the expiration to one year, change the line before running the
makeca script:
Openssl req x509 newkey rsa out ./certs/cassl.pem outform PEM days 365
Creating the Server Certificate
Creating the Server Certificate
Use the following procedure to create the server certificate:
1. Create a configuration file to use as input to the openssl utility. A sample file,
serverssl.conf, was installed.
a. Edit the section [req_distinguished_name], changing the values to your
specifications. The server certificate must contain the fully qualified DNS
(Domain Name Server) name of the machine running the Unicenter CA-
XCOM Data Transport Server as part of the certificate.
b. Edit the subjectAltName option in the [SSL_server_extensions] section of
the cassl.conf file, replacing machine_DNS_name with the machines
DNS name.
2. From the command prompt, issue the makeserver script to generate the
certificate:
makeserver
The makeserver script uses the serverssl.conf file and the cassl.pem file to
generate a server certificate and a key file. The server certificate,
servercert.pem, is saved in the certs subdirectory. The key file, generated as
serverkey.pem, is saved in the private subdirectory.
3. From the command prompt run the listserver script.
listserver
This script displays the server certificate and information stored in the
package.
Creating the Client Certificate
To create the client certificate, follow these steps:
1. Create a configuration file to use as input to the openssl utility. A sample file,
named clientssl.conf, was installed. Edit the [req_distinguished_name]
section, changing the values to meet your system requirements.
2. From the command prompt, issue the makeclient script to generate the
certificate.
makeclient
The makeclient script uses the clientssl.conf file and the cassl.pem file to
generate a client certificate and a key file. The certificate, clientcert.pem, is
saved in the certs subdirectory. The key file, generated as clientkey.pem, is
saved in the private subdirectory.
Configuring Unicenter CA-XCOM Data Transport SSL Server
3. From the command prompt, run the listclient script.
listclient
The listclient script displays the client certificate and information stored in
the package.
Configuring Unicenter CA-XCOM Data Transport SSL Server
Use the following procedure to configure Unicenter CA-XCOM Data Transport
to use the CA and server certificates for establishing server (remote) SSL
connections:
1. Review and modify the Unicenter CA-XCOM Data Transport SSL
configuration file, configssl.cnf, so that the settings meet your site standards.
Server connections use the RECEIVE_SIDE values.
2. Set the XCOM_CONFIG_SSL parameter in your default table/global file to
point to your customized configssl.cnf file.
3. Configure Unicenter CA-XCOM Data Transport to receive remote SSL
connections:
For z/OS, specify the TCP/IP port that will accept SSL connection
requests using the SSLPORT default table parameter.
For UNIX, during installation, manually add the txpis service and the
TCP/IP port that will accept SSL connection requests to the inetd
configuration files.
For Widows, specify the TCP/IP port that that will accept SSL
connection requests using the SSL Port Number on the TCP/IP tab in the
Global Parameters GUI.
4. Verify that the port that receives incoming SSL connections is a unique port
that is not in use by any other application. The port used for incoming
TCP/IP connections cannot also be used for incoming SSL connections. If
Unicenter CA-XCOM Data Transport will be receiving both incoming
TCP/IP connections and incoming SSL connections, then two ports are
required.
For z/OS, reassemble the default table and restart the Unicenter
CA-XCOM Data Transport server (started task).
For UNIX and Windows, restart the Unicenter CA-XCOM Data
Transport service.
Configuring the Unicenter CA-XCOM Data Transport Client
Configuring the Unicenter CA-XCOM Data Transport Client
Use the following procedure to configure the Unicenter CA-XCOM Data
Transport client to use the CA certificate and the server certificate when
establishing client (local) SSL connections:
1. Review and modify the settings of the Unicenter CA-XCOM Data Transport
SSL configuration file, configssl.cnf, as appropriate for your system. Client
connections use the INITIATE_SIDE values.
2. Point the XCOM_CONFIG_SSL parameter in your default table/global file to
your customized configssl.cnf file.
For z/OS, the XCOM_CONFIG_SSL parameter can also be specified as a
destination member parameter.
For UNIX and Windows, the XCOM_CONFIG_SSL parameter can also
be specified in your configuration (cnf) file.
3. Set the SECURE_SOCKET parameter to YES to indicate an SSL connection.
For z/OS, specify the SECURE_SOCKET parameter in the SYSIN01 or
the destination member.
For UNIX and Windows, specify the SECURE_SOCKET parameter in the
configuration (cnf) file.
4. Specify the port through which the remote Unicenter CA-XCOM Data
Transport partner accepts SSL connections using the PORT parameter.
5. Initiate the transfer request.


Chapter
6
Troubleshooting

This chapter contains information about:
Identifying and resolving problems
Contacting Computer Associates Customer Support
Receiving ongoing product releases and maintenance
Requesting product enhancements
Troubleshooting 61
Diagnostic Procedures
See the flowchart below for a summary of the procedures you should follow if
you have a problem with a Computer Associates software product. Each of these
procedures is detailed in the following sections.

Categorize
problem and
collect data. See
Collecting
Diagnostic Data.
Try to identify
problem. See
Interpreting
Diagnostic
Data.
See if fix exists.
See Contacting
Customer
Support.
FIX
FOUND?
PROBLEM
SOLVED?
Collect diagnostic
data and call
support. See
Calling Customer
Support.
Work with
Customer
Support to solve
problem.
Apply fix and
verify that
problem is
solved.
Keep information
for future
reference.
Software
problem
occurs.
NO
YES
YES
NO

Collecting Diagnostic Data
The following information is helpful in diagnosing problems that might occur:
Relevant system log console listings or traces
Relevant system dumps or product dumps
List of other third-party products that might be involved
Manufacturer, model number, and capacity of your hardware
Numbers and text of third-party or CA error messages associated with the
problem
Names of panels where the problem occurs
Listings of all fixes applied to all relevant software, including:
The dates the fixes were applied
Fix numbers
Names of components to which fixes were applied
Short description of problems
Interpreting Diagnostic Data
When you have collected the specified diagnostic data, write down your answers
to the following questions:
1. What was the sequence of events prior to the error condition?
2. What circumstances existed when the problem occurred and what action did
you take?
3. Has this situation occurred before? What was different then?
4. Did the problem occur after a particular PTF was applied or after a new
release of the software was installed?
5. Have you recently installed a new release of the operating system?
6. Has the hardware configuration (tape drives, disk drives, and so forth)
changed?
From your response to these questions and the diagnostic data, try to identify the
cause and resolve the problem.
Troubleshooting 63
Contacting Customer Support
Contacting Customer Support
For online technical assistance and a complete list of locations and phone
numbers, contact Customer Support at http://ca.com/supportconnect.
Customer support is available 24 hours a day, 7 days a week.
For telephone assistance, call:
U.S. and Canada 1-800-645-3042
International (1) 631-342-4683
Product Releases and Maintenance
Clients are requested to operate only under currently supported releases of the
product.
Clients with current maintenance agreements also receive ongoing maintenance.
When a new release of the system is available, a notice is sent to all current
clients.

Index

A
accessing window station and desktop, 2-57
AGE_TIME, 2-4
ALLOCATION_TYPE, mainframe file creation
parameter, 2-23
ATOE.TAB, 1-2
ATOE_FILENAME, global parameter, 2-5
automatic startup, 2-59
B
Batch-Interactive group, 2-57, 4-20
before starting the uninstall, 1-4
BLKSIZE parameter, 2-23
C
CA certificate for SSL, 5-2
expiration, 5-2
CARRIAGE_CONTROL_CHARACTERS parameter,
2-24
CARRIAGE_FLAG parameter, 2-24
changing local system port, 3-8
changing LU alias, 1-9
CHECKPOINT_COUNT, checkpoint parameter, 2-25
CLASS parameter, 2-25
client certificate for SSL, 5-3
CODE_FLAG parameter, 2-26
CODETABL, 2-5, 2-26
communications parameter, DESTINATION_TYPE,
2-29
COMPRESS, data transfer parameter, 2-27
configuration files
editing, 2-3
parameter format, 2-3
precedence of parameter values
at command prompt, 4-5
in GUI, 4-4
XCOM.CNF, 2-1, 2-23
XCOM.GLB, 2-1, 2-4, 4-10
XCOM.SES, 2-1, 2-21, 4-12
configuring Unicenter CA-XCOM Data Transport
SSL client, 5-5
SSL server, 5-4
CONTROL parameter, 2-28
CONVERT_CLASSES, global parameter, 2-5
COPIES parameter, 2-28
CPI-C
side information, 1-10
side information record, 2-2
symbolic destination, 1-10
CREATE_DIRECTORIES, global parameter, 2-5
Customer Support, 6-4
customizing notification, 4-33
Index1

D
DAEMON_TIMEOUT, global parameter, 2-6
data transfer parameters
COMPRESS, 2-27
VERSION, 2-54
DATACLAS, tape parameter, 2-6, 2-28
DEBUG_FLAG, global parameter, 2-6
default parameters, XCOM.GLB, 4-10
default paths and directories, 4-2
DEN, tape parameter, 2-28
desktop, creating group to access, 2-57
DESTINATION parameter, 2-29
DESTINATION_TYPE, communications parameter,
2-29
diagnosing problems, 6-2
DISPOSITION parameter, 2-29
domain name, 3-3, 3-7
Domain parameter (Trusted Access), 4-35
DOMAIN, global parameter, 2-6
DSNTYPE, tape parameter, 2-7, 2-30
E
encrypted parameter values, format, 4-7
EOL_CLASSES, global parameter, 2-7
ERRORLEVEL return codes, xcomqm.exe, 4-16
ETOA.TAB, 1-2
ETOA_FILENAME, global parameter, 2-7
EXPDT, tape parameter, 2-30
EXPIRATION_TIME, global parameter, 2-8
F
failure of transfer in starting state, 4-15
FCB parameter, 2-31
file access, 1-11
FILE_ACCESS_PASSWORD, global parameter, 2-8
FILE_ACCESS_USERNAME, 2-31
global parameter, 2-8
FILE_OPTION parameter, 2-31
FILE_OPTION_RF parameter, 2-33
FORM, send report parameter, 2-34
fully qualified domain name, 3-3
G
global parameters, 4-10
AGE_TIME, 2-4
ATOE_FILENAME, 2-5
CODETABL, 2-5
CONVERT_CLASSES, 2-5
CREATE_DIRECTORIES, 2-5
DAEMON_TIMEOUT, 2-6
DEBUG_FLAG, 2-6
DOMAIN:, 2-6
EOL_CLASSES, 2-7
ETOA_FILENAME, 2-7
EXPIRATION_TIME, 2-8
FILE_ACCESS_PASSWORD, 2-8
IMPLICIT_PACKING, 2-8
INTERNAL_CONVERSION_TABLES, 2-9
MAIL_PASSWORD, 2-9
MAIL_USERNAME, 2-9
MAX_QUEUE_ENTRIES, 2-10
MAX_SESSIONS_ENTRIES, 2-10
METACODE_CLASSES, 2-10
PORT, 2-11
PROTOCOL, 2-11
QUEUE_PATH, 2-11
REMOVE_TRAIL_BLANKS, 2-12
SECURE_SOCKET, 2-12
SESSIONS_FILE, 2-13
SHELL_CMD, 2-13
SOCK_DELAY, 2-13
SOCK_RCV_BUF_SIZE, 2-14
SOCK_SEND_BUF_SIZE, 2-14
STAT_FREQUENCY, 2-15
STORCLAS, 2-14
TCP_CMD, 2-15
TEMPDIR, 2-15
TP_CMD, 2-15
TRACE_PATH, 2-16
Index2 Administrator Guide

TXPI_BUF_SIZE, 2-16
TXPI_RECEIVE_TIMEOUT, 2-16
TXPI_SEND_CHECK_FREQ, 2-16
TXPI_TERM_TIMEOUT, 2-17
WRITE_EOF, 2-17
XCOM_CONFIG_SSL, 2-17
XCOM_PASSWORD, 2-17
XCOM_SHOW_CIPHER, 2-18
XCOM_USERID, 2-18
XENDCMD, 2-18
XLOGFILE, 2-19
XLPCMD, 2-19
XNOTIFYCMD, 2-19
XPPCMD, 2-19
XPRECMD, 2-20
XTRACE, 2-20
Group Name parameter (Trusted Access), 4-35
group, Batch-Interactive, 4-20
H
HOLDFLAG parameter, 2-34
host name, 3-3, 3-7
I
IBM mainframe file creation parameters
ALLOCATION_TYPE, 2-23
NUM_OF_DIR_BLOCKS, 2-40
PRIMARY_ALLOC, 2-41
SECONDARY_ALLOC, 2-49
UNIT_RF, 2-53
VOLUME_RF, 2-55
IMPLICIT_PACKING, global parameter, 2-8
INTERNAL_ CONVERSION_ TABLES, global
parameter, 2-9
IP address, 3-3, 3-7
L
LABEL, tape parameter, 2-35
LABELNUM, tape parameter, 2-35
LCLNTFYL, notification parameter, 2-9, 2-36
local system port, 3-8
LOCAL_FILE, send file parameter, 2-36
LOCAL_FILE_RF parameter, 2-36
LOCAL_FILE_SJ parameter, 2-37
LOCAL_FILE_SR parameter, 2-37
LOCAL_NOTIFY, notification parameter, 2-37
LRECL parameter, 2-38
LU alias, changing, 1-9
LU6RECV, 1-10
LU6SEND, 1-10
M
MAIL_PASSWORD, global parameter, 2-9
MAIL_USERNAME, global parameter, 2-9
managing the queue from command line, 4-14
MAX_QUEUE_ENTRIES, global parameter, 2-10
MAX_SESSIONS_ENTRIES, 2-21, 4-12
MAXRECLEN parameter, 2-38
METACODE_CLASSES, global parameter, 2-10
MGMTCLAS parameter, 2-10, 2-38
modifying
global values, GUI, 3-8
printing scripts, 4-29
N
notification parameters
LCLNTFYL, 2-9, 2-36
LOCAL_NOTIFY, 2-37
NOTIFY_NAME, 2-39
NOTIFYL, 2-39
NOTIFYR, 2-39
RMTNTFYL, 2-12, 2-48
notification script, XCOMNTFY, 4-33
Index3

NOTIFY_NAME, notification parameter, 2-39
NOTIFY_TERM parameter, 2-40
NOTIFYL, notification parameter, 2-39
NOTIFYR, notification parameter, 2-39
NUM_OF_DIR_BLOCKS, mainframe file creation
parameter, 2-40
NUMBER_OF_RETRIES parameter, 2-41
O
open configuration file, GUI, 4-4
overriding parameter values
at command line, 4-5
in GUI, 4-4
P
parallel sessions and XCOM.SES, 2-21, 4-12
parameter values
encrypted, 4-7
using at command prompt, 4-5
using in GUI, 4-4
parameters, guidelines, 4-6
PASSWORD parameter, 2-41
Password parameter (Trusted Access), 4-35
permissions, 2-58, 4-8
port
in GUI, 3-5
local system, 3-8
PORT, 2-11, 2-41, 3-4
XCOM.CNF parameter, 2-41
post processing, 4-20
post transfer script, XCOMEND, 4-24
precedence of parameter values
at command prompt, 4-5
in GUI, 4-4
prerequisites, TCP/IP, 3-1
PRIMARY_ALLOC, mainframe file creation
parameter, 2-41
printing script, XCOMLP, 4-29
PRIORITY, queue parameter, 2-42
problems, diagnosing, 6-2
PROTOCOL, 3-4
protocol and port in GUI, 3-6
protocols
APPCs, 4-2
in GUI, 3-5
Q
queue manager (XCOMQM), 4-14
QUEUE parameter, 2-43
queue parameters
PRIORITY, 2-42
START_DATE, 2-50
START_TIME, 2-51
QUEUE_PATH, global parameter, 2-11
R
RECORD_FORMAT parameter, 2-43
registry entry, 1-2, 1-4
remote system, 2-2, 3-7
REMOTE_FILE parameter, 2-45
REMOTE_FILE_RF parameter, 2-45
REMOTE_SYSTEM parameter, 2-45
REMOTE_SYSTEM_RF parameter, 2-46
REMOTE_SYSTEM_SJ parameter, 2-46
REMOTE_SYSTEM_SR parameter, 2-46
REMOVE_TRAIL_BLANKS
parameter, 2-47

REPORT_TITLE parameter, 2-47
resolving symbolic names, TCP/IP, 3-7
restart parameter, RESTART_SUPPORTED, 2-47
RETPD, tape parameter, 2-48
RETRY_TIME parameter, 2-48
RMTNTFYL, notification parameter, 2-12, 2-48
S
scripts
Unicenter CA-XCOM Data Transport, 4-20
XCOMEND, 4-24
XCOMLP, 4-29
XCOMNTFY, 4-33
XCOMPP, 4-21
SECONDARY_ALLOC, mainframe file creation
parameter, 2-49
SECURE_SOCKET
security, 1-11
jobs and scripts, 1-12
parameter encryption, 1-14
parameters, 1-13
security parameter, TRUSTED, 2-53
send and retrieve file parameters
FILE_OPTION, 2-31
FILE_OPTION_RF, 2-33
server certificate for SSL, 5-3
service-specific error messages, 2-60
session control, 2-21, 4-12
SESSIONS_FILE, global parameter, 2-13
setting session control parameters, 2-21, 4-12
SHELL_CMD, global parameter, 2-13
SNA configuration file, 1-10
SOCK_DELAY, global parameter, 2-13
SOCK_RCV_BUF_SIZE, global parameter, 2-14
SOCK_SEND_BUF_SIZE, global parameter, 2-14
SPACE parameter, 2-50
specifying remote system, 3-7
SPOOL_FLAG parameter, 2-50
SSL
CA certificate, 5-2
expiration, 5-2
client
certificate, 5-3
configuring, 5-5
mode, 5-1
server
certificate, 5-3
configuring, 5-4
START_DATE, queue parameter, 2-50
START_TIME, queue parameter, 2-51
starting XCOMD Unicenter CA-XCOM Scheduler
service, 2-59
STAT_FREQUENCY, global parameter, 2-15
STORCLAS parameter, 2-14, 2-51
System Name parameter (Trusted Access), 4-35
T
tape parameters
DATACLAS, 2-6
DEN, 2-28
DSNTYPE, 2-7
EXPDT, 2-30
LABEL, 2-35
LABELNUM, 2-35
RETPD, 2-48
TAPE, 2-51
UNITCT, 2-53
VOLCT, 2-54
VOLSQ, 2-54
TAPE, tape parameter, 2-51
TCP/IP
name resolution, 3-7
port, 2-11, 2-41
prerequisites, 3-1
protocols, 3-1, 3-4
worksheet, 3-3
TCP_CMD, global parameter, 2-15
TEMPDIR, global parameter, 2-15
Index5

TP
LU6RECV, 1-10
LU6SEND, 1-10
XCOMRECV, 1-10
XCOMSEND, 1-10
TP_CMD, global parameter, 2-15
TPSETUP, 1-10
program, 1-9
TRACE_PATH, global parameter, 2-16
tracing XCOMD Unicenter CA-XCOM Scheduler
service, 2-61
TRANSFER_ID parameter, 2-51
TRANSFER_TYPE parameter, 2-52
TRANSFER_USR_DATA parameter, 2-52
transfers
failure in starting state, 4-15
scheduled, 4-8
TRUNCATION parameter, 2-52
Trusted Access, 1-12
parameters, 4-35
Domain, 4-35
Group Name, 4-35
Password, 4-35
System Name, 4-35
User Name, 4-36
starting the interface, 4-34
using the interface, 4-36
trusted registry entry, 1-2, 1-4
TRUSTED, security parameter, 2-53
tuning and performance parameters, 3-9
TXPI_BUF_SIZE, global parameter, 2-16
TXPI_RECEIVE_TIMEOUT, global parameter, 2-16
TXPI_SEND_CHECK_FREQ, global parameter, 2-16
TXPI_TERM_TIMEOUT, global parameter, 2-17
U
Unicenter CA-XCOM Data Transport configuration
parameters
in XCOM.CNF configuration file, 2-23
in XCOM.GLB configuration file, 2-4
in XCOM.SES configuration file, 2-21
Unicenter CA-XCOM Data Transport parameters, 4-4
Unicenter CA-XCOM Data Transport, using with
TCP/IP, 3-1
UNIT parameter, 2-53
UNIT_RF, retrieve file parameter, 2-53
UNITCT, tape parameter, 2-53
User Name parameter (Trusted Access), 4-36
USER_DATA parameter, 2-53
USERID parameter, 2-54
using scripts, 4-20
V
Version 2 option, 3-5
VERSION, data transfer parameter, 2-54
VOLCT, tape parameter, 2-54
VOLSQ, tape parameter, 2-54
VOLUME parameter, 2-55
VOLUME_RF, retrieve file parameter, 2-55
W
window station, creating group to access, 2-57
WRITE_EOF, global parameter, 2-17
X
XCOM.CNF, 4-5
configuration file, 2-1, 2-23
XCOM.CNF parameters, 2-23
BLKSIZE, 2-23
CARRIAGE_CONTROL_CHARACTERS, 2-24
CARRIAGE_FLAG, 2-24
CHECKPOINT_COUNT, 2-25
CLASS, 2-25
CODE_FLAG, 2-26
CODETABL, 2-26
COMPRESS, 2-27

CONTROL, 2-28
COPIES, 2-28
DATACLAS, 2-28
DEN, 2-28
DESTINATION, 2-29
DESTINATION TYPE, 2-29
DISPOSITION, 2-29
DSNTYPE, 2-30
EXPDT, 2-30
FCB, 2-31
FILE_OPTION, 2-31
FILE_OPTION_RF, 2-33
FORM, 2-34
HOLDFLAG, 2-34
LABEL, 2-35
LABELNUM, 2-35
LCLNTFYL, 2-9, 2-36
LOCAL_FILE, 2-36
LOCAL_FILE_RF, 2-36
LOCAL_FILE_SJ, 2-37
LOCAL_FILE_SR, 2-37
LOCAL_NOTIFY, 2-37
LRECL, 2-38
MAXRECLEN, 2-38
MGMTCLAS, 2-10, 2-38
NOTIFY_NAME, 2-39
NOTIFY_TERM, 2-40
NOTIFYL, 2-39
NOTIFYR, 2-39
NUM_OF_DIR_BLOCKS, 2-40
NUMBER_OF_RETRIES, 2-41
PASSWORD, 2-41
PORT, 2-41
PRIMARY_ALLOC, 2-41
PRIORITY, 2-42
PROTOCOL, 2-42
QUEUE, 2-43
RECORD_FORMAT, 2-43
REMOTE_FILE, 2-45
REMOTE_FILE_RF, 2-45
REMOTE_SYSTEM, 2-45
REMOTE_SYSTEM_RF, 2-46
REMOTE_SYSTEM_SJ, 2-46
REMOTE_SYSTEM_SR, 2-46
REMOVE_TRAIL_BLANKS, 2-47
REPORT_TITLE, 2-47
RESTART_SUPPORTED, 2-47
RETPD, 2-48
RETRY_TIME, 2-48
RMTNTFYL, 2-12, 2-48
SECONDARY_ALLOC, 2-49
SECURE_SOCKET, 2-49
SPACE, 2-50
SPOOL_FLAG, 2-50
START_DATE, 2-50
START_TIME, 2-51
STORCLAS, 2-51
TAPE, 2-51
TRANSFER_ID, 2-51
TRANSFER_TYPE, 2-52
TRANSFER_USR_DATA, 2-52
TRUNCATION, 2-52
TRUSTED, 2-53
UNIT, 2-53
UNIT_RF, 2-53
UNITCT, 2-53
USER_DATA, 2-53
USERID, 2-54
VERSION, 2-54
VOLCT, 2-54
VOLSQ, 2-54
VOLUME, 2-55
VOLUME_RF, 2-55
XCOM_CONFIG_SSL, 2-55
XIDEST, 2-55
XLUNAME, 2-55
XMODE, 2-56
XNODESPEC, 2-56
XTRACE, 2-56
XCOM.GLB, 4-10
and command prompt, 4-5
configuration file, 2-1
in GUI, 4-4
XCOM.SES configuration file, 2-1, 2-2, 2-21
XCOM_CONFIG_SSL
parameter, 2-55
XCOM_HOME environment variable, 4-1
XCOM_PASSWORD, global parameter, 2-17
XCOM_SHOW_CIPHER, global parameter, 2-18
XCOM_USERID, global parameter, 2-18
XCOMD Unicenter CA-XCOM Scheduler service,
2-21, 2-57, 2-58, 4-7
removing, 1-6
starting, 2-59
stopping, 2-60
tracing, 2-61
XCOMEND script, 4-24
XCOMLP script, 4-29
Index7

XCOMNTFY script, 4-33
XCOMPP script, 4-21
XCOMQM, 4-14
command line syntax, 4-14
xcomqm.exe, ERRORLEVEL return codes, 4-16
XCOMRECV, 1-10
XCOMSEND, 1-10, 4-29
XCOMTCP, 3-4
XENDCMD, global parameter, 2-18
XIDEST parameter, 2-55
XLOGFILE, global parameter, 2-19
XLPCMD, global parameter, 2-19
XLUNAME parameter, 2-55
XMODE parameter, 2-56
XNODESPEC parameter, 2-56
XNOTIFYCMD, global parameter, 2-19
XPPCMD, global parameter, 2-19
XPRECMD, 2-20
XTRACE, global parameter, 2-20
XTRACE, testing and tracing parameter, 2-56


Manual Xcom J025731e

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Manual Xcom J025731e

Uploaded by

Copyright:

Available Formats

Unicenter

. This includes upgrading or reinstalling your

You might also like