Starting a PAC using the Command Line

You can start a Performance and Availability Cluster (PAC) using the command line utility casstart. You can use it to script the actions to automate starting a PAC.

Micro Focus recommends that you only remove items from a Scale-Out Repository (SOR) using the caspac utility. See caspac for more information.

In a PAC, you must use either /s:c (cold start) or /s:w (warm start) options when starting an instance. These options will override whatever the SIT settings are for TS or TD. Using the /s:c option will result in all queues being removed along with other data. Using the /s:w option will leave existing queues intact.

Note: If you omit the /s option, then the SIT settings for TS and TD are applied.

The process of cold starting a PAC will remove all existing data from each SOR in the PAC.

To start a PAC, perform the following steps:

Ensure that all regions that are part of the PAC are stopped.
Ensure that a Redis instance is started for each SOR that is referenced by the PAC. Only one Redis instance for the PAC Scale-Out Repository (PSOR) and one for each additional SOR models.
Cold start an enterprise server instance that is in the PAC¹ by specifying /s:c on the casstart command:
```
casstart /rregionName /s:c
```
Note: If you are unable to perform a cold start using casstart then you might need to use the caspac utility with the InitPac option. See caspac for more information.
You can start additional regions that are part of the PAC by performing a warm start:
```
casstart /rregionName /s:w
```

If an enterprise server instance is cold started and another instance is already running in the same PAC, then the start will be changed to a warm start. In this case, the following message will be written:

CASSI9027W Region initializing in Warm startup mode because PAC <PAC_NAME> is already active.

If this message occurs but there are no active regions in the PAC, then caspac should be used with the -aInitPac option to initialize the PAC.

A warm start leaves all data in the SOR intact. A warm start is the default start mode. You must specify /s:w in the casstart command to override SIT settings for TS and TD.

An enterprise server instance that has been cold started will read the CICS resources from its local resource definition file. At resource installation time, PSOR-supported resources, will be placed in the PSOR. See Configuration Restrictions for more information. Regions that are part of the PAC and are subsequently warm started will read those resources from the PSOR.

Resources that are not yet supported in the PSOR will be read from the local resource definition.

If an enterprise server instance is warm started after the PAC has been initialized and there are no other instances in the PAC running, then it will automatically cold start.

¹ This will remove all TSQs and TDQs from all SORs in the PAC; caspac only removes those in the PSOR.