Browse Prior Art Database

Indirect VOLSER Support to Facilitate Migration of UNIX System Services zSeries File Systems

IP.com Disclosure Number: IPCOM000191495D
Original Publication Date: 2010-Jan-05
Included in the Prior Art Database: 2010-Jan-05
Document File: 4 page(s) / 58K

Publishing Venue

IBM

Abstract

Disclosed is a method and system to facilitate the migration of UNIX System Services zSeries file systems by allowing the definition of indirect volume serial names for zFS linear data sets.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 4

Indirect VOLSER Support to Facilitate Migration of UNIX System Services zSeries File Systems

Z/OS system programmers migrate their Unix System Services zSeries file systems (zFS) from one release to another. System programmers, in general, apply maintenance to a test environment in a separate sysplex. System programmers use cloning to copy the System Residence Volumes into the production environment in order to bring the changes into production. The cloning process is derived from IBM recommendations and Redbook examples. After IBM removed the constraint that Hierarchical File Systems had to be SMS managed, system programmers were able to integrate Unix System Services Maintenance into this process by simply moving the USS Version-Root onto the System Residence Volumes.

The cloning of non-VSAM datasets like HFS use the extended indirect volume serial (VOLSER) support. Indirect VOLSER support uses a system symbol in the VOLSER field contained in the catalog data set record. When a VOLSER is requested, a z/OS system facility converts the system symbol to a real VOLSER unique to the system performing the request. Thus, in a shared catalog environment, the data set entry in a catalog need only be defined once with one indirect VOLSER. Systems can then access a particular data set on that system using the one catalog data set entry.

But, with zFSs, IBM introduced a new inhibitor. zFSs are VSAM based using Linear Data Sets (LDS). There is no indirect VOLSER support for VSAM data sets. Since zFSs are based on VSAM LDSs, zFSs are difficult to clone because a specific volume serial is required by VSAM for each z/OS system.

VSAM data set name entries must be be unique. In order to achieve the same functionality as HFS cloning, users must have symbols like &SYSCLONE or &SYSNAME as qualifiers for VSAM data sets.

In short , zFS users require extended indirect VOLSER support for zFS cloning.

Described is a new function which provides a method for indirect VOLSER support of zFS VSAM data sets. In order to use the new function, a system programmer must define a system symbolic in a SYS1.PARMLIB member (IEASYMxx). Then, a VSAM LDS is defined using a real volser. This LDS will be used for the zFS. Next, the USS IOEAGFMT utility is run using the LDS. IOEAGFMT formats the LDS as a zFS dataset, turns on the zFS indicator in the catalog data set record, and builds the zFS control blocks. A DELETE NOSCRATCH is then performed on the data set catalog entry. This removes the data set entry from the catalog, and hence, the reference to the particular VOLSER. A DE...