BASEstartm Open DAS
for Modicon®
on OpenVMStm
Installation and User's Guide


Previous Contents Index

2.2 Installing the DAS

When your system meets all hardware and software requirements, you can install the DAS for Modicon programmable controllers. The installation takes from 1 to 5 minutes, depending on your system load and configuration.

Install the DAS for Modicon programmable controllers by using the following steps:

  1. Log in to a privileged system manager's account.
  2. Set the default directory to SYS$UPDATE:


    $  SET DEFAULT SYS$UPDATE                                           
    

  3. Invoke VMSINSTAL:


    $  @SYS$UPDATE:VMSINSTAL MODVVA031 ddcu: 
    

    where:

VMSINSTAL prompts you for information during the installation. Note that DECnet software does not need to be running to perform the installation procedure. The following is an example of the output from the installation:


 
        OpenVMS VAX Software Product Installation Procedure V7.2 
 
 
It is 22-MAR-2000 at 09:59. 
 
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: 
 
  MODVVA V3.1
 
 
        Beginning installation of MODVVA V3.1 at 10:00 
 
%VMSINSTAL-I-RESTORE, Restoring product save set A ... 
%VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. 
 
 
   Copyright 1994 Compaq Computer Corporation 
 
   Confidential computer software.  Valid license from Compaq or authorized 
   sublicensor required for possession, use or copying.  Consistent with FAR 
   12.211 and 12.212, Commercial Computer Software, Computer Software 
   Documentation, and Technical Data for Commercial Items are licensed to the 
   U.S. Government under vendor's standard commercial license. 
 
   BASEstar Open DAS for Modicon Programmable Controllers 
   installation procedure. 
 
   Checking for a valid license... 
 
 
 
        Product:      MODDAS-V 
        Producer:     DEC 
        Version:      1.0 
        Release Date: 01-JUN-1994 
 
 
* Does this product have an authorization key registered and loaded? y 
 
   Now checking OpenVMS version... 
 
 
   Now checking that OMNI is installed... 
 
 
   Now checking OMNI version... 
 
 
   Now checking OMNI logicals... 
 
 
   Now checking the OMNI integrator registration utility... 
 
 
* Do you want BASEstar Open support [YES]? 
 
   Now checking disk space... 
 
* Do you want to purge files replaced by this installation [YES]? 
* Do you want to run the IVP after the installation [YES]? 
 
   ---------------------------------NOTE------------------------------------ 
 
   During installation the file ODS_MOD_CONFIG.TEMPLATE is copied to the 
   ODS:[SCRIPTS] directory.  Copy and edit this file to create site specific 
   /PATH and /LINE directory definitions for devices at your installation. 
 
 
   ---------------------------------NOTE------------------------------------ 
 
   During installation the file BSTR_MOD_CONFIG.TEMPLATE is copied to the 
   BSTR$KIT:[ETC] directory.  Copy and edit this file to create site specific 
   VMD definitions. 
 
 
   Now modifying the ODS schema to add Modicon specific 
   object classes and attributes... 
 
 
Checking ODS Attribute Type Schema definitions ... 
 
 
Checking ODS Object Class Schema definitions ... 
 
 
Querying ODS Schema definitions ... 
 
Valid Schema definitions found in the attribute schema database as: 
OC ALIASED_NAME CN C L S O OU P_ADDR APC OWNER APT AEQ MAPV SY OBJ_ID BER PSAP S 
SAP TSAP N_ADDR AS_LIST DESCR VMD DOM DEL VN APPSN APROF VERSION NLEVEL MAX_CALL 
ED MAX_CALLING MAX_SEG CBB_LIST SS_LIST VENDOR MODEL REV INUM DN SHARE CONT_FILE 
 CAP_FILE PN REUSE ARG MON DOM_LIST VAR ATYPE ADDR_T ADDR_V PATH LINE STATION LI 
NE_NAME PORT ENQ_RETRIES NAK_RETRIES TIMEOUT SPEED PARITY MODEM TRACE KE_STATION 
 KE_TIMEOUT SLAVE_ADDRESS RETRIES SLAVE_ROUTING NODE_ADDRESS 
 
Valid Schema definitions found in the object class schema database as: 
TOP ALIAS C L O OU AP AE DSA DEVICE TAE OAE AS VMD DOMAIN PI NVAR UNVAR DH_LINE 
DH_PATH MODBUS_PATH MODPLUS_SLAVE_PATH MODPLUS_NODE_PATH MODBUS_LINE MODPLUS_LIN 
E 
 
Normal Completion. 
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... 
 
   Now registering BASEstar Open DAS for Modicon Programmable Controllers 
   with OMNI... 
 
 
   Copyright 1994 Compaq Computer Corporation 
 
   Executing the Installation Verification Procedure. 
 
 
   BASEstar Open DAS for Modicon Programmable Controllers installation 
   procedure has succeeded. 
 
 
        Installation of MODVVA V3.1 completed at 10:01 
 
 
        VMSINSTAL procedure done at 10:01 
 

2.2.1 Files Created During Installation

Table 2-2 lists the files created by the DAS for Modicon programmable controllers installation procedure, and the directories in which those files are placed.

Table 2-2 Files Created During Intallation
Directory Filename
ODS:[SCRIPTS] ODS_MOD_CONFIG.TEMPLATE
BSTR$KIT:[ETC] BSTR_MOD_CONFIG.TEMPLATE

2.2.2 Installation Messages

You may see VMSINSTAL messages during the installation procedure. The following messages are specific to the DAS for Modicon programmable controllers installation:

BADOMNI, The version of OMNI required is OMNI V3.1 or later.,

Explanation: Error. This version of the DAS is designed to work with OMNI V3.1 or later.
User Action: Install OMNI V3.1 or later and then reinstall the DAS.
BADVMS (Alpha), BASEstar Open DAS for Modicon Programmable Controllers must be installed under OpenVMS V6.1.,

Explanation: Error. The DAS is being installed on a version of OpenVMS that is less than OpenVMS V6.1.
User Action: Upgrade OpenVMS to the required minimum version and then install the DAS.
BADVMS (VAX), BASEstar Open DAS for Modicon Programmable Controllers must be installed under OpenVMS V6.1.,

Explanation: Error. The DAS is being installed on a version of OpenVMS that is less than OpenVMS V6.1.
User Action: Upgrade OpenVMS to the required minimum version and then install the DAS.
NETBLOCKS (VAX), BASEstar Open DAS for Modicon Programmable Controllers requires 1500 blocks after installation.,

Explanation: Error. There isn't enough space on the system disk to install the DAS.
User Action: Delete unneeded files and reattempt the installation.
NETBLOCKS (ALPHA), BASEstar Open DAS for Modicon Programmable Controllers requires 450 blocks after installation.,

Explanation: Error. There isn't enough space on the system disk to install the DAS.
User Action: Delete unneeded files and reattempt the installation.
NOETC, Unable to find BSTR$KIT:[ETC] directory.,

Explanation: Error. The directory to place the BASEstar Open configuration template for Modicon devices was not found.
User Action: Reinstall BASEstar Open to set up the BSTR$KIT:[ETC] directory.
NOLICENSE, No license found for this product - IVP will not be run.,

Explanation: Informational. A valid license was not found. The installation will continue, but the IVP will not be run.
User Action: Register and load a valid license for this product before attempting to use the DAS.
NOLOAD, License for this product not loaded - IVP will not be run.,

Explanation: Informational. The license for this product has not been loaded by the License Management Utility. The installation willl proceed, but the IVP will not be run.
User Action: Load the license using the License Management Utility before attempting to use the DAS.
NOOMNI, OMNI must be installed before BASEstar Open DAS for Modicon Programmable Controllers.,

Explanation: Error. The installation procedure could not verify that DEComni was installed on the system. OMNI installation is a prerequisite to the installation of this DAS.
User Action: Install OMNI V3.1 and then reinstall the DAS.
NOINTREG, Unable to find the integrator registration utility.,

Explanation: Error. OMNI provides a registration utility for DASes to use to register their presence with DEComni. This registration utility could not be found.
User Action: Reinstall OMNI to provide the required registration utility.
NOODS, Unable to find the directory for OMNI Directory Services.,

Explanation: Error. The installation procedure creates classes and attributes in the OMNI Directory Services database and this database could not be found.
User Action: Reinstall OMNI to set up the OMNI Directory Services directory.
NOSCRIPT, Unable to find ODS:[SCRIPTS] directory.,

Explanation: Error. The directory to place the ODS configuration template for Modicon devices was not found.
User Action: Reinstall OMNI to set up the OMNI Directory Services directory.
ODSINI, OMNI logicals have not been defined, attempting to define logicals.,

Explanation: Information. The DAS installation requires that certain OMNI logicals be defined and these logical names were not found. The installation procedure attempts to define the logical names by executing SYS$STARTUP:OMNI_LOGICALS.COM.
User Action: None.


Previous Next Contents Index