DSXchange

Posted: **Tue Feb 16, 2016 6:46 am**

Hi All,

We encountered an artificial record and the CASS Job has failed with "Mechanically Generated Address" warning.

*** WARNING *** WARNING *** WARNING *** WARNING *** WARNING *** WARNING *** WARNING ***
APT_CombinedOperatorController,0: The CASS program has detected what appears to be a mechanicaly generated address.
APT_CombinedOperatorController,0: Processing continues without Delivery Point Validation (DPV) and LACS Link.
APT_CombinedOperatorController,0: and your company, please forward 1 file to IBM WebSphere QualityStage support group.
APT_CombinedOperatorController,0: Once the support group has received the file listed above and analyzed the information
APT_CombinedOperatorController,0: you will be contacted for further instructions.
APT_CombinedOperatorController,0: ERROR: Unable to open /DPVFALSE1
APT_CombinedOperatorController,0: Processing has aborted. Please make sure that the directory permisions are set for writing
APT_CombinedOperatorController,0: ???(29872):ERROR: vexit status=100

After the above error, we did try running other files and we were able to get the DPV/Lacs column generated from CASS stage.

The document says "we should reach to IBM Team to get the restart code after the above error"

Since we were able to test for other set of files what does "restoring the DPV/LCAS Processing after error" means here? Is it still an issue and we need to contact the IBM Team. Can someone please clarify on this.

Thanks in advance

Posted: **Tue Feb 16, 2016 7:15 am**

You need to contact IBM Support with the details.

Posted: **Wed Feb 17, 2016 5:48 am**

Thank you.
Before reaching to IBM support , we are mainly looking at the following details

1)We were able to run for other set of files. Does this means the DPV Processing is not locked yet?
2)Since this is the first time error, hence other files got processed?
3)Are there any other ways to find DPV Processing is working fine or issues - (right now looking at the dpv/lacs fields out of CASS)

Thanks

Posted: **Wed Feb 24, 2016 5:32 am**

DPV Process doesn't got locked irrespective of the previous false record as it was not creating the DPVFAlse or LACSFalse file either.

CASS DB was owned by root and when changed to dsadm , the false record run did created the DPVFalse file and locked the DPV processing to run further for any other valid files.

Now the DPV Processing is locked and we have reached the support team for further assistance.

Thanks.

Posted: **Tue Mar 01, 2016 5:34 am**

Support Team to has provided the unlock code and we were able to restart the DPV and LACS Process.

Thanks.

Posted: **Tue Mar 01, 2016 9:17 am**

Thanks for sharing the details.

DSXchange

CASS Stage - false positives records

CASS Stage - false positives records