Previous | Contents | Index |
The following discussion outlines the steps in the PMDF installation procedure. Refer to Chapter 2 for a sample installation dialogue.
vmslicense.com
procedure located in the
SYS$UPDATE:
directory. You need a PAK for PMDF (PMDF or
PMDF-MTA). If you will also be installing PMDF-FAX, PMDF-DIRSYNC,
PMDF-LAN, PMDF-MB400, PMDF-MSGSTORE, PMDF-MR, PMDF-POPSTORE, PMDF-X400,
PMDF-TLS, or PMDF-XGS, then a PAK will also be required for each of
those products.
If you already have existing PAKs, you should check to make sure they
are valid for this release. Use the SHOW LICENSE command to check the
release date of the existing PAKs, and make sure the date is later than
release date of the new version. New PAKs are issued when your
maintenance contract is renewed, not when new versions of software is
released. If you have received new PAKs at your renewal time, you
should register the new PAKs. First delete or disable the old PAKs,
then unload the old PAKs and load the new PAKs. For example, if you
received a new PMDF PAK, do the following:
$ @SYS$UPDATE:vmslicense . . [register the new PAK] . $ LICENSE DISABLE PMDF-productname/PRODUCER=INNOSOFT/AUTHORIZATION=xxx $ LICENSE DELETE PMDF-productname/PRODUCER=INNOSOFT/AUTHORIZATION=xxx $ LICENSE UNLOAD PMDF-productname/PRODUCER=INNOSOFT $ LICENSE LOAD PMDF-productname |
PMDF-productname
is the name of the PMDF
product, e.g., PMDF-MTA, PMDF, PMDF-LAN, PMDF-FAX, PMDF-MR,
PMDF-MB400, PMDF-MSGSTORE, PMDF-POPSTORE, PMDF-X400, or PMDF-XGS,
etc., and where xxx
is the authorization
number of the old PAK. The last two steps, LICENCE UNLOAD and LOAD must
be done on all systems running PMDF and using the new PAKs.
$ @SYS$UPDATE:vmsinstal |
VAX/VMS Software Product Installation Procedure V6.2 It is date at time. Enter a question mark (?) at any time for help. |
* Where will the distribution volume be mounted: |
* Products: |
PMDF062
and press
[RETURN].
* Options: |
* Are you ready: |
YES
followed by a [RETURN]
when the volume is ready for mounting. This question will not appear
when installing from disk. The following messages are then displayed:
%MOUNT-I-MOUNTED, PMDF062 on _DDCU: The following products will be processed: PMDF V6.2 Beginning installation of PMDF V6.2 at time %VMSINSTAL-I-RESTORE, Restoring product saveset A... |
Product: PMDF-MTA or PMDF Producer: INNOSOFT Version: 6.2 Release Date: date * Does this product have an authorization key registered and loaded? |
YES
if you have already registered
and loaded the PMDF license PAK. If you have not already registered and
loaded the PMDF license PAK, then answer
NO
now. Do not attempt to install PMDF if
you have not loaded your license PAKs. Do not upgrade PMDF if you do
not have an appropriate PMDF license PAK. An appropriate license PAK
will have a release date which is in the future. Any version of PMDF
released after the release date of your PAK will not run.
* Do you want to purge files replaced by this installation [YES]? |
NO
if you do not want to purge
replaced files. Press [RETURN] or type
YES
if you want to purge files replaced
by this installation of PMDF. YES
to the next question.
Install Alpha VMS executables as well as VAX VMS executables [NO]? |
NO
if you do not
want to install Alpha VMS support. If you are doing the installation
from an OpenVMS Alpha system, you are asked whether or not you want to
install the VMS VAX executables.
* Enter the device and directory [SYS$SYSDEVICE:[PMDF]]: |
--------------- Attention -------------------- The logical name PMDF_ROOT is already defined. It refers to the directory directory-path ---------------------------------------------- * Do you want to install the new files at that same location [YES]? |
NO
and to the next prompt specify the
name of a different disk or directory or both:
* Enter the device and directory [SYS$SYSDEVICE:[PMDF]]: |
* Username for the PMDF server account [PMDF]: |
* Does this account already exist [NO]? |
YES
if your PMDF server account
already exists, otherwise, press [RETURN] or type
NO
. If the PMDF server account does not
exist, the procedure prompts for a password and UIC for the new account
to be created:
* Password for the PMDF server account: * Numeric UIC for the PMDF server account [[375,1]]: |
* Username for the PMDF user account [PMDF_USER]: |
* Does this account already exist [NO]? |
YES
if your PMDF user account
already exists, otherwise, press [RETURN] or type
NO
. If the PMDF user account does not
exist, the procedure prompts for a password and UIC for the new account
to be created:
* Password for the PMDF user account: * Numeric UIC for the PMDF user account []: |
* Queue PMDF jobs should run in [MAIL$BATCH]: |
* Username for PMDF service jobs [SYSTEM]: |
* Batch queue DELIVER jobs should run in [SYS$BATCH]: |
mail.delivery
files. This queue must be an OpenVMS batch
queue; queues handled by the PMDF Process Symbiont are not suitable
candidates for handling jobs created by DELIVER.
* Current timezone for this site [default]: |
Time Zone | Abbreviation | Offset from GMT |
---|---|---|
Universal Time | GMT | +0000 |
Eastern standard time | EST | -0500 |
Eastern daylight time | EDT | -0400 |
Central standard time | CST | -0600 |
Central daylight time | CDT | -0500 |
Mountain standard time | MST | -0700 |
Mountain daylight time | MDT | -0600 |
Pacific standard time | PST | -0800 |
Pacific daylight time | PDT | -0700 |
shhmm
, where s
is
either "+
" or "-
",
hh
is the hours offset, and
mm
is the minutes offset.
The time zone string is equated with the system logical PMDF_TIMEZONE
which is declared within the command file
SYS$STARTUP:pmdf_startup.com
. Whenever you change your
clock from standard to daylight savings time or vice versa, you will
have to alter the definition of this logical by editing and reexecuting
the file SYS$STARTUP:pmdf_startup.com
.
If the PMDF_TIMEZONE logical does not exist (for example if you choose to deassign it in pmdf_com:pmdf_site_startup.com ), then
PMDF looks for the following system logicals to determine the local
time zone. First it looks for SYS$LOCALTIME, then if that is not
defined, it looks for SYS$TIMEZONE_DIFFERENTIAL and SYS$TIMEZONE_NAME.
|
* Do you want a system help entry for the PMDF DCL command [YES]? |
* Do you want to have PMDF_STARTUP.COM run after the installation completes [YES]? |
YES
to
execute the startup procedure automatically. Type
NO
to prevent the startup procedure from
being executed by the installation. If you plan to run the automatic
configuration generator after installing PMDF, be sure you accept this
action or manually execute SYS$STARTUP:pmdf_startup.com
before using the configuration procedure.
* Do you wish to install PMDF-TLS [YES]? * Do you wish to install PMDF-MR [YES]? * Do you wish to install PMDF-FAX [YES]? * Do you wish to install PMDF-LAN [YES]? * Do you wish to install PMDF-X400 [YES]? * Do you wish to install PMDF-MB400 [YES]? * Do you wish to install PMDF-XGS [YES]? * Do you wish to install PMDF-DIRSYNC [YES]? * Do you wish to install the PMDF Message Store [YES]? The mail RFC files will require 26570 blocks. * Do you wish to install the mail RFC files [YES]? The HTML format documentation will require 28493 blocks. * Do you wish to install HTML format documentation [YES]? |
YES
to install them now. (Note
that you will not be asked about PMDF-MB400 if you answered
YES
to install PMDF-X400. Note also that
PMDF-MSGSTORE and PMDF-POPSTORE are partially installed automatically
with the base PMDF kit, though they allow only limited use unless
separate PMDF-MSGSTORE or PMDF-POPSTORE licenses, respectively, are
installed.) You will be asked if the license PAKs for PMDF-TLS,
PMDF-MR, PMDF-FAX, PMDF-LAN, PMDF-MB400, PMDF-X400, PMDF-XGS,
PMDF-DIRSYNC, PMDF-POPSTORE, or PMDF-MSGSTORE are registered and
loaded, and given a chance to exit the installation procedure if you
have not already done so.
Customers who are using any direct PC channels from before the product restructuring of September 1994 should answer YES to the PMDF-LAN question.
|
Previous | Next | Contents | Index |