Example

Assume that object CICSTEST has a current status of DOWN and its desired status is DOWN. No further action (regarding CICSTEST) is necessary. However, if the operator changes the desired status of CICSTEST to UP, the following events occur:

1. The next time Control-O/COSMOS scans the Object database, it notes that CICSTEST’s current status (DOWN) does not match its desired status (UP).
2. Control-O/COSMOS checks the prerequisites for CICSTEST with a status of UP (for example, VTAM is up). If prerequisites are not satisfied, no action is performed on object CICSTEST.
3. If the prerequisites are satisfied, Control-O/COSMOS searches the Method database for the method to change CICSTEST’s status to UP. Assume that the Method rule found is named CICSUP.
4. A Control-O/COSMOS rule changes the status of CICSTEST to CHANGING.
5. Control-O/COSMOS triggers rule CICSUP to bring CICSTEST up.
6. When the CICSTEST address space starts, the following message is issued:

   IEF403I CICSTEST - STARTED - TIME=HH.MM.SS

   A Control-O/COSMOS rule detects this message, and changes the current status of CICSTEST to STARTING.

   See also the second note below.

7. The CICSTEST address space issues the following message:

   DFHSI1517 CICSTEST CONTROL IS BEING GIVEN TO CICS

8. A Control-O/COSMOS rule detects message DFHSI1517 and sets the current status of CICSTEST to UP.

Object CICSTEST remains in status UP, until the desired status is changed (for example, using an operator command, or using a Control-O/COSMOS online screen).

Note:

• When an object has a status of CHANGING or STARTING, Control-O/COSMOS detects that the desired and current statuses do not match. However, no action is taken since no methods are defined for a current status of CHANGING or STARTING.
• By default, all started tasks (STCs) are expected to issue a "ready" message like DFHSI1517 above, indicating that the product has finished initialization. COSMOS has an appropriate rule that is triggered by such a message and changes the STC’s status from STARTING to UP.

  However, some STCs do not issue a message to indicate that the product is ready. For such STCs, message IEF403I is enough to set their status to UP. STCs without a "ready" message should have a flag with the value N (ready message Not expected), indicating that IEF403I is enough to set their stats to UP. This flag is set in the STC’s object column (variable) COSRSRV1 in the Source Database (COSSTCSD, PRDSTCSD).