402 - 401 - 400 - 308 - 307 - 306 - 305 - 304 - 303 - 301 - 206 - 205 - 204

TRANSFER PROTOCOL HTTP / HHTPS
XcMon is abble to use several file transfer protocols as FTP / FTPS, HTTP / HTTPS.
File transfer protocols managed by XcMon are defined using a symbolic name associated with a protocol type and related parameters.

PROCEDURE BEFORE TRANSFER
A procedure is executed before the file transfert and give acknowlegement to execute the transfer.

EXCLUDE FILE
When creating the transfer query, the user has the possibility of requesting exclusion options :
– File transfer may be ignored if the target file already exist.
– File transfer may be ignored if the source file is older than the target file.

ADDITIONAL ADRESSES
XcMon allows to accept incoming connexion from a recipeint on a system with several IP address that are not managed by a DNS (it can be the case with some Clusters for example).

FILE PARAMETERS FOR IBM Z/Os AND AS400
Symbolic name of IBM files parameters

SYMBOLIC DIRECTORY
Symbolic directories are used to define virtual directories.
A symbolic directory is defined with a symbolic name associated with virtal path and the reel path name of the directory.

QUERIES BATCH
Queries for transfer (files and messages) can be defined in XcWop operator and generated in a file on the remote site. This file can be used in batch mode to execute tranfer by a sample call to the symbolic name of the query.
This allow to centralize the maintenance of transfer commands

LISTEN IP ADRESSE
XcMon allows to force the listening on a specific IP address.
If this value is not given, the listening is executed on any IP address of the host server

FTPS (SSL/TLS) PROTOCOL
FTPS protocol use TLSv1 (Transport Layer Security Protocol) normalised by IETF and based from SSLv3 (Secure Socket Layer) developed at origin by Netscape.
TLSv1 is a transport protocol designed for security of exchanges with mandatory server authentification, eventual authentification of client and session encryption.
XcMon is complient with TLSv1 normalised in RFC-2246 and RFC-2228 (Security Extension to FTP) defined in draft Murray.

XcMon use the OpenSSL 9.7 library in order to provide the following functions :

Strong authentification using X509 v3 certificat :
- Server authentification by the XcMon client
- Eventual XcMon client authentification by server when requested by the server.
Encryption of exchanges :
- XcMon may support asymetric algorithm(RSA, DH) and symetric algorithm (AES, DES, 3DES, IDEA, RC2, RC4).

FTP LOGIN/PASSWORD
The FTP Login/password configuration has been modified and must be done using one or several Symbolic User. A FTP Login/password is associated with a recipient either using the default Symbolic User name defined in the monitor properties or either using the Symbolic User name defined in the recipient properties.

THE XCMON CLIENT XCLFT :
XcLft is a FTP client program specially dedicated for file transfers between systems that don’t possess a XcMon monitor and a remote server using a XcMon monitor.
The XCLFT Client is designed for the companies using XcMon to secure the file transfers and that wish to secure the file transfers with external companies but cannot force them to install the XcMon solution. The XcLft client run in batch command on several operating systems (Windows, Unix, Linux, Netware, IBM OS400, IBM OS390). It is composed of a sample executable program that can be simply installed and don’t require any configuration.
The XcLft client is an option of the XcMon offer and can be free delivered to remote users by the owner of a XcMon licence, without obligation for the remote users to buy a usage licence.

USER ACKNOWLEDGMENT OF RECEIVED MESSAGE
It is now possible to activate a user acknowlegment in the message queue configuration. This allow to serialize the user procedure associated with a message queue. The user procédure is executed in sequence one at the time for each received message when the previous procedure is terminated.

XCCNF - CONFIGURATION GENERATOT :
XcCnf is a Windows program that allows to generate a sample XcMon configuration with only required parameters for initial start of a XcMon monitor.
The generated configuration file may be used as is or updated according to user need.

SUPPORT OF LINUX FOR Z/Os :
a Linux version of XcMon is now available for IBM Z/Os Linux partition.

SUPPORT OF NOVELL NETWARE SYSTEMS :
XcMon had been adapted in order to be run on NOVELL NETWARE systems from release 5.1.
As for others OS supported, the full functions of XcMon are available on this kind of system.

VIRTUAL DIRECTORIES :
Management of Virtual Directories had been updated to be compatible with all Windows systems.

SUPPORT OF DBCS FOR EBCDIC SYSTEMS (OS/390)
XcMon supports file transfers containing DBCS characters (Double Byte Character Set).
This data type is used notably in Asian countries and specific conversion tables must be used.

RELATIVE SCHEDULE
By specifying a time limit, in seconds in relation to the moment of submission (file transfer).
This function is particularly interesting if it used in association with file groups. The same transfer command can be re-launched in an end of group procedure with a relative schedule, which allows directory scans to be run cyclically.

OPERATOR ADDRESS (XcWop)
To connect to the XcMon monitor, the IP address or the DNS name of the XcWop operator must be identical to the one defined in the monitor’s configuration.
This value is optional and allows a static IP address to be forced for the operator.

SHARING THE DATABASE
To prevent several users from modifying the operator station’s database simultaneously, the first operator to connect to XcWop has update permissions (write) to the database until (s)he disconnects or switches to read-only mode.

WINOPER
The supervisor WinOper has been renamed XcWop.

MONITOR COMMUNITIES
The community concept is used to group several XcMon monitors together.
This function is used to facilitate the task of running queries on the catalogs and history files of not only one monitor, but all monitors defined in the community.

RE-LAUNCHING FILE TRANSFERS
In XcWop, it is now possible to re-launch terminated transfers from the results list.
Information on the current or terminated transfers.

DISPLAY OF CONTEXT-SENSITIVE INFORMATION BUBBLES
In XcWop, when you move the mouse pointer over a transfer in the results list, information on the transfer is displayed (in an information bubble).

FILE GROUPS
XcMon offers the possibility to transfer all or part of a directory (or folder, or catalog, etc.).
A transfer is carried out for each file present in the directory.
All transfers inherit the parameters of the query (e.g. an end of transfer procedure applies to each file transfer).
XcMon variables can be used to build the names of remote files.
A procedure can be activated when all the files from a group have been transferred.
Scanning of the directory can be carried out using wildcards and masks (xxx*, *xxx, *).

RENAMING FILES
Renaming is defined directly in the transfer query and is applied after the positive termination (normal end) of a transfer.
Local and / or remote files can be renamed in SEND mode and RECEIVE mode.
In SEND mode, renaming a remote file can have its advantages as it prevents the file in transfer from being used by an external application.
Renaming can also be applied to file groups.

SYMBOLIC PROCEDURES
To automate procedures before / after transfers.
Symbolic procedures are used by file transfer queries. For each file transfer, a symbolic procedure can be defined for positive or negative transfer termination
A symbolic procedure can represent a command file (.exe, script, JCL etc.) or a XcMon command (FT or SM) activated directly on end of transfer.
XcMon variables can be used in the definition of symbolic procedures.

RECIPIENTS LISTS
Automatic management of recipients lists for the transfer of the same files to groups of recipients in a single command.

AUTOMATIC BACKUP
Automatic management of backup addresses for all XcMon monitors (initiator and recipients). With this function, if there is a system or network failure (or simply if the monitor is being used on a backup site), recipients can be reached using a secondary address without any modification of the setup file necessary.

TAG PARAMETER
A new “TAG” parameter in the transfer command (files and messages) allows the user to give an identity (tag) to the transfer (e.g. the name of an application or any other chain of characters – 12 characters max.). This TAG can be used to group transfers under the same identity in order to facilitate their selection in the catalog or history files. It can also be used as a variable when configuring symbolic files (names of files or processes launched on end of transfer).

CONVERSION TABLES
Allows the possibility to assign conversion tables (ASCII/EBCDIC) on IBM OS/390 and OS/400 for each transfer command (overriding the default tables for each transfer).

CONNECTION PERMANENCE
The connection permanence with recipients can be configured : Previous releases imposed a permanent connection with recipients. It is now possible to define a connection type i.e. permanent or temporary. A temporary connection is used to connect only when data exchange is necessary.

XCMESSENGER FUNCTION
XcMessenger is a specific module associated to a XcMon monitor running under Windows. XcMessenger allows the centralization and display in a specific window of : All or part of the message exchanges between different XcMon monitors and warning messages detected by one or several XcMon monitors (extracts from the log files).

DELETING SOURCE FILE
When a transfer query is being created, the user can request that the source file be deleted after transfer.

SUPPRESSION OF LIMITS USING DYNAMIC MEMORY
Previous releases imposed a limit on certain configurable items, notably on the number of recipients, the number of symbolic files, the number of message queues etc.
Dynamic management of the memory now allows these limited to be suppressed.

JES2 INTERFACE
The file transfer command (FT) allows the possibility to communicate with the JES2 job manager on IBM OS/390 systems.
This function can be used to send and activate a JCL as well as for spool retrieval on a OS/390 system. This can be performed from a XcMon monitor installed on any other system.
These functions can be automated and allow, for example, a developer to submit a compilation and to consult the sysout of this compilation on a Windows station without having to connect directly to the OS/390 system.

DATA COMPRESSION
Data compression allows a significant reduction of the volume of data transferred. The compression technique used by XcMon is equivalent to ZIP compression (compression by dictionary).

DATA ENCRYPTION
Data encryption ensures a high level of confidentiality. XcMon has an integrated PKI system (Public Key Infrastructure), allowing each monitor to possess a public key and private key (RSA type). Data encryption is carried out using a symmetric key generated for each transfer (128, 192 or 256 bits according to configuration). The symmetric key is itself encrypted using the public key of the recipient. Only the recipient, using its private key, can decrypt the symmetric key in order to decrypt the data.

REMOTE NETWORK ACCESS
Follow-up of incoming transfers during a period of disconnection (for temporary connections).

SIZE LIMITATION OF INCOMING FILES
Limitation of incoming file size (Windows and Unix only) : A limit can be defined in Kb. The reception of a file whose size exceeds the fixed limit is refused or deferred depending on the parameters defined in the setup file (keyword FSL). The limit and the disposition (refuse or defer) are dynamically modifiable for the current session using an administration command.

MULTI PARALLEL TRANSFERS
Management of multi parallel transfers for each recipient.

MESSAGE QUEUES
Message queues can be User type or Administrator type. The message body received in an Administrator message queue is analyzed. If the message contains an XcMon administration command, this command is run on the receiving system. The use of message queues (User or Administrator) requires authorization which can be defined for one or several recipients. A message that is bound for a message queue for which the initiator (recipient) has no authorization is refused.

FTP RETRY PROCESS
The use of a FTP retry process allows a transfer to be resumed from the point it left off after a problem was encountered. This function is defined for each recipient and is negotiated with the remote FTP server. This function applies only to binary transfers and must be used carefully as some FTP servers cannot manage this process correctly.

CONFIGURATION OF XCMON PORT NUMBER
Allows the possibility to configure the port number of the FTP server to be used (if other than 21).

"REMOTEFILE" VARIABLE
The “Remotefile” variable can be built by the initiator.

SUPPRESSION OF TRAILING BLANKS
Trailing blanks can be deleted on IBM OS/390 and IBM OS/400.

REMOTE NETWORK ACCESS
Integrated RAS management for XcMon monitors in Windows (mobile or isolated stations).

UFAS FILE ACCESS
UFAS file access for the FTP clients of XcMon monitors running on BULL GCOS8 systems.

OPTIMIZATION OF PASSWORD ENCRYPTION
Optimized management of the encryption of 12-character passwords.

ASCII/EBCDIC CONVERSION TABLES
Management of ASCII/EBCDIC character set conversion tables for IBM OS/390 and IBM OS/400.