Академический Документы
Профессиональный Документы
Культура Документы
com
zFS - 1
Trademarks
eNetwork geoManager AD/Cycle ADSTAR AFP APL2 APPN BookManger BookMaster C/370 CallPath CICS CICS/ESA CICS/MVS CICSPlex COBOL/370 DataPropagator DisplayWrite DB2 DB2 Universal Database DFSMS DFSMStvs DFSMSdfp DFSMSdss DFSMShsm DFSMSrmm DFSORT Enterprise System 3090 Enterprise System 4381 Enterprise System 9000 ES/3090 ES/4381 ES/9000 ESA/390 ESCON First Failure Support Technology FLowMark FFST GDDM ImagePlus Intelligent Miner IBM IMS IMS/ESA IP PrintWay IPDS Language Environment Multiprise MQSeries MVS/ESA Network Station NetSpool OfficeVision/MVS Open Class OpenEdition OS/2 OS/390 Parallel Sysplex Print Services Facility PrintWay ProductPac PR/SM QMFr
Tivoli (Tivoli Systems Inc.) Tivoli Management Framework (Tivoli Systems Inc.) Tivoli Manger (Tivoli Systems Inc.)
RACF RMF RS/6000 S/390 S/390 Parallel Enterprise Server SecureWay StorWatch Sysplex Timer System/390 SystemView SOM SOMobjects SP VisualAge VisualGen VisualLift VTAM WebSphere 3090 3890/XP z/OS z/OS.e UNIX (X/Open Company Limited) Windows (Microsoft Corporation) Windows NT (Microsoft Corporation)
zFS - 2
Domino (Lotus Development Corporation) DFS (Transarc Corporation) Java (Sun Microsystems, Inc.) Lotus (Lotus Development Corporation)
REXX
z/OS UNIX Callable Services Interfaces Logical File System z/OS UNIX-PFS Interface
Kernel
HFS PFS
zFS - 3
z/OS UNIX Callable Services Interfaces Logical File System z/OS UNIX-PFS Interface
Kernel
TFS
automount
IP sockets
Local sockets
NFS client
ZFS
ZFSVOL
/ F F F
zFS - 4
Migration Considerations
Often the file system type is used in a portion of the file system name With the change to a file type of zFS, parmlib members, mount scripts and policies are affected as well as the file system name
You may prefer to keep the current file system name and then no changes to mount scripts Migration tool will help with handling these changes
zFS file systems that span volumes must be preallocated prior to invoking the tool zFS file systems that are greater than 4 GB must be defined with a data class that includes extended addressability zFS file systems cannot be striped
zFS - 8
Migration Tool
Use a migration tool to handle many details needed for the migration of HFS file systems to zFS, including the actual copy operation - z/OS V1R7
Migration tool - BPXWH2Z
An ISPF based tool for migration from an HFS file system to zFS It has a panel interface that enables you to alter the space allocation, placement, SMS classes, and data set names A HELP panel is provided Uses a new pax utility for copy
zFS - 9
zFS - 10
zFS - 11
BPXWH2Z Panels
Panels will allow for customization of space allocation, placement SMS class and data set name Tool makes the zFS a little larger if it sees the HFS is near capacity by: 10% if it is over 75% full and under 90% and 20 % if over This is a precaution since zFS is a logging filesystem and includes the log in the aggregate If unmounted it creates a mountpoint in /tmp and mounts it read only for the migration then deletes the mountpoint If there are filesystems mounted below the migrating filesystem they are unmounted for migration The mount points are created in the new filesystem and when complete the filesystems are re-mounted
zFS - 13
BPXWH2Z Panels
By default, the panels are primed such that your HFS data set is renamed with a .SAV suffix and the zFS data set is renamed to the original HFS name You can preallocate the zFS file system or specify a character substitution string such that the data sets are not renamed - The substitution string is specified as the first argument on the command line as follows: /fromstring /tostring/ datasetname For example, if your data set is OMVS.DB2.HFS and you want your zFS data set to be named OMVS.DB2.ZFS, you can specify the following: bpxwh2z -cv /hfs/zfs/ omvs.db2.hfs
zFS - 14
For general purpose file systems, it appears that they consume about the same amount of space
Two data sets will exist during the migration, so plan for space for two file systems about same size
zFS - 15
Migration Steps
If the HFS file system is mounted, either unmount it or switch it to read-only mode The migration tool switches it to R/O If the file system is not mounted make a directory for it and mount it in R/O mode The migration tool creates a temporary directory in /tmp for the mountpoint and deletes it when the migration is complete Create a temporary directory for the zFS file system The migration tool creates a temporary directory in /tmp for the mountpoint and deletes it when the migration is complete Check the allocation attributes for of the HFS file system
zFS - 16
Migration Steps
Define a new zFS file system with the appropriate allocation attributes Mount the zFS file system on its temporary mountpoint (a pre-existing zFS cannot already be mounted) Use the pax utility to copy the HFS contents to the zFS by entering the shell, change directory to the HFS mountpoint, and run the pax utility - The pax command you can use follows: pax -rw -peW -XCM . /tmp/zfsmountpoint If the HFS contains active mountpoints do a mkdir for each of these in the zFS file system and set directory attributes as required
zFS - 17
Migration Steps
Unmount the zFS file system Unmount the HFS file system Remove any temporary directories used as mountpoints Rename the data sets as appropriate and ensure all mount scripts and policies have been updated as needed The migration tool does not modify or search for any type of mount scripts or policies If the HFS file system was originally mounted, mount the zFS file system in that same location along with any hierarchy that also had to be unmounted to unmount the HFS
zFS - 18
zFS - 19
zFS - 20
Migrate in Foreground
A - Alter allocation
Migrating OMVS.ROGERS.TEST creating zFS OMVS.ROGERS.TEST.TMP copying OMVS.ROGERS.TEST to OMVS.ROGERS.TEST.TMP Blocks to copy: 2832 IGD01009I MC ACS GETS CONTROL &ACSENVIR=RENAME IGD01009I MC ACS GETS CONTROL &ACSENVIR=RENAME IDC0531I ENTRY OMVS.ROGERS.TEST.TMP ALTERED IDC0531I ENTRY OMVS.ROGERS.TEST.TMP.DATA ALTERED mount /u/rogers/tmp OMVS.ROGERS.TEST ZFS 1 ***
zFS - 21
zFS - 22
zFS - 23
zFS - 24
pax Enhancements
Sparse files are those which do not use real disk storage for pages of file data that contain only zeros
Copying files as sparse saves disk space
The ability to skip read errors may allow installations to salvage some files from corrupted file systems Preserving all files attributes of copied file saves installations from having to manually set desired attributes that may not have been preserved previously
Create mountpoint directories Copy all attributes from the source root to the target of the copy after the copy is complete
Lotus Domino is an example for an application exploiting the usage of sparse files to save disk space
zFS - 26
$> zfsadm configquery -sysplex_state IOEZ00317I The value for configuration option -sysplex_state is 1.
zFS - 29
$> zfsadm configquery -sysplex_state IOEZ00317I The value for configuration option -sysplex_state is 1.
zFS - 31
PAUL @ SC65:/>zfsadm configquery -group IOEZ00317I The value for configuration option -group is IOEZFS.
zFS - 32
zFS - 35
ioeagslv -aggregate <name> -recoveronly {-converttov3 | -verifyonly | -salvageonly} -verbose -level -help
IOEAGSLV can be executed from any supported release by STEPLIBing to MIGLIB
zFS - 38
z/OS V1R7 zFS will recover for EOM in all situations, earlier releases will not
zFS - 40
zFS - 45
zFS - 46
zFS - 47
RSN=052C018F
RSN=5B220125
zFS - 48
RSN=EF096055
zFS Cache
With V1R4, the log file cache is in a dataspace Default - (64 MB) Frees up space for caches in ZFS address space
Dataspaces
Log file cache
ZFSVL1
/ F F F F OMVS.CMP01.ZFS F
Metadata cache
All directory contents File status information File system structures Also caching of data for files smaller than 7K
zFS - 52
f zfs,query,all
Used as a "paging" area for metadata Allows a larger meta cache for workloads that need large amounts of metadata Only needed if meta cache is constrained
zFS - 53
Performance APIs
Previously, certain zFS performance counters could only be retrieved via operator console command Data could not easily be retrieved by an application Provide an API to obtain statistics on zFS activity Now, all zFS performance counters can be retrieved by an application - pfsctl API (BPX1PCT) Now, zfsadm command can be used to display/reset performance counters zfsadm query -metacache Administrative application programs can use this function RMF exploits this function in z/OS V1R7
zFS - 54
Metadata Caching Statistics Buffers (K bytes) Requests Hits Ratio Updates ---------- --------- ---------- ---------- ------ ---------512 4096 15779 15727 99.6% 4
zFS - 57
Directory Cache
In z/OS V1R7 a new zFS IOEPRMxx parameter file statement is available to set the directory cache size dir_cache_size - Size of the directory buffer cache
Example: dir_cache_size=4M
The minimum and default size is 2M, the maximum value that can be set is 512M Changing this cache size may be useful if you expect situations with many file creates or deletes This is available via APAR OA10136 and PTFs: UA16125 for z/OS V1R4 UA16123 for z/OS V1R5
UA16124 for z/OS V1R6
zFS - 58
zFS - 59
zFS - 60
zFS Redbooks
z/OS Distributed File Service zSeries File System Implementation, SG24-6580-00 - (z/OS V1R3) Publication - September 2002 z/OS Distributed File Service zSeries File System Implementation, SG24-6580-01 - (z/OS V1R6) Publication - April 2005 z/OS Distributed File Service zSeries File System Implementation, SG24-6580-02 - (z/OS V1R7) Publication - February 2006
zFS - 62
zFS - 63
F F F F
User cache
f zfs,query,all
zFS - 64
RMF Overview Report Selection Menu Selection ===> Enter selection number or command for desired report.
Basic Reports 1 WFEX 2 SYSINFO 3 CPC Detail Reports 4 DELAY 5 GROUP 6 ENCLAVE 7 OPD 8 ZFSSUM 9 ZFSACT
(WE) (SI)
Delays (DLY) Group response time breakdown (RT) Enclave resource consumption and delays (ENCL) OMVS process data zFS Summary (ZFSS) zFS File system activity (ZFSA)
RMF Overview Report Selection Menu (Detail reports) Command interface ZFSSUM or ZFSS: zFS summary report ZFSACT or ZFSA: zFS activity report
Gatherer options:
Option NOZFS | ZFS
zFS - 65
Cache activity:
Request rates Hit ratios % read requests % requests delayed
Aggregate section:
Capacity data Mount mode # filesystems in the aggregate Read / Write rates (Bytes per second)
(B/Sec) 1 0
zFS - 66
Date: 09/07/04
Time: 16.30.00
Range: 120
Sec
---- Response Time ---- ---------------- Cache Activity -------------------------- Wait% ----- --------- User -----Avg 0.27 I/O 0.4 Lock Sleep 80.7 Rate Hit% Read% Dly% 100 0.0 0.0 0.0 405.5 -- Vnode -- - Metadata - -Trx Rate Hit% 0.0 0.0 Rate Hit% 10.9 99.9 FS Rate 0.2
Read Write
Count Waits Cancl 528K 29.2 326 R/W CP 0 815 2160K 346 8.0 23 R/W MS 0 1447 7200K 16.1 175 R/W MS 0
Merge Type 1 0 0 137 FILE SYSTEM METADATA 3 29 0 LOG 137 FILE USER FILE DATA 3 2 137 1058
zFS - 67
RMF V1R7 3 Command ===> CSR Samples: 120 Sec System: TRX2
Line 1 of
Scroll ===>
Date: 09/07/04
Time: 16.30.00 Press Range: Enter to 120 return to the Report panel.
---- Response Time ---- ---------------- Cache Activity -------------------------- Wait% ----- --------- User ------Trx -- Vnode -- - Metadata Rate Hit% Rate Hit%
Read Rate : 27.4 Size : 256M 0.27 0.4 80.7 0.0 405.5 100 0.0 0.0 0.0 0.0 10.9 99.9 Write Rate : 16.9 Total Pages : 65536 0.2 Hit (%) Read : 59.4 Free Pages : 12703 Write Hit (%) : 100.0 Segments : 8192 Read Delay (%) : 1.3Name------------------ Size Use% --Mode- FS Read ------------Aggregate Write Delay (%) : 0.0 User Cache readahead: ON Write Async Read Rate : 10.1 Storage fixed : NO (B/Sec) Scheduled Write Rate : 83.8 Page Reclaim Writes : 0 528K 29.2 R/W CP 1 0 FsyncsOMVS.TRX2.LOCAL.COMPAT.A.ZFS : 0
137 OMVS.TRX2.LOCAL.MULTI.A.ZFS Press Enter to return to the Report panel. 137 RMF.TEST.ZFS.HFSMF1 1058 7200K 16.1 R/W MS 3 137 2160K 8.0 R/W MS 3 0
zFS - 68
ibm.com
zFS - 69
zFS - 71
//ZFSJOB JOB ,'COPYPAX',NOTIFY=&SYSUID.,REGION=0M //* -----------------------------------------------------------------//* Use pax to copy source directory structure to target directory //* Property of IBM (C) Copyright IBM Corp. 2002 //* -----------------------------------------------------------------// SET SOURCED='/' <=== Source directory // SET TARGETD='/u/zfs/zfsroot' <=== Target directory //* -----------------------------------------------------------------// SET TIMEOUT=0 <=== Timeout value in seconds, 0=no timeout // SET REXXLIB=HERING.ZFS.REXX.EXEC <=== SYSEXEC library //* -----------------------------------------------------------------//ZFSADM EXEC PGM=IKJEFT01,PARM='COPYPAX &TIMEOUT &SOURCED &TARGETD' //SYSEXEC DD DSNAME=&REXXLIB.,DISP=SHR //SYSTSIN DD DUMMY //SYSTSPRT DD SYSOUT=*,LRECL=136,RECFM=V //*
zFS - 72
ADDMNTPS ........
It looks for all mount points of all the file systems mounted in the system If the file system is the source file system or the mount point is the root ( / ), no action is taken If the parent directory of the mount point belongs to the source file system, then this mount point is one of the mount point directories that needs to exist in the target structure A test is done to determine whether the corresponding directory in the target file system is already there (it could have been defined in the meantime). If it does not exist, it is created with owner UID 0 and permission bits set to 700
zFS - 74
zFS - 77
Different operands on MOUNT command Different security system setup CICS, DB2, and IMS ServerPacs assume that any necessary zFS setup has been done
zFS - 78
RESTFS Job:
Uses appropriate TYPE on MOUNT commands depending on filesystem type Puts appropriate TYPE on MOUNT parameters in BPXPRMFS Add FILESYSTYPE for zFS to BPXPRMFS if needed
zFS - 79