OpenTP1 Version 7 Operation
If MHP terminates abnormally, the receive message of MHP that terminated abnormally can be re-scheduled at the beginning of the schedule queue by shutting down the scheduling of the service group automatically. However, the receive message of MHP cannot be re-queued at full recovery.
In the application attribute definition, specify the following:
mcfaalcap -g srvghold = s recvmsg = r -d holdlimit = 1 |
The handling of the message of the abnormally terminated MHP differs depending on the specification of the service group automatic shutdown. The following table shows the message handling at abnormal termination.
Table 3-1 Message handling at abnormal termination
Specification of application attribute definition | Memory queue | Disk queue | ||
---|---|---|---|---|
Automatic shutdown of service group scheduling specified (srvghold=s) | Rescheduling specified (recvmsg=r) | Maximum error count reached | ERREVT2#1 | Scheduling wait status#2 |
Maximum error count not reached | ERREVT2 or ERREVT3 | ERREVT2 or ERREVT3 | ||
Rescheduling not specified (recvmsg=e or omitted) | ERREVT2 or ERREVT3 | ERREVT2 or ERREVT3 | ||
Automatic shutdown of service group scheduling not specified (srvghold=m or omitted) | ERREVT2 or ERREVT3 | ERREVT2 or ERREVT3 |
Tables 3-2 and 3-3 show the handling of the messages arrived before and after the service group scheduling is automatically shut down.
Table 3-2 Handling of disk queue messages
Shutdown type | Timing | |
---|---|---|
Messages arrived before shutdown and put into the input queue | Messages arrived after shutdown | |
Shutdown of both input and scheduling | Placed in scheduling wait status. After release of the shutdown, MHP is started. | Put into the input queue for ERREVT2. |
Shutdown of input | MHP is started. | Put into the input queue for ERREVT2. |
Shutdown of scheduling | Placed in scheduling wait status. After release of the shutdown, MHP is started. | Put into the input queue and placed in scheduling wait status. |
Table 3-3 Handling of memory queue messages
Shutdown type | Timing | |
---|---|---|
Messages arrived before shutdown and put into the input queue | Messages arrived after shutdown | |
Shutdown of both input and scheduling | Put into the input queue for ERREVT2 again. | Put into the input queue for ERREVT2. |
Shutdown of input | MHP is started. | Put into the input queue for ERREVT2. |
Shutdown of scheduling | Put into the input queue for ERREVT2 again. | Put into the input queue for ERREVT2. |
Tables 3-4 and 3-5 show the handling of the messages that shut down an application or service.
Table 3-4 Handling of messages at application shutdown
Shutdown type | Timing | |
---|---|---|
Messages arrived before shutdown and put into the input queue | Messages arrived after shutdown | |
Shutdown of both input and scheduling | Put into the input queue for ERREVT2 again. | Put into the input queue for ERREVT2. |
Shutdown of input | MHP is started. | Put into the input queue for ERREVT2. |
Shutdown of scheduling | Put into the input queue for ERREVT2 again. | Put into the input queue for ERREVT2. |
Table 3-5 Handling of messages at service shutdown
Shutdown type | Timing | |
---|---|---|
Messages arrived before shutdown and put into the input queue | Messages arrived after shutdown | |
Shutdown of both input and scheduling | Put into the input queue for ERREVT2 again. | Put into the input queue for ERREVT2. |
Shutdown of input | MHP is started. | Put into the input queue for ERREVT2. |
Shutdown of scheduling | Put into the input queue for ERREVT2 again. | Put into the input queue for ERREVT2. |
All Rights Reserved. Copyright (C) 2006, 2010, Hitachi, Ltd.