SHARE in Anaheim, CA August 9, 2012

Cloning zFS in a Shared File System

Environment
Marna WALLE, [email protected]
and
Scott Marcotte, [email protected]
IBM Systems and Technology Group
Poughkeepsie, New York USA

© 2012 IBM Corporation

Trademarks

The following are trademarks of the International Business Machines Corporation in the United States, other countries, or both.

Not all common law marks used by IBM are listed on this page. Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not
actively marketed or is not significant within its relevant market.
Those trademarks followed by ® are registered trademarks of IBM in the United States; all others are trademarks or common law marks of IBM in the United States.

For a complete list of IBM Trademarks, see www.ibm.com/legal/copytrade.shtml:

*, AS/400®, e business(logo)®, DBE, ESCO, eServer, FICON, IBM®, IBM (logo)®, iSeries®, MVS, OS/390®, pSeries®, RS/6000®, S/30, VM/ESA®, VSE/ESA,
WebSphere®, xSeries®, z/OS®, zSeries®, z/VM®, System i, System i5, System p, System p5, System x, System z, System z9®, BladeCenter®

The following are trademarks or registered trademarks of other companies.

Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.
Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom.
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countries.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office.
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency, which is now part of the Office of Government Commerce.
* All other products may be trademarks or registered trademarks of their respective companies.

Notes:
Performance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput that any user will
experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed.
Therefore, no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance ratios stated here.
IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms apply.
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved. Actual
environmental costs and performance characteristics will vary depending on individual customer configurations and conditions.
This publication was produced in the United States. IBM may not offer the products, services or features discussed in this document in other countries, and the information may be subject to change without
notice. Consult your local IBM business contact for information on the product or services available in your area.
All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.
Information about non-IBM products is obtained from the manufacturers of those products or their published announcements. IBM has not tested those products and cannot confirm the performance,
compatibility, or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
Prices subject to change without notice. Contact your IBM representative or Business Partner for the most current pricing in your geography.

© 2012 IBM Corporation

Agenda

Cloning Review:
– Why you clone
– Cloning assumptions

Differences: data sets and file systems, and HFS and zFS

Catalog’s Role in using file systems

Shared file system concepts

Installing and Servicing for a shared file system environment

Copying file system data sets

zFS indirect cataloging support

Cloning assistance provided

A note about quiescing file systems

Extra! Dynamic activating z/OS UNIX corrective service

3
© 2012 IBM Corporation
Cloning Review:
Why We Clone

At some point after you have finished installing
z/OS software you will probably need to make a
copy of it (“clone” it)

Some reasons are:
–For backup
• A backup copy is a copy of the z/OS product set (z/OS
and other products you have installed on the same set
of volumes using the same SMP/E zones) that:
• Resides on different volumes with different volume labels
• Includes copies of the associated SMP/E zones with different names
that point to the data sets on the new volumes
• May include copies of the associated catalogs with different names
• Can be IPLed in place of the original copy when the necessary setup
has been done after making the copy
–To move the software to another system (“deployment”)
–To create another SMP/E-serviceable copy for installing
service or other products
4
© 2012 IBM Corporation
Cloning Review:
Cloning Assumptions

Cloning should include:
• The current target software instance (target PDS and PDSEs, z/OS
UNIX file system data sets, optionally dlibs, and SMP/E CSIs)

Cloning may also include:
• Appropriate operational data sets and configuration files
Software Instance

SMP/E Maintained files

Target DS
dlibs
DLIBs
DLIBs CSIs Operational data sets
CSI's
File Systems
Configuration files

For this presentation, we’ll focus specifically on the z/OS UNIX file system
data sets.
– PDS and PDSE cloning do not seem to raise as many questions as
z/OS UNIX file system data sets do!
– SMP/E CSI data sets and entries are not covered, but remember that
5
your SMP/E CSI should be updated as part of the cloning activity, and
all DDDEF entries should have a correct location and name! © 2012 IBM Corporation
Differences between MVS data sets and z/OS UNIX mounted
file systems

Two different MVS data sets with the same name can be
actively accessed on a single system as long as they reside
on different volumes (with different volume serials) and they
both do not need to be cataloged.
– You need to specify somehow which data set you want
by providing the volume serial where it resides.

Two different z/OS UNIX file systems with the same data set
name, cannot be mounted at the same time on a single
system nor in a shared file system environment (even if you
try to use different z/OS UNIX mount point directories) and
they need to be cataloged to be mounted.
– This is an existing restriction since the beginning of z/OS
UNIX.

6
© 2012 IBM Corporation
z/OS UNIX File System Data Sets

z/OS UNIX File System Data Sets contain many important parts
of the z/OS operating system and associated products:
–TCP/IP, z/OS Shells and Utilities, Infoprint Server, Java SDK, XML
Toolkit, Ported Tools, …

The choice today for z/OS Unix file system data sets is:
–HFS: Stabilized. Non-VSAM data set.
• Can be indirectly cataloged just as target library PDS and PDSEs
can.
• Both cataloged and uncataloged HFS can be on non-SMS DASD.
• Cataloged HFS can be multi-volume on SMS-DASD (up to 255
extents on 59 volumes with up to 123 extents per volume)
–zFS: Enhancements provided that customers need! VSAM LDS,
therefore must be cataloged.
• Support for indirectly cataloged zFS (not VSAM LDS in general!)
• Non-SMS or SMS, can be up to 59 volumes. (EAS-eligible on
EAVs!)
• Indirect catalog zFS support is limited to one volume, however.
7 • Architected maximum size for an aggregate: 4 TB
© 2012 IBM Corporation
Major management zFS difference from HFS: VSAM

VSAM data sets must be cataloged to access them

(regardless of whether they are mounted).

VSAM must be SMS-managed (needs a STORAGECLASS)
if larger than 4 GB.
Needs a DATACLASS that provides extended addressability
– (4 GB is about 5825 cylinders of 3390 DASD)

All SMS-managed data sets must be cataloged.

In a nutshell, for cloning: It’s the catalog.

8
© 2012 IBM Corporation
Catalog’s role in accessing data sets

Master Catalog identified in
–LOADxx member of SYS1.PARMLIB, or
–SYSCATxx member of SYS1.NUCLEUS

User Catalogs defined in Master Catalog, and often used for VSAM data
sets.
–DEFINE ALIAS NAME(HLQ) RELATE(USERCAT.HLQ)
• USERCAT.HLQ -> user catalog that contains data sets that
begins with HLQ

System Symbolics and Extended Alias in catalog entries:

–For the volume: NONVSAM ------- SYS1.LINKLIB … VOLUMES
VOLSER------ &SYSR1. DEVTYPE------X'00000000‘
NONVSAM ------- OMVS.ROOT.HFS … VOLUMES
VOLSER------ &SYSR1. DEVTYPE------X'00000000‘
–For aliasing a data set name: ALIAS --------- SYS1.PRODUCT …
ASSOCIATIONS SYMBOLIC- SYS1.&SYSR1..PRODUCT
RESOLVED-SYS1.ZD113.PRODUCT
–For user catalog names: ALIAS --------- SYS1.ZFS …
ASSOCIATIONS SYMBOLIC- &ZFSVL..UCAT RESOLVED-ZCSDW.UCAT
–For zFS indirect exploitation: CLUSTER ------- ZFS.ROOT … VOLUME
VOLSER------------ &ZFSVL DEVTYPE------X'00000000'
9
© 2012 IBM Corporation
Shared File System Concepts

In a Shared File System environment

(BPXPRMxx specifies SYSPLEX(YES) on all systems):
– There is a single z/OS UNIX file system hierarchy across
the multiple systems in the shared file system
environment.
– When a z/OS UNIX file system is mounted, it is globally
mounted across all the systems.
– Once a file system (name) is mounted into the z/OS
UNIX file system hierarchy, you cannot mount a file
system with the same name.
• On the same mount point or even a different mount
point.
– Several z/OS releases or service levels can be active in
the shared file system environment at the same time.
10
© 2012 IBM Corporation
The z/OS UNIX file system

This is how an end user views the “top” of the z/OS

UNIX hierarchical file system.

It looks like files and directories organized in a

hierarchical tree:

u bin usr SYSTEM dev tmp var etc

11
© 2012 IBM Corporation
The z/OS UNIX hierarchical file system

u bin usr SYSTEM dev tmp var etc

$SYSNAME/dev $SYSNAME/var
$SYSNAME/tmp $SYSNAME/etc

bin usr dev tmp var etc

/bin /usr

This is a non-shared file system view,

as viewed by a system programmer.

12
© 2012 IBM Corporation
Shared File System Data Sets

Sysplex root:
–Only one for all systems in the shared file system
environment
–Does not contain z/OS system software itself, but contains
directories from which you mount z/OS system software.
–Is very small and should be mounted read-only. *

System-specific file systems:
–One per member in the shared file system environment.
–A place where system-specific file systems are mounted
(/etc, /var, /tmp, /dev)
–Does not contain z/OS system software itself.
–Is very small and should be mounted read-write.

Version root file systems:
–Contains the z/OS system software! This is where cloning
is concerned.
–Is rather large (thousands of cylinders)
–Should be mounted read-only. *

13 * UNMOUNT REMOUNT is helpful, if you need to add directories from time to time.
© 2012 IBM Corporation
The z/OS UNIX sysplex shared file system hierarchical
file system

Only one Sysplex Root File System

ZOSR12 ZOSR13 usr bin u SY1 SY2 dev tmp var etc

$VERSION/bin $SYSNAME/dev $SYSNAME/var

$VERSION/usr $SYSNAME/tmp $SYSNAME/etc
One Version Root File System per release or service level

/
/

One System Specific File System per member

u bin usr SYSTEM dev tmp var etc
u bin usr SYSTEM dev tmp var etc /

$SYSNAME/dev $SYSNAME/var bin usr dev tmp var etc

$SYSNAME/dev $SYSNAME/var
$SYSNAME/tmp $SYSNAME/etc
/bin /usr
$SYSNAME/tmp $SYSNAME/etc

bin usr dev tmp var etc

bin usr dev tmp var etc

/bin /usr
/bin /usr
14
© 2012 IBM Corporation
Some BPXPRMxx Statements for a Shared File System
Specification

SYSPLEX(YES) Indicates using shared file system environment

VERSION(‘ZOSR13') Indicates how you want the version identified

ROOT FILESYSTEM('OMVS.SYSPLEX.ROOT') TYPE(ZFS)

MODE(READ) The sysplex root – the same for every system

MOUNT FILESYSTEM('OMVS.&SYSNAME..SYSTEM.ZFS') TYPE(ZFS)

MODE(RDWR) UNMOUNT MOUNTPOINT('/&SYSNAME.')
The system-specific file system

MOUNT FILESYSTEM('OMVS.&ZFSVL..ROOT.ZFS') TYPE(ZFS)

MODE(READ) MOUNTPOINT('/$VERSION') The version root – shared between
systems if applicable

MOUNT FILESYSTEM('OMVS.&SYSNAME..ETC') TYPE(ZFS)

MODE(RDWR) UNMOUNT MOUNTPOINT('/&SYSNAME./etc')
…
15 When using system symbolics, these statement can be shared between systems!
© 2012 IBM Corporation
An Execution Example:
MOUNT FILESYSTEM('OMVS.&ZFSVL..ROOT.ZFS')
BPXPRMxx
TYPE(ZFS) MODE(READ) MOUNTPOINT('/$VERSION')

Master Catalog OMVS alias OMVS.&ZFSVL..UCAT

SY1 SY2
2’
2

3’

3 OMVS.SYSZ13.ROOT.ZFS
OMVS.SYSZ12.ROOT.ZFS
OMVS.SYSZ13.ROOT.ZFS
OMVS.SYSZ12.UCAT
OMVS.SYSZ13.UCAT

Volume: SYSZ12
Volume: SYSZ13
System Symbol &ZFSVL. = SYSZ12
System Symbol &ZFSVL. = SYSZ13

16 How do I clone to get this type of environment?

© 2012 IBM Corporation
A Servicing Example:
(same sysplex)

ZOSR12 ZOSR13 usr bin u SY1 SY2 dev tmp var etc SERVICE

$VERSION/bin $SYSNAME/dev $SYSNAME/var

$VERSION/usr $SYSNAME/tmp $SYSNAME/etc

ZOSR12 ZOSR13

Will deploy to…

OMVS.SYSZ12.ROOT.ZFS OMVSW2.SYSZ12.ROOT.WORK.ZFS

OMVS.SYSZ12.UCAT OMVS.SYWZ12.UCAT

OMVS.SYSZ13.ROOT.ZFS OMVSW1.SYSZ13.ROOT.WORK.ZFS
Volume: SYSZ12
OMVS.SYSZ13.UCAT Will deploy to… Volume: SYWZ12 OMVS.SYWZ13.UCAT
System Symbol &ZFSVL. = SYSZ12 System Symbol
&ZFSW2. = SYWZ12

Volume: SYSZ13 Volume: SYWZ13

System Symbol &ZFSVL. = SYSZ13 System Symbol &ZFSW1 = SYWZ13

17
© 2012 IBM Corporation
 A Service Example:
MOUNT FILESYSTEM('OMVS.&ZFSVL..ROOT.ZFS')
BPXPRMxx TYPE(ZFS) MODE(READ) MOUNTPOINT('/$VERSION')

MOUNT FILESYSTEM(‘OMVSW1.SYSZ13.ROOT.WORK.ZFS ')

TYPE(ZFS) MODE(READ) MOUNTPOINT('/SERVICE/ZOS13')
SY1 (Driving System)
1

Master Catalog
OMVSW1 alias OMVS.&ZFSW1..UCAT
SY2
OMVS.SYSZ13.ROOT.ZFS
OMVSW2 alias OMVS.&ZFSW2..UCAT
OMVS.SYSZ13.UCAT
OMVS alias OMVS.&ZFSVL..UCAT

Volume: SYSZ13
OMVS.SYSZ12.ROOT.ZFS
System Symbol &ZFSVL. = SYSZ13
OMVS.SYSZ12.UCAT

Volume: SYSZ12
OMVSW2.SYSZ12.ROOT.WORK.ZFS
System Symbol &ZFSVL. = SYSZ12
OMVS.SYWZ12.UCAT

OMVSW1.SYSZ13.ROOT.WORK.ZFS OMVS.SYSZ13.ROOT.ZFS

OMVS.SYWZ13.UCAT

Volume: SYWZ13

18 System Symbol &ZFSW1 = SYWZ13

© 2012 IBM Corporation

 A Service Example with
“Flip Flop” in use: MOUNT FILESYSTEM('OMVS.&ZFSVL..ROOT.ZFS')
BPXPRMxx TYPE(ZFS) MODE(READ) MOUNTPOINT('/$VERSION')

MOUNT FILESYSTEM(‘OMVSW1.SYSZ13.ROOT.WORK.ZFS ')

TYPE(ZFS) MODE(READ) MOUNTPOINT('/SERVICE/ZOS13')
SY1 (Driving System)
1

Master Catalog
OMVSW1 alias OMVS.&ZFSW1..UCAT
SY2
OMVS.SYSZ13.ROOT.ZFS OMVSW2 alias OMVS.&ZFSW2..UCAT

OMVS.SYSZ13.UCAT OMVS.&ZFSVL..UCAT
OMVS alias

OMVSW1A alias OMVS.&ZFSW1A.UCAT

Volume: SYSZ13
OMVS.SYSZ12.ROOT.ZFS
System Symbol &ZFSVL. = SYSZ13 OMVSW2A alias OMVS.&ZFSW2A.UCAT OMVS.SYSZ12.UCAT

Volume: SYSZ12
OMVSW2.SYSZ12A.ROOT.WORK.ZFS
OMVSW2.SYSZ12.ROOT.WORK.ZFS
System Symbol &ZFSVL. = SYSZ12
OMVS.SYWZ12A.UCAT
OMVS.SYWZ12.UCAT

OMVSW1.SYSZ13.ROOT.WORK.ZFS
OMVSW1.SYSZ13.ROOT.WORK.ZFS OMVS.SYSZ13.ROOT.ZFS

OMVS.SYWZ13A.UCAT
OMVS.SYWZ13.UCAT

Volume: SYZ13A

19 System Symbol &ZFSW1A = SYZ13A “Flip Flop” allows you to alternate between using different target volumes.
© 2012 IBM Corporation
Some observations for this example:

zFS was used, but it very well could have been HFS! Since the file
system must be cataloged to be mounted and accessed, it makes no
difference in our example whether we used HFS or zFS. We were looking
at the placement of the file systems, and how they were cataloged so that
we could get access to them concurrently.

The driving and target systems were in the same sysplex, and shared
volumes.
–This is a more complicated case then across-sysplexes, where sharing
isn’t done. The alias names in the same sysplex – when sharing the
master catalog – cannot clash. Across sysplexes, the alias names
used could be in common.

The alias names used (OMVS , OMVSW1, and OMVSW2) could have
used the target zone name, the volume name, or another name that is
helpful for you.
–System symbols for the usercat names were used, but aren’t
necessary.

The SERVICE mountpoints (ZOSR13 and ZOSR12) happen to match the
BPXPRMxx VERSION names. They could have been the target zone
name, the volume name, or another name that is helpful for you.

20
© 2012 IBM Corporation
How do I copy the version root file system, with
cataloging in mind?

Most people copy the file system data set using MVS utilities (as opposed to z/OS UNIX utilities
like pax or copytree).
– We will assume DFSMSdss will be used.

How you copy your z/OS system software data sets relies upon your environment for
deployment:
– Same sysplex or across sysplexes? Shared volumes? Installation data set names different
from execution data set names? SMS-managed?
• We’ll assume the environment we’ve shown previously. Other ways may work just as
well.

To copy (clone) the version root file system (either HFS or zFS), decide if you want:
– Full volume copy: will copy the entire volume (which may be more than you want or need,
depending on your environment). Note that this gives you another copy of the file system
with the same name, and only one can be cataloged at a time. Therefore, a subsequent
rename or recatalog may be necessary after this sort of copy if you want to access it.
• If you have any usercats on the volume, a full volume copy isn’t a good choice. For
zFS file systems that are using a usercat on the volume, this is not a recommended
choice.
– Data set copy:
• Logical data set copy: can rename the file system on the copy operation, and
depending on your catalog structure may be immediately accessible. A popular choice
that works well in many situations. (z/OSMF’s Software Deployment task uses this
method.)
• Physical data set copy: will provide you with a copy of the file system data set that is
not cataloged. A subsequent rename or recatalog may be necessary. Note that a
rename on a physical data set copy is not currently available.
• If you are using indirect zFS cataloging, this copy method is best, as you will
be using an existing catalog entry that makes the file system accessible.
21
© 2012 IBM Corporation
Logical data set copy for file system sample
//COPYFS EXEC PGM=ADRDSSU,REGION=0M
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
COPY DATASET( -
INCLUDE(OMVSW1.SYSZ13.ROOT.WORK.ZFS)) -
RENAMEU(OMVSW1.SYSZ13.ROOT.WORK.ZFS, -
OMVS.SYSZ13.ROOT.ZFS) -
OUTDYNAM(SYSZ13) –
CATALOG ALLDATA(*) ALLEXCP -
CANCELERROR

•This is applicable to either HFS or zFS.

•Logical data set copy is not recommended if using zFS indirect
cataloging support (which relies upon a system symbol for the
volume name).
•CATALOG follows normal catalog search order.
22
© 2012 IBM Corporation
zFS Indirect Cataloging Support (as of zOS R12)
• Allows for use of a system symbol as the volser for zFS data sets (not
other VSAM LDS data sets).
• Provides a simple and flexible way to clone zFS data sets, where you
do not need to rename the data set during the copy.
• Ideal for environments where the file system name doesn’t need to
change between the driving system and target system.
• May share mcat on those deployed target systems. (Remember
that unique mount name requirement, though!)
• Includes all non-shared file system environments.

SY2
Volume: OTHER
OMVS.ZOSR13.ROOT
SY1 OMVS.OTHER.UCAT System Symbol &ZFSVL. = OTHER
Will deploy to…

OMVS.ZOSR13.ROOT OMVS alias

OMVS.SYSZ13.UCAT
SY3
Volume: OTHER2
Volume: SYSZ13 OMVS.ZOSR13.ROOT
OMVS.OTHER2.UCAT System Symbol &ZFSVL. = OTHER2
System Symbol &ZFSVL. = SYSZ13
23
© 2012 IBM Corporation
Using zFS Indirect Cataloging Support:
Physical data set copy for file system sample
//COPYFS EXEC PGM=ADRDSSU,REGION=0M
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
COPY DATASET(INC(OMVS.ZOSR13.ROOT)) -
PHYSINDYNAM ( (SYSZ13) ) -
OUTDYNAM ( (OTHER) ) -
ALLDATA(*) •Creates an uncataloged copy.
•Cannot currently rename data sets during a physical copy.
•See quiescing note, may want to unmount file system first.

//RENAME EXEC PGM=IDCAMS,REGION=0M

//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DEFINE CLUSTER -
(NAME(OMVS.ZOSR13.ROOT) -
LINEAR -
VOLUMES(&ZFSVL) - •Recatalogs the zFS to start using the system symbol for the
RECATALOG) volume.
•Only needs to be recataloged once, so subsequent
deployments can reuse the catalog entry!
24
© 2012 IBM Corporation
A note about quiescing…
• When file systems (either HFS or zFS) are mounted and they need to
be copied or dumped, you need to understand about quiescing.
• When doing an DFSMSdss logical COPY or DUMP on a mounted file
system, DFSMSdss automatically will quiesce the file system.
• When doing a physical COPY or DUMP on a mounted file system,
DFSMSdss does not automatically quiesce the file system.
• This means that exclusive ENQs may not succeed during the
physical COPY or DUMP operation.
• To avoid exclusive ENQ failures, you can:
• Unmount the file system prior to the COPY or DUMP
• Attention: Exercise caution if you use TOL(ENQF) during a
physical copy or dump of zFS data sets. Unlike other types of data
sets, if a zFS data set is updated during a physical copy or dump
with TOL(ENQF), it will likely result in an unusable data set.
• Having a zFS mounted read-write during any copy or dump may result
in delays when the copied file system is subsequently used. Avoid the
delays by unmounting the file system before the copy or dump.
25
© 2012 IBM Corporation
Cloning Assistance

Documentation: z/OS Planning for Installation, Appendix D.

Making a copy of your system software (cloning)

JCL samples: IEACLN* samples in SYS1.SAMPLIB

z/OSMF’s Software Deployment (for z/OS R13):

–Use a GUI interface to define software instances and
deployments.
–Supports a local (same sysplex) deployment, or a remote
(across sysplexes) deployment.
–Produces customized JCL jobs for cloning, for you to
run.
• Supports HFS and zFS, but not zFS indirect
cataloging.
26
© 2012 IBM Corporation
z/OSMF Software Deployment

27
© 2012 IBM Corporation
Dynamically Activating z/OS UNIX Service

SY1 (Driving System)

OMVS.SYSZ13.ROOT.ZFS
OMVSW1.SYSZ13.ROOT.WORK.ZFS Is deploying to…. SYS1.LINKLIB
SYS1.LINKLIB SYS1.LPALIB
SYS1.LPALIB
OMVS.SYSZ13.UCAT
OMVS.SYWZ13.UCAT
Volume: SYSZ13

Volume: SYWZ13 System Symbol &ZFSVL. = SYSZ13

System Symbol &ZFSW1 = SYWZ13

To Use z/OS UNIX Dynamic Service Activation:

1.SMP/E install the corrective PTF on the “work” volume. (Allowed PTFs will be
marked with ++HOLD DYNACT.)
2.Set BPXPRMxx on “live” system, point to the target LINKLIB and LPALIB on “work”
• “work” LINKLIB and LPALIB must be APF authorized on “live” system
3.F OMVS,ACTIVATE=SERVICE to activate
4.D OMVS,ACTIVATE=SERVICE to view
5.F OMVS,DEACTIVATE=SERVICE to deactivate

28
© 2012 IBM Corporation
29
© 2012 IBM Corporation
30
© 2012 IBM Corporation
31
© 2012 IBM Corporation
32
© 2012 IBM Corporation
Summary

Data sets and file systems differences: can actively access data sets with
the same names on different volumes. Cannot mount (access) a file system
with the same name as one already mounted.

HFS and zFS differences - VSAM, and therefore catalog!

Catalog’s Role in using file systems – it’s got to be cataloged to be
mounted to be accessed. Use system symbols, use aliases!

Shared file system types: sysplex root, system-specific, and version root
file systems. Version root is where the cloning concerns usually stem.

Copying file system data sets – volume or data set? Logical or physical
copy? Keep catalog requirements in mind!

zFS indirect cataloging support – best when file system names do not
need to change when deploying

Quiescing – know when it’s done automatically for you, and what you may
do when it’s not automatic (unmount?)

Cloning assistance provided – documentation, samples in
SYS1.SAMPLIB, z/OSMF Software Deployment

Dynamic activating z/OS UNIX corrective service - can save you an IPL!

33
© 2012 IBM Corporation
References

z/OS Planning for Installation, especially Appendix D

z/OS DFSMS Managing Catalogs (Defining Aliases for a
User Catalog)

z/OS Basic Skills Information Center: z/OS system
installation and management

34
© 2012 IBM Corporation