gtpd1m3f | Database Reference |
The commands are used to display entries in the coupling facility locking table (CFLT) and manage the CFs in a locking configuration. The following lists the CF locking commands and their functions:
See TPF Operations for more information about these commands.
This section shows a scenario of how you might use the CF commands to manage locks in a CF locking configuration by providing examples that span a series of commands.
Example 1: In the following example, two CFs are added to a processor configuration. First, a CF named CFONE, which is attached to symbolic device address (SDA) FF00, is added. Then, a CF named CFTWO, which is attached to SDA FE00, is added. Both CFs are then added to the locking configuration. The size of the CF list structure for locking on both CFs is 1200 4-K blocks. All the online modules on both the basic subsystem (BSS) and the WP subsystem are then migrated to use the CFs for locking. The general data set (GDS) modules on both the BSS and the WP subsystem are then migrated to use the CFs for locking.
+--------------------------------------------------------------------------------+ |User: ZMCFT ADD CFONE FF00 | |System: MCFT0001I 18.54.45 CFMADD - COUPLING FACILITY CFONE ADDED - | | 2 PATHS EXIST | | | |User: ZMCFT ADD CFTWO FE00 | |System: MCFT0001I 18.54.45 CFMADD - COUPLING FACILITY CFTWO ADDED - | | 2 PATHS EXIST | | | |User: ZCFLK ADD CFONE SIZE 1200 | |System: CFLK0002I 18.54.45 CFLO - COUPLING FACILITY CFONE WAS ADDED TO THE | | LOCKING CONFIGURATION | | | |User: ZCFLK ADD CFTWO SIZE 1200 | |System: CFLK0002I 18.54.45 CFLO - COUPLING FACILITY CFTWO WAS ADDED TO THE | | LOCKING CONFIGURATION | | | |User: ZCFLK MIGRATE ONL TO CF | |System: CFLK0004I 18.54.45 CFLW - ZCFLK MIGRATE PROCESSING COMPLETE | | | |User: WP/ZCFLK MIGRATE ONL TO CF | |System: CFLK0004I 18.54.45 CFLW - ZCFLK MIGRATE PROCESSING COMPLETE | | | |User: ZCFLK MIGRATE GDS TO CF | |System: CFLK0004I 18.54.45 CFLW - ZCFLK MIGRATE PROCESSING COMPLETE | | | |User: WP/ZCFLK MIGRATE GDS TO CF | |System: CFLK0004I 18.54.45 CFLW - ZCFLK MIGRATE PROCESSING COMPLETE | | | +--------------------------------------------------------------------------------+
Example 2: In the following example, a range of modules is migrated to use CF for locking.
+--------------------------------------------------------------------------------+ |User: WP/ZCFLK MIGRATE 01E.021 TO CF | |System: CFLK0004I 20.54.45 CFLW - ZCFLK MIGRATE PROCESSING COMPLETE | | | +--------------------------------------------------------------------------------+
Example 3: In the following example, one module is migrated to use a control unit (CU) for locking.
+--------------------------------------------------------------------------------+ |User: ZCFLK MIGRATE 047 TO CU | |System: CFLK0004I 18.54.45 CFLW - ZCFLK MIGRATE PROCESSING COMPLETE | | | +--------------------------------------------------------------------------------+
Example 4: In the following example, the CF named CFTWO is deleted from the locking configuration. By mistake, an attempt is made to delete the CF named CFONE from the locking configuration before all modules have been migrated to use CUs for locking.
+--------------------------------------------------------------------------------+ |User: ZCFLK DEL CFTWO | |System: CFLK0003I 18.54.45 CFLDEL - COUPLING FACILITY CFTWO WAS DELETED FROM | | THE LOCKING CONFIGURATION | | | |User: ZCFLK DEL CFONE | |System: CFLK0031E 18.54.45 CFLDEL - DELETE ENDED - COUPLING FACILITY CFONE | | CANNOT BE DELETED - IT IS THE LAST CF IN THE | | LOCKING CONFIGURATION AND LOCKS STILL RESIDE ON IT | +--------------------------------------------------------------------------------+