Beginner's Info & Module Status

CMD -- CDF Module Database -- aka cdfdb

version 3.12, John Yoh, 4/24/06

Latest Update --11/10/05:
(****) To write access the forms, you need to be able to load J-initiator at least once--which require admin priveledges in most cases. Many CDF PC users no longer has this priveledge, and thus would require the IT guy (Rich Krull for CDF trailers) to load it for once (and every time that J-initiator is updated)--before the user can access the forms
(0A) Access off the Fermilab site is usually disabled (unless you have VPN arrangement--contact Shirley Jones at jones@fnal.gov if you need to access off site)
(0B) You may need to load a newer version of Jinitiator to access the forms
https://fncduh1.fnal.gov/lists/JINIT.EXE ,
(1) You can now view the comparison of what is stored in the CMD database, compared with the HDWDB of Bill Badgett, which actually reads the PROMs from the modules themselves-- (Thanks to Nelly Stanfield, Julie Trumbo, Bill Badgett, Donatella Torretta)
.... ReportA -- A complete list of 1700+ A slots items
.... ReportA_Terse (mismatches) -- for a list of A slots items that CMD disagrees with the HDWDB, and thus are probably not yet updated correctly--note--only serial # is checked, which should be okay 99.99% of the time, since it is extremely unlikely that a TDC of the same serial # is in a slot where one expects, say, a ADMEM.
--Note that they may be units in CMD that are actually in empty slots--this would not be catched by this comparison, which starts from the HDWDB.
... ReportB -- Comparison of B slot items (prelim--not yet fully implemented)
ReportC--CAFE -- Comparison of 5000+ CAFE daughterboard serial #'s --WARNING : 200 pages (landscape mode) !!!
ReportC_terse--Mismatch CAFE's -showing only mismatches where the two db disagrees

(2) If you are using LINUX, and wish to use CMD in write-access mode
--use KDE (not GNOME)--you must also upgrade to netscape 6.2.3 or above (7 is fine)
--you must also click on the "Always trust Oracle" box when that prompt comes up
(also, you may need to try several times --closing the netscape windows- before succeeding).

To access the DB,--
For "Module maintenance forms", click on CMD-
to actually change the information on the DB, such as the position of a module or initaite a repair job-- you must log in to a valid account in either
...account cdf_test , password "run2", and database "int1" for testing
...Your account and password, and database "misprod1" for Production--you will be allowed to access only modules authorized to your account.

For --"Database report" Click on CMD-production -->Misweb-reports (select integration/int1$ for testing, or production/misprod1 for production database (do not use "mistest"--it's for internal testing)--to find out about what modules are in the DB and where they are located (readonly-no account, password needed)
(See sections below for tutorial on using the CMD)

What is the CDF Module Database? CDF Module Database is the Fermilab PREP Oracle Database suitably modified for CDF's needs, adding position, history, and version tracking abilities. It is intended to satisfy ALL of CDF's module-tracking needs, obsoleting what we did in run 1 (sticky paper, notebooks, private EXCEL spreadsheets, ...). Thus, ALL PRODUCTION electronic modules arriving at Fermilab NEEDS TO BE put into this database. Note that this is the same database as the PREP database, but with added features to track module positions, and restricted only to CDF-owned modules.
Some of the features of the CMD are :

Web accessible from anywhere (even your office off or on site--using Netscape 4.5+ or IE 5.50+ on Windows NT)--though you should use the "direct Oracle form through fncdug" access if you wish quicker response for bulk entries--contact johny@fnal.gov.
Web-access Reports (i.e., formatted display of information from the database--whether simple "canned" reports, or specialized user-defined reports) are avaialble to everyone without the need of accounts or passwords.
Changes in information (position, version, history,..) can be made by "stakeholders" and other authorized persons with password protection for security (see stakeholders to get an authorized account for particular modules).
Recent Changes
Use the "Module Maintenance Forms" link to access the 6 forms and move between different forms without having to log back in.

Pos-mod form should be more intuitive now--please comment--the only slightly tricky part is putting the cursor in the Rack Name field and then clicking on Query to clear the form and type in a new rack to query.

To submit an ESR (Equipment Service Request) for a broken module that you have just removed from a slot in a crate, using the Pos-mod form, press the "M" button; in the "Move" window, you can click on the "Service Request" button to initiate an ESR. Note that PREP-maintained modules should be brought to PREP and have them input an ESR.
Note to Linux users
Linux users using GNOME should upgrade to the latest version of GNOME to use the forms correctly (Reports are okay with the old GNOME). For more info on the problem, click here.

Using the CMD Database : or CMD-production and Testing

You can choose "Module Database Report" to find out about modules, history, positions, etc--no password needed, or
You can choose "Module Maintenance forms" to actually update some info on your modules
--Type in the database box "misprod1" for production--you will need a valid account that will have access to only your modules
or "int1" for testing --use cdf_test with password run2 for testing (test db has been reloaded 8/24/01 and reflect the status then

FAQ -- Frequently Asked Questions -- Check here first if you encounter problems.
Module Database Reports Reference (aka Browsing the CMD) -- Use this as a quick reference to each of the module reports found under (CMD-test/CMD-production-->Module Database Reports-->Reports by Using MISWEB). No account/password is needed for this read access. The reports are useful for finding out:

what your access privileges are, and who can access what modules.
what module types and units are in the production or test CMD,
history of a particular module unit
which rack/crate contains what units

Module Maintenance Forms Reference -- Use this as a reference on how to use each of the maintenance forms (used for data modification).
Test-Drive the CMD (aka Tutorials) -- To enter the test Database, click on CMD and select "Module Maintenance Forms". To log in, use the dummy account: cdf_test, password: run2, and database : int1 (if there is no account/password prompt within 20 seconds, click on refresh or reload). You can now access one of the 6 forms using the drop-down menu or from the CDFDB home page. Note that you must use Netscape 4.5+ on NT (on Linux, use KDE or the most recent version of GNOME, not the old version of GNOME in the current Fermilab official release, 6.1.1). See the reference for instructions on using the maintenance forms--or follow the tutorials below.
In the following list, we provide step-by-step instructions for a few of the most useful things you can do--Please use CMD --int1 database for practicing the exercises:

Preparation--get a list of modules that are in the test CMD-- Browse the CMD --write down the module type and serial number of units that you will use below. Bring up the "Module Maintenance Forms" if you haven't done so already.
Exercise 1 : Position Modification--Changing positions of modules.
Exercise 2 : Module History--Getting history information (position, repair/checkout, etc.) and entering a history record.
Exercise 3 : Equipment Service Request--Initiate a repair request for modules.
Exercise 4 : Job--Complete a repair job for some modules.
Exercise 5 : Alteration--Defining an alteration type and recording alteration on some modules
NEW !! Exercise 6 : Module repair summmary The Repair history of all units of a particular module type
NEW !! Exercise 7 : CAFE cards position changes Tutorial for putting in (or replacing) a CAFE daughterboard into a motherboard.

Make REAL updates to the production database -- (initiate a repair request, moving a module from spare to a slot, etc...)

New users and Stakeholders : setup info -- Getting an account on the production CMD, putting your module type into the production CMD, and procedure for inserting units--Also, for stakeholders to give other people access priveledges
Using Netscape 4.5+ or IE 5+, enter the production database--click on CMD-production above--and select "Module Maintenance Forms". You will have to put in your account and password, database : miscomp (if there is no account/password prompt within 20 seconds, click on refresh or reload). Now choose one of the 6 forms from the drop down menu -- Make your updates, remembering to click on "commit" after each update; once you exit from one of the forms, you can select another form without having to log in again.

Appendix A : Current status of CMD --11/4/03 update
incomplete version 0.6, John Yoh, 10/23/03 --updated 11/4/03
Preamble : We have been requested to give a snapshot of the current situation in monitoring the status of the CDF electronics with CMD (CDF Module Database), along with the comparison with the Badgett online HDWDB, which actually read the proms from the electronics that's online.
Two DB's are of interest :
CMD (or CDF Module DB) --PREP DB upgrades to provide positioning (i.e. rack, crate, slot (A and B), and daughterboard slots), history, alteration, in addition to the PREP DB (miscomp) original functions of repair records and ownership histories. Information must be inputed manually via web-based Oracle forms. Both online and spare units are in this DB.
CDF HDWDB (Badgett's DB)--which reads the actually PROMs from the online DAQ --only A slot and CAFE daughterboards are including in this DB. No B slot items, nor the SMD daughterboards are included.
Note that there could be modules that are in neither of the 2 db-- and thus will not be part of this report
Modules can be in either of the following catagories (some of the numbers below are slightly outdated--11/13/03)

---CMD has 11964 modules defines of 156 module types (including varients) --however,
---ONLY 3243 entries are ONLINE IN POSITION (not including spares) plus about 4800 CAFE Cards ONLINE. So, almost 4000 items are either spares, or not being put in the appropriate position as yet--not to mention those modules that have not yet been put into CMD (Note that All modules that have gone through PREP and assigned to CDF are automatically (daily) added to this total).
---A slot items in HDWDB/CMD --1864 such items are in this catagory--a daily report COMPA compares the serial number in the PROM's (HDWDB) with the serial number in the CMD db, and give in addition a terse report listing the mismatches. Currently, there are about 30 mismatches-- we (JKY, Badgett, James, etc) have updated most of the items that that were changed during the shutdown that was just over
---A slot items NOT in HDWDB --about 636 modules Pat Liston has put in the SMD(492)/SMC(72)/TERM(72) modules in the 48 wedge crates and 24 plug crates. These are not monitoried by the HDWDB--so, it's possible that some of the informaiton could be wrong--only the Argone group can verify these.
---Crates (214) , Power Supplies (132), Backplanes (113) --are online in position in the CMD DB, again unverified. Pat (and Roberto previously) had been quite diligent in updating these until the beginning of this shutdown--so perhaps a few items may be out of synch.
---B slot items --in CMD DB--NOT verified--and some info likely not correct
46 SMC-Aux
57 XTC
47 TOMAIN
85 VTM--15 REM, 15 MVME 712M
96 L1AUX
9 RFAN
2 DEM -likely way undercounted
Total B slot items in CMD --371
---There may be some slight overcounting--since 1864 + 636 + 214/132/113 + 371 = 3330, which exceed the 3243 CMD entries
COMPC---There are also about (5000) CAFE daughterboards --which are both in CMD and CDF HDWDB --verifieable by HDWDB in report COMPC (which, unfortunately, is not currently working)--with about 50 current mismatches (1/2 of which appears to be readout errors)
There are hundreds of spares in CMD DB--see appendix B below for an example
We do not have a good ideas of CDF electronics modules that are not in either CMD nor in HDWDB

Appendix B --Example of all units of a particular module type--ADMEM
Here's that CMD says about the 394 ADMEM's in the DB

310 are "ONLINE", almost all in CDF-Assembly Hall or Collision Hall-- though a few are listed as located in WH-14 or WH-9 ???
36 are listed as "OFF-SITE VENDOR", including serial # 1-19 (do those actually exist ??)
30 are working spares
7 are in repair
1 each in TEST and RETIRED
9 have blank catagory-- 8 in CDF, 1 in WH14
My guess is that most of the items not ONLINE may be incorrect in terms of their catatory--unless Tesarek/Mattson/Tiwari have been diligent.

Action items : to be worked on, with [person responsible]

Keep COMPA updated [John]-John will pester the appropriate stakeholders to update any mismatches in COMPA--starting after the collision hall is closed on Nov 7.
Keep COMPC updated [Tesarek, Mattson, Tiwari]--ADMEM, CAFE
Others [???] who will verify the B slot items ?? SMC/D/etc. ??
Spares ??
Who will identify other modules that are not yet in CMD ??
One option is for me to provide a summary for each module type group (e.g.,--all backplanes, all tracers, all MVME's) giving
the total number in the CMD, and
online, spares, broken, etc.
so we can identify missing items, etc.