I've never used this particular oscilloscope, but I'll give it a go. Note that you'll need to figure out how to incorporate the command sequence I've recommended below into whichever data acquisition software package you're using (LabVIEW, MATLAB, VEE, etc.).
Start by resetting the oscilloscope's controls and settings to their "factory setup defaults" (see also appendix B "Factory Setup" in the TBS1000 Programmer manual [hint: search for "tbs1000 programmer manual" on tek.com]). This is done by issuing the SCPI "*RST" command:
Display channel 1, AND turn OFF channel 2:
SELECT:CH1 ON;CH2 OFF
Configure the horizontal, vertical, triggering controls, etc. as desired—e.g., horizontal time/div = 1ms/div; channel 1 volts/div = 1V/div:
Configure the oscilloscope to acquire a single waveform when the oscilloscope detects that the triggering conditions are met:
Acquire a single waveform ("run once"):
Wait for the data acquisition to complete. This is done by issuing the SCPI query "*OPC?" (operation complete?). As stated in the oscilloscope's Programmer manual, "[t]he *OPC? response is not available to read until all pending operations finish", meaning the *OPC? invocation blocks until the oscilloscope finishes the data acquisition task.
In the WAVEFORM commands group, use the CURVE? query to transfer Channel 1's waveform data from the oscilloscope to your computer:
Note that the "CURVE?" query returns a stream of bytes that are typically stored in a buffer that your program creates for this purpose (e.g., a character array, or a byte array). Your program then parses the desired information from the stored data in the buffer. Exactly how this is done depends entirely upon the programming language and instrument I/O libraries you're using—e.g., LabVIEW, MATLAB, VEE, etc.—and is left as an exercise for the reader.
P.S. If you need help writing the code for a specific programming language, I recommend you find/use forums that are dedicated to the particular programming language you're working with—e.g., LabVIEW instrument I/O programming forums; MATLAB instrument I/O programming forums, etc. Those folks would be much better suited to answering programming language specific questions than the folks in an electronics forum. (<- Not complaining/whining, just sayin'...)