| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
I'm having a problem installing EMS V2.1 It appears something may have
been left out of the install process when it goes to build the Rdb
database. Or something like that.
The configuration is:
VMS T5.4-2
Rdb V4.0-0
CDD V4.3
I've been through the installation manual and this notesfile and have
been unable to find any references to this problem.
Any constructive suggestions are appreciated.
Thanks.
Here is the installation log:
[H[J#3)0lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
#6x x
#6x Unauthorized Access is Prohibited [mx
#6x [mx
#3mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
[m)B
Username: SYSTEM
Password:
Welcome to VAX/VMS version T5.4-2 on node SUNDEC
Last interactive login on Monday, 29-APR-1991 16:02
Last non-interactive login on Monday, 29-APR-1991 15:08
WARNING - Your password expires on Saturday, 4-MAY-1991 07:40
Z
[c
[62"p F
>
Z
[c
[62"p F
>
[1mSYS_SUNDEC> [0m
[K
[1mSYS_SUNDEC> [0m
[K
[1mSYS_SUNDEC> [0m@sys$update:vmsinstal mccems021 sancho"system"::$1$dus60:[mcc_v021]
VAX/VMS Software Product Installation Procedure T5.4-2
It is 30-APR-1991 at 07:30.
Enter a question mark (?) at any time for help.
%VMSINSTAL-W-ACTIVE, The following processes are still active:
NETBIOS
PCFS_SERVER
DECW$TE_7
Lawrence
DECW$TE_0
Temple Tempe
* Do you want to continue anyway [NO]? y
* Are you satisfied with the backup of your system disk [YES]?
The following products will be processed:
MCCEMS V2.1
Beginning installation of MCCEMS V2.1 at 07:30
%VMSINSTAL-I-RESTORE, Restoring product save set A ...
%VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.
************************************************************
* *
* DECMCC EMS V2.1 *
* Integrated Package *
* *
* Installation Procedure *
* *
************************************************************
Product: DECMCC-EMS
Producer: DEC
Version: 2.1
Release Date: 12-APR-1991
* Does this product have an authorization key registered and loaded? y
* Do you want to purge files replaced by this installation [YES]? no
* Do you want to run the DECMCC EMS IVP after the installation [YES]?
* Do you want to install the entire EMS product set? [YES]?
%VMSINSTAL-I-RESTORE, Restoring product save set B ...
%VMSINSTAL-I-RESTORE, Restoring product save set C ...
%VMSINSTAL-I-RESTORE, Restoring product save set D ...
%VMSINSTAL-I-RESTORE, Restoring product save set E ...
%VMSINSTAL-I-RESTORE, Restoring product save set F ...
%BACKUP-E-OPENOUT, error opening $90$DUA2:[SYS0.SYSUPD.MCCEMS021]ELMS$FILEVIEW.COM;1 as output
-RMS-E-FEX, file already exists, not superseded
%VMSINSTAL-E-NOSAVESET, Save set F cannot be restored.
%VMSINSTAL-I-RESTORE, Restoring product save set G ...
%VMSINSTAL-I-RESTORE, Restoring product save set H ...
Asking DECmcc BMS Questions...
DECmcc requires a directory where the DECmcc common files
will be installed. If the logical MCC_COMMON is defined, the
default is for the files to be installed in that directory.
If the logical is not defined, the default is for the files
to be installed in a directory on the system disk called
SYS$COMMON:[MCC]. The installer may override the default.
The target directory for the files as it is now defined is
shown below.
Press RETURN to use the value shown or enter a new disk and
directory specification.
* Target directory for DECmcc Common files [SUNDEC$DUA0:[MCC]]:
%VMSINSTAL-I-RESTORE, Restoring product save set I ...
%VMSINSTAL-I-RESTORE, Restoring product save set J ...
%VMSINSTAL-I-RESTORE, Restoring product save set K ...
%VMSINSTAL-I-SYSDIR, This product creates system specific directory [MCC].
If you intend to execute this layered product on other
nodes in your VAXcluster, and you have the appropriate
software license, you must prepare the system-specific
roots on the other nodes by issuing the following command
on each node (using a suitably privileged account):
$ CREATE/DIRECTORY SYS$SPECIFIC:[MCC]/OWNER_UIC=PARENT -
/PROT=(S:RWE,O:RWE,G:RE,W:R)
%VMSINSTAL-I-SYSDIR, This product creates system directory [SYSTEST.MCC].
%VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.MCC].
The Time Differential Factor (TDF) is the difference between
your time zone and the international standard Coordinated
Universal Time (UTC)
A negative (-) TDF value means that this node is west of UTC
A positive (+) TDF value means that this node is east of UTC
The range is from -12:00 to +13:00. The format is +hh:mm or
-hh:mm with hh indicating the number of hours and mm
indicating the number of minutes. For example:
California (Pacific Standard Time) is -8:00 hours from UTC.
Oklahoma (Standard Time) is -6:00 hours from UTC.
Eastern Standard Time is -5:00 hours from UTC.
Eastern Daylight Time is -4:00 hours from UTC.
Ontario, west of longitude W.63 degrees is -5:00
hours from UTC.
Ontario, east of longitude W.63 degrees is -4:00
hours from UTC.
Newfoundland is -3:30 hours from UTC.
Great Britain, Iceland, Portugal, Upper Volta are
at UTC or 0:0.
Great Britain, Summer Time +1:00 hour from UTC.
Greece is +2:00 hours from UTC.
India is +5:30 hours from UTC.
Singapore is +7:30 hours from UTC.
Japan is +9:00 hours from UTC.
Australian Capital Territory is +10:00 hours from UTC.
* Time Differential Factor [-4:00]: -7:00
You must specify the IDP (or network address initial domain
part) for your network. This must either be the default
value of "49::", or a value explicitly allocated for your
network by one of the recognized allocation authorities.
The format is:
afi:idi:
where:
afi = The "authority and format identifier". This is two
decimal digits indicating the IDP allocation
authority
idi = The "initial domain identifier". This is a string of
decimal digits that has been allocated specifically
for your network.
An IDP of "49::" may be used if your network will not be
interconnected with other OSI networks (there is no "idi"
associated with this "afi").
* Initial Domain Part [49::]:
The DECmcc Reports Package consists of files that allow you
to use DATATRIEVE to create reports using data exported from
DECmcc. Please see the Reports Package section of the
DECmcc Performance Analyzer Use manual for information
on using the DECmcc Reports Package with DATATRIEVE.
The Reports package requires 1100 blocks.
* Do you want to install the DECmcc Reports Package [No]? yes
* Target directory for DECmcc Reports files [SUNDEC$DUA0:[MCC.MCC_REPORTS_FILES]]:
Following the copying of the files, the DECmcc BMS startup
command procedure(s) will be invoked. Operational tables
will be created by this procedure.
To automatically set up DECmcc BMS on your system,
edit your local system start-up command procedure
SYS$MANAGER:SYSTARTUP_V5.COM
so that it invokes the DECmcc BMS start-up command
procedure. Add:
@SYS$STARTUP:MCC_STARTUP_BMS.COM
after the statement that invokes the DECnet start-up
command file (STARTNET.COM).
NOTE: If you have previously installed the DECmcc DIRECTOR
on this system, you should REMOVE the line:
@SYS$STARTUP:MCC_STARTUP_DIR.COM
from your SYS$MANAGER:SYSTARTUP_V5.COM procedure.
NOTE: The DECdns clerk must also be started up before
the MCC_STARTUP_BMS command procedure is invoked.
Following the DECmcc BMS start-up the DECmcc BMS
postinstallation command procedure will be invoked.
Asking DECmcc ETHERnim Questions...
See the NMCC/VAX ETHERnim Installation Guide for help in changing values.
This installation procedure will now prompt for the device name and Directory
name for the ETHERnim files.
NOTE!
Previous versions of ETHERnim created a separate account for ETHERnim. This
version does not create a separate account for ETHERnim. It is recommended
that the ETHERNIM account be disabled from the UAF for security purposes.
* Device for the files [SYS$SYSDEVICE:]: sundec$dua0:
* Directory for the files [ETHERNIM]:
%MCCEMS-I-CRE_ENIM_START, Creating file ENIM$HOST_STARTUP.COM
Asking DECmcc ELMS Questions...
%VMSINSTAL-I-SYSDIR, This product creates system directory [ELMS$DIRECTORY].
If you intend to execute this layered product on other nodes in your
VAXcluster, and you have the appropriate software license, you must
prepare the system-specific roots on the other nodes by issuing the
following command on each node (using a suitably privileged account):
$ CREATE /DIRECTORY SYS$SPECIFIC:[ELMS$DIRECTORY]/PROTECTION=(SYSTEM:RWE,OWNER:RWE,GROUP:RE,WORLD:RE)
You can convert your RBMS directory (if one exists) into
the DECelms registry at any time with the following command:
$ RUN SYS$MANAGER:ELMS$CONVERT.EXE
There are the following restrictions:
o The RBMS detached process, NMS_RBMS$BMLPRC, must be running.
o The DECelms detached process, ELMS$NIMUX, cannot be running.
This install procedure can perform both these operations,
if requested.
You can convert your RBMS directory into the
DECelms registry during this installation procedure.
Answer NO if you are not upgrading from RBMS or
if you do not want to convert your RBMS directory
during the installation. This does not imply that
RBMS will have to be shutdown, if you have reasons
for keeping RBMS running.
* Do you want to convert your RBMS database during the installation [NO]?
The ELMS$NIMUX (Network Multiplexer) module of DECelms must run as a
permanent detached process. The installation procedure normally starts
the ELMS$NIMUX process. If you wish, you may defer starting this process
until a later time. DECelms cannot be run until this is done.
The command to manually start the ELMS$NIMUX process is:
$ @SYS$STARTUP:ELMS$STARTUP
Also, if the ELMS$NIMUX process is not started by the installation
procedure, the installation verification procedure cannot be run.
Any time after the ELMS$NIMUX process has started, the verification
procedure can be manually run by typing the following command:
$ @SYS$COMMON:[SYSTEST]ELMS$IVP
If you let this installation procedure start the ELMS$NIMUX process
the installation procedure can verify the installation
automatically. Note that the installation verification procedure
does not require a bridge to be installed on the network.
* Do you want to start ELMS [YES]?
%RUN-S-PROC_ID, identification of created process is 202004A2
You can start the device listener function during the DECelms
installation. The device listener function enters devices in the
DECelms registry by listening to MOP system ID messages. At any
time after the installation, you can control the device listener
function with the DECelms commands START LISTENER and STOP
LISTENER, as described in the DECelms documentation.
NOTE
The device listener function conflicts with
other applications, such as NMCC/VAX ETHERnim,
that use the MOP Remote Console channel in
shared default mode. The device listener function
will not start if one of these applications is
running.
* Do you want to start the device listener function [YES]?
Error in reading text for output displays.
You can start the background poller function during the DECelms
installation. The background poller function polls the devices
listed in the DECelms registry. When its detects a change in device
state, it displays an event message and logs an event code in the
event log. At any time after the installation, you can control the
background poller function with the DECelms commands START POLLER
and STOP POLLER, as described in the DECelms documentation.
* Do you want to start the background poller function [YES]?
Error in reading text for output displays.
Files ELMS$NIMUX.EXE, ELMS$BCP.EXE, ELMS$DISPLAYS.BIN,
ELMS$BCPPRS.BIN installed in SYS$COMMON:[SYSEXE].
File ELMS$HELP.HLB installed in SYS$HELP.
File ELMS$STARTUP.COM installed in SYS$STARTUP.
File ELMS$SHUTDOWN.COM installed in SYS$COMMON:[SYSMGR].
File ELMS$CONVERT.EXE installed in SYS$COMMON:[SYSMGR].
File ELMS$IVP.COM installed in SYS$SYSTEST.
ELMS$HELP_DCL.HLP inserted into system command table.
Logical name ELMS$UNA defined as Ethernet adapter device id.
Logical name ELMS$NIMUX_MBX defined as mbx number.
Logical name ELMS$BCPPRS defined as SYS$COMMON:[SYSEXE]
Logical name ELMS$DISPLAYS defined as SYS$COMMON:[SYSEXE]
Logical name ELMS$HELP defined as SYS$HELP:ELMS$HELP.HLB
Logical name ELMS$HOME defined as SYS$COMMON:[ELMS$DIRECTORY]
Asking DECmcc NMCC/DECnet Monitor Questions...
The NMCC/DECnet Monitor installation procedure now
asks if you wish to install JUST the blank NMCC
database files. The database files may only be
installed on a system that has a NMCCKERNEL account.
If you wish to install the entire NMCC/DECnet Monitor
product, answer NO to the following question.
A YES answer to the next prompt will install JUST the
NMCC database files.
* Do you want to install JUST the NMCC database files? [NO]?
* Do you want to install just the NMCC User Interface? [NO]?
This installation will give you the option of keeping
the old NMCC database files or installing new (empty)
NMCC database files.
If this is a new NMCC installation, you must install new
NMCC database files.
* Do you want to install the NMCC database files? [YES]?
DECMCC NMCC/DECnet Monitor database files will be installed...
Any previously existing NMCC database files will be superseded.
%VMSINSTAL-I-RESTORE, Restoring product save set L ...
%VMSINSTAL-I-RESTORE, Restoring product save set M ...
The installation procedure prompts you to define the GKS workstation
type (GKS$WSTYPE) that will be the default workstation type whenever
the NMCC/DECnet Monitor is invoked. The correct GKS$WSTYPE value is
required to ensure the accurate display of GKS graphics. At the prompt,
you enter a number to identify the type of workstation you are using.
Some specifiable values are the following:
0 -- Default workstation type
14 -- VT240/41 with black and white display
13 -- VT240/41 with color option, VT340/41
-1 __ VT100 (non_ReGIS terminal)
Not all workstation types are supported by NMCC/DECnet Monitor. For a
complete listing of values for GKS workstation types, see the GKS
documentation or enter the HELP GKS WORKSTATION command at the dollar sign
($) prompt.
* Define GKS$WSTYPE: 13
%MCCEMS-I-GKSOK, GKS found
%MCCEMS-I-RDBOK, RDB found
If you are installing the NMCC/DECnet Monitor for the first time,
you will be prompted for the Greenwich Mean Time (GMT) offset for
your area.
The GMT offset is the number of hours that you have to add to your
local time to get Greenwich Mean Time.
For example, if your node is on the east coast of the United States
and your local time is Eastern Standard Time, your GMT offset is +5.
You would have to add five hours to your time to get Greenwich Mean Time.
* Please enter the current GMT offset for your timezone [0]: +7
%MCCEMS-I-CRELOGICALS, Creating file NMCCLOGICALS.COM
%MCCEMS-I-NMCCLOGICALS, Invoking NMCCLOGICALS.COM to define NMCC logical names
If you are creating the NMCCKERNEL account, the installation procedure
prompts you for the User Identification Code (UIC), which consists of
two integers separated by a comma. The system manager should select
the UIC for the NMCCKERNEL account. The UIC should not belong to another
user or VMSINSTAL will terminate the installation. The first number in
the UIC pair should not be between 1 and 8 because these are reserved
for system UICs. The following are examples of valid UICs:
[123, 456]
[12, 3]
The NMCC installation procedure may create an account under which the
NMCC Kernel runs. All privileges and quotas required by the Kernel are
set up in this account by the installation procedure. If this account
does not already exist, and you wish it to be created, then you should
answer YES to the following question. Otherwise answer NO or just press
RETURN.
* Would you like the NMCCKERNEL account to be created [NO]? y
* UIC for Kernel account: 373,0
*************************************************************
This installation requires the creation of the NMCCKERNEL
account. You MUST choose a password for this account.
**************************************************************
* Please press RETURN to continue:
*************************************************************
The entire installation will FAIL if you do not enter a valid
password for the NMCCKERNEL account. You will be given
3 chances to verify your password. This installation
procedure requires at least 15 characters for the
RDB$REMOTE password. Valid characters for a password are:
A through Z
a through z
0 through 9
$ (dollar sign)
_ (underscore)
As with the DCL SET PASSWORD command, your input will not
appear on the terminal. And to protect against typing errors
that are not seen when entering the password, you must enter
the password twice.
*************************************************************
>
* Please enter PASSWORD to be used for NMCCKERNEL account:
>
*************************************************************
Password MUST be at least 15 characters.
**************************************************************
* Please enter <RETURN> to continue:
*************************************************************
The entire installation will FAIL if you do not enter a valid
password for the NMCCKERNEL account. You will be given
3 chances to verify your password. This installation
procedure requires at least 15 characters for the
RDB$REMOTE password. Valid characters for a password are:
A through Z
a through z
0 through 9
$ (dollar sign)
_ (underscore)
As with the DCL SET PASSWORD command, your input will not
appear on the terminal. And to protect against typing errors
that are not seen when entering the password, you must enter
the password twice.
*************************************************************
>
* Please enter PASSWORD to be used for NMCCKERNEL account:
>
*************************************************************
Password MUST be at least 15 characters.
**************************************************************
* Please enter <RETURN> to continue:
*************************************************************
The entire installation will FAIL if you do not enter a valid
password for the NMCCKERNEL account. You will be given
3 chances to verify your password. This installation
procedure requires at least 15 characters for the
RDB$REMOTE password. Valid characters for a password are:
A through Z
a through z
0 through 9
$ (dollar sign)
_ (underscore)
As with the DCL SET PASSWORD command, your input will not
appear on the terminal. And to protect against typing errors
that are not seen when entering the password, you must enter
the password twice.
*************************************************************
>
* Please enter PASSWORD to be used for NMCCKERNEL account:
>
>
* Please verify the PASSWORD entered for NMCCKERNEL account:
>
%VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named NMCCKERNEL.
%UAF-I-ADDMSG, user record successfully added
%UAF-I-RDBADDMSGU, identifier NMCCKERNEL value: [000373,000000] added to rights data base
%VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named NMCCKERNEL.
%UAF-I-MDFYMSG, user record(s) updated
************************************************************************
* The account NMCCKERNEL has been created solely for running the *
* NMCCKERNEL. You MUST change the NMCCKERNEL password the first time *
* the account is used. *
************************************************************************
%VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[NMCC]/LOG/OWNER_UIC=[373,0]/PROTECTION=(S:WRE,O:RWE,G:RWE,W:RE).
%CREATE-I-CREATED, VMI$ROOT:[NMCC] created
%VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSTEST.NMCCVMS]/LOG/OWNER_UIC=[373,0]/PROTECTION=(S:WRE,O:RWE,G:RWE,W:RE).
%CREATE-I-CREATED, VMI$ROOT:[SYSTEST.NMCCVMS] created
Displaying DECmcc LTM Installation Information...
%VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[DECSERVER].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SPECIFIC:[DECSERVER].
******************************************************************
The files in the distribution kit will be copied to the
appropriate system directories.
File System directory
---------------------- ----------------
LTM$SETUP.COM SYS$COMMON:[DECSERVER]
LTM$LOAD_CONFIG.COM SYS$COMMON:[DECSERVER]
LTM$TYPE_NAME.DAT SYS$COMMON:[DECSERVER]
LTM$MC_NAME.DAT SYS$COMMON:[DECSERVER]
LTM$ADDR_NAME.DAT SYS$COMMON:[DECSERVER]
LTMLIS0200.SYS SYS$COMMON:[DECSERVER]
LTM$REGRESSION.COM SYS$COMMON:[SYSTEST.LTM]
LTM$REGRESSION.BMK SYS$COMMON:[SYSTEST.LTM]
LTM$IVP.COM SYS$COMMON:[SYSTEST]
LTM$UI.EXE SYS$SYSTEM:
LTM012.RELEASE_NOTES SYS$HELP:
---------------------- ----------------
NOTE
PLEASE place the command "$ @SYS$COMMON:[DECSERVER]LTM$SETUP"
in SYS$MANAGER:SYSTARTUP_V5.COM to initialize LTM logical names
at system boot time. Place it after the DECnet startup command.
******************************************************************
%VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSTEST.LTM].
Asking DECmcc TSM Questions...
The TSM installation procedure normally enables service
on the first circuit that it finds on this node. This
allows the node to down-line load and up-line dump
terminal servers.
If you answer "No" to the following question, service
will not be enabled.
* Do you want service enabled in the installation procedure [YES]? no
TSM requires a directory where the TSM command files and library
will be installed. If the logical TSM$DEFAULT_DIRECTORY is
defined, the files will be installed in that directory. If
the logical is not defined, the files will be installed in a
directory on the system disk called SYS$COMMON:[DECSERVER].
The target directory for the files as it is now defined is shown
below.
Press return to use the value shown or enter a new disk and
directory specification.
* Target directory for TSM files [SYS$COMMON:[DECSERVER]]:
Linking Terminal Server Manager VMS V1.4...
DECmcc TSM requires defining and setting OBJECT NML to
PROXY BOTH ALIAS OUTGOING ENABLED.
After the installation use AUTHORIZE to create proxy accounts for
all the TSM users (if you have not done so already).
VMSINSTAL asks no additional questions.
This software is for Digital Internal Use Only
%RDB-E-BAD_DB_FORMAT, NMCC$HOME:NMCCDBROOT.RDB does not reference a database known to Rdb
-RMS-E-FNF, file not found
%RDO-F-INVNOTDON, no DATABASE invoked yet, please issue a DATABASE command
%RDO-F-INVNOTDON, no DATABASE invoked yet, please issue a DATABASE command
%RDO-F-INVNOTDON, no DATABASE invoked yet, please issue a DATABASE command
%RDB-E-BAD_DB_FORMAT, NMCC$HOME:NMCCCOUNTER.RDB does not reference a database known to Rdb
-RMS-E-FNF, file not found
%RDO-F-INVNOTDON, no DATABASE invoked yet, please issue a DATABASE command
%RDO-F-INVNOTDON, no DATABASE invoked yet, please issue a DATABASE command
%RDO-F-INVNOTDON, no DATABASE invoked yet, please issue a DATABASE command
%RDB-E-BAD_DB_FORMAT, NMCC$HOME:NMCCRCOUNTER.RDB does not reference a database known to Rdb
-RMS-E-FNF, file not found
%RDO-F-INVNOTDON, no DATABASE invoked yet, please issue a DATABASE command
%RDO-F-INVNOTDON, no DATABASE invoked yet, please issue a DATABASE command
%RDO-F-INVNOTDON, no DATABASE invoked yet, please issue a DATABASE command
%RDB-E-BAD_DB_FORMAT, NMCC$HOME:NMCCSTATIC.RDB does not reference a database known to Rdb
-RMS-E-FNF, file not found
%RDO-F-INVNOTDON, no DATABASE invoked yet, please issue a DATABASE command
%RDO-F-INVNOTDON, no DATABASE invoked yet, please issue a DATABASE command
%RDO-F-INVNOTDON, no DATABASE invoked yet, please issue a DATABASE command
%RDB-E-BAD_DB_FORMAT, NMCC$HOME:NMCCSTATUS.RDB does not reference a database known to Rdb
-RMS-E-FNF, file not found
%RDO-F-INVNOTDON, no DATABASE invoked yet, please issue a DATABASE command
%RDO-F-INVNOTDON, no DATABASE invoked yet, please issue a DATABASE command
%RDO-F-INVNOTDON, no DATABASE invoked yet, please issue a DATABASE command
%SYSTEM-F-IVLOGNAM, invalid logical name
*********************************************************
Fatal NMCC V2.3 event occurred during installation
*********************************************************
*********************************************************
Canceling DECMCC EMS V2.1
*********************************************************
>
%VMSINSTAL-F-CTRLY, Installation cancelled via CTRL/Y.
*********************************************************
Fatal DECMCC EMS V2.1 event occurred during installation
*********************************************************
%VMSINSTAL-E-INSFAIL, The installation of MCCEMS V2.1 has failed.
VMSINSTAL procedure done at 08:27
[1mSYS_SUNDEC> [0mlo
SYSTEM logged out at 30-APR-1991 09:12:42.15
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 975.1 | patch available to fix your problem | TOOK::SZABIET | Mon May 06 1991 17:51 | 57 | |
Hi,
There is a bug found when installing NMCC/DECnet Monitor V2.3 with Rdb V4.0
(the NMCC/DECnet Monitor component of DECmcc EMS V2.1 applies). It has
to do with the new security features added into Rdb V4.0.
NMCC/DECnet Monitor originally only supported Rdb V3.1-B. If you try to
install DECnet Monitor with Rdb V4.0, you will get either access
problems or file protection problems (depending on whether or not you
have previously installed databases) when the installation procedure
tries to access the DECnet Monitor databases.
There has been code that was added to the DECmcc EMS V2.1 installation
procedure to try to fix these access problems; however the code does
not adequately fix these problems. If you try to install DECnet Monitor
with Rdb V4.0 installed you may get error messages like this:
.
.
%RDB-F-SYS_REQUEST, error from system services request
-RDMS-F-FILEACCERR, error opening database root file
_DUA0:[SYS0.SYSCOMMON.NMCC]NMCCDBROOT.RDB;1
-SYSTEM-F-NOPRIV, no privilege for attempted operation
%RDO-F-INVNOTDON, no DATABASE invoked yet, please issue a DATABASE
command
%RDO-F-INVNOTDON, no DATABASE invoked yet, please issue a DATABASE
command
%RDO-F-INVNOTDON, no DATABASE invoked yet, please issue a DATABASE
command
.
.
It appears that you have a similar problem. You basically cannot
access the DECnet Monitor databases.
The installation of DECnet Monitor is still okay (it has created
the databases and all) but as you can see there are problems in
accessing these databases.
We have a patch available that will basically fix the protections
of the databases back to the original state. You can find the
procedure in the DECmcc EMS V2.1 kit. The command procedure is called
NMCC_RDB_V40_DB_PATCH.COM, and it can be found in the NMCC$HOME
directory. Invoke the following after the DECmcc EMS V2.1
installation completes:
$MCR RDO @NMCC$HOME:NMCC_RDB_V40_DB_PATCH.COM
I will put this procedure in the next reply for those who
don't have this procedure. (Note that you will need
to tailor this procedure if you have moved your NMCC/DECnet Monitor
databases to a place other than NMCC$HOME, the default directory.)
This should solve your problem. Let me know how this works out...
-Lisa
| |||||
| 975.2 | NMCC_RDB_V40_DB_PATCH.COM | TOOK::SZABIET | Mon May 06 1991 17:54 | 31 | |
INVOKE DATABASE FILE NMCC$HOME:NMCCDBROOT.RDB
DEFINE PROTECTION FOR DATABASE POSITION 1 IDENTIFIER [*,*]
ACCESS"READ+WRITE+MODIFY+ERASE+SHOW+DEFINE+CHANGE+DELETE+CONTROL+OPERATOR+ADMINISTRATOR+REFERENCES+DISTRIBTRAN+SECURITY"
.
COMMIT
FINISH
INVOKE DATABASE FILE NMCC$HOME:NMCCCOUNTER.RDB
DEFINE PROTECTION FOR DATABASE POSITION 1 IDENTIFIER [*,*]
ACCESS"READ+WRITE+MODIFY+ERASE+SHOW+DEFINE+CHANGE+DELETE+CONTROL+OPERATOR+ADMINISTRATOR+REFERENCES+DISTRIBTRAN+SECURITY"
.
COMMIT
FINISH
INVOKE DATABASE FILE NMCC$HOME:NMCCRCOUNTER.RDB
DEFINE PROTECTION FOR DATABASE POSITION 1 IDENTIFIER [*,*]
ACCESS"READ+WRITE+MODIFY+ERASE+SHOW+DEFINE+CHANGE+DELETE+CONTROL+OPERATOR+ADMINISTRATOR+REFERENCES+DISTRIBTRAN+SECURITY"
.
COMMIT
FINISH
INVOKE DATABASE FILE NMCC$HOME:NMCCSTATIC.RDB
DEFINE PROTECTION FOR DATABASE POSITION 1 IDENTIFIER [*,*]
ACCESS"READ+WRITE+MODIFY+ERASE+SHOW+DEFINE+CHANGE+DELETE+CONTROL+OPERATOR+ADMINISTRATOR+REFERENCES+DISTRIBTRAN+SECURITY"
.
COMMIT
FINISH
INVOKE DATABASE FILE NMCC$HOME:NMCCSTATUS.RDB
DEFINE PROTECTION FOR DATABASE POSITION 1 IDENTIFIER [*,*]
ACCESS"READ+WRITE+MODIFY+ERASE+SHOW+DEFINE+CHANGE+DELETE+CONTROL+OPERATOR+ADMINISTRATOR+REFERENCES+DISTRIBTRAN+SECURITY"
.
COMMIT
FINISH
| |||||
| 975.3 | Install did not take... | TEMPE::MCAFOOS | Go ahead, plug it in while I stand back here.. | Tue May 07 1991 18:17 | 10 |
I didn't want to put the NMCC files on my system disk, so I pointed them to another disk/directory. I just checked and the only file I have in [nmcc] is MCC_REPORTS_FILES.DIR No other files exist, not even in the default directory. Are there any other fixes??? Thanks, Bob | |||||
| 975.4 | you are not looking in the right place... | TOOK::SZABIET | Wed May 08 1991 11:07 | 27 | |
Hi,
I do not believe you are looking in the correct directory...
SYS$COMMON:[MCC] is the place where you will find the DECmcc BMS
file MCC_REPORTS_FILES.DIR; you will not find any of the
NMCC/DECnet Monitor files there.
Try setting the default to the logical NMCC$HOME and see if you find
the file NMCC_RDB_V40_DB_PATCH.COM. If NMCC$HOME is not defined then
set default to SYS$MANAGER and see if the file NMCCLOGICALS.COM is
there. If you do not find NMCCLOGICALS.COM then the installation did
not complete. If you find NMCCLOGICALS.COM, invoke the command procedure.
That will set all of the logicals needed by NMCC/DECnet Monitor.
You can now check to see if the NMCC/DECnet Monitor database files
have been created. Set default to the logical NMCC$HOME and see if you
find any files with an .RDB extension. If you find them, you know that
the NMCC/DECnet Monitor databases have been created. All you need to do
at this point is invoke the following command to access the NMCC/DECnet
Monitor databases (what was suggested in .1):
$MCR RDO @NMCC$HOME:NMCC_RDB_V40_DB_PATCH.COM
You should be all set at this point. Let me know how things turn out...
-Lisa
| |||||
| 975.5 | The files aren't where they should be... | BLKWDO::MCAFOOS | Go ahead, plug it in while I stand back here.. | Wed May 08 1991 15:28 | 85 |
Thanks for your replies and suggestions, but I am looking in the
correct place for the files.
Here is a log of my last search. DUA0:[MCC] is where I want the files
to be to keep them off the system disk.
Thanks,
Bob
[H[J#3)0lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
#6x x
#6x Unauthorized Access is Prohibited [mx
#6x [mx
#3mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
[m)B
Username: SYSTEM
Password:
Welcome to VAX/VMS version T5.4-2 on node SUNDEC
Last interactive login on Wednesday, 8-MAY-1991 11:16
Last non-interactive login on Wednesday, 8-MAY-1991 09:55
Z
[c
[62"p F
>
Z
[c
[62"p F
>
[1mSYS_SUNDEC> [0msho log nmcc*
(LNM$PROCESS_TABLE)
(LNM$JOB_815E9020)
(LNM$GROUP_000001)
(LNM$SYSTEM_TABLE)
"NMCC$COUNTER_DIR" = "NMCC$HOME:"
"NMCC$EXE" = "_$90$DUA2:[SYS0.SYSCOMMON.SYSEXE]"
"NMCC$GMT_OFFSET" = "7:00:00.0"
"NMCC$HOME" = "_$90$DUA2:[SYS0.SYSCOMMON.NMCC]"
"NMCC$REMOTE_COUNTER_DIR" = "NMCC$HOME:"
"NMCC$ROOT_DIR" = "NMCC$HOME:"
"NMCC$SERVER_COUNT" = "2"
"NMCC$STATIC_DIR" = "NMCC$HOME:"
"NMCC$STATUS_DIR" = "NMCC$HOME:"
(DECW$LOGICAL_NAMES)
[1mSYS_SUNDEC> [0m
[1mSYS_SUNDEC> [0mdir nmcc$home
%DIRECT-W-NOFILES, no files found
[1mSYS_SUNDEC> [0m
[K
[1mSYS_SUNDEC> [0mdir nmcc$home:
%DIRECT-W-NOFILES, no files found
[1mSYS_SUNDEC> [0mset def sys$sysdevice:[sys0.syscommon.nmcc]
[1mSYS_SUNDEC> [0mdir
%DIRECT-W-NOFILES, no files found
[1mSYS_SUNDEC> [0mset def dua0:[mcc]
[1mSYS_SUNDEC> [0mdir
Directory DUA0:[MCC]
MCC_REPORTS_FILES.DIR;1
1/3 30-APR-1991 07:40:25.29
Total of 1 file, 1/3 blocks.
[1mSYS_SUNDEC> [0m
[1mSYS_SUNDEC> [0m
[K
[1mSYS_SUNDEC> [0mdir [...]
Directory DUA0:[MCC]
MCC_REPORTS_FILES.DIR;1
1/3 30-APR-1991 07:40:25.29
Total of 1 file, 1/3 blocks.
[1mSYS_SUNDEC> [0mlo
SYSTEM logged out at 8-MAY-1991 11:18:46.39
| |||||
| 975.6 | I'll call you to get more info... | TOOK::SZABIET | Thu May 09 1991 15:45 | 12 | |
Hi Bob,
Something might be going amiss when you move the NMCC files
off the system disk. It may be that you have one of your NMCC
logical names pointing to the wrong place.
Since you are moving files around I suspect your problem is specific
to your system. Instead of trying to solve the problem here I will
give you a phone call about it so we can try to solve your problem
offline.
-Lisa
| |||||
| 975.7 | Same problem. Any news? | COMICS::SCOBLE | Cantankerous. Me! | Thu May 16 1991 11:57 | 10 |
Hi, I'm seeing exactly the same problem with EMS V2.1 and RDB RT V4.0, and have not tried to put the NMCC files on another disk. Is there any update on the original reported problem? Regards, Gordon | |||||
| 975.8 | DECmcc EMS V2.1 Release Notes | DELNI::L_FELICE | Thu May 16 1991 19:06 | 8 | |
Gordon,
Did you follow the instructions in the release notes (or the replies
from Lisa Szabiet in .2 and .4) with respect to RDB RT V4.0? There
is a problem with RDB 4.0, which has been patched in DECmcc EMS V2.1
and fully explained in the EMS-specific section of the release notes.
Lisa
| |||||
| 975.9 | Any other ideas? | COMICS::SCOBLE | Cantankerous. Me! | Fri May 17 1991 06:36 | 56 |
I can find no reference to this problem in either the RDB
or EMS release notes, and I have tried the suggestions made
so far. The patch in .2 was nowhere on my system, and when I
run a copy, I get:
-----------------------------------------------------------------------------------
Gordon_on_RODERS>mcr rdo @nmcc$home:NMCC_RDB_V40_DB_PATCH.COM;1
%RDB-E-BAD_DB_FORMAT, NMCC$HOME:NMCCDBROOT.RDB does not reference a database known to Rdb
-RMS-E-FNF, file not found
%RDO-F-INVNOTDON, no DATABASE invoked yet, please issue a DATABASE command
%RDO-F-INVNOTDON, no DATABASE invoked yet, please issue a DATABASE command
%RDO-F-INVNOTDON, no DATABASE invoked yet, please issue a DATABASE command
%RDB-E-BAD_DB_FORMAT, NMCC$HOME:NMCCCOUNTER.RDB does not reference a database known to Rdb
-RMS-E-FNF, file not found
%RDO-F-INVNOTDON, no DATABASE invoked yet, please issue a DATABASE command
%RDO-F-INVNOTDON, no DATABASE invoked yet, please issue a DATABASE command
%RDO-F-INVNOTDON, no DATABASE invoked yet, please issue a DATABASE command
%RDB-E-BAD_DB_FORMAT, NMCC$HOME:NMCCRCOUNTER.RDB does not reference a database known to Rdb
-RMS-E-FNF, file not found
%RDO-F-INVNOTDON, no DATABASE invoked yet, please issue a DATABASE command
%RDO-F-INVNOTDON, no DATABASE invoked yet, please issue a DATABASE command
%RDO-F-INVNOTDON, no DATABASE invoked yet, please issue a DATABASE command
%RDB-E-BAD_DB_FORMAT, NMCC$HOME:NMCCSTATIC.RDB does not reference a database known to Rdb
-RMS-E-FNF, file not found
%RDO-F-INVNOTDON, no DATABASE invoked yet, please issue a DATABASE command
%RDO-F-INVNOTDON, no DATABASE invoked yet, please issue a DATABASE command
%RDO-F-INVNOTDON, no DATABASE invoked yet, please issue a DATABASE command
%RDB-E-BAD_DB_FORMAT, NMCC$HOME:NMCCSTATUS.RDB does not reference a database known to Rdb
-RMS-E-FNF, file not found
%RDO-F-INVNOTDON, no DATABASE invoked yet, please issue a DATABASE command
%RDO-F-INVNOTDON, no DATABASE invoked yet, please issue a DATABASE command
%RDO-F-INVNOTDON, no DATABASE invoked yet, please issue a DATABASE command
%RDO-F-SEVERRDET, a severe error was detected
-------------------------------------------------------------------------------------
When I did the original install, on a VAXstation 3100, it eventually
ended as follows, and terminated by DECterm session!
----------------------------------------------------------------------------------
* Target directory for TSM files [SYS$COMMON:[DECSERVER]]:
Linking Terminal Server Manager VMS V1.4...
DECmcc TSM requires defining and setting OBJECT NML to
PROXY BOTH ALIAS OUTGOING ENABLED.
After the installation use AUTHORIZE to create proxy accounts for
all the TSM users (if you have not done so already).
VMSINSTAL asks no additional questions.
-------------------------------------------------------------------------------
Any further help appreciated.
Gordon
| |||||
| 975.10 | More information. | COMICS::SCOBLE | Cantankerous. Me! | Fri May 17 1991 11:33 | 6 |
I've found NMCC_RDB_V40_DB_PATCH.COM in the temporary directory
set up for the installation in SYS$UPDATE, as none of the files
got as far as being moved to their target directories. Running
it again gave the same error as in .9. I was under the
impression that the database files were created by the installation
on a new system. Is this not the case?
| |||||
| 975.11 | installation did not complete... | TOOK::SZABIET | Fri May 17 1991 15:06 | 51 | |
Hi Gordon,
The NMCC/DECnet Monitor database files get copied from the DECmcc
EMS V2.1 kit to the target system. However, in your situation, it
appears as though the installation never completed and did not copy
over the database files (in addition to other files too since you did
not find NMCC_RDB_V40_DB_PATCH.COM).
Let me just first say that because of the bug with RDB V4.0, all people
who install NMCC/DECnet Monitor with RDB V4.0 will see the same errors
you see *during* the installation, specifically after the part that
says 'VMSINSTAL asks no additional questions'. The
reason why people will see this bug when RDB V4.0 is installed is that
the installation procedure checks to see if RDB V4.0 is installed and
if it is, it will run NMCC_RDB_V40_DB_PATCH.COM. However, there is a
bug in the installation procedure because it runs this patch
*before* the database files get copied to their target directories (so
essentially the patch is being applied when there are no database files
to apply it to). The installation should still complete
even though you see these errors, but the user *must* apply this patch
*after* the installation procedure completes in order to access the
DECnet Monitor databases. This is why we are telling users that they
need to run this patch *after* the installation procedure completes if
they come across these errors or else they will not be able to access
the databases.
However, since you are seeing these errors while you are applying the
patch, this tells me that the installation procedure did not complete
successfully since the database files (in addition to the patch
command procedure) were never moved to the target system. You
can check this for yourself by seeing if the *.RDB files and
NMCC_RDB_V40_DB_PATCH.COM exist in the logical directory NMCC$HOME.
I would suggest reinstalling NMCC/DECnet Monitor, and create a log
file of the whole installation procedure. Follow the appendix
containing the sample installation in the back of the installation
guide to see if the installation procedure completes or not (if you
are only installing DECnet monitor just follow the DECnet Monitor pieces
of the sample installation...everything should still proceed in order, for
example, the post installation procedures and the IVP).
If for some reason the installation does not complete again,
please send the log file of the installation along with any other
information you feel is pertinent. If the installation
procedure fails again we can work with you off-line to try to fix your
specific problem.
I will be on vacation next week (May 18-27), so if you still have a
problem send your installation log to Butch (TOOK::) McKinney. He
should be able to help you while I am away.
-Lisa
| |||||
| 975.12 | Works under specific circumstances. | COMICS::SCOBLE | Cantankerous. Me! | Tue May 21 1991 08:13 | 618 |
Hi Lisa,
I have done a re-install, but this time only taken the
option to install NMCC from the EMS product set. Note this
system had no previous NMCC or RDB configuration on it.
The installation completed succesfully, despite coming up
with the "%RDO-F-INVNOTDON, no DATABASE invoked yet, please
issue a DATABASE command" messages on the various NMCC RDB
files not referenced as seen previously. In addition, I got
the following immediately after these previous messages:
--------------------------------------------------------------------------------
%VMSINSTAL-W-NOFILE, File VMI$KWD:NMCCCOUNTER.RDB does not exist.
%VMSINSTAL-W-NOFILE, New file NMCCCOUNTER.RDB does not exist.
%VMSINSTAL-W-NOFILE, File VMI$KWD:NMCCCOUNTER.SNP does not exist.
%VMSINSTAL-W-NOFILE, New file NMCCCOUNTER.SNP does not exist.
%VMSINSTAL-W-NOFILE, File VMI$KWD:NMCCDBROOT.RDB does not exist.
%VMSINSTAL-W-NOFILE, New file NMCCDBROOT.RDB does not exist.
%VMSINSTAL-W-NOFILE, File VMI$KWD:NMCCDBROOT.SNP does not exist.
%VMSINSTAL-W-NOFILE, New file NMCCDBROOT.SNP does not exist.
%VMSINSTAL-W-NOFILE, File VMI$KWD:NMCCRCOUNTER.RDB does not exist.
%VMSINSTAL-W-NOFILE, New file NMCCRCOUNTER.RDB does not exist.
%VMSINSTAL-W-NOFILE, File VMI$KWD:NMCCRCOUNTER.SNP does not exist.
%VMSINSTAL-W-NOFILE, New file NMCCRCOUNTER.SNP does not exist.
%VMSINSTAL-W-NOFILE, File VMI$KWD:NMCCSTATIC.RDB does not exist.
%VMSINSTAL-W-NOFILE, New file NMCCSTATIC.RDB does not exist.
%VMSINSTAL-W-NOFILE, File VMI$KWD:NMCCSTATIC.SNP does not exist.
%VMSINSTAL-W-NOFILE, File VMI$KWD:NMCCSTATUS.RDB does not exist.
%VMSINSTAL-W-NOFILE, New file NMCCSTATUS.RDB does not exist.
%VMSINSTAL-W-NOFILE, File VMI$KWD:NMCCSTATUS.SNP does not exist.
%VMSINSTAL-W-NOFILE, New file NMCCSTATUS.SNP does not exist.
--------------------------------------------------------------------------------
I then ran NMCC_RDB_V40_DB_PATCH.COM, and had no further
problems with NMCC. Re-installing the complete EMS kit again
was trouble free. It looks as if this corrective procedure
is fine if the database files from a previous installation
are on the system, or if NMCC is installed on its own, but
with clean systems with no previous NMCC configuration
there's a fundemental problem installing the full EMS product
set in repect of the database files and others getting
shipped to their appropriate directories.
Here is the full log of the failed installation:
------------------------------------------------------------------------------------
Welcome to the MCC node.
Username: SYSTEM
Password:
Welcome to VAX/VMS version V5.4-2 on node RODERS
Last interactive login on Thursday, 16-MAY-1991 14:51
Last non-interactive login on Thursday, 16-MAY-1991 14:42
Directory SYS$SYSDEVICE:[USERS.SCOBLE.MCCEMS]
MCCEMS021.A;1 MCCEMS021.B;1 MCCEMS021.C;1 MCCEMS021.D;1
MCCEMS021.E;1 MCCEMS021.F;1 MCCEMS021.G;1 MCCEMS021.H;1
MCCEMS021.I;1 MCCEMS021.J;1 MCCEMS021.K;1 MCCEMS021.L;1
MCCEMS021.M;1 MCCEMS021.RELEASE_NOTES;40
MCC_EMS_INSTALL.LOG;1
Total of 15 files.
$@sys$update:vmsinstal MCCEMS021 SYS$SYSDEVICE:[USERS.SCOBLE.MCCEMS] options n
VAX/VMS Software Product Installation Procedure V5.4-2
It is 16-MAY-1991 at 15:01.
Enter a question mark (?) at any time for help.
* Are you satisfied with the backup of your system disk [YES]?
The following products will be processed:
MCCEMS V2.1
Beginning installation of MCCEMS V2.1 at 15:02
%VMSINSTAL-I-RESTORE, Restoring product save set A ...
Release notes included with this kit are always copied to SYS$HELP.
Additional Release Notes Options:
1. Display release notes
2. Print release notes
3. Both 1 and 2
4. None of the above
* Select option [2]: 4
* Do you want to continue the installation [NO]? y
%VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.
************************************************************
* *
* DECMCC EMS V2.1 *
* Integrated Package *
* *
* Installation Procedure *
* *
************************************************************
Product: DECMCC-EMS
Producer: DEC
Version: 2.1
Release Date: 12-APR-1991
* Does this product have an authorization key registered and loaded? y
* Do you want to purge files replaced by this installation [YES]?
* Do you want to run the DECMCC EMS IVP after the installation [YES]?
* Do you want to install the entire EMS product set? [YES]?
%VMSINSTAL-I-RESTORE, Restoring product save set B ...
%VMSINSTAL-I-RESTORE, Restoring product save set C ...
%VMSINSTAL-I-RESTORE, Restoring product save set D ...
%VMSINSTAL-I-RESTORE, Restoring product save set E ...
%VMSINSTAL-I-RESTORE, Restoring product save set F ...
%BACKUP-E-OPENOUT, error opening RODERS$DKA100:[SYS0.SYSUPD.MCCEMS021]ELMS$FILEVIEW.COM;1 as output
-RMS-E-FEX, file already exists, not superseded
%VMSINSTAL-E-NOSAVESET, Save set F cannot be restored.
%VMSINSTAL-I-RESTORE, Restoring product save set G ...
%VMSINSTAL-I-RESTORE, Restoring product save set H ...
Asking DECmcc BMS Questions...
DECmcc requires a directory where the DECmcc common files
will be installed. If the logical MCC_COMMON is defined, the
default is for the files to be installed in that directory.
If the logical is not defined, the default is for the files
to be installed in a directory on the system disk called
SYS$COMMON:[MCC]. The installer may override the default.
The target directory for the files as it is now defined is
shown below.
Press RETURN to use the value shown or enter a new disk and
directory specification.
* Target directory for DECmcc Common files [SYS$COMMON:[MCC]]:
%VMSINSTAL-I-RESTORE, Restoring product save set I ...
%VMSINSTAL-I-RESTORE, Restoring product save set J ...
%VMSINSTAL-I-RESTORE, Restoring product save set K ...
The Time Differential Factor (TDF) is the difference between
your time zone and the international standard Coordinated
Universal Time (UTC)
A negative (-) TDF value means that this node is west of UTC
A positive (+) TDF value means that this node is east of UTC
The range is from -12:00 to +13:00. The format is +hh:mm or
-hh:mm with hh indicating the number of hours and mm
indicating the number of minutes. For example:
California (Pacific Standard Time) is -8:00 hours from UTC.
Oklahoma (Standard Time) is -6:00 hours from UTC.
Eastern Standard Time is -5:00 hours from UTC.
Eastern Daylight Time is -4:00 hours from UTC.
Ontario, west of longitude W.63 degrees is -5:00
hours from UTC.
Ontario, east of longitude W.63 degrees is -4:00
hours from UTC.
Newfoundland is -3:30 hours from UTC.
Great Britain, Iceland, Portugal, Upper Volta are
at UTC or 0:0.
Great Britain, Summer Time +1:00 hour from UTC.
Greece is +2:00 hours from UTC.
India is +5:30 hours from UTC.
Singapore is +7:30 hours from UTC.
Japan is +9:00 hours from UTC.
Australian Capital Territory is +10:00 hours from UTC.
* Time Differential Factor [-4:00]: +1:00
You must specify the IDP (or network address initial domain
part) for your network. This must either be the default
value of "49::", or a value explicitly allocated for your
network by one of the recognized allocation authorities.
The format is:
afi:idi:
where:
afi = The "authority and format identifier". This is two
decimal digits indicating the IDP allocation
authority
idi = The "initial domain identifier". This is a string of
decimal digits that has been allocated specifically
for your network.
An IDP of "49::" may be used if your network will not be
interconnected with other OSI networks (there is no "idi"
associated with this "afi").
* Initial Domain Part [49::]:
The DECmcc Reports Package consists of files that allow you
to use DATATRIEVE to create reports using data exported from
DECmcc. Please see the Reports Package section of the
DECmcc Performance Analyzer Use manual for information
on using the DECmcc Reports Package with DATATRIEVE.
The Reports package requires 1100 blocks.
* Do you want to install the DECmcc Reports Package [No]? y
* Target directory for DECmcc Reports files [SYS$COMMON:[MCC.MCC_REPORTS_FILES]]:
Following the copying of the files, the DECmcc BMS startup
command procedure(s) will be invoked. Operational tables
will be created by this procedure.
To automatically set up DECmcc BMS on your system,
edit your local system start-up command procedure
SYS$MANAGER:SYSTARTUP_V5.COM
so that it invokes the DECmcc BMS start-up command
procedure. Add:
@SYS$STARTUP:MCC_STARTUP_BMS.COM
after the statement that invokes the DECnet start-up
command file (STARTNET.COM).
NOTE: If you have previously installed the DECmcc DIRECTOR
on this system, you should REMOVE the line:
@SYS$STARTUP:MCC_STARTUP_DIR.COM
from your SYS$MANAGER:SYSTARTUP_V5.COM procedure.
NOTE: The DECdns clerk must also be started up before
the MCC_STARTUP_BMS command procedure is invoked.
Following the DECmcc BMS start-up the DECmcc BMS
postinstallation command procedure will be invoked.
Asking DECmcc ETHERnim Questions...
See the NMCC/VAX ETHERnim Installation Guide for help in changing values.
This installation procedure will now prompt for the device name and Directory
name for the ETHERnim files.
NOTE!
Previous versions of ETHERnim created a separate account for ETHERnim. This
version does not create a separate account for ETHERnim. It is recommended
that the ETHERNIM account be disabled from the UAF for security purposes.
* Device for the files [SYS$SYSDEVICE:]:
* Directory for the files [ETHERNIM]:
%VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[ETHERNIM].
%CREATE-I-EXISTS, SYS$SYSDEVICE:[ETHERNIM] already exists
%MCCEMS-I-CRE_ENIM_START, Creating file ENIM$HOST_STARTUP.COM
Asking DECmcc ELMS Questions...
You can convert your RBMS directory (if one exists) into
the DECelms registry at any time with the following command:
$ RUN SYS$MANAGER:ELMS$CONVERT.EXE
There are the following restrictions:
o The RBMS detached process, NMS_RBMS$BMLPRC, must be running.
o The DECelms detached process, ELMS$NIMUX, cannot be running.
This install procedure can perform both these operations,
if requested.
You can convert your RBMS directory into the
DECelms registry during this installation procedure.
Answer NO if you are not upgrading from RBMS or
if you do not want to convert your RBMS directory
during the installation. This does not imply that
RBMS will have to be shutdown, if you have reasons
for keeping RBMS running.
* Do you want to convert your RBMS database during the installation [NO]?
The ELMS$NIMUX (Network Multiplexer) module of DECelms must run as a
permanent detached process. The installation procedure normally starts
the ELMS$NIMUX process. If you wish, you may defer starting this process
until a later time. DECelms cannot be run until this is done.
The command to manually start the ELMS$NIMUX process is:
$ @SYS$STARTUP:ELMS$STARTUP
Also, if the ELMS$NIMUX process is not started by the installation
procedure, the installation verification procedure cannot be run.
Any time after the ELMS$NIMUX process has started, the verification
procedure can be manually run by typing the following command:
$ @SYS$COMMON:[SYSTEST]ELMS$IVP
If you let this installation procedure start the ELMS$NIMUX process
the installation procedure can verify the installation
automatically. Note that the installation verification procedure
does not require a bridge to be installed on the network.
* Do you want to start ELMS [YES]?
ELMS$NIMUX is already running. Do you want to restart? [Y/N]: y
%RUN-S-PROC_ID, identification of created process is 00000077
You can start the device listener function during the DECelms
installation. The device listener function enters devices in the
DECelms registry by listening to MOP system ID messages. At any
time after the installation, you can control the device listener
function with the DECelms commands START LISTENER and STOP
LISTENER, as described in the DECelms documentation.
NOTE
The device listener function conflicts with
other applications, such as NMCC/VAX ETHERnim,
that use the MOP Remote Console channel in
shared default mode. The device listener function
will not start if one of these applications is
running.
* Do you want to start the device listener function [YES]?
Error in reading text for output displays.
You can start the background poller function during the DECelms
installation. The background poller function polls the devices
listed in the DECelms registry. When its detects a change in device
state, it displays an event message and logs an event code in the
event log. At any time after the installation, you can control the
background poller function with the DECelms commands START POLLER
and STOP POLLER, as described in the DECelms documentation.
* Do you want to start the background poller function [YES]?
Error in reading text for output displays.
Files ELMS$NIMUX.EXE, ELMS$BCP.EXE, ELMS$DISPLAYS.BIN,
ELMS$BCPPRS.BIN installed in SYS$COMMON:[SYSEXE].
File ELMS$HELP.HLB installed in SYS$HELP.
File ELMS$STARTUP.COM installed in SYS$STARTUP.
File ELMS$SHUTDOWN.COM installed in SYS$COMMON:[SYSMGR].
File ELMS$CONVERT.EXE installed in SYS$COMMON:[SYSMGR].
File ELMS$IVP.COM installed in SYS$SYSTEST.
ELMS$HELP_DCL.HLP inserted into system command table.
Logical name ELMS$UNA defined as Ethernet adapter device id.
Logical name ELMS$NIMUX_MBX defined as mbx number.
Logical name ELMS$BCPPRS defined as SYS$COMMON:[SYSEXE]
Logical name ELMS$DISPLAYS defined as SYS$COMMON:[SYSEXE]
Logical name ELMS$HELP defined as SYS$HELP:ELMS$HELP.HLB
Logical name ELMS$HOME defined as SYS$COMMON:[ELMS$DIRECTORY]
Asking DECmcc NMCC/DECnet Monitor Questions...
The NMCC/DECnet Monitor installation procedure now
asks if you wish to install JUST the blank NMCC
database files. The database files may only be
installed on a system that has a NMCCKERNEL account.
If you wish to install the entire NMCC/DECnet Monitor
product, answer NO to the following question.
A YES answer to the next prompt will install JUST the
NMCC database files.
* Do you want to install JUST the NMCC database files? [NO]?
* Do you want to install just the NMCC User Interface? [NO]?
This installation will give you the option of keeping
the old NMCC database files or installing new (empty)
NMCC database files.
If this is a new NMCC installation, you must install new
NMCC database files.
* Do you want to install the NMCC database files? [YES]?
DECmcc NMCC/DECnet Monitor databases files will be installed...
Any previously existing NMCC database files will be purged.
* Is this correct? [YES]?
%VMSINSTAL-I-RESTORE, Restoring product save set L ...
%VMSINSTAL-I-RESTORE, Restoring product save set M ...
The installation procedure prompts you to define the GKS workstation
type (GKS$WSTYPE) that will be the default workstation type whenever
the NMCC/DECnet Monitor is invoked. The correct GKS$WSTYPE value is
required to ensure the accurate display of GKS graphics. At the prompt,
you enter a number to identify the type of workstation you are using.
Some specifiable values are the following:
0 -- Default workstation type
14 -- VT240/41 with black and white display
13 -- VT240/41 with color option, VT340/41
-1 __ VT100 (non_ReGIS terminal)
Not all workstation types are supported by NMCC/DECnet Monitor. For a
complete listing of values for GKS workstation types, see the GKS
documentation or enter the HELP GKS WORKSTATION command at the dollar sign
($) prompt.
* Define GKS$WSTYPE: 0
%MCCEMS-I-GKSOK, GKS found
%MCCEMS-I-RDBOK, RDB found
If you are installing the NMCC/DECnet Monitor for the first time,
you will be prompted for the Greenwich Mean Time (GMT) offset for
your area.
The GMT offset is the number of hours that you have to add to your
local time to get Greenwich Mean Time.
For example, if your node is on the east coast of the United States
and your local time is Eastern Standard Time, your GMT offset is +5.
You would have to add five hours to your time to get Greenwich Mean Time.
* Please enter the current GMT offset for your timezone [0]: +1
%MCCEMS-I-CRELOGICALS, Creating file NMCCLOGICALS.COM
%MCCEMS-I-NMCCLOGICALS, Invoking NMCCLOGICALS.COM to define NMCC logical names
If you are creating the NMCCKERNEL account, the installation procedure
prompts you for the User Identification Code (UIC), which consists of
two integers separated by a comma. The system manager should select
the UIC for the NMCCKERNEL account. The UIC should not belong to another
user or VMSINSTAL will terminate the installation. The first number in
the UIC pair should not be between 1 and 8 because these are reserved
for system UICs. The following are examples of valid UICs:
[123, 456]
[12, 3]
The NMCC installation procedure may create an account under which the
NMCC Kernel runs. All privileges and quotas required by the Kernel are
set up in this account by the installation procedure. If this account
does not already exist, and you wish it to be created, then you should
answer YES to the following question. Otherwise answer NO or just press
RETURN.
* Would you like the NMCCKERNEL account to be created [NO]? y
%MCCEMS-W-KERNELACCTEXISTS, An NMCCKERNEL account already exists:[300,3]
* Do you want to change the UIC for the kernel account [no]?
*************************************************************
This installation requires the creation of the NMCCKERNEL
account. You MUST choose a password for this account.
**************************************************************
* Please press RETURN to continue:
*************************************************************
The entire installation will FAIL if you do not enter a valid
password for the NMCCKERNEL account. You will be given
3 chances to verify your password. This installation
procedure requires at least 15 characters for the
RDB$REMOTE password. Valid characters for a password are:
A through Z
a through z
0 through 9
$ (dollar sign)
_ (underscore)
As with the DCL SET PASSWORD command, your input will not
appear on the terminal. And to protect against typing errors
that are not seen when entering the password, you must enter
the password twice.
*************************************************************
>
* Please enter PASSWORD to be used for NMCCKERNEL account:
>
>
* Please verify the PASSWORD entered for NMCCKERNEL account:
>
%VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named NMCCKERNEL.
%UAF-I-MDFYMSG, user record(s) updated
************************************************************************
* The account NMCCKERNEL has been created solely for running the *
* NMCCKERNEL. You MUST change the NMCCKERNEL password the first time *
* the account is used. *
************************************************************************
%VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[NMCC]/LOG/OWNER_UIC=[300,3]/PROTECTION=(S:WRE,O:RWE,G:RWE,W:RE).
%CREATE-I-EXISTS, VMI$ROOT:[NMCC] already exists
Displaying DECmcc LTM Installation Information...
******************************************************************
The files in the distribution kit will be copied to the
appropriate system directories.
File System directory
---------------------- ----------------
LTM$SETUP.COM SYS$COMMON:[DECSERVER]
LTM$LOAD_CONFIG.COM SYS$COMMON:[DECSERVER]
LTM$TYPE_NAME.DAT SYS$COMMON:[DECSERVER]
LTM$MC_NAME.DAT SYS$COMMON:[DECSERVER]
LTM$ADDR_NAME.DAT SYS$COMMON:[DECSERVER]
LTMLIS0200.SYS SYS$COMMON:[DECSERVER]
LTM$REGRESSION.COM SYS$COMMON:[SYSTEST.LTM]
LTM$REGRESSION.BMK SYS$COMMON:[SYSTEST.LTM]
LTM$IVP.COM SYS$COMMON:[SYSTEST]
LTM$UI.EXE SYS$SYSTEM:
LTM012.RELEASE_NOTES SYS$HELP:
---------------------- ----------------
NOTE
PLEASE place the command "$ @SYS$COMMON:[DECSERVER]LTM$SETUP"
in SYS$MANAGER:SYSTARTUP_V5.COM to initialize LTM logical names
at system boot time. Place it after the DECnet startup command.
******************************************************************
%VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSTEST.LTM].
%CREATE-I-EXISTS, VMI$ROOT:[SYSTEST.LTM] already exists
Asking DECmcc TSM Questions...
The TSM installation procedure normally enables service
on the first circuit that it finds on this node. This
allows the node to down-line load and up-line dump
terminal servers.
If you answer "No" to the following question, service
will not be enabled.
* Do you want service enabled in the installation procedure [YES]? n
TSM requires a directory where the TSM command files and library
will be installed. If the logical TSM$DEFAULT_DIRECTORY is
defined, the files will be installed in that directory. If
the logical is not defined, the files will be installed in a
directory on the system disk called SYS$COMMON:[DECSERVER].
The target directory for the files as it is now defined is shown
below.
Press return to use the value shown or enter a new disk and
directory specification.
* Target directory for TSM files [SYS$COMMON:[DECSERVER]]:
Linking Terminal Server Manager VMS V1.4...
DECmcc TSM requires defining and setting OBJECT NML to
PROXY BOTH ALIAS OUTGOING ENABLED.
After the installation use AUTHORIZE to create proxy accounts for
all the TSM users (if you have not done so already).
VMSINSTAL asks no additional questions.
| |||||