SLAC PEP-II
BABAR
SLAC<->RAL
Babar logo
HEPIC E,S & H Databases PDG HEP preprints
Organization Detector Computing Physics Documentation
Personnel Glossary Sitemap Search Hypernews
Unwrap page!
Comp. Search
Who's who?
Meetings
FAQ Homepage
Archive
Environment
Administration
New User Info.
Web Info/Tools
Monitoring
Training
Tools & Utils
Programming
C++ Standard
SRT, AFS, CVS
QA and QC
Remedy
Histogramming
Operations
PromptReco
Simulation Production
Online SW
Dataflow
Detector Control
Evt Processing
Run Control
Calibration
Databases
Offline
Workbook
Coding Standards
Simulation
Reconstruction
Prompt Reco.
BaBar Grid
Data Distribution
Beta & BetaTools
Kanga & Root
Analysis Tools
RooFit Toolkit
Data Management
Data Quality
Event display
Event Browser
Code releases
Databases
Check this page for HTML 4.01 Transitional compliance with the
W3C Validator
(More checks...)

Common Options

For a recent version, use release 14.4.0 or later, or else
% newrel -t 14.3.1d 14.3.1d-test
% cd 14.3.1d-test
% addpkg BbkUserTools V00-00-03
% addpkg BbkTools V00-00-09
% gmake BbkUserTools.bin

General Options

no options  site  user  dbname  localdsprefix  debug  verbose 

Advanced Connection Options

dbtype  dbserver  dbdriver  dbpass 

Note you can use this options to connect to a database or you can create a 'site' with these connection options. Here BbkConnect to find out more.

General Options

site

The connection details to official databases are taken care of by the connection module BbkConnect. Each TierA (slac,ral,in2p3,gridka,padova) should garantee reading access to its bookkeeping database. To access a site simply:

    % Script --site ral

Smaller sites might or might not give access to outside world.

user

For each accessible site there is a default user "anyuser" that can read from the default database. Other user names in general are tied to the database they are accessing. For example bbkr14 user can access bbkr14 database, bfactory can access bbrora subset of tables. In any case if you need to change the user and the access to the default database:

    % Script --user bfactory

dbname

It might happen that at one site a user (as anyuser) has access to more than one database and you want to access another database and not the default one. To access for example bbrora instead of bbkr14:

    % Script --dbname bbrora

localdsprefix

This options allows users to create personal datasets of official collections in special tables so that they don't interfere with the officially created dataset.

NOTE: This option cannot be used unless the 'local' tables have been created. You can do that if you have a personal copy of the database on your machine or you can ask to the site administrator if you can do that for you. The schema for the table is in BbkTools/bbklocalds.mysql It is hihly suggested to change the prefix local with something more personalised.

    % Script --localdsprefix username

will access and join with the official tables username_dataset, username_dstodse, username_alias instead of bbk_dataset, bbk_dstodse, bbk_alias.

debug

    % Script

verbose

    % Script

Advanced Connection Options

dbtype

With dbtype we go to the specifications needed for databases not known by the connection module BbkConnect. For example you want to access a mysql database at Manchester:

    % Script --dbtype mysql

Possible values: mysql and Oracle.

dbserver

As for dbtype this is needed when the connection module BbkConnect doesn't know anything about the database you want to access. For example you want to access a server in Bristol:

    % Script --dbserver server.phy.bris.ac.uk

dbdriver

This is the connection string or in DBI terms the data source for a specific database which again is not known by the connection module BbkConnect. This string is different for mysql and for Oracle, consult the drivers man pages to know more: man DBD::mysql or DBD::Oracle to know more. Just as an example for mysql on your laptop:

    % Script --dbdriver "driver=dbi:mysql:bbrora:localhost"

dbpass

If you specify a user with --user option which is not known by connection module you surely have to specify also the password for that user.

    % Script --dbpass mypassword