- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: LPQ command in DCL procedure has no timeout (F...
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
тАО11-18-2009 09:54 AM
тАО11-18-2009 09:54 AM
I'm trying to generate an overview, with a DCL script, of all LPD printers, and check if they are available.
In the DCL procedure, I do
$ LPQ
But if there is no response, it'l hang endlessly. I can NOT mess with global timeout logicals.
I tried
$ PIPE LPQ
But it does not work.
OpenVMS 7.2-2
TCPIP 5,1 ECO 4
Who can help me out?
Thnx,
Bob.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-18-2009 10:09 AM
тАО11-18-2009 10:09 AM
Re: LPQ command in DCL procedure has no timeout (Find a way to limit a command duration time)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-18-2009 11:40 AM
тАО11-18-2009 11:40 AM
Re: LPQ command in DCL procedure has no timeout (Find a way to limit a command duration time)
If you won't upgrade (which is what I suspect when presented with these cases), then you can brute-force a DCL timeout using a SPAWN that first issues a second nowait spawn of a subprocess that itself first finds and then waits and then kills its parent (and itself in the process), then issue the LPQ.
Alternatively, ping might provide a basic idea if the printer is reachable. (LPD/LPR is rather simple-minded, as printing software goes.) Or SNMP, if the printer supports it.
But getting (more) current software loaded would be better in general. Both OpenVMS Alpha and TCP/IP Services, and ECOs for same.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-18-2009 01:36 PM
тАО11-18-2009 01:36 PM
SolutionTry the attached command procedure
$ @CMD_TIMEOUT
For example:
$ @CMD_TIMEOUT 0:0:30.0 LPQ MYQUEUE
will give the command 30 seconds to complete. Status is that of the command or %SYSTEM-F-EXITFORCED if the command was timed out.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-18-2009 03:47 PM
тАО11-18-2009 03:47 PM
Re: LPQ command in DCL procedure has no timeout (Find a way to limit a command duration time)
or just use John's procedure
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-19-2009 01:36 AM
тАО11-19-2009 01:36 AM
Re: LPQ command in DCL procedure has no timeout (Find a way to limit a command duration time)
@John:
This works fine for me, Thnx!
@Hoff:
- I am not able to upgrade, unfortunately.
- The spawn procedure you suggest is the CMD_TIMEOUT procedure of John.
- Pinging (Which I would prefer as well) is not an option, printer is just known as remote port on a remote machine in a different company then which I am in.
Thnx to you all for your response,
Grtz,
Bob