Red
With tape capacity increasing, customers have requested that ABARS be changed to allow users the ability to stack aggregate backups onto a single tape. ABARS current design allows the customer to backup one aggregate to a minimum of one tape using the STACK parameter on the ABACKUP command. With the restriction of one aggregate backup per tape, the possibility exists, in the case of high capacity tapes, that much of the tape the aggregate resides on can be empty.
This document describes how customers can take existing aggregate backup output files and utilize MVS™ utilities to stack multiple aggregates or multiple versions of the same aggregate onto a single tape and recover any of these (stacked) aggregates.
© Copyright IBM Corp. 2008. All rights reserved.
ibm.com/redbooks 1

The DFSMShsm™ ABARS Aggregate Stacking Procedure is a procedure that describes how a customer can:
1. Stack multiple aggregate backup files onto a single tape volser.
2. Recover a specific aggregate backup from the tape.
3. Prevent the rolloff of a backup version on the tape, thus preventing tape expiration.
4. Delete a specific backup version from the tape.
5. RACF® protect the stacked tape.
6. Handle End of Volume (EOV) during the stacking process.
7. Cleanup after an error during the stacking process.
The examples in this procedure show two batch JCL jobs that can be used to create a single tape with two aggregate backups on it. Customers are not limited to two aggregates per tape.
In order to keep the JCL examples in this document easy to follow, however, two aggregates are used. The JCL examples provided can easily be modified in order to stack more than two aggregates.
Steps 1 and 2 below describe how to use the aggregate backup (ABACKUP) function to backup user defined aggregates (data), resulting in the creation of a tape on which the aggregate backup (output) files reside. The output files created as a result of an ABACKUP are named:
򐂰 the Control (C) file
򐂰 the Data (D) file
򐂰 the Other (O) data file
򐂰 the Instruction/Activity Log (I) file
In this procedure, all of the ABACKUP examples are executed using the STACK parameter on the command. This creates a single tape with the ABACKUP (C, D, O, and I) output files written to it. These are the files that make up each aggregate backup. Refer to the
DFSMShsm Storage Administration Guide, SC35-0421, for a description of what these
ABACKUP files contain.
The STACK parameter is a supported keyword that can be specified on the SETSYS
ABARSTAPES command or on the ABACKUP command. The STACK parameter has nothing to do with stacking multiple aggregates onto a tape. The STACK parameter means that
ABARS will attempt to place all aggregate backup output files, from a single instance of an aggregate backup, onto a single tape cartridge if they will fit. Prior to having the STACK parameter, the Control (C) file was always copied to a separate cartridge from the Data files
(D and O), meaning a single aggregate always used two or more cartridges. Even with the
STACK parameter specified, if the aggregate backup is large enough, the output files for that aggregate could span to multiple tape volumes.
In the procedure, aggregate backup number 1 is executed, resulting in a single output tape whose volser is A00040. The aggregate name used in the sample ABARS commands and
JCL is called AGM1.
2 DFSMShsm ABARS Aggregate Stacking Procedure

Next, a second ABACKUP of this aggregate is executed, once again using the STACK parameter on the ABACKUP command. This results in a second tape which now contains the output files associated with ABACKUP number 2. The volser, containing the files associated with the second aggregate backup, is A00041.
After Steps 1 and 2 are executed, there are two versions of the aggregate backup on two separate tapes.
Steps 3 and 4 below describe the process of stacking aggregate backup number 2 onto the same tape as aggregate backup number 1.
The ABACKUP output files, resulting from the first ABACKUP, reside on tape volser A00040 as shown:
ABACKUP
Output File
Data (D)
Other Data (O)
Instruction/Activity Log (I)
Control (C)
3
4
1
2
File Sequence
Number
ABACKUP output files resulting from the first ABACKUP
The ABACKUP output files, resulting from the second ABACKUP reside on tape volser
A000041 as shown.
ABACKUP
Output File
File Sequence
Number
Data (D)
Other Data (O)
Instruction/Activity Log (I
Control (C)
1
2
3
4
ABACKUP output files resulting from the second backup
To stack the ABACKUP output files associated with the second aggregate backup onto the same tape containing the files from the first aggregate backup, copy the sample batch JCL job named COPYAGGR JCL, shown in Example 1 on page 5, and make the changes necessary to fit your environment. These changes include updating the ABACKUP output file names in the DSN=dsname parameter and the tape volume serial number in the VOL=SER=tapevolser parameter.
DFSMShsm ABARS Aggregate Stacking Procedure 3

This JCL can be used to copy the D, O, I, and C files, associated with aggregate backup number 2, onto the same tape as where the ABACKUP files, associated with aggregate backup number 1 reside. The COPYAGGR job uses the IEBGENER program to copy the output files from one tape to the other.
If the copy is successful, the original output files are uncataloged and the copied files are cataloged on the stacked tape volume. In our example, after the COPYAGGR executes, the 2 aggregates will be “stacked” onto one tape (volser=A00040) in the following file sequence:
Aggregate backup number 1, on volser A00040, appears as:
ABACKUP
Output File
File Sequence
Number
Data (D)
Other Data (O)
Instruction/Activity Log (I)
Control (C)
1
2
3
4
Aggregate backup number 2, on volser A00040, appears as:
ABACKUP
Output File
File Sequence
Number
Data (D)
Other Data (O)
Instruction/Activity Log (I)
Control (C)
5
6
7
8
The sample COPYAGGR JCL batch job in Example 1 on page 5 can be used to stack
ABACKUP Version 2 onto the same tape as ABACKUP Version 1, thus stacking two versions of this aggregate onto a single tape.
This is the IEBGENER job that is used to copy the aggregate backup files from aggregate backup number 2 onto the tape containing the aggregate backup files associated with aggregate backup number 1, uncataloging the original backup 2 files and cataloging the newly copied versions of backup 2. Note that the aggregate backup file names, volsers, and labeling information designating the positioning on the tape where the files are to be written, are in bold. These parameters would need to be modified to successfully run this job in your environment.
4 DFSMShsm ABARS Aggregate Stacking Procedure

Example 1 COPYAGGR JCL
///COPYAGGR JOB ,CLASS=A,USER=userid,PASSWORD=pswd,
// MSGCLASS=A
//***************************************************************
//*
//* Job Name: COPYAGGR
//*
//* Function: STACK aggregate backup files onto a single tape.
//* *
//* Description of Process: This is a sample JCL batch job
//* that copies the aggregate backup output files from the
//* second ABACKUP of an aggregate named AGM1 onto the tape
//* where the files from the first ABACKUP of aggregate AGM1
//* reside, thus stacking both aggregate backups onto a single
//* tape.
//*
//* STEP 1, in this job, copies the D file, STEP 2 copies the
//* O file. STEP 3 copies the I file and STEP 4 copies the C
//* file. You will have to update the data set names (ABACKUP
//* files) and the tape volsers in each step in order to run this
//* job in your environment.
//*
//* To copy additional aggregate backups onto the stacked tape,
//* duplicate these 4 steps for each additional aggregate
//* backup and then update the ABACKUP output file (D, O, I or
//* C) names and the file sequence numbers.
//*
//* The job will copy the files from the original ABACKUP tape
//* onto the stacked tape, uncatalog the files from the original
//* tape and catalog the copied version onto the stacked tape.
//*
//* In order to recover any of the aggregates from the stacked
//* tape, use the ABARS ARECOVER command with the XMIT and
//* NOSTACK options specified.
//*
//* Example of ARECOVER command:
//*
//* ARECOVER DSN(control-file-name) XMIT NOSTACK EXECUTE
//*
//***************************************************************
//*
//***************************************************************
//* Copy the D file from the 2nd ABACKUP of aggregate AGM1 onto
//* the same tape containing the output files from the 1st
//* ABACKUP of aggregate AGM1. This D file is copied at file
//* sequence number 5. If the copy is successful uncatalog the
//* original version of the D file and catalog the new stacked
//* version.
//***************************************************************
//*--------------------------------------------------------------
DFSMShsm ABARS Aggregate Stacking Procedure 5

//STEP1 EXEC PGM=IEBGENER
//*--------------------------------------------------------------
//*
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD DSN=AGM1.D.C01V0002,DISP=(OLD,UNCATLG,KEEP)
//SYSUT2 DD DSN=AGM1.D.C01V0002,DISP=(NEW,CATLG,DELETE),
// UNIT=3480,LABEL=(5,SL),VOL=SER=A00040,
// DCB=(RECFM=U,LRECL=0,BLKSIZE=32760)
//SYSIN DD DUMMY
/*
//***************************************************************
//* Copy the O file from the 2nd ABACKUP of aggregate AGM1 onto
//* the same tape containing the output files from the 1st
//* ABACKUP of aggregate AGM1. This O file is copied at file
//* sequence number 6. If the copy is successful uncatalog the
//* original version of the O file and catalog the new stacked
//* version.
//***************************************************************
//*--------------------------------------------------------------
//STEP2 EXEC PGM=IEBGENER
//*--------------------------------------------------------------
//*
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD DSN=AGM1.O.C01V0002,DISP=(OLD,UNCATLG,KEEP)
//SYSUT2 DD DSN=AGM1.O.C01V0002,DISP=(NEW,CATLG,DELETE),
// UNIT=3480,LABEL=(6,SL),VOL=SER=A00040,
// DCB=(RECFM=U,LRECL=0,BLKSIZE=32760)
//SYSIN DD DUMMY
/*
//***************************************************************
//* Copy the I file from the 2nd ABACKUP of aggregate AGM1 onto
//* the same tape containing the output files from the 1st
//* ABACKUP of aggregate AGM1. This I file is copied at file
//* sequence number 7. If the copy is successful uncatalog the
//* original version of the I file and catalog the new stacked
//* version.
//***************************************************************
//*--------------------------------------------------------------
//STEP3 EXEC PGM=IEBGENER
//*--------------------------------------------------------------
//*
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD DSN=AGM1.I.C01V0002,DISP=(OLD,UNCATLG,KEEP)
//SYSUT2 DD DSN=AGM1.I.C01V0002,DISP=(NEW,CATLG,DELETE),
// UNIT=3480,LABEL=(7,SL),VOL=SER=A00040,
// DCB=(RECFM=U,LRECL=0,BLKSIZE=32760)
//SYSIN DD DUMMY
/*
//***************************************************************
//* Copy the C file from the 2nd ABACKUP of aggregate AGM1 onto
//* the same tape containing the output files from the 1st
//* ABACKUP of aggregate AGM1. This C file is copied at file
//* sequence number 8. If the copy is successful uncatalog the
//* original version of the D file and catalog the new stacked
//* version.
6 DFSMShsm ABARS Aggregate Stacking Procedure

//***************************************************************
//*--------------------------------------------------------------
//STEP4 EXEC PGM=IEBGENER
//*--------------------------------------------------------------
//*
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD DSN=AGM1.C.C01V0002,DISP=(OLD,UNCATLG,KEEP)
//SYSUT2 DD DSN=AGM1.C.C01V0002,DISP=(NEW,CATLG,DELETE),
// UNIT=3480,LABEL=(8,SL),VOL=SER=A00040,
// DCB=(RECFM=U,LRECL=0,BLKSIZE=32760)
//SYSIN DD DUMMY
//***************************************************************
//* To stack additional versions of the aggregate onto this tape,
//* copy the 4 steps that make up this JCL batch job, then update
//* the ABACKUP (D, O, I and C) file names and the file sequence
//* number.
//***************************************************************
/*
Step 4 explains how to recover any of the aggregates from the stacked tape.
The Aggregate Recovery (ARECOVER) of the (stacked) aggregate has to be done using both the XMIT and NOSTACK parameters on the ARECOVER command. Example 2 shows an example of an ARECOVER command with the XMIT and NOSTACK parameters used. It shows the syntax of the ARECOVER command needed to recover an aggregate that has gone through the stacking process described in this procedure. The name of the control data set, associated with the aggregate you want to recover, would replace
in the sample command.
Example 2 ARECOVER command using XMIT and NOSTACK parameters
ARECOVER DSN(control-file-name) XMIT NOSTACK EXECUTE
Step 5 shows how to prevent Aggregate Roll Off processing.
During normal processing, when a new version of an aggregate group is created, ABARS ensures that the number of versions kept does not exceed the amount specified by the
NUMBER OF VERSIONS attribute in the Management Class. If NUMBER OF VERSIONS is exceeded, ABARS rolls off (deletes) the oldest version of that aggregate. The ABARS activity log(s) associated with the aggregate are also deleted.
When an aggregate group is removed during roll off processing, the output files (C, D, O, and
I) associated with that aggregate are located in the catalog, and a list of volume serial numbers that these files reside on, are requested. When necessary, the volumes are deleted from the RACF HSMABR tape volume set.
DFSMShsm ABARS Aggregate Stacking Procedure 7

If SETSYS EXITON(ARCTVEXT) has been specified, installation exit ARCTVEXT is called for each volume being processed, indicating to the exit that the volume being expired is an
ABARS tape volume. If the installation has installed DFSMSrmm™, the EDGTVEXT installation exit is called rather than the ARCTVEXT.
Since we are stacking multiple aggregates on a tape unbeknownst to ABARS, we need to prevent aggregate roll off processing from occurring. If we allow it to occur, we run the risk of having the tape associated with the oldest aggregate expire, even though it still contains valid stacked aggregates on it. This section of the stacking procedure shows you how to prevent
(stacked) aggregates from rolling off.
To prevent aggregate roll off processing from automatically occurring, modify the
Management Class definition found in the ISMF panels for Management Class attributes that apply to ABARS processing. The # Versions field value needs to be changed to NOLIMIT. The
Management Class panel shown in Figure 1 contains the updated value in the # Versions field that will prevent aggregate roll off from happening. ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss
MANAGEMENT CLASS ALTER Page 5 of 5
Command ===>
SCDS Name . . . . . . : HSMATH0.AB1H0PC6.SCDS
Management Class Name : MCLASS1
To ALTER Management Class, Specify:
AGGREGATE Backup Attributes:
# Versions . . . . . . . . NOLIMIT (1 to 9999, NOLIMIT or blank)
Retain Only Version . . . (1 to 9999, NOLIMIT or blank)
Unit . . . . . . . . . . (D=days, W=weeks, M=months, Y=years or
blank)
Retain Extra Versions . . (1 to 9999, NOLIMIT or blank)
Unit . . . . . . . . . . (D=days, W=weeks, M=months, Y=years or
blank)
Copy Serialization . . . . (C=continue, F=fail or blank)
Abackup Copy Technique . . S (P=Conc Preferred, R=Conc Required or
S=Standard)
Use ENTER to Perform Verification; Use UP Command to View previous Panel;
Use HELP Command for Help; Use END Command to Save and Exit; CANCEL to Exit.
Figure 1 ISMF Management Class Alter panel with # Versions parameter
Figure 1 shows page 5 of the ISMF MANAGEMENT CLASS ALTER panels. Note the
# Versions parameter field is changed to NOLIMIT to prevent aggregate roll off.
According to the HELP panel associated with the # Versions parameter, changing it to the value of NOLIMIT equates to “No automatic roll-off of aggregate backup versions occurs.”
This means the roll off of the oldest aggregates and their associated activity logs have to be done manually by the customer or wait until all of the aggregates on a tape are deemed old and use the EXPIREBV ABARSVERSIONS command to expire every aggregate on the tape.
8 DFSMShsm ABARS Aggregate Stacking Procedure

In Step 6 we show how to delete specific versions of an Aggregate from a stacked tape.
Because the Management Class attribute # Versions was changed to NOLIMIT (see “Step 5” on page 7) in order to prevent the roll off of older versions of an aggregate on a stacked tape, one must use the EXPIREBV ABARSVERSIONS command to expire/delete specific versions of an aggregate backup from the stacked tape.
The format of the EXPIREBV command used to expire aggregate backup versions is shown in Figure 2, where
is the aggregate group name and n represents the number of versions of that aggregate to keep.
EXPIREBV EXECUTE ABARSVERSIONS(AGNAME(aggregate_name) RETAINVERSIONS(n))
Figure 2 EXPIREBV command to expire aggregate backup versions
For instance, if there are four versions of aggregate AGM1 stacked onto one tape, and the oldest version needs to be deleted, the EXPIREBV command to accomplish this is shown in
Figure 3.
EXPIREBV EXECUTE ABARSVERSIONS(AGNAME(AGM1) RETAINVERSIONS(3))
Figure 3 Example of EXPIREBV command expiring the oldest of four versions
After this command executes, the oldest version is deleted from the stacked tape and the 3 versions backed up after the oldest version are kept.
Step 7 shows how to use RACF to protect a tape that is used to stack aggregate backup files.
If a new tape is to be used to stack aggregate backup files and that tape is to be RACF protected, use the commands shown in Figure 4, where
is the stacked tape’s volume serial number
.
SETSYS TAPESECURITY(RACF)
RDEFINE TAPEVOL HSMABR
RALTER TAPEVOL HSMABR ADDVOL(volser)
Figure 4 RACF commands to protect a new stacked tape
If a tape with a pre-existing ABACKUP version is used to stack additional aggregates, and if
RACF is the desired security method, use the commands shown in Figure 5.
SETSYS TAPESECURITY(RACF)
RDEFINE TAPEVOL HSMABR
Figure 5 RACF commands for pre-existing tape
DFSMShsm ABARS Aggregate Stacking Procedure 9

During ABACKUP processing of the second aggregate on the tape, ABARS will add the tapes it uses to RACF. The ARC6075I message in Figure 6 is issued during the ABACKUP process indicating this.
ARC6075I TAPE VOLUME volser SUCCESSFULLY ADDED TO ABARS RACF TAPE VOLUME SET
Figure 6 ABACKUP message ARC075I indicating tape added to RACF
Step 8 takes you through the RACF protection of a stacked tape when specific aggregate backup versions are expired from a stacked tape.
When the EXPIREBV ABARSVERSIONS command is used to expire specific aggregate backup versions from a stacked tape, EXPIREBV processing automatically removes the tape from DFSMShsm’s RACF tape volume set. The ARC0353I message is issued during
EXPIREBV processing of an aggregate as shown in Figure 7.
ARC0353I TAPE VOLUME volser SUCCESSFULLY REMOVED FROM DFSMSHSM'S RACF TAPE
VOLUME SET
Figure 7 Message ARC0353I after EXPIREBV processing of an aggregate
If there are still valid aggregate backup versions on the stacked tape, issue the RALTER command in Figure 8 to add the volser back in DFSMShsm’s RACF tape volume set, where
is the stacked tape’s volume serial number.
RALTER TAPEVOL HSMABR ADDVOL(volser),
Figure 8 RACF command to RACF protect tape after EXPIREBV ABARSVERSIONS command
To remove a stacked tape from DFSMShsm’s RACF tape volume set, the RACF RALTER command shown in Figure 9 is used to accomplish this, where
is the stacked tape’s volume serial number.
RALTER TAPEVOL HSMABR DELVOL(volser)
Figure 9 RACF command to remove a stacked tape from RACF tape volume set
10 DFSMShsm ABARS Aggregate Stacking Procedure

Step 9 takes you through End of Volume (EOV) processing when stacking onto a single tape.
If you try to maximize the number of aggregate backup versions you can stack onto a single tape, there is a high probability of hitting EOV. If EOV occurs prior to copying all of the
ABACKUP files associated with a specific version, the error message IEC151I shown in
Figure 10 will display.
IEC151I A13-rc,mod,jjj,sss, ddname .-#.,dev,ser,dsname
Figure 10 Message IEC151I related to EOV processing
For example, if the COPYAGGR JCL shown in this procedure failed during the copy of the O file, in JCL STEP2, DDNAME SYSUT2, using output device address 0B31, writing to volser
A00040, writing the data set AGM1.O.C01V0002, the message in Figure 11 would be issued.
IEC151I A13-18,IFG0195B,COPYAGGR,STEP2,SYSUT2,0B31,A00040,AGM1.O.C01V0002
Figure 11 IEC151I message indicating EOV processing
If an EOV error occurs during the aggregate copy (stacking) job, you will not be able to recover that aggregate without first following the procedure described in the next procedure.
Step 10 takes you through the tasks to cleanup after an error during the stacking procedure.
If a problem occurs during the stacking procedure, you will need to uncatalog the ABACKUP files associated with the bad aggregate version on the stacked tape, and recatalog the files on the original backup tape.
In the EOV example shown in “Step 9” on page 11, the EOV error occurred during the write of the O file. In the COPYAGGR sample JCL, the D file is copied first, followed by the O, the I, and the C file. After the EOV error, version 2 of aggregate AGM1 has all of the D file and part of the O file on the stacked volser (A00040) and the I and C files are on the original volser
(A00041). In order to clean this up, so you can recover the data associated with version 2 of aggregate AGM1 or attempt to stack this version onto a new tape, you need to:
1. Uncatalog the D and O file that reside on the stacked tape A00040.
2. Recatalog the D and O files, just uncataloged, onto their original volser A00041.
Example 3 on page 12 contains sample JCL that can be used to recatalog an entire aggregate onto the original ABACKUP file. The sample JCL demonstrates how to recatalog all of the ABACKUP files associated with version 2 of aggregate AGM1 onto the original
ABACKUP volser.
DFSMShsm ABARS Aggregate Stacking Procedure 11

Example 3 JCL to recatalog an entire aggregate onto the original ABACKUP file
//DEFNVSAM JOB ,CLASS=A,USER=userid,PASSWORD=pswd,
// MSGCLASS=A
//******************************************************************
//* *
//* Job Name: DEFNVSAM *
//* *
//* Function: Use this job to catalog the ABACKUP output files, *
//* onto their original tape volser, when an error occurs during *
//* the IEBGENER stacking JCL job. *
//* *
//* Before running this job, make sure and ABACKUP files, *
//* associated with the failed aggregate copy, are uncataloged. *
//* *
//******************************************************************
//*
//*----------------------------------------------------------------
//STEP0001 EXEC PGM=IDCAMS Catalog D file
//*----------------------------------------------------------------
//SYSPRINT DD SYSOUT=A
//SYSABEND DD DUMMY
//SYSIN DD *
DEFINE NONVSAM -
(NAME(AGM1.D.C01V0002) -
DEVICETYPES(3480) -
FILESEQUENCENUMBERS(1) -
VOLUMES(A00041)) -
CATALOG(HSMLIBC.USERCAT)
/*
//*----------------------------------------------------------------
//STEP0002 EXEC PGM=IDCAMS Catalog O file
//*----------------------------------------------------------------
//SYSPRINT DD SYSOUT=A
//SYSABEND DD DUMMY
//SYSIN DD *
DEFINE NONVSAM -
(NAME(AGM1.O.C01V0002) -
DEVICETYPES(3480) -
FILESEQUENCENUMBERS(2) -
VOLUMES(A00041)) -
CATALOG(HSMLIBC.USERCAT)
/*
//*----------------------------------------------------------------
//STEP0003 EXEC PGM=IDCAMS Catalog I file
//*----------------------------------------------------------------
//SYSPRINT DD SYSOUT=A
//SYSABEND DD DUMMY
//SYSIN DD *
DEFINE NONVSAM -
(NAME(AGM1.I.C01V0002) -
DEVICETYPES(3480) -
FILESEQUENCENUMBERS(3) -
VOLUMES(A00041)) -
12 DFSMShsm ABARS Aggregate Stacking Procedure

CATALOG(HSMLIBC.USERCAT)
/*
//*----------------------------------------------------------------
//STEP0004 EXEC PGM=IDCAMS Catalog C file
//*----------------------------------------------------------------
//SYSPRINT DD SYSOUT=A
//SYSABEND DD DUMMY
//SYSIN DD *
DEFINE NONVSAM -
(NAME(AGM1.C.C01V0002) -
DEVICETYPES(3480) -
FILESEQUENCENUMBERS(4) -
VOLUMES(A00041)) -
CATALOG(HSMLIBC.USERCAT)
This paper was produced by a team of specialists working with the International Technical
Support Organization, San Jose Center team.
Ed Baker is a Senior Software Engineer in the United States. He has 30 years of experience in z/OS® system software development and services. He holds a Bachelor of Science degree in Business Administration from the University of Arizona. His areas of expertise include
DFSMShsm and ABARS. He has written extensively on DFSMShsm/ABARS and Disaster
Recovery topics.
Bill Pulver is a Software Engineer who has worked in z/OS DFSMS™ software test, service and development for 20 years. He has worked for IBM® for 28 years at the Tucson, Arizona site. His areas of expertise are DFSMShsm and DFSMS SDM. He has a Bachelors of
Science degree from the University of Arizona.
Thanks to the following people for their contributions to this project:
Mary Lovelace
International Technical Support Organization, San Jose Center
Lyn Ashton
Glenn Wilcock
DFSMShsm development
DFSMShsm ABARS Aggregate Stacking Procedure 13

14 DFSMShsm ABARS Aggregate Stacking Procedure

This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area.
Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785 U.S.A.
The following paragraph does not apply to the United Kingdom or any other country where such
provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION
PROVIDES THIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of 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.
This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products.
All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.
© Copyright International Business Machines Corporation 2008. All rights reserved.
Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by
GSA ADP Schedule Contract with IBM Corp.
15

This document REDP-4444-00 was created or updated on July 30, 2008.
Send us your comments in one of the following ways:
򐂰 Use the online Contact us review Redbooks form found at:
ibm.com/redbooks
򐂰 Send your comments in an email to: redbooks@us.ibm.com
򐂰 Mail your comments to:
IBM Corporation, International Technical Support Organization
Dept. HYTD Mail Station P099
2455 South Road
Poughkeepsie, NY 12601-5400 U.S.A.
®
Red
™
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines
Corporation in the United States, other countries, or both. These and other IBM trademarked terms are marked on their first occurrence in this information with the appropriate symbol (® or ™), indicating US registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtml
The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both:
DFSMS™
DFSMShsm™
DFSMSrmm™
IBM®
MVS™
RACF®
Redbooks (logo) z/OS®
®
Other company, product, or service names may be trademarks or service marks of others.
16 DFSMShsm ABARS Aggregate Stacking Procedure