Overview of MQe message stores
Local queues and asynchronous remote queues store messages and therefore have properties to determine how and where the messages are stored.
The message store determines how the messages are mapped to the storage medium. The C and Java™ versions of MQe support a default message store, allowing long file names. The Java version of MQe has two additional message stores, MQeShortFilenameMessageStore that ensures the file name does not exceed eight characters, and the MQe4690ShortFilenameMessageStore that supports the default file system on a 4690. A storage adapter provides the message store access to the storage medium, the Java and C versions of MQe provide disk adapters with the Java version also providinges a case insensitive adapter and a memory adapter.
The backing store used by a queue can be changed using an MQe administration message. Changing the backing store is not allowed while the queue is active or contains messages. If the backing store used by the queue allows the messages to be recovered in the event of a system failure, then this allows MQe to assure the delivery of messages.