- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- /DIRECTORY specification when COPYing a UAF record...
Operating System - OpenVMS
1821188
Members
3333
Online
109631
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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-02-2007 10:37 AM
04-02-2007 10:37 AM
Hi,
When I create a new UAF record by the COPY command of the AUTHORIZE utility and I want the new user to have a different default directory, I add the qualifier /DIRECTORY=[].
1) Is it the (implied in this case) /DEVICE qualifier that specifies the disk?
2) Can I specify the full path of that new directory? This new directory will need not be 1 level below the master file directory of the disk but more. I noticed that the DEC manuals give examples without full path of the directories (what if there are more than 1 directories above) ?.
3) In the AUTORIZE utility, if I do SHOW on the user account that I want to COPY I see that the device for the default is a logical name that includes some upper directories (if I translate this logical name). It has the format:
Default: USER_DEVICE:[USER1]
Is that mean that the /DEVICE can be a logical name that includes subdirectories?
4) Is this question true to the other AUTHORIZE commands like MODIFY and ADD?
Thanks for the answers,
Yaron.
When I create a new UAF record by the COPY command of the AUTHORIZE utility and I want the new user to have a different default directory, I add the qualifier /DIRECTORY=[
1) Is it the (implied in this case) /DEVICE qualifier that specifies the disk?
2) Can I specify the full path of that new directory? This new directory will need not be 1 level below the master file directory of the disk but more. I noticed that the DEC manuals give examples without full path of the directories (what if there are more than 1 directories above) ?.
3) In the AUTORIZE utility, if I do SHOW on the user account that I want to COPY I see that the device for the default is a logical name that includes some upper directories (if I translate this logical name). It has the format:
Default: USER_DEVICE:[USER1]
Is that mean that the /DEVICE can be a logical name that includes subdirectories?
4) Is this question true to the other AUTHORIZE commands like MODIFY and ADD?
Thanks for the answers,
Yaron.
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-02-2007 12:39 PM
04-02-2007 12:39 PM
Solution
1) Yes.
2) Yes. Any directory is ok.
3) If AUTHORIZE says:
Default: USER_DEVICE:[USER1]
then the device is "USER_DEVICE:", which may
be a logical name, and the directory is
"[USER1]".
The device part itself may be a logical name,
but if it includes directories, it would, I
believe, need to be a "rooted" logical name,
like SYS$SYSROOT for user SYSTEM:
Default: SYS$SYSROOT:[SYSMGR]
alp $ show logi SYS$SYSROOT
"SYS$SYSROOT" = "ALP$DKA0:[SYS0.]" (LNM$SYSTEM_TABLE)
= "SYS$COMMON:"
1 "SYS$COMMON" = "ALP$DKA0:[SYS0.SYSCOMMON.]" (LNM$SYSTEM_TABLE)
That one's also a two-member search list, but
the important thing here is the trailing dot
in "[SYS0.]" or "[SYS0.SYSCOMMON.]".
(SHOW LOGI /FULL to see all the attributes of
the logical name. Note in particular,
"concealed".)
4) Yes.
2) Yes. Any directory is ok.
3) If AUTHORIZE says:
Default: USER_DEVICE:[USER1]
then the device is "USER_DEVICE:", which may
be a logical name, and the directory is
"[USER1]".
The device part itself may be a logical name,
but if it includes directories, it would, I
believe, need to be a "rooted" logical name,
like SYS$SYSROOT for user SYSTEM:
Default: SYS$SYSROOT:[SYSMGR]
alp $ show logi SYS$SYSROOT
"SYS$SYSROOT" = "ALP$DKA0:[SYS0.]" (LNM$SYSTEM_TABLE)
= "SYS$COMMON:"
1 "SYS$COMMON" = "ALP$DKA0:[SYS0.SYSCOMMON.]" (LNM$SYSTEM_TABLE)
That one's also a two-member search list, but
the important thing here is the trailing dot
in "[SYS0.]" or "[SYS0.SYSCOMMON.]".
(SHOW LOGI /FULL to see all the attributes of
the logical name. Note in particular,
"concealed".)
4) Yes.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP