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



We have found a solution (or at least a workaround) for this problem. In 
our user profiles, we have changed the value for Printer Device to QPRINT. 
Now, the output ends up on the correct (non-printing) output queue.

Still, it is strange that WDSCi gives precedence to the setting of the 
Printer Device. With the old settings, when we executed an interactive 
command on green-screen, the output ended up on the (non-printing) output 
queue, instead of the output queue for the Printer Device. When we 
executed the same command from WDSCi, the output was directed to the 
output queue for the Printer Device. I can't explain the difference in 
behaviour. Perhaps someone else has a suggestion?

Ewout

----- Forwarded by Ewout N Boter/WWLOGISTICS-ZWOLLE/AI/ABBOTT on 
10/28/2004 12:03 PM -----


Ewout N Boter
10/28/2004 11:46 AM

 
        To:     wdsci-l@xxxxxxxxxxxx
        cc: 
        Subject:        Outq for interactive commands

When I execute an interactive command in WDSCi, then the output is 
directed to an output queue that is directly attached to a printer. 
However, I would expect that the output would be directed to the output 
queue that is specified in my user profile. I cannot find a preference or 
a setting to direct the output to the correct output queue. Does anyone 
know how this problem can be solved?

Ewout

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.