294
K
A
DAK
AMX 86 Procedures
Results (continued)
AERTNW = Task was not waiting for any of these signals. These
signals are now pending for the task. At least one of these
signals was already pending implying a signal overrun.
Variable siginfo can be examined to see which signals
caused the overrun.
Siginfo provides additional information concerning the results of the
signal. Bits 0 to 14 identify signal overruns. If any of these bits is set, it
implies that the task was not waiting for that task signal and that the task
signal was already pending.
Bits 16 to 30 of siginfo indicate which, if any, of all of the task's 15 task
signals remain pending after this ajsgnl call. Bits 16 to 30 correspond to
task signal bits 0 to 14 respectively.
An immediate task switch will occur if the task being signalled is of
higher priority than the current task and its signal wait condition has been
satisfied as a result of this call.
Note When signalling multiple task signals at once, it is possible to generate a
signal overrun and still get the AEROK or AERWAT result in status.
For example, if you generate task signals A and B and the task is waiting
for signal A and signal B is already pending, then status will return
AEROK because the task's signal wait condition has been satisfied.
However, an overrun on task signal B did occur and will be indicated in
variable siginfo.
If tsignals only specifies one task signal, then status completely
defines the result. You can replace &siginfo with NULL if so desired.
AEROK Task resumed
AERWKP Task not waiting; signal now pending
AERTNW Task not waiting; signal overrun
AMX procedure ajwake is a simplified form of procedure ajsgnl in
which one predefined private AMX task signal is used.
See Also ajsgwat,ajsgrd,ajsgres, ajwake