HP OpenVMS Systems

Ask the Wizard

HP OpenVMS Systems

OpenVMS information

» What's new on our site
» Upcoming events
» Configuration and buying assistance
» Send us your comments

HP OpenVMS systems

» OpenVMS software
» Supported Servers
» OpenVMS virtualization
» OpenVMS solutions and partners
» OpenVMS success stories
» OpenVMS service and support
» OpenVMS resources and information
» OpenVMS documentation
» Education and training

Quick Links

» Non-javascript page
» Ask the Wizard

Test Drive OpenVMS

» OpenVMS I64 test drive
» Java test drive

Other information resources available to you include:

» OpenVMS freeware
» ECO kits, software and hardware support, prior version support
» Alpha SRM, ARC, and AlphaBIOS firmware updates
» ENCOMPASS - HP user group
» OpenVMS software downloads, OpenVMS freeware CD-ROM
» OpenVMS firmware locations
» DECconnect passive adaptor charts
» Cables reference guide
» MicroVAX console commands
» OpenVMS student research

Select a topic below to see Questions Frequently Asked by partners

» Using the online documentation library(installing BNU from the asap SDK)
» Global sections(how to create and use.)
» xx$CREATE_BUFOBJ system service(usage)
» Ethernet address(methods of determination)
» Shareable images(cookbook approach to creating one)
» Sharing data/code at absolute addresses(a guide with examples)
» Determining the Alpha microprocessor
» Using GETSYI to get hardware status

Evolving business value

» Business Systems Evolution
» AlphaServer systems transition planning
» Alpha RetainTrust program

Related links

» HP Integrity servers
» HP Alpha systems
» HP storage
» HP software
» HP products and services
» HP solutions
» HP support
disaster proof
HP Integrity server animation
HP Integrity server animation
Content starts here

Ask the Wizard Questions

how to force 'd' protection on directories?

The Question is:

Dear wizard,
 is there a way to force the 'd' protection on created
 directories by default, without using the switch
/prot=o:Rewd ?

The Answer is:

      In a word, no. The removal of Delete access is hard coded into the
    CREATE/DIRECTORY code. The protection placed on a newly created
    directory follows normal RMS inheritance and default rules, except that
    the D bits are cleared from the final SOGW mask. This intentional and
    documented behaviour - see RTL Library LIB$ Reference manual for
    routine LIB$CREATE_DIR, "protection-enable" parameter. This dates from
    VMS V1.0 prior to the introduction of the "DIRECTORY bit" in V2 which is
    now used by the XQP to force a check that a directory is empty before
    deletion. In VMS V1.0 this was the only  protection against accidently
    deleting a directory file and "orphaning" any files contained within
    it. Although there is now a more reliable mechanism to prevent
    accidental deletion, the original behaviour is  retained for
    compatibility reasons.

      If your intention is to ensure that the owner of a directory has
    delete access, you can place an ACE in the ACL of the parent directory
    explicitly granting Delete access. All directories created within will
    inherit the ACE (which will also propagate downwards). For example:

    $ SET SECURITY/DEFAULT [...]*.DIR	! propagate to existing directories

    Directory DISK$USER1:[GILLINGS]

    X.DIR;1              [USERS,GILLINGS]      (RWE,RWE,RE,E)


    This must be done for each user's directory tree, since the identifier
    must be the same as the owner.