Given a file containing run/event number pairs, users can
create D0DAD files referencing the events. This section describes the steps
needed to create the D0DAD file. The two steps are:
The D0DAD command on the second line takes three filenames as arguments. The
first file is a file containing run/event pairs, one pair per line, in a format
readable by a fortran ``*'' format descriptor. The second file is the name of
the new D0DAD output file. The third file is the name of a master catalog
containing the run/event information for the desired input run/event pairs.
For run 1a data the file catalog is
D0$D0DAD$CATALOGS:RUN1A_MDS.EVTCAT, and for run 1b
data the catalog is
D0$D0DAD$CATALOGS:RUN1B_MDS.EVTCAT.
These catalogs reference only microDST's. There are currently no plans to
build catalogs for DST's or STA's.
If the input text file name is any of ``-'', ``stdin'' or ``SYS$INPUT'',
the run/event
pairs will be read from the standard input until an end-of-file
is reached.
Other catalogs may be created. For example, the catalog TOPMC.EVTCAT contains
the
standard decay mixture of 
events generated at masses of 120,
140, 160 and 180 GeV. All catalogs will be in the D0$D0DAD$CATALOGS
directory. D0DAD files are transportable
across platforms, so a file written on (e.g.) a Vax can be copied via rcp
to an SGI and used as is. The reverse also holds.