Open M
DSM for OpenVMS Version 7.3 MUP3 (Maintenance Update 3)
Dear DSM for OpenVMS
Customer :
Enclosed is your DSM for
OpenVMS kit. Version 7.3 MUP3 (Maintenance Update 3) of DSM for OpenVMS is
compatible with DSM applications written under previous versions of DSM for
OpenVMS.
Information regarding
current DSM releases is available on the InterSystems Web site. We strongly
recommend that you visit the Web site
(http://mtechnology.intersys.com/mproducts/dsm7) for additional information,
including release notes & cover letters.
_____________________________________________________________________________________
You need to be using... To
install and run…
_____________________________________________________________________________________
OpenVMS VAX Versions 6.2,
7.0, 7.1, 7.2 or 7.3 V7.3 MUP3 of DSM for OpenVMS VAX
OpenVMS Alpha Versions
6.2, 7.0, 7.1, 7.2, 7.2-1, V7.3
MUP3 of DSM for OpenVMS Alpha
7.2-2, 7.3, 7.3-1 or
7.3-2
_____________________________________________________________________________________
For additional
information regarding the coexistence of different versions of DSM/OpenVMS, a
compatibility chart is available at:
http://mtechnology.intersys.com/support/faqs/vmstable.html
You should keep the
following points in mind:
·
Because
of certain internal changes, you will need to recompile all of your DSM
routines after you upgrade to DSM V7.3 MUP3 from any release of DSM prior to
DSM V7.3. If you are upgrading from DSM
V7.3, DSM V7.3 MUP1 or DSM v7.3 MUP2 to DSM V7.3 MUP3, then you do not need to
recompile your DSM routines.
·
If
you are upgrading from any previous release of DSM, you must upgrade
your existing volume sets.
·
No additional new
documentation has been produced for DSM V7.3 MUP3, other than this cover
letter.
·
You will need to
have a valid license from InterSystems Corporation in order to run DSM 7.3 MUP3
in a production environment.
Additional information on licensing can be obtained from the main
InterSystem’s order processing dept at the following address or via your local
InterSystems office.
InterSystems Corporation
Order Processing Group
One Memorial Drive
Cambridge MA 02142
United States
Tel. (617)577-3600 Fax:(617)494-1631
E-mail : orderproc@intersys.com
This document describes
the distribution kits for the following software:
·
Version 7.3 MUP3 of
DSM for OpenVMS VAX[TM]
·
Version 7.3 MUP3 of
DSM for OpenVMS Alpha[TM]
Distribution
DSM is distributed by
InterSystems Corporation on the following media:
·
CD-ROM
The kit can also be
distributed on other media upon special request to InterSystems’s order
processing dept.
If you are installing
DSM software for the first time, read Chapter 1 of the DSM for OpenVMS
Installation and Management Guide. This
chapter describes the installation procedure in detail.
If you are upgrading
from a previous release of DSM, you must upgrade your volume sets. After you
complete your software installation, the upgrade procedure loads Version 7.3 MUP3
manager utilities and globals.
A copy of the DSM for
OpenVMS Release Notes is distributed in printed form and on line as a file with
the DSM distribution kit. Release notes
are also available from the InterSystems web site as previously mentioned.
You can obtain a copy of
these release notes when you install DSM by using the "OPTIONS N"
parameter with the VMSINSTAL procedure.
For example:
$ @SYS$UPDATE:VMSINSTAL DSMVAX073 kit_path: OPTIONS N
or
$ @SYS$UPDATE:VMSINSTAL DSMAXP073 kit_path: OPTIONS N
The release notes can be
obtained in SYS$HELP during the DSM installation or extracted directly from the
.B DSM saveset.
Thank you for purchasing
DSM for OpenVMS.
The DSM Product Group
The following sections
contain information about installing the DSM kit.
If you are installing
DSM software for the first time, read Chapter 1 of the DSM for OpenVMS Installation and Management Guide. That chapter describes the installation
procedure in detail.
Take the following steps
to install the DSM Version 7.3 MUP3 kit:
1.
Back up your
system.
2.
Install the kit.
Run the SYS$UPDATE:VMSINSTAL procedure. On an OpenVMS VAX system, specify DSMVAX073
as the product name. On an OpenVMS
Alpha system, specify DSMAXP073 as the product name.
3.
If you do not run
the IVP during VMSINSTAL, install the DSM for OpenVMS images as shared using
the SYS$STARTUP:DSM$INSTALL.COM procedure.
Post-Installation Activities:
After Installing, take
the following steps:
1.
Use the
SYS$MANAGER:DSM$INIT.COM procedure to create a DSM for OpenVMS environment
manager's account.
2.
Edit the OpenVMS
system files to provide for automatic startup and shutdown of DSM for OpenVMS
configurations when your system is rebooted.
3.
Log into the DSM
for OpenVMS environment manager's account and run the
SYS$MANAGER:DSM$CONFIGURE.COM procedure to initialize DSM for OpenVMS database
volume sets and configurations.
If you are upgrading
from a previous release of DSM you must upgrade your existing volume sets. Read the DSM for OpenVMS V7.3 Release Notes,
in addition to the following information.
Take the following steps
to upgrade from a previous version of DSM to DSM for OpenVMS Version 7.3 MUP3:
1.
Shut down all
running DSM for OpenVMS configurations.
2.
Back up your
system.
3.
Install the kit.
Run the SYS$UPDATE:VMSINSTAL procedure. On an OpenVMS VAX system, specify
DSMVAX073 as the product name. On an
OpenVMS Alpha system, specify DSMAXP073 as the product name.
4.
If you did not run
the IVP (Installation Verification Procedure) during the VMSINSTAL and have not
already successfully reinstalled your DSM images, then install the new DSM
images using the SYS$STARTUP:DSM$INSTALL.COM procedure.
Post-Installation Activities:
1.
You should reboot
your OpenVMS system if any of the following conditions apply:
2.
If necessary, use
the SYS$MANAGER:DSM$INIT.COM procedure from a privileged OpenVMS system account
to upgrade DSM for OpenVMS manager accounts to DSM for OpenVMS Version 7.3 MUP3
environment manager accounts.
3.
If you have
user-written external routine packages, upgrade the external call package table
image to include those packages.
4.
Log in to the DSM
for OpenVMS environment manager's account and run the
SYS$MANAGER:DSM$UPGRADE.COM procedure. You must recompile your application
routines if upgrading from any version prior to DSM V7.3. DSM$UPGRADE optionally reinitializes
before-image and after-image journal files and optionally upgrades mapped
routine sets. You can also use ^BIJINIT, ^JRNINIT, and ^RMBLD to reinitialize
your journal files and rebuild your mapped routines at a later time if
required.
5.
If you have not
already previously done so, edit the OpenVMS system files to provide for automatic
startup and shutdown of DSM for OpenVMS configurations when your system is
rebooted.
6.
Start up the
upgraded configurations.
If you are installing
DSM in an alternate root, read Appendix A of the DSM Installation and Management Guide. It describes the alternate
root installation in detail.
Do the following to
install the DSM Version 7.3 MUP3 kit:
1.
Log in to the
system account.
2.
Shut down all
running DSM configurations. In a VMScluster environment, shut down configurations
running on each node.
3.
Extract the
DSM$ALTROOT_INSTALL.COM procedure from the kit saveset.
On an OpenVMS VAX system, use the following command:
$ BACKUP/LOG kit_path:DSMVAX073.B/SAVE/SELECT=DSM$ALTROOT_INSTALL.COM; *
On an OpenVMS Alpha system, use the following command:
$ BACKUP/LOG kit_path:DSMAXP073.B/SAVE/SELECT=DSM$ALTROOT_INSTALL.COM; *
Where kit_path is the directory
name where the DSM distribution kit is located preceded by the machine name, if
necessary.
4.
Use the
DSM$ALTROOT_INSTALL.COM procedure to create the alternate root directories and
install the DSM software distribution kit.
5.
Use the
DSM$ALTROOT.COM procedure to create and initialize a DSM environment manager's
account for the new alternate root.
6.
Use the
DSM$ALTROOT.COM procedure to initialize the group logical name search lists for
all users within the GROUP.
7.
Log in to the new
manager account and use the SYS$MANAGER:DSM$CONFIGURE.COM procedure to create
volume sets and to define new configurations.
8.
Edit system startup
files to initialize alternate root installation on system reboot.
Attachment B – Additional Product Information
1. ^%GLCHK routine included in DSM distribution
kit.
A DSM routine called ^%GLCHK is included within the DSM V7.3 MUP3 kit (originally included with the DSM V7.3 MUP1 kit). This routine was produced by a DSM customer to assist them in the detection of a particular rare type of corruption that had occurred within one of their global subscripts. The corruption would cause the DSM MERGE operation to hang when used against the corrupted global. The particular type of corruption involved will not be detected by either the ^IC or ^FASTIC utilities. As a service to the DSM customer base, the ^%GLCHK routine has now been included as a standard DSM library routine.
The ^%GLCHK routine is implemented to identify the global data node with subscript encoding corruption.
It uses the $ZO function to scan through an entire global. When the returned next global node is the same as the current one (a global subscript corruption has been located), the global reference string will be reported to the user and appropriate action can then be taken.
The routine can be called from one of the following two entries points:
1. Interactive
^%GLCHK entry (D ^%GLCHK)
This entry allows the user to select a volume set and UCI to begin the search from a specified global reference node.
For example:
>D ^%GLCHK
Enter volume set name > DEF
Enter UCI name > MGR
Global > ^TEST(100)
Checking from node:
^["MGR","DEF"]TEST(100)
Progress to:
^["MGR","DEF"]TEST(1100)
Progress to:
^["MGR","DEF"]TEST(2100)
Progress to:
^["MGR","DEF"]TEST(3100)
Progress to:
^["MGR","DEF"]TEST(4100)
59029,32913
^%GLCHK job successfully completed.
2. Running
^%GLCHK as a background process (D JOB^%GLCHK)
This entry allows the user to start up a job in the background for global node corruption detection.
Before calling this entry, you must reference the global node that you want to begin the search against.
For example:
>I $D(^["MGR","DEF"]TEST(100))
>D JOB^%GLCHK
^%GLCHK job startup executing ...
^%GLCHK job startup log file is:
$1$DUA5:[DSMMGR.MUMPS]DSM_GLCHK.LOG
The created log file can be examined after the process terminates as shown below:
$ TY $1$DUA5:[DSMMGR.MUMPS]DSM_GLCHK.LOG
Checking from node:
^["MGR","DEF"]TEST(100)
59029,33746
^%GLCHK job successfully completed.
%DSM-I-HALT, HALT command executed
2. ^%PCNT routine included in DSM distribution
kit.
In order to assist sites in tracking their DSM process count and license usage over periods of time, a new DSM routine called ^%PCNT is included as standard starting with the DSM V7.3 MUP2 kit. It is designed to run in the background as a jobbed process. The information gathered is intended for export to a comma delimited flat file for analysis with another tool such as a spreadsheet. The information is collected at an interval specified when the utility is jobbed off.
The information is collected in the ^PCOUNT global which will grow at a maximum rate of 1 DSM data block for each 12 collection periods.
Customers requested several enhancements to this routine after release of MUP2. The changes are included as documented below:
START^%PCNT(hang,collections)
To be called to job off a background process to collect
license usage statistics. This entry
point will exit if a collection is already running.
hang - interval in seconds between collections
collections – optional. An optional number of collections before automatically terminating collection.
For example:
>D START^%PCNT(60)
Will create a background process which will log process count and license usage info every minute.
SILENT^%PCNT(hang,collections)
To be called to start new collection with no interaction. Automatically stops currently running collection before starting.
hang – interval in seconds between collections.
collections – optional. An optional number of collections before automatically terminating collection.
STOP^%PCNT
EXPORT^%PCNT(file-name)
To be called to export most recent collection.
file-name – File to receive statistics
For example:
>D
EXPORT^%PCNT("DATA_09-FEB-2004.DAT")
>H
%DSM-I-HALT,
HALT command executed
$
TYPE DATA_09-FEB-2004.DAT
Env,Node,Date,Slot,Total
Jobs,System Jobs,Non-System Jobs,Non-System with Non-Nu
ll
Device,Inactive Non-System,Avail Lic Slots,System Jobs,Programmer Jobs,Applic
ation
Jobs,Improperly Exited,Call Interface,Tied Jobs,Total Jobs,Max Jobs,DDP No
de,Checksum,Interval
DSMMGR,NODE12,4/8/04,6893","0","0","0","0","0","119","7","1","1","0","0","0","
9","128","MIE","52684","10"
DSMMGR,NODE12,4/8/04,6894","9","7","2","1","1","126","7","1","1","0","0","0","
9","128","MIE","1","10"
DSMMGR,NODE12,4/8/04,6895","9","7","2","1","0","126","7","1","1","0","0","0","
9","128","MIE","17107","10"
DSMMGR,NODE12,4/8/04,6896","9","7","2","1","0","126","7","1","1","0","0","0","
9","128","MIE","33193","10"
DSMMGR,NODE12,4/8/04,6897","9","7","2","1","0","126","7","1","1","0","0","0","
9","128","MIE","16773","10"
DSMMGR,NODE12,4/8/04,6898","10","7","3","2","0","125","7","2","1","0","0","0",
"10","128","MIE","61047","10"
DSMMGR,NODE12,4/8/04,6899","10","7","3","2","0","125","7","2","1","0","0","0",
"10","128","MIE","32363","10"
DSMMGR,NODE12,4/8/04,6900","10","7","3","2","1","125","7","2","1","0","0","0",
"10","128","MIE","52793","10"
DSMMGR,NODE12,4/8/04,6901","10","7","3","2","1","125","7","2","1","0","0","0",
"10","128","MIE","24101","10"
DSMMGR,NODE12,4/8/04,6902","10","7","3","2","0","125","7","2","1","0","0","0",
"10","128","MIE","11777","10"
$
The output file is a comma-delimited file with the following fields. The first line is header information for each field.
|
Field # |
Field |
Comments |
|
1 |
DSM environment |
|
|
2 |
VMS node name |
|
|
3 |
Date |
MM/DD/YY |
|
4 |
Slot |
Seconds since midnight DIV interval |
|
5 |
Total Jobs |
From STRT1^%SY |
|
6 |
System Jobs |
From STRT1^%SY |
|
7 |
Non-System Jobs |
From STRT1^%SY |
|
8 |
Non-System Jobs with Non-Null Devices |
From STRT1^%SY |
|
9 |
Inactive Non-System Jobs |
No lines executed or globals referenced during interval |
|
10 |
Available License Slots |
|
|
11 |
System Jobs |
From SUM2^%SY, usually equal to field 6 |
|
12 |
Programmer Jobs |
From SUM2^%SY |
|
13 |
Application Jobs |
From SUM2^%SY |
|
14 |
Improperly Exited |
From SUM2^%SY |
|
15 |
Call Interface |
From SUM2^%SY |
|
16 |
Tied Jobs |
From SUM2^%SY |
|
17 |
Total Jobs |
From SUM2^%SY |
|
18 |
Max Jobs |
From SUM2^%SY |
|
19 |
DSM Node |
From $$DSMNODE^%VOLDEF() |
|
20 |
Checksum |
|
|
21 |
Collection Interval |
In seconds |
3. Automatically start ^%PCNT process at DSM
configuration startup.
The ^CONFIG utility has been enhanced starting with the DSM V7.3 MUP3 kit to include the Process Counter startup option as follows:
>D ^CONFIG
.
.
Enter the configuration identifier <1>
.
.
Automatically start ViewPoint collector at startup [Y OR N] ? <N>
Include support for ViewPoint user-defined metrics [Y OR N] ? <N>
Include support for Cache' Direct application serving [Y OR N] ? <N>
Include support for a license server [Y OR N] ? <N>
Automatically start Process Counter at startup [Y OR N] ? <N> ?
Enter 'Y'
to automatically start a DSM process which will count the
number
and type of DSM processes running in this configuration at a
specified
interval.
Automatically
start Process Counter at startup [Y OR N] ? <N> Y
Enter the interval in minutes to collect Process Count <30>
Include support for security auditing [Y OR N] ? <N>
*** System options updated
Modify Database Sets mounted at startup [Y OR N] ? <N>
.
.
.
The following example shows the Process Counter startup procedure:
>D ^STU
DSM Configuration Startup
Enter the configuration identifier <1>
Enable user logins on startup [Y OR N] ? <Y>
Size memory requirements for configuration 1 [Y OR N] ? <N>
Starting DSM configuration 1
Licensed To: RBOMO
Initializing DSM environment for TEST ... 1284 pages mapped
DSM Write Demon ... Started as DSM_DEMON_19 (PID = 21000309)
DSM Garbage Collector ... Started as DSM_GARCOL_19 (PID = 21000310)
Volume set AAA ... mounted as S0
POLIO$DKA100:[TEST.DATABASE]AAAVOL1.GLS;1 (15 maps)
Starting
process counter ...
DSM Process Counter ... Started as DSM_PCOUNT_19 (PID = 21000316)
DSM startup complete: User logins - enabled
%DSM-I-HALT, HALT command executed
In addition, the following new definition keywords have been created
for the option file utility as follows:
DEFINE PROCESS_COUNTER
PROCESS_COUNTER_INTERVAL="30"
Attachment C – Dev Changes incorporated into Version 7.3 MUP3 of DSM
The following is a
cumulative list that provides information regarding enhancements and problems
that have been corrected in DSM V7.3 MUP3 (known as DEV changes). For ease of reference, the list also
includes information regarding dev changes from previous DSM V7.3 maintenance
kits, which are also incorporated into DSM V7.3 MUP3.
Information regarding enhancements and problems that were corrected in DSM V7.3 MUP1, which have been carried through to DSM V7.3 MUP3:
EHB007D DSM V7.3 MUP1 corrects
a problem whereby OpenVMS's OPERATOR.LOG file can inadvertently grow in size at
a rapid rate (many thousands of blocks per minute). The situation occurs when a DSM journal process requires an
Operator reply and OpenVMS operator coverage has been disabled. The following type of message would be
repeatedly placed into the OPERATOR.LOG file at a rapid rate.
%%%%%%%%%%% OPCOM 1-NOV-2001
10:53:37.37 %%%%%%%%%%%
Request x, from user DSMMGR on HOME26
DSM Journal file for environment DSMMGR ( 1 ) is full,
please reply
%%%%%%%%%%%
OPCOM 1-NOV-2001
10:53:37.37 %%%%%%%%%%%
No operator coverage for request x
This Dev change results in the message now being entered once every
minute into the OPERATOR.LOG file until operator coverage resumes.
RFD021D &
RFD022D DSM V7.3 MUP1 corrects potential problems that could occur with previous versions of DSM that were configured to make use of DCP (Distributed Cache Protocol). Problems could previously occur when DCP and DSM data structures (global sections) inadvertently overlapped in memory.
Examples of possible
problems that could occur, included, but were not restricted to:
·
DSM applications reporting "phantom"
database degradation errors.
·
Cache' to DSM DCP links intermittently failing.
Initially, RFD021D was produced to correct the problem, however it was
found not to be suitable for VAX systems and hence RFD022D was subsequently
produced to successfully correct the issue on both VAX & Alpha systems.
SRS003D DSM V7.3 MUP1 corrects
an issue that previously existed with the ^DDPSTA utility, where inaccurate
statistics could often be returned for the last 3 rows of a statistics screen.