Creates executable scripts and stanza files that are used during the installation process to modify the odm database.
mkodmupdt [ -p PreviousStanzaFile ] -c CurrentStanzaFile -o Option -t ObjectClassDB [ -d OutputFilesDir ] [ -l LastReleaseLink ] [ -u | -i ]
The mkodmupdt command creates executable scripts and stanza files that modify the odm database during the installation process.
The mkodmupdt command is provided with an object class definition file as input. For each object class stanza in the input file, mkodmupdt queries its own database file (specified with the -t flag) and generates the appropriate option.odmadd, option.unodmadd, and option.odmdel scripts. These files are archived into liblpp.a for an install or update package and run by the installp command during the installation process.
The names of the output files are generated based on the option parameter specified with the -o flag and the file name specified with the -c flag. If the option name is bos.diag.rte and the stanza file name is DSMOpt.add, then the output files are:
Note: If the -p flag is not set, either install or update type scripts can be generated. If the -p flag is set, then either the -i flag or the -u flag must be specified. If the -p flag is not set, then the -i flag (install type script) is assumed.
Warnings contain the word Warning followed by a message printed to stderr. The mkodmupdt command continues normally after the warnings are issued. The return code is not affected.
Fatal errors contain the word usage followed by an error message printed to stderr. The mkodmupdt command exits with a non-zero return code if an error is detected.
| object description (.add) files | This file contains one or more object class definitions in stanza
format. The format of a stanza is:
object_class_name: key = value ... attribute = value ... |
| object class database file | This is the internal database file the mkodmupdt command uses
to verify the object classes from the stanza files and generate the
appropriate odm commands for the output odm scripts. This database file
contains one entry for each object class, where the entries are described as
follows:
object class:List of keys:list of fields including keys The list of keys is separated by %. The keys are the set of fields whose combination of values can identify a unique stanza. The list of fields is comma separated.
Example: GAI:Adapter_Id%Module_Key%Module_Path:Adapter_Id,Module_Key,Module_Path |
| option*.odmadd file | This file contains complete stanzas that are used as input to the odmadd command. The odmadd command adds information to the odm database.This file contains complete stanzas that are used as input to the odmadd command. The odmadd command adds information to the odm database. |
| option*.odmdel file | This file is an executable script that contains odmget commands and odmdelete commands for each new and updated stanza in the current stanza file. It also contains one odmget and odmdelete command for each stanza that is to be deleted from the previous stanza file, if applicable. This script is executed during an install to delete previous odm information before the odmadd is executed. |
| option*.unodmadd file | This file is an executable script that contains odmdelete commands for every new stanza in the *.odmadd file. The unodmadd script is executed to reject an update to the odm database. |
The installp command, odmadd command, odmdelete command, odmget command.