DPV Flags differ between the CODE-1 Plus G1CP transaction and the C1BM00 batch driver.

Operating System: z/OS, CICS

There is a discrepancy between with the DPV flag being returned by the CODE-1 Plus interactive (G1CP) and batch (C1BM00).  This discrepancy will occur when a house number belongs to both a street record and a high rise record and secondary data is not present on the input address.  As a rule, when both a street record range and a high rise are present for a house number, CODE-1 Plus will try to match to the most finite level which is the high rise record.  As an example, the following address/house number is listed as part of a street record range and as a high rise record:
House Range     E/O  ZIP  Z+4 Range   Rte       Typ
 2400                    B     27106 4600          C040     H
 2400-2498          E     27106 4606          C040    S
Using the G1CP transaction, this address will return a DPV flag of Y (it is located on the Delivery Point Validation database) and DPV footnotes of AABB:
AA :  Record matched the ZIP+4 database.
BB :  Record was matched to the DSF file.
However, in batch, DPV returns a flag of D (valid primary number; input missing for secondary number) and DPV footnote codes of AAN1
 AA :  Record matched the ZIP+4 database.
 N1 :  Secondary address number was missing.
The batch results are the correct results because CODE-1 Plus must try to match to the high rise record first and since secondary data is not included on the input address, DPV assumes secondary data is missing.
The reason for the discrepancy is normal and working as designed.  It is coded in this fashion In order to reduce memory constraints in CICS and only effects this street default scenario. Interactive (which calls C1MATCHI) handles default range processing different than the batch matchers (C1BM00 which calls C1MATCHB).


UPDATED:  April 5, 2017