Binary Large Objects (BLOBs) are not supported in Windows-based systems. BLOBs are valid for MCP-based systems only.
An external BLOB is a string primitive object based on the Glb.BinaryFile template that contains a reference to an external binary file. If it is marked as persistent in a class, the path is stored in the DMSII database as a DMSII recognized data type.
User processes can create an external BLOB and, provided the BLOB is marked as persistent, the external file path can be stored in the database.
An Internal BLOB is a persistent binary primitive object that contains a binary file. The file is stored in the DMSII database as a DMSII recognized data type.
User processes can create an internal BLOB and the binary file can be stored in the database and retrieved from the database.
Users are responsible for managing the actual BLOB file and its contents.
Limitations
External and Internal BLOBs cannot be used to define parameters.
BLOBs cannot be extracted using the Extract command or Write method.
BLOBs cannot be read from an extract file using the Determine Actual or ForEach commands.
A BLOB’s multiplicity can be either class or singleton but not vector and array. That is, Multiplicity must be less than or equal to 1.
BLOBs cannot be used for specifying a key for a class or a profile.
BLOB file contents cannot be presented in a form.