Subj : Verson260A
To   : Kevin Klement
From : Peter Knapper
Date : Sat Apr 30 2005 10:45 am

Hi Kevin,

 KK> Binkley 260A has lost it's mind over here. I have downlinks that are
 KK> on "hold" because they poll or I dilivier via the internet.

Boy, its been a LONG time (8+ years???) since I used Dial Scripts to access the 
Internet from Bink, so some of my memory may be stuck back in time and have 
faded some what......;-) I can't find any of my old config for this around so 
if I remember correctly you need a Binkley Event file entry to run an event 
that causes Binkley to need to poll a Node via a Dialer Script that does the 
dialing work. 

The first thing I thought of is that as your events start after midnight, that 
suggests to me that Bink is re-reading your Events file at this time, and thats 
when things start going wrong, so something has likely changed in your events 
files thats causing this. The fact its a dialer script is probably a red 
herring, the critical part is "Why is the event being triggered in the first 
place?", and the driver for that is within your Events file. 

Roll back any recent changes you made to that file, also look for any events 
that might overlap in execution BEGIN/END time, particularly for things running 
past 24:00 hrs. If nothing is obvious, the next step is to clear out Binks 
compiled schedule and force a complete Binkley restart to see what happens.

So to roll things back to the very start (this process will re-run ALL events 
for today so be very careful), end Binkley, delete the Binkley.SCD file (this 
forces Binkley to "re-compile" that file and run EVERYTHING up until the  
"current" event time), then start Binkey again. What you want to see are which 
EVENTS are being run, and when they kick in. The Binkley LOG file for this will 
give you the clues... 

I suspect this may not show much at all, because it seems your problem may 
relate to the LAST EVENT OF THE DAY being run, so your problem wont be visible 
until Binkley does a natural roll over of the day. Also consider event entries 
which have recently been added or changed, or which have only just become 
ACTIVE (IE an event set to run after a certain date/time/day of week, etc...).

Lastly, a postig a copy of your .EVT file here may be useful.

Good luck..............pk.


--- Maximus/2 3.01
 * Origin: Another Good Point About OS/2 (3:772/1.10)

.