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



Hi guys,

The reason I was looking for a Device Description was because when I did a
WRKSPLF and then an F22 for Printers, these printers showed up on the
screen. Now they don't.

I recreated a RMTOUTQ for my shipping printer, but when we try to print
something from it, we have to turn the printer off, then on again. If I
have more than 1 SPLF to print, waiting for each other, I can turn the
printer off and on and all of the SPLFs will print. But, if a SPLF
completes, and another SPLF comes along, we have to do the turn off and
turn on thing again. Before we do the turn off, turn on, the status of
the SPLF is SND.



Thanx again,

Nick



Nick Radich
Sr. Programmer/Analyst
EPC Molding, Inc.
Direct (320) 679-6683
Toll free (800) 388-2155 ext. 6683
Fax (320) 679-4516
nick_radich@xxxxxxxxxxxxxx



"Wilt, Charles" <WiltC@xxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
08/30/07 11:26 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


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

Subject
RE: Creating *LAN printer descriptions






Remote outqs don't use *DEVDs.

Note that it is possible to set up a dummy *DEVD for use with applications
that only work with *DEVDs
and not *OUTQ. But it doesn't sound like that's what you had.

Charles


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Nick_Radich@xxxxxxxxxxxxxx
Sent: Thursday, August 30, 2007 12:18 PM
To: Midrange Systems Technical Discussion
Subject: RE: Creating *LAN printer descriptions

Hi Lukas,

Yes they are remote outqs.



Thanx,

Nick



Nick Radich
Sr. Programmer/Analyst
EPC Molding, Inc.
Direct (320) 679-6683
Toll free (800) 388-2155 ext. 6683
Fax (320) 679-4516
nick_radich@xxxxxxxxxxxxxx



"Lukas Beeler" <l.beeler@xxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
08/30/07 11:11 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


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

Subject
RE: Creating *LAN printer descriptions






Are you sure you're not using remote outqs?

You can check this by using CHGOUTQ NAME, and then pressing enter
multiple times till you see all settings..

I don't think a Windows Server upgrade can affect your *DEVDs.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Nick_Radich@xxxxxxxxxxxxxx
Sent: Thursday, August 30, 2007 6:02 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Creating *LAN printer descriptions

Hello everyone,

I'm back with my "favorite" subject, printers.

Our Network guy did an upgrade to our Printer Server, from NT to 2003,
and
everything blew up.

Somehow, the network blew away all of my Printer Device
Descriptions on
our AS/400 for any printer that was set up as a *LAN printer. All of
these printers are Intemec 3400s, whick we use for labels.
My Outqs are

still there and so are the Writers. Just no Device Descriptions. I
didn't think this was even possible.

Where I am stuck is setting up the Device Descriptions for
the Printers
themselves. I am trying to set them up with DEVCLS = *LAN,
PORT = 9100,

LANATTACH = *IP, but what should I use for TYPE and MODEL, MFRTYPMDL,
and
SYSDRVPGM?

Thank you for your help!!

I still hate printers.



Thanx,

Nick


PS, We are at V4R5 and I call our box and AS/400 because that
is what it

says on the front of it. The company is too cheap to upgrade.


Nick Radich
Sr. Programmer/Analyst
EPC Molding, Inc.
Direct (320) 679-6683
Toll free (800) 388-2155 ext. 6683
Fax (320) 679-4516
nick_radich@xxxxxxxxxxxxxx
--
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.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.