Persistence
Use this property to specify whether the message survives after the queue manager is restarted. Restarts might occur because of a system failure or because the queue manager has been manually restarted.
Persistent and non-persistent messages can reside on the same queue.
For input and request links, select one value from the list. This value is then set in the message header. The default value is As in queue definition.
For output links, select one or more values by clicking within the property and then select the appropriate check boxes. When you finish, click outside of the property. There is no default value. If this value is blank for an output link, this property is not used for filtering messages.
You can use different ways to specify this value for input links and output links:
- Specify the value at the job level. You type the value in this property, which sets the value at design time for all messages in this job. If, for some reason, you also specify the data element as a column in the schema (see below), the data element takes precedence over the property.
- For input links, you can specify the value at the message level.
Instead of this property, you specify a column in the schema for this
value by selecting the corresponding value (see below) as the Data
element value on the Columns tab. The
value that is stored in each incoming message is then used during
runtime processing when it is put on the queue. The value in the input
link schema overrides the design-time value of this property at runtime.
For output links, you can view only the value in the Data element column that was retrieved when the message was read from the queue. Generally speaking, you use the data element on an output link when you plan to use this value later on in your job processing.
The data element for this property is WSMQ.PERSISTENCE.