Module Database Report Reference

Module Database Report Reference (aka Browsing the CMD)

CDF Home Page
CDFDB Home Page
FNAL Disclaimer

Find out: Your access privileges, what units are in the CMD, where they are at, and their history

version 1.6, John Yoh, 9/5/2000
version 1.5, Linus Wong, 8/11/2000

This reference will show you step-by-step how to get information in general as well as on specific items (modules, users access, etc.) from the CDF Module Database. Since no account or password is needed, you can do this from both the production db (misprod1) and test db (int1) -- CMD --- Just click on this--(you might want to right-click to open a second window--this way you can look both at the instructions and on the CMD window). Choose "Database report", then Reports/Misweb --misprod1 for production db (or, if you wish, int1 for test db)

Quick reference list : To look for

What your write access privileges are -- see line 1
What units (i.e., serial number) of your modules are in the db -- see line 2
What units are in (all racks, a row of racks, or a particular rack/crate) -- see line 3
What modules occupied a particular position -- see line 3 or 10
What positions has a particular module occupied -- see line 4
What is the repair history of a particular module -- see line 6

Getting started : "Reports" work fine with either Internet Explorer 4+ or Netscape 4+; note that data updates of the CMD through "Module Maintenance Forms" requires Internet Explorer 5+ or Netscape 4.5+.
- Click on "Module Database Reports"
- Click on "Reports by Using MISWEB"
- You will get the main "Reports" menu, allowing you to obtain information on a host of items.
Note that you can use the wild card % in any query--such as the model, serial number, rack, crates (crate 1, crate 2,...), etc. Note also that if you click on the "Run" button, you will get the standard table--if you wish other information, click on the "build" button, and select those fields you want to display.
Line 1 : CDF USER ACCESS
--This is only useful for the production CMD -- since the dummy account can update everything in the test CMD
- If you just click on the "run" button, you will get a list of all users, and what update access they have to any of the module types. If your account does not appear, sign up for a CMD account.
- If you wish to know who has access to a particular module type, type in the module name in the Model box (use % for a wild card, e.g., %TRACER%) and click on "run".
- If you wish to know what access you have, type in your account name into the "CDF User" box and click on "run".
- If you want an "un-duplicated" list of all available module types accessible currently by the CMD, type in "johny" as the user name and click on "run" button. Since I am the system manager, I have access to all available units. You may want to print a copy of this report, so as to have available the EXACT name of each module type that you are interested in--since some module names are abbreviations.
- If your module type is not declared, send email to johny@fnal.gov
- If you see any module type that you should be a "stakeholder" for, send email to me, johny@fnal.gov.
Line 2 : CDF MODULES
--(This line is useful to get a few module types and serial numbers for you to test using the test database)
- To find out what module types have been defined, click on the "List" button to the right of any of the "Model" fields. Note that when you type in a model, you need to type in the letters exactly, including the space between the : and the name of the module. % is a wild card, and can be used as needed (e.g., %TRACER%) Note that the module "List" is updated each evening, so, if a new module type has been added in less than one day, it may not show up in the list till the next day.
- To find out what units (i.e., serial number, etc) of a particular module is in the db, you can do a query. For example, in the CMD-production db, on the second line (CDF Modules), type in %TRACER% Click on "Run" button and you will get a list of TRACER that's in the database. Warning : There are lots of units in both DB. if you do only %, or %CAFE%, you will get thousands of lines !!!!! Note that you may have to wait a few seconds.
- If you need additional information than is not provided by the default printout, you can click on the "BUILD" button, which will allow you to select which fields to print out.
Line 3 : FILLED POSITIONS WITH HISTORY
- If you just click on "run" without any input, You will get a list of all installed modules, and their current positions. Currently, there are more than 1300 units in the db in positions.
- Typing the model (and, if desired, the serial number) gives you the current position for the units (check out the test CMD with %Tracer%).
- Typing a row of racks (e.g., 1RR18%), a particular rack, or a rack/crate combo (1RR18I, CRATE 1) gives you a list of all filled slots in those racks/crates, and which units are in it.
- In the produced report, each filled slot has a gray button in the positionId column. Clicking on it will give a history of that slot and which modules were in that slot in the past.
Often, you would like additional information not displayed in the default "Filled Position" report. You should click on "build" instead of "run"-- you can then select which additional information to be displayed--such as name of "Last Updater", "last Update date", etc.
However, if you add additional items, the width of the report would be too long for a printout. You should then export the report to a spreadsheet (selectable in the "build" form), and then print it out on your NT with EXCEL. This way, you could use magnification/reduction to fit all the items in one page; this also allow you to reduce the number of printout pages if you want to print out lots of entries (such as the entire 1300+ units located in slots).
You can also make cuts on about a dozen quantities (e.g., "Last Activity date" after Apr-1-2001, serial number > 1001, ,...)
Line 4 : POSITION HISTORY OF ASSETS
--Use this form instead of line 3 (Filled positions with History) is you are interested in finding out the position history of a particular module unit.
Line 5 : MODULE ALTERATIONS
--(?? Find out the alteration types that has been defined for particular module types)
Line 6 : MODULE REPAIR HISTORY
--Given a module type and serial number, it returns the repair history of that module unit.
Line 7 : MODULES IN REPAIR
--Given a specifie module type (and serial number, if desired), it returns a list of all modules currently in repair.
Line 8 : MODULE HISTORY
--Given a module type (and serial number, if desired), it returns a history of all (or specific one) modules of that type. Note that history does not include position, only locations (e.g., B0). This report might be slow, especially if it includes module types with many units in the db.
Line 9 : Module Positions with Asset History and
Line 10 : All positions with History
-- Not recommended, since it will display all slots, including those without any modules in them.
Line 9 is useful if you want to view a module's asset history. Given a module type, or a position, after running the report, you can view th the asset history by clicking on the drill down button under the AssetId field.
The only time you should use line 10 is to find out the history of a slot which currently has no modules in it. Do so by first running the report based on the rack, crate, and/or slot. on the results pages, click the drill down button under the positionId field to view the history of that position.
Some comments
1. If more than 240 lines are outputed, only the first 240 lines are displayed (this default can be changed--by using the "build" button--there is a box where you can change the 240 to any number you want.
2. Be careful of querying on a module type that has a large number of units-- do not do "%CAFE%" or "%", since there are 5000 CAFE cards in the db !!!! Specify a particular unit if possible.

Contact johny@fnal.gov with questions, suggestions, or problems.