Message Sets: CWF properties for element reference and local element integer types

The CWF wire format properties for element reference and local element integer types.

The Custom Wire Format properties described here apply to:

  • Objects: Element Reference, Local Element
  • Integer schema types: byte, int, long, short, unsignedByte, unsignedInt, unsignedShort

Physical representation

Property Type Meaning
Physical Type Enumerated type Select one from the displayed list:
  • Integer. This equates to the data type SHORT or LONG in C, or the COMP, COMP-4, COMP-5, or BINARY numeric data type in COBOL.
  • Packed Decimal. Equates to the COMP-3 data type in COBOL.
  • External Decimal. Equates to the data type PIC 9 USAGE DISPLAY in COBOL.

The representation of numeric elements can be affected by the Encoding and CodedCharSetId attributes that are set for the IBM® MQ queue manager:

  • Elements that have Physical Type set to Integer and Packed Decimal are represented in the appropriate IBM MQ Encoding value.
  • Elements that have Physical Type set to External Decimal are represented in the IBM MQ CodedCharSetId value.
Length Integer Enter the number of bytes to specify the element length:
  • If you set the Physical Type to Integer, select 1, 2, or 4 (the default) from the displayed list.
  • If you have set Physical Type to Packed Decimal, enter a value between 1 and 6.
  • If you have set Physical Type to Extended Decimal, enter a value between 1 and 11.
Length Units Enumerated type Select the unit of length for the element or attribute. Select one of the following options from the displayed list (some physical types do not offer all these options):
  • Bytes.
  • Characters. The Length is given in characters. This means that the number of bytes that are processed in the bitstream depends on the code page of the characters that are being processed.
    • For a single-byte code page (SBCS CCSID) such as "latin-1" (CCSID 850), the number of bytes is equal to the number of characters.
    • For a double-byte code page (DBCS CCSID) such as "UTF-16" (CCSID 1200), the number of bytes is exactly twice the number of characters.
    • For a multibyte code page (MBCS CCSID) such as "UTF-8" (CCSID 1208), the number of bytes depends on the bitstream content. The parser reads one character at a time and determines whether the character comprises one or more bytes.
  • Character Units. This option specifies that the size of each character (in bytes) is determined by the code page of the message.
    • For single-byte and double-byte code pages, this option is identical to Characters.
    • For a multibyte code page, this option provides improved parsing performance by assuming that every character is encoded in the smallest character unit that the code page supports. However, this means that a message must contain only these characters if it is to be processed correctly. For example, in code page "UTF-8" (CCSID 1208), the minimum character unit is 1 byte; therefore, the parser can make a single read (of the number of bytes specified by the Length property) to fetch the entire message. The message must contain only characters that are encoded in 1-byte units.
  • End of Bitstream. All data up to the end of the bitstream is processed. This option is valid only if the element is the last in the message. If you select this value, you do not need to enter a value for the Length Count.

The default is Bytes.
Justification Enumerated type If you have set the Physical Type property to External Decimal, select Left Justify or Right Justify (the default value) from the list. If you have selected another value for Physical Type, this property is inactive.
Padding Character String The padding character is used to fill out the remaining character positions when the string length is less than the specified string size. If you have set the Physical Type property to Extended Decimal, and the Justification property is either Left Justify or Right Justify, specify this character in one of the following ways:
  • Select NUL, '0', or SPACE from the displayed list.
  • Enter a character between quotation marks; for example, "c" or 'c', where c is any alphanumeric character.
  • Enter a Unicode value in the form U+xxxx where xxxx is a Unicode value specified in hexadecimal. The maximum length of the string that you can enter is 10.
  • Enter a hexadecimal character in the form 0xYY, where YY is a hexadecimal value.
  • Enter a decimal byte value (from 0 to 255).

The choice of which of these padding character forms is used for an MRM element depends on the padding character that is required and whether the padding character is to be subject to data conversion. In most cases, the specification of a padding character in quotation marks is sufficient, and when this padding character is used, it is converted to the target code page of the output MRM message that is being generated. For example, when converting from ASCII to the code page 500, if you have specified U+0008 as your padding character, this is converted from 0x08 to 0x15, the ASCII and EBCDIC representations of 'back space'.

If a padding character is required that cannot easily be entered in the padding character field, the Unicode mnemonic format can be used to specify the required character. When used, this Unicode value is also converted to the target code page of the MRM message that is being generated.

If you are converting a message from one code page to another, ensure that the converted value of the padding character is valid for this code page. If the padding character cannot be represented in the target code page, it is replaced by a substitution character. The substitution character is fixed and its value depends on the specified target code page.

If a padding character is required that is not subject to data conversion, the hexadecimal or decimal format can be used and you then have the option of specifying an absolute value as a padding character that is inserted directly into the output message. If this format is used, ensure still that this value is valid for the code page of any output messages that are created using these MRM definitions.

Numeric representation

Property Type Meaning
Signed Check box Select (the default) or clear this property. This property is used with Sign Orientation.
Sign EBCDIC Custom Overpunched Check box If the Physical Type is set to External Decimal and the Signed EBCDIC Custom property is set, this indicates that the Sign EBCDIC Custom Overpunched representation is to be used within an ASCII environment. If this check box is not selected (the default), the Sign ASCII representation is used.

The setting of the Sign EBCDIC Custom Overpunched check box is appropriate only if the Sign Orientation property is set to Leading or Trailing (indicating that the element/attribute has an embedded sign representation).

The check box is not available if the element/attribute is unsigned (for example, if the Signed check box is not set).

Sign Orientation Enumerated type If you have set Physical Type to External Decimal and you have selected Signed, choose from the following options that represent the COBOL options for displaying numeric data:
  • Leading Overpunched. This option sets a bit in the first byte if the number is negative. No setting is made if the number is positive. For example, the ASCII hexadecimal representation of the number 22 is x'3232'. Using this option, the number +22 would be x'3232' and the number -22 would be x'7232'. The default value.
  • Leading Separate. This option sets the first byte of the element to '+' if the number is positive and to '-' if the number is negative. For this option, the length must include the sign byte.
  • Trailing Overpunched. This option sets a bit in the last byte if the number is negative. No setting is made if the number is positive. Using this option, the number +22 would be x'3232' and the number -22 would be x'3272'.
  • Trailing Separate. This option sets the last byte of the element to '+' if the number is positive and to '-' if the number is negative. For this option, the length must include the sign byte.
If you have set Physical Type to any other value, the value Not Applicable is set for you.

Representation of null values

Property Type Meaning
Encoding Null Enumerated type Select one of the following options from the displayed list:
  • NULLPadFill. This option is valid only if Physical Type is External Decimal. The field is filled with the value specified by the Padding Character. Encoding Null Value must be set to an empty string.
  • NULLLogicalValue. The Encoding Null Value is transformed to match the required format for the field. The default value.
  • NULLLiteralValue. The Encoding Null Value is directly substituted as if it is a string. You can specify a nonnumeric value for Encoding Null Value.
  • NULLLiteralFill. The field is filled with the value specified by the Encoding Null Value. Encoding Null Value must resolve to a single character.
Encoding Null Value String The use of this property depends on the Encoding Null property, except for NULLLiteralFill. The default value is zero.
If you set the Encoding Null property to NULLLiteralFill, the value must resolve to a single character. Set the character in one of the following ways:
  • Select SPACE, NUL, 0x00 or 0xFF from the displayed list
  • Enter a character between quotation marks, for example 'c' or "c", where c is any alphanumeric character.
  • Enter a hexadecimal character in the form 0xYY where YY is a hexadecimal value.
  • Enter a decimal character code in the form YY where YY is a decimal value.
  • Enter a Unicode value in the form U+xxxx where xxxx is a Unicode value specified in hexadecimal format.

Byte alignment

Property Type Meaning
Byte Alignment Enumerated type Specify how the object is aligned from the start of the message. Select one of:
  • 1 Bytes. The default value.
  • 2 Bytes
  • 4 Bytes
  • 8 Bytes
  • 16 Bytes
Leading Skip Count Integer Specify the number of bytes to skip before reading or writing this object. The default is 0, the minimum value is 0, and the maximum value is 999999. You can use this value to ignore unwanted fields in a structure, or to model a field defined by C or COBOL data which requires alignment on a 2, 4, 8 or 16 byte boundary. Specify the number of bytes to skip before reading or writing this object. When an output message is written, Skip Count bytes are assigned the value of the message set Byte Alignment Pad property.

For repeating objects, this property is applied to the first instance only.
Trailing Skip Count Integer Specify the number of bytes to skip after reading or writing this object. The default is 0, the minimum value is 0, and the maximum value is 999999. You can use this value to ignore unwanted fields in a structure, or to model a repeating structure containing fields which require alignment on a 2, 4, 8 or 16 byte boundary. When an output message is written, Skip Count bytes are assigned the value of the message set Byte Alignment Pad property.

For repeating objects, this property is applied to all instances.

Occurrences

Property Type Meaning
Repeat Reference Enumerated type Use this property if the object occurs multiple times, and the number of occurrences is given dynamically by a field earlier in the message. Select an integer object from the displayed list of integer objects that occur before this object in the structure of the message. The value of the selected integer specifies the number of occurrences of this object. If no objects are listed, there are no integer objects before this one in the message structure.

If a Repeat Reference is specified, it overrides any setting for the Max Occurs logical property when parsing and writing the message, but not for validation of the message.