home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 3 Comm
/
03-Comm.zip
/
tt2man.zip
/
ttftran.doc
< prev
next >
Wrap
Text File
|
1993-12-10
|
31KB
|
819 lines
TABLE OF CONTENTS
9. File Transfer
9.1 Screen Capture
9.2 Ascii
9.3 Compuserv B+
9.4 XModem/YModem/ZModem
9.4.1 Overview
9.4.2 Procedures
9.5 IBM IND$FILE
9.5.1 Introduction
9.5.2 Procedures From Terminal Emulation
9.5.2.1 Sending A PC File To The Host
9.5.2.2 Receiving A PC File From The Host
9.5.3 Procedures From An OS/2 Session
9.5.3.1 File Transfer Commands
9.5.4 VM/CMS Specific Requirements
9.5.4.1 VM/CMS Command Format
9.5.4.2 VM/CMS Positional Parameters
9.5.4.3 VM/CMS Optional Parameters
9.5.5 TSO Specific Requirements
9.5.5.1 TSO Command Format
9.5.5.2 TSO Positional Parameters
9.5.5.3 TSO Optional Parameters
9.5.6 CICS Specific Requirements
9.5.6.1 CICS Command Format
9.5.6.2 CICS Positional Parameters
9.5.6.3 CICS Optional Parameters
9.5.7 IND$FILE Problem Resolution
9.5.7.1 General
9.5.7.2 Release Incompatibilities
9.5.7.3 Common Error Messages
9.5.7.4 Tips To Correcting File Transfer Errors
9.6 Kermit
9. File Transfer
9.1 Screen Capture
The most basic of file transfer techniques is the Capturing of host screen
data as it arrives on the PC. TalkThru supports capturing this data both
to text files or to the Printer. Screen Capture is requested from the
Terminal Emulation Window by selecting Capture from the File pull down menu
or by using the Left MOUSE Button and clicking on the word Capture on the
Status Line.
Once a Capture File has been established, Screen Capture can be toggled ON
and OFF by using the Left MOUSE Button and clicking on the word Capture on
the Status Line. If Screen Capture is ON, the word Capture will be in Bold
Black. If Screen Capture is OFF, the word Capture will be in light gray.
9.2 Ascii
TalkThru supports Ascii File Transfer both to a host and from a host.
Since Ascii File Transfer IS NOT error correcting, it is used when no other
file transfer mechanisms are available or when the only way to place data
into a host application (i.e. an Editor or Word Processor) is to enter the
data directly on the screen. Ascii Upload is the process of requesting
that an existing PC File be sent to the host as if it were keystrokes being
entered at the terminal. Ascii Download is very much like Screen Capture
in that it merely takes any data that appears on the Terminal Emulation
Window and places it in a file.
To perform an Ascii Upload:
1. Place the data you wish to have entered on the host screen into a PC
file.
2. Position the host application to receive the data on the application
screen where it can be typed in.
3. Request Send file and then Ascii from the File pull down menu on the
Terminal Emulation Window.
4. Select the PC file containing the data you want entered on the
application screen.
The data from the PC file will be entered on the host application screen as
if it were quickly typed on the keyboard.
Ascii Download works in the opposite manner. To perform an Ascii Download:
1. Position the host application on a screen where you can request that the
data to be downloaded be listed on the Terminal Emulation Window.
2. Request Receive file... and then Ascii from the File pull down menu on
the Terminal Emulation Window.
3. Indicate the PC file to receive the data being displayed on the Terminal
Emulation Window.
4. Return to the Terminal Emulation Window and request that the data to be
downloaded be displayed on the screen. The data will continue to be
displayed on the Terminal Emulation Window as it is being placed in the
PC file.
5. When the data has completed being displayed, press the Stop Receive push
button on the Ascii Receive dialog window.
9.3 Compuserv B+
Compuserv B+ File Transfer is used solely in conjunction with the Compuserv
Bulletin Board. To request the Compuserv B+ File Transfer, request Send
file or Receive file... and then Compuserv B+ from the File pull down menu
on the Terminal Emulation Window.
9.4 XModem/YModem/ZModem
┌────────────────┐
│ 9.4.1 Overview │
└────────────────┘
The following XModem, YModem and ZModem protocols are supported by
TalkThru:
XModem - CRC
is the standard XModem file transfer with CRC error checking.
XModem - Checksum
is the standard XModem file transfer with Checksum error checking.
XModem - 1K
is a single file protocol that is essentially XModem CRC with 1024 byte
packets. It requires 8 data bits.
XModem - 1KG
is the same as XModem - 1K except that it does not provide software
error detection or recovery -- it is designed for use with error
correcting modems.
YModem
this the same as XModem - 1K except that it allows multiple files to be
sent in one transfer. Filenames can be unique or contain the standard
wildcard characters * and ?.
YModem - G
is the same as YModem except that it does not provide software error
detection or recovery -- it is designed for use with error correcting
modems.
ZModem
is the standard ZModem file transfer.
┌──────────────────┐
│ 9.4.2 Procedures │
└──────────────────┘
From a TalkThru Terminal Emulation Window, you invoke XModem and YModem
file transfer as follows:
1. position your host session on the proper screen
2. request the host to begin the file transfer process
3. select Send File or Receive File from the File pull down menu
4. select the appropriate file transfer from the File Transfer Protocol
dialog
5. indicate the OS/2 or host file name to be created by this file transfer
During the file transfer process, a status dialog will appear.
WARNING:
Once the file transfer is complete, the Status will be updated to
indicate Complete, but the dialog will not go away until you press
Enter.
9.5 IBM IND$FILE
┌────────────────────┐
│ 9.5.1 Introduction │
└────────────────────┘
TalkThru will SEND or RECEIVE files communicating directly with the IBM
IND$FILE program on a VM/CMS, TSO, or CICS host.
The following sections provide the procedures for performing IND$FILE
File Transfer requests in the environments in which it is supported.
WARNING:
The TalkThru versions of the IBM SEND and RECEIVE commands are
called TT2SEND.EXE and TT2RECV.EXE respectively. This is so that
there will be no naming conflicts if you utilize TalkThru and 3270
Sessions on the same workstation. If you are only going to use
IND$FILE File Transfer while within TalkThru asynchronous sessions,
you may rename these modules to SEND.EXE and RECEIVE.EXE if you
wish. They are present in the directory pointed to by the TalkThru
PROGRAMS_DIRECTORY Customization Variable.
┌──────────────────────────────────────────┐
│ 9.5.2 Procedures From Terminal Emulation │
└──────────────────────────────────────────┘
┌───────────────────────────────────────┐
│ 9.5.2.1 Sending A PC File To The Host │
└───────────────────────────────────────┘
If you wish to send a PC File to the host utilizing IND$FILE, perform
the following steps:
1. Logon to the IBM CMS, TSO, or CICS system you wish to receive the
file.
2. Position yourself on a host screen which will accept the IND$FILE
File Transfer command.
3. Request Send file from the File pull down menu on the Terminal
Emulator window.
From this pull down menu, request the IND$FILE which matches your host
environment and press Enter.
The dialog that appears allows you to specify the PC and Host file names
for the transfer. Press F1 or the Help push button to obtain more
information on each of the fields on this window. You may also refer to
the IBM documentation on IND$FILE for more detailed information.
Notice that the default PC Data Directory is the TalkThru
DATA_DIRECTORY. You may change this if you wish by providing the full
file specification in the PC File dialog.
Once you enter the file names and press Enter, the following will occur:
1. The Terminal Emulator window will be minimized on the bottom of the
Desk Top.
2. A status screen will appear indicating the progress of the transfer.
If you minimize the status screen, it will appear as an Icon on the
bottom of the Desk Top, but will continue to provide status on the
message line.
Once the file transfer is complete, the File Transfer window (or Icon)
will beep to inform you that a message is waiting and, once maximized,
will cancel itself and maximize the Terminal Emulation Window.
┌───────────────────────────────────────────┐
│ 9.5.2.2 Receiving A PC File From The Host │
└───────────────────────────────────────────┘
If you wish to Receive a PC File from the host utilizing IND$FILE,
perform the following steps:
1. Logon to the IBM CMS, TSO, or CICS system you wish to receive the
file.
2. Position yourself on a host screen which will accept the IND$FILE
File Transfer command.
3. Request Receive file from the File pull down menu on the Terminal
Emulator window.
From this dialog request the IND$FILE which matches your host
environment and press Enter.
Depending upon you Host Environment, you will now see a dialog similar
The dialog that appears allows you to specify the PC and Host file names
for the transfer. Press F1 or the Help push button to obtain more
information on each of the fields on this window. You may also refer to
the IBM documentation on IND$FILE for more detailed information.
Notice that the default PC Data Directory is the TalkThru
DATA_DIRECTORY. You may change this if you wish by providing the full
file specification in the PC File dialog.
Once you enter the file names and press Enter, the following will occur:
1. The Terminal Emulator window will be minimized on the bottom of the
Desk Top.
2. A status screen will appear indicating the progress of the transfer.
If you minimize the status screen, it will appear as an Icon on the
bottom of the Desk Top, but will continue to provide status on the
message line.
Once the file transfer is complete, the File Transfer window (or Icon)
will beep to inform you that a message is waiting and, once maximized,
will cancel itself and maximize the Terminal Window.
┌───────────────────────────────────────┐
│ 9.5.3 Procedures From An OS/2 Session │
└───────────────────────────────────────┘
You can request IND$FILE File Transfer from any OS\2 Session prompt or
from an OS/2 Command File once you have positioned the Host Session to a
screen that will accept a file transfer request.
┌────────────────────────────────┐
│ 9.5.3.1 File Transfer Commands │
└────────────────────────────────┘
The following two commands are distributed with TalkThru to perform
IND$FILE File Transfer:
TT2SEND - This command will transfer a PC File to the Host.
TT2RECV - This command will transfer a Host File to the PC.
┌────────────────────────────────────┐
│ 9.5.4 VM/CMS Specific Requirements │
└────────────────────────────────────┘
┌───────────────────────────────┐
│ 9.5.4.1 VM/CMS Command Format │
└───────────────────────────────┘
The basic command format is:
┌──────────────────────────────────────────────────────────────────────┐
│ TT2SEND/TT2RECV filespec [session-id:] filename filetype filemode │
│ ( options │
└──────────────────────────────────────────────────────────────────────┘
A sample of the TT2RECV command would be:
TT2RECV a:report.dat a: report script a (CRLF ASCII
┌──────────────────────────────────────┐
│ 9.5.4.2 VM/CMS Positional Parameters │
└──────────────────────────────────────┘
filespec
The name of the PC File. If the PC Name DOES NOT include disk and
directory information, the file will be placed in the directory
specified by the DATA_DIRECTORY Customization Variable.
session-id:
This is the EHLLAPI session id of the TalkThru Terminal Emulator
session connected to the host environment. It MUST be followed by
a colon (:).
filename
The VM/CMS File Name. This can be up to 8 characters in length.
filetype
The VM/CMS File Type. This is a required positional parameter for
TT2SEND. It is an optional parameter for TT2RECV. If it is not
specified, it will default to "*".
filemode
The VM/CMS File Mode. This is an optional positional parameter. If
this parameter is omitted, the default for TT2SEND is "A" and the
default for TT2RECV is "*".
┌────────────────────────────────────┐
│ 9.5.4.3 VM/CMS Optional Parameters │
└────────────────────────────────────┘
The following optional parameters must be separated from the last
positional parameter by a left parenthesis.
ASCII
With TT2SEND, ASCII causes data translation from ASCII to
EBCDIC. With TT2RECV, ASCII causes data translation from EBCDIC
to ASCII. The default is NO TRANSLATION.
CRLF
Specifying CRLF will maintain record level integrity in both
directions. With TT2SEND, Carriage Return Line Feeds will be
eliminated but will trigger normal end of record. With TT2RECV,
Carriage Return Line feeds will be appended at end of record
locations. The default is no CRLF.
APPEND
Causes the file being transferred to be added to the end of the
target file.
LRECL n
Valid for TT2SEND only. It provides a logical record length for
the host file records.
If an existing host file is being replaced, its record length is
used as the record length of the new version of the replaced
file except if LRECL is provided in this parameter list.
When LRECL is specified for a file which is being replaced, the
specified values override the former record length of the file.
If the APPEND option is specified, the current record length of
the file is used and the LRECL value specified is ignored.
The default for LRECL is 80.
RECFM F/V
Valid for TT2SEND only. This specifies the recording mode to use
for the host file.
F = Fixed Length
V = Variable Length
The default is F, unless the CRLF option is also specified, in
which case V is the default.
┌─────────────────────────────────┐
│ 9.5.5 TSO Specific Requirements │
└─────────────────────────────────┘
┌────────────────────────────┐
│ 9.5.5.1 TSO Command Format │
└────────────────────────────┘
The basic command format is:
┌──────────────────────────────────────────────────────────────────────┐
│ TT2SEND/TT2RECV filespec │
│ [session-id:]dsname(member)/password optio ns │
└──────────────────────────────────────────────────────────────────────┘
A sample of the TT2RECV command would be:
TT2RECV abc.txt a: reports(abc) ASCII
┌───────────────────────────────────┐
│ 9.5.5.2 TSO Positional Parameters │
└───────────────────────────────────┘
filespec
The name of the PC File. If the PC Name DOES NOT include disk and
directory information, the file will be placed in the directory
specified by the DATA_DIRECTORY Customization Variable.
session-id:
This is the EHLLAPI session id of the TalkThru Terminal Emulator
session connected to the host environment. It MUST be followed by
a colon (:).
dsname
The TSO File Name. This can be up to 44 characters in length.
member
This is a required positional parameter for Partitioned Data Sets
(PDS). The PDS must exist before a TT2SEND command can occur.
/password
Optional parameter allowing access to password protected Physical
Sequential or Partitioned Data Sets.
┌─────────────────────────────────┐
│ 9.5.5.3 TSO Optional Parameters │
└─────────────────────────────────┘
The following optional parameters are valid for TT2SEND and TT2RECV
commands. They are separated from the rest of the command and from each
other by a space.
ASCII
With TT2SEND, ASCII causes data translation from ASCII to
EBCDIC. With TT2RECV, ASCII causes data translation from EBCDIC
to ASCII. The default is NO TRANSLATION.
CRLF
Specifying CRLF will maintain record level integrity in both
directions. With TT2SEND, Carriage Return Line Feeds will be
eliminated but will trigger normal end of record. With TT2RECV,
Carriage Return Line feeds will be appended at end of record
locations. The default is no CRLF.
APPEND
Causes the file being transferred to be added to the end of the
target file.
The following optional parameters are only valid for TT2SEND commands
and the Data Set is Physical Sequential.
LRECL(n)
Provides a logical record length for the host file records.
In the case of RECFM U or V, this is the maximum record size
expected.
If a file is being replaced, or if the APPEND option is
specified, LRECL MUST NOT be specified. In this case, the old
LRECL is utilized.
The default LRECL for RECFM F or U is 80, for RECFM V, 84,
except under the APPEND conditions itemized above.
BLKSIZE(n)
Provides the desired block size for the Host File.
The default for BLKSIZE is LRECL for new files and is ignored
for APPEND or replace.
RECFM(F,V,U)
Specifies the recording mode to use for the Host File.
F = Fixed Length
V = Variable Length
U = Undefined Record Type
The default is F, unless the CRLF option is also specified, in
which case V is the default.
SPACE(q,i)
Specifies the amount of space to be allocated for a new Host
File.
q
- the number of units of space to be added to the Data Set each
time the previously allocated space has been filled.
i
- the number of units (increment) of space to be allocated
initially for a Data Set. This parameter is required if the
SPACE parameter is provided.
The default is SPACE(10,50).
AVBLOCK(n)
This is only valid if SPACE is also provided. This specifies the
average block length for the output Data Set.
TRACKS
This is only valid if SPACE is also specified. This specifies
that the unit of space is to be by track.
CYLINDERS
This is only valid if SPACE is also specified.
NOTE:
The AVBLOCK, TRACKS, and CYLINDERS parameters are mutually
exclusive. The host will reject the request if more than one is
specified. If none of them are specified, the BLKSIZE parameter will
be used as the unit value for SPACE.
┌──────────────────────────────────┐
│ 9.5.6 CICS Specific Requirements │
└──────────────────────────────────┘
┌─────────────────────────────┐
│ 9.5.6.1 CICS Command Format │
└─────────────────────────────┘
The basic command format is:
┌──────────────────────────────────────────────────────────────────────┐
│ TT2SEND filespec [session-id:]fn ( options ) comments │
│ │
│ TT2RECV filespec [session-id:]fn ( options │
└──────────────────────────────────────────────────────────────────────┘
A sample of the TT2RECV command would be:
TT2RECV abc.txt a: myfile ( ASCII
┌────────────────────────────────────┐
│ 9.5.6.2 CICS Positional Parameters │
└────────────────────────────────────┘
filespec
The name of the PC File. If the PC Name DOES NOT include disk and
directory information, the file will be placed in the directory
specified by the DATA_DIRECTORY Customization Variable.
session-id:
This is the EHLLAPI session id of the TalkThru Terminal Emulator
session connected to the host environment. It MUST be followed by
a colon (:).
fn
The CICS File Name. This can be up to 8 characters in length.
┌──────────────────────────────────┐
│ 9.5.6.3 CICS Optional Parameters │
└──────────────────────────────────┘
The CICS File Transfer command can have two types of optional
parameters:
o Options
o Comments (for TT2SEND only)
They are separated as shown in the example under "CICS Command Format".
The possible "Options" are:
- ASCII or BINARY
- CRLF or NOCRLF
"comments" may be used for control information to be stored in the
first record of the Host File for the TT2SEND command only.
┌───────────────────────────────────┐
│ 9.5.7 IND$FILE Problem Resolution │
└───────────────────────────────────┘
┌─────────────────┐
│ 9.5.7.1 General │
└─────────────────┘
The following sections describe various conditions which may cause File
Transfer errors. Many of them reference timing parameters that can be
modified to help File Transfer perform better. All of these parameters
can be changed by making the following selections from any Phone Book
or Terminal Emulator window.
1. Select File Transfer from the Settings pull down menu.
2. Select IND$FILE from the File Transfer menu.
Once you have done this, you will see the "IND$FILE Settings" dialog.
From this dialog you can change any of the Timing Parameters referenced
below. If you request this dialog from Terminal Emulation, you can
make the changes temporarily and then exit Terminal Emulation without
saving them permanently.
┌───────────────────────────────────┐
│ 9.5.7.2 Release Incompatibilities │
└───────────────────────────────────┘
In some rare instances where your host environment does not contain the
most recent versions of IND$FILE, File Transfer may terminate with the
following message appearing on the Terminal Emulator screen:
16 Incorrect request code: file transfer canceled$
If this appears consistently when you are using Send and Receive, it
may be that an old version of IND$FILE is present on your host. Before
contacting the SCA Hotline, try adding the following Customization
Variable to the TalkThru Customization File:
IND$FILE_VERSION=MODIFIED
Refer to the Chapter, The TalkThru Customization File for more
information on how these variables are changed.
┌───────────────────────────────┐
│ 9.5.7.3 Common Error Messages │
└───────────────────────────────┘
"CRC Error, Retrying ..." <R><R> OR<R><R>The IND$FILE file transfer program has detected a significant number of transmission ERRORS ..."
This message usually occurs when the data CHECK DIGIT does not match
the Received or Sent data check digit. The problem is mostly due to an
unstable (noisy) communications line. If the problem persists, either
have the communications line checked, or increase the IND$FILE
parameter (Maximum Consecutive Errors..).
"the HOST is NOT Responding, or<R> the HOST is NOT Responding as Expected ..."
During file transfer, the transfer program either scans the terminal
buffer looking for a particular pattern of data at a particular screen
location, or it waits until the cursor is moved to a known screen
position. If neither of these conditions are met, within a specified
period of time, an error occurs. This wait time is controlled by the
IND$FILE parameter (Host response timeout). If you have a particularly
sluggish Host, or your Host has periods of long waits, you should
increase this parameter.
"the BURST ECHO option has detected a TIMEOUT ..."
This message occurs when the data being sent to the Host is being sent
too fast. Occasionally a Host controller will "get confused" by the
data being sent to it. The controller will just STOP. To get around
this problem File Transfer will attempt to restart the controller. If
this restart does not seem to work, or if another timeout error occurs,
you will get this error message. Possible solutions:
1. Decrease "Burst size" (number of characters sent at one time).
2. Increase "Burst delay" (time between bursts).
3. Increase "Burst wakeup count (number of times to nudge Host).
4. Increase "Burst echo timeout (time between nudges).
┌─────────────────────────────────────────────────┐
│ 9.5.7.4 Tips To Correcting File Transfer Errors │
└─────────────────────────────────────────────────┘
1. The following keys MUST be correctly defined:
PF1 and PF2
TAB and ERASE_EOF (upload only)
RESET
LEFT and RIGHT Arrows
HOME
ENTER
Get into terminal emulation and verify that all of the required keys
are properly defined.
2. During your first few file transfers, MAXIMIZE the Terminal
Emulator's Window. This will allow you to watch the file transfer
take place. For RECEIVE, the transfer should be uniform and smooth
as the screen fills with characters. For SEND, the transfer should
be smooth during a BURST of sent characters. After a BURST you
should see a slight PAUSE (Burst delay), then another Burst, etc..
If the transfer seems jerky (high hesitations) you are experiencing
a lot of Host stops (confused controllers).
Symptom:
The Host Stops,
File transfer nudges "Burst wakeup count" | Hesitations
File transfer waits "Burst Echo" |
Hopefully transfer continues.
If you see this erratic file transfer, try various combinations of
"Burst size", and "Burst delay". If these changes do not seem to work,
try varying the "Burst echo" time.
NOTES:
1. Try not to increase the "Burst delay" too much. This could impact
file transfer throughput.
2. If you receive CRC errors - have the communications line checked
as these errors force file transfer to resend already transferred
data.
3. Try to maximize the "Burst size" and minimize "Burst delay" as
long as it does not increase the "confused controller syndrome"
(hesitations).
9.6 Kermit
The Kermit file transfer has been implemented within TalkThru in two ways:
- You may SEND or RECEIVE a single file to/from any host which supports
the Kermit Protocol.
- You may invoke Kermit Remote if you are attached to a host where a
Kermit Server is active.
To request to SEND or RECEIVE a file, you must:
1. be connected to a host environment which supports Kermit File Transfer
2. select Send or Receive from the File pull down menu on any Terminal
Emulator screen
3. request Kermit from the File Transfer Protocol Selection dialog
If you wish to establish yourself as a Kermit Remote application, you must:
1. position yourself on a host environment which supports the Kermit Server
function
2. select Kermit Remote from the File pull down menu on any Terminal
Emulator screen
Online help is available from every dialog. There is also the following
additional help available from the Help Index.
remote (KERMIT)
Provides more information on utilizing the Kermit Remote facility.
transfer parameters (KERMIT)
Provides detailed information on the parameters you can modify to tune
your file transfer requests. These parameters are modified through a
dialog available from the Interfaces menu item on the Settings pull down
menu.