O'Reilly logo

SAS 9.4 Language Reference, 6th Edition by SAS Institute

Stay ahead with the world's most comprehensive technology and business learning platform.

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more.

Start Free Trial

No credit card required

encoding
is a set of characters (letters, logograms, digits, punctuation, symbols, control
characters, and so on) that have been mapped to numeric values (called code points)
that can be used by computers. The code points are assigned to the characters in the
character set by applying an encoding method. Some examples of encodings are
Wlatin1 and Danish EBCDIC.
incompatible
describes a file that has a different data representation or encoding than the current
SAS session. CEDA enables access to many types of incompatible files.
Advantages of CEDA
CEDA offers these advantages:
You can transparently process a supported SAS file with no knowledge of the file's
data representation or character encoding.
No transport files are created. CEDA requires a single translation to the current
session's data representation, rather than multiple translations from the source
representation to transport file to target representation.
CEDA eliminates the need to perform multiple steps in order to process the file.
CEDA does not require a sign-on as is needed in SAS/CONNECT or a dedicated
server as is needed in SAS/SHARE.
SAS File Processing with CEDA
What Types of Processing Does CEDA Support?
CEDA supports SAS 7 and later SAS files that are created in directory-based operating
environments like UNIX, Windows, and OpenVMS. CEDA provides the following SAS
file processing for these SAS engines:
BASE
default Base SAS engine for SAS 9 (V9), SAS 8 (V8), and SAS 7 (V7).
SASESOCK
TCP/IP port engine for SAS/CONNECT software.
TAPE
sequential engine for SAS 9 (V9TAPE), SAS 8 (V8TAPE), and SAS 7 (V7TAPE).
Table 32.1 SAS File Processing Provided by CEDA
SAS File Type Engine Supported Processing
SAS data file BASE, TAPE, SASESOCK
input and output
*
PROC SQL view BASE input
710 Chapter 32 Processing Data Using Cross-Environment Data Access (CEDA)
SAS File Type Engine Supported Processing
SAS/ACCESS view for
Oracle or Sybase
BASE input
MDDB file
**
BASE input
*
For output processing that replaces an existing SAS data file, there are behavioral differences. For more
information, see “Behavioral Differences for Output Processing” on page 711.
**
CEDA supports SAS 8 and later MDDB files.
Behavioral Differences for Output Processing
For output processing that replaces an existing SAS data file, the BASE and TAPE
engines behave differently regarding the following attributes:
encoding
The BASE engine uses the encoding of the file from the source library. That is,
the encoding is cloned.
The TAPE engine uses the current SAS session encoding.
For both the BASE and TAPE engines, by default PROC COPY uses the
encoding of the file from the source library. If, instead, you want to use the
encoding of the current SAS session, specify the NOCLONE option. If you want
to use a different encoding, specify the NOCLONE option and the ENCODING=
option. When you use PROC COPY with SAS/SHARE or SAS/CONNECT, the
default behavior is to use the encoding of the current SAS session.
data representation
The BASE and TAPE engines use the data representation of the current SAS
session, except with PROC COPY.
For both the BASE and TAPE engines, by default PROC COPY uses the data
representation of the file from the source library. If, instead, you want to use the
data representation of the current SAS session, specify the NOCLONE option. If
you want to use a different data representation, specify the NOCLONE option
and the OUTREP= option. When you use PROC COPY with SAS/SHARE or
SAS/CONNECT, the default behavior is to use the data representation of the
current SAS session.
Restrictions for CEDA
CEDA has the following restrictions:
SAS catalogs are not supported. Catalog entries could include formats, stored
compiled macros, SAS/AF applications, SAS/GRAPH output, SAS code, SCL code,
data, and other entry types that are specific to various SAS procedures.
Update processing is not supported.
Integrity constraints cannot be read or updated.
An audit trail file cannot be updated, but it can be read.
Indexes are not supported. Therefore, WHERE optimization with an index is not
supported.
Extended attributes cannot be updated, but they can be read.
SAS File Processing with CEDA 711

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, interactive tutorials, and more.

Start Free Trial

No credit card required