BES Logs ... What's in them? Part 16 of 20 (Pending.exe BRK Tool)
Posted 07-11-2009 at 05:00 AM by hdawg
Tags bes log, blackberry logs, blackberry resource kit, brk, pending, pending brk, pending messages, pending.exe
Welcome to Part 16 of the 20 part series looking at the BES logs (Part 15) ... the BRK Tool Pending.exe.
No surprise here, but that the Pending.exe tool tracks user accounts with a pending count that is higher than the pending count specified.
To utilize Pending.exe you need only the BlackBerry Messaging Agent log and the tool itself. The Pending tool parses the MAGT log, and while I can't speak to the exact logic it uses when parsing I can tell you how the output it creates correlates to the data in the BlackBerry Messaging Agent log. The actual output is comma separated, so unlike the PhoneCall / PIN / SMS logs you don't need to do any Unicode to ANSI conversion to read them easily in Excel.
Like all BRK tools the version of the tool needs to match the version of the log file it is processing. In the example below, I've got logs from an Exchange BES 4.1 SP6. Don't forget, all command line driven, so open up a command prompt and cd to the directory where you've got the log file and tool.
Syntax
First, we look at the actual syntax of the command. The required elements are the platform and users. In my example below I'm using an Exchange log wanting to get a report for all users with all pending stats. When I'm looking for a specific user I'll insert just that email address instead of using the all flag ... or i'll isolate the time window ... or the minimum pending count I'm looking for; lots of options. The output comes a little bit quicker ... but for my test here the MAGT log was 51MB for 114 total users and processed in 3 seconds; so we're not talking much time either way.
Result
Below is the output for just testuser1@port3101.org. Had I ran the command Pending.exe -p E -u testuser1@port3101.org this would have been all of the output in the file; so I simply filtered out the user data for this example. Every entry in the data shown here correlates to exactly 1 line in the MAGT log ... my output created 6034 entries ... again not bad for 114 users and 3 seconds of work. Each line is a point in time reference to how many messages are pending for that user, that's it.
Raw Data from DISP Log
As promised, here is how it all correlates with a snip from the MAGT log ... specifically line 4 of the above data at 6:33:43:
____________________
[40435] (07/01 06:33:43.343):{0x344} {testuser1@port3101.org} Queuing new mail through notification. EntryId=14634941. Msgs Pending 15
____________________
Nothing all that crazy, but it is certainly valuable. The one thing that I really like is the high value mark for that user indicated with an asterisk; a good way to identify possible problems. Based on the time of day of the Pending count; I'd be willing to bet that the user is out of coverage ... which I could use the OutOfCoverage.exe tool to figure out.
No surprise here, but that the Pending.exe tool tracks user accounts with a pending count that is higher than the pending count specified.
To utilize Pending.exe you need only the BlackBerry Messaging Agent log and the tool itself. The Pending tool parses the MAGT log, and while I can't speak to the exact logic it uses when parsing I can tell you how the output it creates correlates to the data in the BlackBerry Messaging Agent log. The actual output is comma separated, so unlike the PhoneCall / PIN / SMS logs you don't need to do any Unicode to ANSI conversion to read them easily in Excel.
Like all BRK tools the version of the tool needs to match the version of the log file it is processing. In the example below, I've got logs from an Exchange BES 4.1 SP6. Don't forget, all command line driven, so open up a command prompt and cd to the directory where you've got the log file and tool.
Syntax
First, we look at the actual syntax of the command. The required elements are the platform and users. In my example below I'm using an Exchange log wanting to get a report for all users with all pending stats. When I'm looking for a specific user I'll insert just that email address instead of using the all flag ... or i'll isolate the time window ... or the minimum pending count I'm looking for; lots of options. The output comes a little bit quicker ... but for my test here the MAGT log was 51MB for 114 total users and processed in 3 seconds; so we're not talking much time either way.
Result
Below is the output for just testuser1@port3101.org. Had I ran the command Pending.exe -p E -u testuser1@port3101.org this would have been all of the output in the file; so I simply filtered out the user data for this example. Every entry in the data shown here correlates to exactly 1 line in the MAGT log ... my output created 6034 entries ... again not bad for 114 users and 3 seconds of work. Each line is a point in time reference to how many messages are pending for that user, that's it.
Raw Data from DISP Log
As promised, here is how it all correlates with a snip from the MAGT log ... specifically line 4 of the above data at 6:33:43:
____________________
[40435] (07/01 06:33:43.343):{0x344} {testuser1@port3101.org} Queuing new mail through notification. EntryId=14634941. Msgs Pending 15
____________________
Nothing all that crazy, but it is certainly valuable. The one thing that I really like is the high value mark for that user indicated with an asterisk; a good way to identify possible problems. Based on the time of day of the Pending count; I'd be willing to bet that the user is out of coverage ... which I could use the OutOfCoverage.exe tool to figure out.
Total Comments 0
