IBM Systems Magazine, Mainframe - July/August 2012 - (Page 48)

Administrator Getting the most from your systems The Wonders of z/OS Spool Migration JES2 helps expedite the relocation of data volumes By Tom Wasik, Alexei Pytel and Kevin Kathmann oes your spool configuration contain volumes residing on an antiquated DASD? Would you like to merge those volumes and place them on a DASD using the latest and greatest technology? Spool migration allows an installation to consolidate such volumes in a nondisruptive and expeditious manner. Similar efforts, which previously might have taken weeks, can now be accomplished in a few hours. During and after migration, applications can seamlessly read from and write to migrating volumes without interruption. Applications need not be quiesced during migration. Job Entry Subsystem 2 ( JES2) automatically handles and maps existing spool addresses (MTTR/MQTRs) during and after the migration. Once completed, all migrated data exists on the target volume, and the source volume data sets can be removed. through the simple case of migrating an existing volume, SPOOL2, into another, SPOOL5. First, identify the DASD volumes you wish to migrate. These are potential source volumes for the spool-migration command. Next, identify the DASD volumes that will contain the migrated data, or the potential target volumes. We want to migrate data on SPOOL2 to the data set on SPOOL5. Once participating volumes have been identified, you must verify space requirements. Use the JES2 command $D SPL with the MIGDATA parameter: $D SPL(SPOOL2),MIGDATA D Editor’s note: This overview of Job Entry Subsystem 2 (JES2) spool migration, included in z/OS release 13, is the first article in a four-part series. Successive articles cover more technical details and can be found at IBM JES2 team members Steve Simonson, a senior software engineer, and Bruce Talbott, an advisory software engineer, also contributed to this article. Start With the Basics The following example covers premigration planning, migration phases, post migration, and mapped volume status. Spool migration is a simple way to quickly move data onto new hardware with new features. Many scenarios exist for using spool migration. In this one, we’ll walk MIGDATA displays two pieces of information. The first, SPACE_USED, indicates the highest used track in the SPOOL2 data set. This is the high-water mark of spool usage on SPOOL2, and it defines the size of the data within 48 J U LY/AU G U S T 2 0 12

Table of Contents for the Digital Edition of IBM Systems Magazine, Mainframe - July/August 2012

Editor's Desk: The Taste of Success
Dashboard: Pay by Phone - Current Conditions - Work Without Boundaries - Digital Personalities
IBM Perspective: The Performance of Many, the Efficiency of One
Trends: Why zBX Outperforms DIY When Deploying a Hybrid Infrastructure
Q&A: Accurate TCO Analysis Demonstrates the True Value of System z
IT Today: IBM's Integrated Solution for System z Streamlines Software Delivery
Case Study: Taking Shelter From the Storm: Shelter Insurance employs a measured approach in adopting Linux on zEnterprise 114
Cover Story: Internal Transformation: System z is at the center of initiative, which has saved the company $100 million so far
Feature: Large Memory Tames Big Data: The System z stack evolves to deliver business value from more memory
Tech Corner: A More Effective Comparison Starts With Relative Capacity
Administrator: JES2 Helps Expedite the Relocation of Data Volumes
Solutions: Double-Take Share 5.0 - Vanguard Security and Compliance Solutions - MegaCryption DB - ASG-TMON for DB2 - Reflection Suite for X - Orchestrated IT
Advertiser's Index
Stop Run: Wreck Diving Brings IBMer Face to Face With Lost History
Reference Point - Global Events, Education, Resources for Mainframe
IB Tape Storage

IBM Systems Magazine, Mainframe - July/August 2012