-
AFTER=date
-
specifies a modification date in the form
of a numeric date value or a SAS date constant.
This option is valid for transferring data sets, catalogs,
and libraries and results in data sets or catalog entries being transferred
only if they have been modified on or after the specified date.
Note:
This option is available in Releases 6.09E, 6.11,
TS040, and later. ![[cautend]](../common/images/cautend.gif)
For example, the following statements cause the transfer
of data sets only if they have been modified on or after the specified date.
/************************************/
/* Download all data sets that have */
/* been modified in the last week. */
/************************************/
rsubmit;
data _null_;
today=date();
lastweek=today-7;
call symput('lastweek',lastweek);
run;
proc download in=perm out=work
after=&lastweek memtype=data;
run;
endrsubmit;
If your local session is using an earlier release that
does not support this option, PROC DOWNLOAD still executes this option because
the remote host has the input data set.
-
BINARY
-
specifies that you want to download a binary
image (an exact copy) of an external remote host file. Use this option only
for downloading external files.
The BINARY option prevents record delimiters from being
inserted at each host record. In addition, if the remote host uses a different
method of data representation, the BINARY option prevents any data translation
such as conversion from EBCDIC to ASCII. See The BINARY Option for more
information.
-
CONNECTSTATUS=NO
CSTATUS=NO
STATUS=NO
-
specifies that the status window should
not be displayed while the data set, the catalog, the library, or the external
file is being downloaded. By default, the DOWNLOAD procedure displays the
Transfer Status window.
-
CONSTRAINT=YES|NO
-
specifies if integrity constraints should
be re-created on the local host, when a SAS data set that has integrity constraints
defined is downloaded. You can specify this option with the DATA= option (if
you omit the OUT= option) or with the INLIB= and OUTLIB= options.
Note:
By default, integrity constraints
are re-created when you download a SAS library or when you download a single
SAS data set and omit the OUT= option. If you specify the OUT= option with
the DATA= option, the integrity constraints are not re-created.
-
DATA=remote-SAS-data-set
-
names a SAS data set that you want to download
from the remote host to your local host. If the data set is a permanent SAS
data set, you must define a libref before the PROC DOWNLOAD statement and
specify the two-level name of the data set.
If you specify the name of a data view in the DATA=
option, the materialized data is downloaded to the local host, not to the
view definition.
If you do not use the DATA=, INCAT=, or INFILE= option,
the last SAS data set that was created on the remote host during your SAS
session is downloaded.
If you use the DATA= option, you must either use the
OUT= option or omit all other options.
Using the DATA= option, SAS/CONNECT supports the transfer
of long named members for data set transfers, as long as the host supports
long member names.
-
ENTRYTYPE=etype
ETYPE=etype
ET=etype
-
specifies a catalog entry type to be downloaded.
You can use this option only when you specify both the INCAT= and OUTCAT=
options. See Using the ENTRYTYPE= Option
for more information.
-
EXTENDSN=NO|YES
-
specifies whether or not to promote the
length of short numerics (length less than 8 bytes) when transferring.
-
NO
-
indicates that the length of numeric variables
is not promoted. This is the default.
-
YES
-
indicates that 1 will be added to the length
of any numeric variable that has a length of less than 8 bytes before it
is transferred to the target host. The behavior of this option differs based
on the release that is being used.
In Version 6 style translation, translation
occurs twice
for every transmission. The data is translated from local to transport format,
and then the receiving host translates from transport format to local format.
Two translations occur for all data that is transferred.
When both the local host and the remote host are Version
7, the translation rules have changed. First, no translation occurs if both
the remote and local hosts have the same machine representations. This prevents
any unnecessary translation from occurring. If translation is needed, the
receiving host translates the data directly into its native representation.
So, when both the local and remote hosts are running Version 7, the data
is translated only one time when translation is necessary and is not translated
when both hosts have the same machine architecture.
-
GEN=YES|NO
-
specifies that data set generations are
to be sent during library transfers.
-
YES
-
data set generations are sent during library
transfers. This is the default.
-
NO
-
data set generations are not
sent during library transfers.
-
INCAT=remote-SAS-catalog
-
names a SAS catalog that you want to download
from the remote host to your local host. If the catalog is stored in a permanent
SAS data library, you must define a libref before specifying the PROC DOWNLOAD
statement, and you must specify the catalog's two-level name. To download
all of the catalogs in a SAS data library, specify
If you specify this form for
the INCAT= option, you
must specify the same form for the OUTCAT= option.
You can transfer catalogs with entries that contain
graphics output as well as other catalog entries.
Using the INCAT= option, SAS/CONNECT supports the transfer
of long-named members for catalog transfers, as long as the host supports
long member names.
-
INLIB=remote-SAS-library
IN=remote-SAS-library
INDD=remote-SAS-library
-
names a SAS data library that you want to
download from the remote host to your local host. All three forms of this
option are equivalent. This option must be used with the OUTLIB= option (in
any of its forms). Before using this option, you must define the libref that
is used for remote-SAS-library.
The following examples illustrate some valid pairs of
these options:
-
INDEX=NO
-
specifies that when you download a SAS data
set that has an index, the index is not re-created on the local host. You
can specify this option with the DATA= option (if you omit the OUT= option)
or by using the INLIB= and OUTLIB= options. Note that the index is re-created
by default when you download a single data set and omit the OUT= option, or
when you download a SAS data library.
If you specify the OUT= option with the DATA= option,
the index is not re-created. To create an index for the output data set, use
the INDEX= data set option in the data set name that you specify in the OUT=
option to define the index. The INDEX= data set option is described in SAS Language Reference:
Dictionary.
-
INFILE=remote-file-identifier
-
specifies the external file that you want
to download from the remote host to the local host. remote-file-identifier can be one of the following:
-
fileref
-
is used if you have defined a fileref on
the remote host that is associated with a single file. You must define the
fileref before specifying the PROC DOWNLOAD statement.
-
fileref(member)
-
is used if you have defined a fileref on
the remote host that is associated with an aggregate storage location, such
as a directory or a partitioned data set. member then specifies
the particular file(s) to transfer in that aggregate storage location. An
asterisk (*) can be used as a wildcard character in the member
specification to transfer
You must define the fileref before specifying the PROC
DOWNLOAD statement. Refer to the SAS documentation for your remote host for
more information about this use of filerefs.
The following example demonstrates how to use a wildcard
to transfer (download) all files that have the extension .sas
and are located in a directory on the remote UNIX host to a folder on a local
PC.
filename locref 'c:\';
rsubmit;
filename fref '/local/programs';
proc download infile=fref('*.sas')
outfile=locref;
run;
endrsubmit;
-
'external-file-name'
-
is used to explicitly define the file that
is to be downloaded.
If you use the INFILE= option, you must also use the
OUTFILE= option.
-
MEMTYPE=(mtype-list)
MT=(mtype-list)
MTYPE=(mtype-list)
-
specifies one or more member types to be
downloaded. You can specify this option only with the INLIB= and OUTLIB= options.
See Using the MEMTYPE= Option for
more information.
-
OUT=local-SAS-data-set
-
names the SAS data set on the local host
to which you want the downloaded data set written. If you want to create a
permanent SAS data set, you must define the libref before specifying the PROC
DOWNLOAD statement, and you must specify a two-level SAS data set name.
Using the OUT= option, SAS/CONNECT supports the transfer
of long-named members for data set transfers, as long as the host supports
long member names.
The OUT= option is a valid form of the OUTLIB= option.
The DOWNLOAD procedure determines how to interpret the meaning of the OUT=
option as follows:
See Default Naming Conventions for Downloaded Data Sets
for information about the effect of omitting the OUT= option.
-
OUTCAT=local-SAS-catalog
-
names the SAS catalog on the local host
to which you want the downloaded catalog written. If you want to create a
permanent SAS catalog, you must define the libref before specifying the PROC
DOWNLOAD statement and you must specify a two-level SAS catalog name. To download
all of the catalogs in a SAS data library, specify
If you specify this form for
the OUTCAT= option, you
must specify the same form for the INCAT= option.
If you use the OUTCAT= option, you must also use the
INCAT= option.
Using the OUTCAT= option, SAS/CONNECT supports the transfer
of long-named members for catalog transfers, as long as the host supports
long member names.
-
OUTFILE=local-file-identifier
-
identifies an external file on the local
host to which you want a downloaded external file written. local-file-identifier can be one of the following:
-
fileref
-
is used if you have defined a fileref on
the local host that is associated with a single file. You must define the
fileref before specifying the PROC DOWNLOAD statement.
-
fileref(member)
-
is used if you have defined a fileref on
the local host that is associated with an aggregate storage location such
as a directory. member then specifies the particular file in
that aggregate storage location. You must define the fileref before specifying
the PROC DOWNLOAD statement. Refer to the SAS documentation for your local
host for more information about this use of filerefs.
Note:
If a wildcard (*) is used in the INFILE= option,
then OUTFILE=fileref should point to an aggregate storage location
such as a directory.
-
'external-file-name'
-
is used to explicitly define the file that
is to be downloaded.
If you use the OUTFILE= option, you must also use the
INFILE= option.
-
OUTLIB=local-SAS-library
OUT=local-SAS-library
OUTDD=local-SAS-library
-
names the destination SAS data library on
your local host where the downloaded data sets and catalogs from the remote
host are stored. All three forms of this option are equivalent. Before using
this option, you must define the libref that is used for local-SAS-library.
Note:
The OUT= form of this option is the same as the
OUT= option that is used to specify a SAS data set. When you use this option,
the DOWNLOAD procedure determines whether the input option was DATA= or INLIB=
and processes the downloaded objects appropriately.
The OUTLIB= option must be used with the INLIB= option,
but you can use any form of the OUTLIB= option with any form of the INLIB=
option. Refer to the description of the INLIB= option for examples that illustrate
some valid pairs of these options.
-
TRANIN=translation-table-name
-
specifies a translation table to be used
when transferring a data set that is stored in a different data representation
than that of the remote host.
For example, FTP was used to transfer a data set from
a UNIX machine to a remote VAX, and now you want to transfer the data set
for use on your PC. The data set is not in the native VAX format (the remote
host), so the default translation table will not work. Using the TRANIN= option
with PROC DOWNLOAD, you can specify a translation table that transfers the
data from UNIX to the PC.
The translation will take place on the remote host before
the data is transferred to the local host. This option is equivalent to using
the TRANTAB= data set option on the input data set.
Note:
This option is only valid for data set transfers
between two Version 7 sessions and when the transfer is between two hosts
that have different machine architectures, which makes translation necessary.
-
TRANNET=translation-table-name
-
specifies a translation table to be used
when transferring a data set between remote and local hosts that have different
machine architectures. The translation table specified will be used in place
of the default translation table. The translation will take place on the local
host after the data is transferred from the remote host.
Note:
This option is only valid for data set transfers
between two Version 7 sessions and when the transfer is between two hosts
that have different machine architectures, which makes translation necessary.
-
TRANOUT=translation-table-name
-
specifies a translation table to be used
when transferring a remote data set to a local host, and the OUTREP= data
set option indicates a data representation different from the native data
representation of the local host. The translation will take place on the local
host after the data is transferred from the remote host.
For example, you are using a PC and would like to transfer
a data set from a UNIX machine, and the OUTREP=VAX_VMS data set option is
specified in a DATA statement. Using the TRANOUT= option with PROC DOWNLOAD,
you can specify a translation table that transfers the data set from the remote
UNIX machine to your local PC in a VAX format.
Note:
This option is only valid for data set transfers
between two Version 7 sessions and when the transfer is between two hosts
that have different machine architectures, which makes translation necessary.
-
V6TRANSPORT
-
specifies that data should be translated
in the Version 6 style. This option should only be specified when the Version
6 translation style you want and both the local and remote hosts are Version
7. Version 6 style translation means that the data is translated from a local
format to a transport format, and then the receiving host translates the
data from the transport format to a local format.
When V6TRANSPORT is specified, the default behavior
is to promote the length of numerics that are less than 8 bytes. The EXTENDSN=NO
option may be used with the V6TRANSPORT option to prevent the lengths from
being promoted.
When transferring files from Version 7 to Version 6,
SAS/CONNECT checks that the files are Version 6 compliant. If the files are
not Version 6 compliant, an error message is issued and the transfer is terminated.
For example, a data set from a Version 7 session that contains a variable
with a long name will not transfer because Version 6 does not support long
variable names.
Data set and variable names are truncated if they exceed
the Version 6 maximum. A warning message is issued about the truncation,
but the transfer will continue.
In Version 6, the value of a character variable has
a maximum length of 200. For Version 7, this maximum has been increased to
32K. Therefore, a Version 7 variable value that has a length that is greater
than 200 will transfer to a Version 6 variable, but the value is truncated
to 200. A warning message is issued about the truncation, but the transfer
will continue.
