Вы находитесь на странице: 1из 25

Internal error codes

Página 1 de 25

Internal error codes

FAULT LOCATING DIRECTIONS 1/154 51-CNA 103 807 Uen C

Contents

1

General

2

Printouts

3

Summary of the error codes

4

H'10 Execution time out

5

H'11 Signal entry not found

6

H'12 Signal entry not found for backward combined signal

7

H'13 Faulty pointer

8

H'14 Jump to illegalstate

9

H'15 Buffer not available

10

H'16 Faulty multiple number in SEND statement

11

H'17 Faulty index

12

H'18 Addressed unit not loaded

13

H'19 Unreasonable TRAP operand value

14

H'1A Max number of sigbuffers exceeded

15

H'1B Wrong sequence of operative system calls

16

H'1C Write protection error

17

H'1D Illegal instruction

18

H'1E Zero divide

19

H'1F Faulty access

20

H'20 Max number of signal data exceeded

21

H'21 Invalid data at time measurement handling

22

H'22 Max nesting levels exceeded

23

H'23 Missing multiple number and/or function code in SEND statement

24

H'24 Reload data change forbidden

25

H'25 Faulty address in operative system call

26

H'26 Signal sequence exceeding

27

H'30 Wrong signal entry type

28

H'31 Wrong signal entry level

29

H'32 Physical block address error

30

H'33 Common function table (CFT) not programmed

31

H'34 Receiving LIM address not available

32

H'35 Broadcast not programmed

33

H'36 Hardware disposition table (HDT) not programmed

34

H'40 INTERLIM signal duplicated

35

H'41 INTERLIM signal is lost-mismatching sequence number

Internal error codes

Página 2 de 25

36

H'42 Faulty LIM number in incoming INTERLIM signal

37

H'43 Signal transmission error

38

H'44 Communication status error at buffer transfer

39

H'45 Communication status error at signal transfer

40

H'46 INTERLIM signal is lost-new signal in subsignal

41

H'47 INTERLIM signal is lost-subsignal collection handling

42

H'48 INTERLIM signal is lost-undefined signal type

43

H'49 Inter processor signal is lost

44

H'50 Parity interrupt

45

H'51 Unconfirmed parity error

46

H'52 Soft parity error

47

H'53 Hard parity error

48

H'54 Parity error at DMA-transfer

49

H'60 Address control failure

50

H'62 Faulty access at DMA-transfer

51

H'XX Unknown fault code

1

General

Different errors and disturbances can occur within a system in run time. The errors can originate from faulty hardware, faulty software or distorted data. The errors are called Internal LIM errors.

When an Internal LIM error occurs, by supervision or via an interrupt, the error is identified and assigned an error code.

If the operating system discovers any irregularities on a signal when it is already in the signal buffer,

the job initiated by this signal will not be started. If errors are discovered during execution of program code, execution of this job will be interrupted.

In both these cases the initiating signal, ENTER signal, will be stored as well as further information

. Via

(if any) in a history log in the system. This log can later be printed out via command HIMDP

command HIADP

the system can be ordered to print out the errors spontaneously when they occur.

If a SEND signal is incorrect or sending of this signal is not possible due to incorrect data in the

SEND statement, both ENTER and SEND signals will be stored in the error log.

A signal logged in the error log may be correct itself and indicates only some irregularities in the code

executed in connection with the signal.

Software interrupts can be used as a tool by observation patches (assembler instruction TRAP FO- FF).

When a signal is in a job buffer, it has the signal heads shown below: SW- signal head, HW-signal head & InterLIM signal head.

Internal error codes

Página 3 de 25

Byte in

Substructure Name

By te in Substructure Name Explanation

Explanation

head

0-1

Nbytes

2

b0-b1

Signal state.level

0:

X-level A-level B-level Y-level SW-SW signal HW-SW signal Broadcast signal SW-HW signal Combined forward signal without time gap

 

1:

2:

3:

 

b2-b4

Signal state.signal type

0:

 

1:

2:

3:

4:

5:

Combined backward signal without time gap

 

b5-b7

6-7: Not used Not used

0-7: Trace individual

3

b0-b2

Trace.individual Trace.sequence trace active

b3

0:

1:

No sequence trace active Sequence trace active No function time measurement active Function time measurement active

 
 

b4

Trace.function time active 0:

b5-b7

Not used

4-5

Sending unit

6

Sending LIM

7-8

Signal number

9-10

Receiving unit

11

Receiving LIM

Figure: 1-1. SW-signal head

Byte in head
Byte in
head

Substructure Name

Explanation

0

b0-b2

Access.level

0: X-level 1: A-level 2: B-level 3: Y-level Not used 0: Normal signal 1: Interprocessor signal 2: Reserved 3: InterLIM signal 0: Short asynchronous 1: format Long asynchronous format

Interprocessor signal 2: Reserved 3: InterLIM signal 0: Short asynchronous 1: format Long asynchronous format
b3

b3

b4-b5

Access.type

b6

Access.asynchronous format (only valid if receiving device board has an asynchronous interface)

Access.type b6 Access.asynchronous format (only valid if receiving device board has an asynchronous interface)

Internal error codes

Página 4 de 25

1 2-3 4-5 6-7 8-10
1
2-3
4-5
6-7
8-10

11

b7

Access.frame type

Control byte Nbytes Sender multiple Receiver multiple Switch use

Function byte

0: Normal signals 1: Reserved Always H'10 in EXS

Not used by EXS. Internally used in LSU/DSU Case:

 

InterLIM: LIM address Outgoing HW: Board function Incoming HW: Signal number

Figure: 1-2. HW-signal head

Information in the interLIM head is:

Byte in interLIM-head Name

Explanation

0

Checksum

Signal type

Checksum Signal type 0: 1: 2: 3: 4-255: Two-complement First and only subsignal First of many

0:

1:

2:

3:

4-255:

Two-complement First and only subsignal First of many subsignals Subsequent subsignal Last of many subsignals Not defined

1

2

3-4

Sending LIM Sequence number

Used at subsignal collectingSending LIM Sequence number Used to detect gaps in sequences

Used to detect gaps in sequences detect gaps in sequences

Figure: 1-3. InterLIM-signal head

The basic idea behind all different signal buffer formats is to avoid moving data around.

The following signal buffer layouts are used:

1. Struct signal_s:

All types of intraLIM-signals, most interLIM-signals and interprocessor-signals.

2. Struct interLIM_SubSignal_s:

Reception of subsequent (last) interLIM-subsignals.

3. Struct HW_OutSignal_s:

Outgoing SW-HW signals.

4. Struct HW_InSignalHW_s:

Internal error codes

Página 5 de 25

Reception of incoming HW-signals.

5. Struct HW_InSignalSW_s:

Incoming HW-signal converted to SW-format.

HW_InSignalSW_s: Incoming HW-signal converted to SW-format. Figure: 1-4. SW-SW intraLIM signal format Figure: 1-5. SW-SW

Figure: 1-4. SW-SW intraLIM signal format

to SW-format. Figure: 1-4. SW-SW intraLIM signal format Figure: 1-5. SW-SW inter- LIM/inter-processor sign al format

Figure: 1-5. SW-SW inter-LIM/inter-processor signal format at sending

SW-SW inter- LIM/inter-processor sign al format at sending Figure: 1-6. SW-HW signal formats

Figure: 1-6. SW-HW signal formats

Internal error codes

Página 6 de 25

Internal error codes Página 6 de 2 5 Figure: 1-7. Inter-LIM/inter-proc essor signal formats reception Figure:

Figure: 1-7. Inter-LIM/inter-processor signal formats reception

1-7. Inter-LIM/inter-proc essor signal formats reception Figure: 1-8. HW-SW signal formats at reception 2 Printouts

Figure: 1-8. HW-SW signal formats at reception

2 Printouts

LOGICAL ERROR ADDRESS LOGICAL PROGRAM ERROR ADDRESS PHYSICAL ERROR ADDRESS

The address where the error occurred. The address the program counter pointed at when the error occurred. The physical address where the error occurred.

3 Summary of the error codes

H'00-H'0F can be used by observation patches H'10-H'26 are used for errors with high probability of bugs in the program code H'30-H'36 are used for errors with high probability of inconsistencies in the system tables H'40-H'49 are used for error codes related to the inter-LIM signalling H'50-H'54 are used for parity errors H'60-H'62 are used for other error codes

Internal error codes

Página 7 de 25

4 H'10 Execution time out

4.1 Explanation

If the maximum executing time for a job is exceeded the operating system will interrupt its execution.

The reason why the program executes too long time can be infinite loops or quite simply that there was too much code executed during one job.

4.2 Measure

A

possible bug can be corrected with a patch.

If

the error has occurred due to the fact that it was too much code executed, the actual job has to be

divided.

5

H'11 Signal entry not found

5.1

Explanation

On a signal reception the operating system verifies whether the signal number in the signal header is entered in the signal distribution table of the receiving program unit.

This type of error is possible for the following type of signals:

• Buffered signals

• Forward combined signals without time gap

The error reason can be that the sending program unit has sent the signal to the wrong program unit.

5.2 Measure

A possible bug can be corrected with a patch.

6 H'12 Signal entry not found for backward combined signal

6.1 Explanation

Internal error codes

Página 8 de 25

This error can occur on reception of a combined backward signal with or without time gap. The reason of the error can be that the relevant location in WAIT-FOR TABLE, (used by the operating system to find the right retrieve statement) is incorrect.

6.2 Measure

A

possible bug can be corrected with a patch.

7

H'13 Faulty pointer

7.1 Explanation

Pointer to an individual out of range or the pointer is never set. The printout shows the address where the access to an individual with faulty pointer occurred.

7.2 Measure

A

patch containing a reasonable pointer value corrects this error.

8

H'14 Jump to illegalstate

8.1 Explanation

Used for undefined values in a variable, which has been received in an incoming signal, if the variable

is used to control the program flow.

Such a situation is for example at conditional BRANCH situations, if the conditional variable value is out of range. Then a call to ILLEGALSTATE is executed.

When ILLEGALSTATE is called, the signal which initiated the error is logged. Also the value which caused the call to ILLEGALSTATE is logged, if this is supported in the PLEX-code.

The reason why variables may get unexpected values could be:

• System design errors

• Signals with disturbed data contents

8.2 Measure

A possible bug can be corrected with a patch.

Internal error codes

Página 9 de 25

9 H'15 Buffer not available

9.1 Explanation

I/O buffers are a number of memory areas used by the programs to transmit large sets of data between the LIMs. In order to write or read a buffer so called buffer variables are used. The buffer variable must contain the address of the buffer so that it is possible to read or write in it.

This error occurs if someone attempts to write or read in a buffer when the buffer reference is not valid.

9.2 Measure

A possible bug can be corrected with a patch.

10 H'16 Faulty multiple number in SEND

statement

10.1 Explanation

This error occurs when a signal is sent with incorrect multiple number to hardware.

Both ENTER and SEND signal, in connection with the job, are stored.

10.2 Measure

A possible bug can be corrected with a patch.

11 H'17 Faulty index

11.1 Explanation

This error occurs when the row or column index carries a value that is too high during reading or writing in an array or matrix (multidimensional array).

11.2 Measure

A possible bug can be corrected with a patch.

Internal error codes

Página 10 de 25

12 H'18 Addressed unit not loaded

12.1 Explanation

This error is caused by one of the following reasons:

• the relevant program unit is not loaded in the addressed LIM

• the relevant program unit is not loaded at all

• the relevant program unit is loaded but the signal has been sent to another LIM

• the SEND statement contains address to an unexisting program unit

12.2 Measure

If the receiving program unit does not exist in the system or is loaded in a wrong LIM this will be corrected by a supplementary load of this unit.

If the signal has been sent to the wrong LIM the error is corrected with a patch.

If a faulty unit number has been used in the SEND statement this has to be corrected with a patch.

13 H'19 Unreasonable TRAP operand value

13.1 Explanation

This error occurs when an optional IMMEDIATE DATA operand (intended for the TRAP handler), following the TRAP instruction, has an unreasonable value.

13.2 Measure

If the error depends on a faulty patch, the patch must be removed or modified.

14 H'1A Max number of sigbuffers exceeded

14.1 Explanation

This error occurs when too many sigbuffers are used by the PLEX program at the same time.

The error is discovered by the operating system when it finds that the limit of signal buffers is exceeded.

Internal error codes

Página 11 de 25

14.2 Measure

A possible bug can be corrected with a patch.

15

H'1B Wrong sequence of operative system

calls

15.1

Explanation

This error is caused by a faulty patch for one of the following reasons:

• Double call to allocate signal buffer (call to allocate signal buffer without call to send the first allocated buffer in between)

• No call to send allocated buffer before exit

• Call to send signal buffer without preceding call to allocate signal buffer

• Faulty sending of combined backward signal

• EXIT performed in combined job

15.2 Measure

If the error depends on the faulty patch, the patch must be removed or modified.

16 H'1C Write protection error

16.1 Explanation

Write protection errors occur when a program has attempted to write in a write-protected area. The following areas are write-protected:

• Own code

• Own reload data (write access to this area is done through operating system call, added to the program code by the compiler)

• The operating system area

16.2 Measure

It

may be possible to correct the error with a patch. See also the fault locating directions for fault code

3,

WRITE PROTECTION ERROR .

Internal error codes

Página 12 de 25

17 H'1D Illegal instruction

17.1 Explanation

The error is caused by one of the following reasons:

• Address error caused by a prefetch of an instruction from an odd address

• Illegal operation code

• Privilege violation. A privileged instruction in user mode program

• LineA, LineF instruction

• CHK, CHK2 instruction

17.2 Measure

If the error depends on the faulty patch, the patch must be removed or modified.

18 H'1E Zero divide

18.1 Explanation

A division by zero has been executed by the stated program unit.

18.2 Measure

A possible bug can be corrected with a patch.

19 H'1F Faulty access

19.1 Explanation

The error is caused by one of the following reasons:

• User program has tried to access memory typed as supervisor only belonging to the operating system

• Access to the nonexistent memory has been done

• Limit out of bounds in descriptor table search

• Invalid descriptor encountered during descriptor table search

• Bus time out in EXS during PTEST instruction

19.2 Measure

Internal error codes

Página 13 de 25

A possible bug can be corrected with a patch.

20 H'20 Max number of signal data exceeded

20.1 Explanation

This error occurs when signal data have exceeded maximal number of allowed signal data.

Printout for this error contains the following information:

• LOGICAL PROGRAM ERROR ADDRESS - the address the program counter pointed at when the error occurred.

20.2 Measure

A possible bug can be corrected with a patch.

21 H'21 Invalid data at time measurement

handling

21.1 Explanation

This error occurs when a user program unit has sent faulty information at request or at removal of centralized time measurement in the operating system.

21.2 Measure

A possible bug can be corrected with a patch.

22 H'22 Max nesting levels exceeded

22.1 Explanation

This error occurs when too many combined SEND signals are nested. The limit of nested combined signals is set by the operating system to prevent the stack from overload.

22.2 Measure

A possible bug can be corrected with a patch.

Internal error codes

Página 14 de 25

23 H'23 Missing multiple number and/or

function code in SEND statement

23.1 Explanation

This error occurs when a SWHW signal has no multiple number and/or function code in SEND statement is missing.

23.2 Measure

A possible bug can be corrected with a patch.

24 H'24 Reload data change forbidden

24.1 Explanation

This error occurs when write access to reload data has been done during ongoing dump.

24.2 Measure

A possible bug can be corrected with a patch.

25

H'25 Faulty address in operative system

call

25.1

Explanation

This error occurs when write access to reload data has been done on memory address exceeding size

of accessed reload data sector.

25.2 Measure

A possible bug can be corrected with a patch.

26 H'26 Signal sequence exceeding

26.1 Explanation

Internal error codes

Página 15 de 25

This error occurs when one or more program units within a LIM are sending signals to each other. The detailed conditions of this error are:

• A signal is repeatedly sent to its own program with the same name (retransmission signal).

• Several program units make an infinite signalling loop.

26.2 Measure

Check the history log where the last eight sequences of signals before the termination of job are presented. A possible bug can be corrected with a patch.

27 H'30 Wrong signal entry type

27.1 Explanation

This error occurs when a single signal is entered in a direct signal entry or a signal from the hardware

is entered into a software signal entry.

This error is caused by one of the following reasons:

• Faulty unit address in the SEND statement

• Faulty unit value in the hardware disposition table (HDT)

• Incorrect signal data from a faulty hardware device

• SW signal entered in HW signal entry

27.2 Measure

A possible bug can be corrected with a patch if the error has been created by a faulty SEND

statement. If there is a faulty value in the HDT, data have to be reloaded in the system.

If the error originating from the same hardware device occurs again, also after reload, the device

board has to be replaced.

28 H'31 Wrong signal entry level

28.1 Explanation

Entered signal level does not match signal entry level.

The error occurs when for example an A-level signal is received on B-level in the receiving unit.

The error can occur at faulty unit addressing in the SEND statement.

Internal error codes

Página 16 de 25

28.2 Measure

A possible bug can be corrected with a patch.

29 H'32 Physical block address error

29.1 Explanation

The first thing the operating system does before entering a signal in a program unit is to read the addressed program unit number in the signal header.

Thereafter the operating system programs the MMU so that addressed program unit appears in the memory map. The program unit numbers in the header of addressed program units program sector and reload data sector are read out.

If any of these two values do not match with the program unit number in the signal header then this

type of error will be encountered.

The reason for the error can be incorrect system tables or distorted code or reload data sector.

29.2 Measure

Addressed program unit has to be reloaded.

30 H'33 Common function table (CFT) not

programmed

30.1 Explanation

A table listing all program units having central functions and the LIM in which these program units

are loaded exists in all LIMs. The table is called CFT, Common Function Table.

When a signal is to be sent to a program unit containing common functions this signal is sent to LIM 0. The operating system in the sending LIM checks in this context whether the receiving program unit number in the signal header of the signal to be sent is entered in CFT. If not this error will be encountered.

The reason of the error can be that the receiving program unit is not a common function or it is perhaps not loaded at all. The sending program unit can also have sent the signal to LIM 0 by mistake.

Both ENTER and SEND signal, in connection with the job, are stored.

Internal error codes

Página 17 de 25

30.2 Measure

If no error exists in the sending program unit it may be advisable to run a coordination start phase in

the system. This is achieved with command SFCEI CFTs are updated.

. Coordination start phase is the phase where the

31 H'34 Receiving LIM address not available

31.1 Explanation

All LIMs contain a table stating which output (transmission address) on the group switch is to be used for the extending of software signals to another LIM. The table is called PDT, Processor Distribution Table, or, differently expressed, which PCM line is the signalling link for the respective LIM.

If the signal is addressed to a LIM which does not have any LIM address, then this error will be

encountered.

The main reason for this error is that the sending program unit has tried to send the signal to a LIM that does not exist.

Both ENTER and SEND signal in connection with the job are logged.

31.2 Measure

A possible bug can be corrected with a patch. Otherwise it may be advisable to run a coordination

start phase in the system. This is achieved with command SFCEI

.

32 H'35 Broadcast not programmed

32.1 Explanation

In PLEX-language it is possible to send a signal to all LIMs in the system with a single SEND-

statement. Such a signal is called a broadcast signal.

A LIM that receives a broadcast signal sends a copy of this signal onwards to another LIM that, in its

turn, sends the signal onwards and so on. This procedure is realized with help of the Broadcast Link Table, located in each LIM and containing necessary LIM addresses. If this table is not built up, not

updated or distorted when the broadcast signal arrives, this error occurs.

32.2 Measure

Restart the LIM by the command SFCEI

in order to update the BROADCAST LINK TABLE.

Internal error codes

Página 18 de 25

33 H'36 Hardware disposition table (HDT)

not programmed

33.1 Explanation

The Hardware Disposition Table, HDT is used by the operating system to convert incoming hardware signals into SW-SW-format. The multiple number in the signal header is used as an offset in HDT in order to obtain the program unit number and pointer to the receiving program unit. If the relevant position in the HDT has an incorrect value this error will be generated.

33.2 Measure

Remove and then reinitiate the identified hardware. If the error still exists, reload data in the system.

34 H'40 INTERLIM signal duplicated

34.1 Explanation

The INTERLIM signals are sequence numbered in order to discover if any signal is lost or duplicated. If two (or more) signals received from the same LIM have the same signal sequence number this error occurs.

34.2 Measure

Check the group switch by using command GJLOP

.

If there has been a side change in the group switch, the side change might have caused this error. In

case of repeated errors, key command GSRFI

to restart the group switch.

35 H'41 INTERLIM signal is lost-

mismatching sequence number

35.1 Explanation

The INTERLIM signals are numbered in a sequence in order to discover if any signal is lost or duplicated.

The operating system in each LIM has a sequence counter for incoming and outgoing INTERLIM signals.

Internal error codes

Página 19 de 25

These counters are corresponding to the other LIMs in the system. This error occurs when received signal contains a sequence number which does not match the expected sequence number for sending LIM.

If the lost signal is a subsignal to a long INTERLIM signal, the already collected subsignals will be logged in the error log and the new subsignals belonging to this signal will be ignored.

35.2 Measure

Check the group switch by using command GJLOP

.

In case of repeated errors, key command GSRFI

command SFCEI

to restart the group switch or restart the LIM by the

in order to synchronize the INTERLIM signalling.

36 H'42 Faulty LIM number in incoming

INTERLIM signal

36.1 Explanation

This error occurs only on reception of INTERLIM signals. The operating system compares the LIM number in the signal header with own LIM number. If these two values do not match then the signal has entered the wrong LIM and this type of error will then be generated.

The error reason can be that the sending LIM has corrupted Processor Distribution Table, PDT.

36.2 Measure

Check the group switch by using command GJLOP

.

Key command GSRFI

order to update the Processor Distribution Table, PDT.

37 H'43 Signal transmission error

to restart the group switch or restart the LIM by the command SFCEI

37.1 Explanation

The following errors will cause this error code:

• Wrong length of signal according to signal head

• Signal checksum error

in

The error occurs in conjunction with reception of INTERLIM and hardware signals. When the operating system accepts such a signal it calculates how many bytes the signal has and compares this

Internal error codes

Página 20 de 25

value with stated length in the signal header. If these two values do not match this error will be generated.

37.2 Measure

For INTERLIM signals check the group switch by using command GJLOP

In case of repeated errors, key command GSRFI

to restart the group switch.

.

For hardware signals investigate the identified hardware.

38 H'44 Communication status error at

buffer transfer

38.1 Explanation

Error statistics report generated by the Communication Processor about signal and buffer transfer errors depending on disturbances during signal transmission or bugs in the communication protocol. Printout for this error contains the following statistical information:

• Number of data transfer send errors in duplex mode

• Number of data transfer receive errors in duplex mode

• Number of data transfer send errors in simplex mode

38.2 Measure

See operational directions for LIM SWITCH.

In the event of repeated errors related to Communication Processor, see operational directions CONFIGURATION OF HARDWARE, REPLACEMENT, for replacement of LPU board.

39 H'45 Communication status error at

signal transfer

39.1 Explanation

Error statistics report generated by the Communication Processor about signal and buffer transfer errors depending on disturbances during signal transmission or bugs in the communication protocol. Printout for this error contains the following statistical information:

• Number of signal send errors

• Number of signal receive errors

Internal error codes

Página 21 de 25

39.2 Measure

Check the LIM Switch see operational directions: LIM-SWITCH, LS.

In the event of repeated errors related to Communication Processor see operational directions CONFIGURATION OF HARDWARE, REPLACEMENT, for replacement of LPU board.

40 H'46 INTERLIM signal is lost-new signal

in subsignal

40.1 Explanation

The INTERLIM signals are numbered in a sequence in order to discover if any signal is lost or duplicated. This is also valid for the subsignals. When the number of bytes for a signal to be sent exceeds the size of the HW signal package, the signal has to be split into two or more subsignals. The subsignals are collected in the receiving operating system, in order to merge the subsignals to a regular signal. If a new signal is received when the operating system expects a subsignal, this error occurs.

The already collected subsignals will be logged in the error log.

40.2 Measure

Check the group switch by using command GJLOP

.

In case of repeated errors, key command GSRFI

command SFCEI

to restart the group switch or restart the LIM by the

in order to synchronize the INTERLIM signalling.

41 H'47 INTERLIM signal is lost-subsignal

collection handling

41.1 Explanation

The INTERLIM signals are numbered in a sequence in order to discover if any signal is lost or duplicated. This is also valid for the subsignals. When the number of bytes for a signal to be sent exceeds the size of the HW signal package, the signal has to be split into two or more subsignals. The subsignals are collected in the receiving operating system, in order to merge the subsignals to a regular signal. If a subsignal in a sequence of subsignals is received, and the first subsignal in the sequence has not been received previously, this error occurs.

41.2 Measure

Internal error codes

Página 22 de 25

Check the group switch by using command GJLOP

.

In case of repeated errors, key command GSRFI

command SFCEI

to restart the group switch or restart the LIM by the

in order to synchronize the INTERLIM signalling.

42 H'48 INTERLIM signal is lost-undefined

signal type

42.1 Explanation

When the INTERLIM signal received by the operating system has an invalid signal type in its Inter LIM header, this error occurs.

The signal will be logged in the error log.

42.2 Measure

Check the group switch and the LIM switch by using commands GJLOP

and LSFTI

.

In case of repeated errors, key command GSRFI

the command RFEXI

to restart the group switch or restart the system by

in order to synchronize the INTERLIM signalling.

43 H'49 Inter processor signal is lost

43.1 Explanation

The Inter processor signals between the control system sides in a LIM with duplicated control system are numbered in a sequence in order to discover if any signal is lost. If there is a gap in the sequence number this error occurs.

43.2 Measure

Check for alarms concerning duplicated control system and/or the LIM switch, and fault locate according to the Fault Locating Directions.

In case of repeated errors, reload standby side of the duplicated control system.

44 H'50 Parity interrupt

44.1 Explanation

Internal error codes

Página 23 de 25

In order to discover errors and disturbances in the memory each byte in the memory has a parity bit. A parity test is performed when access to memory takes place. If a parity error is discovered, execution of the ongoing job will be interrupted and a printout with information concerning which job was interrupted and where in the memory the parity error occurred is obtained.

When this error occurs a test is started to find out if the parity error was stable and just not a disturbance on the bus. If the parity error is confirmed a further test is executed to find out if the parity error is repairable (soft parity error) or not (hard parity error). See also the error codes H'51, H'52 and H'53.

44.2 Measure

Wait for one of the error codes H'51, H'52 and H'53 and follow the measure stated for the actual error code.

45 H'51 Unconfirmed parity error

45.1 Explanation

There has been a parity interrupt which could not be confirmed by reading at involved address.

45.2 Measure

In the event of repeated errors, follow the fault locating directions for the Alarm 110 HARD PARITY ERROR.

46 H'52 Soft parity error

46.1 Explanation

This error is caused by a disturbance in the memory.

46.2 Measure

Follow the fault locating directions for the Alarm 111 SOFT PARITY ERROR.

47 H'53 Hard parity error

47.1 Explanation

Internal error codes

Página 24 de 25

There has been a parity interrupt in the memory cell which proved to be of a hard type, i.e. the faulty bit could not be overwritten.

47.2 Measure

Follow the fault locating directions for the Alarm 110 HARD PARITY ERROR.

48 H'54 Parity error at DMA-transfer

48.1 Explanation

This error occurs when DMA-transfer is interrupted by a parity error.

48.2 Measure

Await one of the following error codes:

H'51 UNCONFIRMED PARITY ERROR H'52 SOFT PARITY ERROR H'53 HARD PARITY ERROR

49 H'60 Address control failure

49.1 Explanation

Many processes in the system require that different program units must interwork. During such interworking, individuals in records in the respective program units are linked to one another by the entering of the interworking individual's address (LIM number, program unit number, pointer value and address control) in own individual area.

Each individual has a variable that is called address control variable.

The program unit that started a job, is obligated to generate an address control value. This value, valid only during the same job, must be used for signalling and dynamic linking between all individuals located in all program units, interworking during the one and the same job.

For signal reception to an individual the operating system compares the value of the address control variable with the corresponding value in the signal before the signal is approved. If these two values do not match, this type of error remains.

49.2 Measure

Internal error codes

Página 25 de 25

A patch corrects this error, if the error has been created by a software bug, else no measure has to be

undertaken by the maintenance operator. Connection between individuals will be released when the routine cross address control is executed.

50 H'62 Faulty access at DMA-transfer

50.1 Explanation

This error occurs at access of non-existent memory by Communication Processor during DMA (Direct Memory Access).

50.2 Measure

A

patch corrects this error, if the error has been created by a software bug.

In

the event of repeated errors related to the Communication Processor, replace the LPU-board. See

operational directions CONFIGURATION OF HARDWARE, REPLACEMENT.

51 H'XX Unknown fault code

51.1 Explanation

This printout is obtained for all error codes that the system does not know.

The ENTER signal in connection with the job is logged.

51.2 Measure

-