|
Also power off the printer.--
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Charles Wilt
Sent: Friday, February 05, 2016 8:30 PM
To: Midrange Systems Technical Discussion
Subject: RE: Stopping CPI8030 - *Attention* Device *N on resource *N
failed.
As mentioned in my post, we've done that. But the messages continue.
On Feb 5, 2016 8:04 PM, "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx> wrote:
End the writer job and vary off PRT03, should stop all messages.http://archive.midrange.com/midrange-l.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf
Of Charles Wilt
Sent: Friday, February 05, 2016 7:45 PM
To: Midrange Systems Technical Discussion
Subject: Stopping CPI8030 - *Attention* Device *N on resource *N failed.
Having issue with a printer..
System issued
CPF2677 - Device PRT03 no longer communicating.
CPA5201 - Hardware failure on device PRT03
Cause . . . . . : File QPSPLPRT in library QSYS for job
454603/QSPLJOB/PRT03
is being processed. The device must be made ready before an
active job will
give up control of the device.
Then a bunch more
CPF2677 - Device PRT03 no longer communicating.
Then Some
CPI8030 - *Attention* Device PRT03 on resource CTL02 failed.
Then more
CPF2677 - Device PRT03 no longer communicating.
We ended the writer and varied off the device, but every couple of
minutes the system issues a
CPI8030 - *Attention* Device *N on resource *N failed.
Last time this happened, our monitoring software paged us 200 times
overnight.
How do I make this stop?
Printer is a twinax attached Printek emulating a 4214-002.
Thanks!
Charles
--
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
--
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
--
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.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
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.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
--
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.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
