sahana, Instead of trying to force a Table space scan (which most people try to avoid on large data tables), you might want to figure out why the List Prefetch is failing. You might not have enough space allocated to your sort area.
However, the only way to ensure a Table space scan is to remove any Index(es). Without an Index, you can only have a Table space scan.
If you Explain the query, it can give you some indication of what DB2 is trying to do. For example, which table/index is it doing a RID sort?
Making an assumption you have an index on the A table columns CD_LAB_TIME and SAT_NO (at a minimum and in that order), The A table index could be doing a partial Index scan. Of course if the other A columns in your WHERE clause are Indexed and can reduce the rows that qualify better, DB2 may be using them instead. Again, the Explain will provide this information.
Either way, the qualifying A rows will have all the SAT_NO columns in no particular order. This is the column being joined to the B table. DB2 is (probably) sorting the A and/or the B rows by SAT_NO to make the join more efficient (by getting the RIDs in order so pages are only accessed once to get all possible qualifying rows).