Starting a PAC

PACs cannot be started with a single action. All enterprise server instances within the PAC need to be started individually. You can script the individual actions to automate the process.

Micro Focus recommends that you only remove items from a SOR using the caspac utility. See caspac for more information.

CAUTION:

Use the InitPac action on the caspac command with caution. It must only be used when all enterprise server instances in the PAC are stopped and you want to cold start the PAC.

There is only one method of cold starting a PAC, to do that you need to run caspac with the InitPac action and then run casstart with /s:c.

In a PAC, you must use either /s:c or /s:w 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.

When using the casstart command, use the /s option with either w or c for warm or cold starts respectively to override the SIT setting for cold or warm starts of a TS or TD. If the /s option is not used then the SIT settings for TS or TD will be 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 enterprise server instances that are part of the PAC are stopped.
Ensure that a Redis instance is started for each SOR that is referenced by the PAC. At least one Redis instance for the PSOR and one for each additional SOR models.
Run the following caspac command to initialize the PAC:
```
caspac -aInitPac=pacname -stype,host:port
```
Where the value for the -s option specifies the PSOR for the PAC, for example:
```
caspac -aInitPac=MyPac -sredis,127.0.0.1:6379
```
Note: This command will remove all data from the specified SOR. If the SOR contains TS or TD queue data, then it will be deleted.
Cold start an enterprise server instance that is in the PAC¹ by specifying /s:c on the casstart command²:
```
casstart /rregionName /s:c
```
You can start additional enterprise server instances that are part of the PAC using the following command:
```
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.

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, (this is limited to PCT, FCT, PPT, DCT, and TST) will be placed in the PSOR. Enterprise server instances 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.

² There is currently no option to cold start enterprise server instances via the user interface.