Troubleshooting the pesky out of office agent

This tip describes troubleshooting the out of office agent.

If you've been pestered by users complaining that their out-of-office agent didn't run while they we away you may find this helpful.

In most cases the agent didn't run because it wasn't scheduled or wasn't set to run on the correct server but it's difficult to check this after the event. Even if they are still scheduled you can't see them using 'tell amgr sched' as usually they will not appear until after midnight and disappear after they have run at 01:00.

Using this tip you will have a historical record of the agents scheduled to run on a server.


Create a program document to list the scheduled agents amd get it to run after midnight and before 01:00 - we use 00:20. The list of scheduled agents gets written to the server log.

The command line is ...

-c "te amgr sched"

Obviously the history covers the numbers of days you maintain in your server logs so this may just be 7 but it's usually enough.

This was first published in September 2002

Dig deeper on Domino Resources - Part 7

0 comments

Oldest 

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

-ADS BY GOOGLE

SearchWindowsServer

Search400

  • iSeries tutorials

    Search400.com's tutorials provide in-depth information on the iSeries. Our iSeries tutorials address areas you need to know about...

  • V6R1 upgrade planning checklist

    When upgrading to V6R1, make sure your software will be supported, your programs will function and the correct PTFs have been ...

  • Connecting multiple iSeries systems through DDM

    Working with databases over multiple iSeries systems can be simple when remotely connecting logical partitions with distributed ...

SearchEnterpriseLinux

SearchDataCenter

SearchExchange

SearchContentManagement

Close