LAYVER

1. How do I verify a portion of a displayed group?

This is possible using the LAYVER dialog option. Run-decks will need to filter edge-related violations.

2. Can I optimize verification speed?

There are a number of factors which determine the rate at which databases are analyzed. Built in to LAYVER are certain algorithms and methods that ensure fast handling of data, however, some issues are processor related. These may be controlled by the user using variables which can be defined in the configuration file. The variables with values that work well for Windows XP systems are:

wrkBufferSize = 16384
wrkClusterSize = 4

3. Why are temporary layers not deleted?

In recent releases, major advances in verification speed have been made. As part of these improvements the option to delete temporary layers (those declared with an asterisk prefix) is left to the user. The verification deck now requires the command:

$DELETE LAYERS * /TEMPORARY

if temporary files are to be deleted. Alternatively, temporary files may be deleted immediately after use, where very large databases are involved.

4. Can I execute operating system commands from within LAYED?

Yes, the command $SPAWN is available for this. Particularly useful is the fact that it will run MSDOS batch files and respond depending on the status of the return variable.

5. Can I include date and time stamping in the report files?

Yes, special variables are set to allow this (LV_TIME and LV_DATE). Other variables additional information that the user might want to include in a formal report file.

6. The run-deck I have is not an ASCII file – what is it?

Matricus develops run-decks for certain technologies. Much of the data is protected by confidentiality agreements the details of which are unknown to Matricus. The run-decks are thus developed such that this information is inaccessible to the user. The decks are delivered as encrypted files which can be decrypted by LAYVER prior to execution.

7. What’s the list of files at the start of the LAYVER summary?

LAYVER decks are often a sequence of files whose execution is determined by process flow variables (switch variables). As a syntax check, LAYVER scans the files and expands the files and arguments, checking file existence and reporting the actual command that will be issued. In some cases files do not exist at the start of syntax checking (since they are created during the checking sequence). To avoid halting the process, the variable LayverIncludeCheck must be set as follows:

.define LayverIncludeCheck 0