18.08.2013 Views

Features of LINC Generate - Public Support Login - Unisys

Features of LINC Generate - Public Support Login - Unisys

Features of LINC Generate - Public Support Login - Unisys

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.

New <strong>Features</strong> for MCP Based <strong>LINC</strong> Systems<br />

$ Be transferred using other <strong>Generate</strong> Sets (using the Configure <strong>Generate</strong> set field on<br />

the Transfer Selection screen)<br />

$ Be defined as base systems for Model <strong>LINC</strong> Systems<br />

If the <strong>Generate</strong> Set used to configure your <strong>LINC</strong> System is a BNA <strong>Generate</strong> Set, it must be<br />

the same <strong>Generate</strong> Set used to generate the <strong>LINC</strong> System. This restriction ensures that all<br />

DMS files are compatible.<br />

Specifying Sort Memory<br />

In <strong>LINC</strong> Release 16.3, you can specify the amount <strong>of</strong> sort memory to be used when<br />

database reorganizations are required. This new feature will improve the times taken to<br />

perform reorganizations, especially <strong>of</strong> large databases.<br />

The Allowedcore field has been added to the A Series <strong>Generate</strong> Options screen to enable<br />

you to enter the amount <strong>of</strong> memory to use. The A Series <strong>Generate</strong> Options screen is<br />

described in your <strong>LINC</strong> <strong>Generate</strong> Operations Guide. Similar fields have been added to the<br />

Environment Options screen <strong>of</strong> the Configure Utility and the Home screen <strong>of</strong> the Database<br />

Management Utility (DMU).<br />

Before using this feature, you should check the hardware your site is using can provide the<br />

amount <strong>of</strong> memory you intend to use.<br />

The default value for the Allowedcore field is 0 (zero), which means that a default value <strong>of</strong><br />

12,000 words per reorganization task (the same as in releases prior to <strong>LINC</strong> Release 16.3) is<br />

used.<br />

Avoiding Unplanned Reorganizations<br />

In <strong>LINC</strong> Release 16.3, you can take advantage <strong>of</strong> the DASDL options POPULATIONINCR<br />

and POPULATIONWARN to reduce unplanned reorganizations when database structures<br />

reach their logical capacity. These options enable you to automatically increase the<br />

population <strong>of</strong> a structure, or to request a warning when the population approaches the<br />

limit.<br />

For a generated <strong>LINC</strong> System, or a <strong>LINC</strong> System configured using a Configure <strong>Generate</strong><br />

Set, the population options can be set for the entire database, or for individual Ispecs (the<br />

Event set is considered as a single Ispec). For a <strong>LINC</strong> System configured using the <strong>LINC</strong><br />

Configure Utility, the options can be changed only for the entire database. You can use<br />

DMU to set the options for the database, individual Ispecs, or the Event set.<br />

See your MCP Based <strong>LINC</strong> Administration and Operations Guide for generation issues.<br />

Improved Offline Reorganizations<br />

1-10 v

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

Saved successfully!

Ooh no, something went wrong!