- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Since the system had to be restarted...
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
тАО08-09-2005 06:39 AM
тАО08-09-2005 06:39 AM
So, here is my question. There are some system lables and logicals that are defined during the login.com, but there seems to be other system-wide .COM files that also define lables and logicals that the user's login.com takes advantage. For instance, in the user's login.com file there is a line that says something to the effect:
BRIEF_COMMAND :== @DEV$EXEC:SOME_DOT_COM
and if the user types
BRIEF_COMMAND
at the command line, the error is something to the effect:
%DCL-E-OPENIN, error opening DEV$EXE:[OURUSER]SOME_DOT_COM.COM; as input
-RMS-F-DEV, error in device name or inappropriate device type for operation
Now, I did some research and I fould out that SOME_DOT_COM.COM is located in SYS$SYSDEVICE:[SPECIAL.DEVELOPMENT].
WHAT system-wide file or system-wide setting needs to be changed and what system utility do I need to run to make this happen?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-09-2005 06:53 AM
тАО08-09-2005 06:53 AM
Re: Since the system had to be restarted...
Common login items are usually set up in SYS$MANAGER:SYLOGIN.COM
It appears that DEV$EXEC is not a "rooted logical" from the error message you posted, or something to that effect.
Please be precise.
Approximate information will result in approximate answers.
WWWebb
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-09-2005 08:10 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-09-2005 06:37 PM
тАО08-09-2005 06:37 PM
Re: Since the system had to be restarted...
These will give you SYSTEM and GROUP logicals.
Mind: It is by no means obligatory to use the supplied procedures. A system manager can decide to leave these untouched and execute his own! (even re-do the whole startup....)
Next investigation is checking SYLOGIN, look again for procedures that set up logicals and look for these. Also take a look at user's LOGIN.COM, doing the same. This search id for PROCESS and JOB logicals.
Beware that, in most cases, a logical is searched scanning tabels in sequence as defined in table LNM$PROCESS_DIRECTORY; normally it will be PROCESS - JOB - GROUP - SYSTEM but others may have been put in there (You can tell by $ SHOW LOGICAL/TABLE=LNM$PROCESS_DIRECTORY). The first match encountered will be used.
In your case, it might be that there are different definitions of DEV$EXE:. Given the statement, I expect this would have the CONCEALED attribute at least.
OpenVMS Developer & System Manager
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-09-2005 07:26 PM
тАО08-09-2005 07:26 PM
Re: Since the system had to be restarted...
>>>
(You can tell by $ SHOW LOGICAL/TABLE=LNM$PROCESS_DIRECTORY).
<<<
AFAIK, you get the tables that are searched by $ SHOW LOGICAL LNM$FILE_DEV /TABLE=*
cu,
Martin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-09-2005 08:21 PM
тАО08-09-2005 08:21 PM
Re: Since the system had to be restarted...
it appear as a mismatch between dev$exec and dev$exe.
So you must create a logical name dev$exec like follow command
$ DEF/SYSTEM DEV$EXEC -
SYS$SYSDEVICE:[SPECIAL.DEVELOPMENT]
in SYLOGICALS.COM
or if DEV$EXE is valid you have to change SYLOGIN.COM; to check for dev$exe you can type
$ @DEV$EXE:SOME_DOT_COM
Antonio Vigliotti
P.S.
Bill, may I hint you assign some point? Just for thanking vms guys here :-)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-10-2005 07:19 AM
тАО08-10-2005 07:19 AM
Re: Since the system had to be restarted...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-10-2005 07:29 AM
тАО08-10-2005 07:29 AM
Re: Since the system had to be restarted...
I tried this one this morning ;-) But you're right.
@Doug:
That's also true. A common error (as I found out myself very recently)
So Bill, check ALL procedures that are used in the startup sequence, that they have either SET NOON whereever something MIGHT go wrong, or take appropiate action (that is: have a decent error handling) so startup will finish normally. Same, by the way, applies to LOGIN procedures.
OpenVMS Developer & System Manager
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-10-2005 03:48 PM
тАО08-10-2005 03:48 PM
Re: Since the system had to be restarted...
What helped the most was finding a system that was simular. Although it was not an OpenVMS, it was useful to do a side-by-side comparison and to look at OpenVMS online documentaion and your suggestions to see what line of code needed to be added to the SYS$MANAGER:SYSTARTUP_VMS.COM file.