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


  1.  Home
  2. MIDRANGE-L
  3. August 2003

Re: RUNRMTCMD print output?

George

One trick in DOS (& Unix?) type systems is to redirect output to the system bit bucket. This is done by putting

> nul

at the end of a command.

E.g., if you are in a command prompt in XP, type

dir > nul

and you will see nothing.

HTH

Vern

At 10:24 AM 8/8/2003 -0400, you wrote:
Hopefully someone can point me in the right direction on this one.

I have several jobs scheduled that issue RUNRMTCMD to an NT box.  It works
fine. However, it appears that whatever the job wrote to STDOUT is being
passed back to the iSeries, and printing on the default printer for the
USRPRF  used to submit the job.

My question is: How do I stop this?

I figure I could re-schedule those jobs using a USRPRF that points to an
OutQ that isn't associated with an active writer, but I'd rather stop it
altogether.

Any ideas?



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.