TECHNICAL COMMUNICATION No.

TC0384 Date : 13-11-2002

OmniPCX 4400 Nb of pages : 13

URGENT

NOT URGENT TEMPORARY PERMANENT

SUBJECT : DATABASE : CHECKING THE MAXIMUM VALUES OF INSTALLATION DATA AND

RELATED PROBLEMS

Please find hereafter the "Database : Checking the maximum values of installation data and related
problems" technical communication.

1
 OmniPCX 4400
DATABASE : CHECKING THE MAXIMUM
VALUES OF INSTALLATION DATA AND
RELATED PROBLEMS

CONTENTS

1. GENERAL.....................................................................................3

2. DESCRIPTION OF INFORMATIONS DISPLAYED BY THE

CFGUPDATE COMMAND .............................................................4

3. OCCURED PROBLEMS ..................................................................6

4. MEMORY ALLOCATED FOR THE MANAGEMENT ..........................7

5. SPECIFIC CASES...........................................................................7
5.1. Accessing the sql commands..................................................................... 7
5.2. Counting the objects ................................................................................. 7
5.3. Network.................................................................................................... 8
5.4. Trunks ...................................................................................................... 8
5.5. Translator ................................................................................................. 8
5.6. Supervisions ............................................................................................. 9
5.7. Abbreviated numbers ............................................................................... 9
5.8. Users ........................................................................................................ 9
5.9. Business codes ........................................................................................ 10

6. LIST OF PARA_MAO FIELDS........................................................11

7. RESULT OF SPADMIN/DISPLAY OPS LIMITS COMMAND .............12

ED. 13-11-2002 1 TC0384

 OmniPCX 4400
DATABASE : CHECKING THE MAXIMUM
VALUES OF INSTALLATION DATA AND
RELATED PROBLEMS

TC0384 2 ED. 13-11-2002

 OmniPCX 4400
DATABASE : CHECKING THE MAXIMUM
VALUES OF INSTALLATION DATA AND
RELATED PROBLEMS

1. GENERAL
This technical communication is based on Release 5.0 Ux.

Any change must be preceded by a backup and be carried out by an OmniPCX

4400 ACSE.

The previous releases do not have all the data mentioned below especially for Actis fields.
Three data files are used to check the maximum values of an OmniPCX 4400 installation:
− software.mao
It contains the software locks but does not set the installation. This file is loaded in memory and
checks that the management does not exceed the maximum values.
− hardware.mao
It contains some data ("PARA_MAO" lines followed by a digit) which are going to set the CPU
memory (remanent) and check some maximum values for certain MAO objects.
− config.mao
It contains other similar informations. Some are redundant with the hardware.mao file. So they
are not taken into account by the system: the corresponding data of hardware.mao file takes first
place since some of these values are brought by new releases in the hardware.mao file (they are
part of data Actis). Nevertheless these redundant fields of config.mao file are kept.
These files (text) are located in the /usr3/mao directory and are stored in backups.
These three files are stored as follows:

Files Reading commands Observations

software.mao spadmin Menu 1 to check what is managed (memory
edition).
Menu 2 to edit the corresponding file.
hardware.mao cfgUpdate For some values of PARA_MAO fields.
cat /usr3/mao/hardware.mao
spadmin Field 8 : Display OPS limits.
config.mao cfgUpdate

Notes
The cfgUpdate command read both the data of config.mao and hardware.mao files; see hereafter
for more details.
The software.mao and hardware.mao files are supplied by Actis and config.mao when creating a
blank database. It contains the maximum data which can be accepted for most installations but must
be checked. During database translations, it can be translated.
The reading/modification rules of common data to hardware.mao and config.mao files are the
following:

ED. 13-11-2002 3 TC0384

 OmniPCX 4400
DATABASE : CHECKING THE MAXIMUM
VALUES OF INSTALLATION DATA AND
RELATED PROBLEMS

− The reading with cfgUpdate displays, for common data, the value read in the hardware.mao
file (and not in the config.mao file). When changing one of these values, the two files updated.
− The modification of one of data in the hardware.mao file (with vi), is nor reported in the
config.mao file. This is not very important since the common data are really taken into account
from the hardware.mao file.
− The modifications in these files are taken into account only after rebooting.

2. DESCRIPTION OF INFORMATIONS DISPLAYED BY THE cfgUpdate

COMMAND
This command is launched from /usr3/mao directory.
An error or inconsistency fields will occur (values to -1) if the command is launched from an other
directory.
Display of data

Maximum values in the installation

Users : 1560
Physical equipment numbers : 882
Equipment blocks : 1344
1/2 com : 351

Hit any character to go on

These values depend on other parameters read in config.mao file

Users = Stations + Data Term. + Patients + 5 (Substitution) + 150 (HE-Minitel) +

10 (Attendants)
Physical equipments = (Stations + Data Term) * Equipment_Coefficient
Equipment blocks = Shelves * 1,2 * 28
Half-context = MAX (read value, calculated value)

Fields to be changed

Reading of config.mao and Corresponding

Commentaries
hardware.mao files parameters
1 Stations PARA_MAO 2
2 S0 Buses PARA_MAO 17
3 Data terminals
4 Patients (hospital) Number of fictive sets PARA_MAO 18
5 Trunks See hereafter PARA_MAO 3
6 Equipment_Coefficient
8 Nodes in the network
9 UA Links
10 Shelves (migration excluded) PARA_MAO 19
11 1/2 com PARA_MAO 4
12 TS reserved for operators on INT/RT2

TC0384 4 ED. 13-11-2002

 OmniPCX 4400
DATABASE : CHECKING THE MAXIMUM
VALUES OF INSTALLATION DATA AND
RELATED PROBLEMS

links
13 Tables of the public translator
14 Tables of the satellite translator
15 References in the public translator
16 References in the satellite translator
17 Abbreviated numbers
18 DECT Handsets
19 Supervisable MCDU
20 Number of Sub-Networks
21 Number of Network Set in Hunting
Group
22 Number of ARS route lists
24 Number of areas (accounting
duration)
25 Number of Charge Scales (accounting
duration)
26 Supervisable Trunks / Trunk groups
27 Number of Network Supervisor
34 Number of x25 command
abbreviated numbers
35 Number of called filter
36 Maximum Number Of Account Codes Business codes of
accounting: in D1.311.4
the number is changed
from 255 to 2000 ; see
section 5.9.

Reading of hardware.mao file Corresponding

parameter
41 Remanent size Size of the memory for PARA_MAO 1
telephone application
42 Stand-alone Presence of X25 actors PARA_MAO 5
43 Number of BLF PARA_MAO 6
44 Phone-book (x 2000) PARA_MAO 7
45 SBC PARA_MAO 8
46 4635X PARA_MAO 10
47 4630 PARA_MAO 11
48 4855 PARA_MAO 12
49 Hotel accesses PARA_MAO 13
50 ACD supervisor accesses PARA_MAO 14
51 Set display languages PARA_MAO 16

Note
The value "-1" corresponds to an unavailable PARA_MAO.

ED. 13-11-2002 5 TC0384

 OmniPCX 4400
DATABASE : CHECKING THE MAXIMUM
VALUES OF INSTALLATION DATA AND
RELATED PROBLEMS

If the hardware.mao file is missing, the cfgUpdate tool read the content of the config.mao file. Each
field located before the Values read in hardware.mao file line corresponds ALL to the data of
config.mao file and the following fields are marked "-1". This configuration MUST NOT exist. It is
dangerous for system status and means that OPS has not been correctly installed (the hardware.mao
is missing). The test_ops command under mtcl login checks that each OPS files is available with
correct Unix rights.
If one or more fields are set to "-3" or "-1", this means that the hardware.mao file supplied by Actis is
not is conform to telephone application release (the software of the new release requires a new
value: one of PARA_MAO field of hardware.mao file is missing : a new Actis configuration is
required).
If at the end of cfgUpdate configuration, a trap-message type is sent, this means that some
PARA_MAO fields of hardware.mao file are available but not interpreted by the telephone release.
This problem occurs when a value of PARA_MAO field is changed with this tool. If the modification
concerns data of config.mao file, it is done without error message.

3. OCCURED PROBLEMS
When the config.mao or hardware.mao files are not correctly set, some problems appear up to
perturb equipment or features. The management tools will also give wrong results. The checkdb
command can also show inconsistencies with a description difficult to understand. It is important to
do again an Actis configuration on problem regarding values of hardware.mao file. However, you
can selectively change some values manually meanwhile a correct OPS. In that case, an Actis
configuration and the installation of new OPS must be done as soon as possible.
This wrong setting is due to the management software which has not checked these resources.
Before managing these resources, it is important to check the maximum data of the installation. The
management will be performed both by Actis and with cfgUpdate command according to
requirement.
− If the managed object is checked by the software, an exceeding message of capacity or lack of
memory informs the user.
− If the object is not checked, anomalies will occur at the next reboot.
Objects such as subscribers, abbreviated numbers, trunks are not counted by the software. The
logical number is used as reference.
If an installation has a range of abbreviated numbers beginning at 3000 with 1000 numbers,
the software allocates the index 3999 to the last number. If the corresponding data in
cfgUpdate (see table above : 17 Abbreviated numbers ) is set to 2000, the abbreviated
numbers will not function. The software considers that there are 3999 abbrevieted numbers in
the installation. After a checkdb (maintenance command simulating the initialisation/test of
remanents in memory), some error messages of type below will appear:
ERROR 2656 : DATA INCONSISTENCY TYPNBAB info3=xxxx.
In some releases, the values corresponding to "public and satellite translator" data (fields 13 to 16 in
cfgUpdate) are too large (example: 1000000) ; they can be reduced significantly (typically 1000).

TC0384 6 ED. 13-11-2002

 OmniPCX 4400
DATABASE : CHECKING THE MAXIMUM
VALUES OF INSTALLATION DATA AND
RELATED PROBLEMS

Note about checkdb

This command is a diagnostic tool which simulates the location of remanents (memory allocated to
the telephone application) of MAO objects (disk data towards memory). It must give the same error
results than when staring the telephone application (process initrem).

4. MEMORY ALLOCATED FOR THE MANAGEMENT

The PARA_MAO 1 field of hardware.mao file manages the total size of telephone data loaded on the
disk from the database. There is always a minimum of 400 KB memory for the management. This
size can be larger (for instance when starting a blank database, there is almost no data to save in
memory). When this zone is filled and there is still management to be carried out, an error message
will inform that the memory zones are full.
That means the OPS has not been correctly set. Check that these OPS data corresponds to final
management to be carried out.
As of Release 4.2 (and specifically to BMI installation in Release 3.2M), the system message 4120 No
more memory in remanents occurs when the memory used by the management is higher to
PARA_MAO 1 field.
The given information in argument have the values required by the database and PARA_MAO 1
ones.
In that case, you should envisage a configuration by Actis.

5. SPECIFIC CASES

5.1. Accessing the sql commands

To launch the sql command mentioned in this document, proceed as follows:
− login : mtcl
− directory : /usr3/mao
− command : cuser
− on prompt ->> you are ready for the dialog; enter the command
− enter a dot ( . ) then press the Enter to quit.

5.2. Counting the objects

Some objects are really counted using management tools.
For other objects, the counting is done by detection of the highest identifier. "Holes" can occur in the
identifiers : for instance for 10 instances of an object, the last identifier can be equal to 20.
The various cases listed in this document are the ones which perturb the most frequently the PABX
configuration.
To do not have to reboot OmniPCX 4400, the checkdb command must be used to help diagnostic
during various tests listed below.

ED. 13-11-2002 7 TC0384

 OmniPCX 4400
DATABASE : CHECKING THE MAXIMUM
VALUES OF INSTALLATION DATA AND
RELATED PROBLEMS

5.3. Network
− Number of nodes/subnetworks in cfgUpdate
Change the 8 and 21 fields according to the management. By default, there are 16 or 32 nodes
maximum. These fields must be managed before setting a node number/network higher than
the value in cfgUpdate, otherwise when setting a node number/network hither than these
values, a management error will occur and the modification cannot be done.

5.4. Trunks
Informations about results following the checkinitrem TRACE command launched in the /usr3/mao
directory.

(404)xb004004> checkinitrem TRACE

Data base checking in progress ...
...
Number of trunks :50 (1)
...
Maximum values of the installation
...
Real trunks : 336 (2)
Trunks : 672 (3)
...
MAX_NB_JONCT = 672 (4)
...
maxInit MAX_NB_REEL_JONCT = 336 (5)
...et fin de l’outil.

(1) Displays always the value read in the PARA_MAO 3.

(2) Real value if the PARA_MAO 3 is less than this value. Otherwise display of the PARA_MAO 3
value.
(3) Idem (2) but multiplied by 2.
(4) Idem (3) if the PARA_MAO is less than "Real trunks" (2), otherwise display of the PARA_MAO
value multiplied by 2.
(5) Idem (2).
The maximum number of entries in TABJONC is never displayed.
The "Real trunks" value is the real + fictive number of trunks in the system.

5.5. Translator
When the translator reaches the maximum of entries, the "Translator Full" message is displayed if
adding a new number.
Problem in initrem or checkdb of type :
ERROR 2656 : DATA INCONSISTENCY TABTRPTT info3=3
…etc.
This type of error on the TABTRPTT table occurs only in Release 2.x and below. A new public
translator table is used in other Releases (table xxx).

TC0384 8 ED. 13-11-2002

 OmniPCX 4400
DATABASE : CHECKING THE MAXIMUM
VALUES OF INSTALLATION DATA AND
RELATED PROBLEMS

Change the fields(s) 13 Tables of the public translator and 15 References in the public translator in
cfgUpdate.
In some versions such as some B3.xxx, the value of those fields were set to 1000000 which was too
high. It is better to reduce this value (typically 1000).

5.6. Supervisions
To count the local supervisors is not easy. multitool tool is not a help for this operation since it edits
only the memory.
Errors of type :
ERROR 2675 : EXCEPTION 7, function inismcdu, PC = 0x000185f1
ERROR 4352 : INSTANCE EXCEPTION, Table SUPERV, mcdu_visor=1002 num_tab_vised=5
ERROR 4351 : DATA INCONSISTENCY SUPERV max supervised info1=2 info2=-1 info3=-1
…
will occur when the number of managed supervisions exceeds the field 19 Supervisable MCDU. This
only for not networked supervisions.
The result got with the command checkdb | grep mcdu_visor | wc –l gives the number of errors in
the table of supervisions and therefore the number of missing supervised. The information
mcdu_visor corresponds to various supervisors which causes trouble.
Increase the value of this field, with as minimum, the value previously got in order to have the correct
configuration.

5.7. Abbreviated numbers

The counting is not carried out with the number of abbreviated numbers but by taking into account
the last index in the database. The field 17 Abbreviated numbers in cfgUpdate defines this
maximum.
In case of inconsistency, an initrem incident ERROR 2656 : DATA INCONSISTENCY TYPNBAB
info3=x is displayed (incident also viewable with the command checkdb) where "x" is the
abbreviated number (index) in error. At each number overflow, there is an incident. The biggest
value of "x" will be the minimum value to be entered in cfgUpdate/field 17.
In case of inconsistency, the overflowed abbreviated numbers will not be initialized in memory.
Counting on the disk with cuser :
select numab_id from typnbab order by numab_id ; : in the result, find the highest
number.

5.8. Users
Errors of type hereafter can occur:
ERROR 4351 : DATA INCONSISTENCY, Table POSTE, station=1801 nulog=102 MAXPOSREFIC=93
ERROR 4351 : DATA INCONSISTENCY, Table POSTE, station=1802 nulog=103 MAXPOSREFIC=93

ED. 13-11-2002 9 TC0384

 OmniPCX 4400
DATABASE : CHECKING THE MAXIMUM
VALUES OF INSTALLATION DATA AND
RELATED PROBLEMS

ERROR 4351 : DATA INCONSISTENCY, Table REPERT, nulog=348 key_nbr=1 WITH_postel

ERROR 4351 : DATA INCONSISTENCY, Table REPERT, nulog=348 key_nbr=2 WITH_postel
ERROR 4352 : INSTANCE EXCEPTION, Table TABRAL, nulog=101
ERROR 2675 : EXCEPTION 7, function iniextension, PC = 0x000100b7
ERROR 4352 : INSTANCE EXCEPTION, Table TABRAL, nulog=102
ERROR 2675 : EXCEPTION 7, function iniextension, PC = 0x000100b7
etc.

The counting is carried out with the biggest logical number in the table.
In the previous case, some logical numbers of users exceed the number defined in the PARA_MAO
2.
Definition on the database of the highest logical number:
select nulog from poste order by nulog; : in the result, find the highest number.
In case of inconsistency, change the field 1 in cfgUpdate.
Note
The maximum number of users includes also the field 4 Patients (Hospital).

If the message below occurs:

ERROR 4351 : DATA INCONSISTENCY, Table TABDATA, station=1009 Invalid nulog=5
the number of data terminals in cfgUpdate is not enough. Change the field 3 Data terminals.

5.9. Business codes

In D1.311.4 and D2.304, the number of business codes was increased to 10,000. More, the new
field 36 Maximum Number Of Account Codes from cfgUpdate was created. Migrating to this version,
this field is set to 0. An initrem incident will be displayed to mean that its value is too small. As of the
dynamic patch D1.311.7.l, even with a value set to 0, initrem loads in memory 2,000 business
codes maximum. Change this value to 2,0000 at least to be in accordance with the management.

TC0384 10 ED. 13-11-2002

 OmniPCX 4400
DATABASE : CHECKING THE MAXIMUM
VALUES OF INSTALLATION DATA AND
RELATED PROBLEMS

6. LIST OF PARA_MAO FIELDS

PARA_MAO 1 Size for remanent memory
PARA_MAO 2 Number of sets in the installation (fictive or not)
PARA_MAO 3 Number of trunks
PARA_MAO 4 Number of ½ coms
PARA_MAO 5 X25 presence (Example : ABC network ; 0 = Yes; 1 = No)
PARA_MAO 6 Number of simultaneous BLF
PARA_MAO 7 Number of entries in the phone-book in steps of 2000 names
PARA_MAO 8 Number of SBC
PARA_MAO 9 Not used
PARA_MAO 10 Alcatel 4635x presence
PARA_MAO 11 Alcatel 4630 presence
PARA_MAO 12 Fax server presence (4855)
PARA_MAO 13 Number of simultaneous accesses of hotel consoles behind UA
PARA_MAO 14 Number of simultaneous accesses of ACD supervisors behind UA
PARA_MAO 15 Number of multi sites CCS accesses
PARA_MAO 16 Number of languages
PARA_MAO 17 Number of S0buses
PARA_MAO 18 Number of fictive sets
PARA_MAO 19 Number of ACT shelves
PARA_MAO 20 ACR (OmniTouch)
PARA_MAO 21 Number of "Nice Monitoring"
PARA_MAO 22 Casual conference (from 0 to 20) (from D2.304)

ED. 13-11-2002 11 TC0384

 OmniPCX 4400
DATABASE : CHECKING THE MAXIMUM
VALUES OF INSTALLATION DATA AND
RELATED PROBLEMS

7. RESULT OF SPADMIN/DISPLAY OPS LIMITS COMMAND

If PARA_MAOs are unavailable, the corresponding fields are not displayed.

(401)xa004001> spadmin

Display current counters ........................... 1

Display active file ................................ 2
Check active file coherency..........................3
Install a new file ................................. 4
Write a new file ................................... 5
Read the hard key .................................. 6
Display active and new file ........................ 7
Display OPS limits ................................. 8
Exit ............................................... 0
choice : 8

OPS limits
Remanent size (Kb) = 9778 PARA_MAO 1
Number of stations = 100 PARA_MAO 2
Number of trunks = 120 PARA_MAO 3
Number of half-contexts = 300 PARA_MAO 4
Stand-alone = 0 PARA_MAO 5
Number of BLF = 0 PARA_MAO 6
Phone-book (x 2000) = 3 PARA_MAO 7
SBC = 0 PARA_MAO 8
BLF = 0 PARA_MAO 9
4635 = 0 PARA_MAO 10
4630 = 0 PARA_MAO 11
4855 = 0 PARA_MAO 12
Hotel accesses = 4 PARA_MAO 13
ACD supervisor accesses = 0 PARA_MAO 14
Multi-site CCS accesses = 0 PARA_MAO 15
Nb of set display languages = 4 PARA_MAO 16
Nb S0 Buses = 5 PARA_MAO 17
Nb fictive clients = 100 PARA_MAO 18
Nb ACT = 8 PARA_MAO 19
Param 20 = 5 PARA_MAO 20
Number of Nice Monitoring = 5 PARA_MAO 21
Number of Casual Conferences = 10 PARA_MAO 22

Display current counters ........................... 1

Display active file ................................ 2
Check active file coherency..........................3
Install a new file ................................. 4
Write a new file ................................... 5
Read the hard key .................................. 6
Display active and new file ........................ 7
Display OPS limits ................................. 8
Exit ............................................... 0
choice :

TC0384 12 ED. 13-11-2002