ioefsutl converttov4

Purpose

ioefsutl converttov4 is a batch utility that converts a version 1.5 aggregate to a version 1.4 aggregate.

Format

ioefsutl converttov4 -aggregate name [-verbose][-level][-help]

Options

-aggregate name
Specifies the name of the aggregate to be converted. The aggregate name is not case-sensitive. It is translated to uppercase.
-help
Prints the online help for this command. All other valid options specified with this option are ignored.
-level
Prints the level of the ioefsutl command. This information is useful when you are diagnosing a problem. Except for -help, all other valid options that are specified with -level are ignored.
-verbose
Displays starting and ending messages of each directory being converted.

Usage notes for ioefsutl converttov4

  1. ioefsutl converttov4 cannot convert an aggregate that has been migrated from HFS to zFS with the bpxwmigf command.
  2. ioefsutl converttov4 cannot convert an aggregate that contains data that is encrypted or compress (or both). In this case, you first need to run zfsadm decrypt or zfsadm decompress.
  3. The ioefsutl converttov4 command is used when you need to convert a zFS version 1.5 aggregate to a version 1.4 aggregate. All extended (v5) directories are converted to v4 directories. You might use this if you need to run z/OS® releases prior to z/OS V2R1.
  4. ioefsutl converttov4 cannot convert the version 1.5 aggregate if it has grown larger than approximately 4 TB. In this case, you must copy subsets of the data one at a time into other version 1.4 aggregates using the z/OS UNIX shell command pax. Each subset must be copied into a separate version 1.4 aggregate that is less than 4 TB.
  5. ioefsutl converttov4 cannot convert a directory that contains more than 64K-1 subdirectories. In this case, you must copy subsets of the directory into separate directories contained in a version 1.4 aggregate.
  6. Converting a directory from an extended (v5) directory to a version 4 directory requires both versions of the directory to be on the disk at the same time, temporarily. If the aggregate becomes full during the allocation of the new directory, a dynamic grow is attempted. See Dynamically growing a compatibility mode aggregate for information about controlling the dynamic growth of an aggregate. If there is not enough space to complete the conversion, the new directory is deleted and the conversion operation fails.
  7. The old directory is deleted when the conversion is completed. The resulting new directory can possibly require more space than the old directory, and could also possibly require less space than the old directory. Results will vary based on the actual directory contents.
  8. If a system outage occurs during a directory conversion, the directory is made consistent during log recovery processing. That is, either the old directory will exist or the new directory will exist, but both will not exist.
  9. The conversion will cause the backup change activity flag to be set.
  10. If the aggregate damaged bit is set, conversion does not start and an error is issued. you can still mount the aggregate. The IOEZ00783E console message is displayed: 
    IOEZ00783E Aggregate aggregate_name is damaged

Privilege required

The issuer must be logged in as a root user (UID=0) or have READ authority to the SUPERUSER.FILESYS.PFSCTL resource in the z/OS UNIXPRIV class.

Examples

Figure 1 shows an example of a job that invokes the ioefsutl utility to convert a version 1.5 aggregate to a version 1.4 aggregate.
Figure 1. Job to convert a version 1.5 aggregate to a version 1.4 aggregate
//USERIDA JOB ,'Convert to version 4',
// CLASS=A,MSGCLASS=X,MSGLEVEL=(1,1)
//CONVERT  EXEC PGM=IOEFSUTL,REGION=0M,
// PARM=('converttov4 -aggregate OMVS.PRV.COMPAT.AGGR001')
//SYSPRINT DD SYSOUT=H
//STDOUT   DD SYSOUT=H
//STDERR   DD SYSOUT=H
//SYSUDUMP DD SYSOUT=H
//CEEDUMP  DD SYSOUT=H
//*

In the PARM=(’converttov4 -aggregate OMVS.PRV.COMPAT.AGGR001’) statement, the converttov4 and option -aggregate must be in lowercase.