In our case only the system hardware and the OS changed.
I have seen in some IBM docs that a lot of the *lan printing changed,
and we had to make one change to many *lan printers
Printer error message . . . . . . : *INFO (used to be *INQ) to avoid CPA403D.
This is our only printer attached to a pc (not a network printer) with an issue.
We are upgrading iSeries Access version before open a ticket w/IBM.
Jim

---- Pat Barber <mboceanside@xxxxxxxxxxxxxxxx> wrote:
I ran into a similar thing when a client went to a tcp/ip lan from twinax.

Certain "features" that worked in a twinax connect "would not" work
on the new lan because customer did not PSF. This is required for
certain *AFPDS features.

I didn't have many pc attached printers on that system, but on several
I had to down load the current drivers on the the printer and rebuild
the printer device in Iseries Access. That seemed to fix most of the
problems.


franz400@xxxxxxxxxxxx wrote:

Recent upgrade from V4R5 to V5R4 (new system).
Several print devices stopped working, most needing a more specific *mfrtypmdl,
but a HP6p connected via parallel to iSeries Access pc, configured as *HP6
on both old and new is still a problem.
When *AFPDS spooled file printed - get printer attention light.
No *wscst on old or new system.
Same iSeries Access client.
Any ideas?
Jim Franz


--
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.


This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].