65.2.1 CHANGE-DBC

Change the database configuration data on the hard disk.

NOTE: As the AMO DBC obtains its information from the application table on the hard disk, it does not check for the existence of the individual subsystem files or their load status, nor does it check the available hardware.
Any check for the available hardware is not possible because the hardware connected to the support processors differs from the customer’s hardware.

Procedure Overview


Command Code	Parameter
CHANGE-DBC	{(min 1) BAPPL=<text>,DBAPPL=<text>,ASSEMBLY=<param>
	,CLASS=<param>,OPMODE=<param>,SYSTEM=<text>
	,DIMEN=<text>,RESSWUDB=<param>,LOCATION=<param>
	,ADPSLOT=<number>,SWUSLOT}=<number>,MONOSLOT=<number>
	,ADPMEM=<number>,SWUMEM=<number>,MONOMEM=<number>};

Note

A check of inconsistency between the parameters (error message F01) is done with parameter ASSEMBLY, CLASS and OPMODE.

Trying to generate the System with the same parameters several times will stop the AMO with error message F09.

If only one value for the overlay area of a processor type (Slot or Mem) is set to zero, the AMO will set the second value to zero, too. The AMO stops with the advisory message H05.
Trying to change only slots or memory for the overlay area of a processor type, if the values were set to zero before, the AMO will stop with error message F20.

Due to possible frequent changes of the values of the parameter DIMEN, there are no restrictions to them. For valid inputs see advisory message H02. The valid inputs for this parameter are taken from the DBC dimensioning table on hard disk. This table can be read with the following command:
STA-LIST:":PDS:APSU/DBCDIM0",,,M,N;

The DBC dimensioning table should not be modified.

Examples

Changing the database configuration table for a HICOM 600, EXTENDED-COMPACT-EXTENDED, DUPLEX, subsystem names from basic application DUAL128, database application DUAL128, system-identification Hicom, DB-dimensioning name DUAL128:

Input:

CHANGE-DBC:DUAL128,DUAL128,ECX,H600,DUPLEX,HICOM,DUAL128;

Output:

CHANGE-DBC:DUAL128,DUAL128,ECX,H600,DUPLEX,HICOM,DUAL128;
H500: AMO DBC STARTED
H01: IN ORDER TO LOAD THE CHANGES IN THE CONFIGURATION TABLE, INITIATE
RELOAD AND GENERATE THE SWU-DATABASE.
AMO-DBC -... DATABASE CONFIGURATION
CHANGE COMPLETED;

Changing the System-Identification:

Input:

CHANGE-DBC:SYSTEM=TEST-ANL;

Output:

CHANGE-DBC:SYSTEM=TEST-ANL;
H500: AMO DBC STARTED

AMO-DBC -... DATABASE CONFIGURATION
CHANGE COMPLETED;

Note

This call causes the data of the DB configuration table on the HD and in all available processors to be updated (synchronous state).

Special case: While in split operation, the configuration tables of the SWU which is in call-processing state, of the ADS, and of the LTG must not be overwritten. In this case the configuration table will not be distributed to the above listed processors.

There is a version counter in DB configuration table which guarantees the synchronization of all memories even if there is a breakdown of the System. This counter is increased with all important changes.

The version counter can also be incremented with the command CHANGE-DBC:RESSWUDB=Y; The input must be confirmed if changing this parameter. With any change of the version counter, however, the system must be regenerated.

Caution

The AMO modifies the version counter whenever important data of the DB configuration table is changed. This means that any generated customer data will be lost and need to be REGENERATED.

The next table shows in which cases customer data will be lost:

Table 9

parameter table

Changes of:

Regeneration necessary:

OpenScape 4000 V10, Volume 1: AMO Descriptions, Service Documentation, Issue 5, ID: P31003H31A0S107057620

© 09/2025 Mitel Networks Corporation. - All rights reserved.
Mitel and the Mitel logo are trademarks of Mitel Networks Corporation. Unify and associated marks are trademarks of Unify Software and Solutions GmbH&Co. KG. All other trademarks herein are the property of their respective owners.