Infomover Getting Started 4_4

GETTING STARTED WITH EMC INFOMOVERP/N 300-999-123 REV D09

EMC Corporation Corporate Headquarters: Hopkinton, MA 01748-91031-508-435-1000 www.emc.com

Copyright 2000 - 2004 EMC Corporation. All rights reserved.Printed July 2004

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. Trademark Information

ii

Getting Started with InfoMover

Contents

Preface............................................................................................................................. xi Chapter 1 Introduction to EMC InfoMoverWhat Is EMC InfoMover 4.4........................................................... 1-2

Chapter 2

InfoMover File TransferIntroduction to InfoMover File Transfer....................................... 2-2 Prerequisite: EMC Solutions Enabler..................................... 2-2 Prerequisite: EMC ResourcePak Base .................................... 2-2 Data Transmission .................................................................... 2-3 InfoMover File Transfer Components........................................... 2-4 IFT Client.................................................................................... 2-4 IFT Server ................................................................................... 2-4 InfoMover File Transfer Operations.............................................. 2-5 Transfer Architecture................................................................ 2-5 Transfer Devices........................................................................ 2-5 Local and Remote Clients ........................................................ 2-6 Data Types ................................................................................. 2-8 Alternate Sources and Targets ................................................ 2-9 InfoMover File Transfer User Interface....................................... 2-11 Graphic User Interface ........................................................... 2-11 Command Line Interface ....................................................... 2-11 Privileged Management Utility ............................................ 2-13 The Non-Privileged Management Utility ........................... 2-14 InfoMover File Transfer Data Translation .................................. 2-15 InfoMover File Transfer in Clustered Environments................ 2-16 InfoMover File Transfer Security ................................................. 2-17 Standard Security Features.................................................... 2-17


iii

Contents

Internal Security Features...................................................... 2-17 InfoMover File Transfer Summary .............................................. 2-18 Where to Go Next .......................................................................... 2-19

Chapter 3

InfoMover File SystemIntroduction to InfoMover File System ........................................ 3-2 Prerequisite: EMC Solutions Enabler.................................... 3-2 InfoMover File System Mainframe Components ................ 3-3 InfoMover File System UNIX Components.......................... 3-3 Windows Components ............................................................ 3-5 InfoMover File System Data Transmission .................................. 3-6 Data Access................................................................................ 3-6 Data Types ................................................................................. 3-7 InfoMover File System UNIX Operations.................................... 3-8 Login Operations ...................................................................... 3-9 Read Operations ..................................................................... 3-10 Write Operations..................................................................... 3-10 IFS and NFS Coexistence....................................................... 3-11 IFS in Clustered Environments............................................. 3-11 InfoMover File System Windows Operations ........................... 3-12 Local Operations..................................................................... 3-12 Remote Operations................................................................. 3-13 Read Operations ..................................................................... 3-14 Write Operations..................................................................... 3-14 InfoMover File System Management.......................................... 3-16 Graphic User Interface........................................................... 3-16 Command Line Utilities ........................................................ 3-16 InfoMover File System Dataset Translation............................... 3-17 Setting Up Translation Environment ................................... 3-17 Environment Options ............................................................ 3-17 InfoMover File System SRDF Support........................................ 3-19 The SRDF Process with IFS ................................................... 3-19 SRDF Requirements for IFS .................................................. 3-20 More Information ................................................................... 3-20 InfoMover File System TimeFinder Support ............................. 3-21 InfoMover File System Server State Recovery........................... 3-21 InfoMover File System Security................................................... 3-21 Tracing and Auditing .................................................................... 3-22 The IFS Tracing Facility ......................................................... 3-22 The IFS Auditing Facility ...................................................... 3-22 InfoMover File System Summary................................................ 3-23 Where to Go Next .......................................................................... 3-24

iv


Contents

Chapter 4

Next Steps with EMC InfoMoverEMC InfoMover Components ....................................................... Other InfoMover Documentation ................................................. Information Road Maps ................................................................. InfoMover File Transfer Road Map ....................................... InfoMover File System Road Map......................................... 4-2 4-3 4-4 4-4 4-6

Appendix A

Customer SupportOverview of Detecting and Resolving Problems ...................... Troubleshooting the Problem ...................................................... Before Calling the Customer Support Center ........................... Documenting the Problem ........................................................... Reporting a New Problem ........................................................... Sending Problem Documentation ............................................... A-2 A-3 A-4 A-5 A-6 A-7

Glossary ........................................................................................................................ g-1 Index ............................................................................................................................... i-1


v

Contents

vi


Figures

2-1 2-2 2-3 3-1 3-2 3-3 3-4 3-5 4-1 4-2 A-1

IFT Transfer with Local Client .................................................................... 2-6 IFT Transfer with Remote Client ................................................................ 2-7 Alternate Sources and Targets ..................................................................... 2-9 IFS Transfer to Local UNIX Application .................................................... 3-8 IFS Transfer to Remote UNIX Application ................................................ 3-9 IFS Transfer to Local Windows Application ........................................... 3-12 IFS Transfer to Remote Windows Application ....................................... 3-13 IFS Under SRDF ........................................................................................... 3-19 InfoMover File Transfer Information Road Map ...................................... 4-4 InfoMover File System Information Road Map ........................................ 4-6 Problem Detection and Resolution Process ............................................. A-2


vii

Figures

viii


Tables

2-1 2-2 2-3 2-4 3-1 4-1

IFT CLI Commands ..................................................................................... 2-12 IFT Management Utility Tasks .................................................................. 2-14 IFT Translation Tools .................................................................................. 2-15 InfoMover Components ............................................................................. 2-18 InfoMover File System Summary ............................................................. 3-23 Installation Kit Contents ............................................................................... 4-2


ix

Tables

x


Preface

As part of an effort to improve and enhance the performance and capabilities of its product line, EMC from time to time releases revisions of its hardware and software. Therefore, some functions described in this guide may not be supported by all revisions of the software currently in use. For the most up-to-date information about product features, refer to your release notes. If a product does not function properly or does not function as described in this guide, please contact your EMC representative. Audience This document is intended for technical support personnel who install and manage the InfoMover components:

InfoMover File Transfer (IFT) InfoMover File System (IFS)

This document is also intended for administrative personnel and new users who are unfamiliar with the capabilities of the InfoMover components. Content Overview Here is a table listing where information is located in this document:Chapter or Appendix Chapter 1, Introduction to EMC InfoMover Chapter 2, InfoMover File Transfer Chapter 3, InfoMover File System Contents A brief introduction to InfoMover and its components. An overview of InfoMover File Transfer. An overview of InfoMover File System.


xi

Preface

Chapter or Appendix Chapter 4, Next Steps with EMC InfoMover Appendix A, Customer Support Glossary

Contents A list of the InfoMover kit components Road maps to the InfoMover documentation set. Essential questions that you should be prepared to answer when contacting the EMC Customer Support Center. A list of terms used in this guide.

InfoMover Documentation

In addition to this document, the following guides are provided for InfoMover:Publication InfoMover File Transfer Installation Guide InfoMover File Transfer System Administrators Guide InfoMover File Transfer Users Guide InfoMover File Transfer CLI Commands Quick Reference InfoMover File Transfer Release Notes InfoMover File System for OS/390 and z/OS Installation Guide InfoMover File System for OS/390 and z/OS System Administrators Guide InfoMover File System for OS/390 and z/OS Users Guide InfoMover File System Commands Quick Reference InfoMover File System for OS/390 and z/OS Release Notes InfoMover File System for OS/390 and z/OS Agent Guide Part Number 300-000-451 300-999-125 300-999-126 300-000-112 300-999-124 300-000-452 300-999-121 300-999-122 300-000-454 300-999-260 300-000-942

Conventions Used in this Document

EMC uses the following conventions for notes:Text marked Note:, Important:, Tip:, Background:, or More Information: calls attention to any item of information that may be of special importance.

xii


Preface

Typographical Conventions This document uses the following typographical conventions:Typeface AVANTGARDE SMALLCAPS Sans Serif Bold Uses Keystrokes Selections you can make from windows, including menu items and field entries Names of CLI commands or utilities used in text New terms or unique word usage in text Emphasis in text Variables in a software syntax (non-literal notation) Command-line arguments when used in text Book titles in text Heading titles used as references in text System output File names Complete paths Command-line entries

Bold Italic

Courier

Courier bold Courier italic

User entry in examples Options in command-line syntax Arguments used in examples of command-line syntax Variables in examples of screen or file output Variables in path names

Terminology This document uses IBM mainframe host or mainframe host to refer to an IBM mainframe host, and uses OS/390 and z/OS to refer to the IBM family of operating systems.


xiii

Preface

Where to Get Help

For questions about technical support call your local sales office or service provider. If you have a valid EMC service contract, contact EMC Customer Service at: United States: (800) 782-4362 (SVC-4EMC) Canada: Worldwide: (800) 543-4782 (543-4SVC) (508) 497-7901

Follow the voice menu prompts to open a service call and select the applicable product support. Sales and Customer Service Contacts For the list of EMC sales locations, please access the EMC home page at: http://emc.com/contact/ For additional information on the EMC products and services available to customers and partners, refer to the EMC Powerlink Web site at: http://powerlink.emc.com Your Comments Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Please send a message to [email protected] with your opinions of this guide. Your technical enhancement suggestions for future development consideration are welcome. To send a suggestion, log on to http://powerlink.emc.com, follow the path Support, Contact Support, and choose Software Product Enhancement Request from the Subject menu.

xiv


1Invisible Body Tag

Introduction to EMC InfoMover

This chapter presents an introduction to EMC InfoMover 4.4 and its suite of components. The topic of this chapter is:

What Is EMC InfoMover 4.4.............................................................1-2


1-1


1

What Is EMC InfoMover 4.4Some of the most critical tasks in any business are those of:

Sharing information among functional groups Migrating large amounts of data from one location to another Archiving data for regulatory and legal purposes

EMC InfoMoverTM 4.4 allows your business to perform all of these tasks. InfoMover is a tool for moving and sharing data among hosts:

Within a data center Across a business campus Over extended distances

InfoMover 4.4 is a suite of components, each of which has its own version number. The following table shows the InfoMover 4.4 components and their version numbers:InfoMover Component InfoMover File Transfer InfoMover File System IFS Enabler a EMC Solutions Enabler kit b EMC ResourcePak Base kit c Version 3.7 2.6 6.3 5.4 5.4

a. IFS Enabler is a prerequisite for InfoMovers InfoMover File System on all hosts. The IFS Enabler component on mainframe hosts is the IFS Agent. The IFS Enabler component on open systems hosts is an API library. b. EMC Solutions Enabler is a prerequisite for InfoMovers InfoMover File Transfer and InfoMover File System on UNIX and Windows NT, Windows 2000, and Windows Sever 2003 hosts. For more information about EMC Solutions Enabler, refer to Prerequisite: EMC Solutions Enabler on page 2-2 or Prerequisite: EMC Solutions Enabler on page 3-2. c. EMC ResourcePak Base is a prerequisite for InfoMover File Transfer on mainframe hosts and for the InfoMover File System Agent. For more information about EMC ResourcePak Base, refer to Prerequisite: EMC ResourcePak Base on page 2-2 and InfoMover File System Mainframe Components on page 3-3.

The following chapters discuss InfoMover File Transfer and InfoMover File System.

1-2


Invisible

2InfoMover File Transfer

This chapter discusses the InfoMover File Transfer component. Topics include:

Introduction to InfoMover File Transfer.........................................2-2 InfoMover File Transfer Components.............................................2-4 InfoMover File Transfer Operations................................................2-5 InfoMover File Transfer User Interface......................................... 2-11 InfoMover File Transfer Data Translation ....................................2-15 InfoMover File Transfer in Clustered Environments ..................2-16 InfoMover File Transfer Security ...................................................2-17 InfoMover File Transfer Summary ................................................2-18 Where to Go Next ............................................................................2-19

InfoMover File Transfer

2-1


2

Introduction to InfoMover File TransferInfoMover File Transfer (IFT) is a file-transfer technology. IFT allows you to copy data bidirectionally among any number of IBM mainframe, UNIX, and Windows hosts connected to a Symmetrix storage subsystem. The transferred file or dataset must reside on host disks or other attached storage. On UNIX hosts, you can also transfer to and from named pipes.

Prerequisite: EMC Solutions Enabler

EMC Solutions Enabler is a prerequisite for installing InfoMovers IFT component on UNIX and Windows hosts. EMC Solutions Enabler provides a host using IFT with a SymmAPI shared library. IFT uses this shared library to obtain configuration, status, and performance data from Symmetrix storage subystems. If you do not already have EMC Solutions Enabler installed on each open systems host that will use InfoMover File Transfer, you need to install it as a preparatory step to installing IFT. An EMC Solutions Enabler kit is shipped along with your InfoMover kit.More Information: Refer to the EMC Solutions Enabler Installation Guide (provided with the Solutions Enabler software) for more information about installing EMC Solutions Enabler.

Prerequisite: EMC ResourcePak Base

EMC ResourcePak Base is a prerequisite for installing IFT on OS/390 and z/OS hosts. If you do not have EMC ResourcePak Base installed on each mainframe host that will use InfoMover File Transfer, you need to install it as a preparatory step to installing IFT. An EMC ResourcePak Base kit is shipped with your InfoMover kit.More Information: Refer to the EMC ResourcePak Base for OS/390 and z/OS Product Guide (provided with the ResourcePak Base software) for more information about installing EMC ResourcePak Base.

2-2



2

Data Transmission

In data transmission, IFT can use the following types of Symmetrix channel connections:

ESCON FICON SCSI Ultra SCSI Fibre Channel

Because IFT transmits data through these high-speed channels instead of through a general-purpose network, IFT is especially suited to moving bulk data. Other methods frequently cause network congestion, overload, slowdown, or even shutdown.

Introduction to InfoMover File Transfer

2-3


2

InfoMover File Transfer ComponentsThe primary components of InfoMover File Transfer are:

IFT client IFT server

IFT Client

You make file transfer requests through the IFT client. The IFT client specifies the file or dataset to be accessed, the source file, and the path to which the data is to be transferred, the target file. The IFT client can reside on:

IBM mainframe (OS/390 or z/OS) hosts that also have a resident IFT server UNIX hosts with either a resident IFT server or TCP/IP access to an IFT server on a remote UNIX or Windows host Windows hosts with either a resident IFT server or TCP/IP access to an IFT server on a remote UNIX or Windows host

IFT Server

An IFT server must reside on every host from which and to which files are to be transferred. The IFT server processes the file transfer request from the IFT client and performs the actual file transfer. The components of the IFT server are:

The initiator, which responds to IFT client requests The connector, which responds to initiator requests

2-4



2

InfoMover File Transfer OperationsThe following sections describe how InfoMover File Transfer performs transfer operations.

Transfer Architecture

You can use IFT to transfer files between any two supported hosts. IFT transfers data from local storage on one host to a file or named pipe (UNIX only) on the other host through IFT transfer devices on the Symmetrix storage subsystem common to both hosts. When you set up an IFT implementation, you dedicate some of the devices on your Symmetrix system as transfer devices. The transfer devices provide disk space for buffering and transporting the data during file transfer. Transfer devices must be fixed block architecture (FBA) devices and be configured to be accessible by all hosts that are to participate in data transfer. The transfer devices can be:

Transfer Devices

Spread across multiple logical volumes (as perceived by the host) Located on a single volume

IFT can support up to 32 sets of transfer devices per Symmetrix storage subsystem for open systems and 8 sets for mainframes.

InfoMover File Transfer Operations

2-5


2Local and Remote ClientsThe client controlling a transfer can be on the same host as one of the servers involved in the transfer, as shown in Figure 2-1:Host A

Client

SUNLINK

Server

Source File

Symmetrix

Transfer Devices

Cache

Host B

Server

Target File

Figure 2-1

IFT Transfer with Local Client

In Figure 2-1, the client on host A is transferring a file on host A to host B. The client takes the following steps: 1. The client on host A sends the necessary file information to the server on host A. 2. The server on host A reads the file, the source file, from a count-key-data (CKD) formatted device on the Symmetrix storage subsystem.

2-6



2

3. The server on host A then writes the file data to a transfer device, where the data is cached. 4. The server on host B reads the data from cache while the server on host A continues to write data to the transfer device. 5. The server on host B writes the data to the designated location, the target file. The client can also be on a remote host connected to one of the server hosts through TCP/IP, as shown in Figure 2-2:Host C Host B

SUNLINK

SUNLINK

Client

Server

Source File

Symmetrix

Transfer Devices

Cache

Host A

Server

Target File

Communication and Control Path Data Path

Figure 2-2

IFT Transfer with Remote Client


2-7


2In Figure 2-2 on page 2-7, the client on host C is transferring a file on host B to host A. The client takes the following steps: 1. The client on host C sends the necessary file information to the server on host B. 2. The server on host B reads the source file from a count-key-data (CKD) formatted device on the Symmetrix storage subsystem. 3. The server on host B then writes the file data to a transfer device, where the data is cached. 4. The server on host A reads the data from cache while the server on host B continues to write data to the transfer device. 5. The server on host A writes the data to the designated location, the target file. Remote clients can reside only on UNIX or Windows hosts. A remote client on a UNIX or Windows host can connect to a server on any supported UNIX or Windows host.

Data Types

IFT can transmit both binary and text data. When transmitting between dissimilar hosts (for example, IBM mainframe to UNIX) or between open systems hosts, IFT can translate single-byte text data from the format of the sending host to the format of the receiving host. IFT can transfer the following types of mainframe datasets:

Physical sequential (PS) datasets with the following record formats: Fixed (F) Fixed block (FB) Variable (V) Variable block (VB) Variable block spanned (VBS) Undefined (U)

Partitioned dataset (PDS) members and directories Generation datasets (GDS) Sequential datasets on magnetic tape Members of generation datasets on magnetic tape

For physical sequential datasets and generation datasets, IFT supports reading multiple volume datasets.

2-8



2

IFT cannot use the following types of mainframe datasets as sources and targets on mainframe platforms:

UNIX System Services (USS) files under the Hierarchical File System (HFS) Files with embedded bitmaps or packed decimal data in text (or translation) mode Striped datasets for newly allocated target datasets VSAM datasets

Alternate Sources and TargetsIFT supports transfers of files from and to alternate sources, as shown in Figure 2-3:CLARiiONOS/390 and z/OS tape

Windows Host

IBM Mainframe Host

Symmetrix

CacheNamed pipe

UNIX Host

SUNLINK

JBOD

Connectrix/DS16B

SUNLINK

Open System Hosts

Figure 2-3

Alternate Sources and Targets


2-9


2As Figure 2-3 on page 2-9 shows, you can copy files to or from:

CLARiiON storage systems IBM mainframe magnetic tape Other storage devices, referred to in Figure 2-3 as JBOD 1 UNIX named pipes

In addition, IFT allows full Fibre Channel switching support through ConnectrixTM and DS16B.

1. JBOD, just a bunch of disks, refers to a set of hard disks that have not been configured into a storage system to improve data-access and increase fault tolerance.

2-10



2

InfoMover File Transfer User InterfaceInfoMover File Transfer has:

A graphic user interface (GUI) A command line interface (CLI) A privileged Management Utility A non-privileged Management Utility

Graphic User Interface

The graphic user interface (GUI) is available on the following operating systems:

Windows NT Windows 2000 Windows Server 2003

More Information: Refer to the InfoMover File Transfer System Administrators Guide for a list of the operating system versions supported.

You use the GUI to transfer files, using the familiar tools of windows, panels, pull-down menus, combo boxes, and radio buttons. You can also use the GUI to create batch scripts to perform regularly scheduled transfers. Keep in mind that, although you can run the GUI interface only on Windows clients, you can use the GUI interface to transfer files from any IFT server on any supported platform.Important: The IFT GUI requires the Java Runtime Environment, which is part of the Java 2 Standard Edition. Before you can use the GUI, you, or someone at your site, must download and install the Java 2 Standard Edition 1.4 or higher on your Windows system.

Command Line Interface

The command line interface (CLI) is available on the following operating systems:

OS/390 z/OS Solaris (Available on both Sun and Fujitsu platforms.) AIX HP-UXInfoMover File Transfer User Interface2-11


2

Red Hat Enterprise Linux Tru64 UNIX DYNIX/ptx UNIX_SV, SRV4 MP-RAS Windows NT Windows 2000 Windows Server 2003

On AIX hosts, EMC PowerPath is a prerequisite for IFT. This means that you should install any currently supported version of PowerPath before you use IFT on an AIX host.More Information: Refer to the InfoMover File Transfer Installation Guide for a list of the exact operating system versions supported.

The command line interface consists of a series of FTP-like commands. These commands allow you to perform many of the transfer and translation operations available through the graphic user interface. There are three basic types of commands:

Mainframe-specific commands that let you specify the allocation parameters you want to apply to data you are transferring to or from the mainframe Commands that allow you to specify how you want file translation between an host types to proceed Commands that duplicate the functionality of FTP commands

Table 2-1 shows the CLI commands supported in IFT:Table 2-1

IFT CLI Commands Mainframe-Specific Commands blksize imaddlf imbufno imcylinder imdirblocks imfilenumber imrdw Open-System Specific Commands imcrlf imlog imrecvx imsendx imwrap

FTP-Like Commands binary (bin) cd close connect delete dir get

2-12



2

Table 2-1

IFT CLI Commands (continued) Mainframe-Specific Commands imrelease imtrail likedsn lrecl lsp recfm unit unitcount volcount Open-System Specific Commands

FTP-Like Commands mget help imxlate lcd lpwd ldir open put mput pwd quit replace status upper verbose

You run the batch scripts you create in the GUI through the CLI interface. You can also write your own batch scripts and run them through the CLI.

Privileged Management Utility

The IFT Management Utility, imManager (or IMMANAGE on mainframes) provides access to functions listed in this section. You can access the IFT Management Utility from any system on which the IFT transfer devices reside through a privileged (superuser or Administrator) account. You can run IFT Management Utility through

An interactive interface Batch jobs/background scripts

InfoMover File Transfer User Interface

2-13


2The IFT Management Utility allows you to perform the tasks shown in Table 2-2:Table 2-2

IFT Management Utility Tasks Task Format transfer devices Explanation Format Symmetrix volumes that are designated as the transfer disks to prepare them for use with the server and client software. Formatting establishes the control and data transfer buffers on the Symmetrix storage subsystem according to parameters in the configuration file. Formatting can be done by any host configured in the IFT instance. Display the status of all connections between respective IFT servers in an IFT instance as well as the status of current transfers. Display raw device names, Symmetrix logical device number, shared access port, and Symmetrix serial number. Create a new configuration file or modify an existing configuration file. Convert existing IFT scripts, and update them with encrypted passwords in all environments. Manage log output, manage error message lookup, and display configuration parameters.

Monitor connection status

Display information about Symmetrix devices Create or modify configuration files Encrypt passwords for IFT scripts Handle other administrative tasks

The Non-Privileged Management Utility

IFT also has a non-privileged Management Utility for users of non-privileged accounts. The non-privileged Management Utility is a subset of the privileged Management Utility. The non-privileged Management Utility allows non-privileged users to create transfer scripts or encrypt the passwords in transfer scripts created through the IFT GUI.

2-14



2

InfoMover File Transfer Data TranslationIFT can transmit data in both binary mode and text mode. In binary mode, IFT transfers the entire dataset or file byte-for-byte without character translation. You can use binary mode to transfer any type of file, including packed decimal or embedded packed decimal. In text mode, IFT transfers data in ASCII or EBCDIC format. If the data is moving between different types of hosts (mainframe to open systems or open systems to mainframe), IFT can translate the data from:

ASCII to EBCDIC EBCDIC to ASCII

By default, IFT performs translation for text mode transfers on the local host that initiates the transfer, unless that transfer is between an open systems host and a mainframe host. In open systems to mainframe transfers, IFT, by default, performs translation on the open systems host, no matter which host initiated the transfer. However, IFT provides tools through the IFT configuration file and the IFT CLI interface that let you perform translation on either the local or the remote host involved in a transfer, even if the host you select is a mainframe in a mainframe-to-open-systems transfer. These tools include those shown in Table 2-3:Table 2-3

IFT Translation Tools Tool imXlateDir configuration parameter Use Designates where the IFT server and IFT Management utility should look for translation tables.

imXlate_local_rem Designates where IFT is to perform character translation if the client does not specify the host in the imxlate CLI command. ote configuration parameter recvXlateFile configuration parameter sendXlateFile configuration parameter Designates the default character translation table for received data.

Designates the default character translation table for sent data from this host.

InfoMover File Transfer Data Translation

2-15


2Table 2-3

IFT Translation Tools (continued) Tool binary CLI command imrdw CLI command imrecvx CLI command imsendx CLI command imtrail CLI command imwrap CLI command imxlate CLI command Use Specifies that subsequent transfers will be in binary mode, byte-by-byte, without translation. Use to enable or disable retention of record/span descriptor words (RDWs and SDWs) in V, VS, and VBS format source datasets. Use to specify the single-byte translation table for subsequent get operations (overriding the default single byte translation table specified in the configuration file). Use to specify the single byte translation table for future put commands (overriding the default single byte translation table specified in the configuration file). Use to enable or disable retention of the trailing blanks in an OS/390 or z/OS source dataset during subsequent transfers. Use to enable or disable the wrapping of UNIX or Windows file lines to fit dataset logical record length on transferal to mainframes. Use to enable or disable single-byte character translation during subsequent transfers and specify whether translation is to take place on the local or remote hosts.

These tools allow you to perform translation on the most efficient processor and in the most efficient way for your environment.

InfoMover File Transfer in Clustered EnvironmentsIFT can exist in a Sun Cluster or Tru64 Cluster environment. (That is, IFT is Sun Cluster and Tru64 Cluster tolerant.) However, IFT cannot exploit the features of clustering in these environments.

2-16



2

InfoMover File Transfer SecurityIFT uses the standard security features of UNIX, Windows, and IBM mainframe systems. IFT also provides internal security that allows you to prevent unauthorized access to files and datasets.

Standard Security Features

On IBM mainframe, Windows, and UNIX systems, IFT requires a username and password to be entered for a valid account when establishing a connection to a remote host (server). IFT also verifies that a client has permission to perform remote or local dataset/file access. In a mainframe environment, IFT uses the System Authorization Facility (SAF) interface for access and resource authorization. This interface, which is part of the mainframe operating system, is compatible with the IBM Security Server/Resource Access Control Facility (RACF) and the External Security Manager packages (CA-Top Secret and CA-ACF2) available from Computer Associates, Inc. If an installation does not have one of these security packages, IFT bypasses security altogether. In an open systems environment, IFT uses already established usernames and passwords, or those established just for IFT purposes.When starting an IFT client on a mainframe system, you have the option of either:

Using the TSO logon user identity/JCL batch USERID, supplied by TSO or BATCH mode Entering another valid USERID and password for establishing a connection to the local host

Internal Security Features

IFT has several internal features that help you maintain security. First, IFT allows you to encrypt input passwords through the IFT Management Utility so that scripts and batch job input are protected from accidental or intentional disclosure of passwords. Second, IFT allows you to prevent all users, or selected users, from copying files or datasets to or from a host computer. To do so, you set configuration parameters to prevent specified users or all users from executing gets or puts from or to that host.

InfoMover File Transfer Security

2-17


2

InfoMover File Transfer SummaryTable 2-4 summarizes InfoMover File Transfer features:Table 2-4

InfoMover Components Component Task Interface Supported Operating Systems a InfoMover File Transfer File Transfer Command line interface OS/390 z/OS AIX DYNIX/ptx HP-UX UNIX_SV, SRV4 MP-RAS Red Hat Enterprise Linux Solaris Tru64 UNIX Windows NT Windows 2000 Windows Server 2003 Graphic User Interface Windows NT Windows 2000 Windows Server 2003

Moves data from

OS/390 and z/OS datasets on local host devices Open-systems files on local host devices Named pipes on UNIX hosts OS/390 and z/OS datasets on tapes OS/390 and z/OS datasets on local host devices Open-systems files on local host devices Named pipes on UNIX hosts OS/390 and z/OS datasets on tapes Getting Started with InfoMover InfoMover File Transfer Release Notes InfoMover File Transfer Installation Guide InfoMover File Transfer System Administrators Guide InfoMover File Transfer Users Guide InfoMover File Transfer CLI Quick Reference

Moves data to

Applicable documents

a. Refer to the InfoMover File Transfer Installation Guide or the InfoMover File Transfer System Administrators Guide for a list of supported versions of each operating system.

2-18



2

Where to Go NextThe previous discussion is only a brief introduction to IFT. Refer to the description of the IFT-specific documentation in the Information Road Maps on page 4-4. This road map describes where to go for more information about IFT and its capabilities.

Where to Go Next

2-19


2

2-20


Invisible Body Tag

3InfoMover File System

This chapter discusses the InfoMover File System component. Topics include:

Introduction to InfoMover File System...........................................3-2 InfoMover File System Data Transmission ....................................3-6 InfoMover File System UNIX Operations ......................................3-8 InfoMover File System Windows Operations..............................3-12 InfoMover File System Management ............................................3-16 InfoMover File System Dataset Translation .................................3-17 InfoMover File System SRDF Support..........................................3-19 InfoMover File System TimeFinder Support ...............................3-21 InfoMover File System Server State Recovery.............................3-21 InfoMover File System Security.....................................................3-21 Tracing and Auditing ......................................................................3-22 InfoMover File System Summary ..................................................3-23 Where to Go Next ............................................................................3-24

InfoMover File System

3-1


3

Introduction to InfoMover File SystemInfoMover File System (IFS) is a file-sharing technology. IFS provides open systems users with a transparent, native, file system interface to IBM mainframe catalogs and datasets. IFS is a high speed, open systems, file system interface to mainframe data. IFS allows applications on UNIX or Windows hosts to read data from and write data to OS/390 or z/OS catalogs and datasets stored on CKD devices in a Symmetrix storage subsystem which both the IBM mainframe and UNIX or Windows host address. IFS also allows application on UNIX and Windows hosts to read data from and write data to OS/390 or z/OS catalogs that are:

Stored on CKD devices in a Symmetrix storage subsystem addressed by the mainframe, but not addressed by the client host Stored on non-Symmetrix CKD volumes addressed by the mainframe, but not addressed by the client host

Through IFS, IBM mainframe data appears as if it were ordinary open systems directories and files. As with IFT, IFS uses the Symmetrix systems high-speed channels to minimize the impact on your network. IFS can have components on the following types of hosts:

Mainframes (OS/390 or z/OS) UNIX Windows

Prerequisite: EMC Solutions Enabler

EMC Solutions Enabler is a prerequisite for installing InfoMovers IFS component on UNIX and Windows hosts. EMC Solutions Enabler provides a host using IFS with a SymmAPI shared library that IFT uses to obtain configuration, status, and performance data from Symmetrix systems. If you do not already have EMC Solutions Enabler installed on each open systems host that will use InfoMover File Transfer, you need to install it as a preparatory step to installing IFS. An EMC Solutions Enabler kit is shipped along with your InfoMover kit.

3-2



3

More Information: Refer to the EMC Solutions Enabler Installation Guide (provided with the Solutions Enabler software) for more information about installing EMC Solutions Enabler.

InfoMover File System Mainframe Components

The IFS component on mainframe hosts is the Agent. The Agent manages file access and security. The IFS Agent:

Ensures data integrity Provides catalog and directory services Provides dataset management services Provides I/O services in some environments Verifies and authenticates potential users.

The Agent is required for IFS operation. That is, you must install and configure the Agent before you can use IFS. The Agent has its own install media and manual, the InfoMover File System for OS/390 and z/OS Agent Guide.Note: To install and configure the Agent, follow the steps outlined in the InfoMover File System for OS/390 and z/OS Agent Guide.

Prerequisite: EMC ResourcePak Base

EMC ResourcePak Base is a prerequisite for installing the IFS Agent on OS/390 and z/OS hosts. If you do not have EMC ResourcePak Base installed on each mainframe host that will use InfoMover File System, you need to install it as a preparatory step to installing the IFS Agent. An EMC ResourcePak Base kit is shipped with your InfoMover kit.More Information: Refer to the EMC ResourcePak Base for OS/390 and z/OS Product Guide (provided with the ResourcePak Base software) for more information about installing EMC ResourcePak Base.

InfoMover File System UNIX Components

IFS on UNIX is available on the following operating systems:

Solaris 1 AIX HP-UX

1. Available on both Sun and Fujitsu platforms.

Introduction to InfoMover File System

3-3


3

UNIX_SV, SRV4 MP-RAS Tru64 UNIX Red Hat Enterprise Linux

On AIX hosts, EMC PowerPath is a prerequisite for IFS. This means that you should install any currently supported version of PowerPath before you use IFS on an AIX host.More Information: Refer to the InfoMover File System for OS/390 and z/OS System Administrators Guide for a complete list of prerequisites and for a list of the operating system versions supported.

The IFS is implemented as:

An IFS client An IFS server A collection of IFS utilities

The IFS Client

The client receives data-sharing requests from application users and relays them to the server. The client resides either on the same host on which the server resides or a remote host connected to the server host by TCP/IP. On UNIX hosts, the client is a variant of the NFS (Network File System) client included on all UNIX systems. The IFS client is designed to allow applications to access datasets as they would ordinary NFS or local UNIX File System (UFS) files.

The IFS Server

The server receives requests from the client and communicates them through the TCP/IP network to the Agent on the mainframe. The IFS server on UNIX hosts is a Network File System (NFS) server that receives requests from NFS clients. Because the IFS server complies with NFS protocol, it appears to NFS clients as an ordinary NFS server. IFS, however, differs from traditional NFS in that the files - datasets - it exports come from mainframe hosts rather than from UNIX hosts. The datasets must be stored on Symmetrix CKD devices to which both the UNIX host and the mainframe host share access.

The IFS Utilities

IFS on UNIX provides a collection of utilities to assist you with standard file-movement operations and configuration management.

3-4



3

Windows Components

IFS on Windows is available on Windows NT, Windows 2000, and Windows Server 2003. On Windows hosts, IFS is implemented as:

An IFS client An IFS server A collection of IFS utilities

The IFS Client

The IFS client receives data requests from user programs and sends those requests to the IFS server. On Windows hosts, the nature of the client depends on whether the client is on the same system with the server or on a remote system. If the client is on the same system as the server, the client is the IFS File System Driver (IFS FSD). If the client is on a system that is remote from the server, client requests have to go through Microsoft's Common Internet File System (CIFS) redirector and the CIFS server to reach the File System Driver.

The IFS Server

The IFS server receives requests from IFS File System drivers and communicates them through the TCP/IP network to the Agent. The IFS server then reads the OS/390 or z/OS data and sends them to the client. As with UNIX, applications can access OS/390 or z/OS datasets as they would local or networked Windows files. Again, the datasets must be stored on Symmetrix CKD devices.

The IFS Utilities

IFS on Windows also provides a collection of utilities to assist you with standard file read operations and with configuration management. These utilities are a subset of the utilities available for IFS on UNIX.

Introduction to InfoMover File System

3-5


3

InfoMover File System Data TransmissionIFS communicates with mainframe hosts over TCP/IP. Both hosts communicate with the Symmetrix system through channel connections. The mainframe host and the common Symmetrix system can use any of the following types of Symmetrix channel connections:

ESCON FICON

The UNIX and Windows hosts and the common Symmetrix system can use any of the following:

Fast Wide SCSI Ultra SCSI Fibre Channel

IFS transmits data through these high-speed Symmetrix channels, instead of through a general-purpose network. This makes IFS especially suited to the movement and sharing of bulk data. Potential applications for IFS include:

Catalog and dataset browsing using standard UNIX tools such as Web browsers, graphic file interfaces, and shell commands Data filtering, cleaning, and report generation using third-party vendor or standard UNIX or Windows tools Database and data-warehouse loading

Data Access

IFS does not require transfer devices. Because the data on which IFS operates is stored on a shared Symmetrix system, IFS is able to read or write the data directly from the dataset on the Symmetrix system or vendor device to the requesting application.

3-6



3

Data Types

IFS provides read access to the following types of datasets:

Generation datasets (GDS) Multivolume datasets Partitioned dataset (PDS) members and directories Physical sequential (PS) datasets VSAM 1 entry sequenced datasets (ESDS) VSAM key sequenced datasets (KSDS) VSAM linear datasets (LDS)Important: KSDS .index datasets can only be read in binary mode. KSDS .data datasets cannot be read by IFS.

IFS provides write access to the following dataset types:

Generation dataset (GDS) Physical sequential (PS) datasets

With the exception of partitioned datasets, datasets can consist of extents on multiple volumes. IFS does not support read/write operations with the following types of datasets:

Datasets with ASA control characters (datasets with a RECFM of VA, VBA, FA, FBA, and so forth) 2 VSAM relative record datasets (RRDS) Partitioned datasets extended (PDS/E) Physical sequential extended datasets (PS/E) Any extended VSAM (VSAM/E) datasets 3

1. Virtual storage access method. 2. Unsupported for text mode write. 3. For example, VSAM/E KSDS, VSAM/E ESDS, and so forth.

InfoMover File System Data Transmission

3-7


3

InfoMover File System UNIX OperationsYou must mount IFS through NFS. After you mount IFS, you can use readily-available, plug-and-play applications or your own programs to read from and write to mainframe datasets. If the application resides locally, on the same host as the IFS file server, the data acquisition process is as shown in Figure 3-1:

Nonshared Storage

MainframeSource File

Agent

Symmetrix Shared Storage

Source File

TCP/IP Netwo rk

ApplicationSUNLINK

UNIX

NFS Client

IFS Server


Figure 3-1

IFS Transfer to Local UNIX Application

3-8



3

If the application resides remotely, on a separate UNIX host connected by TCP/IP, the data transmission process is as shown in Figure 3-2:

Nonshared StorageSource Files

Mainframe HostAgent

Symmetrix Shared StorageSource Files

TCP/IP NetworkSUNLINK

Application

UNIX HostNFS Client

UNIX HostIFS Server

SUNLINK

TCP/IP Network


Figure 3-2

IFS Transfer to Remote UNIX Application

Login Operations

A local or remote application on a UNIX system logs into IFS by providing a user ID and password recognized by the mainframe host. IFS sends the encrypted login data over the TCP/IP network to the Agent on the mainframe. The Agent, in turn, uses the Secure Access Facility (SAF) to validate the user credentials. If your site has a security package such as CA-ACF2, CA-TopSecret, or IBM RACF running, IFS validates the user through that package. IFS then ties the UNIX system and the OS/390 or z/OS identities together in an encrypted form for the length of the UNIX/IFS session. This enables multiple connections on the same login.

InfoMover File System UNIX Operations

3-9


3Read OperationsWhen the local or remote UNIX application needs to read data to OS/390 or z/OS datasets, it sends a command for the IFS server to open a specified dataset. The IFS server then sends the command through TCP/IP to the Agent on the mainframe host. If file permissions match and the dataset is valid, the Agent sends catalog information to the IFS server. Using that information, IFS then reads the data from the Symmetrix storage subsystem to the local or remote application. The default mode for reading data is as text. When reading text data, IFS performs the following actions:

Translates each byte from EBCDIC to ASCII format Adds a new line character to the end of each record Binary data Raw data

However, IFS on UNIX can also read:

When reading binary data, IFS reads the data to the open system application byte-for-byte without character translation. IFS can read any type of file, including packed decimal or embedded packed decimal. IFS does not add new line characters at the end of each record. When reading raw data, IFS transfers binary format data along with block, record, and segment description words. IFS does not add new line characters at the end of each record.

Write Operations

When the local or remote UNIX application needs to write data to OS/390 or z/OS datasets, it sends a command to the IFS server. The IFS server then sends the command through TCP/IP to the Agent on the mainframe host. If file permissions match and the dataset is valid, the Agent sends catalog information to the IFS server. Using that information, IFS writes the data from the local or remote application to the CKD devices on the Symmetrix storage subystem. The default mode for writing data is as text. When writing text data, IFS performs the following actions:

Translates each byte from ASCII to EBCDIC format Translates new lines into record boundaries

3-10



3

In addition, IFS on UNIX can also write any type of binary data including packed decimal or embedded packed decimal. IFS writes the binary data byte-for-byte without character translation and without adding new line characters at the end of each record.

IFS and NFS Coexistence

On Solaris, NCR, and AIX platforms, IFS and NFS severs can co-exist on the same host. That is, NFS operations and IFS operations do not affect each other. On HP-UX and Tru64, IFS and NFS servers cannot co-exist on the same host because of operating system restrictions.

IFS in Clustered Environments

IFS can exist in a Sun Cluster environment. (That is, IFS is Sun Cluster tolerant.) However, IFS cannot exploit the features of clustering.

InfoMover File System UNIX Operations

3-11


3

InfoMover File System Windows OperationsIFS on Windows can only read data from mainframe hosts. The read operations performed depend on whether the application making the request is on the same host as the IFS FSD and the IFS server.

Local Operations

If the application resides locally on the same host as the IFS server, the data acquisition process is as shown in Figure 3-3:


Mainframe HostAgent

Symmetrix Shared Storage

Source Files

TCP/IP Network

Application

Windows Host

IFS FSD

IFS Server


Figure 3-3

IFS Transfer to Local Windows Application

As Figure 3-3 shows, applications running on a local host, the same host as an IFS FSD and IFS server, communicate directly with the FSD. The FSD then communicates with the IFS server. The IFS server in turn communicates with the Agent through TCP/IP. The application on a Windows host performs a login in the same way as does a UNIX application. (Refer to Login Operations on page 3-9.) After the Agent has verified the login data, IFS can request to read or write mainframe data.

3-12



3

Remote Operations

If the application resides remotely on a different host from the IFS file server, the data acquisition process is as shown in Figure 3-4:


Mainframe HostAgent

Symmetrix Shared StorageSource Files

TCP/IP NetworkApplication

Windows HostCIFS Server

Windows HostCIFS Redirector IFS FSD

IFS Server

TCP/IP Network


Figure 3-4

IFS Transfer to Remote Windows Application

As Figure 3-4 shows, applications running on a remote host communicate with the IFS FSD through the CIFS (Common Internet File System) redirector and CIFS server. CIFS is a standard protocol that lets programs make requests for files and services on remote computers on the Internet. The CIFS redirector and server are standard Windows networking components that redirect traffic across the network. After receiving a request from a remote application, the FSD communicates directly with the IFS server. The IFS server in turn communicates with the Agent through TCP/IP.

InfoMover File System Windows Operations

3-13


3The application on a Windows host performs a login in the same way as does a UNIX application. (Refer to Login Operations on page 3-9.) After the Agent has verified the login data, IFS can request to read or write OS/390 or z/OS data.

Read Operations

When the local or remote Windows application needs to read data to OS/390 or z/OS datasets, it sends a command for the IFS server to open a specified dataset. The IFS server then sends the command through TCP/IP to the Agent on the mainframe host. If file permissions match and the dataset is valid, the Agent sends catalog information to the IFS server. Using that information, IFS then reads the data from the Symmetrix to the local or remote application. The default mode for reading data is as text. When reading text data, IFS performs the following actions:

Translates each byte from EBCDIC to ASCII format Adds a new line character to the end of each record Binary data Raw data

However, IFS on UNIX can also read:

When reading binary data, IFS reads the data to the open system application byte-for-byte without character translation. IFS can read any type of file, including packed decimal or embedded packed decimal. IFS does not add new line characters at the end of each record. When reading raw data, IFS transfers binary format data along with block, record, and segment description words. IFS does not add new line characters at the end of each record.

Write Operations

When the local or remote Windows application needs to write data to OS/390 or z/OS datasets, it sends a command to the IFS server. The IFS server then sends the command through TCP/IP to the Agent on the mainframe host. If file permissions match and if the dataset resides on a Symmetrix storage subsystem shared by the mainframe host and the IFS servers host, the Agent sends catalog information to the IFS server. Using that information, IFS writes the data from the local or remote application to the CKD devices on the Symmetrix storage subsystem.

3-14



3

The default mode for writing data is as text. When writing text data, IFS performs the following actions:

Translates each byte from ASCII to EBCDIC format Translates new lines into record boundaries

In addition, IFS on Windows can also write any type of binary data including packed decimal or embedded packed decimal. IFS writes the binary data to the Windows application byte-for-byte without character translation and without adding new line characters at the end of each record.

InfoMover File System Windows Operations

3-15


3

InfoMover File System ManagementIFS has two interfaces:

A graphic user interface (GUI) A collection of command line utilities

Graphic User Interface

The GUI, ifsmgr, is available on Solaris and HP-UX only. You use the ifsmgr to configure and administer the IFS server. Before you use ifsmgr, you must install a Java 2 environment. Java packages for HP-UX and Solaris are available from HP and Sun web sites, respectively. The command line utilities are available on all supported hosts. The command line utilities are commands that you can execute at the system prompt or include in script files. These commands allow you to perform the following tasks:

Command Line Utilities

Control IFS administrative functions Start and stop the IFS server List login credentials Log in to and out of an IFS server Mount an IFS or NFS file system Control tracing (Refer to The IFS Tracing Facility on page 3-22.)

3-16



3

InfoMover File System Dataset TranslationInfoMover gives an IFS user the option of sharing text files among IBM mainframe, UNIX, and Windows systems either with or without character translation. If you want to share file data without translation, you can use the binary mode in which data is transferred byte-by-byte. If you want to share file data with translation, you can share file data using the text mode in which the shared data is translated between ASCII and EBCDIC. You can translate the data using:

The IFS default ASCII-EBCDIC translation tables The alternative IFS single-byte character translation tables Your own custom translation tables

Setting Up Translation Environment

You control character translation through settings in the IFS configuration file and through the use of IFS operator commands. IFS uses the file translation tables to translate the source file data and the protocol translation tables to translate the protocol data necessary for server-to-server communications such as:

Passwords Server names Source filename Target filename User IDs

For data sent and received, you can specify the same or different translation tables for file and protocol translation.

Environment Options

The following translation options are available to a user:

Use the IS_XLATE_DFLT environment variable to specify the default ASCII - EBCDIC translation tables. These tables are the default setting when IFS is first installed. The ASCII - EBCDIC translation tables convert ASCII-to-EBCDIC or EBCDIC-to-ASCII using a single-byte, English language, ASCII translation table.

InfoMover File System Dataset Translation

3-17


3

Use the IS_XLATE_DIR environment variable to specify the directory containing the customized translation table files. You can specify your own file and protocol translation tables. Such translation tables must be text files containing a 256-byte hexadecimal representation of the translation table, comma delimited.

3-18



3

InfoMover File System SRDF SupportYou can use Symmetrix Remote Data Facility 1 (SRDF ) with IFS. Figure 3-5 shows the architecture of IFS under SRDF:Mainframe Host UNIX or Windows Host

Mainframe Application

Application Local Symmetrix Remote Symmetrix NFS Client or File System Driver

Catalog security and allocation services R1 Shared CKD volume SymmAPI-Access Agent R2 Shared CKD volume IFS

SRDF Link

IFS Enabler

TCP/IP Connection for Security and Control

Figure 3-5

IFS Under SRDF

SRDF provides data mirroring between two physically-separated Symmetrix systems to ensure the continuous availability of data during an outage. The Symmetrix systems can be in the same room or separated by extended distances. If the Symmetrix storage subystem is part of an SRDF configuration, IFS can read data from either the target (R2) volumes or the source (R1) volumes, provided the link between the volumes is physically and logically active.

The SRDF Process with IFSIFS performs the following steps when used with SRDF: 1. After you perform an IFS login, IFS starts a TCP/IP connect between the library on the open systems host and the Agent on the mainframe host.

1. SRDF allows two or more Symmetrix systems to be connected to each other, permitting logical disks from one Symmetrix system to be mirrored at high speed onto logical disks in another Symmetrix system.

InfoMover File System SRDF Support

3-19


32. The Agent contacts the mainframe security system to ensure that the user ID and password given at IFS login are correct and that the user has access rights to the dataset. 3. The Agent also communicates with the mainframe catalog and I/O services to locate the dataset on the R1 device in the local Symmetrix system. 4. After the dataset is located, the Agent uses the mainframe enqueue rules to enqueue the file. 5. The Windows or UNIX system then accesses the dataset over its SCSI or Fibre channels.

SRDF Requirements for IFSThe following are requirements you need to take into account when you use IFS over SRDF:

Your mainframe dataset must reside on or be moved to SRDF volumes. You must set up the R2 volume as a shared volume. The links between the R1 and R2 volumes must be physically and logically active. All tracks on the R2 volume must be valid.

More InformationRefer to the EMC Symmetrix Remote Data Facility (SRDF) Product Guide. Contact your EMC customer support representative for more information about using IFS with SRDF.

3-20



3

InfoMover File System TimeFinder SupportYou can also use EMC TimeFinder with IFS. If the Symmetrix system is part of a TimeFinder configuration, IFS can read data from a mirrored volume that has been recataloged. Before you use IFS to read data, use a TimeFinder utility to change the mirrored volume serial number (volser).More Information: For more information about TimeFinder, refer to the EMC Solutions Enabler Symmetrix TimeFinder CLI Product Guide for open systems or the TimeFinder/Mirror Product Set for OS/390 and z/OS Product Guide for mainframe systems. Contact your EMC customer support representative for more information about using IFS with TimeFinder.

InfoMover File System Server State RecoveryIFS on both UNIX and Windows offers server state recovery. When you restart IFS after the host has come down, IFS automatically reestablishes file system connections and other state information.

InfoMover File System SecurityOn UNIX, and Windows systems, IFS requires that a user name and password for a valid account both for logging into the local host operating system and for logging into the IFS server when establishing a connection to a remote host. On the mainframe, when run as a started task, the IFS Agent must operate with security system (such as Security Server/RACF) defined user credentials.

InfoMover File System TimeFinder Support

3-21


3

Tracing and AuditingIFS has both:

A tracing facility An auditing facility

The IFS Tracing Facility

The IFS Trace facility is a useful tool in helping to diagnose program errors. It allows you to create trace files that record IFS activity (and the activity of its underlying components) during the execution of an application program. The IFS Trace facility has three tracing components:

IFS tracing - to provide tracing of IFS level events IFS Enabler tracing - to provide tracing of IFS enabler events IFS Agent tracing - to provide tracing from the Agent host

Through IFS utilities, the IFS configuration file, and configuration variables, you can specify what elements you want traces to capture.

The IFS Auditing Facility

The IFS Audit facility allows you to track security and data access events. The Audit facility is supported on UNIX systems only. When you enable the auditing facility, the Audit facility records all login, logout, open, close, rename, remove, and access checks in the audit file. The Audit facility creates a new file each day. These files are retained by IFS until you explicitly delete or move them.

3-22



3

InfoMover File System SummaryTable 3-1 summarizes the InfoMover File System features:Table 3-1

InfoMover File System Summary Component Task Interface InfoMover File System File Data Sharing Command Line Interface AIX HP-UX UNIX_SV, SRV4 MP-RAS Solaris Tru64 UNIX Windows NT Windows 2000 Windows Server 2003 Graphic User Interface

Supported Operating Systems a

Solaris HP-UX

Moves data from Moves data to Applicable documents

OS/390 and z/OS datasets on Symmetrix systems OS/390 and z/OS datasets on Symmetrix systems Getting Started with InfoMover InfoMover File System Release Notes InfoMover File System for OS/390 and z/OS Installation Guide InfoMover File System for OS/390 and z/OS Agent Guide InfoMover File System for OS/390 and z/OS System Administrators Guide InfoMover File System for OS/390 and z/OS Users Guide InfoMover File System Commands Quick Reference

a. Refer to the Infomover File System for OS/390 and z/OS Installation Guide or the InfoMover File System for OS/390 and z/OS System Administrators Guide for a list of supported versions of each operating system.

InfoMover File System Summary

3-23


3

Where to Go NextThe discussion in the previous sections is only a brief introduction to IFS. Refer to the description of the IFS-specific documentation in the Information Road Maps on page 4-4 for more information about IFS and its capabilities.

3-24


Invisible Body Tag

4Next Steps with EMC InfoMover

This chapter describes the next steps to take with InfoMover. Topics include:

EMC InfoMover Components..........................................................4-2 Other InfoMover Documentation....................................................4-3 Information Road Maps ....................................................................4-4

Next Steps with EMC InfoMover

4-1


4

EMC InfoMover ComponentsYour first step in using InfoMover is to unpack the installation kit. Table 4-1 shows the contents of the InfoMover installation kit:Table 4-1

Installation Kit Contents Item InfoMover Software Compact Disc (CD) InfoMover File Transfer Software 3480 Tape InfoMover File System Agent Software 3480 Tape Printed InfoMover Documentation Kit Contains The software you need to install IFT, IFS, and the IFS Enabler on UNIX and Windows hosts. The software you need to install IFT on OS/390 or z/OS hosts. The software you need to install the IFS agent on OS/390 or z/OS hosts. The following printed documents: Getting Started with EMC InfoMover InfoMover File Transfer Release Notes InfoMover File Transfer Installation Guide InfoMover File Transfer CLI Commands Quick Reference InfoMover File System for OS/390 and z/OS Release Notes InfoMover File System for OS/390 and z/OS Installation Guide InfoMover File System for OS/390 and z/OS Agent Guide InfoMover File System Commands Quick Reference Media and documentation for Solutions Enabler. You must install EMC Solutions Enabler on each open systems host on which you are planning to use InfoMovers IFT or IFS components. Media and documentation for ResourcePak Base. You must install EMC ResourcePak Base on each mainframe system on which you are planning to install IFT or the IFS Agent for IFS.

EMC Solutions Enabler Kit

EMC ResourcePak Base Kit

4-2



4

Other InfoMover DocumentationInfoMover also provides the following documents:

InfoMover File Transfer System Administrators Guide InfoMover File Transfer Users Guide InfoMover File System for OS/390 and z/OS System Administrators Guide InfoMover File System for OS/390 and z/OS Users Guide

These documents are provided in Adobe Acrobat Portable Documentation (PDF) format on the EMC Powerlink website: http://powerlink.emc.com The Powerlink website is available to EMC customers. To retrieve these InfoMover documents, log in to Powerlink and follow the path Support, Documentation Library, Software, InfoMover.

Other InfoMover Documentation

4-3


4

Information Road MapsThe following sections show where specific information about IFT or IFS is located in the hardcopy documents supplied with the InfoMover kit or the soft copy documents available through Powerlink.

InfoMover File Transfer Road Map

Figure 4-1 shows the road map to the InfoMover File Transfer documentation:


InfoMover File Transfer Release Notes

Install and configure

Manage in daily use

Transfer data

InfoMover File Transfer Installation Guide

InfoMover File Transfer System Administrators Guide

InfoMover File Transfer Users Guide

Look up CLI command syntaxInfoMover File Transfer CLI Commands Quick Reference

Figure 4-1

InfoMover File Transfer Information Road Map

4-4



4

The following table describes the IFT documents in more detail:If you want to learn about InfoMover as a whole learn the latest information about InfoMover File Transfer learn how to install and configure the IFT component learn how to manage the IFT component read Getting Started with EMC InfoMover InfoMover File Transfer Release Notes which contains an overview of InfoMover a list of IFT features and important information discovered after the rest of the documentation set was produced IFT installation and configuration procedures a detailed overview of IFT information about how to start and stop the server, and client information about managing IFT information about translation files and error messages host-specific considerations a usage-oriented overview of IFT a description of how to use the GUI interface a description of how to use the CLI interface a list of current error messages a description of how to use IFT on OS/390 or z/OS hosts a synopsis of all the IFT CLI commands and their parameters

InfoMover File Transfer Installation Guide InfoMover File Transfer System Administrators Guide

learn how to use IFT to transfer data

InfoMover File Transfer Users Guide

look up IFT CLI commands and their syntax

InfoMover File Transfer CLI Commands Quick Reference

Information Road Maps

4-5


4InfoMover File System Road MapFigure 4-2 shows the road map to the InfoMover File System documentation:


InfoMover File System for OS/390 and z/OS Release Notes

Install and configureInfoMover File System for OS/390 and z/OS Agent Guide

Manage in daily useInfoMover File System for OS/390 and z/OS System Administrators Guide

Transfer dataInfoMover File System for OS/390 and z/OS User's Guide

Look up command syntaxInfoMover File System for OS/390 and z/OS Installation Guide

InfoMover File System Commands Quick Reference

Figure 4-2

InfoMover File System Information Road Map

4-6



4

The following table describes the IFS documents in more detail:If you want to learn about InfoMover as a whole learn latest information about InfoMover File System learn how to install, configure, and manage the Agent read Getting Started with EMC InfoMover InfoMover File System for OS/390 and z/OS Release Notes InfoMover File System for OS/390 and z/OS Agent Guide which contains an overview of InfoMover a list of IFS features and important information discovered after the rest of the documentation set was produced an overview of the Agent a description of how to install the Agent a description of how to configure the Agent a detailed overview of IFS a description of how to install and configure the IFS server a description of how to install and configure the NFS client a discussion of the file system issues a discussion of security issues a usage-oriented overview of IFS a description of how to log in and out of the IFS server a discussion of OS/390 or z/OS file structures a description of error messages and troubleshooting a synopsis of all the IFS commands and their parameters

learn how to install, configure, and manage the IFS component

InfoMover File System for OS/390 and z/OS System Administrators Guide

learn how to use IFS to access files

InfoMover File System for OS/390 and z/OS Users Guide

look up IFS commands and their syntax

InfoMover File System Commands Quick Reference

Information Road Maps

4-7


4

4-8


nvisible Body Tag

ACustomer Support

This appendix reviews the EMC process for detecting and resolving software problems, and provides essential questions that you should answer before contacting the EMC Customer Support Center. This appendix covers the following topics:

Overview of Detecting and Resolving Problems .........................A-2 Troubleshooting the Problem ..........................................................A-3 Before Calling the Customer Support Center ...............................A-4 Documenting the Problem...............................................................A-5 Reporting a New Problem ...............................................................A-6 Sending Problem Documentation...................................................A-7

Customer Support

A-1

Customer Support

A

Overview of Detecting and Resolving ProblemsEMC software products are supported directly by the EMC Customer Support Center in the United States. EMC uses the following process to resolve customer problems with its software products (Figure A-1).

Problem Detection

Refer to this Customer Support Appendix for Instructions

Collect Problem Information as Directed

Contact the EMC Customer Support Center: (800) SVC-4EMC U.S.: Canada: (800) 543-4SVC Worldwide: (508) 497-7901

Confirm that the Problem is Software Related

Call will be Directed to an EMC Software Support Engineer

Problem is Tracked and Managed to Resolution

Figure A-1

Problem Detection and Resolution Process

A-2


Customer Support

A

Troubleshooting the ProblemPlease perform the relevant diagnostic steps before you contact the EMC Customer Support Center: 1. Read the documentation carefully. 2. Reconstruct the events leading up to the problem and describe them in writing. 3. Run some test cases to reproduce the problem. If you encounter a problem that requires technical programming or analysis, call the nearest EMC office or contact the EMC Customer Support Center at one of the following numbers: United States: Canada: Worldwide: (800) 782-4362 (SVC-4EMC) (800) 543-4782 (543-4SVC) (508) 497-7901

Please do not request a specific support representative unless one has already been assigned to your particular system problem.

For additional information about EMC products and services available to customers and partners, refer to the EMC Powerlink website at:http://powerlink.emc.com

Troubleshooting the Problem

A-3

Customer Support

A

Before Calling the Customer Support CenterHave the following information available before calling the Customer Support Center or your support representative (if one has been assigned to you): Your company name Your name Your phone number For an existing problem, the problem tracking system ID, if one was previously assigned to the problem by a support representative For a mainframe problem, the JESLOG, SYSPRINT, all STDOUT DD members of the server job output and similar output for the client, and the relevant portion of the SYSLOG

A-4


Customer Support

A

Documenting the ProblemIf the EMC Customer Support Center requests information regarding the problem, please document it completely, making sure to include the following information: Your company name and address Your name Your telephone number The importance of the problem, so that it can be assigned a priority level To expedite the processing of your support request, you can photocopy this list and include it with the package.

Documenting the Problem

A-5

Customer Support

A

Reporting a New ProblemFor a new problem, please provide the following information: Release level of the software that you are running Software installation parameters Host type on which you are running Operating system you are running and its release number Functions of the software that you are running Whether you can reproduce the problem Previous occurrences of the problem Whether the software has ever worked correctly Time period that the software did work properly Conditions under which the software worked properly Changes to your system between the time the software worked properly and the problem began Exact sequence of events that led to the system error Message numbers and complete text of any messages that the system produced Log file dated near the time the error occurred Results from tests that you have run Other related system output Other information that may help solve the problem

A-6


Customer Support

A

Sending Problem DocumentationUse one of the following methods to send documentation of the problem to the EMC Customer Support Center:

E-mail FTP U.S. mail to the following address: EMC Customer Support Center 171 South Street Hopkinton, MA 01748-2208 If the problem was assigned a number or a specific support representative, please include that information in the address as well.

Sending Problem Documentation

A-7

Customer Support

A

A-8


Glossary

This glossary contains terms related to the InfoMover product. Many of these terms are used in this guide.

AAgent (IFS) The server address space that executes on one or more OS/390 and z/OS images in a computing complex. It provides services to an application program, including protection of data integrity, user verification and authentication, and catalog and dataset control information. See also client. (IFS) The job step task of the Agent job. Only one Agent task exists, and it is responsible for starting all other tasks in the Agent address space. A set of routines that an application program uses to request and execute tasks performed by a computers operating system.

Agent task

application programming interface (API) ASCII audit file

American Standard Code for Information Interchange. (IFS) A file that records security events. (For example, log in attempts, file access, and so on) logged by an IFS server.

Bbidirectional transfers (IFT) Also called duplex transfers. A bidirectional transfer is one in which data can be transferred simultaneously in both directions. If there is a single IFT client, that client can do both gets and puts.Getting Started with InfoMoverg-1

Glossary

Ccache Random-access electronic storage used to retain frequently used data for faster access by the channel. A repository containing information about datasets stored on a mainframe host. It is synonymous with a directory on UNIX or Windows host. noun - An application program that uses data or services provided over the network by another program, usually referred to as a server. adjective - Describes attributes related to the environment in which a application runs. common internet file system (CIFS) command line interface (IFS) A distributed file system access protocol supported by Microsoft operating systems. Analogous to NFS in the UNIX world. Also referred to as CLI. An interface that to IFT and IFS that allows you to set up and control shared access and non-shared access file transfer. The command line interface has a series of commands (and parameters) that perform various tasks. (IFT) A functional subtask in an IFT server. The connector accepts and processes any file transfer requests from an initiator subtask in the same server or in a different server. See also initiator. A data recording format used by mainframe computers. Another data recording format, FBA, is used by open systems computers. See also Fixed Block Architecture. CKD employs self-defining record formats in which each record is represented by a count area that identifies the record and specifies its format, an optional key area that may be used to identify the data area contents, and a data area that contains the user data for the record. CKD can also refer to a set of channel commands that are accepted by a device that employs the CKD recording format.

catalog

client

connector

count key data (CKD)

g-2


Glossary

DDASD Direct access storage device. A storage device that provides nonvolatile storage of computer data and random access to that data. It is analogous to an open systems hard disk. In a mainframe system, a collection of data in one of several prescribed arrangements and described by control information in the volume label and/or the catalog. A dataset may be equivalent to a file in some cases, as in physical sequential files, or several datasets may make up the components of a file. See also partitioned dataset (PDS) and partitioned dataset extended (PDSE). The name of a mainframe dataset. A DSN consists of a series of dot-delimited qualifiers, each of which comprising a maximum of eight characters (e.g., PAYROLL.DSN1.ESDS). A DSN has a maximum of 44 characters. When referencing the member of a partitioned dataset, the maximum length is 54 bytes, including 44 bytes for the name of the PDS, and up to eight bytes for the member name, enclosed in parentheses. A general term referring to a storage device. In the Symmetrix subsystem, a device corresponds to a single device visible to the host. See also Volume. A uniquely addressable part of the Symmetrix subsystem that consists of a set of access arms, the associated disk surfaces, and the electronic circuitry required to locate, read, and write data.

dataset

dataset name (DSN)

device

disk

EEBCDIC ESCON Extended Binary Coded Decimal Interchange Code. Enterprise Systems Connection. A fibre-based specification for connecting IBM mainframes with disk storage devices. It is analogous to SCSI in the open systems world. A continuous block of storage space on a disk that is occupied by or reserved by the mainframe operating system for a particular dataset, data space, file, or program.

extent


g-3

Glossary

eyecatcher

(IFS) A string of characters that can be visually identified quickly. It is commonly used in memory-resident structures where most of the user data is difficult to decipher in a dump file. It catches the eye so a person reading large amounts of hexadecimal memory can better understand what is being looked at. InfoMover File System places eyecatchers in SMF records so that they visually mark important record sections.

FFibre Channel A high speed serial interface capable of data transfer rates of up to 100 megabytes per second. FICON (Fiber Connectivity) is a high-speed I/O interface for mainframe computer connections to storage devices. FICON channels increase I/O capacity to make them up to eight times as efficient as ESCON channels. In OS/390 and z/OS, a file is an abstraction that represents a collection of data at the application level. In some cases, such as physical sequential files, a dataset and a file may be considered equivalent. I

Documents

Infomover Getting Started 4_4