Modules
These modules are involved in z/OS® Communications Server persistent sessions recovery.
ZC (terminal control) together with the following modules:
| Module | Function |
|---|---|
| DFHZCGRP | Program initiated by task CGRP to set up the start type and to call DFHZGRP during initialization. It then analyses the response from DFHZGRP and decides if CICS® can continue or not. |
| DFHZGCA | Sets the appropriate ZC control blocks to reflect the currently agreed Change Number Of Session (CNOS) values for an LU6.2 connection. |
| DFHZGCC | Performs catalog and retrieval of CNOS data. This module is called when CICS needs either to store or to recover CNOS values. During a CICS run, all CNOS values are written to the global catalog. Under normal circumstances they are not needed. However, if a persistent sessions restart is performed, it is necessary to recover the CNOS values that were in operation at the time of the CICS failure. This recovery is achieved by having a record on the global catalog that can be read in during PRSS restart and used to restore the sessions to their state before failure. This module handles the maintenance of the CNOS records during normal CICS operation and the recovery of the records during PRSS recovery. |
| DFHZGCN | Handles the process of LU6.2 Change Number Of Sessions (CNOS) negotiation, acting as either the source or target end of the conversation, and calls DFHZGCA to action the resulting changes. |
| DFHZGDA | Takes control of APPC conversations that have
persisted across a CICS failure,
and ensures that they are ended cleanly, by issuing a Deallocate(Abend)
informing the partner LU that the CICS transaction
has abended. If DFHZGDA is working correctly the CICS failure and restart is transparent to the partner LU, which understands only that the CICS transaction with which it was communicating has ended. DFHZGDA also performs REJECT_ATTACH processing for synclevel 2 conversations that are started by the partner before Exchange Lognames has been done after a persistent sessions restart. |
| DFHZGPC | Performs recovery of CNOS values for modegroups.
This module is called when CICS is performing a persistent sessions (PRSS) restart. When a PRSS restart is performed, it is not enough to recover the sessions. It is also necessary to recover the CNOS state that the sessions had before the CICS failure. DFHZGCC will have maintained a record of the CNOS state on the global catalog. This record is now used in this module in an attempt to restore CNOS values. |
| DFHZGPR | The role of DFHZGPR is to update the global catalog whenever it is necessary to
add, delete, or test for a record indicating that an APPC connection has a Persistent Resource
associated with it. A Persistent Resource can be defined as some session state, or piece of work upon which the partner LU depends, and which will be lost if CICS fails. The only Persistent Resource so far identified is a shipped AID. Before persistent sessions, the failure of the APPC session tells the partner that these resources have been lost, and drives his recovery. With the advent of persistent sessions, it is necessary for a persisting CICS to know that an APPC session had a Persistent Resource associated with it, so that the connection can be unbound (to drive the partner's clean up) and then rebound. |
| DFHZGRP | Initialize z/OS Communications
Server persistent sessions. DFHZGRP is a domain subroutine but is called by DFHZCGRP (task CGRP) during initialization. DFHZGRP is called during ZC initialization or when the z/OS Communications Server ACB is opened dynamically by CEMT SET VTAM® OPEN or EXEC CICS SET VTAM OPEN by DFHEIQVT. The module performs
these tasks:
|
| DFHZGSL | Informs z/OS Communications
Server whether sessions are to persist or not. This module is called when CICS needs to set, unset, or change the Persistent Sessions PSTIMER value. |
| DFHZGUB | Issue CLSDST or TERMSESS for individual NIBs in
a NIBLIST. This module is called by DFHZGRP to unbind NIBs in
a NIBLIST in two ways:
|
| DFHZXPS | DFHZXPS handles Persistent Sessions recovery for
APPC sessions. It does not deal with non-APPC sessions, which are
dealt with by DFHZXRC. DFHZXPS is called by DFHZACT after OPNDST OPTCD=RESTORE has been issued successfully for a persisting APPC session. Both single and parallel APPC sessions are dealt with, but there is no difference in the processing. The task of DFHZXPS is to examine z/OS Communications Server session tracking data which was hung off TCTE_PRSS_CV29_PTR by DFHZGRP following a Persistent Sessions restart, and, if possible, to update the TCTTE to allow work to continue on the session. If it is not possible to determine the state of the session before system failure, or the session was not in a state which allows it to be recovered, the session is unbound. |
| DFHZXRC | DFHZXRC analyses the Session State Vector data that is hung off TCTE_PRSS_CV29_PTR by DFHZGRP during an emergency restart, for each persisting session. The necessary action to clean up and recover the session is then initiated. |