bssrecv(1) [debian man page]

BSSRECV(1)							  BSS executables							BSSRECV(1)

NAME

       bssrecv - Bundle Streaming Service reception test program

SYNOPSIS

       bssrecv

DESCRIPTION

       bssrecv uses BSS to acquire streaming data from bssStreamingApp.

       bssrecv is a menu-driven interactive test program, run from the operating system shell prompt.  The program enables the user to begin and
       end a session of BSS data acquisition from bssStreamingApp, displaying the data as it arrives in real time; to replay data acquired during
       the current session; and to replay data acquired during a prior session.

       The user must provide values for three parameters in order to initiate the acquisition or replay of data from bssStreamingApp:

       BSS database name
	   All data acquired by the BSS session thread will be written to a BSS "database" comprising three files: table, list, and data.  The
	   name of the database is the root name that is common to the three files, e.g., db3.tbl, db3.lst, db3.dat would be the three files
	   making up the db3 BSS database.

       path name
	   All three files of the selected BSS database must reside in the same directory of the file system; the path name of that directory is
	   required.

       endpoint ID
	   In order to acquire streaming data issued by bssStreamingApp, the bssrecv session thread must open the BP endpoint to which that data
	   is directed.  For this purpose, the ID of that endpoint is needed.

       bssrecv offers the following menu options:

       1. Open BSS Receiver in playback mode
	   bssrecv prompts the user for the three parameter values noted above, then opens the indicated BSS database for replay of the data in
	   that database.

       2. Start BSS receiving thread
	   bssrecv prompts the user for the three parameter values noted above, then starts a background session thread to acquire data into the
	   indicated database.	Each bundle that is acquired is passed to a display function that prints a single line consisting of N consecutive
	   '*' characters, where N is computed as the data number at the start of the bundle's payload data, modulo 150.  Note that the database
	   is not open for replay at this time.

       3. Run BSS receiver thread
	   bssrecv prompts the user for the three parameter values noted above, then starts a background session thread to acquire data into the
	   indicated database (displaying the data as described for option 2 above) and also opens the database for replay.

       4. Close current playback session
	   bssrecv closes the indicated BSS database, terminating replay access.

       5. Stop BSS receiving thread
	   bssrecv terminates the current background session thread.  Replay access to the BSS database, if currently open, is not terminated.

       6. Stop BSS Receiver
	   bssrecv terminates the current background session thread.  Replay access to the BSS database, if currently open, is also terminated.

       7. Replay session
	   bssrecv prompts the user for the start and end times bounding the reception interval that is to be replayed, then displays all data
	   within that interval in both forward and reverse time order.  The display function performed for this purpose is the same one that is
	   exercised during real-time acquisition of streaming data.

       8. Exit
	   bssrecv terminates.

EXIT STATUS

       0   bssrecv has terminated.

FILES

       No configuration files are needed.

ENVIRONMENT

       No environment variables apply.

BUGS

       Report bugs to <ion-bugs@korgano.eecs.ohiou.edu>

SEE ALSO

       bssStreamingApp(1), bss(3)

perl v5.14.2							    2012-05-25								BSSRECV(1)

Check Out this Related Man Page

BPSENDFILE(1)							  BP executables						     BPSENDFILE(1)

NAME

       bpsendfile - Bundle Protocol (BP) file transmission utility

SYNOPSIS

       bpsendfile own_endpoint_ID destination_endpoint_ID file_name [class_of_service]

DESCRIPTION

       bpsendfile uses bp_send() to issue a single bundle to a designated destination endpoint, containing the contents of the file identified by
       file_name, then terminates.  The bundle is sent with no custody transfer requested, with TTL of 300 seconds (5 minutes).  When
       class_of_service is omitted, the bundle is sent at standard priority; for details of the class_of_service parameter, see bptrace(1).

EXIT STATUS

       0   bpsendfile has terminated.

FILES

       No configuration files are needed.

ENVIRONMENT

       No environment variables apply.

DIAGNOSTICS

       The following diagnostics may be issued to the ion.log log file:

       Can't attach to BP.
	   bpadmin has not yet initialized BP operations.

       Can't open own endpoint.
	   Another BP application task currently has own_endpoint_ID open for bundle origination and reception.  Try again after that task has
	   terminated.	If no such task exists, it may have crashed while still holding the endpoint open; the easiest workaround is to select a
	   different source endpoint.

       Can't stat the file
	   Operating system error.  Check errtext, correct problem, and rerun.

       bpsendfile can't create file ref.
	   Probably an unrecoverable database error, in which case the local ION node must be terminated and re-initialized.

       bpsendfile can't create ZCO.
	   Probably an unrecoverable database error, in which case the local ION node must be terminated and re-initialized.

       bpsendfile can't send file in bundle.
	   BP system error.  Check for earlier diagnostic messages describing the cause of the error; correct problem and rerun.

BUGS

       Report bugs to <ion-bugs@korgano.eecs.ohiou.edu>

SEE ALSO

       bprecvfile(1), bp(3)

perl v5.14.2							    2012-05-25							     BPSENDFILE(1)

Linux and UNIX Man Pages

bssrecv(1) [debian man page]

Check Out this Related Man Page