4. MemCom 6 and MemCom 7 C API
functions
The MemCom 6 C API was based on the
Fortran library, whereas the MemCom 7 C API
is a completely re-designed, native C API. The tables below give a
summary of some MemCom 6 C API functions and
their MemCom 7 counterparts.
Table C.1. C API DB functions translation table
| MemCom 6 | MemCom 7 | Notes |
| MCC_dssndb | mcDBresSuperset | mcDBresSuperset creates a
super-set but, unlike in MemCom 6,
does not initialize it with a pre-set value. To initialize the
set, call the function mcDBinitSet. Note that
mcDBresSuperset flags an error if the set
already exists. |
| MCC_dsskdb | mcDBresSuperset | mcDBresSuperset creates a
super-set but, unlike in MemCom 6,
does not initialize it with a pre-set value. To initialize the
set, call the function mcDBinitSet. |
| MCC_enddb | mcDBcloseFile | - |
| MCC_exisdb | mcDBisFile | mcDBisFile(name) returns 1 if the DB
file exists and is a MemCom DB file,
or 0 if the DB file exists but is not a
MemCom DB file, or -1 if
name does not exists). |
| MCC_getdb | mcDBgetSet | mcDBgetSet retrieves whole sets,
whereas mcDBgetSubset retrieves
sub-sets. |
| MCC_getkdb | mcDBgetSet | Character data are treated in the same function as
numeric data. mcDBgetSet retrieves whole K
sets, whereas mcDBgetSubset retrieves K
sub-sets. |
| MCC_inqsdb | mcDBinqSetAtt | mcDBinqSetAtt(handle,name,NULL)
returns 1 if the set exists and 0 else. |
| MCC_lgtdb | mcDBinqSetAtt | Attributes are now extracted from the dataset attribute
structure. |
| MCC_opdidb | mcDBopenFile | - |
| MCC_putdb | mcDBputSet | mcDBputSet stores whole sets,
whereas mcDBputSubet stores sub-sets. |
| MCC_putkdb | mcDBputSet | mcDBputSet stores whole K sets,
whereas mcDBputSubet stores K
sub-sets. |
