WHO HAS THE ACCESS TO ENTER UNITS AND UPDATE INFO
A table giving access privileges for various account/password is
checked whenever you desire to make an update. Thus, if you need to be able to
update a particular unit, convince the stakeholder, and have him/her send
email message to the CMD people to add your name/access level to the table.
To see what privileges you have, go to the web reports/misweb, and
click "run" on the line with "CDF USER ACCESS". You will get a list of all
user accounts, and what privileges each accounts have. Alternately, if you
are only interested in your own privileges, type in you own account name
and click on "run". Note that you have to apply for an account in cdfdb--
follow the links in the cmd web page --"stakeholders: getting an account ...".
THE DATABASE SEEMS TO BE HUNG, WHAT DO I DO
When using the update forms, it is easy to hang the system, if you click on
some unexpected places. Here's some of the most commone problems, usually
in web access :
- Often the response on the web is real slow; you may have to wait.
- After selecting one of the 6 update procedures, you should get a prompt
asking for your account, password. If you are waiting for the account/password
prompt to show up and nothing happens, click on the browser "refresh" or
"reload". Leave the database box blank and log in.
- When the work window shows up, you always start in the "query" mode--
just enter the rack name of interest (or select from the ? button--though
it's real slow); then press "Enter" or click on "query" to get details of
the rack, with crate 1 slots displayed. If you wish to look into some
other crate, put the cursor on the crate of interest, and click on the mouse
button. The crate/slot display should display the crate you asked for.
- To insert a spare module into a slot, just type in the PREP number, or
the module-type/serial-number.
- To move a module, click on the "M" button next to the module you want
to move.
- If you get errors, click on "clear" and try again.
- remember to click on "commit" in order to process your request--the
bottom of the top window should show "recorded updated" or some other
"success" message. This must be done before moving to another crate or
rack for more moves.
- with some practice, you will be able to do all changes without much
problems. the Oracle database is quite exacting, so you need to learn to
avoid the "gotchas".
I'M GETTING ERROR MESSAGES--WHAT DO THEY MEAN??
Of course, this depends on the error messages. Here's some possible answer to
some common error messages I've seen :
- "This asset exist but is not assigned to CDF" --This particular module
you try to move, fix, etc. exist in the PREP database, but is not assign
to the cdfdb. Check that you have typed in the correct serial or property
number. Also, go to the cdfdb report to query on that particular module,
to make sure that cdfdb has access to it---NOTE : The production cdfdb
(miscomp) and test cdfdb (misint) may not have the exact same modules !!!!
If you intend to move a bunch of the same type of modules, it might make
sense to print out a list all available modules of this type (if not too
many) to make sure.
- "There is no record of this module"--module has not been put into the
PREP database
- "This module is in rack xxx, crate yyy, slot zzz)--you need to go to
that rack/crate/slot and do a move using the "m" button--make sure that
the unit really belongs in the slot you are moving it to (is there a typo
in the serial or PREP number ??).
- In general, if you get an error, click on "clear" and try again. Another
possibility is to click on "query" before doing anything.
I NEED TO MAKE A BUNCH OF UPDATES, AND THE WEB IS REAL SLOW
For speedier multiple-updates, you can get an account on fncdug, where
the PREP database resides, and "use telnet to direct connect to fncdug".
Contact Shirley Jones (jones@fnal.gov) for more information.
HOW DO I GET A DENSER PRINTOUT OF A REPORT
For any large printout of lots of info (such as the "Filled positions"
for all the racks), you could output the report as a spreadsheet, which you
can transfer to your PC and printout using reduced Zoom. To do this, simply
click on "Build" instead of "Run", and scroll down and select "Output" as
"Spreadsheet".