Remove usage of zFS clone function

Description

z/OS V1R13 was the last release that zFS supported the cloning file systems function. The zFS clone functions included the zfsadm clone and zfsadm clonesys commands. Also removed was the ability to mount any zFS file system aggregates that contain a cloned (.bak) file system. Additional changes as a result of the removal of the cloning file systems function are listed in Steps to take.

Table 1 provides more details about this migration action. Use this information to plan your changes to the system.

Table 1. Information about this migration action
Element or feature: z/OS Distributed File Service
When change was introduced: z/OS V1R13 was the last release for the function. The function was removed in z/OS V2R1. See IBM United States Software Announcemen 211-007t, dated February 15, 2011.
Applies to migration from: z/OS V1R13.
Timing: Before installing z/OS V2R2.
Is the migration action required? Yes, if you are using or have used the zFS clone function.
Target system hardware requirements: None.
Target system software requirements: None.
Other system (coexistence or fallback) requirements: If any system earlier than z/OS V2R2 mounts a zFS aggregate that contains a .bak (clone) file system in a shared file system environment, any catch-up mounts on a V2R2 system fail and z/OS UNIX function ships from the V2R2 system to the z/OS UNIX owning system.
Restrictions: None.
System impacts: None.
Related IBM Health Checker for z/OS check: None.

Steps to take

Follow these steps:
  1. Determine whether you have any .bak file systems. You should delete all .bak file systems before you bring zFS into the shared file system environment or before you IPL the V2R2 system. Minimally, you must ensure that no zFS aggregates that contain .bak file systems are mounted. You can do this by issuing a command like the following: 
    zfsadm lsfs | grep .bak
    You might see results as in this example: 
    PLEX.JMS.AGG1.bak (Not Mounted) 458 K alloc 458 K quota On-line 
PLEX.JMS.AGG2.bak (Not Mounted) 26 K alloc 26 K quota On-line
    This example shows that there are two zFS aggregates that contain a .bak file system: PLEX.JMS.AGG1 and PLEX.JMS.AGG2. In this case, unmount the .bak file systems (if they are mounted) and delete each .bak file system from the aggregate with a command similar to the following example: 
    zfsadm delete PLEX.JMS.AGG1.bak
    (The file system name is case-sensitive.) If the delete fails because the file system was not found, it probably means that the zFS aggregate is not attached. Attach it, delete the .bak file, and detach the aggregate.
  2. Determine whether any of your tools or application programs use any of the keywords that were removed from the zfsadm config or zfsadm configquery commands and remove them.
    • In zfsadm configquery, -auto_attach, -fsgrow, and -user_cache_readahead were removed.
    • In zfsadm config, -fsgrow and -user_cache_readahead were removed.
  3. Determine whether any of your tools or application programs use any of the zfsadm commands and remove them.
    • zfsadm create
    • zfsadm lsquota
    • zfsadm rename
    • zfsadm setquota
  4. Determine whether any of your tools or application programs use the following subcommand numbers for PFSCTL APIs, which are no longer valid, and remove them.
    • Clone File System (143)
    • Query auto_attach setting (183)
    • Query fsgrow setting (188)
    • Query user_cache_readahead (209)
    • Rename File System (140)
    • Set File System Quota (141)
    • Set fsgrow (172)
    • Set user_cache_readahead (162)
  5. (Optional step) The IOEFSPRM variables (auto_attach, fsgrow, user_cache_readahead) are ignored, but you can remove them from your configuration files if you want.

Reference information

For more information, see z/OS Distributed File Service zFS Administration.

Parent topic: Distributed File Service actions to perform before installing z/OS V2R2