The Custom Wire Format properties described here apply to:
Property | Type | Meaning |
---|---|---|
Physical Type | Enumerated type | Select one of the following from the drop-down list:
The representation of numeric elements can be affected by the Encoding and CodedCharSetId attributes that are set for the WebSphere MQ queue manager:
|
Length Count | Integer | Enter
the number of bytes to specify the element length:
|
Length Units | Enumerated type | Select the unit of length for the element or attribute.
Select one of the following options from the drop-down list (some physical
types do not offer all of these options):
The default is bytes. |
Signed | Boolean | Select (the default) or deselect this property. This property is used in conjunction with Sign Orientation. |
Sign EBCDIC Custom | Boolean | If the Physical Type is
set to External Decimal and
the Signed EBCDIC Custom property
is set, this indicates that the Sign EBCDIC Custom representation is to be
used within an ASCII environment. If this check box is not set (the default),
the Sign ASCII representation is used. The setting of the Sign EBCDIC Custom check box is only appropriate 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 disabled if the element/attribute is unsigned (for example, where 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:
|
String 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 drop-down list. If you have selected another value for Physical Type, this is 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 String Justification property
is either Left Justify or Right Justify, specify this character
in one of the following ways:
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 quotes 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, you should 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. This gives the option of specifying an absolute value as a padding character that is inserted directly into the output message. If this format is used, you should still aim to ensure that this value is valid for the code page of any output messages that are created using these MRM definitions. |
Property | Type | Meaning |
---|---|---|
Byte Alignment | Enumerated type | Specify how the object is aligned from the start of
the message. Select one of:
|
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. |