<!> /!\ All the procedures below are defined for the pacs account on the host hpacsegse unless stated different. <!> /!\


TableOfContents(2)

Standard Procedures

A new MIB (combination) is available and ready to be used

The MIB to be ingested can be specified in two different ways, either by the CVS MibTags or by the database MibLabels.

ccm -loadmib PACS_MIB_TAG EGSE_MIB_TAG CDMSSIM_MIB_TAG

or

ccm -loadmib=MIB_LABEL

The MIB loading does not affect any ongoing operation. It can be executed at any time.

To get listings of MibLabels of already loaded MIBs or available CVS MibTags follow this [#MibListing link].

A new (modifiable) instrumentModel shall be created using new MIB definition

The MIB must be already ingested into the database using the above procedure.

Before going to more detail here is the way to go on in almost all cases. Usually the last used CUS definitions will be copied to the next (editable) instrumentModel. In that case use the

ccm -listconfig=active

command to get the current missionConfigurationLabel. In the command

ccm -createmodel -usemib=MIB_LABEL -usecus=cvs=CvsTagName -cvscomment=comment

replace MIB_LABEL with the new Miblabel and CvsTagName with the missionConfigurationLabel returned by the previous command.

Gratulation, you created a new (modifiable) instrumentModel.

In case you want to select a different source for your CUS definitions for the new (modifiable) instrumentModel two command options are available.

This is the way to select CUS definitions belonging to a specific missionConfiguration.

A dialog window will pop-up to enter a CVS comment if none was entered at the command line.

Each of these options will create an instrumentModel, load it with the specified MIB, load the requested CUS definitions (also updating the CVS repository) and create the first missionConfiguration for this new instrumentModel. Finally the property file will be updated with the new instrumentModel and missionConfiguration and the CcsHandler will be restarted.

<!> Note: The CUS editor "cusgui" must be restarted to view (and edit) the new modifiable instrumentModel.

Publish CUS modifications for the current instrumentModel

Whenever you want to make the CUS modification edited with the CUS editor available for commanding you must commit your changes to the database to update the instrumentModel and you must use the following command to create a new missionConfiguration and make it available.

ccm -updatecus -cvscomment=comment

A dialog window will pop-up to enter a CVS comment if none was entered at the command line.

Monitoring CcsHandler and TmIngestion

To monitor and control both TmIngestion and CcsHandler convinience procedures exist.

CcsHandler start       # starting CcsHandler, it will run in the background
CcsHandler stop        # stopping CcsHandler
CcsHandler status      # showing the output of "ps -lf" of CcsHandler (if it runs)
CcsHandler log         # showing the tail of the CcsHandler log file and continue to monitor it

TmIngestion start       # starting TmIngestion, it will run in the background
TmIngestion stop        # stopping TmIngestion
TmIngestion status      # showing the output of "ps -lf" of TmIngestion (if it runs)
TmIngestion log         # showing the tail of the TmIngestion log file and continue to monitor it

List of MIBs

Anchor(MibListing)

The command

ccm -listmib=database

shows all MIBs already loaded into the database.

The command

ccm -listmibs=cvs
}}
shows all MIB tag names available in the Leuven CVS repository.

The command
{{{
ccm -listmib

will give you both listings.

List of (editable) instrumentModels

Anchor(instModelListing)

The command

ccm -listmodel=active

shows the active (editable) instrumentModel as set by a property. Starting a CUS editor will work with this instrumentModel.

The command

ccm -listmodel=database

shows all available (editable) instrumentModels known by the database.

The command

ccm -listmodel

will give you both listings.

List of missionConfigurations (=CVS tag names)

Anchor(missionConfListing)

The command

ccm -listconfig=active

shows the active missionConfiguration as set by a property. The running CCsHandler is working with this missionConfiguration.

The command

ccm -listconfig=database

shows all available (editable) missionConfigurations known by the database.

The command

ccm -listconfig

will give you both listings.

Recovery Procedures

Initial loading of the empty database

Make sure the database is empty by issuing following commands using the <!> dbsa account

echo yes | db_admin -c pacs_fm_ist_fn1@hpacsegse
echo yes | db_admin -u pacs_fm_ist_fn1@hpacsegse
db_admin -i pacs_fm_ist_fn1@hpacsegse

Switch again to the <!> pacs account.

Load the MIB again.

ccm -loadmib PACS_MIB_N_8_16 EGSE_MIB_0_20 CDMSSIM_MIB_0_4

Initialize both the database and the CVS repository with an initial set of CUS definitions

initCVSrepositoryAndDB ~/procedures/FM_ILT_MC_V4-3_PR8-15_E0-20_C0-4.tar.gz 
> 1
> Initial loading of the CUS definitions using the missionConfiguration FM_ILT_MC_V4-3_PR8-15_E0-20_C0-4.tar.gz of the pacs_fm_ilt_3@pacs5 database

cd /home/pacs/CCStemplates mkdir templates cd templates source ../CUS_Shell_Scripts_FM_IST_20070803.script |& tee ../templateGeneration.log cd .. # checks grep Exception templateGeneration.log ls templates | wc -l ; wc -l CUS_Shell_Scripts_FM_IST_20070803.script find templates/ -size 0 find templates/ -size 0 | xargs rm -v