Glossary


A-D

accessing SAS files
the process whereby a user reads, writes , or updates SAS files that are stored on a different operating environment across a network. Such a user typically does not own the files.
architectural compatibility
a characteristic shared by two or more operating environments that use identical internal representations for storing numeric data, character data, or both. Compatible operating environments use the same standards or conventions for storing floating-point numbers (IEEE or IBM 390); for character encoding (ASCII or EBCDIC); for the ordering of bytes in memory (big Endian or little Endian); for word alignment (4-byte boundaries or 8-byte boundaries); and for data-type length (16-bit, 32-bit, or 64-bit).
backward compatibility
the ability of a SAS client that runs a particular version of SAS (such as SAS 9 or SAS Version 8) to read, write, and update a SAS file that was created using an earlier version of SAS (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 was created using the earlier version.

See also forward compatibility.

binary file
a file that is stored in binary format, which cannot be edited with a text editor. Binary files are usually executable, but they can contain only data.
catalog

See SAS catalog.

catalog entry

See SAS catalog entry.

CEDA (Cross-Environment Data Access)
a feature of SAS software that enables a SAS data file that was created in any directory-based operating environment (for example, Solaris, Windows, HP-UX, OpenVMS) to be read by a SAS session that is running in another directory-based environment. You can access the SAS data files without using any intermediate conversion steps.

See also native file format.

See also foreign file format.

client session
a SAS session that is running on a client computer. A client session accepts SAS statements and passes those that are remote-submitted to the server for processing. The client session manages the output and messages from both the client session and the server session.
communications access method
the method that a client uses to communicate with a server. You can use the COMAMID= system option to specify the communications access method.
compatible operating environments

See architectural compatibility.

converting SAS files
the process of changing the format of SAS files to the format that is used by SAS in the target operating environment.

See also copying SAS files.

See also target operating environment.

copying SAS files
the process of transferring SAS files between compatible operating environments, either by means of a magnetic medium or across a network. No transporting or converting is performed.

See also converting SAS files.

See also moving SAS files.

See also transporting SAS files.

Cross-Environment Data Access (CEDA)

See CEDA (Cross-Environment Data Access).

cross-version environment
a computing environment in which SAS clients and servers use different versions or releases of SAS software. The following 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 that is being accessed, and 4) the member type that is being accessed.

See also member type.

data control block (DCB)

See data control block (DCB).

data file

See SAS data file.

data precision
the reliability of numeric data in a SAS file that is exchanged between operating environments. Compatible operating environments, which use the same internal representation for storing floating-point numeric data, exchange numeric data with no loss of precision. Precision is lost when numeric data is passed between incompatible operating environments.

See also architectural compatibility.

data set

See SAS data set.

data view

See SAS data view.

DCB (data control block)
the OS/390 control block that contains information about the physical characteristics of an operating system data set.
descriptor information
information about the contents and attributes of a SAS data set. For example, the descriptor information includes the data types and lengths of the variables , as well as which engine was used to create the data. SAS creates and maintains descriptor information within every SAS data set.



Moving and Accessing SAS 9.1 Files
Moving And Accessing SAS 9.1 Files
ISBN: 1590472306
EAN: 2147483647
Year: 2004
Pages: 109
Authors: SAS Institute

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net