27.12.2013 Views

What's New in Base SAS: Details

What's New in Base SAS: Details

What's New in Base SAS: Details

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

10 Chapter 1 • <strong>Details</strong> about the <strong>New</strong> Features <strong>in</strong> <strong>Base</strong> <strong>SAS</strong> 9.4<br />

ISO-8859–13 (Lat<strong>in</strong> 7) and ISO-8859–15 (Lat<strong>in</strong> 10) are new encod<strong>in</strong>gs that <strong>SAS</strong><br />

supports.<br />

Metadata<br />

<strong>SAS</strong> data can be bound to metadata and subject to metadata layer permissions. A<br />

metadata-bound library is a physical library that is tied to a correspond<strong>in</strong>g metadata<br />

object. You use the AUTHLIB procedure to manage metadata-bound libraries.<br />

In the first ma<strong>in</strong>tenance release for <strong>SAS</strong> 9.4, an adm<strong>in</strong>istrator can use the AUTHLIB<br />

procedure to require that all data sets <strong>in</strong> a metadata-bound library be automatically<br />

encrypted us<strong>in</strong>g the REQUIRE_ENCRYPTION=YES option <strong>in</strong> the CREATE or<br />

MODIFY statements.<br />

The metadata server connection system options support use of a system connection<br />

profile to connect to the <strong>SAS</strong> Metadata Server.<br />

The METAOPERATE procedure and the METADATA procedure have been enhanced<br />

to operate <strong>in</strong> a clustered <strong>SAS</strong> Metadata Server configuration and <strong>in</strong> a s<strong>in</strong>gle <strong>SAS</strong><br />

Metadata Server configuration.<br />

The Metadata LIBNAME Eng<strong>in</strong>e supports extended attributes on <strong>SAS</strong> data sets and<br />

libraries.<br />

A new metadata DATA step function, METADATA_APPPROP, returns the value of a<br />

specified property for a specified SoftwareComponent or DeployedComponent.<br />

Process<strong>in</strong>g of the METAAUTORESOURCES system option has changed. Now, library<br />

assignments that are stored <strong>in</strong> metadata are always applied before library assignments <strong>in</strong><br />

the AUTOEXEC file.<br />

<strong>SAS</strong> Logg<strong>in</strong>g Facility<br />

The <strong>SAS</strong> Logg<strong>in</strong>g facility uses the ConsoleAppender to write messages to z/OS system<br />

consoles.<br />

You can specify whether a logger’s additivity and level sett<strong>in</strong>gs are permanent or can be<br />

modified programmatically by sett<strong>in</strong>g a logger’s IMMUTABILITY sett<strong>in</strong>g.<br />

Three new loggers support audit<strong>in</strong>g logg<strong>in</strong>g configurations.<br />

Two new loggers support audit<strong>in</strong>g access to <strong>SAS</strong> data sets.<br />

Two new loggers support audit<strong>in</strong>g access to metadata-bound libraries.<br />

You can specify the client ID <strong>in</strong> the DEFAULT and TRACE conversion patterns.<br />

Application Response Measurement (ARM)<br />

When you have an ARM appender that is def<strong>in</strong>ed <strong>in</strong> the XML configuration file, you no<br />

longer need to set the ARMAGENT=LOG4<strong>SAS</strong> system option. ARM sets<br />

ARMAGENT to LOG4<strong>SAS</strong> <strong>in</strong>ternally.<br />

There are three new ARM metrics for the ARM_DSIO subsystem:<br />

• NOBS reports the number of observations <strong>in</strong> the file.<br />

• NVAR reports the number of variables <strong>in</strong> the file.<br />

• NOBSREAD reports the number of observations read.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!