- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Login error
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-29-2009 02:09 AM
тАО06-29-2009 02:09 AM
Login error
%DCL-E-OPENIN, error opening DISK$APPLICATIONS:[RS1R4]RS1LOG.COM; as input
-RMS-F-DEV, error in device name or inappropriate device type for operation
$ dir
%DIRECT-E-OPENIN, error opening ALPHA$DKA0:[UTILITIES]*.*;* as input
-RMS-F-DEV, error in device name or inappropriate device type for operation
Could anybody help?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-29-2009 03:07 AM
тАО06-29-2009 03:07 AM
Re: Login error
Apparently the (I assume) logical names DISK$APPLICATIONS and ALPHA$DKA0 do not point to valid devices (disk1) for the system.
Check the various DCL procedures (like SYLOGICALS, SYSTARTUP_VMS, SYLOGIN et alia) for those definitions and check your system for the actual devices.
Regards,
Kris (aka Qkcl)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-29-2009 03:37 AM
тАО06-29-2009 03:37 AM
Re: Login error
Has this worked before? If YES, what has been changed?
Without any more pertinent info, my first guess is that the defining of DISK$APPLICATIONS as ALPHA$DKA0:[UTILITIES] is invalid.
The syntax DISK$APPLICATIONS:[RS1R4] implies that DISK$APPLICATIONS should be a Concealed Device.
That definition then has to be
ALPHA$DKA0:[UTILITIES . ] /TRANS=CONCEAL
( the spaces around the dot in the syntax are for readability, they should NOT be in the definition!
-- only a first guess, without actual code it will be difficult to be sure.
hth
Proost.
Have one on me.
jpe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-29-2009 05:39 AM
тАО06-29-2009 05:39 AM
Re: Login error
Background research is appropriate here. DISK$APPLICATIONS is most likely a logical name. It may be defined at a number of levels, including: cluster-wide, system-wide, group-wide, job-wide, or process-wide.
To determine precisely what is happening, start by checking the file executed when a user logs in. Generally, this is LOGIN.COM in their directory, but the actual file is controlled by their entry in the system authorization file. There is also a system wide login profile, generally located in SYS$MANAGER:SYLOGIN.COM, but this can be re-directed by a system-wide logical name.
Logical names can be created at other times, notably at system startup. That will require tracing the flow of what happens when the system is started. Before doing that, looking carefully at the system and various group logical name tables is advised.
Also, is this problem limited to a single account, or is it occurring on a number of accounts.
Reading background like the Programming Concepts manuals, and my series of articles on logical names on OpenVMS.org is also advised.
- Bob Gezelter, http://www.rlgsc.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-30-2009 02:58 AM
тАО06-30-2009 02:58 AM
Re: Login error
It may also be something pointed to by the LGICMD parameter that's set in your entry in the SYSUAF.
Does DISK$APPLICATIONS exist?
Is that DKA0:
Is the allocation class set to zero (hence ALPHA$DKA0:)?
Steve