RARE DST raw to zebra conversion quick manul


Subject: RARE DST raw to zebra conversion quick manul
From: Erik Katsavounidis (Erik.Katsavounidis@lngs.infn.it)
Date: Mon Jun 12 2000 - 12:33:07 EDT


Hi all,

This is a summary of the (new) RARE DST, RAW to ZEBRA conversion.
This is the kind of tapes we will have to produce for Texas A&M over
the course of the next 30-40 working days. People on shift are expected
to launch, diagnose and report to the macro-gs@budoe.bu.edu mailing list
on TWO such tapes per working day or by the end of each execution
if this extends beyond 24 hours.

The entire procedure runs on AXMAC1 under user ACQMACRO. It converts
two or one RARE DST from RAW format to ZEBRA one. It supports writing
to a 20GB DLT (placed in the MKB100: drive) from two 10GB DLTs (placed
in the MKB200: caddy).

(Notice that the old RARE MAKER area under DISK$SCRAUSA6:[RARE_MAKER]
is left as is and it is fully compatible with the new data production--
the moving to the AXMAC1 cpu was in order to maximize the use of the
facilities, use in an optimal way the 20GB unit on AXMAC1 and leave
more resources on VAXGS for the rest of the tape jobs.)

How to use:
1) Login under ACQMACRO@AXMAC1
2) Make sure DKA100: has AT LEAST 5,000,000 free blocks (do SH DEV DKA100:)
   The procedure does not have disk monitoring options-- so any disk check
   errors by the operator could be fatal. A manual disk monitor of DKA100:
   every 4 hours is required in order to make sure no unpredicted errors
   that limit the disk capability occured. In general, any disk space
   failures will be catastrophic for the tape production and if such occur
   during the tape processing, you have to re-start everything from the top.
3) Edit DKA100:[MACRODATA.RARE.RARE_MAKER.SETUP]ME.DIS and insert the
   VAXGS username where you want to have e-mail from this process to be sent.
   You do need to include a username where to receive such e-mails otherwise
   you will have troubles compiling the end-of-job report.
4) Have all SOURCE and TARGET tapes next to you. If 2-to-1 conversion is
   intended, put the 2 10GB source tapes in the MKB200: caddy and the one
   20GB target tape to MKB100: Please make sure that SOURCE tapes are ALWAYS
   protected, TARGET tapes are ALWAYS unprotected.
   Before and after the handling of any of these tapes, make sure they comply
   with the general rules for tape handling:

5) Do @DKA100:[MACRODATA.RARE.RARE_MAKER.COM]LAUNCH_RAREMAKER
   and the script will guide you to launching the batch job.

In this report, not all e-mail options were enabled. People on data shift
are expected to summarize all e-mails that the procedure sends.

The RAW to ZEBRA conversion yielded 5 error reports that had to do
with the ZEBRA file being shorter than the RAW one. This is a priori
impossible for a MACRo RUN that includes WFD readout.

SIZE RUN11099 NRD002 RAW 33402 FZEX 32527-NO not obvious why of less size
SIZE RUN11231 NRD002 RAW 15249 FZEX 15146-NO not obvious why of less size
SIZE RUN11232 NRD002 RAW 28505 FZEX 27929-NO not obvious why of less size
SIZE RUN11233 NRD002 RAW 10174 FZEX 10083-NO not obvious why of less size
SIZE RUN11286 NRD002 RAW 9768 FZEX 7552-NO WFD combine warnings
                                                 possibly buffers dropped

No further debugging of the errors is expected.

The procedure took 30 hours to run, i.e., beyond the 24 hours expectation.
I believe this is due to the excessive number of files contained in these
two RARE DSTs (~800). As we advance into the running period, RARE DSTs
will have typically 200 runs per tape and thus the 24 hours goal will be
attainable. If for any reason the conversion of two 10 GB RARE DSTs extends
beyond the 24 hours, the shiftworker should lunch the next one as soon as
the other is over.

--Erik K.



This archive was generated by hypermail 2a24 : Mon Jun 12 2000 - 12:33:12 EDT