Configuring Your VeriMove Installation - VeriMove

The settings in the VeriMove config.ini configuration file (Windows, Unix, Linux) or sampcnfg configuration file (z/OS) determine how VeriMove processes your files.

If you are a new VeriMove user, the installation program installs the config.ini configuration file as part of the normal installation process.
If you are an existing VeriMove user, the installation program installs the config.ini.distribute configuration file into the installation directory and leaves your original config.ini configuration file intact.

You can process with VeriMove using the default settings in the config.ini file or you can change the settings in the config.ini file to conform to your specific installation site requirements.

Note: The configuration file includes preset values tested for optimum performance across platforms. Changing the preset values may adversely affect your system performance. Precisely recommends you consult with a Technical Support Representative or Professional Services Representative before changing any preset default values.

Refer to the table below for information on populating your config.ini configuration file.

Table 1. Configuration File Properties
Property	Description
General Attributes (All Environments)
Registered Company	Name of the PAF registered company.
Registered User	Name of the PAF registered user.
NCOA^Link Key	NCOA^Link key assigned to you by Precisely.
SerialNumber	Serial number assigned to you by Precisely.
NCOA^Link Platform ID	Four-character platform ID assigned by the USPS.
Licensee	Customer name as you want it to appear on the reports sent to the USPS.
NCOA^Link License Type	Type of NCOA^Link license: 0 Full Service Provider 1 Limited Service Provider 2 End User
Report Attributes (Windows, Unix, and Linux Only)
ReportPath	Path name for generated report files.
Matching Attributes (All Environments)
Business Name Matching Enhancements	Business Name Matching level. 0 Use the standard Business Name Matching process. The default value is 0. 1 Use the enhanced Business Name Matching process. This option, using additional algorithms, may improve Business Name Matching for a small cost in performance and slightly slower run times.
Internal CASS Processing Attributes (Windows, Unix, and Linux Only)
CASSSerialNumber	CASS serial number that Precisely assigned to you. If you are a new VeriMove customer, your CASS serial number is included with your product shipment. If you are an existing VeriMove customer and want to continue using external CASS processing, specify your current CASS serial number. If you are an existing VeriMove Unix or Linux customer using external CASS processing and you want to start using the VeriMove internal CASS processor, contact your Technical Support Representative for your CASS serial number. If you decide to switch from external CASS processing to the VeriMove internal CASS processor, in accordance with your USPS license agreement, you must recertify your current VeriMove configuration with the USPS. Your Technical Support Representative can answer any questions you may have on recertifying with the USPS.
DPVKey	To perform DPV processing using the VeriMove internal CASS processor, specify your DPV product software key as provided by Precisely.
LACSKey	To perform LACS^Link processing using the VeriMove internal CASS processor, specify your LACS^Link product software key as provided by Precisely.
DPVMemory	(Optional) Memory model for DPV processing: P Pico. Stores no data in memory. No tables or indexes are loaded. U Ultra-small. Stores no data in memory. Partial indexes are loaded. S Small M Medium L Large H Huge. Stores all data in memory. blank or missing — Defaults to: S — When you specify NCOA Use High Memory=0 (default value for NCOA Use High Memory) H — When you specify NCOA Use High Memory=1
LACSLinkMemory	(Optional) Indicates the memory model for LACS^Link processing: P Pico. Stores no data in memory. No tables or indexes are loaded. U Ultra-small. Stores no data in memory. Partial indexes are loaded. S Small M Medium L Large H Huge. Stores all data in memory. blank or missing — Defaults to: S — When you specify NCOA Use High Memory=0 (default value for NCOA Use High Memory) L — When you specify NCOA Use High Memory=1
SuiteLinkMemory	(Optional) Indicates the memory model for Suite^Link processing: P Pico. Stores no data in memory. No tables or indexes are loaded. U Ultra-small. Stores no data in memory. Partial indexes are loaded. S Small M Medium L Large H Huge. Stores all data in memory. blank or missing — Defaults to: S — When you specify NCOA Use High Memory=0 (default value for NCOA Use High Memory) L — When you specify NCOA Use High Memory=1
High Memory Attributes (All Environments)
NCOA Use High Memory	Specify whether to use high memory using these codes: 0 Turns off the large memory model. This is referred to as the small memory model. Use this option when only a small amount of limited real memory is available to you. The default value is 0. 1 Turns on the large memory model. A large number of data files are loaded into memory to improve performance. Use this option only if you have enough free real memory available (see note below). Note: When using the large memory model and internal CASS processing, VeriMove uses approximately 1.7 GB of memory. When using the large memory model and external CASS processing, VeriMove uses approximately 1 GB of memory. For HP-UX Unix, if you are running on an Itanium based machine, the large memory model will not work for NCOA^Link processing. Set this option to 0. When VeriMove is set to "Large Memory Model" (NCOA Use High Memory=1), DPV, LACS^Link and Suite^Link are configured to the "L" (Large) memory model. When VeriMove is set to "Small Memory Model" (NCOA Use High Memory=0), DPV, LACS^Link and Suite^Link are configured to the "U" (Ultra) memory model. It is recommended that you sort your list(s) in ZIP Code order to achieve optimum performance.
Small Memory Attributes (All Environments)
SmallMemEnh	This feature enhances the small memory model only. To turn on the small memory model, specify configuration variable NCOA Use High Memory = 0. To turn on the small memory model enhancement, you must also specify SmallMemEnh=1. The small memory model enhancement may provide a performance gain when running in small memory model if your list is sorted in ZIP Code order. If your list is sorted in ZIP Code order and there are a large number of records within the same ZIP Code segment (first two digits of the ZIP Code), you can use the small memory model enhancement to have VeriMove load an entire segment into memory and perform memory lookups for each record. This process may improve performance by not performing an I/O lookup on disk for each record. Specify whether to use the small memory model enhancement: 0 Do not use the small memory model enhancement. The default value is 0. 1 Use the small memory model enhancement for a potential performance enhancement. Note: To use the small memory model, specify configuration variable NCOA Use High Memory = 0. It is recommended that you sort your list(s) in ZIP Code order to achieve optimum performance.
Internal Diagnostic Attributes (All Environments)
NCOA Logging	Used for internal diagnostics. The default value is 0.
Footnote Legend (All Environments)
NCOA Footnote Legend	Defines the appearance of the NCOA^Link Footnote Statistics section in the NCOA^Link Processing Summary Report. 0 The NCOA^Link Footnote Statistics section in the NCOA^Link Processing Summary Report does not include a description for each footnote. 1 The NCOA^Link Footnote Statistics section in the NCOA^Link Processing Summary Report includes a short text description for each footnote. The default value is 1. For information on how the NCOA^Link Footnote Statistics section displays in the NCOA^Link Processing Summary Report, see the section "NCOA^Link Footnote Statistics" in Chapter 6, Reports in your VeriMove User's Guide.
Database Attributes (All Environments)
NCOA Use Flat Single	Specifies whether to use a single (vs. 26 A-Z) flat file database. 0 Use the 26 flat file A-Z database. 1 Use the single flat file database.
NCOA Use Flat Hash	Determines whether to use the 26 hash files that are used to do a quick test to see if the full data needs to be looked up. The hash files are not strictly necessary for the operation of the flat file database, since a single lookup is done to get all information. Most tests, however, show that using the flat hash files improves performance. 0 Do not use the flat hash files. 1 Use the flat hash files (default value).
Thread Interval Attributes (All Environments)
Interval Input	Frequency of the input thread gaining control of processing. The default value is 6. The recommended range is from 0 to 100. CAUTION: A change to this value can impact throughput, wait time, and CPU usage. Precisely recommends you consult with a Technical Support Representative or Professional Services Representative before changing this value. Note: The smaller the value specified, the more frequently the thread awakens to determine if work is available. A guideline for the Input Thread is to be 1-3 times greater than the value specified for the NCOA Thread to allow for queue transfer to NCOA Thread.
Interval NCOA	Frequency of the NCOA thread gaining control of processing. The default value is 2. The recommended range is from 0 to 100. CAUTION: A change to this value can impact throughput, wait time, and CPU usage. Precisely recommends you consult with a Technical Support Representative or Professional Services Representative before changing this value. Note: The smaller the value specified, the more frequently the thread awakens to determine if work is available. The NCOA Thread should always be kept at a low value. This thread should rarely sleep, and for very short periods of time, to avoid impacting performance.
Interval Move	Reserved for future use.
Interval Output	Frequency of the output thread gaining control of processing. The default value is 8. The recommended range is from 0 to 100. CAUTION: A change to this value can impact throughput, wait time, and CPU usage. Precisely recommends you consult with a Technical Support Representative or Professional Services Representative before changing this value. Note: The smaller the value specified, the more frequently the thread awakens to determine if work is available. A guideline for the Output Thread is to be 2-4 times greater than the value of the NCOA Thread to avoid excessive wakes.
Queue Size Attributes (All Environments)
Queue Size Input	Number of input records that can be processed through the input thread before the queued records are passed to the next processing step. The default value is 3000. CAUTION: A change to this value can impact throughput and memory usage. Precisely recommends you consult with a Technical Support Representative or Professional Services Representative before changing this value. Note: The recommended range is from 200-50,000 in 100 record increments. The queues are held in memory. The higher the queue size specified, the more memory that will be required.
Queue Size Job Input	Number of input records VeriMove processes through the input thread before passing the records to preliminary NCOA^Link move prequalification processing. The default value is 3000. CAUTION: A change to this value can impact throughput and memory usage. Precisely recommends you consult with a Technical Support Representative or Professional Services Representative before changing this value. Note: The recommended range is from 200-50,000 in 100 record increments. The queues are held in memory. The higher the queue size specified, the more memory that will be required. A general guideline is for the size to match the queue size of the input queue.
Queue Size NCOA	Number of prequalified records passed to the move thread or to the output thread. The default value is 4000. CAUTION: A change to this value can impact throughput and memory usage. Precisely recommends you consult with a Technical Support Representative or Professional Services Representative before changing this value. Note: The recommended range is from 200-50,000 in 100 record increments. The queues are held in memory. The higher the queue size specified, the more memory that will be required. A general guideline is for the size to be two times the queue size of the job queue.
Queue Size Move	Reserved for future use.
Queue Size Output	Number of output records that can be written to the output file including move and non-move records. The default value is 3000. CAUTION: A change to this value can impact throughput and memory usage. Precisely recommends you consult with a Technical Support Representative or Professional Services Representative before changing this value. Note: The recommended range is from 200-50,000 in 100 record increments. The queues are held in memory. The higher the queue size specified, the more memory that will be required. A general guideline is for the size to be equal to the queue size of the job queue.
Mainframe Upload Attributes (z/OS Only)
UploadSourceFolderUSPS	This is the folder on the Windows computer that will contain the NCOA^Link data that has been decompressed and is ready to upload to the mainframe. For information on the NCOA^Link data installation process, see Installing NCOALink Data on Windows and z/OS.
UploadSourceFolderVeriMove	The folder on the Windows computer that contains the VeriMove data files to be uploaded to the mainframe. Generally this will be the same as UploadSourceFolderUSPS.
File Allocation Attributes for Sequential Datasets (z/OS Only)
UploadSeqTargetPrefixUSPS	High level qualifier to be prepended to the file names of the NCOA^Link sequential datasets.
UploadSeqTargetPrefixVeriMove	High level qualifier to be prepended to the file names of the VeriMove sequential datasets.
UploadSeqTargetSuffix	(Optional) Value to append to file names when creating sequential datasets.
UploadSeqTargetVolumes	(Optional) Volume serial number(s) used for allocating sequential datasets.
UploadSeqTargetUnit	Device unit to use when allocating sequential datasets. For example, "SYSDA" or "3390".
UploadSeqRetainFor	(Optional) The number of days to retain the sequential files uploaded to the mainframe. If you specify this parameter, do not specify the UploadSeqRetainTo parameter.
UploadSeqRetainTo	(Optional) The day that uploaded sequential files will expire, in the format YYYYDDD (Julian format). If you specify this parameter, do not specify the UploadSeqRetainFor parameter.
File Allocation Attributes for VSAM RRDS Datasets (z/OS Only)
UploadRRDSTargetPrefixUSPS	High level qualifier to be prepended to the names of the USPS VSAM RRDS datasets.
UploadRRDSTargetPrefixVeriMove	High level qualifier to be prepended to the names of the VeriMove VSAM RRDS datasets.
UploadRRDSTargetVolumes	List of volumes to use when allocating VSAM RRDS datasets. The list can be either comma or space separated.
UploadRRDSRetainFor	(Optional) The number of days to retain the VSAM RRDS files uploaded to the mainframe. If you specify this parameter, do not specify the UploadRRDSRetainTo parameter.
UploadRRDSRetainTo	(Optional) The day that uploaded VSAM RRDS files will expire, in the format YYYYDDD. If you specify this parameter, do not specify the UploadRRDSRetainFor parameter.