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 default is Fixed Length String. |
Length Count | Button and Integer | If you have selected
a Physical Type of Fixed Length String or Binary, and have set Length Type to Count,
enter the number of length units for the element. The minimum value that you can specify is 0 (zero), the maximum value that you can specify is 2147483647 The default value is 0 (zero). |
Length Reference | Button and Enumerated type | If you have selected the length to be defined by Length Reference, select the name of
the Integer object that specifies the length of this object. Make your selection
from the drop-down list of Integer objects that are defined as siblings of
the current object, and occur before it in the structure of the message. For information about reordering elements, see Reordering objects. |
Length Units | Enumerated type | Subject to the Physical
Type that has been set, select one of the following from the
drop-down list:
The default is bytes. |
String Justification | Enumerated type | If you have set the Physical Type property to Fixed Length String, select Left Justify (the default value) or Right Justify from the drop-down list. If you have selected another value for Physical Type, this is property is inactive. |
Padding Character | String | If you have set the Physical Type property to Fixed Length String, and the String Justification property is either Left Justify or Right Justify, this property is applicable. When writing an output message, use the padding character to fill out the remaining character positions when the string length is less than the length implied by the Length Count or Length Reference property. Whether the string is padded from the left or the right is governed by the String Justification property. When parsing an input message, the padding character is trimmed from the end of the string. Whether the string is trimmed from the left or the right is governed by the String Justification property. 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. |
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ad15190_ |