XCOMTCP(1) XCOMTCP(1)
En este simple pero útil Post encontrarás la referencia al producto XCOM (Unicenter CA-XCOM Data Transport). Primero, conozcamos el producto.
escribe man xcomtcp para ver las características.
En este simple pero útil Post encontrarás la referencia al producto XCOM (Unicenter CA-XCOM Data Transport). Primero, conozcamos el producto.
escribe man xcomtcp para ver las características.
XCOMTCP(1) XCOMTCP(1)
"03/18/05"
" Unicenter CA-XCOM Data Transport"
" CA, Inc."
NAME
xcomtcp - execute XCOM file transfer program for TCP/IP
networks
SYNOPSIS
xcomtcp [ -h ] [ -r ] [ -iqrst ] [ -cnumber ] [ -f parms . .
. ] [ -xdebuglevel ] [ -vversion_number ]
DESCRIPTION
xcomtcp reads the parameter file, xcom.cnf, and additional
files and parameters specified in parms and executes the
specified file transfer.
Parameters read in from the parameter file are in the form
of assignment statements, i. e., a parameter name, followed
by an = sign, followed by a string of characters terminated
by a newline. Empty lines and line beginning with a # are
discarded. Blanks and tabs may be embedded as part of an
argument.
Parameters contained in the parms fields are either the
names of files or individual assignment statements that will
be used to set a single variable.
Parameter file xcom.cnf is always read.
The precedence of parameter setting is: program defaults,
environment variables, contents of the file
/usr/spool/xcom/config/xcom.cnf, arguments following the -f
option in the order in which they appear.
OPTIONS
-cnumber
Invoke xcomtcp using the command line capability.
number specifies the specific type of transfer to be
attempted, as follows:
1 Send file to remote system
2 Send report to be printed on remote system
3 Send job to be executed on remote system
4 Receive file from remote system.
-f parms . . .
Xcom62 parameters are read from parms and are used to
set the parameters of the transfer. Parameters can be
either assignment statements to set individual XCOM
parameters or names of files containing parameter
assignments.
Page 1 (printed 12/2/08)
XCOMTCP(1) XCOMTCP(1)
-h Display help. The usage message is displayed and
xcomtcp exits.
-i Set invocation mode.
-q Queue this transfer; default is to execute the transfer
immediately.
-r Display release level. The release level of the
software is displayed and xcomtcp exits.
-s Run xcomtcp using silent mode; no messages will be
output to stderr.
-t Send trace output to stderr.
-v Set version of CA-XCOM protocol to use during this
invocation of xcomtcp. Valid values are 1 and 2.
-xdebuglevel
Sets level of debugging output; higher integers give
more output.
EXAMPLES
xcomtcp -c1 -f LOCAL_FILE=dbextract REMOTE_FILE=XCOM.DB.EXTRACT
FILES
/usr/spool/xcom/xcom.log
/usr/spool/xcom/config/xcom.cnf
SEE ALSO
lp(1), mail(1), sh(1), xcom.cnf(5), xcom62(1)
Page 2 (printed 12/2/08)
Ahora, veamos la configuración XCOM. escribe more /usr/spool/xcom/config/xcom.cnf para ver cada uno de los parámetros.
REMOTE_SYSTEM=
# The name of the remote computer with which you are communicating.
# Using SNA Services this should be set to the name of the connection
# profile defined for the remote system.
XLUNAME=
# local lu name
XNODESPEC=
# xcom node specification
XMODE=XCOMMODE
# 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. Defaults to XCOMMODE.
XIDEST=
# Name of the intermediate destination for store-and-forward
# transfers. If this variable is null or unset then a direct connection to
# a remote system is attempted.
LOCAL_FILE=
# The name of the file on your local system that is being
# transferred. All local system file naming conventions apply. If this
# variable is null or unset, standard input is used. In this manner
# XCOM commands can be used in a pipeline or with redirection.
REMOTE_FILE=
# The file on the remote computer to which the transferred
# data is written, in the case of a SENDFILE function.
# The designated filename must be consistent with the file
# naming conventions of the remote system. The local XCOM
# system does not validate this name = ""; the remote I/O
# system determines whether or not the file name is valid.
# A maximum of 256 characters can be entered.
LOCAL_FILE_RF=
# The filename which is created, appended, or replaced on the
# local system when it receives a file. The file naming conventions
# of your local system apply.
REMOTE_FILE_RF=
# Indicates the name of the file to be retrieved from the remote
# system.
FILE_OPTION=CREATE
# Indicates how the transferred data is to be processed by the
# remote system. Valid options are:
# CREATE - Create a new file on the remote system.
# APPEND - Append this data to an existing file on the remote system.
# REPLACE - Replace an existing file on the remote system.
# When creating a file on an IBM mainframe system, some additional
# information may be necessary. See the explanations for the RECORD
# FORMAT, BLKSIZE, VOLUME and UNIT parameters for more
# information.
REMOVE_TRAIL_BLANKS=NO
# Indicates whether or not to remove the blanks at the end of each
# record when receiving a text file.
VOLUME=
# Only used when creating a file on an IBM mainframe (FILE_OPTION=
# CREATE). Specifies the volume on which the file is to be created.
# See the FILE_OPTION parameter for more information.
UNIT=
# Only used when creating a file on an IBM mainframe (FILE_OPTION=
# CREATE). Specifies the unit on which the file is to be created.
# See the FILE_OPTION parameter for more information.
RECORD_FORMAT=VB
# Specifies the record format of the dataset. Corresponds to
# the JCL RECFM subparameter.
# Valid options are:
# F Fixed Unblocked. Indicates that all records have the
# same length.
# FB Fixed Blocked. Indicates a fixed record length
# with multiple records per block.
# V Variable Unblocked. Indicates variable length records.
# VB Variable Blocked. Indicates variable length records
# with multiple records per block.
# U Undefined. The records are of undefined length.
# NOTE: In XCOM Version 2.0.0 or higher the following
# options are also valid:
#
# FA
# VA
# FM
# VM
# FS
# VS
# FBA
# VBA
# FBS
# VBS
# VBM
LRECL=160
# Specifies the actual or maximum length, in bytes, of a logical
# record. This parameter corresponds to the JCL LRECL subparameter.
# For variable blocked record format, this value should equal
# the maximum record length + 4. For fixed or fixed block record
# format, this value should equal the constant record length.
# A maximum of 5 characters may be entered.
BLKSIZE=800
# Specifies the block size of the dataset. For a fixed or
# fixed block record format, this value must be a multiple of
# the Record Length. For a variable record format it must be
# 4 bytes larger than the Record Length. For undefined record
# format, it must be larger than the largest record length. A
# maximum of 5 digits may be entered.
LOCAL_FILE_SR=
# Local filename to be sent as a report to the remote system.
CLASS=
# Indicates the print class to be assigned to this report on the
# remote system. If the remote system is an MVS computer,
# then this field designates the JES SYSOUT class.
DESTINATION=
# Indicates the printer or other device on the remote
# system to send the report. If unspecified, the
# remote system will send it to the system's default printer.
FORM=
# Indicates to the remote operator or user the type of form
# to print the report on. Since XCOM places the
# print job in the remote system's print queue, the print control
# functions will depend on the remote system. You must verify
# that the type of form you are requesting is available at the
# remote site.
FCB=
# Indicates the FCB JCL parameter when sending the report file
# to an MVS mainframe, to define print density, lines per page,
# etc.
COPIES=1
# The number of copies of the report that should be printed.
# A maximum of 3 characters may be printed.
HOLDFLAG=NO
# Indicates whether this transferred report file is to be
# placed on HOLD status on the remote system or is to be
# printed immediately. Specify Y to request that
# it be held.
REPORT_TITLE=
# This field will be interpreted depending on the type of the
# remote (receiving) system:
# - On a System/38, XCOM CPF will assume this to be the
# printer filename.
# - XCOM on MVS will interpret a non-blank value in
# this field to generate a separator page for this value.
# - On VAX/VMS, this title will be printed with the report.
# - XCOM UNIX will pass this field to the lp spooler
# as a title field.
# - When sending the report file to other systems, this
# field is generally used only as a descriptive comment
# and is not printed as part of the report.
# A maximum of 21 characters may be entered. The default for
# this parameter is blank.
CARRIAGE_CONTROL_CHARACTERS=OTHER
# Indicates the type of printer carriage control codes, if
# any, that are included in report file. Valid options are:
# ASA ASA control codes in column 1
# IBM IBM Machine Characters (valid only for MVS remote
# computer)
# OTHER no carriage control codes are being used
# BYPASSASA send a report already in ASA format. XCOM tells the
# partner to expect an ASA file but does not do the
# conversion
SPOOL_FLAG=YES
# Designates whether to spool the report to disk or to print it
# directly. If the remote computer is an IBM mainframe, this parameter
# will have no effect on the transfer.
DISPOSITION=DELETE
# Indicates what the remote system should do with the report
# file after the report has been printed. This field is ignored
# on IBM mainframe systems. Valid options are:
# DELETE delete after printing
# KEEP keep after printing
# HOLD hold after printing
LOCAL_FILE_SJ=
# Indicates the name of the file on the local system to be sent
# as a job.
USERID=
# The userid with the necessary system resource access
# privileges to process the file transfer on the remote system.
# This userid's privileges must include access to the system
# resources necessary to permit the transfer. A maximum
# of 12 characters may be entered.
PASSWORD=
# The password associated with the USERID. A maximum
# of 31 characters may be entered.
QUEUE=YES
# Indicates whether to execute the transmission requests
# immediately (specify NO) or to allow the request to be queued.
# (specify YES). Note that if NO is specified, the request will abort if the
# remote system is unavailable. If YES is specified,
# the START_TIME and START_DATE parameters are read. See
# these parameters for more information.
START_TIME=
# Specifies the time the transfer becomes eligible for
# execution. The format is hh:mm:ss. For example, 14:00:00 indicates
# a 2 p.m. starttime. If this field is blank, then current time is used.
START_DATE=
# Specifies the date the transfer becomes eligible for execution.
# The format is mm/dd/yy. For example, 02/28/92 indicates a
# February 28, 1992 start date. If this field is blank, then current time is used.
NOTIFY_NAME=
# The user on the remote system who is to be notified when
# XCOM has completed the transfer. If the remote system
# is an MVS computer, XCOM uses the NOTIFYR parameter value
# to determine who is to be notified.
NOTIFYR=NONE
# Remote user notification type.
# NONE Do not notify.
# TSO Notify TSO user.
# ROSCOE Notify ROSCOE user.
# WTO Write to operator.
# WRITE Same as WTO.
# MAIL Mail to user.
# ALL Notify all.
# CICS Notify CICS user (not used in Release 1).
# LU Notify Logical Unit (not used in Release 1).
#
# NOTE: Since some of these options are not appropriate for every XCOM
# supported platform, they may be treated differently by XCOM on
# different platforms.
# To find out how exactly each option will be treated consult
# XCOM documentation for your target platform and/or contact your
# target platform's System Administrator.
LOCAL_NOTIFY=
# The user on the local system who is to be
# notified when XCOM has completed the transfer.
# XCOM uses the value of NOTIFYL to determine the type of
# notification to deliver. The system default is the string contained
# in the LOGNAME environment variable.
NOTIFYL=NONE
# Local user notification type.
# NONE Do not notify.
# TSO Notify TSO user.
# ROSCOE Notify ROSCOE user.
# WTO Write to operator.
# WRITE Same as WTO.
# MAIL Mail to user.
# ALL Notify all.
# CICS Notify CICS user (not used in Release 1).
# LU Notify Logical Unit (not used in Release 1).
#
# NOTE: All of the above values are valid, however, the most
# suitable values for Unix system are:
# WRITE Write to user,
# MAIL Mail to user,
# ALL Write to all users.
NOTIFY_TERM=
# Specifies terminal 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
MAXRECLEN=1024
# When transferring 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 then the TRUNCATION
# parameter is read. When transferring binary files, this value
# indicates the length of the records that are transferred. This
# value must be equal to or lower than the LRECL on the remote
# system.
CODE_FLAG=ASCII
# Identifies the type of data being transferred. Specify BINARY to
# transfer a binary file. The local system will not
# translate this data. Specify EBCDIC to transfer an EBCDIC file.
# The data will be translated from from ASCII to EBCDIC
# when sending.
CARRIAGE_FLAG=YES
# Specifies that the file being transferred is a text file and
# that a newline character should be added to the end of incoming
# records and that newline characters should be removed from
# the ends of lines before the outgoing record is sent.
TRUNCATION=NO
# Indicates whether or not XCOM will truncate any excess
# characters on the source file which exceed the maximum record
# length permitted on the target computer. If NO is selected,
# XCOM will abort the transfer if the maximum record length is
# exceeded.
COMPRESS=YES
# Indicates whether or not XCOM is to compress the
# data being transferred (and decompress it at the other end).
# Compressing the data will decrease the transmission time.
# Specify NO if you do not want the file compressed.
XTRACE=0
# Level of execution tracing desired. Defaults to 0 - no
# tracing. Level 9 (the maximum) shows contents of data
# buffers.
DEBUG_FLAG=NO
# Specify YES to cause the transaction to print a trace to file
# /tmp/.it rather than to /usr/spool/xcom/trace/.TRA.
# In addition to the transfer trace information the initialization
# part will also be traced. The trace level is still being set
# by the variable XTRACE.
XLOGFILE=/usr/spool/xcom/xcom.log
# Name of file where XCOM will deposit a log of its
# activities. Defaults to /usr/spool/xcom/xcom.log.
XVIEW_CMD=/usr/lib/xcom/xcomlog
# Only used by xcomtool.
# The command that the menu uses to invoke the trace function.
DESTINATION_TYPE=OTHER
# Indicates the type of target system. Choices are: Midrange,
# Host, and Other.
#---------------------------------------------------------------------
# The following parameters are only used in Version 2 transfers.
#---------------------------------------------------------------------
VERSION=2
# Indicates the version of XCOM protocol to be used for this transfer.
ALLOCATION_TYPE=
# Indicates Cylinders, Tracks, or Blocks for allocation type.
# VALUE DESCRIPTION
# CYL Cylinders
# TRK Tracks
# BLK Blocks
NUM_OF_DIR_BLOCKS=0
# Specifies the number of directory blocks to allocate.
PRIMARY_ALLOC=1
# Identifies primary Cyls/Trks/Blks allocation.
SECONDARY_ALLOC=0
# Identifies secondary Cyls/Trks/Blks allocation.
CHECKPOINT_COUNT=1000
# Defines how often (based on record count) the sending system will request
# a checkpoint to be taken. 0000 denotes no checkpointing.
NUMBER_OF_RETRIES=1
# The maximum number of retries before a failed transfer is logged as failed
# and taken out of the transfer queue.
RESTART_SUPPORTED=YES
# Indicates whether automatic checkpoint/restart is supported.
RETRY_TIME=1
# The number of seconds between retries of unsuccessful transfers. If it is
# zero, then no retries will be attempted.
#---------------------------------------------------------------------
# The following parameters are valid for CA-XCOM 3.0 systems
#---------------------------------------------------------------------
PROTOCOL=TCPIP
# Type of communications protocol to use. Valid values are SNA and TCPIP.
PORT=8044
# The port number on the remote CA-XCOM server that is listening for
# txpi service. Valid only for PROTOCOL=TCPIP.
UMASK=022
# Used to set the permissions assigned to a file when the file is created
# on the local system. The value is expressed as an octal number as used
# in the UNIX chmod command.
#---------------------------------------------------------------------
# The following parameters are valid for CA-XCOM 3.1 systems
#---------------------------------------------------------------------
DEN=1
# Density 1-4
EXPDT=
#Specify expiration date in yyddd format. Bypass if value set to 0 or left blank.
LABEL=SL
# Tape label SL/NL/NSL/SUL/BLP/LTM/AL/AUL
LABELNUM=1
# Tape label number 1-9999
RETPD=0
# Retention period 0-9999
TAPE=N
# Tape flag Y/N
UNITCT=1
# Unit count 1-20
VOLCT=1
# Volume count 1-255
VOLSQ=1
# Volume sequence 1-255
#---------------------------------------------------------------------
# The following parameters are valid for CA-XCOM r11 systems
#---------------------------------------------------------------------
DSNTYPE=
# (MVS SMS only) Data set type definition, specified as LIBRARY or
# PDS. If omitted, the site system default is used.
#
# Note: The DSNTYPE value of LIBRARY defines a PDSE and the DSNTYPE value of
# PDS defines a partitioned data set. These are IBM standards for SMS processing.
DATACLAS=
# (MVS SMS only.) One- to eight-character name of a data class to be used when
# allocating a new SMS-managed data set.
MGMTCLAS=
# (MVS SMS only.) One- to eight-character name of the management class to be used
# when allocating a new SMS-managed data set.
STORCLAS=
# (MVS SMS only.) One- to eight-character name of a storage class that is to be
# used for a new SMS-managed data set.
LCLNTFYL=
# Specifies the local user notification level.
# Value Definition
# --------------------------------------------------------------------
# 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
RMTNTFYL=
# Specifies the remote user notification level when sending data to a remote
# system.
# Value Definition
# --------------------------------------------------------------------
# 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
CODETABL=
# The prefix to the file names, atoe.tab and etoa.tab, containing the external
# ASCII-to-EBCDIC and EBCDIC-to-ASCII custom character conversion tables that
# determine which external translation tables will be used by the transfer.
# This parameter is valid only if INTERNAL_CONVERSION_TABLES=NO
XCOM_CONFIG_SSL=/usr/spool/xcom/config/configssl.cnf
# This parameter specifies the value of the configssl.cnf file
# path and file name
SECURE_SOCKET=NO
# This parameter has two value: YES and NO. When the value is set to YES = ""; the transfer
# uses an OpenSSL socket and must connect to a SSL listener on the remote partner.
# If the value is set to NO = ""; the transfer uses a Non OpenSSL socket.
Ya que tenemos una idea de lo que el producto realiza, vamos a empezar utilizandolo.
Espero les haya gustado!
Ahora, veamos la configuración XCOM. escribe more /usr/spool/xcom/config/xcom.cnf para ver cada uno de los parámetros.
REMOTE_SYSTEM=
# The name of the remote computer with which you are communicating.
# Using SNA Services this should be set to the name of the connection
# profile defined for the remote system.
XLUNAME=
# local lu name
XNODESPEC=
# xcom node specification
XMODE=XCOMMODE
# 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. Defaults to XCOMMODE.
XIDEST=
# Name of the intermediate destination for store-and-forward
# transfers. If this variable is null or unset then a direct connection to
# a remote system is attempted.
LOCAL_FILE=
# The name of the file on your local system that is being
# transferred. All local system file naming conventions apply. If this
# variable is null or unset, standard input is used. In this manner
# XCOM commands can be used in a pipeline or with redirection.
REMOTE_FILE=
# The file on the remote computer to which the transferred
# data is written, in the case of a SENDFILE function.
# The designated filename must be consistent with the file
# naming conventions of the remote system. The local XCOM
# system does not validate this name = ""; the remote I/O
# system determines whether or not the file name is valid.
# A maximum of 256 characters can be entered.
LOCAL_FILE_RF=
# The filename which is created, appended, or replaced on the
# local system when it receives a file. The file naming conventions
# of your local system apply.
REMOTE_FILE_RF=
# Indicates the name of the file to be retrieved from the remote
# system.
FILE_OPTION=CREATE
# Indicates how the transferred data is to be processed by the
# remote system. Valid options are:
# CREATE - Create a new file on the remote system.
# APPEND - Append this data to an existing file on the remote system.
# REPLACE - Replace an existing file on the remote system.
# When creating a file on an IBM mainframe system, some additional
# information may be necessary. See the explanations for the RECORD
# FORMAT, BLKSIZE, VOLUME and UNIT parameters for more
# information.
REMOVE_TRAIL_BLANKS=NO
# Indicates whether or not to remove the blanks at the end of each
# record when receiving a text file.
VOLUME=
# Only used when creating a file on an IBM mainframe (FILE_OPTION=
# CREATE). Specifies the volume on which the file is to be created.
# See the FILE_OPTION parameter for more information.
UNIT=
# Only used when creating a file on an IBM mainframe (FILE_OPTION=
# CREATE). Specifies the unit on which the file is to be created.
# See the FILE_OPTION parameter for more information.
RECORD_FORMAT=VB
# Specifies the record format of the dataset. Corresponds to
# the JCL RECFM subparameter.
# Valid options are:
# F Fixed Unblocked. Indicates that all records have the
# same length.
# FB Fixed Blocked. Indicates a fixed record length
# with multiple records per block.
# V Variable Unblocked. Indicates variable length records.
# VB Variable Blocked. Indicates variable length records
# with multiple records per block.
# U Undefined. The records are of undefined length.
# NOTE: In XCOM Version 2.0.0 or higher the following
# options are also valid:
#
# FA
# VA
# FM
# VM
# FS
# VS
# FBA
# VBA
# FBS
# VBS
# VBM
LRECL=160
# Specifies the actual or maximum length, in bytes, of a logical
# record. This parameter corresponds to the JCL LRECL subparameter.
# For variable blocked record format, this value should equal
# the maximum record length + 4. For fixed or fixed block record
# format, this value should equal the constant record length.
# A maximum of 5 characters may be entered.
BLKSIZE=800
# Specifies the block size of the dataset. For a fixed or
# fixed block record format, this value must be a multiple of
# the Record Length. For a variable record format it must be
# 4 bytes larger than the Record Length. For undefined record
# format, it must be larger than the largest record length. A
# maximum of 5 digits may be entered.
LOCAL_FILE_SR=
# Local filename to be sent as a report to the remote system.
CLASS=
# Indicates the print class to be assigned to this report on the
# remote system. If the remote system is an MVS computer,
# then this field designates the JES SYSOUT class.
DESTINATION=
# Indicates the printer or other device on the remote
# system to send the report. If unspecified, the
# remote system will send it to the system's default printer.
FORM=
# Indicates to the remote operator or user the type of form
# to print the report on. Since XCOM places the
# print job in the remote system's print queue, the print control
# functions will depend on the remote system. You must verify
# that the type of form you are requesting is available at the
# remote site.
FCB=
# Indicates the FCB JCL parameter when sending the report file
# to an MVS mainframe, to define print density, lines per page,
# etc.
COPIES=1
# The number of copies of the report that should be printed.
# A maximum of 3 characters may be printed.
HOLDFLAG=NO
# Indicates whether this transferred report file is to be
# placed on HOLD status on the remote system or is to be
# printed immediately. Specify Y to request that
# it be held.
REPORT_TITLE=
# This field will be interpreted depending on the type of the
# remote (receiving) system:
# - On a System/38, XCOM CPF will assume this to be the
# printer filename.
# - XCOM on MVS will interpret a non-blank value in
# this field to generate a separator page for this value.
# - On VAX/VMS, this title will be printed with the report.
# - XCOM UNIX will pass this field to the lp spooler
# as a title field.
# - When sending the report file to other systems, this
# field is generally used only as a descriptive comment
# and is not printed as part of the report.
# A maximum of 21 characters may be entered. The default for
# this parameter is blank.
CARRIAGE_CONTROL_CHARACTERS=OTHER
# Indicates the type of printer carriage control codes, if
# any, that are included in report file. Valid options are:
# ASA ASA control codes in column 1
# IBM IBM Machine Characters (valid only for MVS remote
# computer)
# OTHER no carriage control codes are being used
# BYPASSASA send a report already in ASA format. XCOM tells the
# partner to expect an ASA file but does not do the
# conversion
SPOOL_FLAG=YES
# Designates whether to spool the report to disk or to print it
# directly. If the remote computer is an IBM mainframe, this parameter
# will have no effect on the transfer.
DISPOSITION=DELETE
# Indicates what the remote system should do with the report
# file after the report has been printed. This field is ignored
# on IBM mainframe systems. Valid options are:
# DELETE delete after printing
# KEEP keep after printing
# HOLD hold after printing
LOCAL_FILE_SJ=
# Indicates the name of the file on the local system to be sent
# as a job.
USERID=
# The userid with the necessary system resource access
# privileges to process the file transfer on the remote system.
# This userid's privileges must include access to the system
# resources necessary to permit the transfer. A maximum
# of 12 characters may be entered.
PASSWORD=
# The password associated with the USERID. A maximum
# of 31 characters may be entered.
QUEUE=YES
# Indicates whether to execute the transmission requests
# immediately (specify NO) or to allow the request to be queued.
# (specify YES). Note that if NO is specified, the request will abort if the
# remote system is unavailable. If YES is specified,
# the START_TIME and START_DATE parameters are read. See
# these parameters for more information.
START_TIME=
# Specifies the time the transfer becomes eligible for
# execution. The format is hh:mm:ss. For example, 14:00:00 indicates
# a 2 p.m. starttime. If this field is blank, then current time is used.
START_DATE=
# Specifies the date the transfer becomes eligible for execution.
# The format is mm/dd/yy. For example, 02/28/92 indicates a
# February 28, 1992 start date. If this field is blank, then current time is used.
NOTIFY_NAME=
# The user on the remote system who is to be notified when
# XCOM has completed the transfer. If the remote system
# is an MVS computer, XCOM uses the NOTIFYR parameter value
# to determine who is to be notified.
NOTIFYR=NONE
# Remote user notification type.
# NONE Do not notify.
# TSO Notify TSO user.
# ROSCOE Notify ROSCOE user.
# WTO Write to operator.
# WRITE Same as WTO.
# MAIL Mail to user.
# ALL Notify all.
# CICS Notify CICS user (not used in Release 1).
# LU Notify Logical Unit (not used in Release 1).
#
# NOTE: Since some of these options are not appropriate for every XCOM
# supported platform, they may be treated differently by XCOM on
# different platforms.
# To find out how exactly each option will be treated consult
# XCOM documentation for your target platform and/or contact your
# target platform's System Administrator.
LOCAL_NOTIFY=
# The user on the local system who is to be
# notified when XCOM has completed the transfer.
# XCOM uses the value of NOTIFYL to determine the type of
# notification to deliver. The system default is the string contained
# in the LOGNAME environment variable.
NOTIFYL=NONE
# Local user notification type.
# NONE Do not notify.
# TSO Notify TSO user.
# ROSCOE Notify ROSCOE user.
# WTO Write to operator.
# WRITE Same as WTO.
# MAIL Mail to user.
# ALL Notify all.
# CICS Notify CICS user (not used in Release 1).
# LU Notify Logical Unit (not used in Release 1).
#
# NOTE: All of the above values are valid, however, the most
# suitable values for Unix system are:
# WRITE Write to user,
# MAIL Mail to user,
# ALL Write to all users.
NOTIFY_TERM=
# Specifies terminal 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
MAXRECLEN=1024
# When transferring 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 then the TRUNCATION
# parameter is read. When transferring binary files, this value
# indicates the length of the records that are transferred. This
# value must be equal to or lower than the LRECL on the remote
# system.
CODE_FLAG=ASCII
# Identifies the type of data being transferred. Specify BINARY to
# transfer a binary file. The local system will not
# translate this data. Specify EBCDIC to transfer an EBCDIC file.
# The data will be translated from from ASCII to EBCDIC
# when sending.
CARRIAGE_FLAG=YES
# Specifies that the file being transferred is a text file and
# that a newline character should be added to the end of incoming
# records and that newline characters should be removed from
# the ends of lines before the outgoing record is sent.
TRUNCATION=NO
# Indicates whether or not XCOM will truncate any excess
# characters on the source file which exceed the maximum record
# length permitted on the target computer. If NO is selected,
# XCOM will abort the transfer if the maximum record length is
# exceeded.
COMPRESS=YES
# Indicates whether or not XCOM is to compress the
# data being transferred (and decompress it at the other end).
# Compressing the data will decrease the transmission time.
# Specify NO if you do not want the file compressed.
XTRACE=0
# Level of execution tracing desired. Defaults to 0 - no
# tracing. Level 9 (the maximum) shows contents of data
# buffers.
DEBUG_FLAG=NO
# Specify YES to cause the transaction to print a trace to file
# /tmp/
# In addition to the transfer trace information the initialization
# part will also be traced. The trace level is still being set
# by the variable XTRACE.
XLOGFILE=/usr/spool/xcom/xcom.log
# Name of file where XCOM will deposit a log of its
# activities. Defaults to /usr/spool/xcom/xcom.log.
XVIEW_CMD=/usr/lib/xcom/xcomlog
# Only used by xcomtool.
# The command that the menu uses to invoke the trace function.
DESTINATION_TYPE=OTHER
# Indicates the type of target system. Choices are: Midrange,
# Host, and Other.
#---------------------------------------------------------------------
# The following parameters are only used in Version 2 transfers.
#---------------------------------------------------------------------
VERSION=2
# Indicates the version of XCOM protocol to be used for this transfer.
ALLOCATION_TYPE=
# Indicates Cylinders, Tracks, or Blocks for allocation type.
# VALUE DESCRIPTION
# CYL Cylinders
# TRK Tracks
# BLK Blocks
NUM_OF_DIR_BLOCKS=0
# Specifies the number of directory blocks to allocate.
PRIMARY_ALLOC=1
# Identifies primary Cyls/Trks/Blks allocation.
SECONDARY_ALLOC=0
# Identifies secondary Cyls/Trks/Blks allocation.
CHECKPOINT_COUNT=1000
# Defines how often (based on record count) the sending system will request
# a checkpoint to be taken. 0000 denotes no checkpointing.
NUMBER_OF_RETRIES=1
# The maximum number of retries before a failed transfer is logged as failed
# and taken out of the transfer queue.
RESTART_SUPPORTED=YES
# Indicates whether automatic checkpoint/restart is supported.
RETRY_TIME=1
# The number of seconds between retries of unsuccessful transfers. If it is
# zero, then no retries will be attempted.
#---------------------------------------------------------------------
# The following parameters are valid for CA-XCOM 3.0 systems
#---------------------------------------------------------------------
PROTOCOL=TCPIP
# Type of communications protocol to use. Valid values are SNA and TCPIP.
PORT=8044
# The port number on the remote CA-XCOM server that is listening for
# txpi service. Valid only for PROTOCOL=TCPIP.
UMASK=022
# Used to set the permissions assigned to a file when the file is created
# on the local system. The value is expressed as an octal number as used
# in the UNIX chmod command.
#---------------------------------------------------------------------
# The following parameters are valid for CA-XCOM 3.1 systems
#---------------------------------------------------------------------
DEN=1
# Density 1-4
EXPDT=
#Specify expiration date in yyddd format. Bypass if value set to 0 or left blank.
LABEL=SL
# Tape label SL/NL/NSL/SUL/BLP/LTM/AL/AUL
LABELNUM=1
# Tape label number 1-9999
RETPD=0
# Retention period 0-9999
TAPE=N
# Tape flag Y/N
UNITCT=1
# Unit count 1-20
VOLCT=1
# Volume count 1-255
VOLSQ=1
# Volume sequence 1-255
#---------------------------------------------------------------------
# The following parameters are valid for CA-XCOM r11 systems
#---------------------------------------------------------------------
DSNTYPE=
# (MVS SMS only) Data set type definition, specified as LIBRARY or
# PDS. If omitted, the site system default is used.
#
# Note: The DSNTYPE value of LIBRARY defines a PDSE and the DSNTYPE value of
# PDS defines a partitioned data set. These are IBM standards for SMS processing.
DATACLAS=
# (MVS SMS only.) One- to eight-character name of a data class to be used when
# allocating a new SMS-managed data set.
MGMTCLAS=
# (MVS SMS only.) One- to eight-character name of the management class to be used
# when allocating a new SMS-managed data set.
STORCLAS=
# (MVS SMS only.) One- to eight-character name of a storage class that is to be
# used for a new SMS-managed data set.
LCLNTFYL=
# Specifies the local user notification level.
# Value Definition
# --------------------------------------------------------------------
# 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
RMTNTFYL=
# Specifies the remote user notification level when sending data to a remote
# system.
# Value Definition
# --------------------------------------------------------------------
# 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
CODETABL=
# The prefix to the file names, atoe.tab and etoa.tab, containing the external
# ASCII-to-EBCDIC and EBCDIC-to-ASCII custom character conversion tables that
# determine which external translation tables will be used by the transfer.
# This parameter is valid only if INTERNAL_CONVERSION_TABLES=NO
XCOM_CONFIG_SSL=/usr/spool/xcom/config/configssl.cnf
# This parameter specifies the value of the configssl.cnf file
# path and file name
SECURE_SOCKET=NO
# This parameter has two value: YES and NO. When the value is set to YES = ""; the transfer
# uses an OpenSSL socket and must connect to a SSL listener on the remote partner.
# If the value is set to NO = ""; the transfer uses a Non OpenSSL socket.
Ya que tenemos una idea de lo que el producto realiza, vamos a empezar utilizandolo.
Espero les haya gustado!
No hay comentarios:
Publicar un comentario