When there is maintenance for SYSVIEW, the SYSVIEW regions and sometimes the SYSVIEW CICS monitor also needs to be recycled..
Only the recycle of the CICS regions, or SYSVIEW CICS monitor possibly cannot be done at the same time as the recycle of SYSVIEW itself..
Sysview all releases
It's not always possible to recycle a CICS region at he same time the SYSVIEW maintenance is activated.
The HOLDDATA provided with SYSVIEW PTF's define the steps to implement the specific changes to that PTF. Generally the following statements.
This PTF requires the SYSVIEW for CICS monitor to be recycled, or CICS to be recycled.
1. Apply the PTF.
2. Stop any CICS regions being monitored by SYSVIEW, or use the GSVT
(terminate) transaction to stop SYSVIEW for CICS within each region.
3. Stop the SYSVIEW STCs, GSSA, and any user sessions.
4. Deploy the PTF to your run-time libraries.
5. Start the SYSVIEW STCs, GSSA, and any user sessions.
6. Start any CICS regions being monitored by SYSVIEW, or use the GSVS
(start) transaction to start SYSVIEW for CICS within each region.
When a CICS module is actually updated it contains the following HOLDDATA statements.
This PTF requires the SYSVIEW for CICS monitor to be recycled, or CICS to be recycled.
1. Apply the PTF.
2. Stop any CICS regions being monitored by SYSVIEW, or use the GSVT
(terminate) transaction to stop SYSVIEW for CICS within each region.
3. Stop the SYSVIEW STCs, GSSA, and any user sessions.
4. Deploy the PTF to your run-time libraries.
5. Start the SYSVIEW STCs, GSSA, and any user sessions.
6. Perform a CICS NEWCOPY for program GSVCGSVS within each region if the CICS regions were not stopped.
7. Start any CICS regions being monitored by SYSVIEW, or use the GSVS
(start) transaction to start SYSVIEW for CICS within each region.
If there is no HOLDDATA indicating CICS was updated then simply stop and restart SYSVIEW.