The issue at hand is that the HTML file being generated for the HP OXPd platform is too large for the HP's operating system to handle. The initial cause (too many jobs being generated) doesn't have a control: Microsoft does not impose any restriction on the number of jobs that can be printed, they can only restrict the available times to print a job and manipulate priority.
Since you are using Blueprint 5.2, you could also use Pharos Print Center as a way to manage the printing.
Right, but I'm not looking to limit the number of jobs submitted, only the number of jobs listed at the terminal. I'd like to limit the number of jobs the server sends to the printer to present the user to say only the 1st 150 jobs. The user than hits 'print all' and either the entire queue is printed (all 150+ jobs) or the next 150 jobs are listed when the queue is refreshed and they hit print all again till they empty their queue.
Currently, there is not a mechanism to limit the number of print jobs displayed. To do so would require a modification to the HP Application Server's code. I'll write up an enhancement request for the product team's consideration in a future release.