---------
<!> /!\
~+
''' All the procedures below are defined for the ''oper'' account on the host ''pacs5'''''.
+~
<!> /!\
---------
<<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.


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

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

Depending from the source for the initial CUS definitions two command options
are available.

 * Using an existing version from the CUS CVS repository specified by a CVS tag name which is formed like a MissionConfigurationLabel.
 {{{
 ccm -createmodel -usemib=MIB_LABEL -usecus=cvs=CvsTagName -cvscomment=comment
 }}}

 * Using the current CUS definitions from an existing (modifiable) instrumentModel in the database specified by an InstrumentModelLabel name.
 {{{
 ccm -createmodel -usemib=MIB_LABEL -usecus=im=InstrumentModelLabel -cvscomment=comment
 }}}

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 test-control server 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 TestControl and TmIngestion ==

To monitor and control both Tm``Ingestion and Test``Control convinience procedures exist.

{{{
TestControl start       # starting TestControl, it will run in the background
TestControl stop        # stopping TestControl
TestControl status      # showing the output of "ps -lf" of TestControl (if it runs)
TestControl log         # showing the tail of the TestControl 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
}}}


= Recovery Procedures =

== Reloading a MIB for an already existing instrumentModel ==

== Ingesting a MIB version which is already in the database ==