The isupdemo startup processes are:
The following table describes the program startup process for isupdemo:
|
Step |
Action |
|
1 |
At startup, the main thread parses the command line arguments, setting global variables based on the results of this parsing. |
|
2 |
The user, test, HMI, UDP, and ISUP threads are started. |
|
3 |
Incoming and outgoing threads are started. |
The following table describes the primary startup process for isupdemo:
|
Step |
Action |
|
1 |
Upon receipt of the HMI_EVN_NOWPRIMARY event from the Health Management service, the HMI thread issues an EVT_PRIMARY event to the ISUP thread. |
|
2 |
When the ISUP thread receives this event, it generates an application ready message to the mate application. |
|
3 |
When an application ready message is received, the primary application initiates a batch checkpoint to the backup application. |
The following table describes the backup startup process for isupdemo:
|
Step |
Action |
|
1 |
Upon receipt of the HMI_EVN_NOWBACKUP event from the Health Management service, the HMI thread issues an EVT_BACKUP event to the ISUP thread. |
|
2 |
When the ISUP thread receives this event, it generates an application ready message to the mate application. |
|
3 |
If an application ready message is received, the backup application again sends an application ready message to the primary application. |