Technical data

Programming Features
5.11 New Process Dump Tools (Alpha)
2. Create a protected directory with rights identifier IMGDMP$PROTECT. For
example:
$ CREATE /DIRECTORY DKA300:[PROCDUMPS] -
/PROTECTION=(S:RWE,O:RWE,G,W) /OWNER_UIC=IMGDMP$PROTECT
$ SET SECURITY DKA300:[000000]PROCDUMPS.DIR -
/ACL=((DEFAULT_PROTECTION,SYSTEM:RWED,OWNER:RWED,GROUP:,WORLD:), -
(IDENTIFIER=IMGDMP$PROTECT,ACCESS=READ+WRITE), -
(IDENTIFIER=IMGDMP$PROTECT,OPTIONS=DEFAULT, -
ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL), -
(CREATOR,ACCESS=NONE))
3. Define protected logical name SYS$PROTECTED_PROCDMP to point to the
protected directory. For example:
$ DEFINE /SYSTEM /EXECUTIVE_MODE SYS$PROTECTED_PROCDMP DKA300:[PROCDUMPS]
If DISKQUOTA is to be used on the disk containing the protected directory,
specify the maximum disk space to be used for process dumps. For example:
$ RUN SYS$SYSTEM:SYSMAN
SYSMAN> DISKQUOTA CREATE /DEVICE=DKA300 ! if necessary
SYSMAN> DISKQUOTA ENABLE /DEVICE=DKA300 ! if necessary
SYSMAN> DISKQUOTA ADD IMGDMP$PROTECT /DEVICE=DKA300 /PERMQUOTA=10000
SYSMAN> DISKQUOTA REBUILD /DEVICE=DKA300 ! if necessary
SYSMAN> EXIT
Caution
Do not grant IMGDMP$PROTECT to any user. It is granted and revoked
as needed by SYS$SHARE:IMGDMP.EXE from executive mode while
writing a process dump. If you grant it permanently to a user, that user
has access to all process dumps written to the protected directory.
You can choose to set up additional ACLs on the protected directory to further
control which users are allowed to read and write process dumps there.
Note that to take a process dump when the image is installed with elevated
privileges or belongs to a protected subsystem, the user must hold CMKRNL
privilege, and is by definition a privileged user (see Section 5.11.6.2).
5.12 RMS Locking Enhancements
This section introduces the new Record Management Services (RMS)
enhancements provided in this release.
5.12.1 RMS Locking Performance Enhancements (Alpha)
The following sections describe RMS locking performance enhancements that are
in OpenVMS Alpha Version 7.2-1H1 and in OpenVMS Version 7.3.
5.12.1.1 RMS Global Buffer Read-Mode Locking
In the RMS run-time processing environment, the use of global buffers can
minimize I/O operations for shared files. This release introduces read-mode
bucket locking that minimizes locking for shared access to global buffers. This
new functionality:
• Allows concurrent read access to the global buffers. Accesses are no longer
serialized, waiting to acquire an exclusive lock for a read access.
5–12 Programming Features