× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hello,

we also had problems with Twinax/IPDS printers after upgrading from 620 to
820. In the problem
determination process we found, that IBM has changed/enhanced the twinax
protocol - look for
APAR II11804. You can switch back to old protocol with a dataarea.

We have a similar config, i.e. fiber optics over multiplexor to warehouse,
and finally found that
we had mixed ports from 2 controllers on the same multiplexor.

Are your failing printers on the same port? If one device on a port fails,
it can affect all others.

I would also check the multiplexors - try different connections etc. Every
now and then we have
problems with these biests.

Good luck,

Oliver Wenzel

> -----Ursprüngliche Nachricht-----
> Von:  Valentin Petrov [SMTP:VPETROV@acme400.ACMESTEEL.COM]
> Gesendet am:  Mittwoch, 7. Februar 2001 15:40
> An:   'MIDRANGE-L@midrange.com'
> Betreff:      Twinax printer IBM 6412 IPDS on V4.5
> 
> We just upgraded from V3.7 to new box 820 on  V4.5 and we have constant
> problems with the printers.
> They are twinax attached - ( fiber optic transferred to the next block) -
> could print first 5-10 pages and stops with the following message:
> 
> 
>  
> 
>  Message ID . . . . . . :   CPI8030
> 
>  Date sent  . . . . . . :   02/07/01      Time sent  . . . . . . :
> 08:59:16   
>  
> 
>  Message . . . . :   *Attention*  Device PRT01 on resource CTL01 failed.
> 
>  
> 
>  Cause . . . . . :   The following may have caused the problem:
> 
>      -- Resource CTL01 detected a data or command error from device PRT01
> 
>      -- Device PRT01 detected a data or command error from resource CTL01
> 
>      -- Resource CTL01 detected a device PRT01 power lost
> 
>  Recovery  . . . :   Power off and power on the device. If the device does
> not  
>    become operational or this error continues, report the problem to your
> 
>    hardware service provider.
> 
>      Press F14 and report the problem.
> 
>  Technical description . . . . . . . . :
> 
>  
> 
>      - Problem Log ID ........: 0103830858
> 
>                                                                        
> Status is VARIED ON ,and just the writer is stopped.
> After starting the writer - the same story. 
> Any ideas would be appreciated.
> 
> Valentin  
> 
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

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.