REGISTER or login:
...you have to put a 2 beside it because on the printer line it is set up to outque instead of the laser.
Most likely, it is always going to go to an output queue and will never 'go to' the printer in your normal operation. That isn't a problem; that's how it's supposed to work even in situations where "auto-print" is working.
(There is a technical possibility of having a program send output directly to a printer, but it's almost guaranteed that you do not want that to happen.)
Your use of the term "auto-print" is a little confusing. However, we would normally assume that you simply mean that you don't want to be forced to use option 6 nor option 2. You just want to run the program and have the printed output come out of the printer.
You would do that by setting up an association between the output queue and the printer. The association is done by starting a "writer" and telling it which output queue to write from and which printer to print to.
Since you are using option 2, that means that a writer is already started for the printer. But that writer is associated with a different output queue than the one that has your reports. When you use option 2, what actually happens is that your reports are being moved to the other output queue, the one that the writer is using.
At some point after your system starts up, the writer for that printer is started. It might be configured to start automatically or someone might run the STRPRTWTR command to do it. Either way, the command could be changed to specify the output queue that is actually being used by your programming.
But the exact way to do that depends on exactly what is going wrong.
Are you the only user having the problem? Or do all users have the same problem? If other users have the same problem, is it the same output queue for everyone? Are there other reports that "auto-print" on that printer? Is this only for particular kinds of reports?