Default language.

Restarting a CAS

When a CAS is stopped, it leaves behind a small amount of storage in CSA that is used to process late arriving recovery operations.

That storage is reused when you perform a warm start of the CAS (for more information about starting a CAS, see Starting-a-CAS.

Related topic

Managing-the-coordinating-address-space-CAS

Important

If you perform a cold start of the CAS (COLD=Y), the CSA storage is abandoned. You should perform a cold start only when instructed to do so by BMC Customer Support, or if you have problems with a warm start. For more information about the COLD parameter, see the table in CAS-START-command-parameters.

Consideration after applying maintenance

The first time that you restart a CAS after applying maintenance, the CAS might determine that a cold start is required to fully implement the new maintenance. If that is the case, the following messages are displayed in the JES joblog during CAS initialization:

BBMZA098I CAS(WGH0) AUTOMATIC COLD START IN PROGRESS FOR THIS STARTUP
BBMZA104I CAS SSID(WGH0) COLD START IN PROGRESS

Important

If a cold start of the CAS is performed (either automatically or because COLD=Y was specified on the START command), you must stop and restart all connected PASs. A PAS cannot successfully reconnect to a CAS that has been cold started.

Consideration when you change the CAS libraries

If you modify the CAS JCL to specify new libraries, remember to update the library names in:

  • Corresponding PAS and UAS JCL
  • BMC AMI OpsCLIST

Make sure that the library names are correctly updated in all these places before you restart the CAS.

Important

The Alternate Access initialization EXEC, BBVINIT, includes the name of the BMC AMI Ops CLIST and its location. If you rename or relocate the CLIST, remember to update the BBVINIT EXEC.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*