104 GENDB - Generate Data Base with MML Command File


Restrictions	Functions of the AMO	Error Messages and Advisories
Interrelationships	Parameter Description

The AMO GENDB is used to generate the system databases (DBs) in batch operation. Before first-time generation, a database must be initialised for configuration data (CFIGDA) and customer data (CUSTDA). Databases which have been thus initialized can be loaded with the aid of the AMO LDB, if present on the hard disk.
AMO GENDB can only be started, if the APS numbers entered into the directory files are identical to those in the MML command file. The numbers in the MML command file can be changed on the hard disk with the aid of the AMO ASPIK. The current APS numbers in the system can be interrogated via the DISPLAY action of the AMO VEGAS, parameter FLIST=LONG.
If the AMO-TEXT-APS-NO in the MML command file are not the same as those in the system, the GENDB will close with an error message, the status ’FREE’ will remain in the VEGAS file. If the RES-CODE-APS-NO or the AMO-CODE-APS-NO are different the status will be set to ’ABORTED’.
If an interrupted generation is to be continued via the CONT parameter of the AMO GENDB, the partially generated database must correspond to the MML command file. The AMO checks that the system number entered in the database is identical to that in the MML command file. Continue GENDB is only possible, if the status in the VEGAS file is set to ’INTRUPTD’ or ’SYBRO’(system crash).

During generation, a sorted file of MML commands is read sequentially, and the DBs generated with the aid of the respective AMOs. The sequence in which the AMOs are called up during generation can be seen in the generating sequence control file. When creating the MML command file with DAGEN, the AMOs are automatically sorted in the correct sequence. The generation sequence is logged in an error and execution file.
AMO GENDB permits parallel generating runs for the DBs in the SWU and ADS. For parallel generation, the AMO must be started separately for each server (single value for parameter UNIT). Otherwise, the generating runs will be executed sequentially.

Generating (or regenerating) runs on the system are coordinated by the AMO VEGAS. The system access status for each HW module is entered in the VEGAS file (control file). The AMO GENDB can only be started if all the modules to be generated are entered in the file as ’FREE’, or have been reserved for the AMO GENDB by the user (status=’RESERVED’).
With the DELETE action of the AMO VEGAS, the operator can set all module operating state entries in the VEGAS file to ’FREE’, thus enabling a successful start of the AMO GENDB. After a correct run of GENDB the status is set to ’FINISHED’. The operator can interrogate the state of the generating (or regenerating) run on the system by calling up the DISPLAY action of the AMO VEGAS.

If DBHOLD=N (no) was entered, then the DBs are loaded from the hard disk on completion of the generating run. When the system is restarted after a generating run, the operating state entries for all (re)generated modules in the VEGAS file are automatically set to ’FREE’.

GENDB can be executed if no system number is entered. If SYSNO is already added (e.g. from a previous GENDB), it can be cleared with the following command:

ADD-ANSU:TYPE=SYSNO,SYSNO="NO-ENTRY-IN-DBASE";

NOTE: If SWU is cleared with the AMO DBC parameter RESSWUDB, also CODEW is lost and must be re-added via license activation or a previously saved REG-CODEW.

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.