VERIFIED SOLUTION i

Why is MailStream Plus 8.3.7 finding less valid CRRT records in the walk sequence presort

Product Affected:  MailStream Plus™ 8.3.7
Product Feature: Installation / Upgrade
Operating System: ALL Platforms
 
Why you see the difference is now in MailStream Plus (MSP) 8.3.7, the software does a better validation of the walk sequence (WS) values when using the ZIP IN parameter with the value C in position 44.
C     Ignore the Carrier Route information on this record if the WS/LOT information is blank or is an unmatched address WS/LOT containing all zeros.
 
In MSP 8.3.6, the software only checked for all spaces or all zeroes and ignored everything else.
In MSP 8.3.7 the software will:
  • Pull the 5 bytes of the walk sequence location, position 36 of the ZIP IN parameter and right-justify the value. 
  • Then  MSP will add leading zeros and verify that the values are numeric. 
  • Now the software can handle scenarios when the walk sequence values posted is only 4 bytes as some vendors only post a 4 byte walk sequence code. 
  • But MSP still treats this as a 5-byte field.  If a 4-byte walk sequence code is in the record and the 5th byte has a non-numeric value, this will cause MSP to consider this an invalid value and not a valid walk sequence code. 
 
For example in MSP 8.3.6 if the walk sequence value found 0000 in your walk sequence code location, this was not validated as a bad walk sequence code because it was neither all zeros or blank.

MSP 8.3.7 will right-justify it and add leading zeros, to make it 00000.  This is not a valid walk sequence value so, this record will not be part of the CRRT presort.
 
UPDATED:  March 12, 2019