****************************************************************************
****************************************************************************

BIRD ID#:       143
ISSUE TITLE:    Correcting the rules for AMI_Close
REQUESTOR:      Arpad Muranyi, Mentor Graphics
DATE SUBMITTED: 
DATE REVISED:   June 29, 2011
DATE ACCEPTED BY IBIS OPEN FORUM:

****************************************************************************
****************************************************************************

STATEMENT OF THE ISSUE:

The IBIS 5.0 specification defines the rules for AMI_Close so that it is
optional when AMI_GetWave doesn't exist in the model.  This results in
unnecessary complications regarding the rules of some other AMI function
arguments.  Making AMI_Close required for all situations would simplify
these rules in the specification and the job of model makers.

****************************************************************************

STATEMENT OF THE RESOLVED SPECIFICATIONS:


On pg. 181 replace these lines:


| The three functions can be included in the shared object library in one of
| the three following combinations:
|
|  Case 1: Shared library has AMI_Init, AMI_Getwave and AMI_Close.
|  Case 2: shared library has AMI_Init and AMI_Close.
|  Case 3: Shared library has only AMI_Init.
|
| Please note that the function ‘AMI_Init’ is always required.


with the following lines:


| The three functions can be included in the shared object library in one of
|* the following two combinations:
|
|  Case 1: Shared library has AMI_Init, AMI_Getwave and AMI_Close.
|  Case 2: shared library has AMI_Init and AMI_Close.
|
|* Please note that the functions 'AMI_Init' and 'AMI_Close' are always
|* required.


****************************************************************************

ANALYSIS PATH/DATA THAT LED TO SPECIFICATION:

Several questions were raised regarding memory allocation and de-allocation
while working on BIRD 137, and discussions revealed that making AMI_Close
always required would simplify the rules in the specification as well as
the rules for the model making process.
             
****************************************************************************

ANY OTHER BACKGROUND INFORMATION:

****************************************************************************