Installing Sentry Software's KMs on Open VMS

Objective

Unlike other operating systems, Open VMS does not provide an installation utility to install KMs. Therefore, the files are designed to be extracted and loaded manually.

To install any Sentry Software’s KM, the contents of the .tar must be extracted in the ‘PATROL$HOME’ directory.

Prerequisites

PATROL environment properly installed and operational.

Procedure

The procedure below is for Hardware Sentry KM for PATROL, file names may differ for other products.

1. Navigate to the existing PATROL$HOME directory:

   $ set def PATROL$HOME 

2. Locate the LIB directory:

   $ dir /col=1 
   
   Directory DS10$DKA0:[SYS0.SYSCOMMO.BMC.PATROL3] 
   
   ALPEXE.DIR;1 
   
   APP-DEFAULTS.DIR;1 
   
   BIN.DIR;1 
   
   CONFIG.DIR;1 
   
   DOC.DIR;1 
   
   LIB.DIR;1 
   
   LOG.DIR;1 
   
   MANAGE.DIR;1 
   
   PEMAPI.DIR;1 
   
   REMOTE.DIR;1 
   
   SECURE_CONFIG_SMITH-3181.LOG;1 
   
   SEN_SWSY8652_AGENT_REMOVE.SH;1 
   
   SW_SENTRY-OSC1-SMITH-3181.BUF;1971 
   
   SW_SENTRY-OSC1-SMITH-3181.BUF;1970 
   
   TMP.DIR;1 
   
   MSHW_VMS_1700.TAR;1 (Archive directory for BMC Hardware Sentry KM for Patrol)
   

3. Using VMSTAR.EXE, or any other tool of your choice, extract the archive content ($ tar xf MSHW_VMS_1700.TAR):

   $ tar ==  "$ SYS$COMMON:[USERS.ROOT]VMSTAR.EXE" 
   
   $ tar 
   
   VMS TAR V3.4-1  (Nov 29 2001) 
   
   usage (VMS  style): TAR tarfile file[,...] 
   
   Options: /HELP -- Print this text and exits 
   
   /LIST -- List contents of tarfile 
   
   /CREATE -- Create a tarfile 
   
   /EXTRACT -- Extract files from tarfile 
   
   /VERBOSE -- Display processed file info 
   
   /CONFIRM -- Prompt before store/extract 
   
   /BINARY -- Create binary files 
   
   /AUTOMATIC -- Automatically determine file type 
   
   /DOTS -- Maintain "." usage 
   
   /FORCE -- Forces copying of unsupported file  formats 
   
   /PADDING -- Adds padding block at the end of the  tar file 
   
   /ODS2 -- Restores files using ODS-2 naming  on ODS-5 volumes 
   
   /BLOCK_FACTOR -- Amount of 512 byte  records in a tar block 
   
   /DATE_POLICY -- Decide what times of extracted files 
   
   will be set: 
   
   [NO]CREATION 
   
   [NO]MODIFICATION 
   
   usage (UNIX style): tar -h|x|t|c[vwbzdo][f tarfile] [file [file...]] 
   
   Options:  h =  /HELP 
   
   t  = /LIST 
   
   c  = /CREATE 
   
   x  = /EXTRACT 
   
   v  = /VERBOSE 
   
   w  = /CONFIRM 
   
   b  = /BINARY 
   
   z  = /AUTOMATIC 
   
   d  = /DOTS 
   
   o  = /ODS2 
   
   b =  /BLOCK_FACTOR 
   
   f file -- Specify a tar file or magtape. Default is $TAPE 

4. Restart the PATROL Agent and load the desired KM.

Related Topics

• Forcing the KM to Run in Classic Mode
• How to Migrate Monitoring Studio X Policies from TrueSight to Helix Operations Management
• More Easily Identify Your Devices Monitored Through a Proxy in TrueSight / Helix Operations Management
• Determining the .si Adapter to Use to Monitor Pure Storage Systems with the Storage Analyzer KM
• Monitoring Remote Windows Hosts Without Credentials