New CICS Start Option to Recover and then shut down

Provide a new CICS start option that would start CICS, connect with all related resource managers (IMS, DB2, MQ, etc.), complete all recovery, and then shutdown without allowing work to start flowing into that CICS.

The current CICS startup options are designed to bring up CICS and get it ready to take on new work, but sometimes, we need to bring up CICS only to use emergency restart.

An example is when we shutdown CICS regions for an extended outage (IPL, other maintenance, batch window), but the region crashes before it can take a warm keypoint, leaving possible inflight UOWs. We must recover those UOWS before we allow batch to run or risk the batch failing and/or the batch updates later backed out when CICS does recover later in the cycle.

Our automation today restarts any region that doesn't have the DFHRM0204 so that it can go through recovery, but if the region was being shutdown, the automation then determines when it's safe to shut the region (DFHRM0206) and then brings the region down as was originally intended.

But the automation is complicated. In addition, we must ensure that work cannot flow into this recovering CICS and in an ARM situation, we use a special set of startup options to turn off IRCSTRT so that work is not coming into a region we are trying to shutdown.

A new START=RECOVER option would reduce most of the complicated logic.