Hi:
I guess without delving more into the structure of the output dataset from GLM, I'd have to say, "it depends" -- it depends on whether there is a variable named PROBF, it depends on whether that variable contains the number you want on every row of the table and it depends on what you mean by "entire" table.
Simply changing the WHERE statement might be enough:
where ProbF < .10;
However, that would only return the rows on which the ProbF variable was actually LT .10; however, you may just as well have a column called _STAT_ and another column called _VALUE_ (hypothetical names) and, on one row the value of _STAT_ was the character string 'ProbF' and _VALUE_ was .10 and on another row, the value of _STAT_ was the character string 'ProbT' and the _VALUE_ was .0000001 (fake example for ProbT). Since GLM is not one of my "go to" procedures, I'm not familiar with the structure of the output datasets.
All I can say is you'll have to test it out and see whether a simple WHERE will work, given the structure of the GLM output. As I said before, more sophisticated processing is possible, such as the situation where you need to read something from the dataset, make your decision and then do your PRINT -- this might be a job for using SAS Macro processing and the SAS Macro facility.This paper is a good overview of the SAS Macro facility and has some examples of conditional processing.
http://www2.sas.com/proceedings/sugi28/056-28.pdf
My standard warning is to explore all possible non-Macro solutions, especially if you are a beginner, before you go down the Macro road and if you decide you do need to use SAS Macro, then start from a WORKING SAS program -- the SAS Macro facility only generates code to send forward to the compiler -- if your starting point code is broken, the Macro facility will then generate broken code.
cynthia