| CRN 01189 | DELETE-ALARM |
| CRN 06122 | INHIBIT-ALARM |
| CRN 06123 | RELEASE-ALARM |
Response in case of an unsuccessful result of the execution, on operator request, of one of the following MMC-commands:
| CRN 00017 | MODIFY-ALARM-PARAM |
| CRN 00018 | DISPLAY-ALARM-PARAM |
| CRN 00019 | DISPLAY-ACTIVE-ALARMS |
| CRN 06140 | DISPLAY-LOADSH-THRESHLD |
| CRN 06141 | MODIFY-LOADSH-THRESHLD |
| CRN 07625 | SWITCH-ALARM-EXCEPT |
| CRN 07626 | CREATE-ALARM-EXCEPT |
| CRN 07627 | MODIFY-ALARM-EXCEPT |
| CRN 07628 | REMOVE-ALARM-EXCEPT |
| CRN 07629 | DISPLAY-ALARM-EXCEPT |
| CRN 07630 | MODIFY-ALCAT-PARAM |
| CRN 07631 | DISPLAY-ALCAT-PARAM |
SWA-ALARM HANDLING
(A)....................... (B).................
-----------------------------------------------------------------
ALMCAT = (1)
SOURCE+ALMTIME = (2) + (3)-(4) (5):(6):(7)
MAPLAMP = (8)
(9)... = (10)....
OPTION = (11)....
ACTIVE ALMCAT = (12)...
FUNCTION = (13) GROUP = (14)
(15)..............................................................
REPORT REFERENCE NUMBER = 0012
| Par. No. | Meaning | Remarks |
|---|---|---|
| (A) | Command name | |
| (B) | Main execution result | |
| (1) | Alarm category | see SI 054 |
| (2) | Reference to indicate the relation where the detected alarm is stored | source:
if source = 0 : relation R_ALRECE if source = 1 : relation R_SAHRECA |
| (3) | Moment of alarm detection; month | |
| (4) | Moment of alarm detection; day | |
| (5) | Moment of alarm detection; hour | |
| (6) | Moment of alarm detection; minute | |
| (7) | Moment of alarm detection; second | |
| (8) | Identification of any lamp on Master Alarm Panel (MAP) | see SI 106 |
| (9) | Kind of alarm type | |
| (10) | alarm type | see SI 006 or SI 007 |
| (11) | Option | Overview,Detailed,Startup,All |
| ALL | all = alrec+sahrec complete | |
| DETAILED | detailed= alrec+sahrec without
startup | |
| OVERVIEW | overview =default= only alrec
alarms | |
| STARTUP | startup = alrec+sahrec only
startup | |
| (12) | Active alarm category | |
| NORMAL (ALMCAT) | normal alarm category | |
| REDUCED (REDCAT) | reduced alarm category | |
| (13) | Loadsharing function number of loadsharing group | |
| (14) | Loadsharing group number of loadsharing group | |
| (15) | Comments on command execution |
| Key Parameter | Contents / Meaning | Action | ||
|---|---|---|---|---|
| 1 | 2 | 3 | ||
| (15) | ACTION NOT ALLOWED FOR THIS ALARM . . . . . . . . | C | ||
| (15) | ALARM CATEGORY NOT IMPLEMENTED . . . . . . . . . . | D | ||
| (15) | ALARM IDENTITY ALREADY STORED . . . . . . . . . . | E | ||
| (15) | ALARM NOT STORED . . . . . . . . . . . . . . . . . | F | ||
| (15) | ALARM TYPE NOT EQUIPPED . . . . . . . . . . . . . | G | ||
| (15) | COMBINATION OF OPTION WITH OTHER PARAM NOT ALLOWED | H | ||
| (15) | GIVEN ALARM IDENTITY NOT FOUND . . . . . . . . . . | Q | ||
| (15) | LOADSH FNC AND GRP NOT FOUND . . . . . . . . . . . | A | ||
| (15) | NEW ALARM CATEGORY NOT IMPLEMENTED . . . . . . . . | I | ||
| (15) | NO ACTIVE ALARMS FOUND . . . . . . . . . . . . . . | J | ||
| (15) | NO ALARMS IN EXCEPTIONS RELATION . . . . . . . . . | K | ||
| (15) | NO LOADSH PROCESSORS FOUND . . . . . . . . . . . . | R | ||
| (15) | NO NEED TO SWITCH : GIVEN CATEGORY ALREADY ACTIVE NOW | S | ||
| (15) | NO SPACE FOR STORAGE . . . . . . . . . . . . . . . | L | ||
| (15) | NOT ALLOWED FOR NOT-CONFIRMED-OFF ALARMS . . . . . | M | ||
| (15) | NOT ALLOWED FOR TYPELAMP-ONLY CATEGORY ALARMS . . | A | ||
| (15) | OPTION NOT ALLOWED (NO AVALANCHE ALARM HANDLING USED) | N | ||
| (15) | ORJ ABORTED, DATABASE ACCESS FAILURE . . . . . . . | B | ||
| (15) | POOLCATEGORY MUST BE HIGHER THAN NORMAL CATEGORY . | A | ||
| (15) | POOLCATEGORY, THRESHOLD, INDEXES ARE NOT CONSISTENT | A | ||
| (15) | REDUCED CATEGORY MAY NOT BE HIGHER THAN NORMAL CATEGORY | A | ||
| (15) | REDUCED CATEGORY NOT IMPLEMENTED . . . . . . . . . | O | ||
| (15) | SBL GROUP CATEGORY NOT IMPLEMENTED . . . . . . . . | P | ||
| (15) | THIS ALARM TYPE HAS NO ADDITIONAL ALARM QUALIFIER | A | ||
| (15) | TYPELAMP-ONLY OR PRINTONLY NOT ALLOWED AS POOL CATEGORY | A | ||
| (15) | USE OF CATEGORY UNEQ NOT ALLOWED (SEE R_AL_ENVFL) | A | ||
| Action | Meaning |
|---|---|
| A | Check input data: - if exact: given result data can be taken as information only. - if faulty: correct your input data and repeat MMC-command. |
| B | Repeat the command after some time. If the result is still unsuccessful, special fault clearing will be necessary. See fault reporting procedures. Refer to the document FAULT REPORTING PROCEDURES which is part of the Customer Documentation Guide. |
| C | (1) Deletion of this type of alarm is not allowed because it is a secondary alarm created due to another primary alarm. Delete or repair the primary alarm (use the MMC-command DISPLAY-ACTIVE-ALARMS (CRN = 00019) to find primary alarm). (2) Inhibit/release action not allowed on avalanche alarm. |
| D | The given alarm category is not existing in the database relation. So, it cannot be used. Correct input data and reenter the command. |
| E | Given alarm identity is already stored in the alarm exception relation. So, it cannot be added by the command CREATE-ALARM-EXCEPT (CRN = 07626). Correct input data and reenter the command. |
| F | The alarm cannot be deleted/inhibited/released because it does not exist. Use MMC-command DISPLAY-ACTIVE-ALARMS (CRN = 00019) to find the existing alarms. |
| G | The alarm type, given in the input, does not exist in the database relation. So, it cannot be used. Correct the input data and reenter the command. |
| H | When the parameter OPTION is used in MMC-command DISPLAY-ACTIVE-ALARMS (CRN = 00019), and equals to either DETAILED/1, STARTUP/2, or ALL/3, no other parameter may be used. Correct the input data and reenter the command. |
| I | The new alarm category is not existing in the relation involved. Thus, it cannot be used. |
| J | There are no active alarms with the given specifications. |
| K | There are no entries in the alarm-exception relation. |
| L | Alarm exception cannot be stored due to lack of space in the database relation. Check if another exception can be removed (use the MMC- command DISPLAY-ALARM-EXCEPT CRN = 07629) and, if so, do this removal before executing the MMC-command CREATE-ALARM-EXCEPT CRN = 07626). |
| M | Inhibit/release not allowed for non-confirmed-off alarms (lamps are already off). |
| N | Parameter OPTION equals to either DETAILED/1, STARTUP/2, or ALL/3, in MMC-command DISPLAY-ACTIVE-ALARMS (CRN = 00019), is not allowed when the avalanche alarm handling is not present in this build. Correct input data and reenter the command. |
| O | The given reduced category is not existing in the database relation. So, it cannot be used. Correct input data and reenter the command. |
| P | The SBL-group alarm category is not existing in relation involved. Thus, it cannot be used. |
| Q | The given alarm identity is not present in the alarm exception relation. So, modify by MMC-command MODIFY-ALARM-EXCEPT (CRN = 07627) or remove by MMC-command REMOVE-ALARM-EXCEPT (CRN = 07628) is not possible. First, display alarm identities which are present using the MMC-command DISPLAY-ALARM-EXCEPT (CRN 07629). Then correct input data and reenter the command. |
| R | There are no loadsharing groups defined, so they cannot be displayed. |
| S | The switch alarm category command is not needed, the active category is already as requested. |