HMF Tutorial: Scheduling CP Messages

HMF schedules one-time and recurring events such as reminders, CP messages, and XAUTOLOG.

On this page we will learn about scheduling CP Messages via HMF.

Background -- Section 1 of 4

CP Messages via HMF have have an advantage over Reminders if you want the personal event to be listed under the sender instead of the receiver of the message, and/or if you need complete control over the message text. Please note that CP Messages via HMF must be authorized by the HMF administrator. To enable this HMF capability, contact the HMF administrator (Wayne T. Smith -- WTS@Maine.edu).

You can define, alter and delete your own scheduled CP Messages, once you are authorized. A full-screen interface is available to work with HMF personal events; use the HMF command to see this full-screen interface. There is also a programmers interface. However, in this tutorial, we'll exclusively use a third interface: the command-line interface.

Members of the UNET Administrative Programming and System Programming groups are setup to work with CP Message personal events.

Syntax of related commands -- Section 2 of 4

HMF commands are entered via the CP "SMSG HMFSERVE AT *" command prefix.

To list all personal events

Query MYevent
displays your personal events.
FOR userid Query MYevent
displays all personal events for the specified userid.
Query MYevent SHOW ALL
displays your personal events with all attributes. (Some attributes such as TASKID are not listed via the default query output).

To define a new CP Message personal event

AT time ON date CP Msg message_text
defines a one-time or recurring CP Message, depending on the format of "date".

where ...

time
"hh:mm:ss" causes an HMF CP Message to be sent at the specified time.
date
defines the day(s) that the one-time or recurring CP Message will be sent to you.

The date may be expressed as ...

yy/mm/dd
With "yy/mm/dd", yy, mm, and/or dd may be replaced with an asterisk (*) to cause the CP Message to recur.
*
With a date of "*", the CP Message recurs daily, forever.
ddd or ddd*
If the date is MON, TUE, WED, ... the CP Message is displayed once on the specified day. Adding an asterisk (*) to the day (MON*, etc.) causes the CP Message to recur once every week on the specified day, forever.
dddn or dddn*
If the date is MON2, TUE3, WED4, ... the CP Message is displayed once on the specified day of the specified week. Adding an asterisk (*) to the specification (MON1*, SAT3*, etc.) causes the CP Message to recur once a month, forever.
LWD
The CP Message recurs on the last working day of every month.
WD
The CP Message recurs on every weekday (Monday through Friday).
WE
The CP Message recurs on every weekend day (Saturday/Sunday).

If the "ON date" parameter is omitted, the CP Message will be sent (once) at the next occurance of "time".

To alter a personal event

Use the "ALter refid" command. For more information, please see the HMF User's Guide and Reference book.

To remove/delete a personal event

DELete refid
discards the specified CP Message. To obtain the "refid", use the "Query MYevent" command.

An example -- Section 3 of 4

Let's say we need to send a CP Message to ADMGROVR once each week to run a program. This is easily accomplished with:

cp sm hmfserve at * at 02:30 on sat* CP M ADMGROVR EXEC MYPROG

But we can do better! They above command places the event in the senders MyEvent queue. It might be better to keep all ADMGROVR messages in the ADMGROVR MyEvent queue. To accomplish this, we use the "FOR" command (all on one line of one command):

cp sm hmfserve at * for admgrovr at 02:30 on sat* CP M ADMGROVR EXEC MYPROG

To see the event we just added, we use this command:

cp sm hmfserve for admgrovr q myevent

References -- Section 4 of 4


Go to An Introduction to the HMF REMINDER facilities   Next

This is An Introduction to HMF CP Message scheduling   Next

Go to An Introduction to the HMF XAUTOLOG facilities   Next


Valid HTML 4.01! Valid CSS!

Copyright © University of Maine System, 2001. Wayne T. Smith
This page was most recently revised on Monday, June 20, 2005
Your comments and suggestions are most welcome!