This indicates whether the message survives system failures and restarts of the queue manager. For the MQPUT and MQPUT1 calls, the value must be one of the following:
When a persistent message is sent to a remote queue, a store-and-forward mechanism holds the message at each queue manager along the route to the destination, until the message is known to have arrived at the next queue manager.
Persistent messages cannot be placed on:
Persistent messages can be placed on permanent dynamic queues, and predefined queues.
In the case of NPMCLASS (HIGH) queues nonpersistent messages survive a normal queue manager shutdown and restart.
In the case of shared queues, nonpersistent messages survive queue manager restarts in the queue-sharing group, but do not survive failures of the coupling facility used to store messages on the shared queues.
The value of DefPersistence is copied into the Persistence field when the message is placed on the destination queue. If DefPersistence is changed subsequently, messages that have already been placed on the queue are not affected.
If there is more than one definition in the queue-name resolution path, the default persistence is taken from the value of this attribute in the first definition in the path. This can be:
The value of DefPersistence is copied into the Persistence field when the message is put. If DefPersistence is changed subsequently, messages that have already been put are not affected.
Both persistent and nonpersistent messages can exist on the same queue.
When replying to a message, applications must use the persistence of the request message for the reply message.
For an MQGET call, the value returned is either MQPER_PERSISTENT or MQPER_NOT_PERSISTENT.
This is an output field for the MQGET call, and an input field for the MQPUT and MQPUT1 calls. The initial value of this field is MQPER_PERSISTENCE_AS_Q_DEF.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
js01325 |