Installing and Upgrading

Install or upgrade the software and perform initial configuration tasks.
cxdtfa1102
This section provides an overview of the installation and configuration process for
XCOM Data Transport
for AS/400 i5/OS.
The installation and configuration consists of the following basic parts:
  • Loading the software
  • Performing transfers using TCP/IP—Configuring TCP/IP for
    XCOM Data Transport
  • Defining the
    XCOM Data Transport
    parameters
This article describes the following topics:
2
System Requirements
The installation of
XCOM Data Transport
for IBM iSeries (AS/400) requires the following software components.
Operating System
Below IBM iSeries(AS/400) Operating System versions are supported:
  • IBM iSeries (AS/400) v7.1
  • IBM iSeries (AS/400) v7.2
  • IBM iSeries (AS/400) v7.3
  • IBM iSeries (AS/400) v7.4
Hardware and Software
The installation of
XCOM Data Transport
requires no modifications to the IBM iSeries(AS/400) operating system and any additional hardware or software.
For transfers using TCP/IP,
XCOM Data Transport
for IBM iSeries(AS/400) also requires following:
  • Any version of TCP/IP supported by IBM
  • For transfers using TCP/IP with Secure Socket,
    XCOM Data Transport
    for IBM iSeries(AS/400) also requires the PASE (Portable Application Solution Environment) programs installed.
Disk Requirements
XCOM Data Transport
requires approximately 50 MB of disk space on your RISC system.
New Installation or Upgrade
New Installation
The
XCOM Data Transport
for AS/400 i5/OS installation process performs certain tasks automatically, depending on whether you are installing
XCOM Data Transport
for the first time or upgrading existing software.
If you are installing…
Then the INSTALL command starts the…
XCOM Data Transport
for the first time, or installing into a new library different
from the existing release
Installation process
XCOM Data Transport
r11 in the same library as an existing r11 release
Upgrade process
Whenever you install
XCOM Data Transport
in a new library, this is considered a new (initial) installation. The presence or absence of the library is used by the INSTALL CL program to route toward the upgrade/installation process. It is not enough for the library just to be empty to force a new installation; it has to be deleted.
If you are installing
XCOM Data Transport
for the first time, the installation process consists of the general stages that are listed below.
In the following process, the name of the program library where you are installing is XCOMR11. The default
XCOM Data Transport
program library on the CD is XCOMR11, but you can rename this library during the installation.
The general stages of the initial installation process are as follows:
  • The XCOM user profile is created. The profile is created with the INLMNU parameter set to the value *SIGNOFF.
This profile is used as the owner of the objects in the XCOMR11 library and as a default user for the communications entry in the XCOM2SBS subsystem.
The profile may require some special authorities if you are going to run XQUE. For more information, see Using Remote Spool.
  • The XCOMR11 library is created and *PUBLIC is assigned *USE authority. The XCOM user profile is made the owner of the XCOMR11 library.
The XCOMR11 library name can be user-designated.
  • The XCOM user profile is granted *USE authority to the OS/400 commands that are required to run
    XCOM Data Transport
    .
  • XCOM is restored to the XCOMR11 library.
XCOM is the owner of all objects in the XCOMR11 library except for the module that is used by the background processor that manages enqueued transfers, XCOMPCO. XCOMPCO is owned by QSECOFR.
  • XCOM sample scripts for creating TLS/SSL certificates and TLS/SSL configuration files are created if they do not exist.
XCOM copies sample scripts for creating TLS/SSL certificates to.
/QOpenSys/CAProduct/ConfigFile/CAXCOM/ssl directory and sample TLS/SSL configuration files into /QOpenSys/CAProduct/ConfigFile/CAXCOM/config directory for use with TCP/IP TLS/SSL transfers. These files are copied for all installations, even if TLS/SSL transfers will not be used.
The owner of the TLS/SSL configuration files is QSECOFR and the directory is created as a secure directory where the owner has read, write, and execute rights, whereas the group and other users have only read and execute rights. The permissions for configuration files, scripts for creating TLS/SSL certificate and directories can be changed and should be customized for your site's security level.
Existing files are not overwritten. You need to delete or rename the directory and/or the configssl.cnf file in the config directory if you want to have XCOM create a new copy of these files.
Additional objects are built, such as output queues, data areas, job queues, and job descriptions. These objects are owned by XCOM.
  • The authority that is designated by the user in the installation procedure is granted to *PUBLIC for the objects in the
    XCOM Data Transport
    program library.
  • The installation process may copy the remote system profiles and distribution profiles from another existing XCOM library into the new XCOMR11 library, as specified by the user in the installation procedure.
  • If requested during the installation procedure, the XCOMR11 library is added to the QUSRLIBL system value. This enables correct routing when your system is used as the target for transfers initiated by other systems. See List of Prompts
    for 'Add PGM Library to QUSRLIBL?'.
  • Sample line, controller, and device descriptions are created.
  • A group of mode descriptions is created. Each mode starts with the letters XCOM, and all have varying RU sizes.
  • The XCOMR11 library is added to the user's library list, and the QSYSOPR message queue is changed to *HOLD mode.
Upgrade
Perform upgrade only if
XCOM Data Transport
r11.x is installed. If the current
XCOM Data Transport
release is 3.
x
or earlier, you must follow the instructions for a new installation. Read the procedure before beginning the upgrade.
When upgrading to a new release of
XCOM Data Transport
, it is a good practice specify a new
XCOM Data Transport
program library other than the program library currently used by the older release of
XCOM Data Transport
. Once the new release has been installed and tested, you can remove the previous
XCOM Data Transport
program library.
If you are upgrading an existing version of
XCOM Data Transport
, your upgrade procedure consists of the general stages that are listed below. For step-by-step upgrade instructions, see Install
XCOM Data Transport
.
XCOMR11 is the default name for the
XCOM Data Transport
program library. You can change this name to whatever you want during the installation.
The general stages of the upgrade installation process are as follows:
  • Files to be restored are allocated to the job. The files are allocated *EXCL. Only working files are allocated. These include the configuration, distribution profile, and control files.
    XCOM Data Transport
    is shipped with source files containing samples and API modules. These files are not allocated by the installation procedure. If these files are in use, the restore may not complete successfully.
  • The configuration and distribution profile files, transmission queue, and log files are renamed. This is done to save them so that they can be copied back after the new configuration and distribution profile files are restored. If the formats of these files have changed, the information in the existing files is updated to the new format.
  • The commands, programs, files, and message files are restored. User-modified objects are not overwritten by the automatic installation process.
    If you have changed the dummy exit programs, save them before restoring the new
    XCOM Data Transport
    version. Restore them after the installation is complete. Exit programs should not be placed in the XCOMR11 library for this reason.
  • The configuration and distribution profile files, transmission queue, and log files are copied back to the active files.
  • XCOM Data Transport
    builds additional objects (if they do not already exist), such as output queues, data areas, job queues, job descriptions. These new objects are owned by the XCOM user profile.
  • The files that were allocated are deallocated.
  • If they do not already exist,
    XCOM Data Transport
    creates XCOM sample scripts for creating TLS/SSL certificates and TLS/SSL configuration files.
    XCOM copies sample scripts for creating TLS/SSL certificates to /QOpenSys/CAProduct/ConfigFile/CAXCOM/ssl directory and sample.
    Existing files are not overwritten. You must delete or rename the directory and/or the configssl.cnf file in the config directory if you want to have XCOM create a copy of these files.
  • If they do not already exist,
    XCOM Data Transport
    creates line, controller, and device descriptions for the optional use of customer support.
  • If they do not already exist,
    XCOM Data Transport
    creates a group of mode descriptions. Each mode starts with the letters XCOM, and all have varying RU sizes.
  • The XCOMR11 library is added to the user's library list, and the QSYSOPR message queue is changed to *HOLD mode.
You are ready to install
XCOM Data Transport
. See Install
XCOM Data Transport
.
XCOM Data Transport
Subsystems
XCOM Data Transport
can operate in either of two ways:
  • Within an existing AS/400 i5/OS subsystem, for example, QCMN
  • Within the XCOMR11/XCOM2SBS subsystem supplied with
    XCOM Data Transport
Installation Programs
The install programs are in the XINSTR11 library. To retrieve the source for these programs, use the RTVCLSRC command.
Libraries
XCOM Data Transport
is shipped in the following six libraries on the distribution media:
  • XINSTR11—Contains the commands and programs for installing
    XCOM Data Transport
    .
  • XCOMPASE—Contains the Secure Socket Library.
  • XCOMR11—Contains the actual product.
  • XCR11ENU—Contains the objects for displaying textual screen data in mixed-case English.
  • XCR11ENP—Contains the objects for displaying textual screen data in uppercase English.
  • XCR11JPN—Contains the objects for displaying textual screen data in Japanese.
The following savf file and directory are created during upgrade:
  • Backup of r11.x program library:
    o XCOMR11/XCOMR11BKP savf file, where XCOMR11 is your
    XCOM Data Transport
    program library. It will be based on the
    XCOM Data Transport
    program library which is being upgraded.
  • Backup of TLS/SSL objects /QOpenSys/CAProduct:
    o /QOpenSys/CAProduct_BKP
Prepare for Installation
XCOM Data Transport
for AS/400 i5/OS is distributed on CD. Before you begin the installation, you must:
  • Determine the subsystem within which you want
    XCOM Data Transport
    to operate.
  • Determine the values for the installation worksheet.
Fill the following worksheet before you start installing the product.
Installation Worksheet
Prompt
Default
Your Value
Saved library
N/A
XINSTALR11
Device
*SAVF
Language
ENU
XCOM Data Transport
program library
XCOMR11T
Copy files from library
*NONE
Add pgm library to QUSRLIBL?
Does not apply to upgrades
*NO
Authority to objects in lib?
Does not apply to upgrades
*EXCLUDE
Prepare for Upgrade
Before upgrading
XCOM Data Transport
, perform the following tasks:
  • Shut down
    XCOM Data Transport
    .
  • Terminate all XQUE writers and enqueued transfer processors.
  • If the dummy exit programs have been changed, save them before restoring the new
    XCOM Data Transport
    version. Restore them after the installation is complete.
  • If you are a target system for transfers, vary off any devices that may be used for a transfer.
  • Back up your current configuration files.
Backup of Configuration Files
Before upgrading to your new release of
XCOM Data Transport
, review the following list of files and directories.
  • XCOMR11/XCOMCNFG—The configuration file that contains the remote system profiles.
  • XCOMR11/XCOMDPRF—The distribution profile table that contains the XQUE distribution profiles.
  • Any dummy exits programs that have been customized:
    • XCOMR11/XCOMPPE—The Post Processing User exit
    • XCOMR11/XCOMRREXIT – The Receive Report User exit
    • XCOMR11/XCOMXQUEEXIT – The XQUE User exit
    XCOM Data Transport
    11.0.02 upgrade process backs up entire XCOMR11 (or your custom
    XCOM Data Transport
    r11.
    x
    program library) program library on which you want to perform upgrade. The backup is inside XCOMR11/XCR11BKP (or <custom program library>/XCR11BKP)savf file.
  • /QOpenSys/CAProduct/ConfigFile/CAXCOM
    This backup directory needs to be configured as a secure directory.
When you perform the upgrade, the installation program skips the following file and directory if they exist:
  • /QOpenSys/CAProduct/ConfigFile/CAXCOM/ config/configssl.cnf file
  • /QOpenSys/CAProduct/ConfigFile/CAXCOM/ssl directory
    XCOM Data Transport
    11.0.02 upgrade process backs up the entire /QOpenSys/CAProduct/ in /QOpenSys/CAProduct_BKP directory.
SNA or TCP/IP Transfers
After installing
XCOM Data Transport
, depending on the types of transfers you wish to perform, check the following:
1. For performing transfers using SNA, ensure that your SNA software is properly configured. See Configure the SNA Network.
2. For performing transfers using TCP/IP, ensure that your TCP/IP connectivity is properly configured. See Configure Your System for TCP/IP or TCP/IP SSL Transfers.
3. For performing transfers using TCP/IP TLS/SSL, in addition to confirming your TCP/IP is properly configured, ensure that the proper CA certificates and TLS/SSL configurations have been set. See Configure Your System for TCP/IP SSL.
To receive remotely initiated TCP/IP transfers, start and run one of the following servers:
  • The
    XCOM Data Transport
    TCP/IP IPv4 server
  • The
    XCOM Data Transport
    TCP/IP IPv4 SSL server
  • The
    XCOM Data Transport
    TCP/IP IPv6 server
  • The
    XCOM Data Transport
    TCP/IP IPv6 SSL server
To start these servers, use the following commands:
The STRXCTCP command to start the
XCOM Data Transport
TCP/IP IPv4 server The STRXCTCPS command to start the
XCOM Data Transport
TCP/IP IPv4 SSL server The STRXCTCP6 command to start the
XCOM Data Transport
TCP/IP IPv6 server The STRXCTCP6S command to start the
XCOM Data Transport
TCP/IP IPv6 SSL server
For more information about these commands, see Remote TCP_IP Transfers.
About the API (Application Programming Interface)
If you are using the APIs in
XCOM Data Transport
, be sure to note the new parameter list changes. Programs need to be recompiled to use the new r11 parameter lists. For details, see Describing API Components.