|
Connected tcp, if I reply with an I it'll go ahead and print, but we have some users that will not have access to job queues so theirs won't print. On Tue, 15 Feb 2005 16:51:36 -0500, Wilt, Charles wrote > How is the printer connected? > > What are you replying? > > Charles Wilt > iSeries Systems Administrator / Developer > Mitsubishi Electric Automotive America > ph: 513-573-4343 > fax: 513-398-1121 > > > -----Original Message----- > > From: midrange-l-bounces+cwilt=meaa.mea.com@xxxxxxxxxxxx > > [mailto:midrange-l-bounces+cwilt=meaa.mea.com@xxxxxxxxxxxx]On > > Behalf Of > > dpalme@xxxxxxxxxxx > > Sent: Tuesday, February 15, 2005 4:49 PM > > To: Midrange Systems Technical Discussion > > Subject: configuring tally printer > > > > > > I have been attempting to configure a tally printer, using their > > documentation but obviously something is going wrong. This > > is a green bar > > printer and the device description has the pritner setup for > > continuous 132, > > however whenever a job is printed the job displays a message > > waiting and > > wants you to load std paper.....which is already loaded. > > > > Any idea how to get rid of this annoying message? > > > > Message . . . . : Load form type '*STD' device TALLY > > writer TALLY. (G B > > I H > > R > > C) > > > > > > > > > > Cause . . . . . : The file on output queue TALLY in > > library QUSRSYS > > requires > > form type '*STD' to be loaded on device TALLY. The form > > type for the > > file > > was all blanks when '' appears as the form > > type. > > Possible choices for replying to > > message . . . . . . . . . . . . . . . : > > G -- Begin processing the current file after loading the form > > type. > > B -- Begin processing the current file after loading and > > aligning the > > form > > type (no alignment message is sent - same as option 1 on > > System/36). > > I -- Ignore the request to load the form type. Print the file on > > the > > current formtype (same as option 0 on > > System/36). > > > > > > More... > > -- > > 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. -- Open WebMail Project (http://openwebmail.org)
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.