MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » July 2008

RE: Substituting a Defunct Printer



fixed

Jerry,

I assume you meant CHGDEVPRT, in which case no that was the command I was talking about.

It doesn't matter what type of printer MW was, all that matters is what type MX is.

If MX is a network attached printer (*LAN 3812 or *LAN *IPDS), the you can easily change/recreate MW
as a separate *DEVD that points to the same physical printer, RMTLOCNAME.

Since MW was a 5250 printer session, I'd say you'd be better off deleting the MW devd and recreating
it.

If MX isn't network attached, then I think you'll have to use one of the first two options I outlined.
Certainly if MX is twinax attached, not sure about 5250 printer sessions, honestly I've not used them
a whole lot.

Charles Wilt
--
Software Engineer
CINTAS Corporation - IT 92B
513.701.1307

wiltc@xxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Jerry Adams
Sent: Friday, July 25, 2008 9:32 AM
To: Midrange Systems Technical Discussion
Subject: RE: Substituting a Defunct Printer

Charles,

The point of the exercise is to re-route any output going to MW as
automagically as possible so that, in case I missed any OCL Printer
statements, OVRPRTF commands or (slightly harder to find) USROPN's with
program invoked OVRPRTF's.

This is (or, rather, was) a PC5250 emulated printer. I looked at the
CHGDEVORT command, but it uses DEVD as the "key". I had looked at this
command earlier, but didn't see anything there that would help. Is there
another command that you are talking about as regards your last point?

Thanks.

Jerry C. Adams
IBM System i Programmer/Analyst
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Wilt, Charles
Sent: Friday, July 25, 2008 8:01 AM
To: Midrange Systems Technical Discussion
Subject: RE: Substituting a Defunct Printer

Unfortunately, there's never been a "built-in" to do this.

You can have the same output queue feed two printers, but you can't have
the same printer feed by
multiple output queues.

What you can do, is change queue MW do be a remote output queue that
points to queue MX on the local
system.

Another option, attach a data queue to the MW output queue along with a
NEP that moves spool files to
MX.

Lastly, assuming that MW is a network printer, you can simply change the
DEVD of MX to point to the
same network printer. Unlike twinax devices, you can have multiple DEVD
for same network printer as
long as the DEVDs don't have INACTTMR(*NOMAX) specified. (The default is
*ATTACH == *SEC15)


HTH,

Charles Wilt
--
Software Engineer
CINTAS Corporation - IT 92B
513.701.1307

wiltc@xxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Jerry Adams
Sent: Friday, July 25, 2008 8:24 AM
To: Midrange Systems Technical Discussion
Subject: RE: Substituting a Defunct Printer

First, it gives me an error: CPF3313 - Writer MW not active nor on job
queue. Which, of course, it isn't.

Second, I thought that this is how one balances output between printers.
I.e., assigning the same out queue to both printers, though I admit I
have
never tried it. Sort of like the BALPRINT command on the /36.

Jerry C. Adams
IBM System i Programmer/Analyst
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Paul Nelson
Sent: Friday, July 25, 2008 7:07 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Substituting a Defunct Printer

Does the CHGWTR command solve this for you?
CHGWTR WTR(MW) OUTQ(MX)

Paul Nelson
Cell 708-670-6978
Office 512-392-2577
nelsonp@xxxxxxxxxxxxx
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jerry Adams
Sent: Friday, July 25, 2008 6:53 AM
To: Midrange-L (midrange-l@xxxxxxxxxxxx)
Subject: Substituting a Defunct Printer

I have a print device description defined (MW), but the printer has long
since gone south. I know one can balance printing between multiple
printers
by defining the same out queue for them.

However, I cannot find or figure out a way to tell the system, "Hey,
when
you get a report for MW, just print it on MX." Is there a way to
automatically do that?

I've already encountered one procedure that has the printer MW defined
as
the output. Since the configuration still exists, it didn't cause the
procedure to crash and burn, but the user had one heck of a problem
finding
their report.

Thanks.

Jerry C. Adams
IBM System i Programmer/Analyst
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx

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





Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact