Moving and Accessing SAS Files across Operating Environments

Glossary

Accessing a SAS file	is the process whereby a user is permitted to read, write, or update a SAS file on a remote host across a network. Such a user does not typically own the file.
Architectural compatibility	is a characteristic shared by two or more hosts that use identical internal representations for storing numeric data or character data or both. Compatible hosts share identical representations along these dimensions: Floating point numeric storage (IEEE and IBM 390); Character encoding (ASCII or EBCDIC), Endian (big or little); Word alignment (4-byte boundaries or 8-byte boundaries), or Data type length (16-bit, 32-bit, or 64-bit). Host compatibility allows the exchange of data with no loss of precision or accuracy. In order to exchange data between incompatible hosts, the SAS file first must be converted to transport format. See Transport format.
Backward compatibility	is the ability of a SAS client that runs a later SAS version (such as Version 7 or Version 8) to read, write, and update a SAS file that was created at an earlier SAS version (such as Version 6) as long as the client's application does not implement new features such as long names. The SAS client and application that run the later version are said to be backward compatible with the SAS file that runs the earlier version. See also Forward compatibility.
Binary file	is a file stored in binary format, which cannot be text edited. Binary files are usually executable, but they can contain data only.
Catalog	See SAS catalog.
Catalog entry	See SAS catalog entry.
CEDA (Cross-Environment Data Access)	is a feature of SAS/CONNECT that enables hosts of any type to create a SAS file in non-native format and to read a SAS file, regardless of the compatibility of the host's internal representation with the format of the file being accessed. Using the file's universal header, any type of accessing host can dynamically translate the file to the format that is native to the host for reading only. However, in order for the accessing host to write to or update the file, the file's format already must be compatible with that of the accessing host or the file's owner must assign to the file a format that is native to the accessing host. See also Native host format and Foreign host format.
Client	See SAS/SHARE client.
Communications access method	is the method your local session uses to communicate with a remote host. Values for the communications access method are specified with the COMAMID= system option.
Compatible hosts	See Architectural compatibility.
Converting a SAS file	is the process of changing the format of a SAS file to that used by the SAS version that runs on the target host. After a SAS file has been copied to the target host, convert it by using the COPY procedure with options that identify the later version input file and the earlier version output file as defined by the LIBNAME statements. See also Copying a SAS file and Target host.
Copying a SAS file	is the process of transferring a SAS file between compatible hosts either by way of a magnetic medium or across a network. No transporting or converting is performed. To access the copied file, use the LIBNAME statement to assign a libref to the file. See also Converting a SAS file, Moving a SAS file, and Transporting a SAS file.
Corrupt file	is the result of an operation that alters the file's data or the file's header, causing the file's structure or its contents to be inaccessible. A common cause of corruption during file transport is that the transport file contains one or more incorrectly placed carriage returns or line feeds to mark the end of record, which makes the entire file unreadable after it is transferred across a network. Invalid file attributes set through the communications software can cause corruption.
Cross-Environment Data Access	See CEDA.
Cross-version environment	is one in which SAS clients and servers use different versions or releases of SAS software. These factors control whether a SAS file can be accessed for reading, writing, or updating: 1) the version of SAS run by the server, 2) the version of SAS run by the client, 3) the version of SAS that was used to create the file being accessed, and 4) the member accessed.
Data control block (DCB)	is the OS/390 control block that contains information about the physical characteristics of an operating system data set.
Data file	See SAS data file.
Data precision	is the reliability of numeric data in a SAS file that is exchanged between hosts. Compatible hosts, which store floating-point numeric data identically, exchange precise numeric data. Precision is lost when passed between incompatible hosts. The two primary floating-point numeric formats are IEEE and IBM 390. See also Architectural compatibility.
Data set	See SAS data set.
Data view	See SAS data view.
Engine	is a part of the SAS System that reads from or writes to a file. Each engine allows the SAS system to access files with a particular format. There are several types of engines, including V6, V7, and V8. See also V6 engine, V7 engine, and V8 engine.
External file	is a file maintained by the host operating system that the SAS System can read data from and route output to. External files can contain raw data, SAS programming statements, procedures output, or output created by the PUT statement. An external file is not a SAS data set. See also Fileref.
FAT-style disk drive	is a File Allocation Table that is maintained on disk drives that are used exclusively with Windows and OS/2 hosts. The FAT file system keeps track of the status of various segments of disk space used for file storage.
FDB (Financial Database)	is a variation of the SAS Multidimensional Database (MDDB) that has been enhanced for use by CFO Vision. See also MDDB.
Fileref	is a name temporarily assigned to an external file or to an aggregate storage location that identifies it to the SAS System. You assign a fileref with a FILENAME statement or with an operating system command. Do not confuse filerefs with librefs. Filerefs are used for external files; librefs are used for SAS data libraries. See also Libref.
File transfer protocol	See FTP.
Financial Database	See FDB.
Foreign host format	is a relative term that contrasts the format of the file being accessed with the internal data representation of the host that is accessing the file. If the internal formats of the remote host and the file being accessed are not the same, then the remote host can read, but cannot write to or update the file. A foreign host format is also referred to as a non-native or an alien host format. As an example, the format file created by a mainframe is considered foreign to that of a Windows host. However, the format of a Windows host that is attempting to access a file that is in Windows format is not foreign. See also Native file format.
Forward compatibility	is the ability of a SAS client that runs an earlier version of SAS to read, write, and update a SAS file that was created with a later version of SAS as long as the SAS file does not implement features that are specific to the later version, such as long names. The accessing SAS client and the application that run the earlier version of SAS are said to be forward compatible with the SAS file being accessed that was created with a later version of SAS. See also Backward compatibility.
FTP (File Transfer Protocol)	In TCP/IP, FTP is an application protocol used for transferring files to and from hosts across a network. FTP requires a userid and usually a password to allow access to the remote host.
Generation data sets	are historical copies of a SAS data set. Multiple copies of a SAS data set can be kept by requesting the generations feature. The multiple copies represent versions of the same data set, which are archived each time it is replaced. The copies are referred to as a generation group and are a collection of data sets that have the same root member name but different version numbers. There is a base version, which is the most recent version, plus a set of historical versions.
Import	is to restore a SAS transport file to its original form (a SAS data library, a SAS catalog, or a SAS data set) in the format appropriate to the target host operating system. Use the CIMPORT procedure to restore a SAS transport file created by the CPORT procedure. Import refers specifically to the use of the CIMPORT procedure for transport file restoration. In general, this term also includes the use of the COPY procedure with the XPORT engine for transport file restoration. See also Restoring a transport file.
Incompatible hosts	See Architectural compatibility.
Integrity constraints	are a set of data validation rules that are specified to restrict the data values accepted into a SAS data file. Using them can preserve the correctness and consistency of stored data. SAS enforces the integrity constraints each time data is inserted or updated in a variable that contains integrity constraints.
Item store	is a SAS member type that is a hierarchical file system with advanced performance features. An item store can contain store registry information and ODS templates, for example. Item stores on the OS/390 host also can contain HTML help files. SAS item stores are of member type ITEMSTOR.
Job control language (JCL)	is a language used to communicate information about a job to the operating system, including the data sets, time, and memory that the job needs.
Library concatenation	is the logical combination of two or more libraries that allows access to the SAS data sets in the combined libraries by using a single libref.
Library reference	See libref.
Libref	is the name temporarily associated with a SAS data library. For example, in the name SASUSER.ACCOUNTS, the name SASUSER is the libref. You can assign a libref with a LIBNAME statement or with operating system control language.
Local SAS session	is a SAS session running on the local host. The local session accepts SAS statements and passes those that are remote submitted to the remote host for processing. The local session manages the output and messages from both the local session and the remote session.
Long names	is a Version 7 and later enhancement to SAS that extends the maximum length of names from the lengths defined in Version 6. This enhancement applies to the names of variables, data sets, procedures, options, statement labels, and librefs or filerefs. Maximum lengths for long names vary according to the type of name. Truncation rules are applied to long names when regressing a Version 7 or later file to a Version 6 host.
MDDB (Multidimensional Database)	is a SAS database format for summary tables that optimizes access and retrieval times for the data that the tables contain by storing data in pre-summarized format.
Member type	is a name assigned by the SAS System that identifies the type of information stored in a SAS file. Member types include ACCESS, CATALOG, DATA, FDB, ITEMSTOR, MDDB, PROGRAM, and VIEW.
Migrating SAS files	is the process of moving SAS files (data and applications) from a host that runs an earlier version of SAS to another host that runs a later version of SAS in order to take advantage of features from the later version. See also Moving a SAS file.
Mixed library	is a Version 7 and later library that contains both Version 7 and later SAS files and Version 6 SAS files. Although mixed libraries are permitted, their maintenance can be difficult. To access a specific Version 6 file or Version 7 or later file in a Version 7 or later library, use the LIBNAME statement with the appropriate engine option. To access all Version 6 files in a mixed library, specify explicitly the V6 engine in the LIBNAME statement. To access all Version 7 or later files in a mixed library, specify explicitly the V7 or V8 engine in the LIBNAME statement. If the engine option is omitted from the LIBNAME statement, the base engine that is used by the SAS session is selected, by default. See also SAS filename extension, V6 engine, V7 engine, and V8 engine.
Moving a SAS file	is the process of passing a SAS file from one host to another host either by way of a magnetic medium or across a network. Three specific variations on moving a SAS file are converting, copying, and transporting. See Converting a SAS file, Copying a SAS file, and Transporting a SAS file.
Multidimensional Database	See MDDB.
Native host format	is a relative term that compares the format of the SAS file being accessed with the internal data representation that is used by the remote host. If the remote host and the file being accessed share a common internal data representation, then the remote host can read, write, and update the file. As an example, a Windows host has read, write, and update access to a file that is in Windows format. See also Foreign host format.
Regressing a file	is the process of moving a SAS file from a later version to an earlier version of SAS; for example, from Version 8 to Release 6.12. Reverting a file to an earlier version requires the setting of the VALIDVARNAME option to the selected engine; for example, OPTIONS VALIDVARNAME=V6, prior to using PROC COPY. If the file created in the later version contains features that do not exist in the earlier version, such as integrity constraints, then you cannot regress the file. Instead, you re-create the file on a host that runs the later version of SAS.
Remote host	in SAS/CONNECT software, is the computer on which processing occurs when you execute a PROC DOWNLOAD, PROC UPLOAD, or other SAS statement that is executed with the RSUBMIT command or the RSUBMIT statement. The term "remote" describes how you interact with the SAS session running on the computer; it is not related to the physical location of the computer. See also Local SAS session.
Restoring a transport file	is the activity that returns the SAS transport file to its original form (a SAS data library, a SAS catalog, or a SAS data set) in the format appropriate to the target host operating system. Restoration is performed using either of two techniques, as appropriate: 1) the COPY procedure to restore a SAS transport file created by the COPY procedure with the XPORT engine, 2) the CIMPORT procedure to restore a SAS transport file created by the CPORT procedure. Also referred to as reading or importing a transport file. See also Import.
SAS catalog	is a SAS file that stores many different kinds of information in smaller units called catalog entries. A single SAS catalog can contain several different types of catalog entries. Some catalog entries contain system information such as key definitions. Other catalog entries contain application information such as window definitions, help windows, formats, informats, macros, or graphics output. See also SAS catalog entry.
SAS catalog entry	is a separate storage unit within a SAS catalog. Each entry has an entry type that identifies its purpose to the SAS System.
SAS data file	is a SAS data set that is implemented in a form that contains both the data values and the descriptor information. SAS data files have the type DATA.
SAS data library	is a collection of SAS files accessed by the same library engine and recognized as a logical unit by the SAS System. Each file is a member of the library.
SAS data set	is descriptor information and its related data values organized as a table of observations and variables that can be processed by SAS software. A SAS data set can be either a SAS data file or a SAS data view. See also SAS data file and SAS data view.
SAS data view	is a SAS data set in which the descriptor information and the observations are obtained from other files. A SAS data view contains only the descriptor and other information required to retrieve the data values from other SAS files. Both PROC SQL views and SAS/ACCESS views are considered SAS data views. SAS data views are of member type VIEW.
SAS filename extension	is a standard filename identifier that captures these file attributes: 1) the engine that was used to create the file, 2) the architecture of the host on which the file was created, and 3) the member type in the file. SAS uses filename extensions as a key for identifying the appropriate files for access. The length of a Version 6 filename extension varies according to the host, whereas a Version 7 and later filename extension is limited to eight characters. As an example, filename extension `.sas7bdat` always identifies a file that was created with the V7 or later engine on a UNIX host for a member of type DATA. See also Architectural compatibility, SAS member type, V6 engine, V7 engine, and V8 engine.
SAS/SHARE client	is a SAS session that requests access to remote data by means of a SAS/SHARE server.
SAS/SHARE server	is the result of an execution of the SERVER procedure. The SERVER procedure is part of SAS/SHARE software. A SAS/SHARE server is also referred to as a server or a SAS server. A server runs in a separate SAS execution that services users' SAS sessions by controlling and executing input and output requests to one or more SAS data libraries.
Server	See SAS/SHARE server.
Source host	is the host from which a SAS file is moved.
Target host	is the host to which a SAS file is moved.
Transferring a SAS file	is the process of delivering a SAS file from a source host to a target host, either by means of a magnetic medium or across a network. See also Copying a SAS file.
Translation table	is an operating system-specific SAS catalog entry that is used to translate the value of one character to another. Translation tables often are needed to support requirements of National Language Support applications. An example of a translation table is one that converts characters from EBCDIC to ASCII-ISO. Specify a translation table by using the TRANTAB= system option, the TRANTAB statement in the CPORT and CIMPORT procedures, or the TRANTAB statement in the SAS/CONNECT UPLOAD and DOWNLOAD procedures.
Transport engine	is the facility that transforms a SAS file from its host-specific internal representation to transport format. To create a transport file, explicitly invoke the XPORT engine in the LIBNAME statement when used with the COPY procedure. See also Transport file, Transport format, and Transporting a SAS file.
Transport file	is a sequential file that contains one or more data sets or catalogs or both in transport format.
Transport format	is the internal representation of a transport file. The transport file contains a header, (which describes the content of the file) and the content of the member type (which is represented in binary format). Two distinctive transport formats result from the method that is used to create the transport file. The methods are: 1) the COPY procedure with the XPORT engine or 2) the CPORT and CIMPORT procedures. See also Transport engine, Transport file, and Transporting a SAS file.
Transporting a SAS file	is the process of putting a SAS file in transport format in order to move it between incompatible hosts. The transport process: 1) creates a transport file on the source host, 2) transfers the transport file to the target host, and 3) restores the transport file to native format on the target host. If the source and target hosts run different versions of SAS, the transport process implicitly converts the file only from an earlier SAS version to a later SAS version. See also Architectural compatibility, Converting a SAS file, Transferring a SAS file, Transport file, and Transport format.
Universal header	is attached to the beginning of a SAS file that was created with CEDA. The header contains architectural attributes such as number size, number alignment, data representation, and character encoding. Accessing the universal header, the remote host can determine if the file's format is native or foreign to that of the accessing host. If the file's format is native, then the host can read, write, and update the file. If the file's format is foreign, then the host only can read it. See also Architectural compatibility, CEDA, Foreign host format, and Native host format.
V6 engine	is the default Version 6 engine. This engine accesses SAS files in Version 6 format SAS data libraries.
V7 engine	is the default Version 7 engine. This engine accesses SAS files in Version 7 format SAS data libraries. Version 7 files and Version 8 files are identical.
V8 engine	is the default Version 8 engine. This engine accesses SAS files in Version 8 format SAS data libraries. Version 8 files and Version 7 files are identical.
XPORT	See Transport engine.

Chapter Contents
Previous
Next
Top of Page