RE: WSCST type function on IPDS printer type

I just tested my idea of using two DEVDs to handle special forms, and it
didn't work as I had hoped. I sent a report with a different form to
printer P1. Then I gave the change forms msg a G, and had the Align Forms
message waiting. While that message was waiting, I released a report on
printer P1LAN. That report waited until I answered the align forms
message, and the first report printed. Unfortunately, after the printer
waited the 30 seconds or so for the device time out, the report on P1LAN
printed, even though I had a different forms type on P1.

While one of the DEVDs is ACTIVE, it must send a busy message to the
second DEVD/OUTQ. Once the DEVD finishes its print job(s) and times out,
the physical printer then becomes available to the next print request. So
the system will prevent the second DEVD from interfering with an ACTIVE
print job, but once that job finishes and times out, the next print job
will grab the physical printer. If it's the original DEVD/OUTQ, it will
track the forms type, but a job from the other DEVD/OUTQ only tracks its
own forms type. The printer is not considered ACTIVE if the change forms
message is waiting, but it is active if the align forms message is
waiting.



Another nice idea shot down.

Steven Morrison
Fidelity Express





Steve Rushing <sgr_mags@xxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
07/23/2007 08:37 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: WSCST type function on IPDS printer type






The printer I am using is LAN attached. I don't see how the two DEVD's can

communicate forms changes to each other. They can't know the other even
exists can they? Now maybe if it was two OUTQs and one DEVD it might work.

I will just have to test this when time allows. For now, they will have to

be careful and hold the writer they are not currently using.

Thanks!



>Charles,
>
>Which are you saying won't work? We are currently using an IBM 6400
>printer, IP attached, with IPDS. We use two device descriptions, both
>active at the same time. On is used for normal printing, the other is
used
>for one barcode report. As I check right now, both writers are active.
The
>IPDS card adds the second address to the printer.
>
>I'm not positive that the forms change would work using both device
>descriptions. (We can't get the users to handle the forms changes
>correctly here.They're convinced they have to send a break message to
>everyone when they print checks, and then answer the forms change
messages
>with an 'I'.
>
>
>Steve
>
>Steven Morrison
>Fidelity Express
>
>
>
>
>"Wilt, Charles" <WiltC@xxxxxxxxxx>
>Sent by: midrange-l-bounces@xxxxxxxxxxxx
>07/23/2007 09:44 AM
>Please respond to
>Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
>
>
>To
>"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
>cc
>
>Subject
>RE: WSCST type function on IPDS printer type
>
>
>
>
>
>
>It might work with twinax, as the system could tell there was only one
>device....
>
>Then again, I vaguely recall that with a twinax attached *IPDS printer
>(6400) I couldn't have two
>*DEVDs.
>
>But I'm pretty sure it doesn't work with a network attached printer.
>
>Charles
>
>
> > -----Original Message-----
> > From: midrange-l-bounces@xxxxxxxxxxxx
> > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Wilt, Charles
> > Sent: Monday, July 23, 2007 10:40 AM
> > To: Midrange Systems Technical Discussion
> > Subject: RE: WSCST type function on IPDS printer type
> >
> > Steven,
> >
> > AFAIK, the system would manage the forms if there was only one *DEVD.
> >
> > With two going to the same printer, you'd run into issues
> > since the system sees them as two separate devices.
> >
> > Charles
> >
> >
> > > -----Original Message-----
> > > From: midrange-l-bounces@xxxxxxxxxxxx
> > > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
> > > smorrison@xxxxxxxxxxxxxxxxxxx
> > > Sent: Monday, July 23, 2007 10:28 AM
> > > To: Midrange Systems Technical Discussion
> > > Subject: Re: WSCST type function on IPDS printer type
> > >
> > > The system will manage the form changes if you let it. Your
> > users must
> > > wait for the forms change messages, then change to the
> > special form,
> > > then answer the message with a 'G' to tell the system that
> > the special
> > > form is loaded. If they answer the forms change message
> > with an 'I' -
> > > Ignore, they just told the system that they did not change forms.
> > > They'll also have to answer the forms change messages to
> > switch back
> > > to normal forms correctly.
> > >
> > > The system will not write to the printer description A if printer
> > > description B is printing. You should test this with the
> > special forms
> > > handling for yourself. We don't change forms often, and our
> > printer is
> > > lightly used, except in the morning.
> > >
> > >
> > > Steven Morrison
> > > Fidelity Express
> > >
> > >
> > >
> > >
> > >
> > >
> > > Steve Rushing <sgr_mags@xxxxxxx>
> > > Sent by: midrange-l-bounces@xxxxxxxxxxxx
> > > 07/20/2007 07:27 PM
> > > Please respond to
> > > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> > >
> > >
> > > To
> > > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc
> > >
> > > Subject
> > > Re: WSCST type function on IPDS printer type
> > >
> > >
> > >
> > >
> > >
> > >
> > > Steven, my concern was forms changes. How does the plain
> > paper device
> > > know
> > >
> > > that the printer is full of invoices for IPDS printing and
> > vice-versa?
> > > We only print invoices weekly, and the normal paper is
> > replaced with
> > > invoice paper. If somebody in another department sends a
> > print job to
> > > the printer before the invoice job prints, wouldn't the
> > printer start
> > > printing the wrong thing on the invoice paper?
> > >
> > > Thanks,
> > >
> > > -Steve
> > >
> > >
> > >
> > >
> > > > >For now we are using two different device descriptions to get it
> > > > >all done, but they have to be careful to hold writers etc. when
> > > > >setting up for special print jobs and forms. I would
> > prefer to have
> > > > >on device description.
> > > >
> > > > >Any suggestions appreciated.
> > > >
> > > >We have an IPDS printer (IBM 6400) with 2 device
> > > descriptions. Both are
> > > >active (along with writers) at the same time with no
> > > problems. I've also
> > > >used laser printers (IBM, HP & Lexmark) with IPDS cards
> > with multiple
> > > >device descriptions. Both device descriptions can be active
> > > at the same
> > > >time without problems. Just send your output to the correct outq.
> > > >
> > > >Steven Morrison
> > > >Fidelity Express
> > > >903-885-1283 ext. 479
> > > >--
> > > >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 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 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 e-mail transmission contains information that is
> > intended to be confidential and privileged. If you receive
> > this e-mail and you are not a named addressee you are hereby
> > notified that you are not authorized to read, print, retain,
> > copy or disseminate this communication without the consent of
> > the sender and that doing so is prohibited and may be
> > unlawful. Please reply to the message immediately by
> > informing the sender that the message was misdirected. After
> > replying, please delete and otherwise erase it and any
> > attachments from your computer system. Your assistance in
> > correcting this error is appreciated.
> >
> > --
> > 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 e-mail transmission contains information that is intended to be
>confidential and privileged. If you receive this e-mail and you are not
a
>named addressee you are hereby notified that you are not authorized to
>read, print, retain, copy or disseminate this communication without the
>consent of the sender and that doing so is prohibited and may be
unlawful.
> Please reply to the message immediately by informing the sender that
the
>message was misdirected. After replying, please delete and otherwise
>erase it and any attachments from your computer system. Your assistance
>in correcting this error is appreciated.
>
>--
>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 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 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 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.