- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Problem with a TNA device ...
Operating System - OpenVMS
1752777
Members
6115
Online
108789
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
тАО10-20-2004 08:02 PM
тАО10-20-2004 08:02 PM
At one of our customer sites we have many TNA devices defined and upon which are connected printers.
With the exception of two specific TNA devices, they work perfectly without any problems.
However, there are two which from time to time are creating problems. When the problem occurs the users no longer receive their print jobs (the printing is done through a third party DSM application which writes directly to the TNA device and does not print via a VMS printer queue). When I do a show dev/full I see that the TNA device is owned by a DSM process. If I do a stop/id on this process then the next print job will again hold the TNA device. At this point the ONLY way out is if I delete the TNA device and redefine it.
Any ideas?
Chaim
With the exception of two specific TNA devices, they work perfectly without any problems.
However, there are two which from time to time are creating problems. When the problem occurs the users no longer receive their print jobs (the printing is done through a third party DSM application which writes directly to the TNA device and does not print via a VMS printer queue). When I do a show dev/full I see that the TNA device is owned by a DSM process. If I do a stop/id on this process then the next print job will again hold the TNA device. At this point the ONLY way out is if I delete the TNA device and redefine it.
Any ideas?
Chaim
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-20-2004 08:37 PM
тАО10-20-2004 08:37 PM
Solution
Do you mean that the next printjob will stall again, like the one you killed?
In that case, try to determine what's within that process. It's not impossible that the problem is located there.
Check, for instance, the process status. Is it waiting for some other device (a mailbox, perhaps?) Is it stalled due to communication issues with the device?
Willem
In that case, try to determine what's within that process. It's not impossible that the problem is located there.
Check, for instance, the process status. Is it waiting for some other device (a mailbox, perhaps?) Is it stalled due to communication issues with the device?
Willem
Willem Grooters
OpenVMS Developer & System Manager
OpenVMS Developer & System Manager
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-20-2004 08:38 PM
тАО10-20-2004 08:38 PM
Re: Problem with a TNA device ...
Chaim,
Maybe some line problems. Try to do a:
$ SET HOST/DTE tnadev
after stoping the owner process. If all is OK the printer must print all you type after this command (depends on the type of printer when, for line printers this will be after you type CR or FF and for lasers after you type FF (L) which will advance one page in both cases). The set host/dte could hang or report some errors if there is a line error. To exit from the hanged set host, you must use STOP/ID.
Bojan
Maybe some line problems. Try to do a:
$ SET HOST/DTE tnadev
after stoping the owner process. If all is OK the printer must print all you type after this command (depends on the type of printer when, for line printers this will be after you type CR or FF and for lasers after you type FF (
Bojan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-20-2004 08:48 PM
тАО10-20-2004 08:48 PM
Re: Problem with a TNA device ...
when the problem occurs have you checked the network connectivity with the printer?
It may be worth looking at the socket as represent by a BG device. There should be one owned by the pid of the process. Then do UCX SHOW DEV BGxxx /FULL
It may be worth looking at the socket as represent by a BG device. There should be one owned by the pid of the process. Then do UCX SHOW DEV BGxxx /FULL
____________________
Purely Personal Opinion
Purely Personal Opinion
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP