UF_CFI Files

A set of Open C API subroutines is available for accessing files. These
routines provide a "C" interface to NX Open C API routines and
native files.

CAUTION
We recommend that you use standard C functions for file and directory
manipulations in lieu of the cfi routines in this file. These routines
will all be impacted by the UGII_OPTION environment variable. In
particular file specifications returned by functions such as uc4576
may be converted to lower case if UGII_OPTION=lower is set.

NOTE
These functions would not work with file names and folder names of
NX Manager and Teamcenter Engineering.
Use routines from uf_ugmgr
for this purpose.

File types are used to identify the contents of a file and are also used
to determine the default extension for a file. Note that for many cases
several files will have different extensions but the same contents
(e.g. text files). Note that many types do not have a name. These are
usually variations on a different file format but with a different
extension.

The following are the restrictions on the length of various items:

File Names are limited to UF_CFI_MAX_FILE_NAME_LEN characters
File Extensions are limited to 4 characters
Directory specifications are limited to UF_CFI_MAX_PATH_NAME_LEN
characters
Full file specifications are limited to UF_CFI_MAX_PATH_NAME_LEN
characters

Many of the Open C API CFI routines request a file type (ftype) as
input. This type is used to determine the default extension for a file
if none is supplied. The system does not add an extension if one is
included in the filespec. A file type of zero does not use any
extension.
For description of file formats see table

Many of the Open C API CFI routines return negative error numbers.
For description of these errors see table