jvalccyy.prop

The jvalccyy.prop file contains a number of configurable parameters for controlling the behavior of the JVC.

These parameters tell the JVC where to find other files that it uses, as well as specifying certain validation options.

When running a map that calls the JVC, the jvalccyy.prop file can be located in a directory of your choosing. Refer to the section How to specify jvalccyy.prop location for more details. If the jvalccyy.prop file is not found on start up, the JVC terminates with an error message.

Note that the recommended best practice is to use a single jvalccyy.prop file for each version of the pack. This is due to several factors, including performance considerations and the fact that jvalccyy.prop contains locations of various other components, such as BIC files, currency files, and XML metadata files. If there is a requirement to use different maps with different validation settings, then the JVC Validator override flags can be used to achieve this. Refer to the validate_messages section for details.

The parameters set by the jvalccyy.prop file include swift.pack.version=srgccyy

This is the current version of the Pack for Financial Payments and is not to be changed. It is used to validate that the correct version of jvalccyy.jar is used.

If this value does not match the version number contained in the jvalccyy.jar, the JVC terminates with an error message.

message.definition.directory

This parameter identifies the location of the metadata files used by the JVC for syntactic validation, and for enabling and disabling message-specific field level and Network Rule validation.
If the metadata files are not found in the specified location, the JVC will terminate with an error message.

rules.networkvalidation.enabled = true|false
  • true - The default value, and the recommended setting. It performs all syntax and semantic validation, including validation defined by the “special functions” in the SWIFT manuals (for example “Party Field Option J”, “Payments Reject/Return” and so forth).
  • false - Performs only basic syntax validation.
bic.file.enabled=true|false
  • true - Indicates that the BIC/BEI validation is required.
  • false - Default value. Indicates that BIC/BEI validation is not required
Note: If bic.file.enabled=false, then the following Network Rules are also disabled:
  • C05
  • E57
  • T27

bic.definition.file

This parameter identifies the location of the bic.xml lookup file used by the JVC for BIC/BEI validation.
If bic.file.enabled=true and the bic.xml file is not found, the JVC terminates with an error message.
If bic.file.enabled=false, the JVC does not attempt to open the bic.xml file.

countrycurrencycodes.definition.file

This parameter identifies the location of the currencycodedecimals.xml lookup file used by the JVC for Currency Code and Country Code validation.

ReportingMode=verbose|terse
  • verbose - This is the default value. Validation results and error messages are returned in a multi-line, XML-like syntax.
  • terse - Validation results and error messages are usually returned as a single line of plain text. Some messages may contain multiple lines, if they include data from a multi-line field that was in error.

validateCopyofFields=true|false

  • true - Causes validation to be performed on the CopyOfFields elements in message types MTn92, MTn95, and MTn96.
  • false - This is the default value. Causes CopyOfFields validation not to be performed.
FileActMode.enabled=true|false
Controls the validation for Tag 51A in MTs 101, 102, 103, 103_REMIT, 104, 107, and 416. No other MTs, Tags, or validation rules are affected.
  • true - Enable FileAct mode, and allow Tag 51A to be present.
  • false - Disable FileAct mode, and return error code D63 if Tag 51A is present.
Note: If FileActMode.enabled is not present in jvalccyy.prop, or is present but contains any other value, validation checking defaults to FileActMode.enabled=false.
MessageLength.enabled=true|false
Controls the validation for message length for all MT messages.
  • true – Enable message length validation and return error code M50 if the message exceeds the permitted length.
  • false – Disable message length checking.
Note: If MessageLength.enabled is not present in jvalccyy.prop, or is present but contains any other value, validation checking will default to MessageLength.enabled=true.
icm.validation.enabled=true|false
  • true - ISO 20022 Contingency Measures (ICM) validation is performed based upon the SWIFT document Contingency Processing for Category 1 and 2 Payment Instruction Messages - Additional Network Validated Rules published on February 21, 2025.

    The MT message will be subjected to additional rules that ensure the MT payment instruction message can be accurately converted to its ISO 20022 equivalent.

  • false - This is the default value. ICM validation is not performed.

rules.icm.baseclass

Indicates the base class name used for ICM validation. The default value shown here should not be changed: com.ibm.websphere.dtx.ip.swift.srgccyy.validation

rules.icm.MTnnn

Indicates the rules that are to be validated for a particular message. The rule name (for example ICMC44) is appended to the BaseClass to obtain the class to use. For example: com.ibm.websphere.dtx.ip.swift.srgccyy.validation.ICMC44

checkE76.CCY=ccyymmdd

where CCY is a former European currency used in E76 error validation, and ccyymmdd is the value date after which this currency must not be used. These parameters should not be changed in normal operation.

rules.marketpractice.enabled=true|false
  • true - Market Practice validation is performed based upon the SWIFT document V1.1 published August 26, 2002.
  • false - This is the default value. Market Practice validation is not performed.
SWIFT has discontinued this document, therefore, this feature is no longer maintained.

rules.marketpractice.baseclass

Indicates the base class name used for Market Practice validation. The default value shown here should not be changed:
com.ibm.websphere.dtx.ip.swift.srgccyy .validation

rules.marketpractice.MTnnn

Indicates the rules that are to be validated for a particular message. The rule name (for example S101) is appended to the BaseClass to obtain the class to use. For example:
com.ibm.websphere.dtx.ip.swift.srgccyy.validation.S101

The following features are used for enabling and configuring basic Java logging capabilities:
  • log.enable=true|false - Default is false.
  • log.filename= Default value for swiftlog.txt
  • log.append=true|flase - Default is false.
  • log.filesize=1000000 - Maximum log file size in bytes before file is recycled.
  • log.level=ALL - Allowable values are OFF, ALL (default), SEVERE, WARNING, INFO, FINE

Editing will be required to change PACK_INSTALL_DIR with actual location where the pack zip distro was extracted.