The messages that you listed are normal. If the
bpsched process wakes up and sees that the main
bpsched is already working you get the message that
you listed. You should be able to search the bpsched
for the policy that did not run and it should indicate
there why it didn't. Usually, the job was run manually
and so is not due again during the window but the
bpsched log should tell you what you need to know. 

Jeff Redington

=====
"A wise man once said 'Wherever you go, there you are'"
      -Mike Brady