When you are developing a message set, you can define the version of the message set as well as any other key information that must be associated with it. After the message set has been deployed, the Configuration Manager can be used to display the properties of the message set. These include the deployment and modification dates and times (the default information that is displayed) as well as any additional version or keyword information that you have set.
You can define information to give details of the message set that has been deployed; therefore, you can check that it is the message set that you expect.
You can set the version of the message set in the Version property. This is in the Documentation view of the message set.
You can also define a default message set version in the Default version tag of the message set preferences. All new message sets that are created after this has been set have this default applied to the Version property at the message set level.
Keywords must be defined in the Documentation property of the message set. These follow certain rules to ensure that the information can be parsed. The following is an example of what you can define in the Documentation property:
$MQSI Author=John Smith MQSI$ $MQSI Subflow 1 Version=v1.3.2 MQSI$
The following table contains the information that the Configuration Manager shows:
Message set name | |
Deployment Time | 28-Aug-2004 15:04 |
Modification Time | 28-Aug-2004 14:27 |
Version | v1.0 |
Author | John Smith |
Subflow 1 Version | v1.3.2 |
In this display, the version information has also been defined using the Version property of the object. If the version information has not been defined using the property, it is omitted from this display.
^$.|\<>?+*=&[]You can use these characters in the values that are associated with keywords; for example: