Use the VMADMIN Main Menu to perform product administration without logging on to each product individually.
Contents
Opening the Administration Menu
These instructions assume you have completed deployment for a product and are ready to run an administration task for that product.
- Log on to VMANAGER.
Enter the VMADMIN command. The system displays the VMADMIN Administration Menu. The menu displays a list of all CA product identifiers for which VMANAGER is a system administrator.
Select the product for which you want to perform administrative functions. If you have deployed more than one instance for a specific product, then a new screen is displayed so you can select the specific deployment to be processed. If there is only one deployed instance, this selection screen is skipped.
After selection, the bottom half of the screen displays product administration functions that you can perform. Press PF8 to scroll forward through the list of functions and PF7 to scroll backward.
Product Administration Tasks
This section describes each of the product administration functions.
Only the designated system administrator or tape librarian for a product can use a function for that particular product. The system administrator or tape librarian is identified by the ALOCAL tag in the VMSERVER NAMES file entry for the server.
CONFIG
Selecting this option places you in XEDIT in the product CONFIG file. After you file any changes, you are returned to the VMADMIN main menu.
CA VM:Archiver relies on a full screen interface for updating the product configuration. CA VM:Archiver must be running for you to update its configuration. Selecting the CONFIG function is equivalent to entering the CA VM:Archiver CONFIG command.
If you select the CONFIG function for CA VM:Secure or CA VM:Director, the system presents you with an additional screen. On this screen you identify which configuration file you want to examine or modify.- DASDINFO
This selection opens the VMACCT DASDINFO file and puts you in XEDIT mode. VMACCT DASDINFO is a control file that allows you to exclude full-pack minidisks from CA VM:Account minidisk accounting. Add the packs you want excluded, then save the changes using the FILE command. This returns you to the VMADMIN Administration Menu and puts the updated VMACCT DASDINFO file on the CA VM:Account 191 minidisk. CA VM:Account validates the file during minidisk accounting.
This selection is available from VMANAGER and the VMACCOUNT system administrator user ID.
Note: For more information about VMACCT DASDINFO file, see the CA VM:Account System Administrator Guide. - END
This selection is the same as issuing the product END command. If the product service virtual machine is disconnected, PROFRUN will issue a CP LOGOFF command. - MANAGERS
This option is available only for CA VM:Secure or CA VM:Director. It is equivalent to issuing the CA VM:Secure or CA VM:Director ADMIN MANAGERS command and allows you to edit the VMSECURE or VMDIRECT MANAGERS file. To use this option, you must have proper authorization in the CA VM:Secure or CA VM:Director configuration files. - REINIT
After editing a product configuration file, you may need to shut down and restart the product so that it will use the new configuration information. If this is necessary, the REINIT selection appears. REINIT can be used only from VMANAGER, and only if there is a PRODUCT VMSISERV VMANAGER record in the product configuration file. - SYSAD/TLIBR
This selection allows a system administrator or tape librarian to link and access the minidisks needed to serve as the system administrator or tape librarian for a product. Linking and accessing these minidisks is necessary for some utilities and reporting programs. - VMARCH
This selection is available only with CA VM:Archiver. It allows a system administrator to access the CA VM:Archiver System Administrator Main Menu. - VMBACKUP
This selection is available only with CA VM:Backup. It allows a system administrator to access the CA VM:Backup System Administrator Main Menu. - VMSERVER
Configuration definitions specific to a deployment, including information about deployed minidisks, reside in an entry in the VMSERVER NAMES file on the VMANAGER 1FF minidisk.
Minidisk definitions are used continually for product startup, maintenance, and administration; therefore, you must make sure they are accurate and up-to-date.
This section brings up a standard NAMES file panel so entries may be viewed or updated.
System Administrator User Startup
If you specified a user ID other than VMANAGER to act as a product system administrator, the PROFILE EXEC on that user ID was built to invoke a PROFRUN EXEC on its last line.
When you log on to this user ID, PROFRUN EXEC automatically verifies that the user ID is a valid system administrator or tape librarian user ID. It then automatically links and accesses the minidisks required to perform system administration or tape librarian functions.
If VMANAGER is your system administrator, issue the VMADMIN command to perform product administration.
VMADMIN EXEC
When you log on to a system administrator user ID or execute the VMADMIN command, processing performs the following actions:
- Releases and detaches any minidisks at virtual addresses 1F0 to 1FD.
- Links and accesses the proper minidisks for the product
- Allows you, if you are running a product on multiple user IDs, to specify the user ID for which you want to perform system administrator functions.
For example, if you are running CA VM:Account on user IDs VMACCT and VMJTEST and wish to set up VMJTEST for system administration, choose the user ID you want to administer on the panel that comes up. The System Administrator startup procedure links and accesses the appropriate minidisks and allows you to perform system administration for CA VM:Account running on service virtual machine VMJTEST.
Changing a System Administrator or Tape Librarian User ID
If you want to change your system administrator or tape librarian user ID, you need to update the user ID definition for the new administrator ID in the CP Directory as follows:
- Add a LINK to the VMANAGER 1FF minidisk at virtual address 1FF.
- Add a LINK to the VMANAGER 195 minidisk at virtual address 1FE.
- Copy the PROFRUN EXEC, from the A-DISK of the existing system administrator, to the A-DISK of the new administrator ID.
- Add an EXEC PROFRUN command as the last statement in the PROFILE EXEC of the new administration ID.
- Give the new system administrator (or tape librarian) permission to LINK to the system administration minidisks. These are defined as the value of the ADMINLINK tag for the entry in the VMSERVER NAMES file. This tag value consists of a set of three tokens for each administration disk. They are the owning user ID, the owner virtual address, and the read password. As an alternative to putting the read passwords in the NAMES file, you may establish External Security Manager permissions for the minidisk access, and use an asterisk as a placeholder token instead of a password.
Update the SYSADMIN and ALOCAL tags in the NAMES file entry to specify the new administrator user ID and A-DISK definition.
For example, to make NEWSYSAD the system administrator for CA VM:Secure, replace VMXSYSAD as the system administrator user ID using the VMSERVER command to bring up a NAMES file panel. Change the entry:Tag: sysadmin Value: VMXSYSAD Tag: alocal Value: VMXSYSAD 191
Replace the values with:
Tag: sysadmin Value: NEWSYSAD Tag: alocal Value: NEWSYSAD 191
- Change the authorization records in the product configuration file to authorize the new system administrator or tape librarian user ID.
Obtaining Links to Minidisks Required for System Administration
If you have CA VM:Secure installed, you can use the Rules Facility to allow the VMANAGER, system administrator, and tape librarian user IDs to link to the required minidisks without having passwords in the ADMINLINK tag in the VMSERVER NAMES file.
For installation, the VMANAGER user ID must be able to obtain a write (W) link to all product service virtual machine minidisks and all system administrator minidisks. For upgrades and future maintenance, the VMANAGER user ID must be able to obtain both write (W) and multi (M) links to all minidisks containing deployed or product materials.
Renaming a Product User ID
You may want to have two versions of a product installed on your system simultaneously. Here is an example. Suppose you are running Release 1.3 of product CA VM:Alpha (with a user ID of ALPHA) and want to install Release 2.0 (also with a user ID of ALPHA). It could simplify your effort if you could rename Release 1.3 user ID to ALPHAOLD and then install Release 2.0. Then, because each release has a unique user ID, you could run both versions of VM:Alpha.
The following instructions explain how to rename a product service virtual machine user ID:
- Bring down the product service virtual machine.
- Use your Directory Manager product or your own installation specific procedures to rename the deployed user ID to the new name. Also update any other user ID entries which LINK to minidisks owned by this user to LINK using the new user name. Products with worker virtual machines may have such LINK statements.
- Use the VMSERVER command to bring up a NAMES panel for the entry for the product server you are renaming.
- On the panel, modify all occurrences of the name of the server by substituting the new name. Modify the value of the NICK tag, and every other use of the name in every other tag value. Use PF6 to update the NAMES file.
- On the PUBLIC disk, usually the VMANAGER 193 minidisk, rename the product MODULE filename from the old user ID to the new one. In our example the file would change from ALPHA MODULE to ALPHAOLD MODULE.
- Copy any SFS directories associated with the old user ID to the new user ID. Now that you have renamed the existing user ID, you may install the new release. In our example, because you renamed the user ID for product CA VM:Alpha to ALPHAOLD you can install the new release of CA VM:Alpha to user ID ALPHA.