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



The device descriptions are identical and the printer files (ie:  qsysprt)
are also identical.

Jerry

----- Original Message -----
From: Steve Richter <srichter@autocoder.com>
To: Midrange Systems Technical Discussion <midrange-l@midrange.com>
Sent: Tuesday, January 21, 2003 4:37 PM
Subject: RE: 4224 works on V4R4 and malfunctions on V5R1


> does a line by line comparison of the device descriptions  of the printer
> between the v4r2 and v5r1 systems show any differences?
>
> When the printer stops printing on the v5r1 system does the writer job
fail?
> any error messages?
>
> Steve
>
>
> -----Original Message-----
> From: midrange-l-bounces@midrange.com
> [mailto:midrange-l-bounces@midrange.com]On Behalf Of Jerome Draper
> Sent: Tuesday, January 21, 2003 6:37 PM
> To: Midrange List
> Subject: Re: 4224 works on V4R4 and malfunctions on V5R1
>
>
> None of the below.
>
> Rob, The printer was not "moved" except that the twinax was moved from the
> brick on the V4R2 AS400 to the brick on the V5R1 AS400.  The printer was
not
> physically moved.  Could it be the brick on the V5R1 AS400 (yes, could
be).
> Paper was not unloaded/reloaded nor was paper thickness changed.
>
> NeilP,  I'll try your suggestion of moving it to a new port on the brick
> (perhaps it's the brick).
>
> bdietz:  No the devices were not migrated and we tried the delete/recreate
> of the device to no avail.
>
> Jerry
>
>
> From: <rob@dekko.com>
> To: Midrange Systems Technical Discussion <midrange-l@midrange.com>
> Sent: Tuesday, January 21, 2003 11:54 AM
> Subject: Re: 4224 works on V4R4 and malfunctions on V5R1
>
> > This sounds like a physical defect rather than a software issue.
> >
> > Did you physically move the printer to attach it to this new machine?
> > Hopefully no physical damage was done.
> >
> > Did you unload/reload paper to attach it to this new machine?
> > Maybe you adjusted your paper thickness wrong.
> >
> > Rob Berendt
>
> From: <neilp@dpslink.com>
> To: Midrange Systems Technical Discussion <midrange-l@midrange.com>
> Cc: Midrange Systems Technical Discussion <midrange-l@midrange.com>;
> <midrange-l-bounces@midrange.com>
> Sent: Tuesday, January 21, 2003 12:36 PM
> Subject: Re: 4224 works on V4R4 and malfunctions on V5R1
>
> > I noticed similar weird behaviour when I moved a 4224 from a V4R5 model
> > 170 to a new V5R2 model 270 on the weekend.  It would drop contact with
> > the system quite often.  I solved the problem by moving it to a
different
> > twinax port (I manually altered the device description port #, didn't
let
> > auto-config do anything, and it's worked fine ever since).
> >
> > ...Neil
>
> From: <bdietz@3x.com>
> To: Midrange Systems Technical Discussion <midrange-l@midrange.com>
> Sent: Tuesday, January 21, 2003 2:09 PM
> Subject: Re: 4224 works on V4R4 and malfunctions on V5R1
> >
> > I'll make an assumption....you migrated the device description from the
> > "old" system to the new one.  This should work. delete thed devd and let
> > auto config create a new one.  I seem to remember some apar or some such
> > document somewhere.
> >
> > -------------------------
> >  Bryan Dietz
> > 3X Corporation
> > 614-410-9205
> >
> > ======================
> > I have two 4224 *IPDS printers hooked up to a V4R2 machine and they work
> > fine.  I move them to a new V5R1 machine and they hardly print at all.
> > Funny scratching by the print head and sporadic print lines but never
> > anything close to a full report.  For example, they won't print a
standard
> > report from QPRINT.  Put them back ont he V4R2 machine and all is fine.
> >
> > Anyone seen this?  PTF?
>
>
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.