SAS/CONNECT User's Guide

Syntax for the PROC UPLOAD Statement

PROC UPLOAD<data-set-option(s)>

<catalog-option(s)>

<library-option(s)>

<external-file-option(s)>

<AFTER=date>

<CONNECTSTATUS=NO>;

data-set-options can be one or more of the following:

CONSTRAINT=NO

DATA=local-SAS-data-set

EXTENDSN=NO

INDEX=NO

OUT=OUT=remote-SAS-data-set

TRANIN=

TRANNET=

TRANOUT=

V6TRANSPORT
catalog-options can be one or more of the following:

ENTRYTYPE=etype

EXTENDSN=NO

INCAT=local-SAS-catalog

OUTCAT=remote-SAS-catalog
library-options can be one or more of the following:

CONSTRAINT=NO

EXTENDSN=NO

GEN=YES

INDEX=NO

INLIB=local-SAS-library

MEMTYPE=(mtype-list)

OUTLIB=remote-SAS-library

V6TRANSPORT
external-file-options are the following:

BINARY

INFILE=local-file-identifier

OUTFILE=remote-file-identifier

PROC UPLOAD Statement Options

The following options can be used with the PROC UPLOAD statement. They are shown in alphabetical order.

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. Its use 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]

For example, the following statement causes the transfer of any data sets or catalog entries in the library ACCTS only if they have been modified on or after December 30, 1995.

proc upload inlib=accts outlib=accts 
   after='30dec95'd status=no;

If your local session is using an earlier release of SAS that does not support this option, PROC UPLOAD produces the following message:

Warning: AFTER= option not supported by earlier
         release; option will be ignored.

Note: However, if the local host is running Release 6.11 TS020 or Release 6.08 TS415 through Release 6.08 TS430, the option is ignored, but no warning is displayed. [cautend]

BINARY

specifies that you want to upload a binary image (an exact copy) of an external file. Use this option only for uploading external files.

The BINARY option prevents record delimiters from being inserted at each remote 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 ASCII to EBCDIC. 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 uploaded. By default, the UPLOAD procedure displays the Transfer Status window.

CONSTRAINT=YES|NO

specifies if integrity constraints should be re-created on the remote host, when a SAS data set that has integrity constraints defined is uploaded. 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 upload a SAS library or when you upload 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. [cautend]

DATA=local-SAS-data-set

names a SAS data set that you want to upload to the remote host from your local host. If the data set is a permanent SAS data set, you must define a libref before the PROC UPLOAD 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 uploaded to the remote host, not the view definition.

If you do not use the DATA=, INCAT=, or INFILE= option, the last SAS data set that was created on the local host during your SAS session is uploaded.

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 uploaded. You can use this option only when you specify both the INCAT= and OUTCAT= options. See Using the ENTRYTYPE= Option for more information.

EXTENDSN=YES|NO

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.

When both the local and remote hosts are Version 7 and the V6TRANSPORT option is specified, the default behavior is to promote the length of numerics whose lengths are less than 8 bytes. This is consistent with Version 6 behavior. To override this behavior, specify EXTENDSN=NO along with the V6TRANSPORT option in the UPLOAD statement.
When the local host is Version 7 and the remote host is Version 6, neither the V6TRANSPORT nor the EXTENDSN= option is supported or recognized.
When the local host is Version 6 and the remote host is Version 7, neither the V6TRANSPORT nor the EXTENDSN= option is supported or recognized.

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=local-SAS-catalog

names a SAS catalog that you want to upload to the remote host from your local host. If the catalog is stored in a permanent SAS data library, you must define a libref before specifying the PROC UPLOAD statement, and you must specify the catalog's two-level name. To upload all of the catalogs in a SAS data library, specify

INCAT=libref._ALL_

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=local-SAS-library
IN=local-SAS-library
INDD=local-SAS-library

names a SAS data library that you want to upload from the local host to your remote 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 local-SAS-library.

The following examples illustrate some valid pairs of these options:

INLIB= OUTLIB=

INLIB= OUT=

IN= OUT=

IN= OUTDD=

INDD= OUTDD=

INDD= OUTLIB=

INDEX=NO

specifies that when you upload a SAS data set that has an index, the index is not re-created on the remote 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 upload a single data set and omit the OUT= option, or when you upload 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=local-file-identifier

specifies the external file that you want to upload to the remote host from the local host; 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 UPLOAD 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 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

all files in the specified location (*).
all files that have the same extension (*.extension).
all files that have the same name but different extensions (name.*).

You must define the fileref before specifying the PROC UPLOAD statement. Refer to the SAS documentation for your local host for more information about this use of filerefs.

The following example demonstrates how to use a wildcard to transfer (upload) all files that have the extension .sas and are located in a directory on a remote UNIX host to a folder on a local PC.

filename locref 'c:\';
rsubmit;
   filename fref '/local/programs';
   proc upload infile=locref('*.sas') 
               outfile=fref;
   run;
endrsubmit;

'external-file-name'

is used to explicitly define the file that is to be uploaded.

If you use the INFILE= option, you must also use the OUTFILE= option.

MEMTYPE=(mtype-list)
MTYPE=(mtype-list)
MT=(mtype-list)

specifies one or more member types to be uploaded. You can specify this option only with the INLIB= and OUTLIB= options. See Using the MEMTYPE= Option for more information.

OUT=remote-SAS-data-set

names the SAS data set on the remote host to which you want the uploaded data set written. If you want to create a permanent SAS data set, you must define the libref before specifying the PROC UPLOAD 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 UPLOAD procedure determines how to interpret the meaning of the OUT= option as follows:

When you specify the DATA= option and the OUT= option, the OUT= option names the output SAS data set.
For example, if the USER= option is set to MYLIB, the following statement uploads the data set A from the library MYLIB on the local host to the library MYLIB on the remote host:
```
proc upload data=a out=a;
run;
```
If you specify only the OUT= option, the UPLOAD procedure uploads the last SAS data set that was created on the local host.
For example, the following statement uploads the last data set that was created on the local host to the data set MYDATA in the library MYLIB on the remote host (assuming USER=MYLIB).
```
proc upload out=mydata;
run;
```
When you specify the INLIB= option (or some other form of this option) with the OUT= option, the OUT= option specifies the name of a SAS data library.
For example, the following statement uploads all of the data sets and catalogs that are in the library A on the local host to the library RMTLIB on the remote host.
```
proc upload inlib=a out=rmtlib;
run;
```

See Default Naming Conventions for Uploaded Data Sets for information about the effect of omitting the OUT= option.

OUTCAT=remote-SAS-catalog

names the SAS catalog on the remote host to which you want the uploaded catalog written. If you want to create a permanent SAS catalog, you must define the libref before specifying the PROC UPLOAD statement and specify a two-level SAS catalog name. To upload all of the catalogs in a SAS data library, specify

OUTCAT=libref._ALL_

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=remote-file-identifier

identifies an external file on the remote host to which you want an uploaded external file written. 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 UPLOAD 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 specifies the particular file in that aggregate storage location. You must define the fileref before specifying the PROC UPLOAD statement. Refer to the SAS documentation for your remote 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. [cautend]

'external-file-name'

is used to explicitly define the file that is to be uploaded.

If you use the OUTFILE= option, you must also use the INFILE= option.

OUTLIB=remote-SAS-library
OUT=remote-SAS-library
OUTDD=remote-SAS-library

names the destination SAS data library on your remote host where the uploaded data sets and catalogs from the local host are stored. All three forms of this option are equivalent. Before using this option, you must define the libref that is used for remote-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 UPLOAD procedure determines whether the input option was DATA= or INLIB= and processes the uploaded objects appropriately. [cautend]

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 the local host.

For example, you used FTP to transfer a data set from a UNIX machine to your local PC, and now you want to transfer the data set for use on a VAX. The data set is not in the native PC format (your local host), so the default translation table will not work. Using the TRANIN= option with PROC UPLOAD, you can specify a translation table that transfers the data from UNIX to the VAX.

The translation will take place on the local host before the data is transferred to the remote 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. [cautend]

TRANNET=translation-table-name

specifies a translation table to be used when transferring a data set between local and remote hosts with different machine architectures. The translation table specified will be used in place of the default translation table. The translation will take place on the remote host after the data is transferred from the local host.

TRANOUT=translation-table-name

specifies a translation table to be used when transferring a local data set to a remote host, and the OUTREP= data set option indicates a data representation different from the native data representation of the remote host. The translation will take place on the remote host after the data is transferred from the local host.

For example, you are using a PC and would like to transfer a data set to a UNIX machine, and the OUTREP=VAX_VMS data set option is specified in a DATA statement. Using the TRANOUT= option with PROC UPLOAD, you can specify a translation table that transfers the data set from your local PC to the UNIX machine in a VAX format.

V6TRANSPORT

specifies that data should be translated in the Version 6 style. This option should only be specified when the Version 6 translation style is desired 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 greater than 200 will transfer to a Version 6 variable, but the value will be truncated to 200. A warning message is issued about the truncation, but the transfer will continue.

Default Naming Conventions for Uploaded Data Sets

Follow these rules when you upload a SAS data set and do not specify the name of the data set in the OUT= option:

If the input data set (the data set that is specified in the DATA= option) has a two-level name and the same libref that is defined for the input data set is also defined in the remote host environment, the data set is uploaded to the library on the remote host that is associated with that libref. The data set has the same member name on the remote host.
For example, suppose you submit the following statement:
```
libname orders 
   local-host-SAS-data-library;
```
When you remote submit the following statements, the data set ORDERS.QTR1 is uploaded to ORDERS.QTR1 on the remote host.
```
   /*******************************************/
   /* The libref ORDERS is defined on both    */
   /* hosts.                                  */
   /*******************************************/
libname orders 
   remote-host-SAS-data-library;
proc upload data=orders.qtr1;
run;
```
If the input data set has a two-level name but the libref for the input data set is not also defined in the remote host environment, the data set is uploaded to the default library on the remote host. This is usually the WORK library, but the library may also be defined by using the USER libref.
The data set retains the same data set name that it had on the local host. For example, if you remote submit the following statement, the data set is uploaded to WORK.QTR2 on the remote host.
```
   /*******************************************/
   /* The libref ORDERS is defined only on    */
   /* the local host.                         */
   /*******************************************/
proc upload data=orders.qtr2;
run;
```

If the input data set has a one-level name and the default libref on the local host also exists on the remote host, the data set is uploaded to that library.

For example, suppose you submit the following statements:

libname orders 
   local-host-SAS-data-library;
options user=orders;

If you remote submit the following statements, the data set ORDERS.QTR1 is uploaded to ORDERS.QTR1 on the remote host.

   /*******************************************/
   /* The libref ORDERS is defined on both    */
   /* hosts.                                  */
   /*******************************************/
libname orders 
   remote-host-SAS-data-library;
libname remote 
   remote-host-SAS-data-library;
   /************************************/
   /* This option has no effect in     */
   /* this case.                       */
   /************************************/
options user=remote;
proc upload data=qtr1;
run;

If the input data set has a one-level name and the default libref on the local host does not exist on the remote host, the data set is uploaded to the default library on the remote host. That is, the USER libref on the remote host is used only if the USER libref on the local host does not exist on the remote host.
For example, suppose you submit these statements:
```
libname orders 
   local-host-SAS-data-library;
options user=orders;
```
When you remote submit the following statements, the data set ORDERS.QTR1 is uploaded to REMOTE.QTR1 on the remote host.
```
   /*******************************************/
   /* The libref ORDERS is defined only on    */
   /* the remote host.                        */
   /*******************************************/
libname remote 
   remote-host-SAS-data-library;
options user=remote;
proc upload data=qtr1;
run;
```
If you omit the DATA= option, as in this example,
```
proc upload;
run;
```
the last data set that was created on the local host during the SAS session is uploaded to the remote host.

The naming conventions on the remote host follow one of the rules described above, based on how the last data set that was created was named.

Data Set Options and Attributes for the UPLOAD Statement

PROC UPLOAD permits you to specify SAS data set options in the DATA= and OUT= options. Note that SAS data set options are not supported with the INLIB= and OUTLIB= options, even when you upload only data sets. The data set options must be associated with a specific SAS data set, so they must be used in the DATA= or OUT= options.

In addition, when you upload SAS data sets by using the DATA= option (omitting the OUT= option) or the INLIB= and OUTLIB= options, or if you omit all of these options, the following characteristics are inherited by the uploaded data set.

Note: The following list of characteristics shows the SAS data set option (in parenthesis) that was used to create the characteristic for the original data set. You do not have to specify the option to have it inherited when the data set is uploaded. [cautend]

password for ALTER protection (ALTER= SAS data set option)
compressed observations (COMPRESS= SAS data set option)
indexes (INDEX= SAS system option or other methods of creating indexes).
Note: The index for an uploaded SAS data set is re-created on the remote host; not copied from the local host. To prevent the re-creation of the index, you can specify the INDEX=NO option in the PROC UPLOAD statement, as described in PROC UPLOAD Statement Options.
data set label (LABEL= SAS data set option)
password for READ protection (READ= SAS data set option)
re-use of free space in compressed data sets (REUSE= SAS data set option)
list of variables that the data set is sorted by (SORTEDBY= SAS data set option)
data set type (TYPE= SAS data set option)
password for WRITE protection (WRITE= SAS data set option)
integrity constraints
maximum generations.

If you specify the OUT= option when uploading a single data set, only the following characteristics are inherited by the uploaded data set:

data set type
data set label.

The following example illustrates the use of the DATA= option and the INDEX=NO option. The example also shows the use of the KEEP= SAS data set option. Note that because no OUT= option is specified, the uploaded data set inherits the characteristics of the input data set except the index (because the INDEX=NO option is specified).

proc upload data=study(keep=age score1 score2) index=no;
run;

Chapter Contents
Previous
Next
Top of Page