RE: Multiple writers on single printer failing on V7R1

Try various settings for SYSDRVPGM for your 3812 device. Probably *IBMIPPDRV is going to work best and easiest. It depends on what protocol that port plays on the printer. *IPDS has its own driver and should not have changed. IPP (internet print protocol) does a good job of notifying the server when it has finished a print job. If you're using it to print PC network print jobs as *USERASCII, *HPPJLDRV probably would work best.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of James Rich
Sent: Friday, August 30, 2013 11:55 AM
To: midrange-l
Subject: Multiple writers on single printer failing on V7R1

Hi everyone,

We upgraded a customer from V5R4 to V7R1 last week. When I say
"upgrade",
I really mean a new install. The old system had two print devices that
pointed to the same LAN printer but on different ports, as follows:

First print device (PS):
DEVD PS
DEVCLS *LAN
TYPE 3812
MODEL 1
LANATTACH *IP
PORT 9100
ATTACH *DIRECT
RMTLOCNAME printer.domain.com

Second print device (P1):
DEVD P1
DEVCLS *LAN
TYPE *IPDS
MODEL 0
LANATTACH *IP
AFP *YES
PORT 9600
RMTLOCNAME printer.domain.com

As you can see, both print devices reference the same printer on the
network, but the ports are different.

The problem we have is that if we start one of the writers (say P1) the
other writer stops responding. If we then end P1 we can start PS, but now
P1 won't work. On the V5R4 system worked just fine, but not now on V7R1.
Is there something I've overlooked?

James Rich

if you want to understand why that is, there are many good books on
the design of operating systems. please pass them along to redmond
when you're done reading them :)
- Paul Davis on ardour-dev
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.