- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: TTA2 always busy
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
тАО04-05-2006 01:20 AM
тАО04-05-2006 01:20 AM
TTA2 always busy
I am using a detached process to enable and get the reading from the clock. But the process is unable to get the clock data. The observation is one process is getting created (process name _TTA2) and it chenges the process ID every minute. If you see the details of that process, the program which is holding the device is LOGINOUT.EXE.
Could some one advice what could be the possible reason for this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-05-2006 01:31 AM
тАО04-05-2006 01:31 AM
Re: TTA2 always busy
log in.
SET TERMINAL /NOTYPE_AHEAD TTA2
HELP SET TERMINAL /TYPE_AHEAD
There's probably some clever code you can use
inside the program to do this, too, but it's
probably a lot easier from DCL.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-05-2006 01:33 AM
тАО04-05-2006 01:33 AM
Re: TTA2 always busy
if unsolicited data is received on an un-owned OpenVMS terminal, LOGINOUT is started to handle the username/password prompt.
If a non-interactive device is connected to such a serial line, you need to SET TERM/NOTYPE_AHEAD/PERM TTA2: to prevent this from happening.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-05-2006 03:44 AM
тАО04-05-2006 03:44 AM
Re: TTA2 always busy
$ SET TERMINAL /NOTYPE_AHEAD/ALTYPAHEAD/PERM TTA2:
during SYSTARTUP_VMS
So the loginout process does not get started.
Then enable the typeahead buffer in the program using a SETCHAR QIOW.
The /ALTYP is to get the bigger typeahead buffer when enabled (if you need this depends on message size from clock).
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-11-2006 02:52 PM
тАО04-11-2006 02:52 PM
Re: TTA2 always busy
To yank the device out of the loop, use the ALLOCATE command in the DCL procedure which starts up your clock reading application like this:
$ Retry: ON WARNING THEN GOTO Retry
$ ALLOCATE TTA2: CLOCK
$
$ SET NOON
$ SET TERMINAL CLOCK/TYPEAHEAD/ALTYPEAHEAD/etc...
$
$ RUN your-clock-reading-program
The warning retry loop will eventually squeeze the ALLOCATE in between login attempts.
Note that because the terminal is allocated with logical name CLOCK, the SET TERMINAL command does not need /PERMANENT, which may reduce the need for privileges. It also means the attribute will be automatically dropped if the program or process terminates abnormally.
You can also write your program to access the device "CLOCK" rather than hardcoding the name TTA2.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-19-2006 09:35 PM
тАО04-19-2006 09:35 PM