Event Codes in STS

Event Codes in STS Changeable Exchange Adaptation
APPLICATION INFORMATION
Page 1 of 25
2/15518-ANT 227 02 Uen B
Telefonaktiebolaget LM Ericsson 2004
STS
1 Revision Information
A -> B updated with more information regarding event 7109.
2 General
This Application Information contains a list of the event messages that are generated by the STS
subsystem. Each event message is listed together with a description of the information given in
the 'Unit', 'Info' and 'Add info' fields.
The Unit field contains the identify of the Software Unit where an event has occured.
The Info field contains the event information.
The Add Info field contains optional additional event information.
This Application Information contains a brief explanation of the cause of the event message, it
should be used in conjunction with the Operational Instruction Statistics and Traffic Measurement
Subsystem Event Codes, Repair
STS Event codes are in the range 7100 - 7199.
file://C:\Program Files\ALEX\Lib\ALEX_TMP\1005\alex0340.htm
2/6/2016
Page 2 of 25
3 STS Event Codes

Code Information String
7100
7101
7102
7103
7104
7105
7106
7107
7108
7109
7110
7111
7112
7113
7114
7115
7116
7117
7118
7119
7122
7125
7126
7127
7128
7148
7149
SEND ERROR
NO BUFFER
NO PROCESS
NO INFORMATION IN TABLES
NOT EXISTING
COUNTER NOT FOUND
WRONG PARAMETER
OBJECT TYPE NOT FOUND
DATABASE NOT AVAILABLE
OUT OF RANGE IN DATABASE
OUT OF RANGE CONFIGURATION DATA
OBJECT NOT FOUND
FMS ERROR
FAULTY OBJECT TYPE
RANGE ERROR
GENERATION MISMATCH
ERROR IN AXIOJTP JOB
CP DATA FAULT
TIME CONVERSION ERROR
BUFFER MISSING
DID CONTENTS ERROR
TRANSLATION TABLE DOES NOT EXIST
ACCESS ERROR
PROCESS ABORTED
ARITHMETIC OVERFLOW
PRINTOUT ABORTED BY I/O
REPORT REQUEST ERROR
7150- 7199 Reserved For Future Use

All events occurring in module STSPSORT do not have an event code information string printed.
2/6/2016
Page 3 of 25
4 Event Codes
4.1 EVENT CODE 7100
4.1.1
4.1.1.1
Specific Event Printout

Reporting Module STDB, STJTT, STMRGP, STRGP, STRTT
Info: SEND ERROR

Add info: (Will be one of the following)
AXIOJTP, PROCESS INST HAS STOPPED
Generation file not reinit
JOB NUMBER nnn HAS A FAULTY PROGRAM NUMBER
MESSTRANS, INSTANCE HAS STOPPED
NO PROGRAM ADDRESSES AVAILABLE IN STCD nnn
INSTANCE NO TO PR3_STFIOP_ADM
Instance no to STRGP_adm
Instance no to STMRGP_adm
PRINT_REQ
Print result to STRTT
PR5_STCD_ADM HAS STOPPED
REFCHECKR
RPTID_ENQ
SEND TO pr1_db_5min
Send to sorting-program
Signal Jexdiscreq to JTP
STJTT. JOBCONTROL HAS STOPPED
STJTT. PR1_DUMPSUPPORT HAS STOPPED
STRTT, RTT COMHANDLER INST HAS STOPPED.
STSPSORT_ADM HAS STOPPED
S10_SUBSCRIBE
24 hour file not reinit
Cause:SEND ERROR is a predefined exception raised by the operating system. SEND ERROR is
raised when the receiver of a signal is not present in the system.
Note: SEND ERROR exceptions may be symptomatic of a system which is running out of
memory.
2/6/2016
Page 4 of 25
4.1.1.2
4.1.2
Non Specific Event Printout
4.1.2.1 Reporting Modules STCD, STDB, STFIOP, STJTT, STMRGC, STMRGP, STOGH, STRGC,
STRGP, STRTT, STSORT
Info: SEND ERROR
Add info:
Cause: SEND ERROR is raised when the receiver of a signal is not present in the system.
Note: SEND ERROR exceptions may be symptomatic of a system which is running out of
memory.
4.2 EVENT CODE 7101

4.2.1
4.2.1.1

Reporting Module STDB, STJTT, STTRAN
Info: NO BUFFER
DID not copied from CP
NO BUFFER at SEND signal
NO SPACE AVAILABLE FOR ADM BUFFER
NOT POSSIBLE TO ALLOCATE A BUFFER FOR DID REQUESTS
Send to pr1_db_5min or pr2_db_24hour
Send to STDB pr3_stdb_adm
Cause: NO BUFFER is raised if there is no memory available to the operating system to allocate a
buffer of the requested size.
Note: When NO BUFFER occurs at runtime this is a serious problem. Expect erratic observation
alarms in the SPS EVENT LOG all relating to a shortage of system memory.
4.2.1.2
Reporting Module STTRAN
Info: NO BUFFER
Add info: n MEMORY ALLOCATION RETRIES
(Where n is a value between 1 and 5.)
Cause: STS has attempted to allocate a buffer and has run out of memory if the buffer is small
STS is halted but as this buffer is large STS will make 5 memory allocation retries before halting
STS.
2/6/2016
4.2.2
Page 5 of 25
4.2.2.1
Reporting modules STDB, STFIOP, STMRGC, STMRGP, STOGH, STRGC, STRTT, STSORT
Info: NO BUFFER
Add info:
Cause: NO BUFFER is raised if there is no memory available to the operating system to allocate a
buffer of the requested size.
Note: When NO BUFFER occurs at runtime this is a serious problem. Expect erratic observation
alarms in the SPS EVENT LOG all relating to a shortage of system memory.
4.3 EVENT CODE 7102

4.3.1
4.3.2
4.3.2.1
Reporting Modules STFIOP, STMRGC, STMRGP, STOGH, STRGC, STRTT, STSORT
Info: NO PROCESS
Add info:
Cause: NO PROCESS is a predefined exception raised by the operating system. NO PROCESS is
raised if there is no memory available at process activation. There has been a failure in
activating a process.
4.4 EVENT CODE 7103

4.4.1
4.4.1.1

Reporting Modules STACC, STJTT
Info: NO INFORMATION IN TABLES

Add Info: NO PROGRAM ADDRESS AVAILABLE IN STCD nnn
(Where n represents an event specific numeric value)
Cause: STS has a list of actions which it performs at certain times during a Basic Recording
Period (BRP). STS cannot access this list as it is either corrupted or does not exist. This is a
serious fault.
2/6/2016
4.4.1.2
Page 6 of 25
Reporting Module STCD

Add Info: STTRAN failed to update the translation tables during configuration.
Cause: Translation tables are updated by command, at CP restart or when the STS Measurement
Database is configured. STS has failed to update the translation tables. There are two known
causes of this event .
a
Possible Cause A - STS system files STTRANF1 or STTRANF2 have become corrupt.
b
Possible Cause B - STS cannot receive information from the CP. This is not an STS fault,
this is a CP or JTP fault.
4.4.1.3
Reporting Module STMRGP, STRGP

Add Info: No counter info when building recpars
Cause: STS failed to find an Object Type name or a counter name when building its recording
parameters.
4.4.2
4.5 EVENT CODE 7104

4.5.1
4.5.1.1

Reporting Modules STMRGP, STRGP
Info: NOT EXISTING

Add Info: No counter info when building recpars
Cause: STS failed to find an Object Type name or a counter name when building its recording
parameters.
4.5.2
4.5.2.1

Reporting Modules STACC, STSORT, STSPSORT
Info: NOT EXISTING

Add Info:
Cause: STS has attempted to process a DID it should not. STS has found an erroneous Object
Type number or DID position. STS may be encountering memory problems.
2/6/2016
Page 7 of 25
4.6 EVENT CODE 7105

4.6.1
4.6.1.1
Reporting Modules STACC, STSORT
Info: COUNTER NOT FOUND

Add Info: For additional information reference section 5.1 Error in STS sorting or accumulation,
Add Info format.
Cause: STS cannot find a counters position in the STS Measurement Database.
Note: STS will flag the counter as faulty if it is writing to the STS Measurement database or it
will explicitly initialize the not found counter position to 0 if it is reading counter values from the
Measurement database.
4.6.2
4.7 EVENT CODE 7106

4.7.1
4.7.1.1
Reporting Module STACC, STSORT
Info: WRONG PARAMETER

Add Info format.
Cause:
a
Possible Cause A - STS has found a faulty parameter in data sent from the CP.
b
Possible Cause B - STS could not find an Object Type in the data sent from the CP.
c
Possible Cause C - The number of individuals that STS has been asked to process is faulty.
d
Possible Cause D - While STS was translating a DID position into a route number it
encountered a faulty route number in the DID position.
e
Possible Cause E - STACC has received a corrupt instruction from STS.
Possible Cause F - A sorting parameter has been found to be faulty.
Add Info: (Will be one of the following)
Adm-pointer NIL or illegal
DID-pointer outside adm-area
First value record illegal
Noof adm-parts is 0
2/6/2016
Page 8 of 25
Too many adm-parts

Value pointer illegal
Value record too small
Cause: STS has received corrupt information from the CP. This is not an STS fault.
Note: STS has not been able to run its sorting/accumulation program.
4.7.1.2
Reporting Module STDB

Faulty data in buffer, record-number for buffer cannot be calculated.
Generation time handling error
Cause: STS has found that certain data has become corrupt.
4.7.2
4.8 EVENT CODE 7107

4.8.1
4.8.1.1

Reporting Module STSORT
Info: OBJECT TYPE NOT FOUND

Add info: For additional information reference section 5.1 Error in STS sorting or accumulation,
Add Info format.
Cause: When STS was trying to calculate the record number in the STS Measurement Database,
it found that the Object Type number was faulty. STS could not continue calculating the record
number.
4.8.2
4.9 EVENT CODE 7108

4.9.1
4.9.2
4.9.2.1

Reporting Module STACC, STDB, STSORT, STSPSORT
Info: DATABASE NOT AVAILABLE
2/6/2016
Page 9 of 25
Add Info:
Cause: This event is raised by STS, if STS tries to write to or read from the STS Measurement
Database while the Measurement Database is not open.
a
Possible Cause A - The exchange is in an alarm state.
b
Possible Cause B - The Measurement Database is not open as STS is in the process of
creating the database.
c
Possible Cause C - While STS was attempting to store information in the Measurement
Database, STS could not calculate a record number to store data.
d
Possible Cause D - The Measurement Database has not been created properly.
e
Possible Cause E - The STDBRCFILE or the STDB24HFILE file has become corrupt.
f
Possible Cause F - File STDBRCFILE or STDB24HFILE are not installed correctly.
2/6/2016
Page 10 of 25
4.10 EVENT CODE 7109

4.10.1
4.10.1.1

Info: OUT OF RANGE IN DATABASE

Add Info format.
Cause: The number of objects / records delivered from the CP is greater than the number of
objects allocated for storing this Object Type in the Measurement Database.
Action: Increase the number of objects (NOBJ) for the related Object Type in the Measurement
Database, use the command SDDOC. See Operational Instruction Statistics and Traffic
Measurement Subsystem Event Codes, Repair.
Note: If this event code is received in the SPS EVENT LOG some information for some objects
collected for this BRP will be lost as some values will not be stored in the STS Measurement
Database. This alarm will be repeated for every BRP as long as the condition exists.
4.10.2

4.11.1
4.11.1.1

Info: OUT OF RANGE CONFIGURATION DATA

Add Info format.
Cause:
a
Possible Cause A - STS encountered an Object Type Number which is faulty.
b
Possible Cause B - The job number or DID position which STS is currently processing is
faulty.
2/6/2016
4.11.1.2
Page 11 of 25
Reporting Module STCD

Add Info: Objtype = nnn
Cause:
a
Possible Cause A - STS encountered an Object Type Number which is faulty.
b
Possible Cause B - The job number or DID position which STS is currently processing is
faulty.
4.11.1.3
Reporting Module STJTT

Add Info: C37_PGMNO_GENERAL_STSPSORT IS FAULTY
Cause: STS is trying to order SP DID values, failure has occurred as it could not find the correct
program to perform this.
Add Info:
JOB NUMBER nn HAS A FAULTY PROGRAM NUMBER
Cause: A program number which STS expects to be in a certain range is outside of this range.
Add Info: NO PROGRAM ADDRESSES AVAILABLE IN STCD, nn
Cause: STS is trying to process a DID but it cannot find the correct processing program.
4.11.2

4.12.1
4.12.1.1

Info: OBJECT NOT FOUND

Add Info format.
2/6/2016
Page 12 of 25
Cause: There was a problem encountered when STS was calculating a counters position within
the Measurement Database. The object position STS received is faulty, and could not be found.
Note: All the counter values for this object will be lost.
4.12.2
4.12.2.1
Reporting Module STSPTRAN, STTRAN
Info: OBJECT NOT FOUND

Add Info:
Cause: There has been a problem translating a CELL ID to a CELL NAME or an object which STS
received is faulty.

4.13.1
4.13.1.1

Reporting Module STMRGP, STRGP
Info: FMS ERROR

STREPSPFILE NOT CLOSED
STFORMFILE NOT CLOSED
Cause: STS could not close a file.
2/6/2016
4.13.2
4.13.2.1
Page 13 of 25

Reporting Module STACC, STCD, STDB, STJTT, STRTT, STSORT, STSPSORT
Info: FMS ERROR

Add Info: aaaaaaa aaaaaaaaaaaaaaaaaaaaaaaa
(reason)(filename) (subfile name)
(Where a represents an alphabethic character)
Cause: An FMS ERROR indicates that STS is having problems reading from or writing to files.
a
Possible Cause A - STS could not access the file STMPFILE. This file is used to store
measurement program data. All STS Measuring programs will not work.
b
Possible Cause B - STS could not access the STDBRCFILE file. This file is used to store
counter values for the STS Measurement Database. Counter values will be lost.
c
Possible Cause C - STS could not access the STCPDUMP file. This is used to store copied
counter data from the CP to the SP. If STS has not been configured to use the JTP
conversion mode collection mechanism, no counter data from the CP can be stored.
Note : Depending on the file reported in the (filename) field of the Add Info section, an FMS
ERROR will affect STS in a number of different ways.

4.14.1
4.14.1.1

Info: FAULTY OBJECT TYPE

Add Info format.
Cause:
a
Possible Cause A - STS cannot find a translation table.
b
Possible Cause B - STS has attempted to process an object from and object type which
does not exist.
4.14.2

4.15.1
2/6/2016
4.15.2
Page 14 of 25
4.15.2.1
Reporting Modules STACC, STJTT, STRTT, STSORT, STTRAN
Info: RANGE ERROR

Add Info:
Cause: A RANGE ERROR exception is a predefined exception which may be raised by the
operating system at any time. A value is found to be outside its declared range.

4.16.1
4.16.2
4.16.2.1

Reporting Module STDB
Info: GENERATION MISMATCH

Add info:
Cause: When STS was storing the latest generation it found that the time interval between
generations was less than 5 minutes.

4.17.1
4.17.1.1

Info: ERROR IN AXIOJTP JOB

Add Info: nnnn COUNTERS WERE COLLECTED nnnn COUNTERS WERE COLLECTED FOR aaaaaaaa
(Where a represents an alphabetic character)
(Where n represents a numeric value)
Cause: STS has attempted to collect too many counters from the CP.
Note: The operator should reduce the number of counters being collected by STS.
2/6/2016
Page 15 of 25

BREAKDOWN ON TRANSPORT LEVEL OR LOWER
CONGESTION IN JTP
CP USER NOT AVAILABLE
INCOMPLETE DATA
ILLEGAL RESULTCODE
CP FUNCTION BUSY
UNABLE TO INITIATE A CONV WITH JTP
Cause: STS has received an unexpected disconnection indication from the CP or STS has been
unable to communicate with LAVS. The CP/ JTP has encountered one of the above difficulties.
Note: If STS has not been able to communicate with LAVS expect no counter values to be
collected for this BRP.
BLOCK PASSIVATED OR INDIVIDUAL VARIABLE DECREASED TO ZERO.
BUFFER CONGESTION
CLOSE - FILE ERROR
CP FUNCTION BUSY
ILLEGAL RESULTCODE
INPUT DATA ERROR
OPEN - FILE ERROR
VARIABLE SIZE DECREASED
WRITE - FILE ERROR
Cause: STS has received corrupt data ffrom the CP. STS orders then processes 150 buffers at a
time from the CP. This event code will be seen if STS tries to order data when it has become too
late in the BRP for STS to order and process more buffers before the end of the BRP.
Add Info: ILLEGAL RESULTCODE REATTEMPTING REGISTRATION
Cause: When STS tried to register with JTP it was unable to do so. STS reattempts registration.
4.17.1.2

DID not copied from CP
result code from JTP = BUFFER CONGESTION
fileerror
Cause: STS cannot connect to the CP so STS has not received any translation information from
the CP.
4.17.2
2/6/2016
Page 16 of 25

4.18.1
4.18.1.1

Info: CP DATA FAULT

DID NUMBER nnn WAS NOT FOUND IN THE HEADER
NUMBER OF INDIVIDUALS GIVEN FOR DID NUMBER nnn IS INVALID
VALUE OUT OF RANGE IN ADM RECORD NUMBER OF DIDS CONVERTED nnn BYTE INDEX = nnnn
VALUES OUT OF RANGE IN DUMPHEAD
nnnn FOR FIRST FREE RECORD IS OUT OF RANGE
nnnn FOR FIRST VALUE RECORD IS OUT OF RANGE
nnnn IS A BYTE OFFSET VALUE OUT OF RANGE FOR DID
nnnn IS A DID NUMBER OUT OF RANGE
nnnn IS A NUMBER OF DIDS OUT OF RANGE
nnnn IS A START RECORD NUMBER OUT OF RANGE FOR DID
Cause: STS has received corrupt data from the CP.
Info: CP DATA FAULT
Add Info: NO DIDs FOUND IN DUMPFILE WHEN PVRESULT_CODE = 0
Cause: STS may use a DUMPFILE to read DID information from hard disk into primary memory.
If a situation arises where it is not possible to read a specific DID or the DID information is not
available, this event code is raised.
Note: Counter information for this particular DID will be unobtainable. There may be problems
with any report using this particular DID.
4.18.2
2/6/2016
Page 17 of 25

4.19.1
4.19.1.1

Reporting Module STJTT, STRTT
Info: TIME CONVERSION ERROR

Add info:
Cause:
a
Possible Cause A - When STS attempted to convert the system clock to a date STS
calculated an invalid date.
b
Possible Cause B - When STS attempted to convert the system clock to a time STS
calculated an invalid time.
c
Possible Cause C - When STS attempted to calculate the current BRP using the system
clock STS calculated an invalid BRP.
d
Possible Cause D - If the start time is later than the stop time for a BRP this event will be
raised.
e
Possible Cause E - The system time has become corrupt.
4.19.2
2/6/2016
Page 18 of 25

4.20.1
4.20.1.1

Reporting Modules STACC, STSORT, STSPSORT
Info: BUFFER MISSING

Add Info format.
Cause: After STS has sorted the counter values for a particular object from a particular Object
Type. STS inserts these values into a buffer it uses this buffer to store the counter values in the
STS Measurement database. STS could not write these values into the Measurement database
for this BRP as the buffer is missing.
4.20.2

4.21.1
4.21.1.1

Info: DID CONTENTS ERROR

Add info: Operation ID (code) not copied from CP
Cause: Updated translations were not copied from the CP.
Add info: RANGE ERROR
Cause: While STS was filling/updating its translation tables, STS accessed a value outside its
range.
Add info: STRING LENGTH FAULT IN DIDNO nnnn
VARIABLE NO nnnn
INDIVIDUAL NO nnnn
Cause: Data being transferred from the CP must be converted into SP format. While this
conversion was taking place STS found that the string length for a DID was faulty. This may be
due to a fault in the buffer transferred from the CP.
2/6/2016
4.21.2
Page 19 of 25

4.22.1
4.22.1.1

Reporting module STACC, STSORT, STSPSORT
Info: TRANSLATION TABLE DOES NOT EXIST

Add Info format.
Cause: While STS was attempting a translation it could not find the translation table for the DID
received from the CP.
4.22.2

4.23.1
4.23.1.1

Info: ACCESS ERROR

Add info: For additional information reference section 5.1 Error in STS sorting or accumulation,
Add Info format.
Cause: STS has attempted to access/manipulate an invalid reference in a pointer.
4.23.1.2
Reporting Module STJTT, STRTT
Info: ACCESS ERROR

FAULTY BUFFER FROM JTP
FAULTY BUFFER FROM JTP (CONTAINING NMC INFO)
NIL POINTER FOR ADM BUFFER
NIL POINTER FOR HEADER BUFFER
FAULTY BUFFER FROM JTP (CONTAINING DCAT INFO)
Cause: STS has attempted to access/manipulate an invalid reference in a pointer.
4.23.2
2/6/2016
Page 20 of 25

4.24.1
4.24.2
4.24.2.1

Reporting modules STMRGP, STRGP
Info: PROCESS ABORTED

Add info:
Cause: An abortion of this kind means STS has encountered a serious problem, for example an
APZ alarm. STS has no possibility of continuing its work.

4.25.1
4.25.2
4.25.2.1

Info: ARITHMETIC OVERFLOW

Add info:
Cause: Arithmetic overflow has occurred, STS has attempted to assign a value into a variable
which is too large for that variable to hold.
2/6/2016
Page 21 of 25

4.26.1
4.26.1.1

Reporting modules STFIOP, STMRGC, STMRGP, STRGC, STRGP
Info: PRINTOUT ABORTED BY I/O

Add info: Mt dest not obtainable.
Cause:
a
Possible Cause A - The Support Processor Module MESSTRANS is not obtainable.
b
Possible Cause B - The terminal you are printing to is not configured properly.
c
Possible Cause C - The terminal you are attempting to print to is currently busy.
Note: If there is a problem with MESSTRANS as it is the SP module which deals with command
and printout translations there may be no STS printouts. Also, as there is no conversation
between STS and MESSTRANS STS commands may be unrecognized by the exchange.
4.26.2
4.26.2.1

Info: PRINTOUT ABORTED BY I/O

Add info:
Cause: This event code will occur if the operator aborts a printout with the BREAK command.
Note: EOT DURING PRINTOUT received in the report. Printout will be aborted.

4.27.1
4.27.1.1

Info: REPORT REQUEST ERROR

Add Info: Max number of exec instances is reached.
Cause: STS has reached the maximum number of reports allowed.
Note: Recording will be turned off when this event occurs. No file or alphanumeric reports will
contain any data for two basic recording periods
Info: REPORT REQUEST ERROR
Add Info: Simultaneous demand printouts not allowed.
Cause: The number of allowed simultaneous demand printouts has been exceeded.
2/6/2016
Page 22 of 25
Note: FUNCTION BUSY message printed to the terminal.

4.27.2
2/6/2016
Page 23 of 25
5 Additional Information
5.1 Error In STS sorting or accumulation program, Add Info format.
When an error has occurred in an STS sorting or accumulation program the add Info printout is
useful to STS designers in accessing where a problem has occurred. The Add Info field will
display an error in the same general format as below but certatin parameters such as Individual
no or Block number may be replaced by parameters like Objectid or table size.
Error in p43_13_general:
Parameters:
Job no: nn
Obj type: nnn
Object number
= nn
Individual no = nnn
DID position = nn
Block number = aaannnnnnnn
END OF ERROR MESSAGE.
(Where a represents an alphabethic character)
(Where n represents a numeric value)
Example of how the additional information of an STS sorting or accumulation error will look.
2/6/2016
Page 24 of 25
6 Glossary of Terms
6.1 Object Type
An Object Type corresponds to a specific type of equipment or type of function units in the
switch for which statistical data measurement may be of interest. An Object Type corresponds to
a unique set of counters which are measurable units within the equipment.
6.2 Object
An Object is defined as an Individual within the Object Type. Each Object Type contains one or
more objects, each object having the same set of counters. If an Object Type is compared to a
file then in most cases an object can be thought of as being analogous to a record in that file.
6.3 Counter
Each object within an Object Type has a set of counters which are analogous to fields within a
record. The counters are implemented in the counter owning block and images of them at
specified intervals, called Basic Recording Periods (BRPs), are transferred to STS and stored in a
database.
6.4 BRP
The Basic Recording Period is the interval for which counters are collected before being
transferred to a database. This interval may be specified by the user as 5 or 15 minutes in the
command SDDOC.
6.5 DID
A Data Interface Description (DID), is a means of reporting a particular data structure within CP,
for use by STS in creating statistical information.
6.6 Measuring Program

This function allows the scheduling of STS reports such that a user may specify a start and an
end time at which a report shall be output.
6.7 Recording Parameter

This is a column identifier in the alphanumeric report representing either an actual counter or a
mathematical expression involving counters, constants and operators defined with the command
SDRPI.
6.8 Generation
STS stores counters read from the CP in the STS Measurement Database. The counters included
in such a reading are called a generation. The time interval between each generation is the BRP
time.
2/6/2016
Page 25 of 25
6.9 Translation Table

Translates internally recognised Object ID's into externally recognised names.
6.10 Info
The information string being reported in the event code.
6.11 Add Info

The additional information string being reported in the event code.
6.12 Job Number

A job is a piece of work STS must perform. Each job has a specific number.
6.13 Unit
The software unit identity where an event has occurred.
2/6/2016

Event Codes in STS

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Event Codes in STS

Uploaded by

Copyright:

Available Formats

Event Codes in STS Changeable Exchange Adaptation

2/15518-ANT 227 02 Uen B

Telefonaktiebolaget LM Ericsson 2004