Mitel Sx 200 Ml Pabx Lightware 16 Instructions Guide

							Maintenance Log Messages 
Table 7-l Fault Reports (continued) 
Alarm 
Code Message Action Required 
111 LS/GStrnkcardfai1edat020201 OOTrkl Can’t Verify the wiring from the trunk circuit to the 
seize trunk AlarmCode= 111 public network. Correct as required. Refer to 
CO tnmk card failed at 02 02 0100 Trk 01 Can’t the /r~s~a//a~~or~ /r~~orrrra~io/~ Practice. if this is 
seize trunk Alarm Code = 111 not the problem, suspect failure or bad wiring 
at the Central Off ice. 
E&M trunk card failed at 02 02 0100 Tk2 Can’t 
seize trunk Alarm Code = 111 
DID trunk card failed at 02 02 0100 Tk7 Can’t 
seize tnmk Alarm Code = 111 
112 LS/GStmkcardfai1edat020201 OOTrkl Can’t No release signal was received from the 
release trunk Alarm Code = 112 Central Off ice. Verify wiring. Refer to the 
CO trunk card failed at 02 02 0100 Trk 1 Can’t hstalation hforrnation Practice for details. 
release trunk Alarm Code = 112 
E&M trunk card failed at 02 02 0100 Tk7 Can’t 
release trunk Alarm Code = 112 
DID trunk card failed at 02 02 0100 Trk 7 Can’t 
release trunk Alarm Code = 112 
113 UNIVERSAL card failed at 02 03 0100 The total power rating of the modules installed 
Exceeds power rating Alarm Code =113 on the specified Universal Card exceeds the 
maximum permitted total power rating. Refer 
to the hstalation hfomation Practice for 
details. 
114 
PRINTER failed at 00 00 02 00 The printer used for SMDR printing is off-line 
SMDR printer down Alarm Code = 114 or not working. Check printer. Refer to printer 
troubleshooting procedures. 
117 RAM failed at 00 00 05 00 This is not a serious problem if it occurs once. 
CMOS checksum failed Alarm Code = 117 However, if it is persistent, refer problem to 
MITEL Field Service. 
118 COV card failed at 01 05 01 00 ext 1501 The specified card is a high-power card 
Card in low pwr slot Alarm Code = 118 installed in a low power slot. Use SHOW 
UNIVERSAL card failed at 02 03 0100 CONFIG command to obtain information on 
Card in low pwr slot Alarm Code = 118 the card slot. Re-install/reprogram the card 
for a high-power slot. 
DID card failed at 0105 01 00 
Card in low pwr slot Alarm Code = 118 
OPS card failed at 02 03 01 00 ext 1502 
Card in low pwr slot Alarm Code = 118 
121 PFI sense failed at 00 00 08 00 The bay has gone into Power Fail Transfer 
Bay has cut through Alarm Code = 121 mode. Use SHOW ALARMS command and 
examine logs further to find the actual cause 
BAY failed at 03 00 00 00 of the cut through. 
Bay has cut through Alarm Code = 121 
Page7of 1: 
March 1997 Issue 1 Revision 0 7-7  
						

							Troubleshooting 
Table 7-l Fault Reports (continued) 
Alarm 
Code Message Action Required 
122 PFT sense passed at 00 00 08 00 The bay has been cut back to normal 
Bay has cut back Alarm Code = 122 operation. Verify that appropriate action was 
PFT sense passed at 03 00 00 00 taken to rectify the event which caused the 
Bay has cut back Alarm Code = 122 cut through. 
123 ONS card failed at 02 01 01 00 ext 123 GENERAL: The recording device attached to 
Recording dev failed 
Alarm Code = 123 the specified port has malfunctioned. 
Check 
ONS card failed at 02 01 01 00 ext 2101 wiring. Refer to the instructions provided by 
Recording device failed - false origination the manufacturer of the recording device. 
Alarm Code = 123 
ONS card failed at 02 01 01 00 ext 2101 RAD failed to hang up - locked out. 
Recording device failed to hang up-lok 
Alarm Code = 123 
ONS card failed at 02 01 01 00 ext 2101 
Recording device failed to hang up - sus 
Alarm Code = 123 
ONS card failed at 02 01 01 00 ext 2101 RAD failed to hang up - suspect state. 
Recording device failed to answer 
Alarm Code = 123 
ONS card failed at 02 01 01 00 ext 2101 
Recording device failed - nil error 
Alarm Code = 123 
124 PRJNTER failed at 00 00 02 00 The printer used for Hotel/Motel wakeup 
Wakeup printer downAlmCode=l24 printing is off-line or not working. Check 
printer. Refer to Printer troubleshooting 
procedures. 
125 ONS card failed at 02 010100 ext 210 Wakeup information only. 
not answered Alan&ode=1 25 
COV card failed at 0105 0100 ext 111 Wakeup 
not answered Alarm Code= 125 
126 Any line card failed at 02 01 01 00 extl23 Plid Record this and watch for further 
Restored Alarm Code = 126 occurrences. If system pefformance is 
degraded substantially, contact MITEL Field 
Service. 
128 DTMF RX module failed at 02 02 01 00 Reseat the 
affected Universal Card. 
Receiver locked out Alarm Code =128 
Page8of 15 
7-8 Issue 1 Revision 0 March 1997  
						

							Maintenance Log Messages 
Table 7-l Fault Reports (continued) 
Alarm 
Code Message Action Required 
129 ** anything ** failed at 00 00 00 00 Record this and watch for further occurrenc- 
Group-Link-Test not a proper member es. Perform a Verify Database operation and 
Alarm Code = 129 check for further occurrences of this Alarm 
* * anything * * failed at 00 00 00 00 Code. if system performance is degraded 
Group-Link-Test Invalid Group Link substantially, contact MITEL Field Service. 
Alarm Code = 129 
** anything ** failed at 00 00 00 00 
Group-Link-Test many members in Group 
Alarm Code = 129 
** anything ** failed at 00 00 00 00 
Group-Link-Test nil error 
Alarm Code = 129 
130 * * anything * * failed at 00 00 00 00 Record this and watch for further occurrenc- 
Plid to Swid failed Alarm Code = 130 es. Perform a Verify Database operation 
and 
check for further occurrences of this Alarm 
Code. If system performance is degraded 
substantially, contact MITEL Field Service. 
131 RAM failed at 00 00 04 00 Record this and watch for further 
CMOS VS Ram FailedAlarm Code= 13 1 occurrences. Perform a Verify Database 
operation and check for further occurrences 
of this Alarm Code. if system performance is 
degraded substantially, contact MITEL Field 
Service. 
132 ** anything** failed at 00 00 00 00 A CDE audit has failed. If this persists, attempt 
Key DB corrupt. Set has no prime key. a COPY DATABASE as soon as possible. 
** anything ** failed at 00 00 00 00 Perform a Verify Database operation and 
Key DB corrupt. Key data not for set. check for further occurrences of this Alarm 
Code. If this still persists; contact MITEL Field 
** anything **failed at 00 00 00 00 Service. 
Key DB corrupt. Invalid key number. 
** anything **failed at 00 00 00 00 
Key DB corrupt. Prime is not key 1. 
** anything **failed at 00 00 00 00 
Key DB corrupt. Prime is not immediate ring. 
** anything **failed at 00 00 00 00 
Key DB corrupt. Prime not in and out. 
** anything** failed at 00 00 00 00 
Key DB corrupt. Line WA index wrong. 
** anything** failed at 00 00 00 00 
Key DB corrupt. Line owner swid wrong. 
** anything** failed at 00 00 00 00 
Key DB corrupt. Nil error. 
Page9of 15 
March 1997 Issue 1 Revision 0 
7-9  
						

							Troubleshooting 
Table 7-l Fault Reports (continued) 
Jarm 
>ode Message Action Required 
132 Key-DB-test failed at 00 00 00 00 Key 1 is not programmed as an INTERCOM 
ont’d) ICM is not key 1 key - key I must be an INTERCOM key. 
Key-DB-test failed at 00 00 00 00 The INTERCOM key is not programmed as 
ICM not immed ring IMMEDIATE RING - must be so. 
Key-DB-test failed at 00 00 00 00 The DIRECTION for the INTERCOM key is 
ICM not in and out not programmed as In/Out - must be so. 
Key-DB-test failed at 00 00 00 00 A trunk has been programmed as a DTS key 
Trk DTS and CO on a PBX SUPE/?SETtelephone and a CO 
Line on a Key System SUPERSETtelephone 
- this is not permitted. 
KeyyDB-test failed at 00 00 00 00 
Trk Private and CO A trunk has been programmed as a PRIVATE 
key on a PBX SUPERSETtelephone and a 
CO Line on a Key System SUPERSET 
telephone - this is not permitted. 
133 ** anything ** failed at 00 00 00 00 A CDE audit has failed. If this persists, attempt 
Trunk Number Corrupt. a COPY DATABASE as soon as possible. 
Perform a Verify Database operation and 
check for further occurrences of this Alam 
Code. If this still persists; contact MITEL Field 
Service. 
134 ** anything ** failed at 00 00 00 00 A CDE audit has failed. If this persists, attempt 
Access Code Tbl Bad. a COPY DATABASE as soon as possible. 
Perform a Verify Database operation and 
check for further occurrences of this Alarm 
Code. If this still persists; contact MITEL Field 
Service. 
135 UPS sense failed at 00 00 09 00 The Uninterruptible Power Supply is not 
UPS not available Alarm Code = 135 operating. Check the relevant wiring (see the 
/r~.sWaf;on hformatio~ Practice). Refer to the 
UPS part of this Practice* 
136 UPS sense passed at 00 00 09 00 Information only. 
UPS available Alarm Code = 136 
137 UPS sense failed at 00 00 09 00 The line ac voltage has failed. Ensure UPS is 
ac voltage failure Alarm Code = 137 functioning. 
13% UPS sense failed at 00 00 09 00 Either the battery is failing, or the battery 
Battery/charger Alarm Code = 138 charger is not functioning. Examine battery, 
charger, and wiring. Also refer to the 
instructions provided by the manufacturer of 
the UPS. 
139 UPS sense failed at 00 00 09 00 There is no line ac voltage. Also, the battery 
AC/batte$charger Alarm Code = 139 is failing, or the charger is/was not functioning 
properly. Examine battery, charger and 
wiring. Also, refer to the instructions provided 
by the manufacturer of the UPS. 
PagelOof l! 
7-10 Issue 1 Revision 0 March 1997  
						

							Maintenance Log Messages 
Table 7-l Fault Reports (continued) 
Alarm 
Code Message Action Required 
141 Nil device failed at 00 00 00 00 The PMS system failed to respond to 20 
PMS is down Alarm Code = 141 consecutive queries from the PABX. Refer to 
PMS procedures. 
142 Nil device failed at 00 00 00 00 After failing to respond, the PMS system has 
PMS is up Alarm Code = 142 now responded to a PABX enquiry. 
143 Nil device failed at 00 00 00 00 The system attempted to send a message to 
PMS buffer is full Alarm Code = 143 the PMS message buffer; buffer was full. If 
persistent, refer to PMS procedures. 
144 Nil device failed at 00 00 00 00 PMS has sent the PBX an invalid 
No STX from PMS Alarm Code = 144 START-OF-TEXT message. Refer to PMS 
procedures. 
145 Nil device failed at 00 00 00 00 PMS has sent the PBX an invalid 
No ETX from PMS Alarm Code = 145 END-OF-TEXT message. Refer to PMS 
procedures. 
146 Nil device failed at 00 00 00 00 PMS has sent the PBX an invalid function 
Bad PMS function Alarm Code = 146 message. Refer to PMS procedures. 
147 Nil device failed at 00 00 00 00 PMS has sent the PBX an invalid status 
Bad PMS status Alarm Code = 147 message. Refer to PMS procedures. 
148 Nil device failed at 00 00 00 00 PMS has sent the PBX an invalid room 
Bad PMS room number AlarmCode= number message. Refer to PMS procedures. 
149 Nil device failed at 00 00 00 00 If the PMS refuses to accept a transaction 
Cannot send PMS msg Alan&ode=149 from the PBX after five tries, the PBX will 
generate this log. 
150 LS/GS trk card failed at 0105 0100 trk 001 This trunk was seized and after 10 seconds 
Trunk no dial tone Alarm Code = 150 dial tone was not detected. The trunk has 
been busied out. 
151 Link 07 Channel 19 Busied out Device busied out by maintenance personnel. 
Alarm Code = 151 
151 ONS card failed at 01 01 01 00 ext 1101 Device busied out by maintenance personnel. 
Busied out Alarm Code = 15 1 
152 ONS card passed at 01 01 0100 ext 1101 Device returned to service by maintenance 
Returned to service Alarm Code = 152 personnel. 
152 Link 07 Channel 19 Returned to service Device returned to service by maintenance 
Alarm Code = 152 personnel. 
155 Tl trunk card passed at 0106 01 00 Trk 019 The link has exceeded thespecified threshold 
has exceeded the maintenance slip threshold - this is a warning - watch for further 
occurrences. If persistent, refer to Tl Trunk 
troubleshooting procedures. 
Tl trunk card passed at 01 06 01 00 Trk 019 Link was running with errors, is now running 
is now below the maintenance slip threshold at an acceptable error rate. Information only. 
Page 11 of 15 
March 1997 Issue 1 Revision 0 7-I 1  
						

							Troubleshooting 
Table 7-l Fault Reports (continued) 
Alarm 
Code Message Action Required 
155 Tl trunk card at 01 06 01 00 Trk 019 The link has exceeded the specified 
(cont’d) has exceeded the service slip threshold threshold. A yellow alarm has been sent to 
the far end, and the link has been removed 
from service, and a new sync source selected. 
The RTS - Service Limit timer has been 
started. Refer to Ti Trunk troubleshooting 
procedures. 
Tl trunk card at 0106 01 00 Trk 019 
has exceeded the maint loss frame threshold The link has exceeded the specified threshold 
- this is a warning - watch for further 
occurrences. If persistent, refer to Tl Trunk 
troubleshooting procedures. 
Tl tr~~nk card at 0106 0100 Trk 019 Link was running with errors, is now running 
is now below the maint loss frame threshold at an acceptable error rate. Information only. 
Tl trunk card at 0106 0100 Trk 019 The link has exceeded the specified 
has exceeded the service loss fi-ame threshold threshold. A yellow alarm has been sent to 
the far end, and the link has been removed 
from service, and a new sync source selected. 
The RTS - Service Limit timer has been 
started. Refer to Ti Trunk troubleshooting 
procedures. 
Tl trunk card at 01 06 01 00 Trk 019 
has exceeded the maintenance ber threshold The link has exceeded the specified threshold 
- this is a warning - watch for further 
occurrences. If persistent, refer to Tl Trunk 
troubleshooting procedures. 
Tl trunk card at 0106 0100 Trk 019 Link was running with errors, is now running 
is now below the maintenance ber threshold at an acceptable error rate. Information only. 
Tl trunk card at 01 06 01 00 Trk 019 removed Refer to Tl Trunk troubleshooting 
from service and transmitting yellow alarm procedures. 
Tl trunkcardatOlO601 OOTrkOl9 The link yellow alarm has been cleared. 
is returned to service Possibly the RTS service limit timer has 
expired, and the link is within an acceptable 
threshold allowing it to be returned to service. 
The link may now be used as the network sync 
source. Information only. 
Tl trunk card at 0106 0100 Trk 019 
is receiving a yellow alarm The link has received a yellow alarm condition 
from the far end, and has been removed from 
service. If this is the network sync source, a 
new source has been selected. Problem with 
either the local Channel Service Unit, or at the 
far end. 
Page 12 of 15 
7-12 Issue 1 Revision 0 March 1997  
						

							Maintenance Log Messages 
Table 7-l Fault Reports (continued) 
Alarm 
Code Message Action Required 
155 Tl trunkcardatO1 0601 OOTrkO19 There is no synchronization detected on the 
(cont’d) is in red alarm condition due to loss of sync link; it has been removed from service. If this 
is the network sync source, a new source has 
been selected. Problem with either the local 
Channel Service Unit, or at the far end. 
Tl trunk card at 0106 0100 Trk 019 No power on the link; it has been removed 
is in red alarm condition due to loss of power from service. If this is the network sync 
source, a new source has been selected. 
Problem with either the local Channel Service 
Unit, or at the far end. 
Tl tnmk card at 0106 0100 Trk 019 exceeded The link is the current network sync source - 
sync slip thresh as current sync source a new sync source has been selected. Refer 
to Tl troubleshooting procedures. If this 
message persists, may be necessary to make 
changes to the network synchronization 
source list. 
Tl tnmkcardatO1 0601 OOTrkO19 
is now below the net sync slip threshold The RTS net slip timer has expired, and the 
link is within an acceptable threshold allowing 
it to be returned to service. The link may now 
be used as the network sync source. 
Information only. 
Tl trunkcardatO1 0601 OOTrkO19 
alarm condition is now cleared A red or yellow alarm has been cleared, and 
the RTS after alarm timer has expired. The 
link has returned to service. Information only. 
Tl trunk card at 0106 0100 Trk 019 
System in freenm mode no sync source 
available There is no network synchronization source 
that can be used (the source list has been 
exhausted) -the system is therefore in freerun 
mode. Refer to the Tl Trunk troubleshooting 
procedures. May be necessary to make 
changes to the network synchronization 
source list. 
Tl trunk card at 0106 0100 Trk 019 The link is the new sync source, and the 
is current sync source and is in auto mode system is in auto mode. Information only. 
Tl trunkcardat010601 OOTrkO19 The link is the new sync source, and the 
is current sync source and is in manual mode system is in manual mode. Information only. 
Tl trunkcardatO1 0601 OOTrkO19 There was a change in the network sync 
The system’s previous sync source was freerun source. The system was previously in freerun 
mode mode. Information only. 
Tl trunkcardatO1 0601 OOTrkO19 There was a change in the network sync 
was previous sync source in manual mode source. The link was the old sync source, and 
the system was in manual mode. Information 
only. 
Page 13 of 15 
March 1997 Issue 1 Revision 0 7-13  
						

							Troubleshooting 
Table 7-l Fault Reports (continued) 
Alarm 
Code Message Action Required 
155 Tl trunk card at 0106 01 00 Trk 019 There was a change in the network sync 
[cont’cf) was previous sync source in auto mode source. The link was the old sync source, and 
the system was in auto mode. Information 
only. 
Tl trunk card at 01 06 01 00 Trk 019 
is reporting unstable link (phase error) The link is reporting phase errors. If this is the 
network sync source, a new source has been 
selected. Problem with either the local 
Channel Service Unit, or at the far end. 
Tl trunkcardat010601 OOTrkO19 
is reporting unstable link (no phase error) The link is no longer reporting phase errors. 
It is now avaialable for use as the network 
sync source. Information only. 
Tl trunkcardat010601 OOTrkO19 
sync source manual timer has expired The network sync source manual timer has 
expired and the system is changing from 
manual to auto or freerun mode. A network 
sync source is picked from the network 
synchronization source list. Information only. 
Tl trunk card at 0106 01 00 Trk 019 Links for network sync have been specified, 
No Tl clock module, running in freerun mode but there is no Tl clock module in the system. 
The system is running in freerun mode as a 
result. Refer to Main Control Card II 
procedures. 
Tl Trunk card at 01 06 01 00 Trk 019 Delete programming for the 24th circuit from 
has 24th cct programmed. Wrong bay type CDE Form 14 (Non-Dial-In Trunks) or Form 
reported. 15 (Dial-In Trunks). 
Power down the bay and then power it up 
again to generate another bay status report. 
Tl trunkcardat010601 OOTrkO19 Non problem. If persistent, contact MITEL 
created log for unknown reason Field Service. 
156 DIG line card and failed at 05 0101 Checksum of dataset firmware failed, replace 
PST checksum failed Alarm Code =156 set. Device will be busied out. 
157 DIG line card failed at 05 0101 RAM in dataset failed (external or 6803). 
PST RAM failed Alarm Code = 157 Replace set. Device wil be busied out. 
158 DIG line card failed at 05 01 01 UART loopback power up test failed; replace 
PST UART l/h failed Alarm Code =158 set. Device will be busied out. 
159 DIG line card failed at 05 01 01 DNIC loopback power up self test failed; 
PST DNIC l/b failed Alarm Code =159 replace set. Device will be busied out. 
160 DIG line card failed at 05 0101 HDLC controller failed in power up test; 
PSC HDLC failed Alarm Code = 160 replace set. Device will be busied out. 
161 DIG line card failed at 01 02 11 02 ext 123 Firmware trap occurred in set; check power 
Firmware trap Alarm Code = 161 supply. The device will not be busied out. 
Page 14 of 15 
7-14 Issue 1 Revision 0 March 1997  
						

							Maintenance Log Messages 
Table 7-l Fault Reports (continued) 
Alarm 
Code Message Action Required 
162 DIGlinecardfailedatOlO2 1102ext 123 Flood Call Processing received more than 125 EIA 
of EIA input Alarm Code = 162 input reports within 2 minutes while in the idle 
state; the data device was busied out. When 
the device is replaced, the data device will be 
unbusied. Check the equipment attached to 
the data device for a faulty EIA output. 
163 DIG line card failed at 01 02 11 02 ext 123 A flood of ASCII characters (100 more than 
Flood of ASCII input Alarm Code = 163 the maximum input) was received, and the 
data device was busied out. if the device is 
replaced the data device will be unbusied. 
Check the equipment attached to the data 
device for flooding of ASCII characters (such 
as a large file being dumped to the DTRX 
process). 
164 NIL PLID failed at 00 00 00 00 The name field received from the PMS system 
Bad PMS Name Alarm Code = 164 is improperly formatted, or is inconsistent with 
the name operator. Refer to PMS 
procedures. 
165 NIL PLID failed at 00 00 00 00 The time field received from the PMS system 
Bad PMS Time Alarm Code = 165 is improperly formatted. Refer to PMS 
procedures. 
166 NIL PLID failed at 00 00 00 00 Dial 0 routing for the PMS is not a console 
PMS requires console Alarm Code= 166 LDN or a console prime number. Problem 
either with PMS database or local PABX 
programming. 
170 DIG line card failed at 05 01 01 Firmware trap occurred in set; check power 
Firmware trap Alarm Code = 170 supply. The device will not be busied out. 
171 DIG line card failed at 05 01 01 Call Processing received more than 125 EIA 
Flood of EL4 input Alarm Code = 17 1 input reports within 2 minutes while in the idle 
state; the data device was busied out. When 
the device is replaced, the data device will be 
unbusied. Check the equipment attached to 
the data device for a faulty EIA output. 
172 DIG line card failed at 05 01 01 A flood of ASCII characters (100 more than 
Flood of ASCII input Alarm Code = 172 the maximum input) was received, and the 
data device was busied out. If the device is 
replaced the data device will be unbusied. 
Check the equipment attached to the data 
device for flooding of ASCII characters (such 
as a large file being dumped to the DTRX 
process). 
Pagel5ofl5 
March 1997 Issue 1 Revision 0 7-15  
						

							Troubleshooting 
Table 7-2 Alarm Log Reports 
Alarm Code 
Action Required 
Tot alarm went from No Alarm to MAJOR 
Use SHOW ALARMS command for more detailed 
see Alarm Reasons in Table 7-3 information. Also see the applicable entry in Table 7-3. 
Tot alarm went from MINOR to MAJOR see Use SHOW ALARMS command for more detailed 
Alarm Reasons in Table 7-3 information. Also see the applicable entry in Table 7-3. 
Tot alarm went from MAJOR to Use SHOW ALARMS command for more detailed 
CRITICAL see Alarm Reasons in Table 7-3 information. Also see the applicable entry in Table 7-3. 
Tot alarm went from MAJOR to MINOR see This is an improvement in service. Information only. 
Alarm Reasons in Table 7-3 
Tot alarm went from MINOR to No Alarm see This is an improvement in service. Information only. 
Alarm Reasons in Table 7-3 
Table 7-3 Alarm Reset Reasons 
Alarm Level Change Reason Action Required 
Alarm level change due to Bay XX pcm Check the status of the specified bay (XX) via the SHOW 
Alarm level change due to Bay XX rcvrs ALARMS and SHOW STATUS commands. 
Alarm level change due to Bay XX trunks 
Alarm level change due to Bay XX lines 
Alarm level change due to system pcm Check the system status via the SHOW ALARMS and 
Alarm level change due to system rcvrs SHOW STATUS commands. 
Alarm level change due to system trunks 
Alarm level change due to system lines 
Due to threshold change of Bay XX pcm Check the status of the specified bay (XX) via the SHOW 
Due to threshold change of Bay XX rcvrs ALARMS and SHOW STATUS commands. 
Due to threshold change of Bay XX trunks 
Due to threshold change of Bay XX lines 
Due to threshold change of system PCM Check the status via the SHOW ALARMS and SHOW 
Due to threshold change of system rcvrs STATUS commands. 
Due to threshold change of system trunks 
Due to threshold change of system lines 
7-16 Issue 1 Revision 0 March 1997