The following instructions describe the runm.tar.Z file.  This will allow a user to pipe a
password to the ./runm command, thur the command line.  By having the ability to pipe a 
password to the ./runm command, this will give the VR administrator the ability to automate
the start/stop of VR thur a crontab file.  

-----------------------------------------------------------------------------------------------
For a Vault Registry System That Is Already Configured
-----------------------------------------------------------------------------------------------


For a Vault Registry system that has already been configured, complete the following steps to 
apply the "enhanced" runm filesets:

1.  Stop Vault Registry by issuing the runm command with the appropriate switches. See the "Vault 
    Registry System Operations Guide" for instructions.
    
2.  Prepare the runm filesets: 
          a.  Place the "runm.tar.Z" file in a directory (for example, /local/ptf or /temp), and cd to that
                directory. The directory you choose is not important. However, after using the files, you 
                should retain them as a precaution. 

          b.  Uncompress the runm.tar.Z file by issuing the following: 

                uncompress runm.tar.Z

          c.  Extract the files from the tar file by issuing the following: 

                tar -xvf runm.tar

3.  Apply the filesets: 
          a.  As root, issue the smit update_all command to begin the installation of the files: 

               smit update_all

          b.  In SMIT, enter the directory where you placed the PTF files during Step 2a above (for 
                example, /local/ptf or /temp).  A screen appears, prompting you for further information.  
                Normally you can take the defaults, but you may want to specify "No" to the Commit 
                Software Updates? question.

          c.  Complete the prompts and click OK.
  
4.  Verify the fix by issuing the following at the system prompt: 

	lslpp -l | grep irg

	For each language that your Vault Registry system supports, you should see something 
	similar to the following: 
 
		irg.regapp.us.main		2.2.209.2  APPLIED    IBM Vault Registration           
		irg.regapp.us.msg.en_US	2.2.209.1  APPLIED    IBM VR Application English       
		irg.vc.us.main			2.2.209.2  APPLIED    IBM Vault Controller Strong 

5.  Change Directory to /usr/lpp/irg/bin.

6.  Verify that you have the new runm.tpl with the size 873.

7.  Back up the old runm by copying it and renaming it.	

8.  Update the new runm.tpl by doing the diff command between the two files and update runm 
     accordingly.

9.  After the Vault Registry system has been updated, test Vault Registry by issuing the runm 
     command with the appropriate switches or by creating a crontab file.  Us the following 
     commands to test the VR system with the runm command.

	su - irguser
	cd   /usr/lpp/irg/bin      THEN TYPE AT COMMAND LINE:
	echo Secure98  |  ./runm -d   -a  -x  (or    -u   -a   -x)


----------------------------------------------------------------------------------------------
For a Vault Registry System That Is Not Yet Configured
----------------------------------------------------------------------------------------------

For a Vault Registry system that has not been configured, complete the following steps:


1.  Install Vault Registry according to the instructions in the "Installation and Configuration Guide", 
    but do not start the Configuration applet.

2.  Prepare the fileset: 
      a.  Place the runm.tar.Z file in a directory (for example, /local/ptf or /temp), and cd to that 
           directory. The directory you choose is not important. However, after using the fix files, you 
           should retain them as a precaution. 

      b.  Uncompress the runm.tar.Z file by issuing the following: 

		uncompress runm.tar.Z

      c.  Extract the files from the tar file by issuing the following: 

		tar -xvf runm.tar

3.  Apply the fix: 
      a.  As root, issue the smit update_all command to begin the installation of the filesets: 

                smit update_all

      b.  In SMIT, enter the directory where you placed the PTF files during Step 2a above (for 
            example, /local/ptf or /temp).  A screen appears, prompting you for further information. 
            Normally you can take the defaults, but you may want to specify "No" to the Commit 
            Software Updates? question.

      c.  Complete the prompts and click OK.

4.  Verify the fix by issuing the following at the system prompt: 

	     lslpp -l | grep irg

	For each language that your Vault Registry system supports, you should see something 
	similar to the following: 

	irg.regapp.us.main                      	2.2.209.2  APPLIED    IBM Vault Registration           
	irg.regapp.us.msg.en_US       	2.2.209.1  APPLIED    IBM VR Application English       
	irg.vc.us.main        		2.2.209.2  APPLIED    IBM Vault Controller Strong 


5.  Continue with the Vault Registry configuration procedures. 

   
6.  After the Vault Registry system is configuried, you may test the system by running a contab file 
    or the following command.
	su - irguser
	cd   /usr/lpp/irg/bin      THEN TYPE AT COMMAND LINE:
	echo Secure98  |  ./runm -d   -a  -x  (or    -u   -a   -x)