The ACH validation example demonstrates how to validate whether an ACH file conforms to
NACHA operating rules.
About this task
The base implementations are based on the ACH type tree rules and are not designed to
replace the use of the ACH type tree. This ACH validation example can be used to further investigate
any ACH type tree failures.
Procedure
-
Use the Design Studio to open the following map source file:
ach_validation.mms
-
Build all maps that are contained in the source file. Run the achval01
map.
-
Set all compiled maps with the
.mmc
extension.
-
Define the following directories for operating systems other than Windows:
-
When the artifacts listed here are copied to operating systems other than Windows, make certain that the FTP settings are set as
described in a and b:
- Set FTP settings to TEXT mode for the following input data:
- ach_sec_example.in
- ach_error_codes.txt
- Set FTP settings to BINARY mode for the following items:
- All compiled maps
- All XML schema files
- ach_config.xml
-
For MVS, edit the following map card setting of the to //DD:ddname where
ddname references the XML schema ach_config.xsd
- achval01asf
- input card #2 (ach_config.xsd)
- output card #1 (ach_parse_info.xsd)
- achval02
- output card #1 (ach_parse_info.xsd)
- achval03
- input card #1 (ach_validation_report.xsd)
- output card #1 (ach_validation_report.xsd)