VM

How have you implemented CA VM:Operator in an SSI environment? Below you will find a draft of our recommendations. Do they differ from your experience? Do you have any best practices? Is the information below helpful and adequate?

Feel free to edit this document, adding information that you think could be of use to other customers. Please collaborate with us on creating a set of recommendations.

CA VM:Operator is, of course, designed to run on the system operator virtual machine, OPERATOR.  IBM supplies this virtual machine definition in an SSI installation as an IDENTITY userid with a MDISK 191 defined in each SUBCONFIG.  CA recommends that you continue to define the OPERATOR virtual machine with an IDENTITY directory entry and simply add or modify the MDISKs appropriately in order to satisfy the requirements needed to run CA VM:Operator.

The steps you will need to perform in order to deploy CA VM:Operator as an IDENTITY are as follows:

1. After installing the product material define and tailor a common product deployment using the VMDEFINE command. Then issue the VMALLOC SERVER OPERATOR ( DIRECT command to see the sizes of the MDISKs you will need to allocate manually.
2. Note the various OPERATOR MDISKs that are required. All of the MDISKs with link mode RR (read-only) can be defined in the IDENTITY on globally shared volumes because they are always linked read-only. Placing them in globally shared storage insures that the OPERATOR identities on each member will run the same level of code.
3. All of the MDISKs with link mode MR will have to be allocated in a SUBCONFIG on private volumes specific to each member. IBM has supplied a 191 minidisk definition that will have to be made larger. The 1D0 SYSLOG minidisk should be allocated with a size equal to or larger than the required size.
4. Issue the VMDEPLOY OPERATOR INIT command to cause a set of default configuration files and the startup PROFILE EXEC to be placed on the local OPERATOR 191 MDISK.  The minidisks defined on the DEPLOY tag are also populated with product material.
5. Then on the remaining member systems, logon VMANAGER and issue the VMDEPLOY OPERATOR INIT ONLY command to perform the deployment customization without populating the minidisks defined on the DEPLOY tag.
6. You will then have to tailor the various control files on the 191 MDISK for each instance of the OPERATOR IDENTITY.

Once CA VM:Operator has been fully deployed you will be able to start the product and run it as though it were on a separate VM system.  While the OPERATOR and VMYIAMOP MODULEs will reside on the VMANAGER PUBLIC disk (which is shared between all members), you will only be able to access the OPERATOR identity running on the same member as your virtual machine.