Sei sulla pagina 1di 396

Unicenter

CA-XCOM Data

Transport for Windows NT

Server/Professional

User Guide

r11

Unicenter  CA-XCOM  Data Transport  for Windows NT Server/Professional User Guide r11 J02577-2E

J02577-2E

This documentation and related computer software program (hereinafter referred to as the “Documentation”) is for the end user’s informational purposes only and is subject to change or withdrawal by Computer Associates International, In c. (“CA”) at any time.

This documentation may not be copied, transferred, reproduced, disclosed or duplicated, in whole or in part, without the prior written consent of CA. This documentation is 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 this documentation for their own internal use, provided that all CA copyright notices and legends are affixed t o each reproduced copy. Only authorized employees, consultants, or agents of the user who are bound by the confidentiality provisions of the license for the software are permitted to have access to such copies.

This right to print copies 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 return to CA the reproduced copies or to certify to CA that same have been destroyed.

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 this documentation and this documentation is governed by the end user’s applicable license agreement.

The manufacturer of this documentation is Computer Associates International, Inc.

Provided with “Restricted Rights” as set forth in 48 C.F.R. Section 12.212, 48 C.F.R. Sections 52.227-19(c)(1) and (2) or DFARS Section 252.227-7013(c)(1)(ii) or applicable successor provisions.

2011 Computer Associates International, Inc.

All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

Contents

Contents

Chapter 1: Introduction

Unicenter CA-XCOM Data Transport Connectivity

1-2

Network Levels in the SNA Model

1-3

End User Level

1-3

Logical Level

1-4

Physical Level

1-4

Network Level Diagram

1-5

Benefits of LU 6.2 (APPC)

1-5

Improved Throughput

1-6

Support for Advanced Networking

1-6

Unicenter CA-XCOM Data Transport in the TCP/IP Network

1-7

TCP/IP Protocol Stack

1-7

Network Layer

1-8

Internetwork Layer

1-8

Transport Layer

1-8

Application Layer

1-9

Unicenter CA-XCOM Data Transport Nodes in the TCP/IP Network

1-9

TCP/IP Address

1-9

TCP/IP Port

1-9

Successful Send File Transfer Scenario

1-10

Chapter 2: Using Unicenter CA-XCOM Data Transport

Unicenter CA-XCOM Data Transport GUI

2-1

File Name, Path, and Directory Considerations

2-1

Keyboard Commands

2-2

Default Directories and Drives

2-2

Requirements

2-3

Starting Unicenter CA-XCOM Data Transport

2-3

Using the Unicenter CA-XCOM Data Transport Main Window

2-5

Main Window

2-5

Considerations

2-6

Procedure

2-6

Menu Bar Selections

2-7

Pushbuttons

2-8

Using Transfer Configuration Files

2-9

Default Configuration Files

2-9

Precedence of Parameter Values

2-10

Modifying Options and Configurations

2-10

Multiple Transfers from the GUI

2-10

Considerations

2-11

Creating a Configuration File

2-11

Considerations

2-11

Procedure

2-12

Editing an Existing Configuration File

2-14

Considerations

2-14

Procedure

2-15

Using the Transfer List to Access and Perform Transfers

2-16

Transfer List Fields

2-17

Saving Displayed Transfers

2-17

Considerations

2-17

Procedure

2-18

Fields

2-19

Transfer List Symbols

2-19

Using the Edit Transfer Windows

2-20

Accessing the Edit Transfer Window

2-20

Menu Bar Selections

2-21

Pushbuttons

2-21

Fields

2-22

RECORD_FORMAT

2-26

Setting the Options on an Edit Transfer Window

2-28

Modifying the Options Group

2-29

Encoding Options

2-29

Maximum Record Length Field

2-30

CodeTable Option

2-30

Truncation Option

2-31

Procedure

2-31

Edit Transfer Window Options Summary

2-32

Sending a File Using an Edit Transfer Window

2-33

Accessing the Send File Window

2-33

Considerations

2-34

Procedure

2-34

Sending a Report Using an Edit Transfer Window

2-35

Accessing the Send Report Window

2-35

Considerations

2-36

Procedure

2-36

Sending a Job Using an Edit Transfer Window

2-37

Accessing the Send Job Window

2-37

Considerations

2-38

Procedure

2-38

Receiving a File Using an Edit Transfer Window

2-39

Accessing the Receive File Window

2-39

Considerations

2-39

Procedure

2-40

Using the Version 2 Window—Checkpoint, Restart, Protocol, Port

2-41

Accessing the Version 2 Window

2-41

Considerations

2-42

Procedure – Checkpoint/Restart

2-42

Procedure – Protocol/Port

2-43

Fields

2-43

Pushbuttons

2-44

Specifying User IDs and Passwords for File Access

2-44

Accessing the Security Window

2-45

Considerations

2-45

Procedure

2-45

Remote System Access Fields

2-46

Local File Access Fields

2-46

Pushbuttons

2-46

Notifying Local Users of Transfer Completion

2-47

Accessing the Local Notify Dialog

2-47

Considerations

2-47

Procedure

2-47

Drop-down Lists

2-48

Field

2-48

Pushbuttons

2-49

Notifying Remote Users of Transfer Completion

2-49

Accessing the Remote Notify Dialog

2-49

Considerations

2-49

Procedure

2-50

Drop-down List

2-50

Field

2-51

Pushbuttons

2-51

Setting Compression Type for a Transfer

2-52

Accessing the Compression Window

2-52

Considerations

2-52

Procedure

2-52

Drop-down List

2-53

Pushbuttons

2-53

Sending an Indirect Transfer

2-54

Accessing the Indirect Transfer Window

2-54

Considerations

2-54

Procedure

2-54

Field

2-55

Pushbuttons

2-55

Setting System Environment Variables—Reports Containing Machine Code Characters

2-55

Debugging Problems and Tracing

2-57

Accessing the Debugging Window

2-57

Procedure

2-57

Drop-down List

2-57

Pushbuttons

2-58

Scheduling Transfers

2-58

Accessing the Schedule Window

2-58

Considerations

2-59

Procedure

2-59

Priority Menu Options

2-60

Fields

2-60

Pushbuttons

2-60

Performing Secure Socket Transfers

2-61

Accessing the Secure Socket Window

2-61

Procedure

2-61

Pushbuttons

2-62

Browsing the Log File

2-62

Accessing the Log Browser Window

2-63

Procedure

2-63

Pushbuttons

2-63

Searching for Information in the Log

2-63

Accessing the Find Window

2-64

Procedure

2-64

Field

2-64

Checkbox

2-64

Pushbuttons

2-65

Viewing and Controlling Transfer Status

2-65

Accessing the Queue Status Window

2-66

Procedure

2-66

Menu Bar Selections

2-67

Pushbuttons

2-68

Queue Status

Direction Symbols

2-68

Viewing Transfer Status Details

2-69

Accessing the Details Window

2-69

Procedure

2-69

Fields

2-70

Pushbutton

2-70

Using the Properties Dialog Pages

2-70

Accessing the Properties Tab Pages

2-71

Considerations

2-72

Procedure

2-72

Character Conversions Properties Tab Page

2-73

Options

2-74

Incoming Transfers Properties Tab Page

2-75

Options

2-76

Queue Properties Tab Page

2-77

Options

2-78

Security Properties Tab Page

2-79

Options

2-80

System Properties Tab Page

2-81

Options

2-82

TCP/IP Properties Tab Page

2-84

Options

2-85

Trace Properties Tab Page

2-88

Options

2-89

Chapter 3: The Command Line Interface

Command Prompt

3-1

Using Configuration Files

3-1

Configuration Files

3-2

Creating Configuration Files from the Command Prompt

3-2

Transferring Files

3-4

Specifying Protocols

3-4

XCOM62

3-5

XCOMTCP

3-5

Multiple Transfers

3-5

Wildcard Characters

3-5

Syntax

3-5

Syntax for XCOM62

3-5

Syntax for XCOMTCP

3-6

Notes On Using Options

3-6

Options

3-6

Transferring Files Using SNA/APPC Protocols

3-8

Using SNA/APPC Protocols

3-8

Transferring Files Using TCP/IP Protocols

3-9

Using IP Addresses and Names

3-9

Specifying the Remote System

3-10

TCP/IP Name Resolution

3-11

Using TCP/IP Protocols with Unicenter CA-XCOM Data Transport

3-11

PROTOCOL

3-13

Setting Communications Parameters

3-13

Communications and Data Transfer Parameters

3-13

Parameters

3-14

CODETABL

3-14

COMPRESS

3-14

MAXRECLEN

3-15

REMOTE_SYSTEM

3-15

REMOTE_SYSTEM_RF

3-16

REMOTE_SYSTEM_SJ

3-16

REMOTE_SYSTEM_SR

3-16

TEMPDIR

3-17

TRUNCATION

3-17

VERSION

3-17

Using the Send File Command

3-17

Parameters

3-18

FILE_OPTION

3-18

LOCAL_FILE

3-20

REMOTE_FILE

3-20

Using the Retrieve File Command

3-20

Parameters

3-21

FILE_OPTION_RF

3-21

LOCAL_FILE_RF

3-23

REMOTE_FILE_RF

3-23

REMOTE_SYSTEM_RF

3-23

UNIT_RF

3-24

VOLUME_RF

3-24

Creating a File on an IBM Mainframe

3-24

Parameters

3-25

ALLOCATION_TYPE

3-25

BLKSIZE

3-25

DATACLAS

3-26

DSNTYPE

3-26

LRECL

3-26

MGMTCLAS

3-27

NUM_OF_DIR_BLOCKS

3-27

PRIMARY_ALLOC

3-27

RECORD_FORMAT

3-28

SECURE_SOCKET

3-29

STORCLAS

3-30

SECONDARY_ALLOC

3-30

UNIT

3-30

VOLUME

3-30

XCOM_CONFIG_SSL

3-30

XCOM_SHOW_CIPHER

3-31

Tape Parameters for an IBM Mainframe

3-31

DEN

3-31

EXPDT

3-32

LABEL

3-32

LABELNUM

3-33

RETPD

3-33

TAPE

3-33

UNITCT

3-34

VOLCT

3-34

VOLSQ

3-34

Using a Send Report Command

3-35

Parameters

3-36

CARRIAGE_CONTROL_CHARACTERS

3-36

CLASS

3-36

COPIES

3-37

DESTINATION

3-37

DISPOSITION

3-37

FCB

3-38

FORM

3-38

HOLDFLAG

3-38

LOCAL_FILE_SR

3-38

REMOTE_SYSTEM_SR

3-39

REPORT_TITLE

3-39

SPOOL_FLAG

3-40

Using the Send Job Command

3-40

LOCAL_FILE_SJ

3-41

REMOTE_SYSTEM_SJ

3-41

ERRORLEVEL Return Codes from xcomtcp.exe and xcom62.exe

3-41

Tracing Problems

3-42

XTRACE

3-43

Setting Up Log Files

3-43

XLOGFILE

3-44

Setting File Type Conversion

3-44

CARRIAGE_FLAG

3-45

CODE_FLAG

3-46

Creating Custom Character Sets for File Conversion

3-47

Custom Character Sets

3-47

Procedure

3-47

Hexadecimal Numbers in Conversion Tables

3-48

Customizing Default Character Sets

3-49

Procedure

3-49

Specifying a Custom Character Set

3-49

Procedure

3-50

Using Store and Forward

3-50

XIDEST

3-52

Setting Password and User ID Security

3-52

DOMAIN

3-53

FILE_ACCESS_PASSWORD

3-53

FILE_ACCESS_USERNAME

3-53

PASSWORD

3-53

TRUSTED

3-53

USERID

3-54

Encrypting Parameter Values in Existing Configuration Files

3-54

Syntax

3-54

Options

3-55

Procedure

3-55

Changing an Encrypted Value

3-56

Scheduling Locally Initiated Transfers

3-56

Parameters

3-57

PRIORITY

3-57

QUEUE

3-57

START_DATE

3-58

START_TIME

3-58

Notifying of Transfer Completion

3-59

Example 1

3-59

Example 2

3-59

Parameters

3-60

LCLNTFYL

3-60

LOCAL_NOTIFY

3-60

NOTIFYL

3-61

NOTIFY_NAME

3-61

NOTIFYR

3-62

RMTNTFYL

3-63

Checkpointing and Restarting Transfers

3-63

List of Parameters

3-65

CHECKPOINT_COUNT

3-65

NUMBER_OF_RETRIES

3-65

RESTART_SUPPORTED

3-65

RETRY_TIME

3-66

Purging the Unicenter CA-XCOM Data Transport Log File

3-66

Syntax

3-66

Chapter 4: The Application Programming Interface

XcomAPI

4-1

XcomQAPI

4-2

Upgrading from Previous Releases

4-2

Link Libraries

4-2

SNA Libraries

4-2

TCP/IP Libraries

4-3

Starting States

4-3

Starting States in startst.h

4-3

API Control Block Structure

4-4

Using API Member Names

4-8

XcomAPI Member Names

4-8

allocation_type

4-8

blksize

4-9

carriage_control_characters

4-9

carriage_flag

4-10

checkpoint_count

4-10

class

4-11

code_flag

4-11

codetabl

4-11

compress

4-12

config_ssl

4-13

convert_classes

4-13

copies

4-13

datacls

4-13

debug_flag

4-13

den

4-14

destination

4-14

disposition

4-14

domain

4-15

dsntype

4-15

eol_classes

4-15

expdt

4-15

fcb

4-16

file_option

4-16

file_type

4-17

form

4-17

hold

4-18

label

4-18

labelnum

4-18

lclntfyl

4-19

local_file

4-19

local_file_rf

4-19

local_file_sj

4-20

local_file_sr

4-20

local_notify

4-20

lrecl

4-21

maxreclen

4-21

metacode_classes

4-21

mgtclas

4-22

notify_name

4-22

notifyl

4-22

notifyr

4-23

notify_term

4-24

number_of_retries

4-24

num_of_dir_blocks

4-24

password

4-24

primary_alloc

4-25

port

4-25

protocol

4-25

queue

4-26

record_format

4-26

remote_file

4-28

remote_file_rf

4-28

remote_system

4-28

remove_trail_blanks

4-29

report_title

4-29

restart_supported

4-29

retpd

4-30

rmtntfyl

4-30

secondary_alloc

4-30

shell_cmd

4-31

spool_flag

4-31

start_date

4-31

start_time

4-31

stat_frequency

4-32

storcls

4-32

tape

4-32

tempdir

4-32

transfer_id

4-33

transfer_usr_data

4-33

truncation

4-33

trusted

4-33

unit

4-34

unitct

4-34

userid

4-34

user_data

4-34

version

4-34

volct

4-35

volsq

4-35

volume

4-35

xcomfullssl

4-35

xendcmd

4-36

xidest

4-36

xlogfile

4-36

xlpcmd

4-36

xmode

4-37

xnotifycmd

4-37

xppcmd

4-37

xprecmd

4-37

xtrace

4-38

Using XcomQAPI Option Parameters

4-38

Option Parameters

4-38

funccode

4-38

Parameters Set Within the XcomQAPI Program

4-40

API Examples

4-40

About the XcomAPI Example

4-40

Unicenter CA-XCOM Data Transport for Windows NT API Return Codes

4-41

XcomQAPI Example

4-43

Chapter 5: Remote System Information

AS/400

5-1

Naming Conventions

5-1

Types of Files Supported

5-2

Additional Features

5-2

Configuration Issues

5-2

Case Sensitivity

5-2

z/OS

5-3

Naming Conventions

5-3

Types of Files Supported

5-4

DCB Information

5-4

Additional Features

5-5

Novell NetWare

5-5

Naming Conventions

5-5

Types of Files Supported

5-6

Destination Printer Information

5-6

Restriction

5-6

OpenVMS

5-7

Naming Conventions

5-7

Restrictions

5-8

Stratus/System 88

5-9

Naming Conventions

5-9

Types of Files Supported

5-10

Additional Features

5-10

Restrictions

5-10

Tandem

5-11

Naming Conventions

5-11

Types of Files Supported

5-11

File Type Specification

5-12

Remotely-Initiated Send Requests

5-13

UNIX

5-13

Naming Conventions

5-13

Types of Files Supported

5-13

Restriction

5-14

VM

5-14

Naming Conventions

5-14

Types of Files Supported

5-14

DCB Information

5-15

Restriction

5-15

VSE

5-16

VSAM Naming Conventions

5-16

SAM Naming Conventions

5-17

TAPE Naming Conventions

5-19

DTF Information

5-20

Types of Files Supported

5-20

Restrictions

5-20

Windows

5-21

Naming Conventions

5-21

Restriction

5-22

Windows NT Server/Professional

5-22

Naming Conventions

5-23

Types of Files Supported

5-24

Additional Features

5-24

Destination Printer Information

5-25

Restrictions

5-25

Chapter 6: Performance Tuning

Appendix A: Unicenter CA-XCOM Data Transport Parameters

Parameter Values Used in the GUI

A-2

Parameter Values Used at the Command Prompt

A-3

Parameter Format for Command Prompt and Scripts

A-3

Syntax

A-4

Guidelines

A-4

List of Unicenter CA-XCOM Data Transport Parameters

A-5

Version 2 Parameters

A-5

AGE_TIME

A-5

ALLOCATION_TYPE

A-6

ATOE_FILENAME

A-6

BLKSIZE

A-6

CARRIAGE_CONTROL_CHARACTERS

A-7

CARRIAGE_FLAG

A-7

CHECKPOINT_COUNT

A-8

CLASS

A-9

CODE_FLAG

A-9

CODETABL

A-10

COMPRESS

A-10

CONTROL

A-11

CONVERT_CLASSES

A-11

COPIES

A-11

CREATE_DIRECTORIES

A-12

DAEMON_TIMEOUT

A-12

DATACLAS

A-12

DEBUG_FLAG

A-12

DEN

A-13

DESTINATION

A-13

DESTINATION_TYPE

A-13

DISPOSITION

A-14

DOMAIN

A-14

DSNTYPE

A-14

EOL_CLASSES

A-15

ETOA_FILENAME

A-15

EXPDT

A-15

EXPIRATION_TIME

A-15

FCB

A-16

FILE_ACCESS_PASSWORD

A-16

FILE_ACCESS_USERNAME

A-16

FILE_OPTION

A-16

FILE_OPTION_RF

A-18

FORM

A-19

HOLDFLAG

A-19

IMPLICIT_PACKING

A-20

INTERNAL_CONVERSION_TABLES

A-20

LABEL

A-20

LABELNUM

A-21

LCLNTFYL

A-21

LOCAL_FILE

A-22

LOCAL_FILE_RF

A-22

LOCAL_FILE_SJ

A-22

LOCAL_FILE_SR

A-23

LOCAL_NOTIFY

A-23

LRECL

A-23

MAIL_USERNAME

A-24

MAX_QUEUE_ENTRIES

A-24

MAX_SESSIONS_ENTRIES

A-24

MAXRECLEN

A-25

METACODE_CLASSES

A-25

MGMTCLAS

A-25

NOTIFY_NAME

A-26

NOTIFYL

A-26

NOTIFYR

A-27

NOTIFY_TERM

A-28

NUMBER_OF_RETRIES

A-28

NUM_OF_DIR_BLOCKS

A-28

PASSWORD

A-28

PORT

A-29

PRIMARY_ALLOC

A-29

PRIORITY

A-29

PROTOCOL

A-30

QUEUE

A-30

QUEUE_PATH

A-30

RECORD_FORMAT

A-31

REMOTE_FILE

A-32

REMOTE_FILE_RF

A-32

REMOTE_SYSTEM

A-33

REMOTE_SYSTEM_RF

A-33

REMOTE_SYSTEM_SJ

A-33

REMOTE_SYSTEM_SR

A-34

REMOVE_TRAIL_BLANKS

A-34

REPORT_TITLE

A-34

RESTART_SUPPORTED

A-35

RETPD

A-35

RETRY_TIME

A-35

RMTNTFYL

A-36

SECONDARY_ALLOC

A-36

SECURE_SOCKET

A-36

SESSIONS_FILE

A-37

SHELL_CMD

A-37

SOCK_DELAY

A-37

SOCK_RCV_BUF_SIZE

A-38

SOCK_SEND_BUF_SIZE

A-38

SPACE

A-39

SPOOL_FLAG

A-39

START_DATE

A-39

START_TIME

A-40

STAT_FREQUENCY

A-40

STORCLAS

A-40

TAPE

A-40

TCP_CMD

A-41

TEMPDIR

A-41

TP_CMD

A-41

TRACE_PATH

A-41

TRANSFER_ID

A-42

TRANSFER_TYPE

A-42

TRANSFER_USR_DATA

A-42

TRUNCATION

A-43

TRUSTED

A-43

TXPI_BUF_SIZE

A-43

TXPI_RECEIVE_TIMEOUT

A-44

TXPI_SEND_CHECK_FREQ

A-44

TXPI_TERM_TIMEOUT

A-44

UNIT

A-45

UNITCT

A-45

UNIT_RF

A-45

USER_DATA

A-45

USERID

A-45

VERSION

A-46

VOLCT

A-46

VOLSQ

A-46

VOLUME

A-46

VOLUME_RF

A-47

WRITE_EOF

A-47

XBUFFSIZE

A-47

XCOM_CONFIG_SSL

A-47

XCOM_PASSWORD

A-47

XCOM_SHOW_CIPHER

A-48

XCOM_USERID

A-48

XENDCMD

A-48

XIDEST

A-49

XLOGFILE

A-49

XLPCMD

A-49

XLUNAME

A-49

XMODE

A-50

XNODESPEC

A-50

XNOTIFYCMD

A-50

XPPCMD

A-50

XPRECMD

A-51

XTRACE

A-51

Appendix B: Messages

Error Message Example

B-1

Message ID Content

B-1

List of Messages

B-3

Service-Specific Messages

B-61

Appendix C: Logical Units

Physical Network Components

C-1

Logical Network Components

C-2

Session

C-2

PCID

C-2

SID

C-2

Logical Unit Types

C-3

Criteria for Independent Logical Units

C-4

Systems Supporting ILUs

C-4

Software Version Support for ILUs

C-4

LU 6.2 Independent Implementations

C-5

Direct Sessions with Dependent Logical Unit

C-5

PU Type

C-5

Index

Chapter

1

Introduction

This guide provides information about the use of the Unicenter ® CA-XCOM ® Data Transport ® product with Microsoft Windows NT Server/Professional (2000, 2003, and XP). Its scope ranges from an overview of the software to descriptions of the parameters required to execute Unicenter CA-XCOM Data Transport functions. Although there are extensive similarities between all of the Unicenter CA-XCOM Data Transport components, you should always refer to the corresponding user’s guide when requiring specific information about a component.

Unicenter CA-XCOM Data Transport Connectivity

Unicenter CA-XCOM Data Transport Connectivity

The following diagram shows how Unicenter CA-XCOM Data Transport can provide connectivity across very diverse environments. Any client node using Unicenter CA-XCOM Data Transport can send and receive files from any of the remote systems shown in this example or any other Unicenter CA-XCOM Data Transport component. For more information, see the section Modular Support of Most Systems in the chapter “Welcome” in the Unicenter CA-XCOM Data Transport for Windows NT Server/Professional Getting Started.

in the Unicenter CA-XCOM Data Transport for Windows NT Server/Professional Getting Started . 1–2 User Guide

Network Levels in the SNA Model

Network Levels in the SNA Model

An SNA network is divided into levels of physical and logical components. A path control network that runs over the physical components interconnects the logical components.

As data is passed up and down the SNA functional layers, each layer performs a set of control functions and adds control information to the data in the form of a header. The headers do not change the information in the data, but communicate with the next layer of SNA to ensure that the data is understood.

As the data is passed through the layers, headers that are added at one end of the network are stripped off and read by the receiving end. Thus, when the data reaches its final destination, it is back to its original form.

End User Level

The end user level consists of transaction programs (like Unicenter CA-XCOM Data Transport) that communicate with other transaction programs using LUs. In a Unicenter CA-XCOM Data Transport transfer request, the local end user specifies the following:

Type of transfer (send report, file, or job, or receive file)

Name of the local file

Name of the remote file to create, append, or replace

The request is then processed by the Unicenter CA-XCOM Data Transport transaction program on the local system that sends an allocate verb and header record to the remote system to establish an LU 6.2 session. When a session is established and all of the parameters are confirmed by the remote system, Unicenter CA-XCOM Data Transport on the local system will send the file, broken into data records, across the physical connection.

The remote Unicenter CA-XCOM Data Transport transaction program is then invoked by the allocate verb sent by the local system (some systems cannot be automatically invoked and must already be active to receive the allocate verb). The remote transaction program then creates or opens the requested file, receives the data records, and places them in the file. When all the records have been received, Unicenter CA-XCOM Data Transport on the remote system will send a trailer record to the local system stating the number of records transmitted.

Network Levels in the SNA Model

Logical Level

The logical level consists of logical units (LUs) that link the physical units (PUs) and transaction programs (TPs). Each Unicenter CA-XCOM Data Transport user should be assigned a unique LU name for gateway or workstation identification. Each data record traveling across the line will contain LU 6.2 protocol information containing instructions for the remote system.

Physical Level

The physical level consists of physical unit (PU) nodes linked by a physical connection. Unicenter CA-XCOM Data Transport supports transfers between physically connected systems whether they are directly or indirectly connected. PU Type 2.1 nodes can make a direct logical link even without a direct physical connection. Transfers involving PU Type 2.0 nodes (like VAX/VMS) can be made using the store-and-forward feature of Unicenter CA-XCOM Data Transport.

Network Levels in the SNA Model

Network Level Diagram

The following diagram shows the various network levels used to communicate with Unicenter CA-XCOM Data Transport:

END

USER

LEVEL

LOGICAL

LEVEL

PHYSICAL

LEVEL

Benefits of LU 6.2 (APPC)

Local Remote User User Unicenter Unicenter CA-XCOM CA-XCOM Data Transport Data Transport LU 6.2 LU
Local
Remote
User
User
Unicenter
Unicenter
CA-XCOM
CA-XCOM
Data Transport
Data Transport
LU 6.2
LU 6.2
Physical
Physical
Unit Node
Unit Node
Physical Connection

Unicenter CA-XCOM Data Transport is built upon the LU 6.2 protocol. LU 6.2 is also known as Advanced Program-to-Program Communications (APPC) and is IBM’s most powerful enhancement to the Systems Network Architecture (SNA) suite of communications protocols.

Network Levels in the SNA Model

Improved Throughput

When Unicenter CA-XCOM Data Transport uses the LU 6.2 protocol, it does not place hardware restrictions on the size of the data that it sends. RJE-based data transfer packages (LU Type 1) limit the size of a data frame (RU) to 80 characters, while 3270-based transfer packages (LU Type 2) often limit the size to 1,920 characters, the size of one screen. LU 6.2 allows RU sizes of up to 65,536 characters.

Each transmitted string of data is wrapped in a protocol envelope. Larger RU sizes, such as those allowed with Unicenter CA-XCOM Data Transport, mean less protocol overhead and a higher percentage of actual data traveling across your communication links.

of actual data traveling across your communication links. Support for Advanced Networking For SNA, LU 6.2

Support for Advanced Networking

For SNA, LU 6.2 fully exploits the PU Type 2.1 peer protocol. This means that LU 6.2 is the only protocol that can use advanced functions such as Low Entry Networking (LEN), Advanced Peer-to-Peer Networking (APPN), and Independent Logical Units (ILUs) that are changing the face of computer networking today. For more information, see the appendix “Logical Units.”

APPC allows two programs running on distinctly different computers to converse with each other in real time without regard to hardware. All other protocols assume that one of the two devices communicating is a dumb terminal and impose all the limitations of a particular terminal on the partner computer. APPC and Unicenter CA-XCOM Data Transport recognize that distributed processing employs intelligent processors so they can exploit the intelligence of the computers on which they are running.

Unicenter CA-XCOM Data Transport in the TCP/IP Network

Unicenter CA-XCOM Data Transport in the TCP/IP Network

The architectural and conceptual framework of the TCP/IP communications protocol as it relates to the implementation of Unicenter CA-XCOM Data Transport as a TCP/IP application is discussed in the following topics.

TCP/IP Protocol Stack

TCP/IP is a collection of specialized communications protocols and functions organized into a stack of four layers. The layers that make up the TCP/IP protocol stack are the following:

Network layer (the lowest protocol layer)

Internetwork layer

Transport layer

Application layer (the highest protocol layer)

Each layer in the TCP/IP protocol stack provides services to the layer above it and uses the services below it.

The following table lists the protocols and functions that form the content of each layer of the TCP/IP protocol stack. (The table shows only partial contents for the top and bottom layer.)

TCP/IP Protocol Layer

Protocols and Functions

Network layer

Token Ring

Ethernet

X.25

and so on

Internetwork layer

Internet Protocol (IP) Control Message Protocol (ICMP) Address Resolution Protocol (ARP)

Transport layer

Transmission Control Protocol (TCP) User Datagram Protocol (UDP)

Application layer

Telnet File Transfer Protocol (FTP) Simple Mail Transfer Protocol (SMTP) Domain Name System (DNS) Sockets and so on

Unicenter CA-XCOM Data Transport in the TCP/IP Network

The next few sections provide a summary of the services that each layer of the protocol stack performs in the TCP/IP network and a description of the protocols that are particularly important for the functioning of Unicenter CA-XCOM Data Transport as a TCP/IP network node.

Network Layer

The Network layer provides a set of protocols, such as Token Ring and Ethernet, that define how data are transported over different physical networks.

Internetwork Layer

The protocols of the Internetwork layer provide connection services for TCP/IP. The protocols in this layer connect physical networks and transport protocols.

The Internet Protocol (IP) of this layer integrates different physical networks into a unified logical network known as the Internet and provides for the universal addressing of computers (hosts) in a TCP/IP (Internet) network. IP uses a 32-bit number (IP address) that identifies both a physical network and a specific computer within that network. The IP address is the basic transport mechanism for routing data from a source computer to a destination computer.

However, IP does not ensure a reliable communication, because it does not require that the computers participating in a data exchange acknowledge the reception of the transmitted data. The reliability of communication is implemented at the next higher protocol layer.

Transport Layer

The protocols of the Transport layer allow communication between application programs.

The Transmission Control Protocol (TCP) of this layer establishes a connection between the sender and receiver and provides a continuous communication service with reliability of transmissions. TCP divides the data to be transmitted into smaller units (packets, datagrams), sends them individually using IP, and reassembles them at the destination node, comparing the received data with the data that were sent. TCP is capable of determining if the two are the same. If they are not (for example, data were lost or damaged during transmission), TCP resends the missing data.

Unicenter CA-XCOM Data Transport in the TCP/IP Network

Application Layer

The Application layer, which is built on the services of the Transport layer, provides a number of applications that allow users to use network services (terminal-to-terminal communication, data transfer, electronic mail, and so on).

The Application layer provides an application-programming interface known as Sockets for communications applications. Unicenter CA-XCOM Data Transport uses this component of the Application layer to transfer files to machines in a TCP/IP network.

Unicenter CA-XCOM Data Transport Nodes in the TCP/IP Network

Each computer in a TCP/IP network is assigned at least one unique address, which is used by the IP and other higher-level protocols.

TCP/IP Address

 

TCP/IP employs an addressing scheme consisting of a 32-bit long field divided into two parts. The first part of the address field contains a network address; the second field contains the address of a specific computer.

A TCP/IP address is written in dotted-decimal notation, which is obtained by first dividing the 32-bit long address into four 8-bit long fields and then converting each of the four fields into a decimal number and separating the fields with periods. The decimal numbers should be specified without leading zeros.

Instead of using a numeric address, a symbolic name may be used to identify a computer in a TCP/IP network. Each computer in a TCP/IP network is assigned at last one name, which is resolved to a numeric address using either a translation file or an application known as the name server (which is part of the Domain Name System function of the Application layer).

TCP/IP Port

The notions of port and port number are extensions of the TCP/IP address. Once the TCP/IP address has been used to deliver data to the desired computer in the network, the port number is used to identify the process for which the data are intended. By using ports and port numbers one computer can provide more than one service. Unicenter CA-XCOM Data Transport uses a predefined port number but it can be changed if it interferes with existing application services.

Successful Send File Transfer Scenario

Successful Send File Transfer Scenario

The following flowchart illustrates a normal Unicenter CA-XCOM Data Transport send file:

Scenario The following flowchart illustrates a normal Unicenter CA-XCOM Data Transport send file: 1–10 User Guide

Successful Send File Transfer Scenario

Compare the following steps with the Send File Flowchart to follow a typical successful send file transfer.

1. The local Windows user invokes Unicenter CA-XCOM Data Transport and requests a transfer.

2. Unicenter CA-XCOM Data Transport verifies the information contained in the request.

For example, Unicenter CA-XCOM Data Transport checks to see if the local file exists on the local system.

3. Unicenter CA-XCOM Data Transport establishes a connection with the remote system and sends along the header record to the remote system. The header record contains transfer information regarding the request, for example, file names and compression. The local system then waits for confirmation of the header record information.

4. Once the contents of the header record are verified, Unicenter CA-XCOM Data Transport begins sending data records to the remote system. Unicenter CA-XCOM Data Transport sends each data record, checking to see if any sending errors occur. If no errors are found, the local system checks for an end-of-file marker denoting the last record of the file. If no end-of-file marker is found, another data record is sent.

5. If an end-of file marker is found, the local system sends a trailer record, which indicates the number of data records sent. The local system then awaits verification from the remote system that the number of records received is equal to the number of records sent. If the number of records matches, a successful send file message is sent to the user on the local system and the conversation ends. If notification was specified, Unicenter CA-XCOM Data Transport on the remote system notifies the user of a successful transfer.

Chapter

2

Using Unicenter CA-XCOM Data Transport

This chapter contains information about using the Graphical User Interface (GUI) of Unicenter CA-XCOM Data Transport. It describes the functions and options available from the Unicenter CA-XCOM Data Transport for Windows NT main window, and then describes how to create and edit transfer configuration files, how to set options, and how to perform transfers. It also contains information about using the GUI to manage Unicenter CA-XCOM Data Transport. In addition, this chapter also contains information for administrators on using the Properties Dialog pages to modify global defaults.

Unicenter CA-XCOM Data Transport GUI

The Graphical User Interface of Unicenter CA-XCOM Data Transport provides access to all of the features of Unicenter CA-XCOM Data Transport. From the GUI you can do the following:

Create and edit Unicenter CA-XCOM Data Transport transfer configuration files

Specify transfer type

Initiate transfers

Monitor the log and trace functions

Update the status of active and pending transfers

File Name, Path, and Directory Considerations

Consider the following:

Before executing a file transfer request, be sure that you have properly set up your directories and path variables.

Unicenter CA-XCOM Data Transport accesses files locally or from any file server on the Microsoft Windows Network or the NetWare or Compatible Network.

Universal Naming Convention (UNC) is supported.

Unicenter CA-XCOM Data Transport GUI

Standard Windows path names are supported. To specify a path name that contains a blank or special character, put double quotes (“ ”) around it.

Standard Windows file types are supported (FAT, NTFS, HPFS).

In addition, administrators should be aware of the following:

Be sure that the XCOM_HOME environment variable is set to the directory where Unicenter CA-XCOM Data Transport is installed.

Your PATH variable should include the directory where Unicenter CA-XCOM Data Transport is installed. The default directory is C:\XCOMNT.

The C:\XCOMNT directory is the default repository for the subdirectories that Unicenter CA-XCOM Data Transport uses for log and configuration files.

Keyboard Commands

When you use keyboard commands instead of mouse operations, note the following:

Use Alt+Spacebar to open the list of control-menu box options for any Unicenter CA-XCOM Data Transport window. (Use this instead of the Windows Alt+Hyphen keyboard command.)

Use Alt+Underlined letter to open any menu. Then, to select a menu command, use the underlined letter of that command. Note that if the Caps Lock key is on, these commands do not function.

Default Directories and Drives

In this user guide we indicate C:\XCOMNT as the default path. Your installation may have Unicenter CA-XCOM Data Transport under a different path or on a different drive. If this default is changed during the installation of Unicenter CA-XCOM Data Transport, the default values in the XCOM.GLB file will reflect this change.

For further information on PATH and directory defaults, see the appendix “Unicenter CA-XCOM Data Transport Parameters.”

Starting Unicenter CA-XCOM Data Transport

Requirements

To use Unicenter CA-XCOM Data Transport you need the following:

Unicenter CA-XCOM Data Transport installed on your server or workstation.

For using SNA/APPC protocols, appropriate APPC communications software installed.

For using TCP/IP, TCP/IP capability installed and configured for your server or workstation.

Your Windows Username and Password.

The XCOMD Unicenter CA-XCOM Scheduler service must be started.

To edit configuration files, you need the appropriate user rights to read and write to those files.

To send a transfer using the GUI, you need the appropriate user rights to run XCOMNT.EXE and XCOMTP.EXE.

For information about installing Unicenter CA-XCOM Data Transport, see the Unicenter CA-XCOM Data Transport for Windows NT Server/Professional Getting Started. For more information about the XCOMD Unicenter CA-XCOM Scheduler service and the Unicenter CA-XCOM Data Transport operating environment, administrators should see the following chapters:

“The Command Line Interface” in this guide

“Operating Environment” in the Unicenter CA-XCOM Data Transport for Windows NT Server/Professional Administrator Guide

Starting Unicenter CA-XCOM Data Transport

Before you can use Unicenter CA-XCOM Data Transport to perform transfers, the XCOMD Unicenter CA-XCOM Scheduler service must be running. For a procedure for starting the XCOMD Unicenter CA-XCOM Scheduler service, see the Unicenter CA-XCOM Data Transport for Windows NT Server/Professional Getting Started.

You can start Unicenter CA-XCOM Data Transport for Windows NT in the same ways that you start any Windows application:

By double-clicking the program icon

By selecting Start>Programs>Unicenter CA-XCOM Data Transport on your Windows desktop

At the command prompt by typing XCOMNT and pressing ENTER.

Starting Unicenter CA-XCOM Data Transport

Note: For starting and stopping the Unicenter CA-XCOM Data Transport user interface, ERRORLEVEL has no meaning. When executing the command-line programs (xcomtcp.exe and xcom62.exe), the ERRORLEVEL indicates successful or failed processing. An ERRORLEVEL of ZERO indicates successful operation and termination. An ERRORLEVEL of NON_ZERO values indicates program processing was not successful, and that the program has terminated.

The Unicenter CA-XCOM Data Transport interface displays:

and that the program has terminated. The Unicenter CA-XCOM Data Transport interface displays: 2–4 User Guide

Using the Unicenter CA-XCOM Data Transport Main Window

Using the Unicenter CA-XCOM Data Transport Main Window

Use the Unicenter CA-XCOM Data Transport for Windows NT main window to select, create, or edit transfers. This window provides access to files and provides the ability to create, open or save transfer configurations. From here you can submit transfers to the Unicenter CA-XCOM Data Transport queue. You can add, duplicate, delete or edit transfers, save configuration files, and access the queue and the log.

save configuration files, and access the queue and the log. Main Window The Unicenter CA-XCOM Data

Main Window

The Unicenter CA-XCOM Data Transport for Windows NT main window is the beginning point for all transfers. The first time this window is displayed, it is blank. When you add or duplicate a transfer, the transfer appears in the transfer list displayed in this window.

Note: In this chapter we will refer to this window as the main window. The title bar displays Unicenter CA-XCOM Data Transport for Windows NT. In addition, when a configuration file is open, the name of the file is displayed in the title bar.

The main window provides the following functions:

Management of configuration files

Access to other windows

Using the Unicenter CA-XCOM Data Transport Main Window

From the main window you can access other windows to configure parameters for the four Unicenter CA-XCOM Data Transport transfer types:

Send File

Send Job

Send Report

Receive File

The functions and options of this window can be selected from the menu bar or from the pushbuttons on the toolbar at the top of the window.

For information about configuration files, see Using Transfer Configuration Files later in this chapter.

Considerations

Before using the main window to access a transfer you should know the values of the options you wish to edit and the particular type of action you wish to perform on the transfer. Each type of transfer operation is described later in this chapter, with suggestions about the information you may need, along with procedures for performing each type of transfer.

Procedure

To perform an action on a transfer listed in the Unicenter CA-XCOM Data Transport main window, do one of the following:

Highlight a transfer on the list and click on one of the toolbar pushbuttons.

Highlight a transfer on the list and select an action from a drop-down list on the menu bar.

Highlight a transfer on the list and double-click it to open an Edit Transfer window.

The applicable window is displayed or the applicable action is performed.

Note: To select more than one transfer, hold down the CTRL key and click on each appropriate transfer.

Using the Unicenter CA-XCOM Data Transport Main Window

Menu Bar Selections

Use the following selections and options of the menu bar to perform functions from the main window:

Selection

Options

File

The following options can be selected:

Option

Function

New

Clear the displayed Transfer List and create a new configuration file.

Open

Open a saved configuration file.

Save

Save a configuration file.

Save As

Save a configuration file under a different name.

Select all

Select all transfers from the list.

transfers

Queue

Submit all transfers that were selected from list.

transfers

Exit

Exit Unicenter CA-XCOM Data Transport.

Edit

The following options can be selected:

Option

Function

Add transfer

Add a new transfer with default parameters to the transfer list.

Duplicate

Add a copy of the selected transfer(s) to the transfer list.

transfer

Delete transfer

Delete selected transfer(s) from the transfer list.

Edit transfer

Edit the selected transfer’s parameters. This opens an Edit Transfer window for the selected transfer type.

parameters

Connect

The connect menu selection is dimmed, and does not apply to this implementation of Unicenter CA-XCOM Data Transport.

Tools

The following options can be selected:

Option

Function

Queue

Open the Queue Status window. Display the status of transfers.

manager

Log browser

Open the Log Browser window. Display the Unicenter CA-XCOM Data Transport log.

Using the Unicenter CA-XCOM Data Transport Main Window

Selection

Options

 

Global

Open the Unicenter CA-XCOM Data Transport for Windows NT Properties dialog, to access the Properties dialog pages, for modifying global defaults.

parameters

Trusted Access

Open the Unicenter CA-XCOM Data Transport for Windows NT Trusted Access user interface, from which you can set up permissions to allow Unicenter CA-XCOM Data Transport on other platforms to initiate file transfers without requiring a password.

Help

The following options can be selected:

Help Contents

Open the contents for Unicenter CA-XCOM Data Transport online help.

About

Displays information about this version of the product.

Pushbuttons

Use the following toolbar pushbuttons to perform functions from the main window. All the pushbuttons, except for Queue, can be used in place of menu bar selections.

Button

Icon

Function

Add

Add Add a new transfer with default parameters to the transfer list.

Add a new transfer with default parameters to the transfer list.

Duplicate

Duplicate Add a copy of the selected transfer(s) to the transfer list.

Add a copy of the selected transfer(s) to the transfer list.

Delete

Delete Delete selected transfers from the transfer list.

Delete selected transfers from the transfer list.

Edit

Edit Edit the selected transfer’s parameters. This opens an Edit Transfer window for the selected transfer

Edit the selected transfer’s parameters. This opens an Edit Transfer window for the selected transfer type.

Select All

Select All Select all transfers in the list.

Select all transfers in the list.

Queue

Queue submits selected transfers.

Select All Select all transfers in the list. Queue Queue submits selected transfers. 2–8 User Guide

Using Transfer Configuration Files

Button

Icon

Function

Queue

Queue Open the Queue status window and display the status of transfers.

Open the Queue status window and display the status of transfers.

Manager

Log

and display the status of transfers. Manager Log Open the Log Browser window and display the

Open the Log Browser window and display the Unicenter CA-XCOM Data Transport log.

Using Transfer Configuration Files

Unicenter CA-XCOM Data Transport uses transfer parameters stored in configuration files to manage each transfer. You can control how Unicenter CA-XCOM Data Transport performs transfers by specifying values for the parameters for each transfer. You can use a combination of default values and values you specify.

Using the GUI, you can create or open specific configuration files. You can create any number of these transfer configuration files for different transfer situations. You can edit a configuration on-screen, save it under another name and modify it for your own use, or add and delete transfers to create different configuration files. You can also simply modify the default values on-screen for a selected transfer.

Default Configuration Files

Unicenter CA-XCOM Data Transport comes with default configuration files, XCOM.GLB and XCOM.CNF, which can be modified as needed. Authority to change these files should be controlled by an Administrator.

WARNING! The parameters in the XCOM.GLB files and the values of the options on the Properties dialog pages in the GUI should only be changed by authorized Unicenter CA-XCOM Data Transport administrators. Most users will not need to change these values. The values should not be changed or deleted unnecessarily, and parameters should not be deleted from XCOM.GLB unnecessarily. If these values or parameters are deleted unnecessarily, the results are unpredictable.

Note: The installation process installs XCOM.GLB with parameters used for TCP/IP transfers. Even if you are not using TCP/IP, you should not delete these parameters from XCOM.GLB.

For information about modifying default values in XCOM.GLB using the GUI, see Using the Properties Dialog Pages in this chapter.

Using Transfer Configuration Files

Precedence of Parameter Values

The GUI uses parameter values in the following ways:

Values specified on-screen take precedence over values in open user- specified configuration files.

When using the GUI, parameter values in a user-created configuration file only take effect if the file is open.

When you save a configuration, the file is updated to include the values you have indicated on-screen.

Parameter values in the XCOM.GLB file are the global default values.

For more information about how parameter values take effect, see the chapter “Operating Environment” in the Unicenter CA-XCOM Data Transport for Windows NT Server/Professional Administrator Guide.

Modifying Options and Configurations

Each line displayed in the transfer list on the main window represents a transfer with specific parameters associated with it. Modify the options for a particular transfer by opening the appropriate Edit Transfer window.

For information about using the transfer list, see Using the Transfer List to Access and Perform Transfers later in this chapter. For information about using configuration files from the command prompt and in scripts, see the chapter “The Command Line Interface.” For information about how configuration files are edited and used from the command prompt, see Using Configuration Files in the following chapters:

“The Command Line Interface” in this guide

“Operating Environment” in the Unicenter CA-XCOM Data Transport for Windows NT Server/Professional Administrator Guide

Multiple Transfers from the GUI

You can create up to 99 transfers and save them as a single configuration file, which lets you create configurations to control multiple transfers. When you open a configuration file, the transfers are displayed on the main window.

Select multiple transfers by holding down the control key (CTRL), clicking the desired transfers to highlight them, and then clicking the Queue pushbutton.

Creating a Configuration File

Considerations