- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Phone Utility
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-12-2009 10:36 AM
тАО11-12-2009 10:36 AM
When I enter
$ Phone BAXTERD
I get:-
OpenVMS Phone Facility 12-NOV-2009
%
That person's terminal cannot be used as a telephone.
-------------------------------------------------------------------------------
BUD::SYSDAB
Any idea of the cause, or resolution for this??
Note: BAXTERD is logged in on the same node.
Dave.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-12-2009 11:06 AM
тАО11-12-2009 11:06 AM
Re: Phone Utility
and provide the output?
In V7.3-2 if the terminal is set /nobroadcast
of has used
$ set broadcast=nophone
Then it will display
That person's phone is unplugged (/NOBROADCAST).
But that's a different message than you are reporting.
I just searched sys$system:phone.exe on a 8.3 alpha, using Hein's STRINGS program, and I don't see any strings that match the string. In fact using search doesn't find the string "telephone".
Are you sure you are using the real phone.exe from VMS?
$ sho sym phone ! make sure it isn't doing something funny
$ sho log phone
$ ! if you have the verb utility, verify that phone is using image phone
$ analyze/image/select=(id,build,link) 'f$parse("phone","sys$system:.exe")'
Jon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-12-2009 11:12 AM
тАО11-12-2009 11:12 AM
Re: Phone Utility
http://labs.hoffmanlabs.com/node/1091
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-12-2009 07:09 PM
тАО11-12-2009 07:09 PM
Re: Phone Utility
You get that message when the terminal is not a CRT.
I just tried with SET TERM/LA36 and got that.
On the terminal itself you get
%PHONE-F-BADTERM, you cannot use this type of terminal as a telephone
For me the fix is: $SET TERM/INQ
Cheers,
Hein.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-12-2009 09:03 PM
тАО11-12-2009 09:03 PM
Re: Phone Utility
Give Hein 10 points.
The reason STRINGS and SEARCH didn't find the text is becaue these messages are in the sys$message:cliutlmsg.exe file.
Jon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-13-2009 04:38 AM
тАО11-13-2009 04:38 AM
Re: Phone Utility
Some additional information:
1. Have 4 node cluster, 3 blades sharing 8.3-1H1 system disk, and DS10 using its own system disk. Also have 3 external standalone development blade systems (8.3-1H1).
2. The problem only manifests itself when one (or both) of the communicating systems is/are a production cluster blade. The phone utility is working fine between the standalone systems.
As Hoff will probably remember, we had some issues with networking back in Feb, when we first migrated to blades, and as part of the troubleshooting process we trimmed the DECNet Phase V configuration to the absolute minimum, basically reducing all of the references to a single interface. This primarily affected the net$routing_startup.ncl file, and the net$cmsacd_startup.ncl file.
Once the problem was resolved, we were a bit wary about putting the files back, so they have remained as they were.
I suspect that this is a part, if not all of the problem.
Does this make any sense, or explain anything in the context of the "Phone" issue??
Dave.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-13-2009 06:14 AM
тАО11-13-2009 06:14 AM
Re: Phone Utility
When you do a $ SHOW TERM in the target session, what does it indicate?
When you just launch $ PHONE in the target sesssion without a user to phone, what does it report? Does the phone screen appears, or the message I indicated earlier?
Hein.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-13-2009 06:31 AM
тАО11-13-2009 06:31 AM
Re: Phone Utility
No, and No. :-)
SHOW TERMINAL on the target session on the target host. Is the target session marked as a DECCRT-class terminal? If not, then PHONE won't work.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-13-2009 09:35 AM
тАО11-13-2009 09:35 AM
Re: Phone Utility
In the attachment I have added the information you were asking for.
Basically, between my development machines, Phone is working fine, so I have to assume that the terminal setups on those machines are also fine.
I then matched the production terminal setup to the development machines, (which did require some changes to the DEC_CRT3 and DEC_CRT3 settings), and I get the following results.
When I Phone out from Prod to Dev:
Appears to work OK, i.e. the "
"Attempting to continue after a transmission error..."
When I Phone from Dev to Prod, or from Prod to Prod, I get;
"That person's terminal cannot be used as a telephone."
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-13-2009 09:52 AM
тАО11-13-2009 09:52 AM
Re: Phone Utility
a quick look in the sources indicates: PHONE is looking for TT$M_SCOPE, if that fails, it will issue the 'targterm' message.
If DECnet links are involved, there is a mapping between various status codes to 'universal' codes, this code is more complicated to look at...
Volker.