Custom rule sets

[lstsaur]

Contact your IBM Account Manager to get the current CASS database files because it's not stored in the same place as all other software that can be downloaded. It's a pain!

[kennyapril]

asked the admin and got the current database files which are used for the reference.

so when I use CASS stage to correct the address the input from a file should
be addr1,addr2,addr3,city,state,zip

In the properties of CASS stage
there is a folder form3553 under this folder there are 3 fields to be filled.

one is company name,list identifier,output file.

Is there any specific file from which the date is taken.?

[pattemk]

ISD Job? what is an ISD Job? and how do you specify the parameter to 10000?

please advice

[quote="JRodriguez"]Kennyapril,

Reading through your post look like you just need a QS job with a CASS std stage exposed as a service using ISD


CASS don't return all addresses from the USPS reference database that match the address provided. It just return the input address with the enhancement from the process when a match is found in the reference database

Also be aware that when using CASS in a ISD job you must set the maximum runtime parameter to 10000 for the job. This allow to restart the job every 2 1/2 hours and ensures that the job retrieves the most current CASS data that is installed. (CASS data expired every 105 days)

The good news is that an ISD job could use expired data (This is the only way to reuse an expired database ) :D[/quote]

[rjdickson]

The expiration date is encrypted and part of the reference files. There is no way to extend the life of the files you are using - you must download the latest.

By the way, the 105 day expiration is a USPS requirement, not an IBM requirement.

[lstsaur]

Kenny,
Just ignore those 3 fileds for Form 3553 since you are not seeking the discount from USPS.

[kennyapril]

Actually these fields were filled in the previous jobs designed by other developer.

do you think I also need to fill them,If they are related to discount from USPS?

Thanks,

[lstsaur]

Kenny,
Sorry, forgot to mention that you can also populate any junk you wish in those 3 fields.

[kennyapril]

Thanks Istsaur

So ignore them or fill them with anything........doesn't matter right?

[stuartjvnorton]

Thanks Istsaur

So ignore them or fill them with anything........doesn't matter right?

Uh, I think that any downstream jobs that use your results are the place to go for answers to that question, not some internet forum.

[kennyapril]

Thanks for the Information.

In the job I used CASS stage for correcting the address,So is it something when the input is any address the output will be a correct address.

Coming to standardized stage,After using the CASS stage the next stage I use is standardize stage to standardize the correct address.

please suggest me is this the right flow to get the output required?
(output required is- the addresses which are standardized from the correct address)

[ray.wurlod]

There's no way we can address that issue (pun not intended). Where are your test data? Do your actual results comply with your expected results?

[kennyapril]

Actually first I designed a service using only CASS stage,i.e only to correct the address.
so when I test his service with soap UI tool

the request which I sent is

<addr_line1>1800 holand dr</addr_line1>
<city>somerset</city>
<state>NJ</state>
<zip>08873</zip>

and the response I received is

<addr_line1>1800 holand dr</addr_line1>
<city>somerset</city>
<state>NJ</state>
<zip>8873</zip>
<zip5_cass xsi:nil="true"/>
<zip4_cass xsi:nil="true"/>
<deliverypoint_cass xsi:nil="true"/>
<deliverypointchkdigit_cass xsi:nil="true"/>
<carrierroute_cass xsi:nil="true"/>
<city_cass xsi:nil="true"/>
<state_cass xsi:nil="true"/>
<urbanization_cass xsi:nil="true"/>
<recipient_cass xsi:nil="true"/>
<deliveryaddressline1_cass>1800 holand dr</deliveryaddressline1_cass>
<deliveryaddressline2_cass xsi:nil="true"/>
<lacindicator_cass xsi:nil="true"/>
<dpvmatchflag_cass xsi:nil="true"/>
<dpvcommflag_cass xsi:nil="true"/>
<dpvfpflag_cass xsi:nil="true"/>
<dpvcode1_cass>A1</dpvcode1_cass>
<dpvcode2_cass xsi:nil="true"/>
<dpvcode3_cass xsi:nil="true"/>
<lacsflag_cass xsi:nil="true"/>
<lacsreturncode_cass xsi:nil="true"/>
I dont see any difference in the address given,that was a wrong address with spelling mistake in the street name and did not get the correct response.

please rectify my mistake!!

Thanks,

[stuartjvnorton]

Looking at that, it has obviously said it can't verify the address.
But you should know that, based on DPV code 1, and the fact that you should have the doco for the CASS stage and will understand the output codes.

I did a quick online check of that using QAS and it verified it fine. So maybe there is an issue with your CASS setup. ?

Is that the only test you have done? Does it verify other addresses that are entered correctly? Others that have minor mistakes?

[rjdickson]

Did you define your zip code field as numeric? Numeric fields will get stripped of their leading zeroes. Try varchar and let us know how you make out.

By the way, the USPS site does not like the address without the leading zero, or WITH the leading zero either.

[kennyapril]

In the documentation given by IBM along with the tool I did not find the CASS stage document in quality stage guide.

Some of the addresses entered return with the zip code with addition of 4
but none of the entered wrong address is not giving the response as the correct address.

I changed the datatype for zip to varchar but no change in the output.

any suggestions please?