validate_messages

The validate messages map can be used to start the JVC. It can be found in install_dir/mt/jvc/maps/validate_messages

This map can be incorporated directly into your workflow, or adapted to meet your needs. It can also be called from another map by using the RUN command. The map has one input and two output cards:
  • Input Card 1 - SWIFT message, which is defined as blob type tree.
  • Output Card 1 - Validator settings for defining pack version number (do not change in normal operation), validator flags, and jvalccyy.prop location.
  • Output Card 2: ValidatorResults. This card is used to call the JVC by use of the JVCWrapper validate method. It uses parameters from Output Card 1 to collect the validation results.

Validator flags can be used to modify the behavior of the JVC. They are specified as a single eight-character string, and the position within the string determines which flag is being set. The meaning and usage of each flag is shown in the table.

Position Name Allowable Values Description
1 Preload Definitions 0 Load message definitions as needed (recommended).
    1 Preload all message definitions
2 Map Server Mode 0 Enforce normal CRLF checking (recommended)
    1 Use <NL> as a line delimiter instead of <CR><LF>
3 Network Rules 0 Do not enforce network rules
    1 Enforce network rules
    2 Check jvalccyy.prop to determine if network rules enforced
4 Check Methods 0 Do not enforce field-level rules
    1 Enforce field-level rules
    2 Check metadata file to determine if field-level rules enforced
5 BIC Validation 0 Do not enforce BIC validation
    1 Enforce BIC validation
    2 Check jvalccyy.prop to determine if BIC validation enforced
6 Market Practice 0 Enforce market practice rules
    1 Do not enforce market practice rules
    2 Check jvalccyy.prop to determine if market practice rules enforced
7 FileActMode 0 FileActMode is disabled
    1 FileActMode is enabled
    2 Check jvalccyy.prop to determine FileActMode
8 MessageLength 0 MessageLength check is disabled
    1 MessageLength check is enabled
    2 Check jvalccyy.prop to determine MessageLength

Use a value of 0 or 1, for example, for the Network Rules, BIC Validation, or Market Practice flags in order to override the settings that are specified in the jvalccyy.prop file. This lets different maps, or map instances, that are in the same directory to use different validation criteria. For example, one map or map instance can enforce BIC validation, while another has BIC validation disabled.

Note that the flags are positional, and that the character position determines which parameter is being acted on. For example, to override the value for Flag position 8 (Message Length), all 7 previous Flags must also be supplied.

For backward compatibility with earlier pack versions, only the first six Flags are mandatory for Flag overrides. If only six flags are supplied, the remaining two flags default to the behavior that existed before the two parameter overrides were introduced, as follows:
  • Flag 7 FileActMode=false
  • Flag 8 MessageLength=true