07.08.2013 Views

SAS 9.1.3 Intelligence Platform: System Administration Guide

SAS 9.1.3 Intelligence Platform: System Administration Guide

SAS 9.1.3 Intelligence Platform: System Administration Guide

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.

258 Reserved omaconfig.xml Options R Appendix 4<br />

to include them by <strong>SAS</strong> Technical Support. There are two categories of reserved options:<br />

<strong>SAS</strong> Metadata Server options and debugging options. The <strong>SAS</strong> Metadata Server<br />

options control features that are considered important for the optimized operation of the<br />

metadata server, but can be turned off if necessary. Because they are turned on by<br />

default, the only reason to include them in the omaconfig.xml file is to turn them off.<br />

The debugging options can increase the processing overhead of the metadata server;<br />

therefore, they are not recommended for normal use.<br />

The reserved server options are specified along with other server options in the<br />

XML element in the omaconfig.xml file. The debugging options are specified in<br />

an XML element in the omaconfig.xml file.<br />

Reserved Options<br />

BLOCK_ADDS="0 | 1"<br />

optimizes server processing for adding metadata. A value of 1 (the default)<br />

optimizes processing by writing all objects that need to be added to a repository<br />

container data set in a single engine call. A value of 0 causes each object to be<br />

added by a separate engine call.<br />

LOCK_DEPENDENT_REPOS="0 | 1"<br />

determines the repository locking algorithm used by the server. A value of 0 (the<br />

default) specifies to lock only repositories that are explicitly referenced in update<br />

and delete requests. A value of 1 specifies to lock all repositories that have a<br />

hierarchical relationship with the repository on which update and delete requests<br />

are issued. Locking all repositories in a repository hierarchy can have a negative<br />

effect on server performance.<br />

PHYSICAL_DELETE="0 | 1"<br />

(deprecated) determines the disposition of deleted metadata records in a<br />

repository. A value of 0 specifies that deleted records are logically deleted from a<br />

repository. A value of 1 specifies that deleted records are physically deleted from a<br />

repository. The default is to physically delete metadata records.<br />

WORKUNIT_INDEXES="0 | 1"<br />

optimizes server processing for update requests by using indexes in workunits. A<br />

value of 0 causes internal searches to apply WHERE clauses to each object in the<br />

workunit list. A value of 1 (the default) causes internal searches of workunit<br />

updates to use indexes, which significantly speeds up the search.<br />

Debugging Options<br />

DEBUG<br />

supports the debugging macros documented in the <strong>SAS</strong> Internal Programmer’s<br />

<strong>Guide</strong> for <strong>SAS</strong> Scalable Architecture applications.<br />

GENERIC="0 | 1"<br />

supports the $GENERIC system option for <strong>SAS</strong> Scalable Architecture applications.<br />

A value of 1 turns the option on. A value of 0 (the default) turns the option off.

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

Saved successfully!

Ooh no, something went wrong!