ibm education assistance for z/os v2r1 · ibm education assistance for z/os v2r1 item: ... zfs...

© 2013 IBM CorporationMaterial is current as of June 2013

IBM Education Assistance for z/OS V2R1

Item: Release UpdatesElement/Component: zFS

I © 2013 IBM Corporation

Filename: zOS V2R1 zFS

of 46

Agenda

■ Trademarks■ Presentation Objectives■ Overview■ Usage & Invocation■ Interactions & Dependencies■ Migration & Coexistence Considerations■ Installation■ Health Checks■ Presentation Summary■ Appendix

IBM Presentation Template Full Version



of 46

Trademarks

■ See url http://www.ibm.com/legal/copytrade.shtml for a list of trademarks.


http://www.ibm.com/legal/copytrade.shtml

http://www.ibm.com/legal/copytrade.shtml



of 46

Presentation Objectives

■ zFS Large directory - Aka zFS Extended directory■ zFS Salvager■ zFS osi_ctl quiesce■ zFS backup bit■ ZFS AUDITFID■ zFS Eliminate multi-file system aggregates and cloning ■ zFS Rename of zSeries File System




of 46

Overview: zFS Extended Directory

■ Problem Statement / Need Addressed – zFS has a performance problem with a directory that has many entries (over

10,000 to millions of entries) due to the current linear search method.– Need a permanent solution.

■ Solution– Support a new directory format (v5) using an extensible hashing scheme.– Optional new version 1.5 file system (current field version is 1.4) – Multiple means to convert to the new version file system

■ Benefit / Value– Improves Large directory performance.– Also improved directory readdir+ time for both version 1.4 and 1.5 aggregates

(z/OS Unix line item exploitation of LIC407).– Increased maximum aggregate size & number of sub-directories




of 46

Usage & Invocation: zFS Extended Dir - Version 1.5 Aggregates

■ Maximum aggregate size: 4 TB -> 16 TB■ Maximum number of sub-directories: 65535(64k-1) -> 4294967293■ Can have both the old (v4) and new version directory formats (v5) ■ Newly created directories will be v5■ Conversion programs support changing the aggregate version to 1.5 and

optionally converting the directories■ Conversions are atomic■ Version 1.4 aggregate remains supported and converting to version

1.5 is optional.




of 46

Usage & Invocation: zFS Extended Dir - New Command and Parameters

■ New zfsadm convert command – zfsadm convert {-path <pathname> | -aggrversion <aggrname>}– With -path parameter, convert pathname v4 directory to v5 directory. – With -aggrversion parameter, change aggrname to version 1.5. No directories

are converted.

■ New IOEFSPRM options:– format_aggrversion= 4 | 5

• Default aggregate version remains 1.4– change_aggrversion_on_mount= On |Off

• Change aggregate version to 1.5 on RW mount• NO existing directories are converted.

– converttov5= On |Off• Change aggregate version to 1.5 and convert the root directory at mount time• Each v4 directory will be converted to v5 when first accessed.

– Can be dynamically changed via zfsadm config command




of 46

Usage & Invocation: zFS Extended Dir - New Command

■ New zfsadm fileinfo command –zfsadm fileinfo -path <pathname> [{-globalonly | -localonly | -both}]–Displays additional file/directory information, including whether a

directory is v4|v5–Example (next slide)




of 46

Usage & Invocation: zFS Extended Dir - Example #zfsadm fileinfo /tst path: /tst *** global data *** fid 1,1 anode 493805,516 length 137439010816 format BLOCKED 1K blocks 69457480 permissions 777 uid,gid 0,0 access acl 0,0 dir model acl 0,0 file model acl 0,0 user audit F,F,F auditor audit N,N,N set sticky,uid,gid 0,0,0 seclabel none object type DIR object linkcount 8 object genvalue 0x00000000 dir version 5 dir name count 201554084 dir data version 201554083 dir tree status VALID dir conversion na file format bits na,na,na file charset id na file cver na charspec major,minor na .....




of 46

Usage & Invocation: zFS Extended Dir - Enhanced Format Programs

■ Honor the new IOEFSPRM option format_aggrversion– Default is version 4– Also honored in ISHELL and AUTOMOUNT.

■ zfsadm format command – New -version5 | -version4 options. If no -versionx specified, will honor

IOEFSPRM option format_aggrversion.

■ Batch utility IOEAGFMT– New -version5 | -version4 options. If no -versionx specified, will honor

IOEFSPRM option format_aggrversion.– Now requires zFS being active.

■ zFS Format aggregate API supports new flag af_aggrversion– Value can be 0, 4 or 5.– If value=0, will honor IOEFSPRM option format_aggrversion.




of 46

Usage & Invocation: zFS Extended Dir - More commands

■ New options in zfsadm config and configquery commands corresponding to the IOEFSPRM options:

– format_aggrversion ,change_aggrversion_on_mount and converttov5.■ New MOUNT parms

– CONVERTTOV5 and NOCONVERTTOV5– Overrides IOEFSPRM options converttov5 and change_aggrversion_on_mount

■ zfsadm aggrinfo -long displays the aggregate version and the converttov5 attribute. Example:

# zfsadm aggrinfo -long IOEZ00369I A total of 1 aggregates are attached to the sysplex. PLEX.DCEIMGNJ.CONVTEST (R/W COMP): 7031 K free out of total 7200 version 1.5 auditfid C3C6C3F0 F0F10B2B 0000 sysplex-aware, converttov5 .....




of 46

Usage & Invocation: zFS Extended Dir - APIs

■ New zFS List File Information API – Additional info about file/directories (including whether dir is v4 or v5)

■ zFS List Aggregate Status (Version 2) API– Support version 1.5 aggregates by using the AGGR_STATUS3.

■ zFS Grow Aggregate API – support version 1.5 aggregate by using the AGGR_ID version 3.

■ zFS List File System Status API – Support version 1.5 aggregate by using the FS_STATUS2




of 46

Usage & Invocation: zFS Extended Dir - New Batch Utility IOEFSUTL

■ IOEFSUTL - 4 commands for non-mounted file systems■ format (acts as IOEAGFMT)

– -version4 |-version5 option. Requires zFS to be active if -versionx is not specified– Honors new IOEFSPRM option format_aggrversion

■ salvage (acts as IOEAGSLV)– Supports version 1.4 &1.5 aggregates and v4/v5 directories

■ converttov5– Converts aggregate version 1.4 to 1.5 and– Converts each v4 directory to v5 (new directory format)

■ converttov4– Only way to convert aggregate version 1.5 to 1.4 and– Converts each v5 directory to v4 (old directory format) – Restriction: cannot convert backwards if:

• A directory in the file system has a size > 4G • File system size >4TB or • A directory has > 64k-1 sub-directories




of 46

Usage & Invocation: zFS Extended Dir - Guidelines for v4 to v5 Conversions

■ The version 1.4 aggregates and v4 directory format remain supported. Customers are not required to convert all directories and aggregates to v5.

■ If installation exports zFS file systems to NFS or SMB, recommend to use offline conversion or CONVERTTOV5 MOUNT PARM.

■ If not planning to convert all file systems:– Determine the most active file systems

• modify zfs,query,filesets or wjsfsmon tool (from IBM Tools and Toys page)– Determine file systems with large directories (with >= 10,000 names or dir size

>= 800KB)• ls -l and df -t

– Consider conversion performance• Approx. conversion rate is 3500 names/sec (for a z9 machine) and 10,000

names/sec (for a zEC12 machine) per CP




of 46

Usage & Invocation: zFS Extended Dir - Guidelines for v4 to v5 conversions cont'd

■ Only change aggregate version to v1.5, no directory conversion:• Change version on specific file systems (use zfsadm convert -aggrversion

aggrname)– Or

• Change version on all file systems that are mounted on a particular image (use IOEFSPRM option change_aggrversion_on_mount).

■ Convert upon access (also changes aggregate version to v1.5)• CONVERTTOV5 MOUNT parameter on specific file systems

– Or• Set converttov5 mount attribute on all file systems are mounted on a

particular image (use IOEFSPRM option converttov5).

■ Targeted conversion of a directory (also changes aggregate version to v1.5)– Use zfsadm convert -path pathname

■ Full conversion (change aggregate version to v1.5 and convert all directories to v5)• Use IOEFSUTL converttov5 offline utility




of 46

Migration & Coexistence Considerations: zFS Extended Dir

■ zFS toleration APAR OA39466 - PTF UA90646(R11/R12) UA90647(R13) must be installed and active on all z/OS V1R12 and z/OS V1R13 systems before bringing zFS V2R1 into the shared file system environment.

■ Do not use version 1.5 aggregates until all systems are on z/OS V2R1–Version 1.5 aggregates can only be used on z/OS V2R1 systems.–Use IOEFSUTIL converttov4 command to re-version 1.5 aggregates for

use on pre-V2R1 releases (restriction does apply).

■ In V2R1, IOEAGFMT (batch utility) requires zFS being active. For JCL job containing IOEAGFMT, run the job when zFS is active.




of 46

Migration & Coexistence Considerations: zFS Extended Dir■ Changed default values for IOEFSPRM options meta_cache_size and

metaback_cache_size – Prior to V2R1, the default value of

• meta_cache_size is 64M. • metaback_cache_size is to not create the metadata backing cache.

– In V2R1, • If metaback_cache_size is specified and meta_cache_size is not, the default value

of meta_cache_size is 64 M.• If both are not specified, zFS calculates 10% of real storage (X) during zFS

initialization and


If X.... Default value of meta_cache_size

Default value of metaback_cache_size

X < 64M 64M No metadata back cache created

64M <= X < 100M X No metadata back cache created

100M <= X <= (2G +100M) 100M X - 100M

X > (2G + 100M) 100M 2G



of 46

Migration & Coexistence Considerations: zFS Extended Dir

■ Changed default value for IOEFSPRM options user_cache_size– Prior to V2R1, the default is 256M– In V2R1, zFS calculates 10% of real storage (X) during zFS initialization and

■ New migration check: ZOSMIGV2R1_ZFS_VERIFY_CACHESIZE

■ If already specify values for meta_cache_size, metaback_cache_size and user_cache_size or the new defaults are acceptable, do nothing.

■ Otherwise, specify desired values in IOEFSPRM file.


If X.... Default user_cache_size

X < 256M 256M256M <= X <= 2G X

X > 2G 2G



of 46

Installation: zFS Extended Dir

■ Changes in zFS installation –IOEAGFMT now requires zFS active– Install APAR OA39466 for down-level (prior to z/OS V2R1) systems–Changed default values for IOEFSPRM options meta_cache_size and

metaback_cache_size and user_cache_size




of 46

Health Checks: zFS Extended Dir■ Migration Health Check to assist you on z/OS V1R12 and V1R13 systems:

– ZOSMIGV2R1_ZFS_VERIFY_CACHESIZE– Verifies two cache sizes, user_cache and the sum of the meta_cache and the metaback_cache.– If the cache sizes will be smaller than the new z/OS V2R1 default values, the check will produce an

exception to alert you that they are different from the z/OS V2R1 changed defaults.– This check will identify your current cache sizes and the newly changed z/OS V2R1 defaults are.– Will verify the current system defaults (or what you have requested with the PARM on the health

check) with what is currently in use (what you specified in IOEFSPRM, or dynamic set with zfsadm command).

– If you do not want to use the current system defaults, then simply update the check PARM with your preferred values: PARM('META_CACHE=size1, METABACK_CACHE=size2,USER_CACHE=size3’)

– Inactive, one time check, low severity. Provided in an APAR, marked with IBM.Function.HealthChecker FIXCAT.

■ Best Practice Health Check to verify and notify of differences on z/OS V2R1 and higher:– ZFS_VERIFY_CACHESIZE– Exactly the same check as the Migration Health Check, except that the messages are different. (No

“migrating to z/OS V2R1” phrase necessary!), and it is Active.– This check will help you to know if your cache sizes fall below a desired level (either system default,

or some specified value you have determined).




of 46

Overview: zFS Salvager

The salvager utility is a zFS supplied program that runs as a batch job.■ The salvager examines a zFS aggregate to determine if there are any

inconsistencies in the structure of the aggregate. –In many cases, it can also fix a corrupted aggregate.

■ Before running the salvager utility against an aggregate, the aggregate must be unmounted (detached).

■ zFS recommends that you should begin using the new zFS batch utility program (IOEFSUTL) for the zFS salvage utility (IOEAGSLV). Support remains for running IOEAGSLV.

■ It supports both version 1.5 aggregates and version 1.4 aggregates.




of 46


■ Problem Statement / Need Addressed –Current zFS salvager utility has several shortcomings:

• It does not always find and fix zFS file system structure problems.• Sometimes it needs to be run several times against the same zFS

file system before it completely resolves the inconsistencies.• It cannot handle very large zFS file systems or file systems with

many objects (it runs in a 2G address space).• Sometimes, it abends when trying to fix a zFS file system.• The serviceability characteristics of the current salvager are

insufficient for problem diagnosis.• Some Salvager messages do not have message numbers.



of 46


■ Solution –Salvage utility can process larger zFS file systems by using storage

above the 2 GB bar.– The repair processing will complete without requiring to be run

multiple times.– All messages have message numbers. – The verify option (-verifyonly) replays the log when necessary.

■ Benefit / Value –Improve the functioning (run only once).–Improve the scalability of the zFS batch salvager (processes large file

systems).–Improved RAS by improving messages.–Improved performance.



of 46

Usage & Invocation: zFS Salvager

■ Recommend using the new IOEFSUTL batch utility.Format:

ioefsutl salvage -aggregate name [-verifyonly][-help] -levelOptions:

-aggregate nameSpecifies the name of the aggregate to be verified or salvaged.-help Prints the online help for this command. All other valid options that are specified with this option are ignored.-verifyonlySpecifies that the Salvager is to verify the specified aggregate. It should not attempt to repair any damage found. The log is replayed before the verification unless an error occurs during the replay. If this option is omitted, the Salvager will replay the log, verify the specified aggregate and then attempt to repair any damage found.



of 46

Usage & Invocation: zFS Salvager

■ Example job://USERIDA JOB ,’Salvage verify’,// CLASS=A,MSGCLASS=X,MSGLEVEL=(1,1)//SALVAGE EXEC PGM=IOEFSUTL,REGION=0M,// PARM=(’salvage -aggregate SUIMGNJ.HIGHRISK.TEST -verifyonly’)//IOEZPRM DD DSN=CFCIMGNJ.PARMLIB(IOEFSPRM),DISP=SHR//SYSPRINT DD SYSOUT=H//STDOUT DD SYSOUT=H//STDERR DD SYSOUT=H//SYSUDUMP DD SYSOUT=H//CEEDUMP DD SYSOUT=H//*



of 46

Usage & Invocation: zFS Salvager - Sample Salvager Job Output #1

IOEZ00559I zFS IOEFSUTL: Initializing z/OS zFS Version 02.01.00 Service Level 0000000 - HZFS410. Created on Wed Mar 20 16:05:20 EDT 2013. Address space asid x1C IOEZ00178I CFCIMGNJ.PARMLIB(IOEFSPRM) is the configuration dataset currently in use IOEZ00707I Log file size 107 8K blocks, verified correct IOEZ00729I Verification of aggregate SUIMGNJ.HIGHRISK.TEST started IOEZ00705I Formatted v5 aggregate size 10800 8K blocks, dataset size 10800 8K blocksIOEZ00707I Log file size 107 8K blocks, verified correct IOEZ00709I Bitmap size 2 8K blocks, verified correct IOEZ00782I Salvage has verified 17 of 175 pages in the anode table. IOEZ00782I Salvage has verified 34 of 175 pages in the anode table. ....IOEZ00782I Salvage has verified 153 of 1530 directories in the directory tree. IOEZ00782I Salvage has verified 306 of 1530 directories in the directory tree. .... IOEZ00722I Primary file system size 465 8K blocks, verified correct IOEZ00739I Salvage processed 1573 directory pages, 4128 anodes, 3 indirect blocks and 175 anode table pages. IOEZ00730I Verification of aggregate SUIMGNJ.HIGHRISK.TEST completed, no errors found.



of 46

Usage & Invocation: zFS Salvager - Sample Salvager Job Output #2 ....

IOEZ00729I Verification of aggregate SUIMGNJ.HIGHRISK.TEST1 started IOEZ00705I Formatted v5 aggregate size 41040 8K blocks, dataset size 41040 8K blocksIOEZ00707I Log file size 107 8K blocks, verified correct IOEZ00709I Bitmap size 6 8K blocks, verified correct IOEZ00703E Corruption: Anode Table (T3): direct block index=6 physPage=8 IOEZ00704E Expected: Anode Table (T3): physPage=8 not alllocated to another objectIOEZ00703E Corruption: Anode Table (T2): allocated=12032 visible=12032 IOEZ00704E Expected: Anode Table (T2): calculated allocated=12024 visible=12024...IOEZ00723E Primary file system on aggregate SUIMGNJ.HIGHRISK.TEST1 is corruptedIOEZ00703E Corruption: Bitmap (B18): bits array in Bitmap physPage 00000001 logPage/offset/value=<0 2319 000000FF>IOEZ00703E Corruption: Bitmap (B18): represented physPage 1386 IOEZ00704E Expected: Bitmap (B18): bits array in Bitmap physPage 00000001 logage/offset/value=<0 2319 00000000>..... IOEZ00739I Salvage processed 16916 directory pages, 47972 anodes, 5 indirect blocks and 1500 anode table pages.IOEZ00733I Verification of aggregate SUIMGNJ.HIGHRISK.TEST1 completed and the aggregate is in error IOEZ00735I Salvage found 16 minor errors of aggregate SUIMGNJ.HIGHRISK.TEST1IOEZ00753I Salvage is repairing anode table pages. IOEZ00755I Salvage is repairing the ZLC list. IOEZ00756I Salvage is repairing file, directory, and ACL objects. IOEZ00757I Salvage is repairing bitmap pages. IOEZ00758I Salvage repaired 1 anode table pages, 0 partially free pages, 0 zlc pages, 0 indirect blocks.IOEZ00787I Repair of aggregate SUIMGNJ.HIGHRISK.TEST1 completed



of 46

Migration & Coexistence Considerations: zFS Salvager

■ IBM recommends use of the IOEFSUTL batch facility to invoke the salvager, but the IOEAGSLV batch utility is still available.



of 46


■ zFS exploitation of osi_ctl (quiesce/unquiesce) –The zFS commands and zFS APIs used to quiesce and unquiesce

zFS file systems are unchanged, but the way quiesce works internally and the way the quiesce status is displayed are modified.



of 46

Overview: zFS osi_ctl quiesce

■ Problem Statement / Need Addressed –Currently, zFS handles the quiesce of a zFS aggregate independently

of z/OS UNIX.–The D OMVS,F operator command and the z/OS UNIX df shell

command show the file system as ACTIVE rather than QUIESCED. This makes it harder for system administrators to determine why a job is not making progress when the zFS aggregate is quiesced.



of 46

Overview: zFS osi_ctl quiesce

■ Solution –zFS will notify z/OS UNIX prior to zFS quiesce via a call to the z/OS

UNIX osi_ctl quiesce API and again after unquiesce via the z/OS UNIX osi_ctl unquiesce API.

–When z/OS UNIX receives the osi_ctl quiesce call from zFS, z/OS UNIX will quiesce and suspend operations in its layer thus avoiding unnecessary latch contention and allowing zFS aggregate quiesce status to be available via USS commands.

■ Benefit / Value –System Administrators will be able to determine when zFS aggregates

are quiesced using standard z/OS UNIX commands.



of 46

Usage & Invocation: zFS osi_ctl quiesce

■ No external interfaces are changed. • D OMVS,F and the df command will display the quiesce status for

zFS aggregates.•The z/OS UNIX w_getmntent API provides a Version 3 MNTE that contains the PFS Exception status•The zFS zfsadm aggrinfo –long command is enhanced to show the quiescing job, system and time for a zFS quiesced aggregate.•The zFS List Aggregate Status (Version 2) API is enhanced with those same fields

Example:# mount -f usszfs.plex01.zfs '-o norwshare' /u/totten/testdir

# zfsadm quiesce USSZFS.PLEX01.ZFS

IOEZ00163I Aggregate USSZFS.PLEX01.ZFS successfully quiesced



of 46


- D OMVS,F,N=USSZFS.PLEX01.ZFS PXO045I 15.14.39 DISPLAY OMVS 252 OMVS 0011 ACTIVE OMVS=(ST,R1,X9) TYPENAME DEVICE ----------STATUS----------- MODE MOUNTED LATCHES ZFS 425 QUIESCED RDWR 01/30/2013 L=245 NAME=USSZFS.PLEX01.ZFS 15.13.24 Q=245 PATH=/u/totten/testdir MOUNT PARM= norwshare OWNER=NP5 AUTOMOVE=Y CLIENT=N QSYSTEM=NP5 QJOBNAME=TOTTEN26 QPID= 50595795



of 46


In the shell:NP5 /u/totten# zfsadm aggrinfo -long usszfs.plex01.zfs USSZFS.PLEX01.ZFS (R/W COMP QUIESCED): 2134143 K free out of total 2160000 version 1.4 auditfid D6C5F9F6 F7F70010 0000 266767 free 8k blocks; 7 free 1K fragments 21616 K log file; 56 K filesystem table 312 K bitmap file Quiesced by job TOTTEN26 on system NP5 on Wed Feb 6 13:31:07.687179 2013



of 46


In the shell: NP5 /u/totten# df -Pkv /u/totten/testdir Filesystem 1024-blocks Used Available Capacity Mounted on USSZFS.PLEX01.ZFS 0 0 0 0% ZFS, Read/Write, Device:401, ACLS=Y norwshare File System Owner : NP5 Automove=Y Client=N Quiesce Owner : NP5 Quiesce Jobname : TOTTEN26 Quiesce PID : 50595795 Filetag : T=off codeset=0 Aggregate Name : USSZFS.PLEX01.ZFS



of 46


■ Slight difference in the output when the file system is mounted with the rwshare parameter.

# mount -f usszfs.plex01.zfs '-o rwshare' /u/totten/testdir

# zfsadm quiesce USSZFS.PLEX01.ZFS

IOEZ00163I Aggregate USSZFS.PLEX01.ZFS successfully quiesced



of 46


-D OMVS,F,N=USSZFS.PLEX01.ZFS BPXO045I 15.07.53 DISPLAY OMVS 248 OMVS 0011 ACTIVE OMVS=(ST,R1,X9) TYPENAME DEVICE ----------STATUS----------- MODE MOUNTED LATCHES ZFS 423 ACTIVE RDWR 01/30/2013 L=245 NAME=USSZFS.PLEX01.ZFS 15.05.59 Q=0 PATH=/u/totten/testdir MOUNT PARM= rwshare OWNER=NP5 AUTOMOVE=Y CLIENT=N PFS INFO: PFS EXCP: QUIESCED

Display also reported in z/OS UNIX shell by zfsadm aggrinfo -long



of 46

Interactions & Dependencies: zFS osi_ctl quiesce

■ Software Dependencies–None

■ Hardware Dependencies–None

■ Exploiters– Any users of zFS file systems in V2R1

■ Note the slight difference in output format based on zFS mount parameter norwshare/rwshare.

■ The df utilitydoes not show the quiesced status if the file system is mounted RWSHARE. Using the D OMVS,F command is the most reliable.

■ Read/write/lookup operations are suspended as they are today.



of 46

Overview: zFS backup bit

Problem Statement: With the backup change activity flag (when the change activity flag is set, it means that backup is needed):

–zFS sets the change activity flag at MOUNT even though no writes may have occurred.

–zFS does not set the change activity flag after a backup occurs (and the change activity flag has been reset) even when writes occur.

Solution–zFS will not set the change activity flag at MOUNT –zFS will set the change activity flag in the following cases

•on the first write after MOUNT•on the first write after a successful reset change activity flag PFSCTL call •on log recovery

New zFS Reset Change Activity Flag API



of 46

Overview: AUDITFID

The default of IOEFSPRM configuration option CONVERT_AUDITFID is changed from OFF to ON.

zfsadm format and IOEAGFMT –changed default to –newauditfid (-newauditfid option already exists)– new option –nonewauditfid

New IOEFSUTL format command always formats with a unique auditfid (acts like -newauditfid)



of 46

Migration & Coexistence Considerations: AUDITFID

Accommodate new zFS CONVERT_AUDITFID default–CONVERT_AUDITFID/IOEAGFMT/zfsadm format–zfsadm configquery -convert_auditfid displays the current

convert_auditfid setting– If accepting the new auditfid

•Ensure IOEFSPRM option convert_auditfid is not specified or set to ON for the next IPL•Or use zfsadm config -convert_auditfid on for dynamical update•SMF 80 records will have new unique auditfids. May require updates in programs processing SMF 80 records.

– If keeping the old non-unique auditfid•Specify the IOEFSPRM option convert_auditfid=off for the next IPL•Use -nonewauditfid option in IOEAGFMT or zfsadm format for formatting new aggregates•Do not use IOEFSUTL format command as it defaults to -newauditfid



of 46

Installation: AUDITFID

■ Default for auditfid is now set to on.



of 46

Overview: Elimination of Multi-File System Aggregates and Cloning

■ Change name of zFS to System z file system –Publication only change–Will see change in F ZFS,Q,LEVEL.

• From–IOEZ00639I zFS kernel: z/OS zSeries File System

• To– IOEZ00639I zFS kernel: z/OS zFS



of 46

Migration & Coexistence Considerations: Elimination of Multi-File System Aggregates and Cloning■ Do not attempt to use any multi-file system or clone commands, APIs or

options.



of 46

Presentation Summary

■ Extended directory support includes new aggregate version 1.5, improved directory performance to v5 directories.

■ Scaling improvements in file system size and number of sub directories.■ IOEFSUTL is the new suite of batch utilities introduced in V2R1. IBM

recommends that the salvage and format utilities be invoked using IOEFSUTL.

■ There are many improvements to the salvager utility in V2R1.




of 46

Appendix

■ Publication references –z/OS Distributed File Service zSeries File System Administration

(SC24-6887)–z/OS Distributed File Service Messages and Codes (SC24-6885)–z/OS UNIX Tools and Toys web page:

• http://www-03.ibm.com/systems/z/os/zos/features/unix/bpxa1ty2.html


http://www-03.ibm.com/systems/z/os/zos/features/unix/bpxa1ty2.html

ibm education assistance for z/os v2r1 · ibm education assistance for z/os v2r1 item: ... zfs...

Documents