- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: OpenVMS bug with duplicate process names?
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
тАО06-14-2018 10:48 PM
тАО06-14-2018 10:48 PM
OpenVMS bug with duplicate process names?
One of our recent 2nd-line hires asked me why he was getting a couple of errors when he logged in.
The first was:
%SET-E-NOTSET, error modifying process name
-SYSTEM-F-DUPLNAM, duplicate name
The second was:
So, I tested to see what happened - first login (with no attendant SET PROCESS /NAME in any login procedure) causes the process name to be set to the username,
That set me thinking...
In one session I logged on with terminal RTA4:
The only thing I can think of is that attempts to reference a process by name would likely get the process with the lower IPID, so you could end up monitoring/killing the wrong process; I'm not sure whether or not internally it might cause issues for OpenVMS (or some layered products)???
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-15-2018 12:02 AM
тАО06-15-2018 12:02 AM
Re: OpenVMS bug with duplicate process names?
Mark,
FWIW, on OpenVMS Alpha V8.3 LOGINOUT assigns an empty process name ("") to such a process, if the default process name (_ccann:) already exists, so the behaviour of LOGINOUT seems to have changed.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-15-2018 12:29 AM
тАО06-15-2018 12:29 AM
Re: OpenVMS bug with duplicate process names?
Hmm, what changed when and where ?
$ sh sys/full/noproc OpenVMS V8.4-2L2 on node EISNER 15-JUN-2018 03:25:18.96 Uptime 63 08:59:12 AlphaServer DS20 500 MHz $ pipe show sys|search sys$pipe rta 0002620D _RTA1: LEF 5 1215 0 00:00:00.19 850 86 00031215 _RTA2: LEF 4 323 0 00:00:00.18 647 84 00030A18 _RTA2: LEF 4 339 0 00:00:00.11 520 103 $
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-15-2018 01:03 AM
тАО06-15-2018 01:03 AM
Re: OpenVMS bug with duplicate process names?
CHAALP $ sho us/node/full system/int
OpenVMS User Processes at 15-JUN-2018 09:58:35.02
Total number of users = 1, number of processes = 3
Username Process Name PID Terminal
SYSTEM 000044BA VTA83: TNA84:
SYSTEM SYSTEM 000044B0 VTA80: TNA81:
SYSTEM _VTA83: 000044B7 VTA81: TNA82:
CHAALP $ sho sys
OpenVMS V8.3 on node CHAALP 15-JUN-2018 09:58:24.33 Uptime 372 22:21:07
Pid Process Name State Pri I/O CPU Page flts Pages
000044B0 SYSTEM LEF 4 281 0 00:00:00.49 312 122
000044B7 _VTA83: LEF 4 191 0 00:00:00.62 442 117
000044BA CUR 4 204 0 00:00:00.62 400 185
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-15-2018 02:19 AM
тАО06-15-2018 02:19 AM
Re: OpenVMS bug with duplicate process names?
More hmmmm, either LOGINOUT changed again or it isn't LOGINOUT. And, would "your" LOGINOUT assign another empty process name if the default process name already exists? Anyway, it seems that on current versions of VMS the system can end up with two (or more) identical process names.
$ sh sys/noproc/full OpenVMS V8.4-2L2 on node EISNER 15-JUN-2018 05:03:45.64 Uptime 63 10:37:38 AlphaServer DS20 500 MHz $ pipe sh sys |search sys$pipe _VTA323 00031031 _VTA3230: LEF 4 411 0 00:00:00.22 858 63 00031445 _VTA3230: LEF 4 563 0 00:00:00.19 693 91 $
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-15-2018 03:30 PM
тАО06-15-2018 03:30 PM
Re: OpenVMS bug with duplicate process names?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-16-2018 05:23 AM
тАО06-16-2018 05:23 AM
Re: OpenVMS bug with duplicate process names?
Are you sure that the process names are exactly equivalent? I would look for invisible characters (spaces). The space is a significant character unseen in a name display.
Dan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-16-2018 05:57 AM
тАО06-16-2018 05:57 AM
Re: OpenVMS bug with duplicate process names?
Did you look? How?
$ pipe sh sys |search sys$pipe "_VTA3417:" 00031E30 _VTA3417: LEF 8 640 0 00:00:00.56 996 166 00030634 _VTA3417: LEF 5 815 0 00:00:00.16 616 111 $ write sys$output "<"+f$getjpi("00031E30","prcnam")+">" <_VTA3417:> $ write sys$output "<"+f$getjpi("00030634","prcnam")+">" <_VTA3417:> $
Do you suspect that $getjpi trims/suppresses invisible characters?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-19-2018 01:21 PM
тАО06-19-2018 01:21 PM
Re: OpenVMS bug with duplicate process names?
Thanks to all who replied; following on from Volker & Hartmut's posts, I considered briefly that it might be an artefact of the terminal driver, so that perhaps the VT driver had been updated but the RT one had not; then I came to my senses and thought it wouldn't make programmatic sense for the process name to be set by the terminal driver.
Chris - your point about UIC changing - yes, very valid - I hadn't even considered it, though in this particular case, checking for duplication at process creation is something that could be done, and arguably should be done.
Dan - re the process names having additional spaces (and which might have been a means by which differentiation between processes could have been made)- I hadn't considered that, but Hartmut's post suggests that that's not the case.
It's not something that we (or, I suspect) most folks are likely to encounter in the real world, so I'm not going to worry too much about it - it's just an oddity that I encountered when positing a "what if..." and wanted to make sure I wasn't going nuts.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-19-2018 04:57 PM
тАО06-19-2018 04:57 PM
Re: OpenVMS bug with duplicate process names?
FWIW, I have seen process names that appear to be the same with trailing spaces. While using the F$getjpi service as shown earlier will show trailing spaces in the count, the original posting did not use that to show the process names. With the standard services (show system for example), the trailing spaces will not be seen and thus could be the difference in process names.
Dan