Clarification of Log Entries / Errors

[GoogleCodeExporter]

I have included a few of the entries from the Log below.  A file with 683 
records created nearly 4000 log entries.  The ones that concern me the most are:
"ERROR: Field of type 'callinglineinfo' could not be made"
"ERROR: Could not find field name 'callinglineinfo.'  We will continue 
processing this record, but the record will be corrupt"
"ERROR: Record has outgrown its stated length of 118. It is now 120"
"ERROR: Unknown modules id: 7 at 159.86 record type Record 1: Toll call or 
non-US" (appears for a variety of module id numbers)

I am running Version 1.3.1 running on Windows 2000 Server
I do not recall having so many log entries in the 1.2 version.

-------------------------------------------------------------------------
- 2010-09-23 23:37:38 INFO: Running Program
- 2010-09-23 23:37:38 INFO: Processing 900-BAF_2009-11-18_01h11_05_UTC started
- 2010-09-23 23:37:38 WARN: The year read from the baf file 2019 is greater 
than the current system year 110 assuming decade mismatch, subtracting 10 from 
baf file year
- 2010-09-23 23:37:38 ERROR: Field of type 'callinglineinfo' could not be made
- 2010-09-23 23:37:38 ERROR: Could not find field name 'callinglineinfo.'  We 
will continue processing this record, but the record will be corrupt
- 2010-09-23 23:37:38 ERROR: Record has outgrown its stated length of 118. It 
is now 120
- 2010-09-23 23:37:38 ERROR: Unknown modules id: 6 at 36.120 record type Record 
625: Interlata call
- 2010-09-23 23:37:38 ERROR: Record has outgrown its stated length of 118. It 
is now 122
- 2010-09-23 23:37:38 WARN: The year read from the baf file 2019 is greater 
than the current system year 110 assuming decade mismatch, subtracting 10 from 
baf file year
- 2010-09-23 23:37:38 WARN: The year read from the baf file 2019 is greater 
than the current system year 110 assuming decade mismatch, subtracting 10 from 
baf file year
- 2010-09-23 23:37:38 ERROR: Field of type 'callinglineinfo' could not be made
- 2010-09-23 23:37:38 ERROR: Could not find field name 'callinglineinfo.'  We 
will continue processing this record, but the record will be corrupt
- 2010-09-23 23:37:38 ERROR: Unknown modules id: 7 at 159.86 record type Record 
1: Toll call or non-US
- 2010-09-23 23:37:38 ERROR: Unknown modules id: 1 at 159.88 record type Record 
1: Toll call or non-US
- 2010-09-23 23:37:38 ERROR: Unknown modules id: 10 at 159.90 record type 
Record 1: Toll call or non-US

Original issue reported on code.google.com by bge...@gmail.com on 24 Sep 2010 at 7:49

Attachments:

• logs31.log

[GoogleCodeExporter]

Well the Warnings about the system year are because you are parsing a 2009 baf 
file in 2010.  Because its a different decade bafprp will try to fix the date 
automatically.  In general those are safe to ignore but its not advised to run 
baf files from different decades as the baf file only stores years as a single 
digit, and so figuring out the decade bafprp should use is a bit of an unneeded 
complication.

The Errors are concerning as they indicate a field has not been properly setup.
I looked into it and it seems like callinglineinfo is from a module definition 
for module 306.
For some reason the field is not defined yet it is declared as part of the 
module.  I will have to look at some documents and figure out what should be 
happening.

Original comment by charless...@gmail.com on 24 Sep 2010 at 8:14

• Changed state: Accepted
• Added labels: OpSys-All, Priority-High, Usability
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Original comment by charless...@gmail.com on 24 Sep 2010 at 8:18

[GoogleCodeExporter]

I committed a fix for the callinglineinfo problem.  It should now recognize the 
proper field type and name.  See if that will work for your baf files.

Original comment by charless...@gmail.com on 1 Oct 2010 at 5:36

• Changed state: Fixed

[GoogleCodeExporter]

Thanks for the quick response!  How do I download the updated version?  The 
most recent version on the download page appears to be from July.

Original comment by bge...@gmail.com on 1 Oct 2010 at 4:26

[GoogleCodeExporter]

I committed the changes to the source trunk of bafprp, you can checkout the 
source and build it to get the change.  Alternatively I attached a build I just 
made from the trunk to this issue.

Original comment by charless...@gmail.com on 1 Oct 2010 at 7:10

Attachments:

• bafprp.exe

[GoogleCodeExporter]

Works like a champ!  Thanks again for the quick turnaround.

Original comment by bge...@gmail.com on 5 Oct 2010 at 8:13

[GoogleCodeExporter]

Original comment by charless...@gmail.com on 5 Oct 2010 at 8:21

• Changed state: Verified