I'm not sure of what they were looking for, but here goes:
TSO Batch uses TSO submit to present the TSO user's JOB to the batch environment. Fom that point on it behaves like any batch job. It's put on the IPQ gets selected for execution and its printable Op is placed on the OP Spool.
In some shops "batch" jobs are submitted via TSO directly or through scheduling packages. Some packages may have their own s/w to do this.
But once the job is presented to theop system it becomes a batch job.
I've written batch jobs annd CICS transactions that submit other jobs to the batch environment. So there are a range of ways to "run" batch jobs.