Dispatcher commands

Alphabetic Index

• ACCTREC:data
• ALLFINISHED
• ANALYZERS?
• BEGINTAPE[:runNo[:tapeNo]]
• BROADCAST:to:command
• CLOSE:DATA
• CLOSE:isocket
• DEBUG[:arg]
• Display[:triggerMask[:latchMask]]
• DIR?
• DIRECTORY
• DROP:isocket
• DUMP
• ENDTAPE
• EXIT
• FINISHED
• FLUSH[:time]
• HOST
• ITAPE?
• LOG?
• login:address:pid:host
• NODEBUG[:arg]
• NOP
• PING
• PING-REPLY
• PWD
• REQUEST_DATA[:nreq]
• REQUEST_DISPLAY
• RUN?
• SCALERSUM:data
• SCALERREC:data
• SCALERS?
• SHUTDOWN
• STATUS?
• START
• STOP
• Write[:triggerMask[:latchMask]]
• QUIT
• QUIT_DISPLAY

Command description

Undocumented commands

ACCTREC:data

The production analyzer uses this command to periodically send the acounting data to the Dispatcher. This data contains the information on how many events were processed, how fast, etc... The accouting data is appended to the file Accounting.dat.

BEGINTAPE:runNo:tapeNo

This command is sent to the Dispatcher to start processing of one run from one data tape. When the Dispatcher receives this command from the data source, it sends a BEGINTAPE to all the analyzers and write clients and processing begins.

If the Dispatcher receives a BEGINTAPE when it already has a data source, it ignores the new command and disconnects the new client.

See also: FINISHED, ENDTAPE, ALLFINISHED, BEGINTAPE

BROADCAST:to:command

The command is resent to the Dispatcher clients specified by the to argument:

• socket number - send to this socket
• ALL - send to all clients
• SOURCE - send to the data source
• PROC - send to all analyzers
• DISPLAY - send to all display clients
• WRITE - send to all write clients

ENDTAPE

To end processing of a run, the data source sends an ENDTAPE command. The Dispatcher processes all the buffered events, sends an ENDTAPE to all analyzers, waits for them to answer with FINISHED and sends an ALLFINISHED command to the data source, analyzers and write clients, flushes the scaler data into the database and goes into the "NoTape" state.

See also: FINISHED, ENDTAPE, ALLFINISHED, BEGINTAPE

FINISHED

When ending the processing of a run, the Dispatcher sends to the analyzer the ENDTAPE command. The analyzer will receive it, perform any actions that have to be done at the end of a run (such as summing histogram files, sending back accouting and scaler data) and sends back to the Dispatcher the FINISHED command. If the analyzer does not respond with FINISHED within a timeout period, it is presumed dead and it's connection os closed.

See also: FINISHED, ENDTAPE, ALLFINISHED, BEGINTAPE

ALLFINISHED

See also: FINISHED, ENDTAPE, ALLFINISHED, BEGINTAPE

EXIT

Immediately terminate the Dispatcher. For a graceful shutdown use the SHUTDOWN command.

See also: SHUTDOWN

SHUTDOWN

Gracefully shutdown the Dispatcher. If no data is being processed, the Dispatcher exits immediately. Otherwise, the QUIT command is sent to the data source, which is expected to close the input file and send an ENDTAPE to normally finish processing of the data. Then, after processing stops (the final ALLFINISHED is sent out to everybody), the Dispatcher broadcasts the QUIT command to the analyzers and write clients, waits 15 seconds, closes all the network connections and exits.

SCALERS?

The dispatcher sends back the current scalers record

SCALERSUM:data

The scaler data is added to the current scaler record. This command is used by the analyzer to sum per-analyzer scalers, such as the number of processed events, the number of vetoed events, etc...

SCALERREC:data

The scaler data is added to the current scaler record once per spill. This command is used by the analyzer to store the EOS/BOS scalers.

Because every analyzer sends back a SCALERREC for each spill, the Dispatcher uses the 'spillNo' field of the data to ensure that data for any given spill is added only once.

ANALYZERS?

The Dispatcher will reply with the list of all connected analyzers. The output format is:

ANALYZERS:
1 4 tcp/130.199.22.3:7343 178
2 5 tcp/130.199.22.151:1928 128
END

1. sequencial number
2. dispatcher socket number
3. remote TCP connection - hostname and TCP socket number
4. number of events processed

DROP:isocket

Close the connection to the client on the socket isocket

DUMP

Write into the Log file all sorts of useful information- all the connections, all the clients, all the queues, etc...