The following is additional information about DSM documentation and functionality that is not included in the DSM for OpenVMS Release Notes
This section contains notes about and corrections to the DSM documentation set.
The DSM for OpenVMS Programmer's Manual left out the description of the %SETUCI utility. The following is the missing description of this utility:
Changes your default UCI and volume set. If you omit the flag argument, then DSM changes the UCI and volume set for both globals and routines. If you do not specify the volume set name (VOL), DSM uses volume set 0.
You can control access to this external routine by enabling configuration access control using the ^CONFIG utility.
Format:
SET X=$&ZLIB.%SETUCI(UCI,{VOL},{flag})
where UCI is the New UCI name, VOL is the new volume set name, and flag can be either:
Chapter 9 of the DSM for OpenVMS Database Operations Guide contains a typographical error. Please replace every occurrence of the word "rambles" in Chapter 9 with the word "re-enables."
This section contains notes about DSM technical changes.
DSM for OpenVMS has implemented the following behavior for handling year dates:
DSM will interpret that all year dates entered as two-digit numeric values refer to a year within the century in which the value is entered. For example, when you enter a year date of "99" before Dec 31, 1999 at 11:59:59 PM, DSM will interpret that year date as 1999. When you enter a year date of "99" after Dec 31, 1999 at 11:59:59 PM, DSM will interpret that year date as 2099.
The $HOROLOG special variable, however, will continue to keep the correct absolute date.
A partial remedy of the BIJ file overflow issue was included in Version 6.6 of DSM for OpenVMS. Version 6.6A of DSM for OpenVMS includes a more complete solution to the problem (documented as ECO 5 in ECO Descriptions) that greatly decreases the likelihood of BIJ file overflow. This solution does not preclude the environmental system manager's responsibility to design the BIJ file properly, according to the information previously published about sizing files.
To resolve the issue documented as ECO 6 in ECO Descriptions, security auditing now allows users to disable auditing for non-journaled globals. To do so, run ^CONFIG and answer the following prompts:
Modify security audit name definition [Y or N] ? <N> Y <Return>
. . .
Disable security auditing for non-journaled globals [Y or N] ? Y <Return>
In an attempt to prevent DSM environment managers from dismounting a database set while that set is being dejournaled, Version 6.6 of DSM for OpenVMS inadvertently removed the ability of running concurrent processes to dejournal separate volume sets (as documented in ECO 7 in ECO Descriptions). This condition has been corrected in Version 6.6A. Dejournaling to separate volume sets can once again run concurrently.
The ability to mount and dismount database sets has given DSM environment managers greater flexibility over the maintenance of their DSM configurations. Along with that flexibility comes the responsibility to:
For example, attempts to dismount a database set while it is being dejournaled will bring about unexpected results.
For backwards compatibility, the $ZV special variable again reports the string "VAX DSM." (See ECO 15 in ECO Descriptions for an explanation of the original issue.)
The following describes DSM ECOs for DSM Version 6.6A-020.
If a multiple-volume-set TP set is mounted in non-contiguous slots (for example: S2 and S4), the AIJ control for the volume sets after the "gap" is not correctly associated with the preceding TP volume set.
The recovery process can loop in HIB status in the event of cluster state transition due to another node going down, while the database set is dismounted. This only occurs when the database set has been dismounted from the master node and the node attempting to perform a recovery is not capable of being master
If you use a global reference with a $D value of 10 as the first argument of $GET and you supply a second argument, $GET always ignores the second argument and returns a null. Consider the following:
> K ABC S ABC("TEST")="TEST" W $G(ABC,1) <Return>
1
>K ^ABC S ^ABC("TEST")="TEST" W $G(^ABC,1) <Return>
If you issue the following command with a reference to a volume set in a different DSM environment, you receive a DSM-E-NOSUCHVOLSET error, even though you can see the global with ^%G and $D (that is, the DDP connection to the volume set is working properly).
W $ZS(^["UCI","VOL"]GLOBAL)
A possible BIJ FULL error may occur if a volume set has a large number of blocks allocated for globals. The routine used to search the global directory for top-level deletions, creations, and modifications would perform before-image journaling on each of the blocks it scanned while searching for the block that contained the global's data. DSM for OpenVMS Version 6.6 logs an error to DSMCRASH.LOG indicating the BIJ file overflow.
Go to BIJ File Overflow
Security auditing cannot be turned off for non-journaled globals.
Go to Security Auditing for Non-Journaled Globals
Starting with Version 6.6 of DSM for OpenVMS, you can no longer run concurrent processes to dejournal.
Go to Running Concurrent Dejournal Processes
If a "user open call" routine is defined, an inadvertent attempt to close a previously-closed journal file may hang the process.
You may get a GDT allocation error because of corruption in the free memory chain when smaller-sized segments are allocated from an existing larger segment; for example: if a volume set containing x number of globals is dismounted and another volume set with x-n globals is mounted in the same slot.
%ERRCHK fails to report a warning for using SET $FIND and SET $EXTRACT as described in the following extract from the help text.
The ^%ERRCHK Utility has been modified to detect occurrences of SET $EXTRACT and SET $FIND in your application. The utility prints a warning for each SET $EXTRACT occurrence when the /EXTENSION=SETFUNCTION is in force. However, it always prints a warning for each occurrence of SET $FIND.
Modifying the "ALTERNATE" field in the database description for mounting using an alternate name does not work.
A user can get an <UNDEF> error when accessing the top-level node of a global immediately after creating the global.
> K ^X S ^X(1)=0,^X=9,^Y(0)=9 S ^Y(0)=^Y(0)_^X <Return>
%DSM-E-UNDER, undefined variable ^X
With a multi-volume transaction-processing database set, you can experience a process hang when writing to the AIJ file. The problem is caused when the TP monitor, DSM_JRNL, attempts to write to the AIJ for a non-base TP volume set (any volume set that is not first) from the timer AST routine.
DSM reports an erroneous DDP error message when dismounting a database set.
The $ZV special variable no longer reports "VAX DSM."
Go to $ZV Special Variable Value
If you try to display the current line of a % routine being executed in a non "MGR" UCI, from any non "MGR" UCI, it fails with "(cannot display routine line - source is unavailable)".
Under certain conditions, a process may go into a COM 0 state while running ^%JOB on another process. For example, suppose ^%JOB is run for a process that defined a large symbol by a process that has not defined a symbol table of the same size or larger. If the process running ^%JOB tries to load the symbol table of the first process, that process goes into a COM 0 state.
Under OpenVMS Alpha V6.2 only: The %BASEDIT Ecall subfunction 32 (convert lower to uppercase) does not work correctly for certain German characters.
Errors occur in the ^CONTR utility in the following situations:
In prior versions of DSM, TP database sets could not be mounted as read-only.