Alternate Server Start Options

The deployment process allows for up to three sets of deployment disks (PRIMARY, ALTERNATE, and PREVIOUS). CA Mainframe VM Product Manager populates the chosen set of disks according to the “Type” value that is used on the VMDEPLOY. For example, deploying product materials to the primary disk space (PRIMARY type) populates the set of disks identified by tag names RUNTIME, ADMIN, CPUPDTS, and PUBLIC. Deploying product materials to an alternate disk space location (ALTERNATE type) populates based on the ALTRUNTIME, ALTADMIN, ALTCPUPDTS, and ALTPUBLIC tags. Deploying product material to a previous disk space (PREVIOUS type) populates the PREVRUNTIME, PREVADMIN, PREVCPUPDTS, and PREVPUBLIC tags. The user decides how they want to utilize this capability.

The user determines which set of disks gets executed by specifying the Runtime Environment tag for the server. The tag setting on installation is PRIMARY. You can switch the Runtime Environment tag to ALTERNATE or PREVIOUS.

Note: For best results, a system should be operating on the same set of deployable disks. In this situation, a CP is built with the appropriate cpupdates disk, a CMS/ZCMS is built with the same set of cpupdates, and the users have link accesses to the admin disk.

This section contains the following topics:

Start the CA Top Secret Server on an Alternate Runtime Disk

When product materials were deployed during installation, a runtime environment tag value (PRIMARY) in the VMSERVER NAMES file determined which set of deployed disks to use when the product server is next started. The Runtime Environment setting also controls which disks get IPLed by the server.

At any time, you can change this tag setting to start with alternate disks.

Follow these steps:

Enter the following command:
```
VMSERVER name
```
name

Specifies the user ID of the CA Top Secret server.

The NAMES file modification screen appears.
Specify one of the following values for Runtime Environment:

Primary

Starts from the primary version of the RUNTIME, ADMIN, CPUPDTS, and PUBLIC disk.

Alternate

Starts on the alternate version of the disks (altruntime, altadmin, altcpupdts, and altpublic).

Previous

Starts on the previous version of the disks (prevruntime, prevadmin, prevcpupdts, and prevpublic).
Press PF6 to change the VMSERVER NAMES file, and then press PF3 to exit the NAMES screen.
Restart the server by entering the following command:
```
XAUTOLOG server_ID
```
server_ID

Specifies the VM user ID of the CA Top Secret for z/VM server (typically TSSVM).

The server should now be able to IPL under the appropriate environment.