home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cc.umanitoba.ca software
/
ftp.cc.umanitoba.ca-software-.zip
/
ftp.cc.umanitoba.ca-software-
/
mac_network
/
Comet.3.0.8.sit.bin
/
ibm-host-software
/
UPLOAD.HELPCMS
< prev
Wrap
Text File
|
1988-06-28
|
3KB
|
67 lines
.cs 1 on
UPLOAD
The UPLOAD command transfers IBM PC or Macintosh files to CMS.
(Cornell EXEC)
.cs 1 off
.cs 2 on
The format of the UPLOAD command is:
+----------+------------------------------------------------------------------+
| UPLOAD | <">source_file<"> <fn|* <ft|* <fm>>> <(options<)>> |
| | |
| | options: |
| | |
| | <REPlace> <BINary> <lrecl> |
+----------+------------------------------------------------------------------+
.cs 2 off
.cs 3 on
where:
source_file
is the name of the file to upload from the microcomputer.
If the name contains blanks, enclose it in double quotes (").
Slashes ('/') are interpreted by the microcomputer as directory
delimiters; thus, a PC interprets them as back-slashes ('\')
and a Macintosh interprets them as colons (':').
fn ft fm specifies the file name for the CMS file on the mainframe. If you
don't specify fn and/or ft, they default to the first and second
parts of source_file, respectively. The default for fm is 'A1'.
REPLACE specifies that the uploaded file will overwrite a file with
that name if it already exists on the mainframe. If you
do not specify REPLACE, UPLOAD will stop with an error message
without overwriting the file if it finds that a CMS file with
the same name already exists.
BINARY causes the file to be uploaded as a binary file; by default
the program will perform EBCDIC/ASCII translation and start
a new line in the CMS file when it encounters a linefeed
in the micro file.
LRECL tells UPLOAD to create the CMS file with fixed length records of this
record length (less than 65535). The default is to create the CMS
file with variable length records.
.cs 3 off
.cs 5 on
Usage Notes:
1. The UPLOAD EXEC part of the FT3270 and FTC19 file transfer programs
translates ASCII backslashes to EBCDIC cents signs (hexidecimal code 4A)
when sending a file from a micro to the mainframe, and DOWNLOAD translates
EBCDIC backslashes similarly incorrectly when transferring a file from the
mainframe to a micro. If you use UPLOAD EXEC to upload C programs from a
micro you will have to change all 4A codes to E0 codes in these C programs
before running them with a C compiler on the mainframe, and change E0 codes
to 4A codes before downloading C programs from the mainframe to a micro
using DOWNLOAD EXEC.
Examples:
.cs 5 off