= Loading/Updating the MIB/CUS database =
----
Procedure to update the PACS EQM IMT database with
* the initial MIB
* the initial CUS definitions
* a MIB update
* update of CUS definitions (observation, building block, procedure)
----
Author: Erich Wiezorrek<
>
Version: 1.0<
>
Date: September 21, 2205<
>
----
== General: ==
For the MIB updates make sure the following property is set as specified:
{{{
var.mib.raw = ${user.home}/mib
}}}
== Loading the initial MIB definitions (PACS V7.18) on an empty database: ==
Go to the directory where to place the input MIB files. Create the directory
if it doesn't exist (BUT is shall exist on our operational server).
{{{
cd ~/mib/raw
}}}
Unzip the empty_mib_files.zip archive to make sure all necessary input files
for the MIBingestion exists.<
>
Unzip the PACS_MIB_7_18.zip archive. When asked to overwrite files select the
option to overwrite all files.<
>
On the operational server those archives are in the parent directory.
{{{
unzip ../empty_mib_files.zip
unzip ../PACS_MIB_7_18.zip
}}}
Go to the parent directory and run MIBpreparation and MIBingestion.
{{{
cd ..
preparemib ~/mib/raw ~/mib
ingestmib | & tee test.log
}}}
Congratulation, it's done.
== Loading the initial CUS definitions: ==
Go to the directory where to place CUS files. Create the directory
if it doesn't exist (BUT is shall exist on our operational server).
{{{
cd ~/cus
}}}
Unzip the cus-definitions.zip archive which holds all initial CUS definitions
including the CUS tables..
{{{
unzip cus-definitions.zip
}}}
Load the TC definitions from the currently loaded MIB
{{{
cd ~/cus
cus -loadmib 1 <>
Unzip the new PACS MIB archive. When asked to overwrite files select the
option to overwrite all files.<
>
On the operational server the empty_mib_files.zip archive is in the
parent directory.
{{{
unzip ../empty_mib_files.zip
unzip yourPath/PACS_MIB_x_y.zip
}}}
Go to the parent directory and run MIBpreparation and MIBingestion.
{{{
cd ..
preparemib ~/mib/raw ~/mib
ingestmib | & tee test-PACS-MIB-x-y.log
}}}
If the MIB contains new TC definitions to be used by CUS those definitions
must be loaded by CUS.<
>
The problem is to know the new MIB version number to be used during loading.
The "cus -listmibs" shall list MIB versions which have not been loaded yet.
If there is only a line printed "New mibs available" but no numbers this means
there are NO new MIBs.
In the statements below replace TBW with the MIB version number to be used
listed with the "cus -listmibs" command.
{{{
cd ~/cus
cus -listmibs
cus -loadmib TBW <>
Create the directory a patch directory and step into this directory.<
>
'''Don't''' use "patch1" but use a more verbose name.<
>
{{{
cd ~/cus
mkdir patch1
cd patch1
}}}
Place the CUS definition text files in this directory.
{{{
cp whatever .
}}}
Loading the CUS tables if there are any updates.<
>
Replace COMMENT with a real comment, FILE is the actual filename.
The TABLE name is optional if missing the filename is used.
{{{
cus -f -m "COMMENT" -uploadcal FILE [TABLE]
}}}
Load the CUS definitions (observing modes, building blocks, procedures) if
there are any updates.<
>
Replace COMMENT with a real comment, FILE is the actual filename.
{{{
cus -f -m "COMMENT" -import FILE
}}}
Congratulation, it's done.