Often referred to as the MemQueue FC. The Memory Queue FC encapsulates the functionality of the TDI Memory Buffer Pipe (as present in the API) and provides a GUI to configure it. The FC contains two parts: the raw FC and the Config Editor (GUI) component. The raw FC encapsulates the calls to the memory buffer pipe. The GUI provides a way for the user to configure the behavior of a memory buffer pipe. The FC either returns a reference to the Memory Buffer Pipe object or reads/writes to it.
There can be multiple readers and writers for the same queue. Every writer has to obtain a lock before adding data . The writer has to release the lock before a reader can access it.
Direct usage of the Memory Queue FC is deprecated in this release. It is much easier and also recommended to use the Memory Queue Connector or directly use The system object to create a new pipe, add data to the pipe and put data into the pipe. APIs for this functionality have been exposed in the System Object.
The system object has a method called getFunction(string
name) that returns an initialized instance of the FC. The returned
object can be used to perform calls as in:
Using a simple call:
Using the Entry call:
The Memory Buffer Queue FC returns a reference to a Memory Buffer
Pipe for a null Entry object, performs a read operation on the Memory
Buffer Pipe for the empty Entry object and a write operation on the
Memory Buffer Queue for a non-empty Entry object.
The returned MemBufferQ object has two methods that can aid in
managing the object: purgeQueue() and deletePipe().
MemBufferQ pipe = system.getFunction("ibmdi.MemQueueFC").perform(null);
var inp = system.newEntry();
inp.setAttribute ("test", "this is a sample entry");
MemBufferQ pipe = system.getFunction("ibmdi.MemQueueFC").perform(inp);
See also