STRPRTWTR DEV(PAMPRT1) OUTQ(P9)
Just making sure that you are specifying the outq.
<i>If he emulates a print session, the printer will go active…</i>
Then the printer device description is a printer emulation session device description. I <i>think</i> that it’s <i>possible</i> that someone manually created the device description in such a way that it ended up with all appropriate attributes to allow it to respond to a printer session startup, but that doesn’t matter. However it was created, it’s a session device.
In order to use it, start the related printer session. Without the session answering, the device can’t vary on and the writer has nothing to talk to.
The session should be configured to start when the PC starts and connects to the AS/400.
Alternatively, create a remote *OUTQ that sends spooled files to a queue on the PC. The PC needs to allow remote systems to send spooled files to it. The queue will be a Windows spool queue that’s associated with the printer. The name of the queue might be something like LPT1 and should be visible if you look at the Port assignment in Windows Printers.
The device description doesn’t have be varied on in order to use it in programming. It only needs to be varied on if there’s an *OUTQ that is sending to the physical device. But you don’t have to use that *OUTQ; you can create a different one — the remote *OUTQ. A remote *OUTQ that sends over TCP/IP isn’t necessarily talking to a printer device; it’s possible for it to be sending to a remote system (e.g., a PC) that is actually doing the talking to the device.