CA XCOM Data Transport for

Transcription

1 CA XCOM Data Transport for AS/400 i5/os Getting Started r11 SP01

2 This documentation (the Documentation ) and related computer software program (the Software ) (hereinafter collectively referred to as the Product ) is for the end user s informational purposes only and is subject to change or withdrawal by CA at any time. This Product may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Product is confidential and 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 the Documentation for their own internal use, and may make one copy of the Software as reasonably required for back-up and disaster recovery purposes, 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 provisions of the license for the Software are permitted to have access to such copies. The right to print copies of the Documentation and to make a copy of the Software 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 user s responsibility to certify in writing to CA that all copies and partial copies of the Product have been returned to CA or destroyed. EXCEPT AS OTHERWISE STATED IN THE APPLICABLE LICENSE AGREEMENT, TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS PRODUCT 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 PRODUCT, 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 this Product and any product referenced in the Documentation is governed by the end user s applicable license agreement. The manufacturer of this Product is CA. This Product is provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections , , and (c)(1) - (2) and DFARS Section (c)(1)(ii), as applicable, or their successors. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies. Copyright 2009 CA. All rights reserved.

3 CA Product References This document references the following CA product: CA ACF2 Security (CA ACF2 Security) CA Roscoe (CA Roscoe) CA Top Secret Security (CA Top Secret Security) CA XCOM Data Transport (CA XCOM Data Transport) Contact CA Contact Technical Support For your convenience, CA provides one site where you can access the information you need for your Home Office, Small Business, and Enterprise CA products. At you can access the following: Online and telephone contact information for technical assistance and customer services Information about user communities and forums Product and documentation downloads CA Support policies and guidelines Other helpful resources appropriate for your product Provide Feedback If you have comments or questions about CA product documentation, you can send a message to techpubs@ca.com. If you would like to provide feedback about CA product documentation, complete our short customer survey, which is also available on the CA Support website, found at

4

5 Contents Chapter 1: Welcome About CA XCOM Data Transport What Does CA XCOM Data Transport Do? How Does CA XCOM Data Transport Work? CA XCOM Data Transport Advantages Possible CA XCOM Data Transport Applications Multiple User Interfaces Unified Solution CA XCOM Data Transport Applications CA XCOM Data Transport Features Support of Most Operating Systems Data Link Types Standard Features Standard Functions High Capacity and Performance Security Management Types of Transfers Answering Remote Requests Chapter 2: Pre-Installation System and Storage Requirements Overview of the Installation Process New Installation or Upgrade? About Performing SNA or TCP/IP Transfers About the API (Application Programming Interface) Installation Process Upgrade Process What s Next? Contents v

6 Chapter 3: Installing and Upgrading CA XCOM Data Transport CA XCOM Data Transport Subsystems Installation Programs Libraries What You Need to Install or Upgrade CA XCOM Data Transport Before You Begin What s Next? The Installation Parameter s List of Prompts What s Next? Installing CA XCOM Data Transport Before You Begin What s Next? Install Procedure from CD Upgrading CA XCOM Data Transport Before You Begin Back Up Your Configuration Files What s Next? Upgrade Procedure from CD Installing or Upgrading Using Save Files What s Next? Post-Installation or Upgrade Considerations CA XCOM Data Transport Release CA XCOM Data Transport Considerations SNA Considerations TCP/IP and TCP/IP SSL Considerations CA XCOM Data Transport API Considerations Chapter 4: Configuring the SNA Network Planning Your Configuration Sharing Descriptions Network Configuration Procedures Configuration Worksheets Configuration Examples A Note About DLOGMOD Creating an LU What s Next? vi Getting Started

7 Configuring the AS/400 i5/os to a Host Node Before You Begin Task Overview Task 1 Create Line and Host Controller Descriptions Procedure Task 2 Verify That an LU is Defined on the Host Defining an LU Task 3 Create the Device Description for an AS/400 i5/os to Host Connection Device Description Fields The Mode as Part of the Device Description Task 4 Vary the Device Description On for an AS/400 i5/os to Host Connection Procedure What s Next? Configuring the AS/400 i5/os to a Non-Host Node Before You Begin Task Overview Task 1 Create the Line and APPC Controller s Procedure Task 2 Create the Device Description for an AS/400 i5/os to Non-Host Connection Procedure Task 3 Vary the Device Description On for an AS/400 i5/os to Non-Host Connection Procedure What s Next? Processing Remote Requests Specifying a Subsystem OS/400 Allocates the APPC Device to a Subsystem OS/400 Processes the Program Start Request OS/400 Establishes the Library List for the Job OS/400 Determines the Initial Program to Be Run Chapter 5: Configuring and Customizing CA XCOM Data Transport Remote System Names and Profiles What Is a Profile? How Does It Work? Multiple Profiles for One Remote System Where are the Profiles Stored? Required Profile Information Worksheets What s Next? Contents vii

8 Configuration Commands Entering Data Fields with Lowercase Characters List of Configuration Commands Changing Remote Systems WRKXCOM (Work with XCOM) Command Keyword Screen Screen Options Function Keys ADDRMTSYS (Add Remote System) Command Command Defaults Keywords CHGGFOPT (Change Get File Options) Command Command Defaults Keywords CHGRMTSYS (Change Remote System) Command Keywords CHGSFOPT (Change Send File Options) Command Command Defaults Keywords CHGSJOPT (Change Send Job Options) Command How CA-XCOM Sets Command Defaults Keywords CHGSROPT (Change Send Report Options) Command How CA XCOM Data Transport Sets Command Defaults Keywords DLTRMTSYS (Delete Remote System) Command Keyword DSPRMTSYS (Display Remote System) Command Keyword Defining a Remote System Profile Before You Begin Procedure What s Next? Modifying a Remote System Profile Before You Begin Procedure What s Next? Establishing Authorization to Use CA XCOM Data Transport Requirements What s Next? viii Getting Started

9 Chapter 6: Using CA XCOM Data Transport with TCP/IP Configuring Your System for TCP/IP or TCP/IP SSL Transfers What You Need for TCP/IP Data Encryption Using Secure Socket Layer (SSL) Configuring Your System for TCP/IP SSL About Remotely Initiated TCP/IP Transfers TCP/IP Server Commands TCP/IP SSL Server Commands Using TCP/IP Protocols or TCP/IP SSL Protocols TCP/IP Keywords Specifying the TCP/IP Remote Host TCP/IP Name Resolution Chapter 7: Generating SSL Certificates Using SSL Mode Task 1 Set the Expiration for the CA Certificate Task 2 Create the CA Certificate Task 3 Create the Server Certificate Task 4 Create the Client Certificate Task 5 Configure the CA XCOM Data Transport SSL Server Task 6 Configure the CA XCOM Data Transport Client Encryption Using XCOMOSSL Syntax How to Use XCOMOSSL Appendix A: Installation, Configuration, and Customization Worksheets... A 1 What s Next?... A 1 Installing CA XCOM Data Transport... A 2 Worksheet... A 2 Configuring CA XCOM Data Transport for TCP/IP or TCP/IP SSL... A 2 TCP/IP Worksheet... A 2 TCP/IP Socket Worksheet... A 3 Configuring to a Host Node... A 4 Worksheet... A 4 Configuring to a Non-Host Node... A 6 Worksheet... A 6 Contents ix

10 Adding a Remote System... A 8 Worksheet... A 8 Changing Get File Options... A 11 Worksheet... A 11 Changing a Remote System Profile... A 13 Worksheet... A 13 Changing Send File Options... A 16 Worksheet... A 16 Changing Send Job Options... A 18 Worksheet... A 18 Changing Send Report Options... A 19 Worksheet... A 19 Index x Getting Started

11 Chapter 1: Welcome This chapter introduces CA XCOM Data Transport for AS/400 i5/os. Read this chapter before installing or configuring CA XCOM Data Transport. About CA XCOM Data Transport CA XCOM Data Transport is a family of software products that operates under SNA using LU 6.2, or under TCP/IP, to provide high-speed data transfer between supported systems such as mainframes, minicomputers, PCs, servers, and workstations. Users can send files from their local system to remote systems across an SNA network or using TCP/IP, and retrieve files from those remote systems. The same transfer capabilities are available to the local and remote systems. What Does CA XCOM Data Transport Do? CA XCOM Data Transport allows data centers in various locations worldwide to interact with each other for the purposes of sharing data and automating data and report distribution. The following applications are a few examples of how CA XCOM Data Transport can be used to interact with other computers and workstations company-wide and worldwide: Sharing data Automating data and report distribution Providing unattended back-up to dissimilar computers Controlling and auditing network activities Maintaining network security Communicating with POS (Point-of-Sale) terminals Distributing price information from a main data center to departmental stores Distributing application software to remote computers Providing distributed processing with the sendjob function Welcome 1 1

12 Chapter 1: Welcome The applications listed above are only a few examples. Under most CA XCOM Data Transport allows file sharing between any two computers or workstations within your company. How Does CA XCOM Data Transport Work? The following process occurs when a file transfer from a local system to a remote (partner) system takes place: The user starts the menu (the menu interface) or API (application programming interface) to initiate the transfer. CA XCOM Data Transport verifies the information contained in the request. For example: When requesting a send file transfer, CA XCOM Data Transport checks whether the local file exists on the local system. When requesting a receive file transfer, CA XCOM Data Transport checks whether the file exists on the remote system. If the information is confirmed, CA XCOM Data Transport attempts to transfer the file. The transfer is in progress. The transfer completes. CA XCOM Data Transport logs the details of the transfer in a log. Note: While the previous example illustrates a general idea of how CA XCOM Data Transport works, please be aware that it is simplified. Much more takes place during the file transfer than is included in the example. A more detailed explanation is available in the CA XCOM Data Transport for AS/400 i5/os User Guide. CA XCOM Data Transport Advantages CA XCOM Data Transport is a widely used, proven vehicle for moving data between a growing number of dissimilar systems. CA XCOM Data Transport provides security, recovery, scheduling, and administrative facilities. By using CA XCOM Data Transport, our customers realize the following advantages: Effectively utilize the existing investment in data processing hardware. Reduce costs by replacing multiple information transfer products with a single, easy-to-use package. 1 2 Getting Started

13 Chapter 1: Welcome Reduce operations and end-user staff training costs by implementing a centrally-controlled, highly automated data transfer solution. Provide an environment that supports the development of strategic new applications. Increase the flexibility and accessibility of remote computers, allowing your organization to respond quickly and accurately to changing business needs. Possible CA XCOM Data Transport Applications CA XCOM Data Transport allows data centers in various locations worldwide to interact with each other for the following purposes: Sharing data Automating data and report distribution Providing unattended back-up to dissimilar computers Controlling and auditing network activities Maintaining network security Communicating with Point-of-Sale (POS) terminals The applications listed above are only a few examples. Under most conditions, CA XCOM Data Transport allows file sharing between any two computers. Multiple User Interfaces Any computer using CA XCOM Data Transport can communicate with any other machine using CA XCOM Data Transport. Transfers can be invoked through the following methods: Menu interface Batch/command line interface Application Programming Interface (API) Unified Solution CA XCOM Data Transport is a unified solution. It supports communications over more operating systems than any other software product on the market today. CA XCOM Data Transport also has a solid technology base. By using LU 6.2 or TCP/IP communications protocols, CA XCOM Data Transport uses stateof-the-art technology, protecting your company s investment for years to come. Welcome 1 3

14 Chapter 1: Welcome CA XCOM Data Transport Applications The key to considerable flexibility of CA XCOM Data Transport is its ability to transfer the following: Files Jobs Reports When these functions are combined, a wide variety of applications are possible. File Transfer CA XCOM Data Transport supports high-speed file transfers between all supported operating systems. In some environments, you can start thousands of transfers resulting in hundreds of simultaneous transfers, all with a single operation. Parallel sessions are possible in varying degrees throughout the product line. You can totally automate CA XCOM Data Transport transfers. On a PC, you can be actively engaged in the use of other applications (for example, word processing) while receiving or transmitting files in the background. Comprehensive management tools allow for effective central-site control of CA XCOM Data Transport activity, including advanced problem determination features. CA XCOM Data Transport supports transfers between any two computers in an SNA network or a TCP/IP network with one of the following methods: By using the z/os, z/vm, or z/vse mainframes for store-and-forward Through Independent Logical Unit (ILU) support over the SNA (Systems Network Architecture) backbone Through use of the TCP/IP network (except for z/vm and Stratus) Type 2.1 Support CA XCOM Data Transport supports node Type 2.1 connections to allow the direct interchange of files between Windows, AS/400s, NetWare workstations, and others. Support for Independent Logical Units (ILUs) allows CA XCOM Data Transport to deliver data in Advanced Peer to Peer Networking (APPN) and Low Entry Networking (LEN) networks. This means that PCs and minicomputers attached to the same SNA or APPN network can exchange data even if they are not directly connected. 1 4 Getting Started

15 Chapter 1: Welcome TCP/IP Support CA XCOM Data Transport provides support for performing transfers using TCP/IP between CA XCOM Data Transport platforms that support TCP/IP and that are running r3.0, r3.1, or r11. TCP/IP support is provided between the following platforms: AS/400 i5/os Linux S/390 Linux x86 NetWare Open VMS Alpha Tandem z/vse Windows family) z/os Most common UNIX platforms You can use the Secure Socket Layer (SSL) to perform secure TCP/IP transfers between platforms running CA XCOM Data Transport r11 and above that support secure TCP/IP. A secure TCP/IP transfer allows for the encryption of the transmitted data. It also adds a digital signature to the encryption of the transmitted data. CA XCOM Data Transport uses OpenSSL to implement a secure TCP/IP transfer. Secure TCP/IP support is provided between the following platforms: AS/400 i5/os Linux S/390 Linux x86 Windows family z/os Most common UNIX platforms Report Distribution CA XCOM Data Transport allows z/os, z/vm, z/vse, AS/400 i5/os, and OpenVMS Alpha users to take print output from any supported system and automatically transfer it to another system for printing. The application programs producing the reports do not require any modification to support CA XCOM Data Transport report distribution, and no operator intervention is required at either end. Welcome 1 5

16 Chapter 1: Welcome RJE/NJE Replacement Current Remote Job Entry (RJE) systems contain inherent limitations. Remote computers can submit work to the host for processing and receive print data, but the host cannot distribute processing tasks to idle processors residing on the network. A further concern for data processing managers is the requirement that users are familiar with Job Entry Subsystem (JES) commands to operate the system. CA XCOM Data Transport avoids these limitations by taking advantage of the LU 6.2 and TCP/IP protocols, providing a peer-to-peer relationship between all supported systems. Any CA XCOM Data Transport system is able to send and receive batch jobs and print data from any other CA XCOM Data Transport system without formatting constraints. For example, an AS/400 i5/os user can do the following: Automatically retrieve files from a number of attached PCs. Process the data. Generate a report. Send one copy of the report back to the source PC for printing. Send another to the z/os mainframe for printing on a high-speed printer. You can easily implement CA XCOM Data Transport without any changes to your existing application programs. Data is transferred with greater integrity and higher efficiency. CA XCOM Data Transport Features CA XCOM Data Transport provides peer-to-peer communications using LU 6.2 or TCP/IP over a wider range of systems than any other product. All of the major features of CA XCOM Data Transport are supported across the product line. 1 6 Getting Started

17 Chapter 1: Welcome Support of Most Operating Systems By supporting the LU 6.2 and TCP/IP protocols, CA XCOM Data Transport can transfer data between a diversity of platforms. CA XCOM Data Transport is now available on the following systems: DG/UX Linux S/390 Digital UNIX Linux X86 IBM z/os MS Windows 2000 IBM z/vm MS Windows 2003 IBM z/vse MS Windows XP IBM iseries/400 NCR 3000 (AT&T) IBM AIX Novell NetWare Stratus VOS OpenVMS Alpha HP NonStop SCO OpenServer HP OpenVMS SCO UnixWare HP TRU64 UNIX Siemens/Nixdorf SINIX HP-UX Sun Solaris Data Link Types CA XCOM Data Transport supports the following data link types: SDLC X.25 Local Area Network (such as Token Ring and Ethernet) All SNA data links, including channel-based links TCP/IP Standard Features The following features are standard to CA XCOM Data Transport: Simple installation You can install CA XCOM Data Transport without hardware changes to your system. Initiation by either computer (any-to-any) Either computer can send and retrieve data files. Welcome 1 7

18 Chapter 1: Welcome Low maintenance There are no hooks or patches into the operating system. Choice of interfaces You can choose from batch/command line, programming (on supported platforms), and menu interfaces. Standard Functions The following functions are offered over most of the CA XCOM Data Transport platforms: Compression CA XCOM Data Transport compresses repeating characters prior to transmission. In certain cases, throughput is significantly higher than the actual line speed. Packing CA XCOM Data Transport can pack records into fixed-size data transfer blocks as large as 31K, significantly improving performance and throughput. ASCII/EBCDIC translation CA XCOM Data Transport can translate data between ASCII and EBCDIC formats as needed. Translations occur on the ASCII-based platform. Checkpoint/Restart All components of CA XCOM Data Transport support checkpoint/restart. Transfers that are stopped or fail prior to completion automatically resume, continuing from the last checkpoint. Store-and-forward Users communicating through a common z/os, z/vm, or z/vse hub can perform data transfers even if the remote (target) machine is not communicating or turned on at the time of the initial transfer. CA XCOM Data Transport ensures that the data is sent as soon as the device is available. Remote spooling CA XCOM Data Transport allows z/os, z/vm, z/vse, AS/400 i5/os, and Open VMS Alpha users the following reporting options: CA XCOM Data Transport on all platforms can receive reports. CA XCOM Data Transport on all platforms can send a file to a remote CA XCOM Data Transport partner, requesting that it be treated as a report. Some CA XCOM Data Transport platforms can also take reports off the system spool and forward them to another CA XCOM Data Transport platform without operator action. This automatic report transfer facility is called Process SYSOUT on z/os and z/vse, and it is called XQUE on AS/400 i5/os and Open VMS Alpha. z/vm does not allow automatic processing of spooled files. However, spooled files on z/vm can be manually received and redirected. 1 8 Getting Started

19 Chapter 1: Welcome High Capacity and Performance CA XCOM Data Transport is optimized for high-speed bulk data transfer. For instance, CA XCOM Data Transport for z/os can allow hundreds of simultaneous file transfers from a single machine, depending upon your hardware and software configuration. Comparatively, CICS-based products limit the user to a maximum of 34 simultaneous transfers, and many other VTAM file transfer products are faced with similar limitations. Security CA XCOM Data Transport interfaces with the native security facility on all supported systems. When security is invoked, you are required to provide a valid user ID and password for the remote system. For example, in the z/os environment, an interface is also provided to IBM RACF, etrust CA-ACF2 Security, and etrust CA-Top Secret Security. Unlike most other communication facilities, CA XCOM Data Transport encrypts passwords. This ensures that communications line tapping does not breach security. CA XCOM Data Transport also has special security capabilities that can help data centers handle their individual needs. For example, the security features of CA XCOM Data Transport allow installer specification of what can or cannot run under the privileges of someone other than the person requesting the transmission. These security features can also force user IDs from both remote computers to be the same or different. For otherwise unsatisfied security needs, CA XCOM Data Transport supplies a variety of user exits, which enable user-written security packages to be fully integrated. CA XCOM Data Transport r11 can also use the Secure Socket Layer (SSL) to perform data transfers under TCP/IP. CA XCOM Data Transport provides certificate authentication, data encryption, and data integrity checking. All data transfers using SSL are secure. Management An important feature for any enterprise-wide information product is the ability to effectively control and manage the distribution of files and work throughout the network. CA XCOM Data Transport systems maintain a comprehensive log of all transfer activity. Utilities are provided to allow the system administrator to view the log online and modify the status of pending or currently active transfers. Welcome 1 9

20 Chapter 1: Welcome Details of any transfer errors are also maintained in the log, allowing rapid problem determination and resolution. In addition, messages signaling the completion of any CA XCOM Data Transport event can be directed to a user in the network. Types of Transfers CA XCOM Data Transport performs the following transfers: Sending files With CA XCOM Data Transport, a computer can send a data file to be stored on the remote system in a specified remote file. Sending reports CA XCOM Data Transport can send a report to be printed on a remote system. Sending batch jobs for execution CA XCOM Data Transport can send a job to be executed on a remote system. Retrieving files When a computer starts the transmission request, it can also retrieve a file from a remote computer and store it in a specified local remote file. Answering Remote Requests CA XCOM Data Transport monitors the network for incoming requests. Upon detecting one, CA XCOM Data Transport determines whether it is a request to send a file inbound (from the remote system to this machine) or outbound (from this machine to another system). Files The remote system can send or retrieve files. When a remote system requests CA XCOM Data Transport to send it a file, CA XCOM Data Transport tries to allocate and open the file. CA XCOM Data Transport then reads the data records and transfers them to the remote system. Jobs The remote system can use CA XCOM Data Transport to submit jobs to the local system Getting Started

21 Chapter 1: Welcome Reports The remote system can send the local system a report. CA XCOM Data Transport writes the report to an output spool file. Each supported system has unique spooling capabilities and CA XCOM Data Transport has been designed to provide a high degree of print redirection and manipulation. Welcome 1 11

22

23 Chapter 2: Pre-Installation This chapter provides an overview of the requirements and procedures for installing, upgrading, and configuring CA XCOM Data Transport. When you have reviewed the sections in this chapter, you can begin to install CA XCOM Data Transport. Follow the instructions in the chapter Installing and Upgrading CA XCOM Data Transport. System and Storage Requirements CA XCOM Data Transport for AS/400 i5/os is distributed on CD. For the latest information about system and storage requirements, see the Readme file on the product CD. Overview of the Installation Process This section provides an overview of the installation and configuration process for CA XCOM Data Transport for AS/400 i5/os. The installation and configuration of CA XCOM Data Transport consists of the following basic parts: Loading the software (see the chapter "Installing and Upgrading CA XCOM Data Transport") For performing transfers using SNA Configuring the SNA network (see the chapter "Configuring the SNA Network") For performing transfers using TCP/IP Configuring TCP/IP for CA XCOM Data Transport (see the chapter "Using CA XCOM with TCP/IP") Defining the CA XCOM Data Transport parameters (see the chapter "Configuring and Customizing CA XCOM Data Transport") Pre-Installation 2 1

24 Chapter 2: Pre-Installation New Installation or Upgrade? The CA XCOM Data Transport for AS/400 i5/os installation process performs certain tasks automatically, depending on whether you are installing CA XCOM Data Transport for the first time or upgrading existing software. If you are installing CA XCOM Data Transport for the first time, or installing into a new library different from the existing release CA XCOM Data Transport r11 in the same library as an existing r11 release Then the INSTALL command starts the Installation process Upgrade process Note: Whenever you install CA 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. About Performing SNA or TCP/IP Transfers After installing CA 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 the chapter "Configuring the SNA Network." 2. For performing transfers using TCP/IP, ensure that your TCP/IP connectivity is properly configured. See the chapter "Using CA XCOM with TCP/IP." 3. For performing transfers using TCP/IP SSL, in addition to confirming your TCP/IP is properly configured, ensure the proper CA certificates and SSL configurations have been set. See the chapter "Generation SSL Certificates." Note: In order to receive remotely initiated TCP/IP transfers, one of the following servers must be started and running: The CA XCOM Data Transport TCP/IP IPv4 server The CA XCOM Data Transport TCP/IP IPv4 SSL server The CA XCOM Data Transport TCP/IP IPv6 server The CA XCOM Data Transport TCP/IP IPv6 SSL server 2 2 Getting Started

25 Chapter 2: Pre-Installation To start these servers, use the following commands: The STRXCTCP command to start the CA XCOM Data Transport TCP/IP IPv4 server The STRXCTCPS command to start the CA XCOM Data Transport TCP/IP IPv4 SSL server The STRXCTCP6 command to start the CA XCOM Data Transport TCP/IP IPv6 server The STRXCTCP6S command to start the CA XCOM Data Transport TCP/IP IPv6 SSL server For more information about these commands, see the chapter Processing Options in the CA XCOM Data Transport for AS/400 i5/os User Guide. About the API (Application Programming Interface) If you are using the APIs in CA 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 more information, see the chapter The Application Programming Interface in the CA XCOM Data Transport for AS/400 i5/os User Guide. Installation Process If you are installing CA XCOM Data Transport for the first time, the installation process consists of the general stages listed below. For step-by-step installation instructions, see the chapter Installing and Upgrading CA XCOM Data Transport. Note: In the following process, the name of the program library where you are installing is XCOMR11. The default CA XCOM Data Transport program library on the CD is XCOMR11, but you can rename this library during the install. 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. Pre-Installation 2 3

26 Chapter 2: Pre-Installation The profile may require some special authorities if you are going to run XQUE. For more information, see Required Authorization for XQUE in the chapter The Remote Spooling Feature (XQUE) and Checking for Remotely Initiated Transfers in the chapter Security in the CA XCOM Data Transport for AS/400 i5/os User Guide. The XCOMR11 library is created and *PUBLIC is assigned *USE authority. The XCOM user profile is made the owner of the XCOMR11 library. Note: The XCOMR11 library name can be user-designated. The XCOM user profile is granted *USE authority to the OS/400 commands required to run CA 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 used by the background processor that manages enqueued transfers, XCOMPCO. XCOMPCO is owned by QSECOFR. XCOM sample scripts for creating SSL certificates and SSL configuration files are created if they do not exist. XCOM copies sample scripts for creating SSL certificates to /QOpenSys/CAProduct/ConfigFile/CAXCOM/ssl directory and sample SSL configuration files into /QOpenSys/CAProduct/ConfigFile/CAXCOM/config directory for use with TCP/IP SSL transfers. These files are copied for all installations, even if SSL transfers will not be used. The owner of the 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 SSL certificate and directories can be changed and should be customized for your site s security level. Note: Existing files are not overwritten. You need to delete or rename the ssl 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 designated by the user in the installation procedure is granted to *PUBLIC for the objects in the CA 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 (see Add pgm library to QUSRLIBL? in List of Prompts in the chapter Installing and Upgrading CA XCOM Data Transport ). This enables correct routing when your system is used as the target for transfers initiated by other systems. 2 4 Getting Started

27 Chapter 2: Pre-Installation For more information about processing remote requests using SNA, see the chapter Configuring the SNA Network. 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. For more information about modes, see SNA Request/Response Units in the chapter Processing Options in the CA XCOM Data Transport for AS/400 i5/os User Guide. The XCOMR11 library is added to the user s library list, and the QSYSOPR message queue is changed to *HOLD mode. Upgrade Process If you are upgrading an existing version of CA XCOM Data Transport, your upgrade procedure consists of the general stages listed below. For step-by-step upgrade instructions, see the chapter Installing and Upgrading CA XCOM Data Transport. Note: XCOMR11 is the default name for the CA XCOM Data Transport program library. You can change this name to whatever you want during the install. 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. CA 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 CA XCOM Data Transport version. Restore them after the installation is complete. Exit programs should not be placed in the XCOMR11 library for this reason. Pre-Installation 2 5

28 Chapter 2: Pre-Installation The configuration and distribution profile files, transmission queue, and log files are copied back to the active files. CA XCOM Data Transport builds additional objects (if they do not already exist), such as output queues, data areas, job queues, job descriptions, and so forth. These new objects are owned by the XCOM user profile. The files that were allocated are deallocated. If they do not already exist, CA XCOM Data Transport creates XCOM sample scripts for creating SSL certificates and SSL configuration files. XCOM copies sample scripts for creating SSL certificates to /QOpenSys/CAProduct/ConfigFile/CAXCOM/ssl directory and sample SSL configuration files into /QOpenSys/CAProduct/ConfigFile/CAXCOM/config directory for use with TCP/IP SSL transfers. These files are copied for all installations, even if SSL transfers will not be used. Note: Existing files are not overwritten. You need to delete or rename the ssl directory and/or the configssl.cnf file in the config directory if you want to have XCOM create a new copy of these files. If they do not already exist, CA XCOM Data Transport creates line, controller, and device descriptions for the optional use of customer support. If they do not already exist, CA XCOM Data Transport creates a group of mode descriptions. Each mode starts with the letters XCOM, and all have varying RU sizes. For more information about modes, see SNA Request/Response Units in the chapter Processing Options in the CA XCOM Data Transport for AS/400 i5/os User Guide. The XCOMR11 library is added to the user s library list, and the QSYSOPR message queue is changed to *HOLD mode. What s Next? You are ready to install CA XCOM Data Transport. Go to the chapter Installing and Upgrading CA XCOM Data Transport. 2 6 Getting Started

29 Chapter 3: Installing and Upgrading CA XCOM Data Transport This chapter describes the procedures for installing and upgrading CA XCOM Data Transport. CA XCOM Data Transport Subsystems CA 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 CA XCOM Data Transport Installation Programs The install programs are in the XINSTR11 library. To retrieve the source for these programs, use the RTVCLSRC command. Two versions of XINSTR11 exist on the installation CD. The version in the root directory is used when installing directly from the installation CD. An alternate version in the SAVEFILE directory is used for the alternative installation method, which allows the installation to be done from save files. This alternative method allows an installation to be done remotely. For more information, see Installing or Upgrading Using Save Files in this chapter. Libraries CA XCOM Data Transport is shipped in the following five libraries on the distribution media: XINSTR11 Contains the commands and programs for installing CA XCOM Data Transport. XCOMPASE Contains the Secure Socket Library. Installing and Upgrading CA XCOM Data Transport 3 1

30 Chapter 3: Installing and Upgrading CA XCOM Data Transport 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. Note: An additional library, XCOMPTFS, may or may not be provided. What You Need to Install or Upgrade CA XCOM Data Transport To load the CA XCOM Data Transport software, you must be able to do the following: Sign on as the security officer on your AS/400 i5/os. Use the CD and Command Entry screen. You should be familiar with your installation s production processing activity and security procedures. Before You Begin Before you begin the installation, you must do the following: Review the chapter Pre-Installation. Determine the subsystem within which you want CA XCOM Data Transport to operate. Determine the values for the installation worksheet in the appendix Installation, Configuration, and Customization Worksheets. Determine whether the installation will be done directly from the installation CD, or by the alternate installation method using save files. 3 2 Getting Started

31 Chapter 3: Installing and Upgrading CA XCOM Data Transport What s Next? To find the information necessary to complete your installation, see the Installing CA XCOM Data Transport worksheet in the appendix Installation, Configuration, and Customization Worksheets. The Installation Parameter s This section describes the prompts you respond to when you install or upgrade CA XCOM Data Transport on your system, and supplies valid entries for your responses. For a worksheet designed to assist you in installing CA XCOM Data Transport, see the appendix Installation, Configuration, and Customization Worksheets. Photocopy the quantity you need and mark your copies with the values for your system. List of Prompts The following table describes the prompt information needed to install or upgrade CA XCOM Data Transport. Prompt Saved library Description Required Specifies the name of the saved library on the installation media. Valid entries: Up to 10 characters Default value: XINSTR11 Language Specifies the language for the textual data on the screens. Valid entries: ENU United States English ENP Uppercase English JPN Japanese Default value: ENU Installing and Upgrading CA XCOM Data Transport 3 3

32 Chapter 3: Installing and Upgrading CA XCOM Data Transport Prompt CA-XCOM program library Description Specifies the name of the program library for CA XCOM Data Transport. Valid entries: Up to 10 characters Default value: XCOMR11 Device Required Specifies the name of the device from which the CA XCOM Data Transport files are restored. Enter OPT01 for CD or *SAVF if installing from save files. Valid entries: Up to 10 characters Default value: OPT01 Product save file Applies to save file installs only. Specifies the Product save file name created for a save file install. Valid entries: XCOMR11 Default value: XCOMPROD Language save file Applies to save file installs only. Specifies the Language save file name created for a save file install. Valid entries: XCR11ENU, XCR11ENP, XCR11JPN Default value: XCR11ENU PTF save file Applies to save file installs only. Specifies the PTF save file name created for a save file install. Note: PTF save file is reserved for future use. Valid entries: *NONE Default value: *NONE Library Applies to save file installs only. Specifies the library where the save files copied or transferred by FTP from the installation CD were created. Valid entries: Any valid AS/400 i5/os library name up to 10 characters Default value: XCOMR11I 3 4 Getting Started

33 Chapter 3: Installing and Upgrading CA XCOM Data Transport Prompt Copy files from library Description Does not apply to upgrades. Specifies the library from which the configuration files for CA XCOM Data Transport are copied. Valid entries: *NONE or a valid existing XCOM library name up to 10 characters Default value: *NONE. Add pgm library to QUSRLIBL? Does not apply to upgrades. Specifies whether the XCOM program library will be added to the user portion of the library list. If you are using the XCOM2SBS subsystem, you don t have to add this library. For more information, see the chapter Configuring the SNA Network. This parameter pertains to remotely initiated SNA transfers only. If only remotely initiated TCP/IP transfers will be used, set this value to *NO. Note: If you are running multiple copies of CA XCOM Data Transport, only one library should be in QUSRLIBL. Valid entries: *YES No routing entries required *NO Assume XCOM2SBS as target Default value: *NO Authority to objects in lib Does not apply to upgrades. Specifies the authority to CA XCOM Data Transport objects for users without specific authority to objects in the XCOM program library. Valid entries: *CHANGE, *ALL, *USE, or *EXCLUDE Default value: *EXCLUDE Installing and Upgrading CA XCOM Data Transport 3 5

34 Chapter 3: Installing and Upgrading CA XCOM Data Transport Prompt All APPC devices to XCOM2SBS? Description Does not apply to upgrades. Specifies whether a communications entry is added to the XCOM2SBS subsystem that allocates all APPC devices (see the chapter Configuring the SNA Network ). This parameter pertains to remotely initiated SNA transfers only. If only remotely initiated TCP/IP transfers will be used, set this value to *NO. Note: If your system is the target system for CA XCOM Data Transport transfers and you specify *NO, you must manually add communications entries for the devices that are used. Valid entries: *YES or *NO Default value: *NO What s Next? Use the following table to determine where to go next: If you are Installing CA XCOM Data Transport for the first time, or installing into a new library Go to the following section Installing CA XCOM Data Transport Upgrading CA XCOM Data Transport Upgrading CA XCOM Data Transport Installing CA XCOM Data Transport This section contains the procedure for a first-time installation of CA XCOM Data Transport on your AS/400 i5/os system. Read the procedure before beginning the installation. Before You Begin Before beginning the installation procedure, complete the installation worksheet in the appendix Installation, Configuration, and Customization Worksheets. 3 6 Getting Started

35 Chapter 3: Installing and Upgrading CA XCOM Data Transport If this is a brand new install of CA XCOM Data transport on your system, meaning you currently do not have any version of CA XCOM Data Transport already on your system, go to What s Next? Before installing CA XCOM Data Transport, perform the following tasks: Shut down CA 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 CA 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. See Back Up Your Configuration Files in this chapter. What s Next? Use the following table to determine where to go next: If you are Installing CA XCOM Data Transport directly from the installation CD Installing CA XCOM Data Transport using the alternate installation method Go to the following section Install Procedure from CD Installing or Upgrading using save files Install Procedure from CD Use the following procedure to install the Unicenter CA-XCOM Data Transport software: 1. Mount the distribution material in the appropriate drive. Sign on as the security officer. The Command Entry screen is displayed. 2. Type the following command and press F4: RSTLIB The initial Restore Library parameter list is displayed. Installing and Upgrading CA XCOM Data Transport 3 7

36 Chapter 3: Installing and Upgrading CA XCOM Data Transport 3. Fill in the following values on the initial Restore Library parameter list, and press F10: Saved Library = XINSTR11 Device = device name The rest of the Restore Library parameters are displayed. 4. Edit the following prompt values by typing over the existing values, and press Enter: End of media option = *LEAVE Data base member option = *ALL Allow object differences = *ALL All values are accepted and the XINSTR11 library is added to your disk. 5. Enter the following on the command line: ADDLIBLE XINSTR11 The XINSTR11 library is added to the library list. 6. Enter the following on the command line: INSTALL A prompt is displayed for a choice of screen text language. 7. Choose the language for textual screen displays and press Enter. The following prompt is displayed: CA-XCOM program library 8. Accept the default value of XCOMR11 for the program library or overtype it with a value from your worksheet and press Enter. The following prompt is displayed: Device 9. Accept the inherited value for Device or type over it with a value from your worksheet and press Enter. The following additional prompts are displayed: Copy files from library Note: If you are using the default CA XCOM Program Library, XCOMR11, and renamed your previous CA XCOM Program Library, be sure to specify the renamed CA XCOM Program Library here. Add pgm library to QUSRLIBL? Authority to objects in lib All APPC devices to XCOM2SBS? 3 8 Getting Started

37 Chapter 3: Installing and Upgrading CA XCOM Data Transport 10. Accept the default values for these prompts or overtype them with the values in your worksheet and press Enter. Additional messages about the progress of the install procedure appear at the bottom of the screen. When the installation is complete, the following message appears, followed by the CA XCOM Data Transport configuration services screen: Installation completed successfully 11. Go to Post Installation or Upgrade Considerations in this chapter. Upgrading CA XCOM Data Transport This section contains the procedure for upgrading CA XCOM Data Transport on your AS/400 i5/os. Follow the upgrade procedure only if CA XCOM Data Transport r11.x is installed. If the current CA XCOM Data Transport release is 3.x or earlier, you must follow the instructions for a new install. Read the procedure before beginning the upgrade. Note: When upgrading to a new release of CA XCOM Data Transport, it is a good practice specify a new CA XCOM Data Transport program library other than the program library currently used by the older release of CA XCOM Data Transport. Once the new release has been installed and tested, you can remove the previous CA XCOM Data Transport program library. Before You Begin Before upgrading CA XCOM Data Transport, perform the following tasks: Shut down CA 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 CA 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. See Back Up Your Configuration Files in this chapter. Complete the installation worksheet in Installation, Configuration, and Customization Worksheets before beginning the upgrade procedure. Installing and Upgrading CA XCOM Data Transport 3 9