An event flag is a process synchronization primitive in the OpenVMS operating system. It has two possible states, set or cleared. The following basic primitive operations are provided:
- Set event flag ($SETEF)
- Clear event flag ($CLREF)
- Wait for event flag ($WAITFR)--if the flag was clear, this would make the process wait until it was set. If the flag was already set, this would immediately return, leaving the flag set.
Additional synchronization operations are:
- $WFLOR--wait for any of the specified event flags to be set.
- $WFLAND--wait for all the specified event flags to be set.
Event flags can be either local (per-process) or common (accessible by more than one process). Each process has its own set of 64 local flags, numbered 0-63. It is also possible to associate the process with up to 2 sets of common event flags. These come in sets of 32 each, and the process can assign them numbers 64-95 or 96-127. They come into existence when the first process associates with them, and disappear when the last process removes its association.
Every potentially time-consuming asynchronous system call (QIO among others) includes an argument specifying the number of an event flag to set on completion.
Compare semaphore.
Famous quotes containing the words event and/or flag:
“We can glut ourselves with how-to-raise children information . . . strive to become more mature and aware but none of this will spare us from the . . . inevitability that some of the time we are going to fail our children. Because there is a big gap between knowing and doing. Because mature, aware people are imperfect too. Or because some current event in our life may so absorb or depress us that when our children need us we cannot come through.”
—Judith Viorst (20th century)
“Our flag is red, white and blue, but our nation is a rainbow—red, yellow, brown, black and white—and we’re all precious in God’s sight.”
—Jesse Jackson (b. 1941)