ca xcom data transport for as/400 i5/os found at . contents v contents chapter 1: new features ........

12
Release Summary r11 SP01 CA XCOM Data Transport ® for AS/400 i5/OS

Upload: trinhbao

Post on 12-Jun-2018

246 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: CA XCOM Data Transport for AS/400 i5/OS found at . Contents v Contents Chapter 1: New Features ..... 1 –1 IPv6 Support

Release Summary

r11 SP01

CA XCOM™ Data Transport® for

AS/400 i5/OS

Page 2: CA XCOM Data Transport for AS/400 i5/OS found at . Contents v Contents Chapter 1: New Features ..... 1 –1 IPv6 Support

This documentation and any related computer software help programs (hereinafter referred to as the

“Documentation”) is for the end user’s informational purposes only and is subject to change or withdrawal by CA at

any time.

This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in

part, without the prior written consent of CA. This Documentation 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 related 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 product are permitted to have access to such copies.

The right to print copies of the documentation and to make a copy of the related software is limited to the period

during which the applicable 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

Documentation 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 DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING

WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE

OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO THE END USER OR ANY THIRD PARTY FOR ANY LOSS

OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT

LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY

ADVISED OF SUCH LOSS OR DAMAGE.

The use of any product referenced in the Documentation is governed by the end user’s applicable license

agreement.

The manufacturer of this Documentation is CA.

Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the

restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-

7014(b)(3), 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.

Page 3: CA XCOM Data Transport for AS/400 i5/OS found at . Contents v Contents Chapter 1: New Features ..... 1 –1 IPv6 Support

CA Product References

This document references the following CA product:

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 http://ca.com/support, 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 [email protected].

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 http://ca.com/docs.

Page 4: CA XCOM Data Transport for AS/400 i5/OS found at . Contents v Contents Chapter 1: New Features ..... 1 –1 IPv6 Support
Page 5: CA XCOM Data Transport for AS/400 i5/OS found at . Contents v Contents Chapter 1: New Features ..... 1 –1 IPv6 Support

Contents v

Contents

Chapter 1: New Features ........................................................ 1–1

IPv6 Support ........................................................................................................................ 1–1

CA XCOM Internal TCP/IP Tracing ............................................................................................ 1–2

Encryption Using XCOMOSSL .................................................................................................. 1–2

Chapter 2: Changes to Existing Features .............................. 2–1

Changed Stop and Start Commands for TCP/IP Servers ............................................................. 2–1

Parameters for Start Commands ........................................................................................ 2–2

Parameters for Stop Commands ........................................................................................ 2–3

Remote TCP/IP Transfers ....................................................................................................... 2–3

Page 6: CA XCOM Data Transport for AS/400 i5/OS found at . Contents v Contents Chapter 1: New Features ..... 1 –1 IPv6 Support
Page 7: CA XCOM Data Transport for AS/400 i5/OS found at . Contents v Contents Chapter 1: New Features ..... 1 –1 IPv6 Support

New Features 1–1

Chapter 1: New Features

The Release Summary for CA XCOM Data Transport for AS/400 i5/OS

documents both new features and changes to existing features for r11 SP01.

This chapter describes new features added to the product. The chapter

“Changes to Existing Features” describes changes made to existing features.

New features include the following:

IPv6 support

CA XCOM internal TCP/IP tracing

Encryption using XCOMOSSL

IPv6 Support

IPv6 support is now provided for CA XCOM Data Transport for AS/400 i5/OS.

The following new start and stop commands support this feature:

STRXCTCP6 (start TCP/IP IPv6 server)

STRXCTCP6S (start Secure Socket TCP/IP IPv6 server)

STPXCTCP6 (stop TCP/IP IPv6 Server)

STPXCTCP6S (stop Secure Socket TCP/IP IPv6 server)

There are two new parameters for these commands:

TCPL6PORT

Specifies the local TCP/IP port on which the server listens.

TCPLS6PORT

Specifies the local TCP/IP port on which the server listens.

Otherwise these commands use the same parameters as the commands for

starting and stopping a TCP/IP IPv4 server. For more information about these

parameters, see the chapter “Changes to Existing Features.”

Page 8: CA XCOM Data Transport for AS/400 i5/OS found at . Contents v Contents Chapter 1: New Features ..... 1 –1 IPv6 Support

Chapter 1: New Features

1–2 Release Summary

CA XCOM Internal TCP/IP Tracing

You can use the parameter TCPTRACE(*ON) to start CA XCOM internal TCP/IP

tracing with the following commands:

If you use TCPTRACE(*ON) with one of the commands to start a TCP/IP

listener (STRXCTCP, STRXCTCPS, STRXCTCP6, or STRXCTCP6S), trace

output is generated for the listener and all its slave jobs.

If you use TCPTRACE(*ON) with one of the SENDFILE, GETFILE, SENDJOB,

or SENDREPORT commands, trace output is generated in the job where

the CA XCOM file transfer is run, as follows:

– For a foreground transfer (parameter ENQ(*NO)) this is the current

job.

– For a background transfer (parameter ENQ(*YES)) this is one of the

background jobs XCOMBGxx in the XCOM2SBS subsystem.

For information about using CA XCOM internal TCP/IP tracing, see the CA

XCOM Data Transport for AS/400 i5/OS User Guide.

Encryption Using XCOMOSSL

The XCOMOSSL utility allows you to encrypt password parameter values in an

existing configuration file.

For information about using XCOMOSSL, see the CA XCOM Data Transport for

AS/400 i5/OS Getting Started.

Page 9: CA XCOM Data Transport for AS/400 i5/OS found at . Contents v Contents Chapter 1: New Features ..... 1 –1 IPv6 Support

Changes to Existing Features 2–1

Chapter 2: Changes to Existing Features

This chapter documents changes made to existing features for r11 SP01.

Changed features include the following:

Changed stop and start commands for TCP/IP servers

Remote TCP/IP transfers

Changed Stop and Start Commands for TCP/IP Servers

In r11, which supported IPv4, the start and stop commands for TCP/IP servers

were as follows:

Start commands

– STRXCOMTCP (start XCOM TCP/IP server)

– STRXCMTCPS (start TCP/IP SSL server)

Stop commands

– STPXCOMTCP (stop XCOM TCP/IP server)

– STPXCMTCPS (stop TCP/IP SSL server)

Because r11 SP01 supports IPv6, these commands have been renamed and

new commands have been added. The start and stop commands for TCP/IP

servers are now as follows:

Start commands

– STRXCTCP (start TCP/IP IPv4 server)

– STRXCTCPS (start secure socket TCP/IP IPv4 server)

– STRXCTCP6 (start TCP/IP IPv6 server)

– STRXCTCP6S (start secure socket TCP/IP IPv6 server)

Stop commands

– STPXCTCP (stop TCP/IP IPv4 server)

– STPXCTCPS (stop secure socket TCP/IP IPv4 server)

– STPXCTCP6 (stop TCP/IP IPv6 server)

– STPXCTCP6S (stop secure socket TCP/IP IPv6 server)

Page 10: CA XCOM Data Transport for AS/400 i5/OS found at . Contents v Contents Chapter 1: New Features ..... 1 –1 IPv6 Support

Chapter 2: Changes to Existing Features

2–2 Release Summary

Parameters for Start Commands

The start commands use the following parameters:

TCPLCLPORT, TCPLCSPORT, TCPL6PORT, or TCPLS6PORT

Specifies the local TCP/IP port on which the server listens.

BUFFERSIZE

Specifies the internal buffer size for sends and receives. The default size

allows multiple CA XCOM Data Transport records to be received in a single

secure socket call.

SENDCHKFRQ

Indicates the frequency with which CA XCOM Data Transport checks to see

if incoming error information is available when sending data. For example,

if the value is 5, a check is made every fifth time to see if there is

incoming data to receive before the data is sent.

MAXBACKLOG

Specifies the maximum number of incoming SSL TCP/IP file transfers that

can be held in the backlog queue.

RCVBUFSIZE

Specifies the buffer size for receives. Use 0 for the default size provided by

the TCP/IP socket implementation. The value for RCVBUFSIZE can be

smaller than the value for BUFFERSIZE.

SNDBUFSIZE

Specifies the buffer size for sends. Use 0 for the default size provided by

the TCP/IP socket implementation. The value for SNDBUFSIZE can be

smaller than the value for BUFFERSIZE.

TCPTRACE

Sets the CA XCOM Data Transport internal TCP/IP trace facility.

NODELAY

Refers to the Nagle algorithm for send coalescing. By default, small sends

may be delayed.

JOBD

Specifies the job description for the transfer request. This name includes

the library name for the job.

JOBQ

Specifies the job queue name for the job. This name includes the library

name for the job queue.

Page 11: CA XCOM Data Transport for AS/400 i5/OS found at . Contents v Contents Chapter 1: New Features ..... 1 –1 IPv6 Support

Chapter 2: Changes to Existing Features

Changes to Existing Features 2–3

Parameters for Stop Commands

The stop commands use the following parameters:

TCPLCLPORT, TCPLCSPORT, TCPL6PORT, or TCPLS6PORT

Specifies the local TCP/IP port on which the server listens.

LIB

Specifies the library where the secure socket TCP/IP server was started.

OPTION

Specifies whether the secure socket TCP/IP server terminates immediately,

or in a controlled way for the amount of time specified in the INTERVAL

keyword.

INTERVAL

Specifies the amount of time between the times when CA XCOM Data

Transport receives the command to terminate the secure socket TCP/IP

server and when the server is actually terminated.

Remote TCP/IP Transfers

In r3.0 and r11, TCP/IP IPv4 transfers were processed by pre-started TCP/IP

slave jobs. With r11 SP01, no more pre-started TCP/IP slave jobs are used.

Each remote TCP/IP transfer (IPv4, SSL IPv4, IPv6, and SSL IPv6) is run in a

separate slave job started by the TCP/IP master job. The master jobs are

named TCP4M<nnnnn>, SSL4M<nnnnn>, TCP6M<nnnnn>, and

SSL6M<nnnnn> for the IPv4, SSL IPv4, IPv6, and SSL IPv6 master jobs

respectively, where nnnnn is a five-digit port number. The slave jobs use a

similar job name, with the M replaced by S, for example SSL4S<nnnnn>.

Page 12: CA XCOM Data Transport for AS/400 i5/OS found at . Contents v Contents Chapter 1: New Features ..... 1 –1 IPv6 Support