GTE Omni Si Database Technical Practices Manual

							I
I
I
I
i
IREGISTER STORED DATA VALUEII,Ii
III
iFAULTCODEIIB
IC’I02IE3
IH
I
I
I
LIIIIII; 12-PEC; : PEC No.I Channel No.I DataI Data ReadIAddress of Faulty Byte
IRead AfterI I
I III WrittenII1IIII WriteChannel I III Memory Failure \ %LIIIIIIIIIII
IIIIII Ii13-PEC! Self TestI Error -
i ; PEC No.
I I
I I
I 
II II I
Il.I I
I I
I I
I I
I I
I I
I I
I II I,II I
I I
I I
I I
I II I
I I
I I
I I
I I
; 00 = PEC-CEC1 DataIi Data Read:I; WrittenIAddress of Faulty ByteI CommonIIIII MemoryI
; Read-and-tII
III
l WriteIII
III:II,! OI=PEC !IIIIAddress of Faulty ByteI
\ Block ParityiII
I
II
I
I5210
I II I
I I
I I
I I
I I
II
I I
I I
I
I 14-PEC, 
II III
I I
I II I
I I
;07=MDR iI Checksum on ICall InfoI;I BufferI
II
I
III
II
I
I
I
I
I
I
I
! OS=PECi Directive No.Ir Parameter 1i Parameter 2 t Parameter 3 i
: Illegal PECI!II
IIII DirectiveIIII
IIIII
III
i 10 MS Error; ; PEC No.I1 02=TestI!
I
\ Failure; CECCountII PECCount I
I
I
I
IIII II IIIfII
I!I II1I1 15 Tl Alarm: ; PEC No.; OO=TlA! OO=System II
,
II IIII
II II; AlarmI
I
II II
I
I
II II
I
II I1 01 = RemoteIIII I; Ol=TlBI AlarmI
,I III,II II
II III 02 =CutoffIf
II I
I
II II\ AlarmII
I,
I
I III
II
II IIII
II III 03=LocalIr Alarm,,
II III
I 16CECI IIII, II) 10 MS Stopped! !I1
; 02=PECIiIr Address of Faulty Byte III DynamicIIII
; MemoryIII
I
IIIIIII; 03=PECi Directive NO.I Parameter 1t Parameter 2.1 Parameter3 I
i Illegal,III
I DirectiveII
II!II
IIII
I 04zMPB85I CounterI
II Addressof Attempted Write I
; TimeoutII
II
I
I
f 06 = Invalid! Test No.I
I
I Test No.III
IITL-130200-l uu I
Figure 2.2Fault Code Quick Reference Guide (Continued)
8/87M-29 
						

							TL-130200-1001I
I
i
IREGISTER STORED DATA VALUE1
II
III
II
I1
IFAULT CODEI
IIIBIC’ID2IE3HILI
I1 
17-CECI Alarm Faulti I Attendant; OO=ArtCard iI
III I Console No.
II
II I, Alarm
I Ol-lO=Tl Line
III
!
II I
I IIiI
I
I.~_I Ii Numberl-16;II
II
II Ii 11-tB=Attend- IIII III. . .II I: antI
II Ir 00-07 = Trans-i mission FaultI!II
II I
I IIiII
II
II 
III
i 18-Commoni-1 PEC No. .ItII
II
i Memory Blocki ;IIEnd Address of BlockIAddress of Block ThatII Parity Error
IIII III FailedI
II II
II
IIII IQCEC; Preloadingr r OO= Instruction iI, Memory Test1 1 Page0iAddress of Block ThatI
I II1 FailedI
I
Ii : 01 =Instruction iII
I
I
I
II Page 1
II
I III
II
I
I
; ; 02=DataIII
II I Page0III
II III
IfI
II I 03=DataI
J; 1 Page 1I
IIIII
I
II4
Figure 2.2Fault Code Quick Reference Guide .(Continued)M-30
8l875210 
						

							FUJITSU GTESECTION TL-130200-1001 ISSUE 1
BUSINESS SYSTEMS, INC.
AUGUST 1987MAINTENANCE
OMNI SI@’
TECHNICAL PRACTICES5.2.1.0 
						

							PurposeThis Technical Practice has been prepared for FGBS Employees
who operate and maintain the equipment manufactured and sold
by Fujitsu GTE Business Systems, Inc. The information in this
practice is subject to change and may not be suitable in all
situations. Fujitsu GTE Business Systems, Inc. acknowledges
that a customer’s special requirements or practices may take
precedence over those supplied in this practice if a conflict
develops during installation or ongoing operation. Fujitsu GTE
Business Systems, Inc. hereby disclaims any responsibility or
.-liability for any consequential or inconsequential damages that
may result from the use of this practice.
This document is provided with the understanding that it shall not
be copied or reproduced in whole or in part or disclosed to
-others with-out the prior written permission of Fujitsu GTE
Business Systems, Inc.
Copyright 
a1987 by FGBS, Inc.
OMNI SI@ is a trademark of Fujitsu GTE Business Systems, Inc.
Comm 
I’” is a trademark of Fujitsu GTE Business Systems, Inc.
FlashComm Plus’” is a trademark of Fujitsu GTE Business
Systems, Inc.
FeatureComm I’” is a trademark of Fujitsu GTE Business
Systems, Inc.
FeatureComm II’” is a trademark of Fujitsu GTE Business
Systems, Inc.
FeatureComm 
Ill’” is a trademark of Fujitsu GTE Business
Systems, Inc.
FeatureComm 
IV’” is a trademark of Fujitsu GTE Business
Systems, Inc.
FeatureComm 
V’” is a trademark of Fujitsu GTE Business
Systems, Inc.
FeatureComm VI’” is a trademark of Fujitsu GTE Business
Systems, Inc.
AnswerComm 
IT, is a trademark of Fujitsu GTE Business
Systems, Inc.
AnswerComm II’” is a trademark of Fujitsu GTE Business
Systems, Inc.
OMNI IVMS’” is a trademark of Fujitsu GTE Business Systems,
Inc. 
						

							II
IREGISTER STORED DATAVALUEI
II
I
I
FAULT CODEIII
III
I
IBC’DzIEsHLII
II III
II I; 80 = Illegal Di-ii rectiveNo.lnto ;I
II
II I
II
II III
II I
II IITarget RoutineII
II
II
II I
r FF=PEDTest 1II II FailedIIIi 22-24SpareI II
I 25 Real TimeI II
I
III I
II1Clock FailureI I
I 
IIII
I ‘1”I III
I II
I
IIII
III If
I
I I:III
I
II II
IfII
Ic I-.IIII
II,I
II III
I27 H/M Data notI i DiskOperationIi Failure Mode IIII
r Backed upr r FailureI
II I
IIII IIII
i 28-CAS Main/i ! PEC No.IIIIII
; ACDAgentI I( Data Link No.I A=Time-outi Agent I.D.INO MeaningI
IIIData LinkII
i ErrorI II;9=2ndNack iIII III
I
I III
I
I
IIII
II II
I
IIi 8=DataNot 1I
Ir ExpectedII
IIII
I
; ; PEC No.i Data Link No.1 FF = RequestII fori Agent I.D.II
I
I
I IIIINO MeaningI
I
II II1 Initialization IIII
I
; ; PEC No.IIII
I
I
r r Bufferi No Meaning; C=NoPEC1 NoMeaning iNO MeaningI
I
If ) DestinationI
II Message Buffer IIII AvailableIII IIII
I
! 29-CAS Main/I IfII
IIIIIII
; ; PEC No.I
Ir B = FailureII
iACD Message
I Queue ErrorI III Whena PEC’s iiIII
II III QueueCleared III
II II; All PEC,I,If IIII
III IiI Queue Were iII
II II ClearedIII
I
I IIIIII
IIII i No.of TimesI00 = Message1 C=NoIII
II I That NoIi i MessageI Buffer Queuei Not Cleared1 Message
IIIIII
Ir Buffers Were III
Ir r BuffersWereIII
Ii i Available1 Availablei FF=Message IIIII
II III Ii Buffer Queue II,IIIIIIII II ClearedIIII
i 30-AttendantI f
III
[ ConsoleI 1 Console No.
II Ii Console No. ;i Typeof Error iII 8=Checksum III DataI IIIII
i CheckI IIIi 9=DataLink iIII
I A=Time-out II
I ErrorIIIIII III1 Occurred
IIII
II II1I III
II FF=Data LinkII;,
II
iI II
I1 Check Failure II
31PEC ODDB;;IIPEC No.IIti 
BackupFailure I lIi
Figure 2.2Fault Code Quick Reference Guide (Continued)
52108187
M-31 
						

							;I
II
IREGISTER STORED DATAVALUEI
II
II
I
IFAULT CODEIIIBIC’DzIIEsHII
ILII
I1 
32- CIP Cardi ; PEC No.i 00 = CLP CardIIICard No.IIII FailureI If Test FailureiII;II
II
II
II I
IIII
I; 01 =CIPCard [II IIII
III:I
II II XMlTError IIIII
II
IIII
II II 02=CILCard iIIII
II I
I 
-.~_I II WatchdogII
I
IIIII
I
;II
II
. . .I II Timer ErrorI
IIII -I Ii 03=CIPCardIIII
IIII IiII
II
I
II I1Hardware Error IIII
IIIII II! 04=CIPCard ,IIII
I
; .;III
II Initialization IIIIII
I
I III!I
iI ErrorIII
IIIII 33-CIP PortIII
] Failure; i PEC No.I 00= Data Linki Port No.IIIII I; Test FailureI
II
IIIIII
II I; Ol=PortLBP tI1fI
II IIIIII III I; Protocol Error IIIIIIIIIII II
II It! Total #of Sync III
I
I I
I 02=CIPPort ,ISync ErrorI ChangeI
III
III
II III 03 = Port Initial- ,IIIi
II
If I1 ization Error iIIIII III
I1
II III
II Ii 04=TestCom- iII
Ii
I
II II mand Failure IIIII
IIIIII III
I; 05=PCRTSoft ;I Total #of Soft II
II I; ProtocolI, ProtocolI
IIIII III
I
II II 06 = Down; SIDI Block Numberi DN = Directory NumberII II
II I
, Load Failure,III
I
i 3CRemote’ ’ BO=MDR-ESP
I
II1 Number of
I Current Status I*See Below iIIIII FADSI! Communications, CommunicationsIIII
I Transmissioni ( Status Changet Status Change; Ol=OKI OO=BADIIIII
IIII ErrorIII
i1 I 01 = MDRMem- ’ Number ofI
I_-
I11 ory Allocation1 FiguresI
INo MeaningIIII
I’ , FailureIIIIII III
II
II IIIII I 02=Remote, Previous ESP
fI I FADS must be( Statei New ESP State 1
No MeaningI
I
III
II I started(FADS II
I
I
I ( periodicdata II1I
II
II
,I I collection in-II
IIIi i terval error)1I
II
II
II
) 35-Remote FADSI III;; 01 = Real-Timei Real-Time1 Real-TimeII1 Reporting Error
, I Packet Lost Sync I Packet CountII I
I1 Data Timer
INo MeaningII
II
Figure 2.2Fault Code Quick Reference Guide (Continued)
M-32
81875210 
						

							I L- I3uLuu- I vu I. .
I
I
REGISTER STORED DATA VALUEI
I
I
I
I
IIIIIII
i
FAULT CODEIBC’D*EsHLI
.:- ,I. . .I
I
i1 02 
=Real-Time i Real-TimerI
I Real-TimeINo MeaningI
I
r Packet Counti Packet CountI Data TimerII
I ErrorIIII
III
i 03=15i 15Minutesi 15 MinutesIINo Meaning;
I Minute Packet I Packet Counti DataTimer ;IIr Count LostI
II
i SyncI
II
II
II
I
i 04=15
,II 15 MinutesIr 15 MinutesII
r Minute Packet I Packet CountI Data TimerINo MeaningIIII Count ErrorIIIII
III
I
II1 OS=Logon[ Logon IDi Logon IDIIINo MeaningI
I IDPacketII Packet Counti DataTimer ;II Count ErrorI
IIII
II
I
II
I I 06=Max#of! Buffer Failure IIII
I;f TimesCannotiPeg ValueI00INo MeaningIII , Finda BufferI
I III
IIII
I
I I 07=LogoffII
IIII
i i BufferIII
I00I
I00INo MeaningI
II( ( OverflowI
II
III37-System Restart 
I IIIIII00I
00IIIII IItII
IIII III ICEC ReloadIIIIII II
II
I
I IIIII
III IIIIII IIIIIII I
IIII
II IIIII
NOTES:
1.
2.
3.
4.See Table 6-4
See Table 6-5
See Table 6-5, Register EFault 34 Reg E = Reason for Change
00 = MDR not in Service
01 = Timeout Waiting for ESP Acknowledgement
02 = Unexpected Input from ESP
06 = Acknowledge from ESP
12 = No-Acknowledge from ESP
52108187M-33 Figure 2.2Fault Code Quick Reference Guide (Continued) 
						

							REGISTER STORED DATA VALUE
FAULT CODEII
BIC’D2IEsIHL
39-ADMPtI 01 =Can’tInitialization and!!II
I
r r Enable ADMPII
IAssociated! i orNoBufferIfI
II .I
I
IErrors
f 1 AvailableIIIiIII
; ; 02=Host;I0 PECOOSIII
; ; PEUADMP: IDSOOSIII
I
II
I
II .*.03 = DuplicateiiII
I
III I initial Request:II
III. .I I 04=Config-IIII
I I urating Data :i DevTypI Dev Number 1II Dev Number 2! PARM 1! PARM2
II 1 Errori Card SlotII
II
II
I
i I D5= PRDoes ‘m i PEC#i OWNGPIII
IIII Not MatchIIIII III
I
I I 06=Spare; PARM 1; PARMZI
II 
I; PARM3I
I
II1
I i 07=Undefined j StatusI
II
,II
I
iI StatusII:IIII
! ! 08=SpareIjPARM 1; PARMZI
I
I
f I: = DevTyp
.j PARM3I; =PEC; =SIDIII1 
i 09=Devi DevTyp
II
I
)i Type NotIIIII
f 1 Implemented iiIIII III
II40-Disk Files
: : OO=GVTX009GVTX009/I I
; OO=FileFailed ! SeeFMSIII
IIIi toOpeni Code for D2IIIGVTXOI 0I I 01 =GVTXOlO. 0 1 =R e a d I Register DataIII
(TCMIFRL)I I
I IiRecord Errori ValuesIII
I
and1 I 02=RC/OM: 02=WriteI
I
l/O ERRORSI I: Record ErrorIIIIIII Ii 03 = File Failed!II Ii to.CloseII
III II
I
I IIII
I
41-Disk I/O ErrorIIII I/O Request Code i Error Code (See
DCB Table Index r DCB Sequence
I 1 (See Note 5)i Note 6)(TCTl X));I Index(TCSlX) ,DRB ADDR
42-Time Slot 
Lock-
UPTime SlotHardware IDCall StorePEC Number !Number
Number
NOTES:
5.
I/O Request Codes are as follows:
02 = Read PEC 0 Generic and Data Base
03 = Read PEC 1 Generic and Data Base
04 = Read PEC 2 Generic and Data Base
05 = Read PEC 3 Generic and Data Base
06 = Read MDR Generic and Data Base
08 = Read PEC 0 Data Base Only
09 = Read PEC 1 Data 
BaseOnlyOA = Read PEC 2 Data Base Only
OB = Read PEC 3 Data Base OnlyOC = Read MDR Data Base Only
OE = Write all Data Base
13 = Read 
HC/M Data
14 = Write HUM Data (MR)
15 = Write HC/M Data (Power Fail)18 
= Read a Recent Change Program
IA = Close Recent Change File
1 D = Read Featurephone Generic
1 E = Load a PEC (Parallel Loading)1 F = Close Featurephone File
20 = Read PEC 4 Generic and Data Base
21= Read PEC 5 Generic and Data Base22 = Read PEC 6 Generic and Data Base
23 = Read PEC 7 Generic and Data Base
24 = Read PEC 4 Data Base
25 = Read PEC 5 Data Base
26 = Read PEC 6 Data Base
27 = Read PEC 7 Data Base
M-34
81875210 
						

							NOTES:
6.Error Codes are as follows:
81 = Disk Directory Full
82 
= Not Enough Spare to Define File
83 = File Size Is Larger then Disk
84 = Filename in Use
85 = Record Size too Large
86 = Device’s not 
tiqual87 = Device Invalid
88 = Filename Is Invalid
89 = Security Violation
8A = File Does not Exist
88 = Not Allowed on FMS System File
. . .8C = File Is Already Open
8D = Mode Is Invalid
8E = 
FID(s) not Available- 8F = FIDIslnvalid90 = FID Is not an Active File
91 = FID Specified Is Already in Use
92 = FID in Use by Other Processor
52108187M-3593 
= Read Past Logical EOF Attempted
94 = File Is not Open for Input
95 = File Is not Open for Output
96 = Write Past Physical EOF Attempted
97 = Seek Past EOF Attempted
98 = Record Sizes not Equal
99 = Files Open on Device
9A = FID not Sized9B = Access Is Invalid9E = Device not Ready9F = Device I/O ErrorA0 = Device Write Protected
Al = Device not Mounted
A2 = Request not Allowed on Mounted Disk
A3 = No Device Attached
A4 = Device Is Private
A8 
= Invalid Command Number
FF = Timeout 
						

							TTY Response
Log Display2.1.3 A response log is provided within the system memory to
record the responses to tests performed. The system performs
these tests when certain tasks attempted will alter the system
configuration.For example, the system conducts a series of
tests when the PEC is to be placed in service or out of service.
A response message is associated with each task attempted. If
an operating system maintenance terminal is connected to the
in-service CEC, the response messages are printed as they
occur.
__For most tasks, the response messages appear only if the task is
successfully completed. This is true even though some failures
occur. Each response message includes information about
those failures. The format for the 
resoonse messaaes is shown
M-36in Figure 2.3. As a quick reference 
guide for the responsecodes, refer to Figure 2.4.
DATEHOUR/MINUTE
ON-LINE CEC (0 )
(CONTROLS ON-LINE TTY)
CEC REPORTING
RESPONSE (0)
(REPORTS RESPONSE)
RESPONSE CODE
hdiECX ‘tih B C D E H L
xx xx xx xxxx xx
IXX = TWO 
HEXAIDECIMAL
DIGITSNN = TWO-DIGIT FAULT CODE
-.-- -REGISTER STORED DATA
VALUE AT TIME OF
RESPONSE-Hgure 2.3Response Reporting Format on TTY
Em75210