Sybase DC38133-01-0902-01 Current database must be granted Remote permissions using, Specified

Argument	Description
send_time	An optional string containing a time specification
	with the following meaning:
	♦ If frequency is SEND EVERY, specifies a length
	of time between messages.
	♦ If frequency is SEND AT, specifies a time of day
	at which messages will be sent.
	If no frequency is specified, the Message Agent sends
	messages, and then stops.

See also	“sp_revoke_remote procedure” on page 432
	“GRANT REMOTE statement” on page 366
Description	In a SQL Remote installation, each database receiving messages from the
	current database must be granted REMOTE permissions using the
	sp_grant_remote procedure.
	The remote user is identified by a message system, identifying the method
	by which messages are sent to and received from the consolidated user. The
	address-name must be a valid address for the message-system, enclosed in
	single quotes.
	The sp_grant_remote procedure is required for the remote database to
	receive messages, but does not by itself subscribe the remote user to any
	data. To subscribe to data, a subscription must be created for the user ID to
	one of the publications in the current database.
	The optional frequency argument specifies a frequency at which messages
	are sent. The send_time argument contains a time that is a length of time
	between messages (for SEND EVERY) or a time of day at which messages
	are sent (for SEND AT). With SEND AT, messages are sent once per day.
	If no frequency argument is supplied, the Message Agent processes
	messages, and then stops. In order to run the Message Agent continuously,
	you must ensure that every user with REMOTE permission has a frequency
	specified.
	It is anticipated that at many consolidated databases, the Message Agent will
	be run continuously, so that all remote databases would have a frequency
	argument specified. A typical setup may involve sending messages to laptop
	users daily (SEND AT) and to remote servers every hour or two (SEND
	EVERY). You should use as few different times as possible, for efficiency.
Example

394