z/OS DFSMSdfp Storage Administration
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Fallback procedure

z/OS DFSMSdfp Storage Administration
SC23-6860-01

Recommendation: Do not use this procedure for normal or abnormal disabling of the SMSVSAM server.

Follow these steps to fall back from VSAM RLS processing:

  1. Ensure that there are no outstanding recovery requirements.

    Use the access method services SHCDS LISTRECOVERY or LISTSUBSYSDS command to list all current recovery requirements known to SMSVSAM. Any recovery must be completed prior to continuing with fallback processing, or data integrity is compromised. SMSVSAM is not aware of certain subsystem-related recovery, such as indoubt resolution.

    See z/OS DFSMS Access Method Services Commands for a complete description of the access method services SHCDS command.

    _______________________________________________________________

  2. Activate an SMS configuration where all nonblank cache set specifications on storage classes are changed to blank cache set specifications.

    The SMS configuration should not include any cache sets defined in the base configuration. This ensures that the CF is only used for access to data sets which are already bound to a CF cache structure.

    _______________________________________________________________

  3. Ensure that you have no running applications which specify VSAM RLS processing, either specified in an ACB or using JCL.

    _______________________________________________________________

  4. Quiesce all CF cache structures.
    Use the VARY SMS command, as follows:
    VARY SMS,CFCACHE(CF_cache_structure_name),QUIESCE
    where:
    CF_cache_structure_name
    Is the name of the cache structure being quiesced.
    Enter this command for each CF cache structure in your configuration. Use the D SMS,CFCACHE command to verify that all CF cache structures are quiesced.

    _______________________________________________________________

  5. Reset RLS indicators in all applicable catalogs, using the SHCDS CFRESET command.

    _______________________________________________________________

  6. When you delete RLS information in the catalog, revert to CICS® FCT definitions, even if the CICS level remains unchanged.

    Be sure to complete all the preceding steps before continuing with the procedure to permanently shut down SMSVSAM and delete all knowledge of the lock structure and sharing control.

    _______________________________________________________________

  7. Change the value for the RLSINIT parameter in parmlib member IGDSMSxx to NO in all applicable parmlib members and activate the change.

    _______________________________________________________________

  8. Enter the following MVS command to disable the SMSVSAM server:
       *ROUTE ALL V SMS,SMSVSAM,TERMINATESERVER
    Reply C to any outstanding IGW418D message. If FORCE SMSVSAM,ARM does not disable the SMSVSAM server, use FORCE SMSVSAM.

    _______________________________________________________________

  9. Enter the following command to complete the VSAM RLS fallback procedure:
       VARY SMS,SMSVSAM,FALLBACK
    This command issues message IGW523 to request confirmation. You should first ensure that all SMSVSAM servers are disabled, then respond with:
       FALLBACKSMSVSAMYES
    Any other response cancels the command.
    The FALLBACK command forces all lock table connections, and deletes the lock structure and the sharing control group, IGWXSGIS. If any of these steps fail, or if another FALLBACK command is already in process, the command is rejected.
    Note: This command deletes the IGWLOCK00 lock structure, but does not delete any secondary lock structures. To delete secondary lock structures, use the SETXCF FORCE DELETE command. To completely fall back, you must also remove all secondary lock structures from the CFRM policy.

Fallback is complete when message IGW524I is issued to the console that issued the FALLBACK command.

See Understanding the product environment for VSAM RLS for a list of rules and considerations to follow if you are also falling back to different CICS, CICSVR, or DFSMS releases.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014