Table 1 defines the properties that you can set for the message set. Some of the message set properties (marked with an asterisk (*)) are relevant only if the message being processed is not using WebSphere® MQ as the transport protocol. If the transport protocol is WebSphere MQ, values are derived from the message headers (for example, MQMD), and the message set properties, if set, are ignored.
| Property | Type | Meaning |
|---|---|---|
| Boolean True Value | String | Enter up to eight hexadecimal digits. Do not include the hexadecimal indicator (0x) preceding this number. Each digit is a half byte. The maximum length is 4 bytes. You must enter an even number of digits (a whole number of bytes). This value must be different from, but the same length as, the Boolean False Value. The default value is 00000001. |
| Boolean False Value | String | Enter up to eight hexadecimal digits. Do not include the hexadecimal indicator (0x) preceding this number. Each digit is a half byte. The maximum length is 4 bytes. You must enter an even number of digits (a whole number of bytes). This value must be different from, but the same length as, the Boolean True Value. The default value is 00000000. |
| Boolean Null Value | String | Enter up to eight hexadecimal digits. Do not include the hexadecimal indicator (0x) preceding this number. Each digit is a half byte. The maximum length is 4 bytes. You must enter an even number of digits (a whole number of bytes). This value can be the same as either Boolean True Value or Boolean False Value, or different. The default value is 00000000. |
| Property | Type | Meaning |
|---|---|---|
| Packed Decimal Positive Code | Enumerated Type | Select the positive sign used for packed decimal numbers from the drop-down list. The default is C, which indicates that 0x0C is used as the positive sign, which is the usual value. You can also select F, which indicates that 0x0F is used as the positive sign: some systems require this setting. |
These settings are used when messages are being serialized.
| Property | Type | Meaning |
|---|---|---|
| Byte Alignment Pad | String | If the xsd:element Custom Wire Format properties Byte
Alignment, Leading Skip Count, and Trailing
Skip Count cause bytes to be skipped in the bit stream when the message
is serialized, this property supplies the character to be used in the skipped
positions. Set this character in one of the following ways:
|
| Policy for Missing Elements | String | The setting of this property governs the action when
fields are missing from the message tree when the message is serialized:
|
| Property | Type | Meaning |
|---|---|---|
| Derive default dateTime format from logical type | Button | Select this option if the dateTime format that will be used is to be taken from the dateTime format specified in the properties of an object that has one of the dateTime types. For example, a type gDay. |
| Use default dateTime Format | Button and dateTime | Select this option if you want to specify a dateTime
format that is different from the logical dateTime format. Specify the default format for objects of type dateTime for this physical format. You can override this property for a dateTime object within a complex type. The initial value for this property is yyyy-MM-dd'T'HH:mm:ssZZZ, which you can change by over-typing. For more information about dateTime formats, see DateTime formats. |
| Century Window | Integer | This property determines how two-digit years are interpreted.
Specify the two digits that start a 100-year window that contains the current
year. For example, if you specify 89, and the current year is 2002, all two-digit
dates are interpreted as being in the range 1989 to 2088. The initial value is 53, which you can change by over-typing. |
| Days in First Week of Year | Enumerated Type | Specify the number of days of the new year that must
fall within the first week. The start of a year usually falls in the middle of a week. If the number of days in that week is less than the value specified here, the week is considered to be the last week of the previous year; hence week 1 starts some days into the new year. Otherwise it is considered to be the first week of the new year; hence week 1 starts some days before the new year. Select a number from the drop-down list. The initial value is 4. |
| First Day of Week | Enumerated Type | Specify the day on which each new week starts. Select a value from the drop-down list. The initial value is Monday. |
| Strict DateTime Checking | Check box | Select this option if you want to restrict dateTimes to a valid dateTime format. This will not allow 35th March to be processed as 4th April, and 10:79 to be processed as 11:19. If Strict DateTime Checking is set, receiving an incorrect dateTime will cause an error. The default is to not to restrict dateTimes. |
| Time Zone | Enumerated Type | The value that you set for this property is used if the value that you specified for the Default DateTime Format property does not include Time Zone information. |
| Daylight Savings Time | Check box | Select this option if the area in the Time Zone property
observes daylight savings time. If it does not observe daylight savings time,
this option should not be selected. For example, if an area is selected in Time Zone and this option is not selected, the value passed will represent the time zone without the daylight savings time. Default is not to observe daylight savings time. |
The settings in the Table 3 are used only for messages with no MQMD.
| Property | Type | Meaning |
|---|---|---|
| Default CCSID* | Integer | Enter a numerical value for the default Coded Character
Set Identifier. The default is 500. If the input message is a WebSphere MQ message, the equivalent attribute set for the queue manager is used and this property is ignored. |
| Byte Order* | Enumerated Type | Select either Big Endian (the default)
or Little Endian from the drop-down list to specify the byte
order of numbers that are represented as binary integers. In C, this is equivalent to data type short or long. In COBOL, this is equivalent to a PIC 9 COMP, COMP-4, COMP-5 or BINARY data type. Your choice must match the encoding with which messages are created. Big Endian is normally the correct option for messages created on UNIX® or z/OS®, Little Endian for Windows®. This property is not used if the message is received across the WebSphere MQ transport protocol: in this case, the property is deduced from the MQMD of the message. |
| Packed Decimal Byte Order* | Enumerated Type | Select either Big Endian (the default)
or Little Endian from the drop-down list to specify the byte
order of numbers that are represented as packed decimal. In COBOL, this is
equivalent to PIC 9 COMP-3 data type. (There is no equivalent data type in
C.) Your choice must match the encoding with which messages are created. Big Endian is normally the correct option for messages created on UNIX or z/OS, Little Endian for Windows NT®. |
| Float Format* | Enumerated Type | Select one of S390 (the default), IEEE, or Reverse IEEE from the drop-down list to specify the byte order of numbers in the message that are represented as floating point. |