Illustration of the quiesce flow across two CICS regions

Figure 1 illustrates the operation of the CICS® RLS quiesce operation. The notes that follow explain the numbered points.
Figure 1. The CICS RLS quiesce operation with the CICS quiesce exit program
This diagram illustrates the process described in the notes that follow. It shows 2 MVS images connected through one coupling facility, and using the same VSAM integrated catalog facility (ICF) catalog. CICS AOR1 is shown running in MVS1, and CICS AOR2 is running in MVS2, and each AOR is connected to the SMSVSAM server in its MVS image.In the note list that follows, steps 1, 2, and 3 are executed in AOR1; steps 4, 5, and 6 are executed in both AORs; steps 4a by both SMSVSAM servers; steps 7 and 8 are performed by the SMSVSAM server in MVS1 only.
Note:
  1. A suitably-authorized user application program (AOR1 in the diagram) issues an EXEC CICS SET DSNAME(…) QUIESCED command (or a terminal operator issues the equivalent CEMT command).

    If the command specifies the BUSY(NOWAIT) option, all phases of the quiesce operation are asynchronous, and the user application program continues processing.

    If the command specifies BUSY(WAIT), control is not returned to the user application program until SMSVSAM replies to CFQS that the quiesce function has completed (or failed).

  2. CICS file control (AOR1 in the diagram) invokes CFQS to send the quiesce request to SMSVSAM.
  3. The long-running CICS (AOR1) CFQS task passes the quiesce request to SMSVSAM across the control ACB interface using the IDAQUIES macro QUICLOSE function.
  4. SMSVSAM drives the CICS RLS quiesce exit program of each CICS region that has an open RLS ACB for the specified data set (as shown in both AOR1 and AOR2 in the diagram).
    Note: This also applies to the CICS region in which a quiesce request is initiated if it has open RLS ACBs for the data set. Thus an initiator can also be a recipient of a quiesce request.

    (4a) SMSVSAM uses the coupling facility to propagate the request to the other SMSVSAM servers in the sysplex.

  5. The CICS RLS quiesce exit program schedules a CICS region task (CFQR) to perform asynchronously the required quiesce actions in that CICS region.
  6. When CICS has closed all open RLS ACBs for the data set, CICS issues the "quiesce completed" notification (the IDAQUIES macro QUICMP function) direct to SMSVSAM through the control ACB interface.
  7. When all CICS regions have replied with the IDAQUIES macro QUICMP function, the SMSVSAM server that handled the original request (from AOR1 in the diagram) sets the quiesced flag in the ICF catalog. This prevents any files being opened in RLS mode for the data set, but allows non-RLS open requests that are initiated, either implicitly or explicitly, by user transactions.
  8. SMSVSAM returns to the CICS region that initiated the quiesce request. If the BUSY(WAIT) option was specified on the request, CFQS resumes the waiting application program.
The flow of an unquiesce request is virtually the same as that illustrated in Figure 1, with the following differences in operation:
  • As soon as SMSVSAM receives the unquiesce request from the initiating CICS region, it immediately sets the quiesce flag in the ICF catalog to the unquiesce state.
  • SMSVSAM invokes the RLS quiesce exit program of each CICS region registered with a control ACB to notify it of the change in the quiesce state.
  • The CICS RLS quiesce exit program returns a "quiesce completed" code to SMSVSAM immediately, and then passes the request to CFQR for processing.


dfht2c00212.html | Timestamp icon Last updated: Monday, 5 June 2017