- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Server Que
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-25-2004 03:07 AM
тАО08-25-2004 03:07 AM
to print to two different printers? Presntly our programs print only to one printer, but we would like the same job to print to two different printers. Thanks Joe
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-25-2004 03:10 AM
тАО08-25-2004 03:10 AM
Re: Server Que
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-25-2004 03:13 AM
тАО08-25-2004 03:13 AM
Re: Server Que
Yes, the exact same file that prints on one printer, should be the same file print on the other printer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-25-2004 03:32 AM
тАО08-25-2004 03:32 AM
Re: Server Que
- send output to two different queues (one local, the other was a DQS queue for printing in a different location)
- adapt output that I have received from a IBM host via SNA/PRE (printer emulator) to send it to a laser printer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-25-2004 03:38 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-25-2004 03:53 AM
тАО08-25-2004 03:53 AM
Re: Server Que
The job is currently qued with the PRINT command. Print/que=XXX.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-25-2004 03:58 AM
тАО08-25-2004 03:58 AM
Re: Server Que
HTH,
Thanks & regards,
Lokesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-25-2004 04:34 AM
тАО08-25-2004 04:34 AM
Re: Server Que
If you want a transparent way to yours problem, try to implement CTLSMB as mentioned by Uwe. With CTLSMB you will have a queue which works with all methods for submitting print jobs.
You can write your own print symbiont. (The hardest way).
If you want a simplier way, you can write a simple command procedure which will substitute the print command. I give you a sample, which is not perfect but working:
$ double=0
$ a=1
$l:
$ qual = p'a'
$ if f$extract(0,4,qual).eqs."/QUE"
$ then
$ que = f$element(1,"=",qual)
$ if que.eqs."DOUBLE"
$ then
$ double=1
$ p'a'=""
$ endif
$ endif
$ show symbol /all
$ a=a+1
$ if a.lt.9 then goto l
$ oldprint=print
$ print=="PRINT"
$ if double
$ then
$ print /queue=q1 'p2' 'p3' 'p4' 'p5' 'p6' 'p7' 'p8'
$ print /queue=q2 'p2' 'p3' 'p4' 'p5' 'p6' 'p7' 'p8'
$ else
$ print 'p2' 'p3' 'p4' 'p5' 'p6' 'p7' 'p8'
$ endif
$ print==oldprint
You must define a symbol like this:
$ PRINT == "@dev:[dir]PRINT.COM X"
The X at the end is a dummy parameter to allow to have a qualifier as first parameter (Not allowed by command procedures).
Bojan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-29-2004 04:01 PM
тАО08-29-2004 04:01 PM
Re: Server Que
Regarding your code:
>$ oldprint=print
>$ print=="PRINT"
>...
>$ print whatever
>...
>$ print==oldprint
You can replace this with
$ printxx whatever
The additional "xx" will bypass symbol lookup, and since DCL doesn't look past the first 4 characters, it will invoke the real "PRINT" command. Purists will tell you that's not strictly supported, which is true (but I doubt very much it will ever break).
If you want fully supported, go with:
$ SET SYMBOL/SCOPE=(NOLOCAL,NOGLOBAL)
This will prevent the translation of global symbols and local symbols from higher level procedures while executing your procedure.
Note that your existing code will break symbol contraction. Consider:
$ PR*INT=="@dev:[dir]PRINT.COM X"
this will allow the verb "PRINT" to be contracted down to PR (just like the real command), but after your code executes, the ability to contract will be lost.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-29-2004 06:12 PM
тАО08-29-2004 06:12 PM
Re: Server Que
Thank you for your hint. The printxx reduces the procedure for some error handling (in my procedure if you get an error in the real print command you lose the print symbol). The procedure I posted is far away from perfection. There is much to do abbout qualifier recognition ( print /copy=3/queue=double or print /queue=double/copy=3 will not work properly because there is no space between qualifiers). Maybe a new lexical function, say f$dclparse, will be great for such procedures.
I also noted that there is an extra line in my code ($ show symbol /all) this was only for debuging purpouses.
Bojan