as400 printer setup

[turbosporsche]

I know this must be an old beating down question but sorry i got thrown into maintaining out as400 machine. Right now at work theres one network printer setup on system. the printer is on its way out and the company already bought a new hp 5600 crappy printer. They want it set up on one computer as an end user. whats the best way to remove the network printer and install the local one via its usb cable. If i dont have to remove it thats fine to just make the new printer the default one. thanks

[Rocky]

If it's attached to a PC with a USB and not to the network - the only way that I know of to make it work with the iSeries is to use iSeries Access.

Start -> All Programs -> IBM System i Access for Windows -> Emulator -> Start or Configure Session. Then select New Session. Specify the name you want to call the printer in the workstation ID field, select Printer radio button and hit ok - save the configuration.

The user will have to have this session running anytime they want to print an AS400/i5/i report.

[turbosporsche]

ok thanks. You mean do the setup on the as400 server itself. Not the local machine/ end users computer

[jtaylor]

Originally Posted by Rocky

If it's attached to a PC with a USB and not to the network - the only way that I know of to make it work with the iSeries is to use iSeries Access.

Start -> All Programs -> IBM System i Access for Windows -> Emulator -> Start or Configure Session. Then select New Session. Specify the name you want to call the printer in the workstation ID field, select Printer radio button and hit ok - save the configuration.

The user will have to have this session running anytime they want to print an AS400/i5/i report.

I know you can share the local printer and then create a remote OUTQ.

Originally Posted by turbosporsche

ok thanks. You mean do the setup on the as400 server itself. Not the local machine/ end users computer

No, Rocky is talking about local config on the PC itself.

We really need to know how the printer is currently configured. On a 5250 command line, issue DSPDEVD DEVD(printer name) and look at the device class. If that command fails, issue WRKOUTQD OUTQ(printer name) and look for the remote system.

[Rocky]

I never thought of using remote outq - that should work... I've never set that up though except to a Create!Form server...

[jtaylor]

Originally Posted by Rocky

I never thought of using remote outq - that should work... I've never set that up though except to a Create!Form server...

We use remote OUTQ's almost exclusively, although only rarely to shared local printers. When connecting to a shared printer, make sure the PC firewall allows your iSeries on the LPR port (?515?).

[Rocky]

We used to use them quite a bit - but since IBM allowed device descriptions to network attached printers we've eliminated all of those except for our electronic forms software (createform) and one barcode printer.

We have just a handful of PC attached printers - can number them on one hand and have fingers left over.

[DéesseT]

LPD port is 515

The title is self-documenting : PC5250 Printer Emulation: Everything You Need to Know

It comes from : System i Access

We mostly use remote OUTQs, and some virtual printer devices (local w/ HPT) for highly confidential purposes

[jtaylor]

We generally prefer remote OUTQ's to devices due to the problem with devices timing out. If a device runs out of paper overnight, it will not automatically start printing when paper is loaded, but a remote OUTQ will.

There are two reasons we use devices:

1. Page ranges
2. Form types

[Rocky]

Originally Posted by jtaylor

We generally prefer remote OUTQ's to devices due to the problem with devices timing out. If a device runs out of paper overnight, it will not automatically start printing when paper is loaded, but a remote OUTQ will.

There are two reasons we use devices:

1. Page ranges
2. Form types

Well - with the help of IBM we've overcome those problems by doing the following:

Specifying PRTERRMSG(*INFO) and SYSDRVPGM(*IBMSNMPDRV) - our timeout issues have gone away....