Specifying BWO using access method services
There is a BWO parameter on the access method services DEFINE CLUSTER statement.
About this task
- TYPECICS
- The data set is eligible for BWO in CICS®.
- NO
- The data set is not eligible for BWO.
- TYPEIMS
- The data set is eligible for BWO in IMS™, but CICS treats this as NO.
- TYPEOTHER
- The data set is eligible for BWO, but CICS treats this as NO.
- If you specify BWO(TYPECICS), and you have also specified LOG(ALL) and a forward recovery log stream name, LOGSTREAMID(logstream_name), your file is recoverable, and the status of the PTF is not important.
- If you specify BWO(TYPECICS), and the PTF has been applied, BWO processing is now enabled for all VSAM RLS files whether you have specified LOG(ALL), LOG(NONE) or LOG(UNDO).
- But if you specify BWO(TYPECICS), and the PTF has not been applied, and
you have not specified LOG(ALL) and a forward recovery log stream name, BWO
processing for RLS remains disabled for such files. To achieve BWO for the
file, you must either:
- apply the PTF,
- or specify LOG(ALL) and a forward recovery log stream name (if those actions are appropriate for the file in question).
If you omit the BWO parameter from the DEFINE statement, by default it is UNDEFINED in the ICF catalog, and the BWO attribute from the CICS file resource definition is used.
BWO(TYPECICS) is the equivalent of BACKUPTYPE(DYNAMIC) in a CICS file resource definition. All other values, including UNDEFINED, are treated by CICS as the equivalent of BACKUPTYPE(STATIC) in a CICS file resource definition. For simplicity, the CICS terms BACKUPTYPE(DYNAMIC) and BACKUPTYPE(STATIC) are used unless it is necessary to specifically mention the access method services BWO parameters.
The BWO options for the CSD are taken from the ICF catalog if they are defined there, and the system initialization parameters (CSDBKUP, CSDRECOV, and CSDFRLOG) are ignored.