Technical data

System Management Features
4.4 Dedicated CPU Lock Manager (Alpha)
• You can eliminate the first available nonprimary CPU as an available Fast
Path CPU. To do so, clear the bit associated with the CPU ID from the IO_
PREFER_CPUS system parameter.
For example, let’s say your system has eight CPUs with CPU IDs from zero
to seven and four SCSI adapters that will use Fast Path. Clearing bit 1 from
IO_PREFER_CPUs would result in the four SCSI devices being bound to
CPUs 2, 3, 4, and 5. CPU 1, which is the default CPU the lock manager will
use, will not have any Fast Path devices.
• You can set the LCKMGR_CPUID system parameter to tell the LCKMGR_
SERVER process to use a CPU other than the default. For the above example,
setting this system parameter to 7 would result in the LCKMGR_SERVER
process running on CPU 7. The Fast Path devices would by default be bound
to CPUs 1, 2, 3, and 4.
4.4.5 Using the Dedicated CPU Lock Manager on the AlphaServer GS Series
Systems
The new AlphaServer GS Series Systems (GS80, GS160, and the GS320) have
NUMA memory characteristics. When using the Dedicated CPU Lock Manager
on one of these systems, the best performance is obtained by utilizing a CPU and
memory from within a single Quad Building Block (QBB).
For OpenVMS Version 7.3, the Dedicated CPU Lock Manager does not yet have
the ability to decide from where QBB memory should be allocated. However,
there is a method to preallocate lock manager memory from the low QBB. This
can be done with the LOCKIDTBL system parameter. This system parameter
indicates the initial size of the Lock ID Table, along with the initial amount of
memory to preallocate for lock manager data structures.
To preallocate the proper amount of memory, this system parameter should be
set to the highest number of locks plus resources on the system. The command
MONITOR LOCK can provide this information. If MONITOR indicates the
system has 100,000 locks and 50,000 resources, then setting LOCKIDTBL to the
sum of these two values will ensure that enough memory is initially allocated.
Adding in some additional overhead may also be beneficial. Setting LOCKIDTBL
to 200,000 thus might be appropriate.
If necessary, use the LCKMGR_CPUID system parameter to ensure that the
LCKMGR_SERVER runs on a CPU in the low QBB.
4.5 OpenVMS Enterprise Directory for e-Business (Alpha)
1
OpenVMS Enterprise Directory for e-Business is a massively scalable directory
service, providing both X.500 and LDAPv3 services on OpenVMS Alpha with no
separate license fee. OpenVMS Enterprise Directory for e-Business provides the
following:
• Large percentage of the Fortune 500 already deploy Compaq X.500 Directory
Service (the forerunner of OpenVMS Enterprise Directory for e-Business)
• World’s first 64-bit directory service
• Seamlessly combines the scalability and distribution features of X.500 with
the popularity and interoperability offered by LDAPv3
1
On OpenVMS VAX a similar service, but without LDAP support and with more limited
performance, is still available with Compaq X.500 Directory Service Version 3.1.
4–6 System Management Features