CICS responses to file open requests

CICS® file control uses the backout setting from the file definition to decide whether to log before-images for a file request.

CICS takes the actions shown in the following list when opening a file for update processing in non-RLS mode—that is, the file definition specifies RLSACCESS(NO), and the operations parameters specify ADD(YES), DELETE(YES) or UPDATE(YES). If you set only READ(YES), BROWSE(YES) or both CICS does not make these consistency checks. These checks are not made at resource definition or install time.
  • If a file definition refers to an alternate index path and RECOVERY is ALL or BACKOUTONLY, the alternate index must be in the upgrade set for the base. This means that any changes made to the base data set are also reflected in the alternate index. If the alternate index is not in the upgrade set, the attempt to open the ACB for this alternate index path fails.
  • If a file is the first to be opened against a base cluster after the last cold start, the recovery options of the file definition are copied into the base cluster block.
  • If a file is not the first to be opened for update against a base cluster after the last cold start, the recovery options in the file definition are checked against those copied into the base cluster block by the first open. There are the following possibilities:
    • Base cluster has RECOVERY(NONE):
      • File is defined with RECOVERY(NONE): the open proceeds.
      • File is defined with RECOVERY(BACKOUTONLY): the attempt to open the file fails, unless overridden by an XFCNREC global user exit program, which can allow inconsistencies in backout settings for files that are associated with the same base data set.
      • File is defined with RECOVERY(ALL): the open fails.
    • Base cluster has RECOVERY(BACKOUTONLY):
      • File is defined with RECOVERY(NONE): the attempt to open the file fails unless overridden by an XFCNREC global user exit program to allow inconsistencies in backout settings for files associated with the same base data set.
      • File is defined with RECOVERY(BACKOUTONLY): the open proceeds.
      • File is defined with RECOVERY(ALL): the open fails.
    • Base cluster has RECOVERY(ALL):
      • File is defined with RECOVERY(NONE): the open fails.
      • File is defined with RECOVERY(BACKOUTONLY): the open fails.
      • File is defined with RECOVERY(ALL): the open proceeds unless FWDRECOVLOG specifies a different journal id from the base cluster, in which case the open fails.

Any failure to open a file against a data set results in a message to the console. If necessary, the recovery options must be changed. To change the recovery attributes (held in the base cluster block) of a VSAM data set, you can use the CEMT, or EXEC CICS, SET DSNAME REMOVE command. This deletes the base cluster block, so CICS has no record of prior recovery settings for the VSAM data set. The next file to open against this data set causes a new base cluster block to be built and, if the file is opened for update, the data set takes on the recovery attributes of this file.

The base cluster block, together with its recovery attributes, and the inconsistency condition that may be set if you are using XFCNREC, are preserved even when all the files relating to the block are closed, and across warm and emergency restarts.



dfht2c00179.html | Timestamp icon Last updated: Sunday, 4 June 2017