Mail And Database Verifying

You are an administrator and you are tired of your mail user because they
always call you saying that they are no more able to use their mail database
because they have loaded it! Don't worry! This code sends and log a message to
the administrator and the user if the user have overpass his mail database
capacity.
You will need a new database (that I name "Mail verifying"). That database will
contain these elements : 2 forms, 2 views and 2 agents. It should be on the
same server who contains the databases to analyse. The reason is that the
database have to look in the Log.NSF Database server's. Also, make sure that
the agent is signed with the server.id.

Form #1
This form will act as a pilot table where the administrator control the sending
messages and it is created for the profile document. For my personnal usage, I
name it "PilotTable". There are 7 fields in it.

Field #1: AdminMessage (Text field)
This field contain's a message to advertise the administrator when a database
have overpass the fixed capacity.
If there is no message, the adminstrator won't receive a message

Field #2: Admin (Text field)
Put in this field all administrators names who want's and advertise

Field #3: UserMessage (Text field)
This field contains a message to advertise the user that his mail database have
overpass the fixed capacity.
Same as AdminMessage, if there is no message, the user won't receive a message

Field #4: Capacity (Number field)
This field contain the maximum value that a database should get (expressed in
Mb)

Field #5: UserExclusion (Text field)
This field contain all users or databases that the administrator want's to
exclude from the maximum capacity

Field #6: LogServer (Text field)
If the "MailVerifying" database is not on the local server or is on another
server, the adminstrator will have to insert the name of the server where it
should analyse the databases.

Field #7 : DataBaseType (Keywords)
The Keywords are :
Mail | 1
Database | 0
Both | -1

Don't forget the pipes! The first keyword tell the agent that only Mail
databases should be analyse. The second tell the agent that only Databases
(excluding Mail databases) should be analyse. "Both" tell's the agent that it
have to process on all databases (Mail and Database)

Form #1
This form contains a log on all database who overpass the fixed capacity. I
name'd it "MessageLog". There are 6 fields in it.

Field #1: SendWhen (Date Time field)
This field contain's the date log overpass database

Field #2: Who (Text field)
This field contain's the user name overpass database

Field #3: UserMessage (Text field)
This field contain's the advertising user message in the "PilotTable" form

Field #4: Admin (Text field)
This field contain's all administrator who wanted a feedback message (field
Admin in "PilotTable" form)

Field #5: AdminMessage (Text field)
This field contain's the advertising administrator message in the "PilotTable"
form

Field #6 : DataBaseType (Keywords)
This field contain's the database type:
Mail | 1
Database | 0

The Views

View #1: Advertise User Mail
This view contain's all documents sent to Mail database Users
The selection formula is: SELECT DataBaseType = "1"
The first row contain this formula: @Text (SendWhen; "S0D3")
The second row contain this field: Who
The third row contain this field: Admin

View #2: Advertise for Database
This view contain's all documents for overpass Database
The selection formula is: SELECT DataBaseType = "0"
The first row contain this formula: @Text (SendWhen; "S0D3")
The second row contain this field: Admin

For both views put an action button that retreive the "PilotTable" form. Here's
the code: @Command([EditProfile]; "PilotTable"). I name it "Parameter modifying"


The Agents
The best part of the database and the one who should be view by all the people
who wants that program.

Agent #1: As I say before, this agent open the Log.NSF database to retreive
helpfull informations. It takes information in the Profile document and deliver
messages to the administrator and user. It also log's in the database all
information so the administrator will be able to retrace the overpass databases.

This agent should run periodically on the server. Don't forget to sign the
agent with the server.i
This was first published in November 2000

Dig deeper on Domino Resources

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