DFSMSdss Storage Administration Manual

DFSMS/MVS Version 1 Release 5
IBM
DFSMSdss Storage Administration

Reference
SC26-4929-04
IBM

Reference
SC26-4929-04
Note!
Before using this information and the product it supports, be sure to read the general information under Notices on page ix.
Fifth Edition (March 1999)

This edition applies to Version 1 Release 5 of DFSMS/MVS (5695-DF1), Release 7 of OS/390 (5647-A01), and to any later releases
until otherwise indicated in new editions.
This edition replaces and makes obsolete the previous edition, SC26-4929-03. Significant changes are summarized under Summary
of Changes on page xv. Specific changes are indicated by a vertical bar in the left margin.
Consult the latest edition of the applicable IBM system bibliography for current information on this product.
The following paragraph does not apply to any 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
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.
Order IBM publications from your IBM representative or the IBM branch office serving your locality. Publications are not stocked at
the address given below.
A Reader's Comment Form is provided at the back of this publication. Either mail the form, or fax it to 1 (520) 799-2906. If the form
has been removed, address your comments about this book to IBM Corporation, Department 61C, 9000 South Rita Road, Tucson,
Arizona 85744-0001, U.S.A.
You can send your comments electronically to starpubs@vnet.ibm.com
When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes
appropriate without incurring any obligation to you.
Copyright International Business Machines Corporation 1984, 1999. All rights reserved.
Note to U.S. Government Users Documentation related to restricted rights Use, duplication or disclosure is subject to
restrictions set forth in GSA ADP Schedule Contract with IBM Corp.
Contents
Notices . . . . . . . . . . . . . . . . . . . . . . . . . .
Programming Interface Information
. . . . . . . . . .
Trademarks . . . . . . . . . . . . . . . . . . . . . . . .
Do You Have Problems, Comments, or Suggestions?
Preface . . . . . . . . . . . . . . . .
Required Product Knowledge . . . .
How to Tell if a Book is Current . .
Required Books . . . . . . . . . . . .
Related Books
. . . . . . . . . . . .
Other DFSMS/MVS Publications
The Storage Management Library
MVS/ESA . . . . . . . . . . . . . .
Other Related Publications . . . .
Summary of Changes
Publication Updates .
Fifth Edition
. . . .
Fourth Edition . . .
Third Edition . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 2. FilteringChoosing the Data Sets You Want Processed

How DFSMSdss Filters Data Sets . . . . . . . . . . . . . . . . . . . . . .
Considerations for VSAM Data Sets:
. . . . . . . . . . . . . . . . . .
Filtering by Data Set Names . . . . . . . . . . . . . . . . . . . . . . . . .
Using an * in Partially Qualified Data Set Names . . . . . . . . . . . .
Using a % in Partially Qualified Data Set Names . . . . . . . . . . . .
Examples of Fully and Partially Qualified Data Set Names . . . . . .
Relative Generation Filtering . . . . . . . . . . . . . . . . . . . . . . . .
Filtering by Data Set Characteristics . . . . . . . . . . . . . . . . . . . . .
Some Examples of the BY Keywords
. . . . . . . . . . . . . . . . . .
Standard Catalog Search Order . . . . . . . . . . . . . . . . . . . . . . .
. .
. .
. .
. .
. .
. .
. .
. .
. . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
Chapter 3. SyntaxFunction Commands . . . . . . . . . . . . . . . . . .

What DFSMSdss Commands Can Do . . . . . . . . . . . . . . . . . . . . . .
Building the Stand-Alone IPL-able Core Image . . . . . . . . . . . . . . .
Backup and Recovery (Dump, Restore) . . . . . . . . . . . . . . . . . . .
Data Movement (COPY) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Conversion to and from Storage Management Subsystem (CONVERTV)
Space Management (COMPRESS, DEFRAG, RELEASE)
. . . . . . . .
Conversion from a PDS to a PDSE and from a PDSE to a PDS (COPY)
Copyright IBM Corp. 1984, 1999
xi
xi
. xi
. xi
xii
xii
xii
xiii
xiii
. . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 1. Specifying DFSMSdss Commands . . . . . . . . . . . . . . . .

Command Syntax
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How Many Subkeywords Are Allowed? . . . . . . . . . . . . . . . . . . . . . .
Specifying Subkeywords in a Command Data Set . . . . . . . . . . . . . . . .
How to Read Syntax Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . .
The JCL You Need . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Control DFSMSdss via PARM Information in the EXEC Statement
Examples of Invoking DFSMSdss with JCL . . . . . . . . . . . . . . . . . .
ix
ix
x
x
. .
. .
. .
. .
. .
. .
. .
. .
xv
xv
xv
xv
xvi
1
1
2
2
3
5
7
9
11
11
11
12
12
12
13
14
14
19
19
21
21
21
21
21
22
22
22
iii
Copying DFSMSdss-Produced Dump Data (COPYDUMP) . . .

Printing for Diagnostic Purposes (PRINT) . . . . . . . . . . . . .
BUILDSA Command . . . . . . . . . . . . . . . . . . . . . . . . . . .
BUILDSA Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . .
Explanation of BUILDSA Command Keywords . . . . . . . . . .
BUILDSA Command Examples . . . . . . . . . . . . . . . . . . .
COMPRESS Command . . . . . . . . . . . . . . . . . . . . . . . . .
COMPRESS Syntax
. . . . . . . . . . . . . . . . . . . . . . . . .
Explanation of COMPRESS Command Keywords . . . . . . . .
Example of Compress Operations
. . . . . . . . . . . . . . . . .
CONVERTV Command . . . . . . . . . . . . . . . . . . . . . . . . .
CONVERTV Command Syntax . . . . . . . . . . . . . . . . . . .
Explanation of CONVERTV Command Keywords
. . . . . . . .
Examples of CONVERTV Operations
. . . . . . . . . . . . . . .
COPY Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Special Considerations for Copy
. . . . . . . . . . . . . . . . . .
COPY DATASET Syntax . . . . . . . . . . . . . . . . . . . . . . .
COPY FULL and COPY TRACKS Syntax . . . . . . . . . . . . .
Explanation of COPY Command Keywords . . . . . . . . . . . .
Data Integrity Considerations for Full or Tracks Copy Operation
Examples of Full and Tracks Copy Operations . . . . . . . . . .
Examples of Data Set Copy Operations . . . . . . . . . . . . . .
ALLDATA and ALLEXCP Interactions . . . . . . . . . . . . . . .
COPYDUMP Command . . . . . . . . . . . . . . . . . . . . . . . . .
COPYDUMP Syntax . . . . . . . . . . . . . . . . . . . . . . . . .
Explanation of COPYDUMP Command Keywords . . . . . . . .
Examples of COPYDUMP Operations . . . . . . . . . . . . . . .
DEFRAG Command . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
DEFRAG Syntax
Explanation of DEFRAG Command Keywords . . . . . . . . . .
Examples of DEFRAG Operations . . . . . . . . . . . . . . . . .
Results of a Successful DEFRAG Operation . . . . . . . . . . .
DUMP Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Special Considerations for Dump . . . . . . . . . . . . . . . . . .
DUMP FULL and DUMP TRACKS Syntax . . . . . . . . . . . . .
DUMP DATASET Syntax for Logical Data Set . . . . . . . . . .
DUMP DATASET Syntax for Physical Data Set . . . . . . . . . .
Explanation of DUMP Command Keywords . . . . . . . . . . . .
Data Integrity Considerations for Full or Tracks Dump Operation
Format of the Output Data Set
. . . . . . . . . . . . . . . . . . .
Examples of Full and Tracks Dump Operations . . . . . . . . . .
Examples of Physical Data Set Dump Operations . . . . . . . .
Examples of Logical Data Set Dump Operations . . . . . . . . .
PRINT Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PRINT Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Explanation of PRINT Command Keywords . . . . . . . . . . . .
Examples of Print Operations . . . . . . . . . . . . . . . . . . . .
RELEASE Command
. . . . . . . . . . . . . . . . . . . . . . . . . .
RELEASE Syntax for Physical Processing . . . . . . . . . . . . .
RELEASE Syntax for Logical Processing . . . . . . . . . . . . .
Explanation of RELEASE Command Keywords . . . . . . . . . .
Example of a Release Operation . . . . . . . . . . . . . . . . . .
RESTORE Command . . . . . . . . . . . . . . . . . . . . . . . . . .
Special Considerations for Restore . . . . . . . . . . . . . . . . .
|
|
iv
DFSMS/MVS V1R5 DFSMSdss Storage Administration Reference
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
22
22
23
23
24
26
29
29
30
33
34
34
35
38
39
39
40
42
43
71
71
72
77
80
80
80
81
82
82
82
87
88
89
90
90
91
92
93
110
111
111
112
113
117
117
118
123
124
125
125
126
134
135
135
Data Integrity Considerations for Full or Tracks Restore Operations

RESTORE FULL and RESTORE TRACKS Command Syntax . . .
RESTORE DATASET Command Syntax for Logical Data Set . . .
RESTORE DATASET Command Syntax for Physical Data Set
. .
Explanation of RESTORE Command Keywords
. . . . . . . . . . .
DFSMSdss RESTORE Process . . . . . . . . . . . . . . . . . . . . .
Examples of Full and Tracks Restore Operations
. . . . . . . . . .
Examples of Physical Data Set Restore Operations . . . . . . . . .
Examples of Logical Data Set Restore Operations . . . . . . . . . .
Chapter 4. SyntaxAuxiliary Commands . .
Writing to the Operator with the WTO Command
Scheduling Tasks . . . . . . . . . . . . . . . . . .
SERIAL Command . . . . . . . . . . . . . . .
PARALLEL Command . . . . . . . . . . . . .
Controlling Task Processing
. . . . . . . . . . .
Condition Codes . . . . . . . . . . . . . . . . .
Setting Condition Codes . . . . . . . . . . . .
Using Condition Codes . . . . . . . . . . . . .
Ending Your DFSMSdss Step . . . . . . . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . .
Chapter 5. Stand-Alone Services of DFSMSdss . . . . .

Preparing to Run the New Stand-Alone Services Program .
. . . . . . .
Running Stand-Alone Services in 370 Mode
Running Stand-Alone Services in XA or ESA Mode . . .
Running Stand-Alone Services with a Predefined Console
Using a Tape Library . . . . . . . . . . . . . . . . . . . . .
Using an Automatic Cartridge Loader
. . . . . . . . . . .
Controlling Command Sequence Processing . . . . . . .
IPLing and Running the Stand-Alone Services Program . .
IPLing Stand-Alone Services
. . . . . . . . . . . . . . . .
RESTORE Restoring a Formatted Dump Tape . . . .
. . . .
TAPECNTL Rewinding and Unloading a Tape
Building the IPL-able Core Image . . . . . . . . . . . . . . .
The BUILDSA Function . . . . . . . . . . . . . . . . . . . .
Understanding BUILDSA Command Authorization Levels
Stand-Alone Services Hardware Requirements
. . . . . . .
Supported Processors . . . . . . . . . . . . . . . . . . . .
Supported Devices . . . . . . . . . . . . . . . . . . . . . .
Chapter 6. Data Security and Authorization Checking
Effects of SPECIAL, OPERATIONS, and DASDVOL . .
SPECIAL . . . . . . . . . . . . . . . . . . . . . . . . . .
OPERATIONS . . . . . . . . . . . . . . . . . . . . . . .
DASDVOL . . . . . . . . . . . . . . . . . . . . . . . . .
General Data Security Information . . . . . . . . . . . . .
Protecting Resources and Data Sets . . . . . . . . . .
Protecting Usage of DFSMSdss . . . . . . . . . . . . .
Password Protection . . . . . . . . . . . . . . . . . . .
. . . . . . . . .
Protected User and Group Data Sets
Generic and Discrete Profile Considerations
. . . . .
Security-Level, Category, and Label Checking . . . .
Protect-All and Always-Call
. . . . . . . . . . . . . . .
Standard Naming Conventions . . . . . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
Contents
136
136
137
138
139
166
169
170
172
177
177
177
177
178
178
178
179
180
183
185
185
186
186
187
188
190
190
190
192
196
201
202
202
202
203
203
203
207
207
207
208
208
209
209
209
210
210
211
213
213
213
DFSMSdss Temporary Data Set Names . . . . . . . . . . .

Discretely Protected Multivolume Data Set
. . . . . . . . .
Erase-on-Scratch . . . . . . . . . . . . . . . . . . . . . . . .
SMS-Managed Data Set Protection . . . . . . . . . . . . . .
Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DFSMSdss Storage Administrator . . . . . . . . . . . . . . . .
ADMINISTRATOR Keyword . . . . . . . . . . . . . . . . . .
FACILITY-Class Profiles for the ADMINISTRATOR Keyword
DFSMSdss Volume, Data Set and Catalog Access Authority
Volume Access and DASDVOL . . . . . . . . . . . . . . . .
Data Set Access Authorization Levels . . . . . . . . . . . .
Protected Catalogs . . . . . . . . . . . . . . . . . . . . . . .
Non-SMS Versus SMS Authorization . . . . . . . . . . . . .
System Operator Authorization, Special Data Set Types
.
Access Authorization for DFSMSdss Commands . . . . . . .
COMPRESS . . . . . . . . . . . . . . . . . . . . . . . . . . .
CONVERTV . . . . . . . . . . . . . . . . . . . . . . . . . . .
COPY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
COPYDUMP . . . . . . . . . . . . . . . . . . . . . . . . . . .
DEFRAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DUMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PRINT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RELEASE
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
RESTORE . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Appendix A. Compatibility Considerations . . .
Access Authority . . . . . . . . . . . . . . . . . . . .
ALLMULTI Keyword . . . . . . . . . . . . . . . . . .
Concurrent Copy . . . . . . . . . . . . . . . . . . . .
Track Overflow Support . . . . . . . . . . . . . . . .
DASD I/O Pacing . . . . . . . . . . . . . . . . . . . .
Disaster Recovery . . . . . . . . . . . . . . . . . . .
Validation of Indexed VSAM Data Sets . . . . . . .
Restoring Existing DFDSS Dumps using DFSMSdss
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . .
Appendix B. Data IntegritySerialization . . . . . . . .

Volume Serialization . . . . . . . . . . . . . . . . . . . . . .
Avoiding Lockout . . . . . . . . . . . . . . . . . . . . . .
The WAIT Option . . . . . . . . . . . . . . . . . . . . . .
Data Set Serialization . . . . . . . . . . . . . . . . . . . . .
EnqueuingENQ . . . . . . . . . . . . . . . . . . . . . .
Dynamic AllocationDYNALLOC . . . . . . . . . . . . .
Enqueuing versus Dynamic Allocation of Data Sets . .
Read/Write Serialization Scheme . . . . . . . . . . . . .
The WAIT Option . . . . . . . . . . . . . . . . . . . . . .
An Example of RESERVE-ENQUEUE Processing . . .
Backup-While-Open Data Sets CICS . . . . . . . . . . .
Backup-While-Open Status Meanings . . . . . . . . . .
Backup-While-Open Processing . . . . . . . . . . . . . .
. . . . . . .
Backup-While-Open and Concurrent Copy
TOLERATE(ENQFAILURE) and SHARE Considerations
Recovery Data . . . . . . . . . . . . . . . . . . . . . . . .
Backup-While-Open Data Sets IMS . . . . . . . . . . .
vi
. . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
213
215
215
215
216
216
216
217
218
218
221
222
223
223
223
224
224
224
230
230
230
231
231
231
237
237
237
237
237
237
238
238
238
241
241
242
243
243
243
244
244
245
246
248
249
250
251
252
252
253
253
Appendix C. Application Programming Interface . . . . . . . . . . . .

Calling Block Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User Interactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Programming Information . . . . . . . . . . . . . . . . . . . . . . .
Application Interface Blocks . . . . . . . . . . . . . . . . . . . . . . . . .
Exit Identification Block . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cross-Memory Application Interface Restrictions . . . . . . . . . . . . .
User Interaction Module Exit Option Descriptions . . . . . . . . . . . . . .
Function Startup (Eioption 0)
. . . . . . . . . . . . . . . . . . . . . . . .
Reading SYSIN Record (Eioption 1) . . . . . . . . . . . . . . . . . . . .
Printing SYSPRINT Record (Eioption 2) . . . . . . . . . . . . . . . . . .
Reading Physical Tape Record (Eioption 3) . . . . . . . . . . . . . . . .
Reading Logical Tape Record (Eioption 4)
. . . . . . . . . . . . . . . .
Writing Logical Tape Record (Eioption 5) . . . . . . . . . . . . . . . . .
Writing Physical Tape Record (Eioption 6) . . . . . . . . . . . . . . . . .
Reading Disk Track (Eioption 7)
. . . . . . . . . . . . . . . . . . . . . .
Writing Disk Track (Eioption 8) . . . . . . . . . . . . . . . . . . . . . . .
Reading Utility SYSPRINT (Eioption 9) . . . . . . . . . . . . . . . . . . .
Writing SYSPRINT Record (Eioption 10) . . . . . . . . . . . . . . . . . .
Writing WTO Message (Eioption 11) . . . . . . . . . . . . . . . . . . . .
Writing WTOR Message (Eioption 12) . . . . . . . . . . . . . . . . . . .
Presenting ADRUFO Record (Eioption 13)
. . . . . . . . . . . . . . . .
Function Ending (Eioption 14) . . . . . . . . . . . . . . . . . . . . . . . .
Presenting WTOR Response (Eioption 15) . . . . . . . . . . . . . . . .
OPEN/EOV Tape Volume Security and Verification Exit (Eioption 16) .
OPEN/EOV Nonspecific Tape Volume Mount (Eioption 17) . . . . . . .
Insert Logical VSAM Record During Restore (Eioption 18) . . . . . . .
Output Tape I/O Error (Eioption 19)
. . . . . . . . . . . . . . . . . . . .
Volume Notification (Eioption 20) . . . . . . . . . . . . . . . . . . . . . .
Data Set Verification (Eioption 21) . . . . . . . . . . . . . . . . . . . . .
Bypass Verification Exit (Eioption 22)
. . . . . . . . . . . . . . . . . . .
Data Set Processed Notification Exit (Eioption 23) . . . . . . . . . . . .
Concurrent Copy Initialization Complete (Eioption 24) . . . . . . . . . .
Dump Volume Output Notification (Eioption 26) . . . . . . . . . . . . . .
Avoiding Lockout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Application Interface Summary . . . . . . . . . . . . . . . . . . . . . . . . .
ADREID0 Data Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Constants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cross Reference
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example: Invoking DFSMSdss by Using an Application Program . . . . .
How to Determine DFSMSdss Version, Release, and Modification Level
255
255
258
259
259
260
263
264
264
264
265
265
266
266
266
267
267
267
267
268
268
268
268
269
269
269
269
270
270
270
271
274
275
277
277
277
278
282
282
284
284
. . . .
287
. . . . . . . . . . . . . . . . . . . . . . . .
307
Appendix D. Examples of the Application Program with the User

Interaction Module (UIM) . . . . . . . . . . . . . . . . . . . . . . . . .
Appendix E. Data Set Attributes
Appendix F. Customizing ISMF . . .

ISMF Libraries That Can Be Customized
Restrictions to Customizing ISMF . .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. . . . . . . . . . . . . . . . . . . . . .
311
311
311
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
313
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
323
Glossary
Index
. .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . .
Contents
vii
viii
Notices
References in this publication to IBM products, programs, or services do not imply
that IBM intends to make these available in all countries in which IBM operates.
Any reference to an IBM product, program, or service is not intended to state or
imply that only IBMs product, program, or service may be used. Any functionally
equivalent product, program, or service that does not infringe any of IBMs
intellectual property rights or other legally protectible rights may be used instead of
the IBM product, program, or service. Evaluation and verification of operation in
conjunction with other products, programs, or services, except those expressly
designated by IBM, are the users responsibility.
IBM may have patents or pending patent applications covering subject matter 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 154-1785
USA
Programming Interface Information

This publication primarily documents information that is NOT intended to be used
as a Programming Interface of DFSMSdss.
This publication also documents intended Programming Interfaces that allow the
customer to write programs to obtain the services of DFSMSdss. This information is
identified where it occurs either by an introductory statement to a section by the
following marking:
Programming Interface information
End of Programming Interface information
Licensees of this program who wish to have information about it for the purpose of
enabling: (i) the exchange of information between independently created programs
and other programs (including this one) and (ii) the mutual use of the information
which has been exchanged, should contact:
IBM Corporation
Information Enabling Requests
Dept. DZWA
56 Cottle Road
San Jose, CA 95193
U.S.A.
Such information may be available, subject to appropriate terms and conditions,
including in some cases, payment of a fee.
ix
Trademarks
The following terms are trademarks of the IBM Corporation in the United States or
other countries or both:
AIX
CICS
DFSMS
DFSMS/MVS
DFSMSdss
DFSMShsm
ESA/370
ESA/390
ES/9000
Hiperspace
IBM
MVS/ESA
OpenEdition
OS/390
RACF
RAMAC
System/370
System/390
S/370
S/390
Do You Have Problems, Comments, or Suggestions?
|
|
|
|
Your suggestions and ideas can contribute to the quality and the usability of this
book. If you have problems in using this book or if you have suggestions for
improving it, please complete and mail the readers' comments form found at the
back of the book.
You can also send comments to us electronically:
|
|
|
|
IBMLink from US: STARPUBS at SJEVM5

IBMLink from Canada: STARPUBS at TORIBM
IBM Mail Exchange: USIB3VVD at IBMMAIL
Internet: starpubs@us.ibm.com
Preface
This manual describes the DFSMSdss commands, and it is intended for the storage
administrator and the system programmer. Its purpose is to explain the command
syntax to perform various storage management tasks.
Required Product Knowledge

To use this manual, you need some knowledge of DFSMSdfp, DFSMShsm,
Resource Access Control Facility (RACF, an element of the OS/390 Security
Server), and job control language (JCL).
How to Tell if a Book is Current

IBM regularly updates its books with new and changed information. When first
published, both hardcopy and BookManager softcopy versions of a book are
identical, but subsequent updates may be available in softcopy before they are
available in hardcopy. Here's how to determine the level of a book:
Check the book's order number suffix (often referred to as the dash level). A
book with a higher dash level is more current than one with a lower dash level.
For example, in the publication order number SC26-4930-02, the dash level 02
means that the book is more current than previous levels, such as 01 or 00.
Suffix numbers are updated as a product moves from release to release, as
well as for hardcopy updates within a given release.
Check to see if you are using the latest softcopy version. To do this, compare
the last two characters of the book's file name (also called the book name). The
higher the number, the more recent the book. For example, DGT1U302 is more
recent than DGT1U301.
Compare the dates of the hardcopy and softcopy versions of the books. Even if
the hardcopy and softcopy versions of the book have the same dash level, the
softcopy may be more current. This will not be apparent from looking at the
edition notice. The edition notice number and date remain that of the last
hardcopy version. When you are looking at the softcopy product bookshelf,
check the date shown to the right of the book title. This will be the date that the
softcopy version was created.
Also, an asterisk (*) is added next to the new and changed book titles in the
CD-ROM booklet and the README files.
Vertical lines to the left of the text indicate changes or additions to the text and
illustrations. For a book that has been updated in softcopy only, the vertical lines
indicate changes made since the last printed version.
Required Books
Familiarize yourself with the information presented in the following books:
DFSMS/MVS General Information (GC26-4900) introduces you to DFSMSdss
and helps in evaluating its use.
xi
DFSMS/MVS DFSMSdss Storage Administration Guide (SC26-4930) gives

guidance on how to use DFSMSdss.
DFSMS/MVS DFSMSdss Diagnosis Guide (LY27-9609) tells how to diagnose
errors you might encounter while using DFSMSdss.
DFSMS/MVS Planning for Installation (SC26-4919) describes the tasks required
to ensure a successful installation of DFSMSdss/ISMF.
DFSMS/MVS Installation Exits (SC26-4908) describes the installation user exits
available with DFSMS/MVS.
DFSMS/MVS Using ISMF (SC26-4911) describes how to use ISMF to manage
data sets and storage.
OS/390 MVS System Messages, Vol 1 (ABA-ASA) (GC28-1784) lists
DFSMSdss messages.
Related Books
The following books are associated with procedures described in this reference:
Other DFSMS/MVS Publications

Publication Title
DFSMS/MVS Access Method

Services for ICF

Access Method Services for the
Integrated Catalog Facility
SC26-4906
DFSMS/MVS Access Method

Services for VSAM

Access Method Services for VSAM
Catalogs
SC26-4905
DFSMS/MVS Macro
Instructions for Data Sets

Macro Instructions for Data Sets
SC26-4913
DFSMS/MVS Managing
Catalogs

Managing Catalogs
SC26-4914
DFSMS/MVS DFSMSdfp
Storage Administration
Reference

DFSMSdfp Storage Administration
Reference
SC26-4920
DFSMS/MVS DFSMShsm
Storage Administration Guide

DFSMShsm Storage Administration
Guide
SH21-1076
DFSMS/MVS DFSMShsm
Storage Administration
Reference

DFSMShsm Storage Administration
Reference
SH21-1075
DFSMS/MVS Utilities

Utilities
SC26-4926
The Storage Management Library
xii
Order
Number
Short Title
Order
Number
Short Title
Publication Title
DFSMS/MVS Implementing
System-Managed Storage

Implementing System-Managed
Storage
SC26-3123
MVS/ESA SML: Managing

Data
MVS/ESA Storage Management

Library: Managing Data
SC26-3124
Title
Order Number
OS/390 MVS Assembler

Services Guide
OS/390 MVS Programming: Assembler

Services Guide
GC28-1762
OS/390 MVS Assembler

Services Reference
OS/390 MVS Programming: Assembler

Services Reference
GC28-1910
OS/390 MVS JCL Reference
OS/390 MVS JCL Reference
GC28-1757
OS/390 MVS JCL User's

Guide
OS/390 MVS JCL User's Guide
GC28-1758
Short Title
Publication Title
Order
Number
OS/390 Security Server

(RACF) Introduction
OS/390 Security Server (RACF)

Introduction
GC28-1912
OS/390 Security Server

(RACF) Security
Administrator's Guide
OS/390 Security Server (RACF)

Security Administrator's Guide
SC28-1915
MVS/ESA
Other Related Publications
Preface
xiii
xiv
Summary of Changes
This summary of changes includes specific release updates to this book.
Publication Updates
|
|
|
Fifth Edition
The following new information has been added to the DFSMS/MVS Version 1
Release 5 edition:
|
|
Support for extended-format VSAM data sets, including data set COPY, logical
data set DUMP and RESTORE, and logical RELEASE support.
|
|
|
The STORGRP keyword allows filtering by storage group name, in addition to

filtering by volume serial numbers. STORGRP supports data set COPY, logical
data set DUMP, and logical RELEASE.
|
|
The addition of the INCAT, LOGDDNAME, LOGDYNAM, and SPHERE

keywords for logical RELEASE processing.
|
|
In addition, fresh examples of printed output are included, along with technical and
editorial updates.
Fourth Edition
The following information has been added to update the original DFSMS/MVS
Version 1 Release 4 edition in a subsequent, softcopyonly release:
The incorporation of SnapShot using DFSMS COPY and DUMP commands.
Snapshot support is added to Eioption 24 (Concurrent Copy Initialization
Complete) for new reason and return codes.
Additional requirements are provided for dumping and restoring HFS type data
sets when using the DFSMSdss Cross Memory Application Interface (XMAPI).
The following information was added with the original DFSMS/MVS Version 1
Release 4 edition:
The new Stand-Alone Services program replaces the existing Stand-Alone
restore function.
The BUILDSA command allows you to build an IPL-able core image for the
new Stand-Alone Services program.
The SELECTMULTI keyword replaces the ALLMULTI keyword for the
CONVERTV, COPY, and DUMP commands.
The FORCECP keyword allows checkpoint/restart data sets to be processed be
the CONVERTV, COPY, DUMP, DEFRAG, RELEASE, and RESTORE
commands.
The CPVOLUME keyword supports VM-format volumes with the COPY, DUMP,
and RESTORE commands.
In addition, fresh examples of printed output are included for DEFRAG and PRINT
operations, and for the DFSMSdss User Interaction Module (UIM).
xv
Support for the TRACKOVERFLOW keyword is removed for this release.
Third Edition
Information has been added to this DFSMS/MVS Version 1 Release 3 edition to
support:
The 7-digit (yyyyddd) date format, in addition to the existing 5-digit (yyddd)
format, for Year 2000.
Backup-while-open serialization for IMS data sets.
The optional VOLCOUNT keyword for data set RESTORE and data set COPY
of SMS data sets.
VSAM extended addressability, which provides additional addressability to data
in a VSAM key-sequenced data set.
VSAM record level sharing (RLS), which provides access to shared
SMS-managed VSAM data sets in a multisystem environment. User exits 22,
23, and 24 in Appendix C are updated.
A new section, Appendix E, Data Set Attributes , details how data set
attributes are affected by various components of the DFSMSdss environment.
Changes to the DFSMSdss UTILMSG parameter that allow more control over
which DFSMSdss utility messages are sent to the SYSPRINT output data sets.
IBM 3494 and 3495 tape libraries.
In addition, information for the existing DFSMSdss Stand-Alone restore function has
been consolidated into this book. Some of this information was formerly in
Appendix C in DFSMS/MVS DFSMSdss Storage Administration Guide.
xvi
Command Syntax
Chapter 1. Specifying DFSMSdss Commands

This section is divided into the following:
Command Syntax on page 1 describes syntax requirements.
How Many Subkeywords Are Allowed? on page 2 explains the allowable
number of subkeywords that you can specify in the input (command) stream.
Specifying Subkeywords in a Command Data Set on page 2 explains how to
use keywords in a command data set.
How to Read Syntax Diagrams on page 3 explains the syntax conventions
used in this book.
The JCL You Need on page 5 summarizes the job control language (JCL)
that you might need to use DFSMSdss.
Command Syntax
You can write DFSMSdss commands in free form in columns 2 through 72
(inclusive). Any character in column 1 or past column 72 is ignored, causing
unpredictable results when the task is processed. Syntax requirements are:
Commands: A command must appear first, followed by its keywords. Each
command must take up only one line, unless a continuation character is
used to indicate continuation of the command on the next line. A
command is separated from its keywords by one or more blanks, a
comment, or both. For example:
DUMP FULL INDD(DASD1) OUTDD(TAPE1)
or
DUMP FULL INDD(DASD1)
OUTDD(TAPE1)
Comments: A comment is a string of characters that begins with a /* and ends
with an */. For example:
/\THIS IS A COMMENT \/
A comment that does not begin and end on the same line must contain
a continuation character, or syntax errors will result. For example:
/\ THIS IS A MULTI
LINE COMMENT \/
Separators: A separator can be a comma (,), one or more blanks, or a comment.
Separators shown in the syntax diagrams in this manual are always
commas, but any of the three types can be used.
Keywords: Keywords are separated from one another by one or more separators.
Subkeywords: Subkeywords follow their associated keywords and are separated
from them by a pair of enclosing parentheses. One or more blanks can
precede and follow each parenthesis in the pair. For example:
REBLOCK( DATASET1 )
or
REBLOCK(DATASET1)
If two or more subkeywords are permissible for a single keyword, they

are separated from one another by one or more blanks or by commas.
Each comma can be preceded and followed by one or more blanks. For
example:
REBLOCK(DATASET1 , DATASET2)
or
REBLOCK(DATASET1,DATASET2)
or
REBLOCK(DATASET1 DATASET2)
Continuation: Continuation of a command is specified by a hyphen (-) as the
right-most nonblank character, preceded by one or more blanks. If a
continuation character is used, the following line is read as if it were part
of the previous line. Since only one command is allowed per line, no
additional commands may be included on the continued line. If no
continuation character is used, the first word on the following line must
be a command. For example:
COPY DATASET (INCLUDE(DATASET1)) ALLDATA(\) CATALOG REBLOCK(DATASET1)
For examples of the continuation usage, see Continuation Rules for
IF-THEN-ELSE Command Sequencing on page 181, using the
IF-THEN-ELSE command sequence.
The absence of such a hyphen indicates the end of the command. If a
keyword or subkeyword cannot fit on the remainder of a line, it can be
started on that line, followed immediately by a plus sign (+) in column
72, and continued on the next line.
End of a command: The end of a command can be specified by a semicolon (;).
Everything to the right of the semicolon is ignored.
How Many Subkeywords Are Allowed?

DFSMSdss allows most command keywords to have a maximum of 255
subkeywords specified within the inline command stream. Exceptions to this rule
are noted within individual command descriptions.
Specifying Subkeywords in a Command Data Set

Rather than specifying the data set names in the inline (command) stream, you can
instead specify the ddname of a sequential data set or a member of a partitioned
data set that contains the list of data set names. This allows you to specify more
than 255 data set names.
The following keywords allow this ddname specification:
DATASET
EXCLUDE
FILTERDD
PASSWORD
(FILTERDD(ddn))
(DDNAME(ddn))
(ddn)
(ddn)
Syntax Conventions
How to Read Syntax Diagrams

To read syntax diagrams, follow one line at a time from the beginning to the end,
and code everything you encounter on that line.
The following conventions apply to all syntax diagrams for DFSMSdss commands:
Read the syntax diagrams from left to right and top to bottom.
Each syntax diagram begins with a double arrowhead (55) and ends with
opposing arrows (5%).
An arrow (5) at the end of a line indicates that the syntax continues on the
next line. A continuation line begins with an arrow (5).
Commands and keywords are shown in uppercase and lowercase letters. The
uppercase portion is the minimum needed to code the command properly; the
lowercase portion is optional. For example, COPYDump can be coded in any of
the following ways: COPYD, COPYDU, COPYDUM, or COPYDUMP.
Note: Commands must be entered in uppercase. Lowercase is not
recognized.
Some commands and keywords have alternative abbreviations; these appear
as part of the stack for that command or keyword. For example, the alternative
abbreviation for COPYDump is CPYD.
55COPYDump5
CPYD
Words in all lowercase letters represent information you supply. For example,
volser or ddn.
You must provide all items enclosed in parentheses, ( ), and you must include
the parentheses.
Where you can choose from two or more keywords, the choices are stacked
one above the other. If one choice within the stack lies on the main path, you
must choose a keyword. In the following example you must choose either BLK,
TRK, or SOURCE.
5BLK5
TRK
SOURCE
If one or more keywords are below the main path, they are optional. In the
following example CATalog and RECATalog are optional keywords. You can
choose one, or the other, or none.
55
CATalog
RECATalog
If a stack of keywords are below the main path and one keyword is above the
main path, the use of the keyword is optional, and the above item is the
default. In the following example, if no keywords are specified, the default
TGTAlloc(SOURCE) is taken.
Syntax Conventions
TGTAlloc(SOURCE)
55
TGTAlloc(BLK)
CYL
TRK
SOURCE
SRC
The repeat symbol is shown below:

The repeat symbol appearing above keywords and variables indicates that you
can specify those keywords and variables more than once. If a comma appears
in the repeat symbol, you must separate repeated keywords or variables with a
comma or any valid separator.
For example, after the keyword BYPASSACS, you can enter multiple data set
names separated by commas.
,
6dsn)5
5BYPASSACS(
Substitution blocks are used to simplify the diagrams. They indicate that blocks
of the syntax diagram are located outside of the main diagram. You insert the
keywords for that block where the symbol appears, and return to the main
diagram to continue with the command.
In the following example the substitution block, A, points to a block of the
syntax diagram that immediately follows the FULL keyword.
55RESToreFULL5%
A
A: Optional Keywords Used with FULL:
55
CANcelerror COPYVolid
CPYV
The above example is equivalent to the following:
55RESToreFULL5%
CANcelerror COPYVolid
CPYV
JCL
The JCL You Need

The examples in this manual are shown with the necessary JCL. You may need the
following JCL to use DFSMSdss:
Statement
Usage
JOB (required)
Initiates your job.
EXEC (required)
Specifies the program name (PGM=ADRDSSU) or, if the

job control statements reside in a procedure library, the
procedure name. See How to Control DFSMSdss via
PARM Information in the EXEC Statement on page 7
for additional information that can be entered in the
PARM parameter of the EXEC statement.
STEPCAT DD (optional) or JOBCAT DD (optional)

Points to the user catalogs, that are searched prior to
the standard order of search. This DD statement is
required when either:
In a full or tracks operation a volume contains a
nonintegrated catalog facility VSAM data set that is
cataloged in a user catalog, or
Copying or logically dumping VSAM data sets whose
catalog is outside the standard order of search.
It is not required for other DFSMSdss operations.
STEPCAT or JOBCAT must not be specified if you are
processing SMS-managed data sets.
SYSPRINT DD (required)
Defines a sequential message data set. The data set
can be written to a system output device, a tape volume,
or a direct-access device. If the DCB keyword LRECL is
specified on the DD statement, it must be from 84 to 137
inclusive. If the BLKSIZE keyword is specified, it must be
at least four greater than LRECL. If LRECL is less than
84, the return code is 8, and an error message is issued.
If the specified LRECL is greater than 137, the LRECL
and BLKSIZE are set to 137 and 141, respectively.
Note: If the SYSPRINT DD or a temporary message
data set resides on a volume that is being
processed by DFSMSdss and a secondary
allocation is needed for it, the job may result in
an S138 abend. This is because the DADSM
EXTEND function attempts to enqueue on the
volumes VTOC while DFSMSdss holds the
enqueue on that VTOC. To avoid this situation,
define the SYSPRINT DD to another volume or
use the WORKUNIT or WORKVOL parameters,
or both.
SYSIN DD (required)
Defines a command data set containing your DFSMSdss

commands. It usually resides in the input stream.
However, it can be defined as a blocked or unblocked
JCL
sequential data set or as a member of a partitioned data

set. Records must be fixed format, LRECL=80.
input DD (optional)
Defines the input (also called the source). The ddname,

input, is supplied by you and is referred to by your
DFSMSdss commands. This DD statement is not
required for some operations. Do not specify the BUFNO
keyword.
The following example shows an input DD statement that
specifies a DASD volume:
//DASD DD UNIT=338,VOLUME=(PRIVATE,SER=111111),DISP=OLD
See the reference under the INDDNAME, INDYNAM,
DDNAME and DYNAM keywords of the various
commands (for example, COPY or DUMP) for additional
information.
output DD (optional)
Defines the output (also called the target). The ddname,

output, is supplied by you and is referred to by your
DFSMSdss commands. This DD statement is not
required for some DFSMSdss operations. Do not specify
the BUFNO keyword. Code a volume count when a new
data set will reside on six or more volumes.
Notes:
1. DISP=MOD is not supported for an output DD
statement.
2. For dump operations, the output DD statement
describes a sequential data set that DFSMSdss
dumps the data to. If this dump data set resides on a
DASD volume that is being processed by DFSMSdss
and a secondary allocation is needed for it, the job
may result in a S138 abend. This is because the
DADSM EXTEND function attempts to enqueue on
the volumes VTOC while DFSMSdss holds the
enqueue on that VTOC.
3. For dump operations, the output DD statement can
be directed to DUMMY.
4. If multiple dumps are done in the same step, each
dump command should have an output DD
statement that refers to a unique JCL DD statement.
5. The output data set must be a standard format
sequential data set and cannot use any
extended-format features, such as compression.
The following example shows an output DD statement
that specifies a tape volume:
//TAPE DD UNIT=348,VOLUME=SER=TAPE1,LABEL=(1,SL),
// DISP=(NEW,CATLG),DSNAME=USER2.DUMP
See the reference under the OUTDDNAME and
OUTDYNAM keywords of the various commands (for
example, COPY or DUMP) for additional information.
JCL
filter DD (optional)
Defines a data set consisting of cards or card-image

records that contains the filtering criteria (INCLUDE,
EXCLUDE, and BY) to be used in a data set command.
The ddname, filter, is supplied by you and is referred to
by your DFSMSdss commands.
password DD (optional)
Defines a data set consisting of card-image records that

contains data set names and their passwords. The
ddname, password, is supplied by you and is referred to
by your DFSMSdss commands.
For more information on coding JCL, refer to OS/390 MVS JCL Reference.
How to Control DFSMSdss via PARM Information in the EXEC

Statement
The EXEC statement for DFSMSdss can contain PARM information that is used by
the program. You can use the following keyword parameters:
ABEND=nnn
nnn is a 3-digit decimal message number (ADRnnnx). If this is specified and
this message is to be issued, DFSMSdss performs a user 0001 ABEND dump
after issuing the message, and the task stops. To get a dump, include a DD
statement for SYSABEND, SYSMDUMP, or SYSUDUMP. This keyword is
provided for diagnostic purposes only.
AMSGCNT=nnnn
The abend message occurrence count that tells DFSMSdss to end abnormally
on the nth occurrence of the message specified in ABEND=nnn. nnnn for
AMSGCNT can be a number between 1 and 9999. The default is 1 (first
occurrence). This keyword is provided for diagnostic purposes only.
LINECNT=nnnn
nnnn is a 1- to 4-digit number indicating the number of lines to be printed per
page for the SYSPRINT data set. The default is 60. Specify LINECNT=9999 to
prevent a page ejection.
PAGENO=nnnn
nnnn is a 1- to 4-digit number indicating the starting page number to be used
for the SYSPRINT data set. The default is 1.
SDUMP=nnn
nnn is a 3-digit decimal message number (ADRnnnx). If this is specified,
DFSMSdss requests an SVC dump after issuing the message, and the task
continues processing. The SVC dump is directed to a system defined data set
(SYS1.DUMPnn) for later analysis. This keyword is provided for diagnostic
purposes only.
SIZE=nnnnK
nnnn is a 1- to 4-digit number indicating the number of KB (1KB equals 1024
bytes) of main storage to be used by DFSMSdss. This amount must be less
than or equal to that specified by the REGION keyword. The default value is
the region size.
SMSGCNT=nnnn
The sdump message occurrence count that tells DFSMSdss to request an SVC
DUMP on the nth occurrence of the message specified in SDUMP=nnnn.
JCL
nnnn for SMSGCNT can be a number between 1 and 9999. The default is 1
(first occurrence). This keyword is provided for diagnostic purposes only.
TMPMSGDS=YES|NO
This parameter indicates whether or not a temporary SYSPRINT message data
set is to be allocated. When NO, SYSPRINT messages are buffered in an ESA
Hiperspace and performance is improved. The default is NO.
TRACE=YES
When used during a defragmentation operation, this prints messages that
indicate the relocated extents. This is a diagnostic tool.
TYPRUN=NORUN
For copy, dump, restore, compress, and release operations, only input data set
selection is done without actually processing data sets. Printed output for the
run indicates the data sets selected. For a defragmentation operation, the initial
volume statistics are printed without actually relocating any extents. For a
CONVERTV operation, a full report is produced, but no volumes or data sets
are actually converted.
TYPRUN=SCAN
Only control card syntax checking is done. No tasks are processed.
UTILMSG=YES|NO|ERROR
This parameter controls the output of messages from auxiliary programs
invoked by DFSMSdss (including ICKDSF, IDCAMS, IEBCOPY, IEBISAM, and
IEHMOVE) to the DFSMSdss SYSPRINT output. When YES, informational,
warning, and error messages from these auxiliary programs are copied to the
DFSMSdss SYSPRINT output. When NO, messages are not copied to the
output. When ERROR, messages are copied only if the auxiliary return program
returns an error code to DFSMSdss. The default is ERROR.
WORKUNIT=workunit
You can supply an esoteric DASD unit name (for example, SYSDA), a generic
DASD unit name (for example, 3380), or a specific DASD address. DFSMSdss
passes this unit to dynamic allocation when temporary data sets are allocated.
When WORKUNIT is specified by itself, the volumes to be processed by
DFSMSdss should not fall within the esoteric group passed as the WORKUNIT
name. If the esoteric name applies to the volumes to be processed by
DFSMSdss, specify WORKVOL.
WORKVOL=volser
You can supply a volume serial number on which DFSMSdss should allocate
temporary data sets. DFSMSdss passes the volume serial number to dynamic
allocation. The volume serial number passed as a WORKVOL should not be
the same as any volume being processed by DFSMSdss under the current
task.
Notes:
1. WORKUNIT, WORKVOL, or both parameters can be specified when
invoking DFSMSdss.
2. When DFSMSdss invokes the IDCAMS utility to copy an ICF user catalog,
the export data set is allocated as a permanent data set. The permanent
data set cannot be placed on the volume specified by WORKUNIT or
WORKVOL.
JCL
3. An esoteric unit name that requests virtual I/O can be used in the
WORKUNIT parameter, but when DFSMSdss invokes the IEHMOVE utility
during data set copy, the default dynamic allocation unit name is used
(SYSALLDA).
XABUFF=ABOVE16|BELOW16
The I/O buffers used by DFSMSdss for COPY, COPYDUMP, DEFRAG, DUMP,
PRINT, and RESTORE operations are to be above or below 16 megabytes
virtual storage. The default is ABOVE16.
Examples of PARM information are:
//
//
//
EXEC
PGM=ADRDSSU,
PARM='PAGENO=8,LINECNT=57,SIZE=5K,UTILMSG=YES'
EXEC
PGM=ADRDSSU,PARM='TYPRUN=SCAN,XABUFF=ABOVE16'
For further information on the PARM parameter of an EXEC statement, refer to

OS/390 MVS Extended Addressability Guide.
Examples of Invoking DFSMSdss with JCL

The following are some examples of JCL job streams for invoking DFSMSdss.
Note: Throughout the examples in this manual, a DASD is presented as
UNIT=3380 or UNIT=3390, and a tape device as UNIT=3480. This is only
for illustration; you can specify any supported DASD and any supported
tape device. Refer to the appropriate system generation manual for the
device-type notation to be used in the UNIT parameter of a DD statement.
Moving a Data Set

The following example shows how to move a data set from one DASD volume to
another using JCL and a DFSMSdss command. The source data set is deleted and
the target data set is cataloged to reflect its new location.
//MYJOB
JOB
accounting information,REGION=nnnnK
//STEP1
EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=A
//DASD1
DD
UNIT=338,VOL=(PRIVATE,SER=111111),DISP=OLD
//DASD2
DD
//SYSIN
DD
\
COPY DATASET(INCLUDE(MYDATSET)) LOGINDDNAME(DASD1) OUTDDNAME(DASD2) DELETE CATALOG
/\
Dumping a Data Set

Do not use a data set name that DFSMSdss will reference during execution.
Otherwise, enqueue contention with the operating system initiator will occur. This
example shows how to back up a DASD data set to tape:
JCL
//MYJOB
JOB
//STEP1
EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=A
//DASD
DD
//TAPE
DD
UNIT=348,VOL=SER=TAPE1,
// LABEL=(1,SL),DISP=(NEW,CATLG),DSNAME=MYDATSET.BACKUP
//SYSIN
DD
\
DUMP DATASET(INCLUDE(MYDATSET)) INDDNAME(DASD) OUTDDNAME(TAPE)
/\
Restoring a Data Set

Do not use a data set name that DFSMSdss will reference during execution.
Otherwise, enqueue contention with the operating system initiator will occur. In this
example, the data set (MYDATSET) that has been backed up on tape in the
Dumping a Data Set example is restored to the original DASD volume on which it
resided.
//MYJOB
JOB
//STEP1
EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=A
//TAPE
DD
// LABEL=(1,SL),DISP=(OLD,KEEP),DSNAME=MYDATSET.BACKUP
//DASD
DD
//SYSIN
DD
\
RESTORE DATASET(INCLUDE(MYDATSET)) INDDNAME(TAPE) OUTDDNAME(DASD) REPLACE
/\
10
Filtering
Chapter 2. FilteringChoosing the Data Sets You Want

Processed
This chapter is divided into the following sections:
How DFSMSdss Filters Data Sets describes how DFSMSdss filters data sets
by data set name and by data set characteristic.
Filtering by Data Set Names on page 12 explains how to specify fully and
partially qualified data set names for filtering. This section includes rules for
spelling out qualifiers and examples of qualified data set names.
Filtering by Data Set Characteristics on page 14 lists the data set
characteristics on which filtering can be done.
Standard Catalog Search Order on page 19 identifies the standard order in
which DFSMSdss searches for a data set name.
For information about how DFSMSdss determines individual data set attributes, see
Appendix E, Data Set Attributes on page 307.
How DFSMSdss Filters Data Sets

DFSMSdss filters data sets by:
Applying inclusion and exclusion criteria to fully or partially qualified data set
names.
If you specify inclusion (INCLUDE) criteria, DFSMSdss tentatively selects
all data sets that fit any of the criteria.
Note: If you do not specify inclusion criteria, you must specify EXCLUDE
or BY. In this case, DFSMSdss tentatively selects all data sets
(equivalent to INCLUDE(**)). For the DEFRAG command,
INCLUDE(**) is always implied.
If you specify exclusion (EXCLUDE) criteria, DFSMSdss surveys the data
sets selected with the inclusion criteria and rejects the data sets that fit any
of the new criteria.
Applying data set characteristics (BY) criteria to the data sets tentatively
selected with the inclusion and exclusion criteria. DFSMSdss selects only those
data sets that satisfy all BY criteria.
DFSMSdss lets you find out which data sets are selected by the filtering process
without actually performing the requested operations. You can do this by specifying
TYPRUN=NORUN on the JCL EXEC PARM field.
Considerations for VSAM Data Sets:

INCLUDE and EXCLUDE filtering is performed on the cluster names of the data
sets.
If you specify the BY criterion DSORG, MULTI, CATLG, or FSIZE, filtering is
done at the cluster level. One exception is the DEFRAG command, that filters
at the VSAM component level. If you specify other BY criteria, the data
components of the selected clusters are further filtered on those BY criteria by
using information from the VTOC. If a data component is selected, the index
11
Filtering by Data Set Names
component for the cluster is also selected. Again, the one exception is the
DEFRAG command, that requires index components to pass all BY criteria.
DFSMSdss supports the BY criterion EXPDT as it exists in the VTOC only.
For a physical data set RESTORE, to prevent index components from being
restored inadvertently, you must specify the fully qualified name of the cluster.
For data set print operation, the fully qualified name of the data set to be
printed is required. Support is at the component, not the cluster, level.

A fully qualified data set name is one in which all qualifiers are completely spelled
out. A partially qualified data set name is one in which asterisks (\) or percent signs
(%) are used to represent qualifiers or parts of qualifiers.
Using an * in Partially Qualified Data Set Names

The single asterisk, \, is used in place of exactly one qualifier. In addition, it can
be used to indicate to DFSMSdss that only part of a qualifier has been specified.
For example, just the first, last, middle, or first and last parts.
When used with other qualifiers, the double asterisk, \\, indicates either the
nonexistence of leading, trailing, or middle qualifiers, or the fact that they play no
role in the selection process.
The rules for using asterisks in a qualifier are:
Two asterisks are the maximum permissible in a qualifier.
If there are two asterisks in a qualifier, they must be the first and last
characters.
Consequently, the following are permissible qualifiers:
\\
\A\
The following are not permissible qualifiers:
\\A\
\A\B\
\A\B
A\B\C
Using a % in Partially Qualified Data Set Names

The % acts as a place holder for a single character during data set name filtering.
The rules for using % in a qualifier are:
Each % corresponds to exactly one character.
% can be specified more than once, consecutively or in any level of the qualifier.
A % cannot match a null ('') or a period ('.').
Use of a % in filtering does not change any of the other filtering specifications
for data set names.
12
Consequently, specifying
I%M.A.%AT%%ET
matches the data set names
IAM.A.DATASET
IBM.A.BATTYET
but not
IAM.A.DATASE
IAM.AA.DATASET
IAM.A.ATASET
IM.A.DATASET
Examples of Fully and Partially Qualified Data Set Names

The following are examples of fully and partially qualified data set names.
Fully-Qualified Data Set Names:

USER2LD
The first and only qualifier is USER2LD.
SYS1.UTIL3.LOAD
The first qualifier is SYS1, the second, UTIL3, and the third,
LOAD.
USER2.PROGRAM1.LIST The first qualifier is USER2, the second, PROGRAM1, and

the third, LIST.
Partially Qualified Data Set Names Using **:

\\.LOAD
All data sets whose last, or only, qualifier is LOAD.
SYS1.\\
All data sets whose first, or only, qualifier is SYS1.
USER2.\\.LIST
All data sets whose first and last qualifiers are USER2 and
LIST, respectively, including USER2.LIST.
More Partially Qualified Data Set Names:

\.LOAD
All data sets with two qualifiers whose last qualifier is LOAD.
SYS1.\
All data sets with two qualifiers whose first qualifier is SYS1.
SYS1.\.LOAD
All data sets with three qualifiers whose first and last
qualifiers are SYS1 and LOAD, respectively.
SYS1.UT\.LIST
All data sets with three qualifiers whose first and last
qualifiers are SYS1 and LIST, respectively, and whose
second qualifier begins with UT.
\\.\LIB
All data sets whose last, or only, qualifier ends with LIB.
\\.\LIB\
All data sets whose last, or only, qualifier has LIB in it.
\.\PLI\.\
All data sets with three qualifiers whose second qualifier has
PLI in it.
\.\.P\M
All data sets with three qualifiers whose last qualifier begins
with P and ends with M.
\\
All data sets.
%.LIST
All data sets with one character in the first qualifier and LIST
in the last qualifier.
13
Filtering by Data Set Characteristics
USER%.\
All data sets with two qualifiers whose first qualifier is USER
followed by some other character.
\%%\
All data sets whose single qualifier consists of two or more

characters.
Note: Single quotation marks around a data set name indicates the name is fully
qualified. For example, specifying USER.% selects a data set whose first
qualifier is USER and whose second qualifier is the character %. This data
set is selected using the filter USER.\ because the wildcard (*) matches the
character %.
Relative Generation Filtering

DFSMSdss allows filtering on relative generations of a generation data group
(GDG) data set in the INCLUDE, EXCLUDE, and REBLOCK data set name lists. A
GDG is specified as dsn(n) where dsn is a fully or partially qualified base name
without the last qualifier (GggggVvv), and n is the relative generation number or *
for all generations.
The following are examples of relative generation filtering:
dsn(0)
For the current generation
dsn(x)
For the xth prior generation
dsn(+x)
For the xth future generation
dsn(*)
For all generations.
For logical operations using catalog filtering, you must use either the fully qualified
data set name, the partially qualified base name with the last qualifier (GggggVvv)
not specified (for example, USER1.GDG.*), or the above relative generation
filtering. Partial qualification of the last qualifier (GggggVvv) is not supported unless
a wildcard (* or %) is specified in the first character of the qualifier. For example,
USER1.GDG.*V01 is valid but USER1.GDG.G%%10* is not.
Note: Relative generation filtering is not applicable when using the CONVERTV,
COPYDUMP, or PRINT functions. These functions do not allow filtering of
any kind.

After DFSMSdss has tentatively selected data sets by applying INCLUDE and
EXCLUDE criteria, you can apply BY criteria to further restrict the data sets finally
chosen. You can, for example, use BY to select data sets by creation date, storage
class, and a wide variety of other criteria. The BY keyword takes this form:
,
6
5BY((schar,op,(6arg)))5
14
Where
Represents
schar
The selection characteristics:

Keyword
Criteria
ALLOC
Allocation type (cylinder, track, block, absolute track,

or movable)
op
arg
CATLG
Whether the data set is currently cataloged or not

(using the standard catalog search order)
CREDT
Creation date (absolute or relative)
DSCHA
Whether the data-set-changed flag is on or off
DSORG
Data set organization (SAM, PAM, PDS, PDSE,

BDAM, HFS, EXCP, ISAM, or VSAM)
EXPDT
Expiration date (absolute or relative)
EXTNT
Number of allocated or used extents for the entire data

set on all the volumes on which it resides
FSIZE
Number of allocated or used tracks for the entire data

set on all the volumes on which it resides (data set
size)
MULTI
Whether the data set is single- or multivolume
REFDT
Last-referenced date (absolute or relative)
DATACLAS
Data class for SMS
MGMTCLAS
Management class for SMS
STORCLAS
Storage class for SMS
The operator:
Operator
Meaning
EQ or =
Equal to
LE or <=
Less than or equal to
LT or <
Less than
GT or >
Greater than
GE or >=
Greater than or equal to
NE or =
Not equal to
An argument that qualifies the selection characteristic (schar).
Table 1 on page 16 summarizes the permissible combinations of schar, op, and

arg.
Data sets without expiration dates explicitly assigned to them are considered to have an expiration date of zero. If you wish to
exclude these data sets from expiration date processing, you must specifically exclude them in your filtering list, that is, BY
EXPDT NE 0000000.
Single volume data sets that have been allocated but have never been opened and are not cataloged may be selected as
multivolume.
15
Table 1 (Page 1 of 3). BY Keywords

schar
op
arg
Notes
ALLOC
EQ
NE
CYL (cylinder
allocation)TRK (track
allocation)
BLK (block length
allocation)
ABSTR (absolute track
allocation)
MOV (movable data sets)
If MOV is picked, the data sets to be processed cannot be allocated as

any of the following:
PSU (physical sequential unmovable)

POU (partitioned organization unmovable)
DAU (BDAM unmovable)
ABSTR (absolute tracks)
ISAM (indexed sequential access method).
COMPRESS command: If MOV is picked, only data sets allocated as

POU cannot be compressed.
CATLG
EQ
|
|
|
|
|
YES (or 1)
NO (or 0)
YES: Only currently cataloged data sets are processed. NO: Only
uncataloged data sets are processed. DUMP command: The CATLG
filter is valid only when used with an input volume list (INDD, INDY,
LOGINDD, LOGINDY, STORGRP). COPY command: The CATLG
filter is valid only when used with an input volume list (INDD, INDY,
LOGINDD, LOGINDY, STORGRP). RESTORE command: The target
data set is tested to determine if it is cataloged or not.
Notes:
1. Data sets cataloged via JCL are not cataloged until the job step
ends. Therefore, when you use the (CATLG,EQ,NO) filter, you
should also use a CREDT or REFDT filter. The value used in the
CREDT or REFDT filter should be for data sets at least two days
old: (CREDT,LE,*,-2) or (REFDT,LE,*,-2).
2. A data set is considered uncataloged if it is not cataloged in the
standard order of search or if it is cataloged in an unavailable
catalog.
CREDT
EXPDT
REFDT
LT
GT
EQ
NE
GE
LE
[yy]yyddd(,n): 4-digit (or 2-digit)

year and 3-digit day, modified
by an optional 1-digit to 4-digit
positive or negative number of
days, n. The year values range
from 1900 through 9999. For
example, 1998100 (or 98100) is
the 100th day of 1998 and
2000001 (or 00001) is the first
day of 2000.
*(,n): Current date (run date),
modified by an optional 1-digit
to 4-digit positive or negative
number of days, n. For
example, *,-5 is five days
before this job is run.
NEVER: Never-expire date
(valid only for EXPDT). A
never-expire data set has an
expiration date in its VTOC
entry of 99365, 99366, or
99999.
DSCHA
16
EQ
NE
YES (or 1)
NO (or 0)
The preferred form of a date has a 4-digit year (yyyyddd). When you
specify a date with a 4-digit year other than a date of all zeros, the
smallest valid date before modification is 1900001. When you specify a
date with the 2-digit year format (yyddd), a yy of 00 through 49
indicates years 2000 through 2049; a yy of 50 through 99 indicates
years 1950 through 1999. You must use the 4-digit year format if you
wish to filter on years 1900 through 1949 or on years higher than 2049.
CREDT and EXPDT: For a multivolume data set, the date from its first
volumes VTOC is used for checking.
EXPDT: When you specify a date of 99365 or 1999365, you are
specifying the last day of 1999. When you specify EXPDT with NEVER,
99366, 1999366, 99999, 1999999, or 9999999, you ask DFSMSdss to
look for all valid forms of never-expire dates (including 99365 in a data
sets VTOC entry). Therefore, BY(EXPDT,EQ,1999365) selects no
data sets. DFSMSdss considers the valid forms of never-expire dates
as equal to each other and as greater than all other dates. A
never-expire date cannot be modified and cannot be specified with the
GT operator.
REFDT: For a multivolume data set, the latest date from all its VTOCs
is used for checking. RELEASE and DEFRAG commands: The date
in the VTOC of the volume being processed is used for filtering both
single- and multivolume data sets.
For a multivolume data set, the value used for checking is 1 if any of
the indicators from all of its VTOCs is 1. Otherwise, the value is 0.

schar
op
arg
Notes
DSORG
EQ
NE
SAM (all sequential data sets,

including compressed and
striped), PAM (partitioned data
sets, including PDS and
PDSE), PDS, PDSE, HFS
(hierarchical file system data
sets), BDAM (all direct access
data sets), ISAM (all indexed
sequential data sets), VSAM
(includes all VSAM data set
types), EXCP (applies to data
sets not allocated as any of the
listed organizations and not
accessed by using any of the
listed access methods)
COMPRESS command: Because DFSMSdss assumes data set

organization, you do not need to specify it.
YES (or 1)
NO (or 0)
YES: DFSMSdss processes only multivolume data sets. NO:

DFSMSdss processes only single-volume data sets. DEFRAG
command: If a data sets volume sequence number is greater than
one in the VTOC, DFSMSdss assumes it is multivolume. If this
sequence number is 1, DFSMSdss assumes it is a single-volume data
set. COMPRESS command: Because DFSMSdss assumes the data
set is single-volume, you do not need to specify MULTI.
MULTI
EQ
Note: The selective characteristic of DSORG can be specified more

than once.
Note: Single volume data sets that have been allocated but have
never been opened and are not cataloged may be selected as
multivolume.
DATACLAS EQ
MGMTCLAS NE
STORCLAS
An appropriate SMS class

name.
17

schar
op
arg
Notes
EXTNT
FSIZE
LT
GT
EQ
NE
GE
LE
nnnnn (1- to 5-digit number,

from 0 to 99999)
nnnnn is the number of used or allocated extents (EXTNT) or used or

allocated tracks (FSIZE). RESTORE command: The data set that was
dumped determines the number of used or allocated extents or tracks.
DUMP and COPY commands:
For non-VSAM data sets:
If ALLDATA or ALLEXCP is specified, FSIZE is equal to the
allocated tracks, and EXTNT is equal to the allocated extents.
If ALLDATA or ALLEXCP is not specified, FSIZE is equal to
the used tracks, and EXTNT is equal to the used extents.
Note: A specification of FSIZE,EQ,0 can be used to select
PDSE data sets that have no members (that is, have
no used directory blocks), and a specification of
FSIZE,NE,0 can be used to exclude PDSE data sets
that have no members.
For VSAM data sets, FSIZE is always equal to the allocated tracks,
and EXTNT is always equal to the allocated extents.
Logical data set COPY, DUMP, and RESTORE commands:
FSIZE criteria are applied once for the entire data set on all
volumes that the data set resides on. For logical dump of HFS
files with TYPRUN NORUN, FSIZE equals all of the allocated
space. For logical dump of HFS files without TYPRUN NORUN, the
used space represents the FSIZE unless ALLDATA was specified.
EXTNT criteria are applied to non-VSAM data sets once for the
data set on all volumes that the data set resides on.
EXTNT criteria are applied to each VSAM data component on all
volumes that the VSAM data component resides on. If a VSAM
data component is selected by EXTNT filtering, the index
component for the cluster is automatically selected.
|
|
|
|
Physical data set DUMP and RESTORE commands:
|
|
|
FSIZE criteria are applied once for each volume being processed
of a non-VSAM or VSAM data set. For HFS data sets, FSIZE
equates to the allocated space, not the space actually used.
EXTNT criteria are applied once for each volume being processed
of a non-VSAM data set or VSAM data component. If a VSAM data
component residing on a volume is selected by EXTNT filtering, the
index component (if any) residing on the same volume for the
cluster is automatically selected.
FSIZE and EXTNT can be used to select certain volumes of a
multivolume data set without selecting all of the volumes that the
data set resides on.
DEFRAG commands:
For VSAM data sets, EXTNT and FSIZE criteria are applied at the
VSAM component level for the volume being processed only.
EXTNT and FSIZE filtering are performed for both VSAM data and
index components; VSAM index components are not automatically
selected if the data component for the cluster is selected.
For non-VSAM data sets, EXTNT and FSIZE criteria are applied for
the volume being processed only. For HFS data sets, FSIZE
equates to the allocated space, not the space actually used.
|
|
|
Notes:
1. When multiple arguments are specified for an NE operation, DFSMSdss selects only those data sets not matching any of
the arguments.
2. When multiple arguments are specified for an EQ operation, DFSMSdss selects those data sets matching any of the
arguments.
3. BY criteria do not apply for the CONVERTV or COPYDUMP commands.
18
Catalog Search Order
Some Examples of the BY Keywords

If you code
BY((ALLOC EQ CYL) (CATLG EQ YES))
you receive all cataloged data sets with cylinder allocation.
If you code
BY(FSIZE GE 1)
you receive all data sets whose size is greater than or equal to 100 tracks.
If you code
BY(DSORG EQ (PAM,SAM))
DFSMSdss selects all partitioned and sequential data sets.
Standard Catalog Search Order

For a complete description of the standard catalog search order, refer to the
DFSMS/MVS Access Method Services for ICF.
When catalogs are searched for a data set name, the standard order of the search
is:
1. DFSMSdss first searches the catalogs specified with INCAT, if any. If INCAT
and ONLYINCAT are specified, the following steps are skipped.
2. DFSMSdss searches the user catalogs specified in the current job step
(STEPCAT), or if none is specified for the job step, the user catalogs specified
for the current job (JOBCAT). If more than one catalog is specified for the job
step or job, the catalogs are searched in order of concatenation.
Note: If data sets with the same name are cataloged in more than one catalog
within the standard search order, DFSMSdss selects only the first one
encountered. Also, STEPCAT and JOBCAT can be used only in a
non-SMS-managed environment.
3. If the data set name is a qualified name and is the name of a user catalog, or
the data set name is the same as the alias of a user catalog or the alias of a
CVOL, DFSMSdss searches that user catalog or CVOL.
4. DFSMSdss searches the master catalog.
19
Catalog Search Order
20
SyntaxFunction Commands
Chapter 3. SyntaxFunction Commands

This chapter describes function commands. Function commands specify tasks,
which are operations to be performed. These commands are:
BUILDSA
COMPRESS
CONVERTV
COPY
COPYDUMP
DEFRAG
DUMP
PRINT
RELEASE
RESTORE
The DFSMS/MVS DFSMSdss Storage Administration Guide contains usage notes,

including DFSMSdss restrictions. Refer to these notes as needed.
What DFSMSdss Commands Can Do

|
|
There are several functions that DFSMSdss commands can perform. A feature of
the DFSMS COPY and DUMP commands is the incorporation of Snapshot support.
Building the Stand-Alone IPL-able Core Image

The DFSMSdss BUILDSA command allows you to build the Stand-Alone Services
IPL-able core image. The core image is the executable module that is loaded into
the processors storage during the IPL process.
Backup and Recovery (Dump, Restore)

You can use DFSMSdss to back up your data in case of hardware failure or user
error. You can also use DFSMSdss to back up data on DASD and to restore the
backup if the original is lost, damaged, or changed inadvertently. In addition to
meeting routine backup requirements, DFSMSdss can be used to back up
application data for disaster recovery and vital records purposes.
You can use DFSMSdss to back up and recover data sets, entire volumes, or
specific tracks. The DFSMSdss DUMP command is used to back up tracks,
volumes, and data sets. The RESTORE command is used to recover them.
|
|
|
|
|
|
|
Data Movement (COPY)

You must move data to replace storage devices, add storage capacity, and meet
storage requirements. DFSMSdss lets you:
Move
Move
Move
Move
data sets from old to new direct-access storage devices (DASD).

data sets between SMS- and non-SMS-managed volumes.
data sets off a volume when hardware maintenance is required.
or copy data sets for other purposes.
21
SyntaxFunction Commands
|
|
You can move data sets from one DASD volume to another volume of like or unlike
device type.3
|
|
|
|
|
However, if you copy a full volume or ranges of tracks, the DASD must be of like
device type. The user must specify both the source and target volumes. Only one
source volume and one target volume are allowed. See "COPY Command" in this
section. The DFSMSdss COPY command is used to perform data set, volume, and
track movement.
Conversion to and from Storage Management Subsystem (CONVERTV)

Storage Management Subsystem (SMS) allows you to match the needs of users
data (like data set organization, size, and format) to the characteristics of storage
devices without requiring users to know or understand your installations hardware
configuration. With SMS, users can store and retrieve data without being aware of
space limitations, device characteristics, or volume serial numbers.
The DFSMSdss CONVERTV command is used to convert existing volumes to and
from SMS management without data movement.
Space Management (COMPRESS, DEFRAG, RELEASE)

DFSMSdss provides features to consolidate free space on volumes, compress
partitioned data sets, and release unused space in data sets.
The DFSMSdss DEFRAG command is used to consolidate the free space on a
volume to help prevent out-of-space abends on new allocations. The DFSMSdss
COMPRESS command is used to compress partitioned data sets by taking unused
space and consolidating it at the end of the data set. The DFSMSdss RELEASE
command is used to release unused space in sequential and partitioned data sets
for use by other data sets.
Conversion from a PDS to a PDSE and from a PDSE to a PDS (COPY)

The DFSMSdss data set COPY command can be used to move or copy a PDS
and convert it to a PDSE, or vice versa.
Copying DFSMSdss-Produced Dump Data (COPYDUMP)

The DFSMSdss COPYDUMP command lets you make up to 255 copies of
DFSMSdss-produced dump data.
Printing for Diagnostic Purposes (PRINT)

You can print DASD data to SYSPRINT or to a sequential data set in print format.
For data set printing, tracks are printed in logical sequence of the data set on the
volume, not in the physical cylinder and head sequence.
The DFSMSdss PRINT command is used to print a single-volume non-VSAM data
set, a single-volume VSAM data set component, all or part of the VTOC, or ranges
of tracks.
|
|
|
Like devices have the same track capacity and number of tracks per cylinder (for example, 3380 Model D, Model E, and Model K
DASD). Unlike DASD devices have different track capacities (for example, 3380, 3390, and RVA) or a different number of tracks
per cylinder, or both.
22
BUILDSA Command
BUILDSA Command
Use the BUILDSA command to build the IPL-able core image for the Stand-Alone
Services program. With the BUILDSA command you can specify the device (card
reader, tape drive, or DASD volume) from which Stand-Alone Services will be
IPLed. You can also specify the operator console to be used for Stand-Alone
Services.
The BUILDSA function allocates temporary data sets if needed for BUILDSA
processing. These data sets are deleted when the BUILDSA operation is complete.
System-generated, temporary data set names are used.
The BUILDSA function invokes the linkage editor (or Binder) utility. Specify
UTILMSG=YES whenyou run the BUILDSA function, and keep the output as a
debugging reference when you run the Stand-Alone Services program.
The BUILDSA function builds the IPL-able core image under the current operating
system, and determines a record size based on whether the IPL is from card, tape,
or DASD.
Notes:
1. The Stand-Alone Services modules reside in target library SYS1.SADRYLIB
after they are installed and accepted by System Modification Program (SMP) or
System Modification Program Extended (SMP/E). If you name this data set
something other than SYS1.SADRYLIB, then substitute that name for
SYS1.SADRYLIB in the examples shown later in this section.
2. Stand-Alone Services does not support the creation of the core image from an
SMS-managed volume.
3. To ensure that Stand-Alone Services is available when you run from DASD, do
not delete the SYS1.ADR.SAIPLD.Vvolser data set or move it to another
volume.
4. If you IPL from DASD and later change the volume serial number, you must
rerun the BUILDSA function to create a new core image data set with the new
volume serial number in the name.
5. Consider creating a password or providing other security protection for the
SYS1.ADR.SAIPLD.Vvolser data set and for the Stand-Alone Services
modules.
6. Specifying TYPRUN=NORUN with the EXEC statement causes the BUILDSA
task to end without processing input or output.
BUILDSA Syntax
55BUILDSAINDDNAME(ddname1)OUTDDNAME(ddname2)ADMINISTRATOR5
(volser)
OUTDYNAM
55%
CARD
OPERCNSL(ccuu)
IPL(TAPE)
(SERV)
DASD
23
BUILDSA Command
Explanation of BUILDSA Command Keywords

This section describes the keywords for the BUILDSA command.
ADMINistrator
55
ADMINistrator
ADMINISTRATOR specifies that you are a DFDSS-authorized or

DFSMSdss-authorized administrator for the BUILDSA command. If you are not
authorized to use the ADMINISTRATOR parameter, the command is ended with an
error message. If you are authorized, and you have access authorization to the
output data set, you may create an IPL-able core image for the DASD volume. The
ADMINISTRATOR parameter does not give you access to the input data sets, or to
the output data sets for IPL(TAPE) or IPL(CARD).
To use the ADMINISTRATOR parameter, all of the following must be true:
FACILITY class is active.
Applicable FACILITY-class profile is defined.
You have READ access to that profile.
For more details, seeUnderstanding BUILDSA Command Authorization Levels on
page 202 .
INDDname
5INDDname(ddname1)5
INDDNAME specifies the DD card in the JCL that identifies the partitioned data set
containing the information needed to build the STAND-ALONE Services core
image. This is the target library (SYS1.SADRYLIB) where the Stand-Alone Services
modules are placed after the SMP or SMP/E install is complete.
ddname1 specifies the name of the DD statement that identifies a volume whose
partitioned data set contains the input information.
IPL
55
CARD
IPL(TAPE)
DASD
IPL specifies the type of device from which Stand-Alone Services will be IPLed.
The appropriate loader is then created for the specified device type. If the IPL
parameter is not specified, then the core image is created to IPL from a card
reader.
CARD specifies that the core image be created for IPLing from a card reader.
When IPL(CARD) is specified, the OUTDDNAME parameter must also be specified.
The core image is created with BLKSIZE=80 and LRECL=80, and is placed into the
data set specified by the OUTDD parameter. This core image can be used to IPL
from a card reader or tape drive. Create the output data set with DSORG=PS,
RECFM=F, BLKSIZE=80 and LRECL=80.
24
BUILDSA Command
TAPE specifies that the core image be created in order to IPL from a tape drive.
This core image can only be used to IPL from a tape drive. The tape is created
with a blocksize determined to be the best for IPL of the Stand-Alone Services
program from tape, and IBM therefore recommends that you specify TAPE when
IPLing from a tape drive. Create the output data set with DSORG=PS, RECFM=U,
BLKSIZE=32760, and LRECL=32760. When IPL(TAPE) is specified, the
OUTDDNAME parameter must also be specified.
DASD specifies that the core image be created for IPLing from a DASD volume.
When IPL(DASD) is specified, the OUTDYNAM parameter must also be specified.
The volume specified by the OUTDYNAM parameter is the volume from which the
Stand-Alone Services program will be IPLed. The core image is created with a
record size determined to be the best for IPL of the Stand-Alone Services program
from DASD. It is then placed in data set SYS1.ADR.SAIPLD.Vvolser that is
allocated by Stand-Alone Services on the volume specified in the OUTDYNAM
parameter.
Additionally, the BUILDSA command invokes the ICKDSF REFORMAT command
to place the IPLTEXT and bootstrap records on this volume. The BUILDSA
command provides ICKDSF with IPLTEXT necessary to IPL the Stand-Alone
Services core image.
This core image can only be used to IPL from the DASD volume specified in the
OUTDYNAM parameter. Only the DASD IPL devices listed in Supported Devices
on page 203 are supported with the IPL(DASD) parameter.
Note: Stand-Alone Services does not support the creation of the core image from
an SMS-managed volume.
OPERCNSL
5(ccuu)5
OPERCNSL
(SERV)
OPERCNSL specifies the device address to be used as the operator console when
running Stand-Alone Services.
ccuu specifies that Stand-Alone Services attempt to use the device address as the
operator console instead of using the device that generates the first interrupt.
Specify a valid device that exists in the configuration where the Stand-Alone
Services program will be executed. You can specify a 3 digit or 4 digit address.
SERV specifies that the ES/9000 service console be used as the Stand-Alone
Services operator console instead of a unit address.
When OPERCNSL is not specified, Stand-Alone Services loads a wait-state, and
then waits for the operator console to generate an interrupt. Limited verification of
this parameter is performed during processing of the BUILDSA command. For more
information about the predefined console, see Running Stand-Alone Services with
a Predefined Console on page 187
25
BUILDSA Command
OUTDDname
5OUTDDname(ddname2)5
OUTDDNAME specifies the output location for the IPL-able core image.
ddname2 specifies the DD card in the JCL where the IPL-able core image is
placed when IPL(TAPE) or IPL(CARD) is specified.
See Supported Devices on page 203 for specific IPL devices.
When IPL(TAPE) is specified, it becomes the physical sequential data set where
the core image (including bootstrap) is placed to IPL from a tape drive.
When IPL(CARD) is specified, it becomes the physical sequential data set where
the core image (including bootstrap) is placed to IPL from a card reader. If this is a
DASD data set, you can then punch it to cards or use it in a VM virtual card reader
for IPL.
Specify either OUTDDNAME or OUTDYNAM, not both. When OUTDDNAME is
specified, IPL(CARD) is the default. You can specify the IPL(CARD) parameter or
the IPL(TAPE) parameter.
OUTDYnam
5OUTDYnam(volser)5
OUTDYNAM specifies the output volume serial number for the DASD volume
where the IPL-able core image is placed when IPL(DASD) is specified.
volser specifies the name of the DASD volume from which the Stand-Alone
Services program will be IPLed.
See Supported Devices on page 203 for specific IPL devices.
The IPL bootstrap and IPLTEXT (needed to read in the core image) are placed on
this volume. Additionally, Stand-Alone Services allocates data set
SYS1.ADR.SAIPLD.Vvolser on this volume and places the core image into this data
set. If the SYS1.ADR.SAIPLD.Vvolser data set already exists, StandAlone
Services deletes and reallocates it.
Specify either OUTDDNAME or OUTDYNAM, not both. When OUTDYNAM is
specified, IPL(DASD) must also be specified.
BUILDSA Command Examples

Example 1: Core Image Using the Default Parameters
In this example, the IPL parameter is not specified, so the default (CARD) is used.
Stand-Alone Services is created with BLKSIZE=80, LRECL=80, a bootstrap, and is
placed in a data set on volume 339001. This core image can be used to IPL from a
tape or a card reader. You can either punch the Stand-Alone Services program to a
card reader or use IEBGENER to copy the Stand-Alone Services program to tape.
The OPERCNSL parameter is not specified; after Stand-Alone Services is IPLed, it
26
BUILDSA Command
loads a wait-state and then waits for the first interrupt to define the operator
console.
Note: The DCB parameters must be coded as shown.
//BUILDSA JOB accounting information,REGION= nnnnK

//STEP1
EXEC PGM=ADRDSSU,PARM='UTILMSG=YES'
//SAMODS
DD DSN=SYS1.SADRYLIB,DISP=SHR
//CARDDD
DD DSN=ADRSA.IPLC,UNIT=339,
//
DISP=(NEW,KEEP),VOL=SER=3391,
//
SPACE=(TRK,(4,5)),
//
DCB=(DSORG=PS,RECFM=F,BLKSIZE=8,LRECL=8)
//SYSPRINT DD SYSOUT=A
//SYSIN
DD \
BUILDSA INDD(SAMODS) OUTDD(CARDDD)
/\
The following example copies the Stand-Alone Services core image (created in
Example 1) to tape.
//COPYSA
//STEP1
//SYSPRINT
//SYSUT1
//
//SYSUT2
//
//
//SYSIN
/\
JOB
EXEC
DD
DD
DD
DD
accounting information
PGM=IEBGENER
SYSOUT=A
DSN=ADRSA.IPLC,DISP=SHR,VOL=SER=3391,UNIT=339,
DCB=(RECFM=F,BLKSIZE=8,LRECL=8)
DSN=DSSSA,DISP=(,KEEP),VOL=SER=T112,LABEL=(,NL),
DCB=(RECFM=F,BLKSIZE=8,LRECL=8),
UNIT=348
DUMMY
Example 2: Core Image for IPL from Tape

In this example, Stand-Alone Services is created for IPLing in stand-alone mode
from a tape. The core image is then placed on an unlabeled tape. The OPERCNSL
option is not specified; after Stand-Alone Services is IPLed, it loads a wait-state
and then waits for the first interrupt to define the operator console.
27
BUILDSA Command

//STEP1
//SAMODS
//TAPEDD
DD DSN=ADRSA.IPLT,UNIT=348,LABEL=(,NL),
//
DISP=(NEW,KEEP),VOL=SER=TAPE1,
//
DCB=(DSORG=PS,RECFM=U,BLKSIZE=3276,LRECL=3276)
//SYSIN
DD \
BUILDSA INDD(SAMODS) OUTDD(TAPEDD) IPL(TAPE)
/\
Example 3: Core Image for IPL from DASD

In this example, the core image is created for IPLing in stand-alone mode from the
DASD with volume label IPLVOL. The core image, the IPL bootstrap, and IPLTEXT
are all placed on volume IPLVOL in data set SYS1.ADR.SAIPLD.VIPLVOL. The
OPERCNSL option is not specified; after Stand-Alone Services is IPLed, it loads a
wait-state and then waits for the first interrupt to define the operator console.

//STEP1
//SAMODS
//SYSIN
DD \
BUILDSA INDD(SAMODS) OUTDYNAM(IPLVOL) IPL(DASD)
/\
Example 4: Core Image for IPL from DASD with OPERCNSL

Option
In this example, the core image is created for IPLing in stand-alone mode from the
DASD with volume label IPLVOL. The core image, the IPL bootstrap, and IPLTEXT
are all placed on volume IPLVOL in data set SYS1.ADR.SAIPLD.VIPLVOL. The
OPERCNSL customization option is specified for the operator console definition;
after Stand-Alone Services is IPLed, it attempts to use the device at address 0009
as the operator console instead of waiting for the first interrupt.
28
COMPRESS Command

//STEP1
//SAMODS
//SYSIN
DD \
BUILDSA INDD(SAMODS) OUTDYNAM(IPLVOL) IPL(DASD) OPERCNSL(9)
/\
COMPRESS Command
The COMPRESS command compresses partitioned data sets on a specified
volume. Compressing (degassing) removes unused space between members in a
partitioned data set. Depending on the filtering criteria you specify , you can
compress either all or some of the partitioned data sets. This command is useful for
compressing system partitioned data sets before you apply maintenance (thus
avoiding certain space-related abends).
Note: You must not compress the data sets that contain DFSMSdss or IEBCOPY
executable code.
The actual PDS compression is done on the existing volume using the IEBCOPY
utility. To prevent loss of data if the system or IEBCOPY abnormally ends during
the processing, back up volumes or data sets that meet the filtering criteria before
using the COMPRESS command.
The COMPRESS command cannot process partitioned data sets that:
Are unmovable
Have no directory
COMPRESS Syntax
55COMpress A 5
FILterdd(ddn) ADMINistrator DYNALloc PASsword(ddn)
FDD
PSWD ,
6dsn/pswd
WAIT (2,2)
,
5DDName(6ddn)5%
WAIT(numsecs,numretries)
,
DYNAM(6(volser))
,unit
A : Additional Keywords with the COMPRESS command
29
COMPRESS Command
INClude(\\)
5BY(6(schar,op,(6arg)))5
,

,

EXClude(6dsn) INClude(6dsn)
,
INClude(\\)
EXClude(6dsn)
,

,

INClude(6dsn)

6
6
BY((schar,op,(arg)))
6
INClude(dsn)
,

,
EXClude(6dsn)
BY(6(schar,op,(6arg)))
Explanation of COMPRESS Command Keywords

This section describes the keywords for the COMPRESS command.
ADMINistrator
55
ADMINistrator
ADMINISTRATOR lets you act as a DFSMSdss-authorized storage administrator

for the COMPRESS command. If you are not authorized to use the
ADMINISTRATOR keyword, the command is ended with an error message.
Otherwise, access checking to data sets and catalogs is bypassed.
To use the ADMINISTRATOR keyword all of the following must be true:
The applicable FACILITY-class profile is defined.
For more details, see ADMINISTRATOR Keyword on page 216.
BY
,
6(schar,op,(
6arg)))5
5BY(
BY specifies that the data sets selected up to this point, by the processing of the
INCLUDE and EXCLUDE keywords, are to be further filtered. To select the data
set, all BY criteria must be met. See Filtering by Data Set Characteristics on
page 14 for a full discussion of schar, op, and arg. See the separate discussions of
the INCLUDE and EXCLUDE keywords for information on how these keywords are
specified.
Note: You must use FILTERDD when you have more than 255 entries in
INCLUDE, EXCLUDE, or BY list keywords.
30
COMPRESS Command
DDName
,
6ddn)5
5DDName(
ddn
specifies the name of the DD statement that identifies a volume whose partitioned
data sets, if selected, are to be compressed. To assure correct processing, each of
the DD statements corresponding to a DDNAME (ddn) must identify only one
volume serial number.
Refer to DFSMS/MVS DFSMSdss Storage Administration Guide for additional
information regarding storage requirements when processing multiple volumes.
DYNALloc
55
DYNALloc
DYNALLOC specifies dynamic allocation, instead of enqueue, to serialize the use

of selected partitioned data sets. This allows cross-system serialization in a
JES3/MVS environment.
Consider:
The serialization is of value only when the dynamic allocation/JES3 interface is
not disabled.
Run time increases when DYNALLOC is used to serialize data sets (as
opposed to enqueue) because overhead is involved in dynamic allocation and
serialization across multiple processors.
DYNAM
55
6(volser))
DYNAM(
,unit
DYNAM specifies a dynamically allocated volume whose partitioned data sets, if

selected, are to be compressed. The volume must be mounted and online. You
cannot specify a nonspecific volume serial number using an asterisk (*). Consider
using DYNAM instead of DD statements to allocate DASD volumes. This does not
appreciably increase run time and permits easier coding of JCL and command
input. Refer to DFSMS/MVS DFSMSdss Storage Administration Guide for additional
information regarding storage requirements when processing multiple volumes.
volser
specifies the volume serial number of a DASD volume to be processed.
unit
specifies the device type of a DASD volume to be processed. This parameter is
optional.
31
COMPRESS Command
EXClude
,
6dsn)5
5EXClude(
dsn
specifies the name of a data set to be excluded from the data sets selected by the
INCLUDE keyword. Either a fully or a partially qualified data set name can be used.
See the separate discussions of the INCLUDE and BY keywords for information on
how they are specified.
FILterdd
5FILterdd(ddn)5
FDD
ddn
specifies the name of the DD statement that identifies the sequential data set or
member of a partitioned data set that contains the filtering criteria to use. This is in
the form of card-image records, in DFSMSdss command syntax, that contain the
INCLUDE, EXCLUDE, and BY keywords that complete the syntax of the
COMPRESS command.
INClude
,
6dsn)5
5INClude(
dsn
specifies the name of a data set eligible to be compressed. Either a fully or a
partially qualified data set name can be used. See Filtering by Data Set Names
on page 12. If INCLUDE is omitted (but EXCLUDE or BY is specified) or if
INCLUDE(**) is specified, all partitioned data sets are eligible to be selected for
compressing. See the separate discussions of EXCLUDE or BY for information on
how these keywords are specified.
PASsword
55
PASsword(ddn)
PSWD
,
6dsn/pswd
PASSWORD specifies the passwords DFSMSdss uses for selected

password-protected data sets. (Password checking is bypassed for RACF-protected
data sets.) This must be specified only if:
You do not have the required RACF DASDVOL or RACF DATASET access.
The installation authorization exit does not bypass the checks.
32
COMPRESS Command
Note: You should specify the passwords for all data sets that do not have RACF
protection but do have password protection. During processing, a utility
invoked by DFSMSdss may have to prompt the operator for a password.
You can control authorization checking by using the installation
authorization exit.
ddn
member of a partitioned data set that contains data set names and their passwords.
This data set must contain card-image records in DFSMSdss command syntax
format.
dsn/pswd
dsn is a fully qualified data set name. pswd is its password. If no password follows
the slash (/), dsn is treated as though it were ddn.
Printing of actual data set passwords specified in your input command stream is
suppressed in the SYSPRINT output.
WAIT
WAIT(2,2)
55
WAIT specifies to DFSMSdss the length of a wait in seconds and the number of
retries to obtain control of a data set.
numsecs
is a decimal number (0255) that specifies the interval, in seconds, between retries.
numretries
is a decimal number (099) that specifies the number of times an attempt to gain
control of a data set can be retried.
The default for numsecs,numretries is WAIT(2,2), which specifies two retries at
2-second intervals. If you do not want to wait for a data set, specify 0 for either
numsecs or numretries.
Note: The WAIT keyword does not control wait/retry attempts for system
resources (such as the VTOC and the VVDS). For system resources, the
default wait time is 3 seconds and the default retry count is 30. This results
in a total wait time of 90 seconds. Refer to DFSMS/MVS DFSMSdss
Diagnosis Guide for information about controlling the wait/retry attempts for
system resources.
Example of Compress Operations

The following example compresses a selected partitioned data set.
33
CONVERTV Command
//JOB1
JOB accounting information,REGION=nnnnK
//STEP1
EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=A
//SYSIN
DD
\
COMPRESS
DYNAM(338)
/\ DYNAM ALLOC VOL 338
EXCLUDE(SYS1.\\)
/\ EXCL 'SYS1....' DATA SETS
/\ IF THEY MEET THIS CRITERION
BY((DSCHA EQ ))
/\ DATA SET WAS BACKED UP
/\
\/ \/ \/ \/
Compress partitioned data sets on volume 338000 if:

They are not system data sets (EXCLUDE(SYS1.**)), and
They have not been updated (DSCHA EQ 0) since the last time they were
backed up (dumped). This ensures that the data set can be recovered if the
system fails while the compress operation is running.
CONVERTV Command
The CONVERTV command is used to convert existing volumes to and from SMS
management without data movement. The CONVERTV command performs three
functions:
Locks volumes that are ready for conversion to prevent new data set
allocations (PREPARE keyword).
Examines volume identified by SMS to determine if they can be converted to
SMS management (TEST keyword). No conversion is actually performed, but
DFSMSdss identifies any data sets that cannot be converted to SMS
management and why they cannot be converted.
Performs conversion of volumes into or out of SMS management. Any
conditions that prevent conversion are identified.
Note: Proper RACF security authorization may be required. Refer to DFSMS/MVS
DFSMSdss Storage Administration Guide for more information.
CONVERTV Command Syntax

The syntax of the CONVERTV command is:
SMS
55CONVERTV5
A
TEST
SELECTMulti(ALL)
NONSMS
SELECTMulti(ALL) FORCECP(days)
SELM
ANY
FIRST
PREPARE
,
5DDName(6ddn)5%
DYNAM(6(volser))
,unit
A: Optional Keywords with CONVERTV SMS
34
CONVERTV Command
SELECTMulti(FIRST)
55
CATalog SELECTMulti(ALL) REDETermine
SELM
ANY
INCAT(6catname)
FIRST
Explanation of CONVERTV Command Keywords

This section describes the keywords for the CONVERTV command.
CATalog
55
CATalog
6catname)
INCAT(
CATALOG specifies that if a data sets catalog entry is not found in the standard
order of search, the data set is to be cataloged during the conversion.
If the CATALOG keyword has not been specified, and a data sets catalog entry is
not found in the standard order of search, the data set is not converted.
INCAT
specifies input catalogs that are not in the standard search order. This allows
non-VSAM data sets cataloged outside the standard order of search to be
processed.
catname
specifies a fully qualified catalog name.
If CATALOG is specified without INCAT, a single volume, non-VSAM data set
cataloged outside the standard order of search might be cataloged in more than
one place.
DDName
,
6ddn)5
5DDName(
ddn
specifies the name of the DD statement that identifies a volume to be processed.
This parameter is required when the DYNAM keyword is not specified.
DYNAM
,
6(volser))5
5DYNAM(
,unit
DYNAM specifies that a volume being processed must be dynamically allocated.

The volume must be mounted and online. You cannot specify a nonspecific volume
serial number using an asterisk (*). This keyword is required if DDNAME is not
specified.
35
CONVERTV Command
Consider using DYNAM instead of DD statements to allocate DASD volumes. This

does not noticeably increase run time and presents easier coding of JCL and
command input.
volser
unit
optional.
FORCECP
55
FORCECP(days)
FORCECP specifies that checkpointed data sets resident on the SMS volume can
be converted to non-SMS management. Checkpoint indications are removed from
the data set during conversion.
days
is a one-to-three-digit number in the range of zero to 255, and specifies the number
of days that must have elapsed since the last referenced date before the data set
can be converted.
INCAT
See the CATALOG keyword.
NONSMS
5NONSMS5
NONSMS specifies that a volume and all of the data sets on that volume are to be
converted from SMS management.
PREPare
5PREPare5
PREPARE specifies that a volume is to be prepared for SMS without conversion of

data sets. This prevents the volume from changing prior to performing the full SMS
conversion. After the PREPARE is requested, the volume is placed in initial status
and you cannot allocate new data sets. However, you can delete existing data sets.
The NONSMS keyword must be specified to return the volume to non-SMS
management.
REDETermine
55
REDETermine
REDETERMINE specifies that the SMS class information is to be reset for data
sets previously converted to SMS management whose SMS management class or
SMS storage class do not match those returned by the current ACS routines.
36
CONVERTV Command
REDETERMINE allows management class and storage class to be reset, but does
not update the data class.
If REDETERMINE is used with the TEST keyword, a report is produced specifying
all data sets eligible for conversion, including those already converted.
SELECTMulti
SELECTMulti(ALL)
55
ALL
SELECTMulti(ANY)
SELM
FIRST
SELECTMULTI specifies how cataloged multivolume data sets are to be selected

during conversion to or from SMS management. The volume list is the list of
volumes supplied by the DDNAME or DYNAM keyword.
ALL specifies that DFSMSdss not process a multivolume data set unless all of the
volumes that contain a part of the non-VSAM data set or VSAM base cluster are in
the volume list specified by DDNAME or DYNAM. ALL is the default for non-SMS
processing.
ANY specifies that DFSMSdss process a multivolume data set when any part of the
non-VSAM data set or VSAM base cluster is on a volume in the volume list
specified by DDNAME or DYNAM.
FIRST specifies that DFSMSdss process a multivolume data set only when the
DDNAME or DYNAM volume list includes the volume that contains the first part of
the non-VSAM data set or the primary data component of the base cluster for a
VSAM sphere. FIRST is the default for SMS processing.
SMS
SMS
55
SMS specifies that a volume and all of the data sets on that volume are to be
converted to SMS management. SMS is the default when the SMS, NONSMS, or
PREPARE keyword is not specified.
TEST
55
TEST
TEST specifies that DFSMSdss is to verify that a volume and its data sets are
eligible for conversion or for preparation. The TEST keyword functions just as if
TYPRUN=NORUN had been specified on the JCL EXEC PARM field. DFSMS must
be active to use this function.
Note: It is also possible to use TEST to verify that the ACS algorithms would
process correctly because the resulting report indicates the classes
associated with the various data sets on the volume.
37
CONVERTV Command
Examples of CONVERTV Operations

The following are examples of the CONVERTV command.
Example 1: Using the CONVERTV Command to Simulate

Conversion
//JOB1
//STEP1
//SYSPRINT
//SYSIN
JOB
EXEC
DD
DD
PGM=ADRDSSU
SYSOUT=A
\
CONVERTV SMS DYNAM((VOL1,338),(VOL2,338),(VOL3)) TEST

/\
The preceding example uses the TEST keyword to simulate conversion. The TEST
keyword produces a report that indicates whether the three volumes (VOL001,
VOL002, and VOL003) can be converted to SMS management.
Example 2: Using the CONVERTV Command to Convert to SMS

//JOB1
//STEP1
//SYSPRINT
//DVOL1
//DVOL2
//SYSIN
JOB
EXEC
DD
DD
DD
DD
PGM=ADRDSSU
SYSOUT=\
UNIT=SYSDA,VOL=SER=3381,DISP=OLD
UNIT=SYSDA,VOL=SER=3382,DISP=OLD
\
CONVERTV DDNAME(DVOL1,DVOL2) SMS INCAT(SYS1.ICFCAT.V3382) SELECTMULTI(FIRST) CATALOG

/\
The non-SMS-managed volume 338002 and the SMS-managed volume (in INITIAL
state) 338001 are converted to SMS. The volume 338001 has been placed in the
initial state by the storage administrator. Regardless of where the data sets reside,
all multivolume data sets whose first extent is on volume 338001 or 338002 are
processed. In addition, there are some data sets on volume 338002 cataloged in
the user catalog SYS1.ICFCAT.V338002. These data sets are uncataloged from
the user catalog and cataloged in the standard order of search. The INCAT
keyword provides access to the user catalog because the STEPCAT keyword is not
allowed.
Example 3: Using the CONVERTV Command to Convert from

SMS
38
COPY Command
//JOB1
//STEP1
//SYSPRINT
//SYSIN
JOB
EXEC
DD
DD
accounting information,nnnnK
PGM=ADRDSSU
SYSOUT=\
\
CONVERTV DYNAM(3383) NONSMS

/\
This example converts a volume to non-SMS-managed.
COPY Command
|
|
|
|
|
Use the DFSMSdss COPY command to perform data set, volume, and track
movement. You can copy data from one DASD volume to another, or move data
sets from one DASD volume to another volume of like or unlike device type.4 You
can copy data sets between DASD of like or unlike device type or a full volume or
ranges of tracks between DASD of like device type.
|
|
|
However, if you copy a full volume or ranges of tracks, the DASD must be of like
device type. The user must specify both the source and target volumes. Only one
source volume and one target volume are allowed.
DFSMSdss offers two ways to process COPY commands:
Logical processing is data-set oriented, which means it operates against data
sets and volumes independently of physical device format.
Physical processing operates against volumes and tracks, but is oriented
toward moving data at the track-image level.
Integrated catalog facility catalogs should not have a high-level qualifier of
SYSCTLG because this causes DFSMSdss to treat them as CVOLs.
For information on how to use the COPY command, refer to DFSMS/MVS
DFSMSdss Storage Administration Guide.
Special Considerations for Copy

The following special considerations may apply when you perform a copy operation:
The logical data set copy function does not support hierarchical file system
(HFS) data sets.
The copy function is not supported for SAM compressed extended function
data sets being copied to a non-SMS-managed target.
When you perform a logical copy operation of a VSAM compressed data set,
the target data set allocation must be consistent with the source data set
allocation as follows:
|
|
|
Like devices have the same track capacity and number of tracks per cylinder (for example, 3380 Model D, Model E, and Model K
DASD). Unlike DASD devices have different track capacities (for example, 3380, 3390, or RAMAC Virtual Array) or a different
number of tracks per cylinder, or both.
39
If the source is an extended-format VSAM KSDS, then the target must be

an extended-format VSAM KSDS.
If the source is a compressed VSAM KSDS, then the target must be a
compressed VSAM KSDS.
If the source is an alternate index for an extended-format KSDS, then the
target must be an alternate index for an extended-format KSDS.
The target control interval size must be equal to the source.
Extended-format VSAM is not supported by physical data set COPY.
COPY DATASET Syntax

55COPyDATASet( A )5%
DS
FILterdd(ddn)
B
,
FDD
OUTDDname(6ddn)
ODD
6
OUTDYnam((volser))
ODY
,unit
A: Additional Keywords with COPY DATASET

,
INClude(\\)
,

,

6dsn) INClude(6dsn)
EXClude(
,
INClude(\\)
EXClude(6dsn)
,

,

INClude(6dsn)

6
6
6
INClude(dsn)
,

,
EXClude(6dsn)
B: Optional Keywords with COPY DATASET
40
55
ADMINistrator
,
ALLExcp
,
ALLData(6dsn) ALLX BYPASSACS(6dsn)

ALLData(\)
55
AUTORELBlockaddress CANcelerror CATalog CHECKvtoc
AUTORELBLKA
RECATalog(newcatname)
RECATalog(\)
55
CONCurrent
,
CC NOTIFYCONCurrent
CONVERT(PDSE(6dsn))
NOTIFYCC
,PDS(6dsn)
PDS(6dsn)
,PDSE(6dsn)
55
DELete DYNALloc FORce FORCECP(days) FREESPACE(CI)
FSPC
,CA
55
INCAT(6catname)
ONLYINCAT
55
INDDname(6ddn)
IDD
6
INDYnam((volser))
IDY
,unit
,
SELECTMulti(ALL)
6
LOGINDDname(ddn)
LIDD
SELECTMulti(ALL)
SELM
ANY
6
LOGINDYnam((volser))
FIRST
LIDY
,unit
55
MAKEMULTI MENtity(modeldsn) MGMTCLAS(management-class-name)
MVOLser(volser)
NULLMGMTCLAS
NMC
PERCENTUtilized(1)
55
,
PASsword(ddn)
,
NOPACKing(6dsn)
PSWD
,
PERCENTUtilized(6n)
6
dsn/pswd
PCTU
B: Optional Keywords with COPY DATASET (continued)
41
READIOPacing()
55
PROCESS(SYS1) PURGE READIOPacing(nnn)
,UNDEFINEDSORG
PRG
RIOP
UNDEFINEDSORG
,SYS1
55
,

,
REBLock(6dsn) RELBlockaddress(6dsn)
RELBLKA
55
RENAMEUnconditional(pfx) REPlace SHAre SPHERE
RENUNC
,
SHR
(6(on,nn))
((pfx),6(on,nn))
|
|
TGTAlloc(SOURCE)
55
STORCLAS(storage-class-name)
,
TGTAlloc(BLK)
NULLSTORCLAS STORGRP(6groupname)
CYL
NSC
TRK
SOURCE
SRC
55
TGTGDS(DEFERRED) TOLerate(IOERror)
,
ACTIVE
,ENQFailure
TTRAddress(6dsn)
ROLLEDOFF
ENQFailure
SOURCE
,IOERror
SRC
VOLcount(\) WAIT(2,2)
55
UNCATalog VOLcount(\) WAIT(numsecs,numretries) WRItecheck
SRC
WRC
N(nn)
ANY
COPY FULL and COPY TRACKS Syntax

55COPyFULl5
,,c1,max head #
6
TRACKS((c1))
TRKS
,c1,max head #
D
,h1
,max head #
,c2
,h2
5INDDname(ddn)OUTDDname(ddn)5%
IDD
ODD
INDYnam(volser) OUTDYnam(volser)
IDY
,unit
ODY
,unit
C: Optional Keywords with COPY FULL

55
ADMINistrator
,
ALLExcp CANcelerror CHECKvtoc CONCurrent
ALLData(6dsn) ALLX
CC
ALLData(\)
READIOPacing()
55
COPYVolid PASsword(ddn) PURge READIOPacing(nnn)
CPYV
PSWD ,
PRG
RIOP
6dsn/pswd
5WRItecheck5
TOLerate(IOERror) WRC
D: Optional Keywords with COPY TRACKS

42
COPY Command
55
ADMINistrator CANcelerror CHECKvtoc COMpress CONCurrent COPYVolid CPVOLume
CC CPYV
|
|
55
,
PASsword(ddn) PURge
PSWD ,
PRG
6
OUTTRacks((cc))
6dsn/pswd
OUTTRKS
,hh
READIOPacing()
55
READIOPacing(nnn) TOLerate(IOERror) WRItecheck
RIOP
WRC
Explanation of COPY Command Keywords

This section describes the keywords for the COPY command.
ADMINistrator
55
ADMINistrator

for the COPY command. If you are not authorized to use the ADMINISTRATOR
keyword, the command is ended with an error message. Otherwise, access
checking to data sets and catalogs is bypassed.
ALLData
55
6dsn)
ALLData(
ALLData(\)
dsn
specifies the fully qualified name of a data set whose data set organization is PS5,
PSU, PO, POU, or null.6The data set is processed as follows:
For a full-volume copy, all of the allocated space for the source data set is
copied to the target volume.
When ALLDATA or ALLEXCP is specified for an extended-sequential data set, data beyond the last used block pointer is not
retained. The target data set is allocated with the same amount of space as the source data set during a logical restore or copy
operation.
Any time a data set can have data beyond the last used block pointer in the data set's VTOC entry, or has a null data set
organization, or is the first or intermediate volume of a multivolume data set that has a null data set organization, you must specify
ALLDATA(dsn) (or ALLDATA(*) if the data set is not empty or ALLEXCP if the data set is empty) to copy all its data. This applies
to like targets only. JES2/JES3 data sets can have these characteristics, as can CICS journal and MSVCJRNL data sets.
43
COPY Command
For a data set copy, the function of this parameter is dependent upon certain
data set characteristics, device characteristics, and other DFSMSdss keywords
specified. See Table 2 on page 78 and Table 3 on page 79 for more
information.
* (asterisk)
specifies all data sets whose data set organization is PS, 5 PSU, PO, POU, or null
and are not empty (the last used block pointer in the data set's VTOC entry is not
zero). 6 The data sets are processed as follows:
For a full-volume copy, all of the allocated space for the source data set is
For a data set copy, the function of this parameter is dependent upon certain
information.
DFSMSdss determines the amount of space allocated or used for the data set by
counting how many tracks have been allocated or used by the data set. For this
reason, the allocated space for the target data set may occupy more tracks than
the source when going to a different device type.
Attention: Since the unused portion of the data set may or may not be copied,
care should be used when specifying the ALLDATA keyword with DELETE. For
example, if a data set contains records past the last used block pointer in the data
sets VTOC entry that you wish to preserve and you perform a data set copy with
ALLDATA and DELETE to an unlike device, these records are not copied to the
target, but the source will be deleted upon successful completion of the copy.
ALLExcp
55
ALLExcp
ALLX
ALLEXCP specifies all data sets whose data set organization is PS, 5 PSU, PO,
POU, or null and are empty (the last used block pointer in the data set's VTOC
entry is zero). 6 The data sets are processed as follows:
For a full-volume copy, all of the allocated space for the source data set are
For a data set copy, the function of this keyword is dependent upon certain
information.
Attention: Since all of the allocated space may or may not be copied, care should
be used when specifying the ALLEXCP keyword with DELETE. For example, if a
data set contains records that you wish to preserve, but the last block pointer in the
data sets VTOC entry is zero and you perform a data set copy with ALLEXCP and
DELETE to an unlike device, these records are not copied to the target, but the
source will be deleted upon successful completion of the copy.
44
COPY Command
AUTORELBlockaddress
55
AUTORELBlockaddress
AUTORELBLKA
AUTORELBLOCKADDRESS specifies that direct access data sets are to be

automatically processed as being organized by relative block address provided that
they were accessed with an OPTCD setting indicating relative block addressing.
(Refer to DFSMS/MVS Macro Instructions for Data Sets.) These direct access data
sets are to be processed by relative block address rather than by TTR, and without
maintaining the relative track and record number for each record. The blocks must
fit on the tracks of the target volume.
Notes:
1. If any such data set is actually organized by TTR, the data set may become
unusable.
2. The TTRADDRESS keyword takes precedence over the
AUTORELBLOCKADDRESS keyword. Refer to the RELBLOCKADDRESS and
TTRADDRESS keywords for more information.
3. AUTORELBLOCKADDRESS is ignored for direct access data sets with
variable-spanned record formats or standard user labels.
BY
,
6(schar,op,(
6arg)))5
5BY(
INCLUDE and EXCLUDE keywords, are to be filtered further. To select the data
page 14 for a full discussion of schar, op, arg, and for further information on BY
filtering.
BYPASSACS
55
6dsn)
BYPASSACS(
BYPASSACS specifies that the automatic class selection (ACS) routines are not
invoked to determine the target data set class names. To specify BYPASSACS,
RACF authorization may be required. Refer to DFSMS/MVS DFSMSdss Storage
Administration Guide for more information.
See Assignment of Class Names by Using the RESTORE and COPY Commands
on page 168 for information on the assignment of class names using the COPY
command.
45
COPY Command
dsn
specifies a fully or partially qualified data set name. (See Filtering by Data Set
Names on page 12 for rules.)
If a data set is being renamed, the old name must be specified.
CANcelerror
55
CANcelerror
CANCELERROR specifies that the copy task be ended for a permanent read error,
or that the copy of a data set is ended for a write error.
Permanent read error, such as a data check:
If CANCELERROR is specified, the copy task is ended. If this keyword is not
specified, the track in error is not copied and the copy continues. Only the data
set receiving the error is ended, and the DFSMSdss copy function continues to
process any subsequent data sets.
Write error, such as an invalid track format:
When invalid tracks are created during COPY processing, message ADR367E
is issued and the invalid tracks are erased from the target volume, regardless
of whether CANCELERROR is specified. For data set copy, processing of the
data set ends and the target data set is deleted. The copy operation continues
with the next data set. For full volume and tracks copy, processing for the
volume ends. Subsequent tracks are not processed.
|
|
|
|
DFSMSdss allows you to change this default operation. A patch byte is

provided to allow you to change the default handling of invalid tracks created
during COPY processing. Refer to DFSMS/MVS DFSMSdss Diagnosis Guide
for additional information.
During copy operations in which a utility performs the copy, DFSMSdss ignores this
keyword. CANCELERROR has no effect on the following types of errors on a
DASD volume:
Equipment check
Command reject
Intervention required
Busout parity
This keyword may be used in conjunction with CHECKVTOC to specify whether or

not the operation is to continue in the event of terminating VTOC errors found
during VTOC checking. Refer to CHECKVTOC keyword.
CATalog
55
CATalog
RECATalog(\)
CATALOG specifies that on a data set copy operation, DFSMSdss is to catalog

data sets that it allocates.
46
COPY Command
CATALOG
catalogs the target data set as determined by the standard catalog search order.
This is the default for VSAM, multivolume data sets, and SMS-managed data sets.
RECATALOG(newcatname)
catalogs the target data set in the newcatname catalog.
RECATALOG(*)
catalogs the target data set in the same catalog that points to the source data set.
If the source data set was not cataloged, the new data set is not cataloged either.
After DFSMSdss determines the catalog status of the data set and is changed by
other means outside of DFSMSdss, the original catalog status is used.
Notes:
1. Be careful when using the RECATALOG(newcatname) keyword because the
target data set may be cataloged outside of the standard order of search.
2. The CATALOG or RECATALOG operation fails if the target data set is already
cataloged in the same catalog and DELETE, RENAMEU, or UNCATALOG is
not specified. The RECATALOG keyword is ignored for SMS-managed targets.
3. An alternate index (AIX) is always cataloged in the same catalog as its
associated base cluster. If the base cluster is recataloged, the AIX is
recataloged.
4. If you omit the CATALOG or RECATALOG keyword for a single volume,
non-VSAM, non-SMS-managed data set, the target data set is uncataloged.
5. The CATALOG and RECATALOG keywords are ignored for preallocated data
sets.
CHECKvtoc
55
CHECKvtoc
CHECKVTOC specifies that a VTOC analysis of the source volume be performed

during copy processing. In the event of terminating VTOC errors found during
analysis, operation continues unless the CANcelerror keyword is specified.
CHECKVTOC is ignored if CPVOLUME is also specified.
CONCURRENT
55
CONCurrent
CC NOTIFYCONCurrent
NOTIFYCC
CONCURRENT specifies that the data is to be processed with concurrent copy if it

is possible. Otherwise, the data is processed as if CONCURRENT were not
specified.
If a concurrent copy operation fails after signaling that the concurrent copy
initialization was complete (and update activity on the data has resumed), it is not
possible to recover the data at the point-in-time at which the concurrent copy
operation was started. This is because the data may have been updated while the
copy operation was progressing.
47
COPY Command
Attention: Performing concurrent copy operations against many large data sets
when there is also heavy update activity (such as reorganizing data sets or
initializing the volume the data sets reside on) can result in a shortage of storage.
The shortage occurs because data is transferred to data-space storage faster than
DFSMSdss can process it. Refer to the DFSMS/MVS DFSMSdss Storage
Administration Guide in the "Managing Availability with DFSMSdss" chapter for
additional information on determining concurrent copy storage requirements.
Note: CONCURRENT cannot be specified with DELETE or UNCATALOG
keywords because after the concurrent copy operation has begun, the
original data can still be updated.
|
|
|
|
If the source volume is a RAMAC Virtual Array and CONCURRENT keyword is

specified, DFSMSdss uses the Snapshot capability of the RVA to provide a function
equivalent to concurrent copy. This function is called concurrent copy-compatible
Snapshot and is transparent to the user.
NOTIFYCONCURRENT
For a logical data set copy operation, specifies that DFSMSdss issues message
ADR767I for every data set that is successfully included in the concurrent copy
operation. If not specified, messages are issued only for data sets that are not
successfully included in the concurrent copy operation.
CONVERT
55
6dsn))
CONVERT(PDSE(
,

6dsn)
,PDS(
6dsn)
PDS(
6dsn)
,PDSE(
CONVERT(PDSE(dsn))
specifies that the PDSs listed in the dsn be converted to PDSE
CONVERT (PDS(dsn))
specifies that the PDSE listed in the dsn be converted to PDSs.
Notes:
1. If the target data set is a PDSE, it must be SMS-managed.
2. The CONVERT keyword is not supported for extended-sequential data sets.
COPYVolid
55
COPYVolid
CPYV
COPYVOLID specifies that the volume serial number (VOLID) from the input DASD
volume is to be copied to the output DASD volume. This applies to full copy
operations and to tracks copy operations if track 0 (zero) is copied.
48
COPY Command
Notes:
1. COPYVOLID is required for a full-volume copy operation of an SMS-managed
input volume.
2. When the volume serial number is changed by using a COPYVOLID keyword,
profiles are not built for the RACF-protected data sets on the target volume or
for the RACF DASDVOL for the RACF-protected DASD volume. When the
volume serial number on a DASD volume is changed, the operator is notified.
The operating system then initiates a demount of the volume.
3. Exercise caution using COPYVOLID in a multiple task job step when two or
more of the tasks are using the same output volume. If the output volume is
made unavailable by the first task, all succeeding tasks that use the same
output volume fail.
4. COPYVOLID cannot be performed if there are permanent I/O errors or if
CANCELERROR is specified. If TOLERATE(IOERROR) is honored, however,
COPYVOLID is performed.
CPVOLume
55
CPVOLume
CPVOLUME specifies that the input and output volumes are VM-format volumes
and that the OS-compatible VTOCs must begin on track zero, record five. You must
specify the track range to be copied with the TRACKS keyword, as the
OS-compatible VTOCs do not describe the extents of any data on the volume. You
must also specify the ADMINISTRATOR keyword with CPVOLUME because
DFSMSdss cannot check access authorization for VM data.
DATASet
5DATASet5
DS
DATASET specifies a data set copy operation using filtering. See Chapter 2,
FilteringChoosing the Data Sets You Want Processed on page 11 for an
explanation of the filtering process used. Unless ALLDATA or ALLEXCP is
specified, only used tracks are copied for sequential and partitioned data sets and
for data sets with a data set organization that is null (for example, JES2/JES3 data
sets). If the free space map in the VTOC is invalid, all tracks for the data set are
copied.
Notes:
1. Either the FILTERDD, INCLUDE, EXCLUDE, or BY keyword must be specified
when data set is selected.
2. Non integrated catalog facility VSAM catalogs are not supported for data set
processing. If non integrated catalog facility VSAM catalogs are processed, the
results can be unpredictable.
49
COPY Command
DELete
55
DELete
DELETE specifies that for a data set copy DFSMSdss deletes VSAM and
non-VSAM data sets from the source volume after a successful copy. This moves,
in effect, a data set from one volume to another. The data sets are scratched and
uncataloged.
Notes:
1. If you do not specify DELETE when copying cataloged data sets, the target
data set must either be cataloged (with RECATALOG) in a different catalog or
renamed (with RENAMEU).
2. If you copy a data set with DFM attributes to a non-SMS-managed target, the
new data set will not have the DFM attributes.
3. Unexpired source data sets are deleted only if you also specify PURGE.
4. Even if PROCESS (SYS1) is specified, SYS1.VVDS and SYS1.VTOCIX data
sets cannot be copied and deleted.
5. Do not specify SHARE if you specify DELETE.
6. If DFSMSdss encounters a damaged PDS during logical data set copy, it
displays messages indicating the nature and relative location of the problem.
In order to maintain complete data integrity, DFSMSdss does not delete the
source data set. The copy of the data set fails, and the target is deleted. In
order to copy and delete a damaged PDS, use the NOPACKING keyword.
7. Do not specify DELETE with CONCURRENT, because after the concurrent
copy operation has begun, the original data can still be updated.
DYNALloc
55
DYNALloc

of data sets. The data sets whose extents are to be relocated are serialized
throughout the copy operation. This allows cross-system serialization in a
Notes:
1. The serialization is of value only when the dynamic allocation/JES3 interface is
not disabled.
2. Run time increases when you use DYNALLOC to serialize data sets (as
3. If a data set passes INCLUDE/EXCLUDE filtering and is migrated before BY
filtering and DYNALLOC is used, the dynamic allocation causes the data set to
be recalled. DFSMSdss waits for the recall processing to complete. If the data
set is recalled to a different volume, a message is issued indicating that the
VTOC entry was not found.
50
COPY Command
EXClude
,
6dsn)5
5EXClude(
dsn
specifies the name of a data set to be excluded from the data sets selected by the
INCLUDE keyword. Either a fully or a partially qualified data set name can be used.
See the separate discussions of INCLUDE and BY for information on how these
keywords are specified.
FILterdd
55FILterdd(ddn)5%
FDD
ddn
member of a partitioned data set that contains the filtering criteria to be used. This
is in the form of card-image records, in DFSMSdss command syntax, that contain
the INCLUDE, EXCLUDE, and BY keywords.
FORce
55
FORce
FORCE specifies that DFSMSdss copy one or more unmovable data sets to a like
or unlike device type. Unmovable data sets are those allocated as absolute track
(ABSTR) or as unmovable (PSU, POU, DAU, or ISU). FORCE applies to ISAM
data sets only when they are allocated with the unmovable attribute. The allocation
attribute, unmovable or ABSTR, is carried over to the output volume.
When copying to like devices, DFSMSdss copies the data sets to the same track
locations on the target volume. In this case, FORCE is not required if the target
volume uses an indexed VTOC, and the space where the unmovable data set is to
reside is available. If any of these conditions is not true, DFSMSdss does not copy
any unmovable data sets unless FORCE is specified. In this case, DFSMSdss
places the unmovable data sets in any available location.
When copying to unlike devices, you must specify FORCE. The unmovable data
sets are placed in any available location.
FORCECP
55
FORCECP(days)
51
COPY Command
FORCECP specifies that checkpointed data sets resident on the SMS volume or
volumes can be copied. Checkpoint indications are removed from the target data
set.
days
is a one- to three-digit number in the range of zero to 255, and specifies the
number of days that must have elapsed since the last referenced date before the
data set can be copied.
FREESPACE
55
FREESPACE(CI)
FSPC
,CA
FREESPACE specifies free space values for DFSMSdss-allocated target VSAM

data sets. If this keyword is omitted, the control interval and control area free space
are the same as the source data set.
CI
specifies the percentage of free space to be kept in each control interval during
allocation of the data set.
CA
specifies the percentage of free space to be kept in each control area during
allocation of the data set. When omitted, the control area free space is the same as
the source data set.
FULl
5FULl5
FULL specifies that an entire DASD volume is to be copied. This is the default.
Unallocated tracks are not copied. Unless specified by ALLDATA or ALLEXCP, only
the used (rather than allocated) tracks are copied for sequential data sets,
partitioned data sets, and for data sets with unknown data set organization (for
example, JES2/JES3 data sets with a data set organization that is null). If the
VTOC has errors, all tracks are copied. Used tracks consist of the tracks from the
beginning of the data set to the last-used track (as indicated by the last used block
pointer in the data sets VTOC entry).
Notes:
1. You cannot specify the SHARE or TOL(ENQF) keywords for FULL operations.
2. Non integrated catalog facility VSAM catalogs are not supported for full-volume
processing. If non integrated catalog facility VSAM catalogs are processed, the
INCAT
55
6catname)
INCAT(
ONLYINCAT
52
COPY Command
INCAT specifies one or more user catalogs to be searched before the standard
order of search for locating data sets. STEPCAT and JOBCAT are not allowed for
processing SMS-managed data sets. This keyword allows you to identify specific
source catalogs. To specify INCAT, RACF authorization may be required. Refer to
DFSMS/MVS DFSMSdss Storage Administration Guide for more information.
catname
ONLYINCAT
specifies that DFSMSdss is to only search catalogs specified in the INCAT catalog
name list.
DFSMSdss does not process an SMS-managed data set that is cataloged outside
the standard order of search, even if it is cataloged in one of the catalogs specified
with the INCAT keyword.
INClude
,
6dsn)5
5INClude(
dsn
specifies the name of a data set eligible to be copied. Either a fully or a partially
qualified data set name can be used. See Filtering by Data Set Names on
page 12. If INCLUDE is omitted (but EXCLUDE or BY is specified) or INCLUDE(**)
is specified, all data sets are eligible to be selected for copying.
INDDname
55
6ddn)
INDDname(
IDD
ddn
specifies the name of the DD statement that identifies a volume to be copied. For a
data set copy operation, you can specify multiple names (that is, multiple volumes),
separated by commas. For single-volume data sets, each of the DD statements
corresponding to a DDNAME (ddn) must identify only one volume serial number.
Note: If no input volumes are specified for a data set copy operation, DFSMSdss
selects from all data sets cataloged in the catalogs accessible through the
standard search order. If either INDDNAME or INDYNAM is specified,
DFSMSdss still uses the standard catalog search order, but it selects data
sets only from the specified volumes. For multivolume data sets, use
LOGINDDNAME or LOGINDYNAM with SELECTMULTI.
When DFSMSdss invokes IEHMOVE to copy multivolume non-VSAM data sets,
IEHMOVE requires that the first DD statement in the job stream must identify all
input volumes. DFSMSdss requires separate DD statements for the input volumes.
To accommodate both requirements, you must code your JCL as follows:
//INDD1
//INDD2
DD
DD
UNIT=(SYSDA,2),VOL=SER=(VOL1,VOL2),DISP=SHR
UNIT=SYSDA,VOL=SER=VOL2,DISP=SHR
53
COPY Command
and code your DFSMSdss control statement:

COPY
LOGINDD(INDD1,INDD2) ...
INDYnam
55
6(volser))
INDYnam(
IDY
,unit
INDYNAM specifies that the volumes to be copied are to be dynamically allocated.

serial number using an asterisk (*). Only one volume is allowed for a full or tracks
copy; one or more volumes are allowed for a data set copy operation. Consider
using INDYNAM instead of DD statements to allocate DASD volumes. This does
not appreciably increase run time and permits easier coding of JCL and command
input.
volser
specifies the volume serial number of a DASD volume to be copied.
unit
specifies the device type of a DASD volume to be copied. This parameter is
optional.
LOGINDDname
55
,
SELECTMulti(ALL)
LOGINDDname(6ddn)
LIDD
SELECTMulti(ALL)
SELM
ANY
FIRST
LOGINDDNAME specifies that data sets be selected from the specified volume or
volumes (which you can also do by specifying INDDNAME or INDYNAM) and also
allows you to specify SELECTMULTI (which cannot be done with INDDNAME or
INDYNAM).
ddn
specifies the name of the DD statement that identifies a volume that contains the
data sets to be copied. For single-volume data sets, each of the DD statements
corresponding to a DDNAME (ddn) must identify only one volume serial number.
See the SELECTMULTI description and the Notes under LOGINDYNAM.
LOGINDYnam
55
,
SELECTMulti(ALL)
LOGINDYnam(6(volser))
LIDY
,unit
SELECTMulti(ALL)
SELM
ANY
FIRST
LOGINDYNAM specifies that the volumes that contain the data sets to be copied
are dynamically allocated. The volume must be mounted and online. You cannot
specify a nonspecific volume serial number using an asterisk (*).
54
COPY Command
volser
specifies the volume serial number of a DASD volume to be copied.
unit
specifies the device type of a DASD volume to be copied. This parameter is
optional.
SELECTMULTI
specifies the method for determining how cataloged multivolume data sets are to be
selected during a logical data set copy operation. SELECTMULTI is accepted only
when logical volume filtering is specified with either LOGINDDNAME or
LOGINDYNAM keywords. If logical volume filtering is not used, the specification of
SELECTMULTI is not accepted.
ALL is the default, and specifies that DFSMSdss not copy a multivolume data set
unless the volume list specified by LOGINDDNAME or LOGINDYNAM lists all the
volumes that contain a part of the data set or VSAM cluster.
ANY specifies that DFSMSdss copy a multivolume data set when any volume in
the volume list specified by LOGINDDNAME or LOGINDYNAM contains a part of
the data set or VSAM cluster.
FIRST specifies that DFSMSdss copy a multivolume data set only when the volume
list specified by LOGINDDNAME or LOGINDYNAM lists the volume that contains
the first part of the data set. For VSAM data sets, the volume list must include the
volume containing the first extent of the data component for the base cluster.
Notes for LOGINDDNAME and LOGINDYNAM keywords:
1. If neither LOGINDDNAME nor LOGINDYNAM is specified, DFSMSdss selects
from all data sets cataloged in the catalogs accessible through the standard
search order. If either LOGINDDNAME or LOGINDYNAM is specified,
DFSMSdss still uses the standard catalog search order, but it selects data sets
only from the specified volumes.
2. A multivolume data set that has extents on volumes not specified with either
the LOGINDDNAME or LOGINDYNAM keywords is copied only if you specify
the SELECTMULTI keyword.
MAKEMULTI
55
MAKEMULTI
MAKEMULTI allows DFSMSdss to convert single volume data sets into multivolume
data sets. The default is not to convert single volume data sets into multivolume
data sets.
This keyword applies only to SMS-managed target data sets. Only single volume,
non-VSAM data sets are eligible to be changed into multivolume data sets.
SMS-managed target data sets are given a volume count (VOLCOUNT) that is
either:
The number of SMS output volumes specified in the COPY command, if output
volumes are specified through OUTDDNAME or OUTDYNAM
The number of volumes in the target storage group or 59, whichever is less
55
COPY Command
A data set's volume count is the maximum number of volumes to which the data
set may extend. At any one time, there may be a mixture of primary volumes
(volumes on which space is allocated for the data set) and candidate volumes
(volumes on which space may be allocated at a future time). The total sum of the
primary volumes and candidate volumes is the data set's volume count.
Note: When MAKEMULTI is specified and VOLCOUNT is also specified with an
option other than VOLCOUNT(*), the VOLCOUNT option overrides
MAKEMULTI.
MENtity
55
MENtity(modeldsn)
MVOLser(volser)
MENTITY specifies, for RACF-protected data sets, an entity (modeldsn) and,

optionally, the serial number of the volume containing that entity (volser). These
keywords are used to define the data sets to RACF. Specification of MVOLSER is
optional for one of the following:
When the model entity (MENTITY) is cataloged in an integrated catalog facility
catalog.
When a non-VSAM data set is cataloged in the standard catalog search order.
When MVOLSER is specified for a VSAM model entity, volser must be the volume
serial number of the catalog in which the model entity is cataloged. If these
keywords are not specified, DFSMSdss defines the data set to RACF by modeling
the target profile after the source data set, if the source is discretely protected.
Target data sets (preallocated or nonpreallocated) are RACF-protected only if the
corresponding source data sets were so protected. If a source data set is protected
with a generic profile, RACF generic profile checking must be activated prior to
invoking the copy function.
See Chapter 6, Data Security and Authorization Checking on page 207 for more
information about data security and data set profile considerations.
MGMTCLAS
55
MGMTCLAS(management-class-name)
NULLMGMTCLAS
NMC
MGMTCLAS specifies the user-desired management class that replaces the source
management class as input to the ACS routines. You must have the proper RACF
authority for the management class specified. The keyword itself does not require
RACF authorization.
NULLMGMTCLAS/NMC specifies that the input to the ACS routines is a null
management class rather than the source data sets management class.
MGMTCLAS and NULLMGMTCLAS are mutually exclusive; you cannot specify
these keywords together.
56
COPY Command
Notes:
1. All SMS-managed data sets specified in the BYPASSACS keyword are
assigned the specified management class because the ACS routines are not
invoked. Non-SMS-managed data sets do not have a management class.
2. See Assignment of Class Names by Using the RESTORE and COPY
Commands on page 168 for information on the assignment of class names
using the copy function.
NOPACKing
55
6dsn)
NOPACKing(
NOPACKING specifies that DFSMSdss is to allocate the target data set only to the
same or like device types as the source data set is allocated on and that
DFSMSdss is to use track level I/O to perform data movement. This results in an
exact track-for-track image of the source data set on the target volume.
dsn
specifies the fully or partially qualified names of a PDS to be processed.
NOPACKing is only valid with a PDS. If REBLOCK is specified, REBLOCK is
ignored for the data set. If the data set is specified with CONVERT(PDSE()),
NOPACKing is ignored for the data set.
A PDS copied or restored by using NOPACKing is not be compressed during data
movement.
NOPACKing can be used for a damaged PDS that is currently usable by an
application but would be made unusable by compression or other rearrangement of
the physical layout of the data.
NOTIFYCONCURRENT
See the CONCURRENT keyword.
NULLMGMTCLAS
See the MGMTCLAS keyword.
NULLSTORCLAS
See the STORCLAS keyword.
ONLYINCAT
See the INCAT keyword.
OUTDDname
55
6ddn)
OUTDDname(
ODD
57
COPY Command
ddn
specifies the name of the DD statement that identifies the output DASD volume. To
assure correct processing, each of the DD statements corresponding to a DDNAME
(ddn) must identify only one volume serial number. The volume serial number
specified must be a valid DASD device; DD DUMMY is not supported. Only one
volume is allowed for a full or tracks copy; one or more volumes are allowed for a
data set copy operation. Multiple names in a data set copy must be separated by
commas.
See the Note under OUTDYNAM for additional information.
OUTDYnam
55
6(volser))
OUTDYnam(
ODY
,unit
OUTDYNAM specifies that the output DASD volume is to be dynamically allocated.

serial number using an asterisk (*). Only one volume is allowed for a full or tracks
copy; one or more volumes are allowed for a data set copy.
volser
specifies the volume serial number of the volume.
unit
specifies the device type of the volume. This parameter is optional.
Note for OUTDDNAME and OUTDYNAM Keywords: DFSMSdss now
distinguishes between non-SMS and SMS volumes specified in the
OUTDDNAME or OUTDYNAM keywords. For non-SMS allocations, only the
volumes that are non-SMS are considered for allocation. Similarly, only
SMS volumes are considered for SMS allocations.
This distinction is also used when determining the volume count for a
multivolume allocation. Where volume count is determined from the number
of specified volumes, only those volumes eligible for the type of allocation
being done are counted. If there are no volumes that match the type of
allocation (SMS volumes for SMS allocation, or non-SMS volumes for
non-SMS allocation), processing proceeds with a null volume list.
OUTTRacks
55
6(cc))
OUTTRacks(
OUTTRKS
,hh
OUTTRACKS specifies, for a tracks copy operation, the cylinder (cc) and head
number (hh) on the output volume to which the tracks from the input volume are to
be copied. If you do not specify OUTTRACKS operation, the tracks are copied to
the same place on the output volume where they were on the input volume. The
number of (cc,hh) combinations specified in the OUTTRACKS keyword must be the
58
COPY Command
same as the number of (c1,h1,c2,h2) combinations specified in the TRACKS

keyword.
PASsword
55
PASsword(ddn)
PSWD
,
6dsn/pswd
PASSWORD specifies the passwords that DFSMSdss is to use for

password-protected data sets. (Password checking is bypassed for RACF-protected
data sets.) This keyword is required only when:
You do not have the required RACF DASDVOL or RACF data set access.
You do not want to be prompted for the password for VSAM data sets.
authorization exit.
Catalog passwords are not supported to facilitate disaster recovery operations,
application data transfers, and data set migration. Catalog protection via an access
control facility, such as RACF, is the preferred method of protection.
Passwords for a tracks copy operation are required only for the data sets on which
the requested ranges fall.
ddn
specifies the name of the DD statement that identifies the sequential data set, or
member of a partitioned data set, that contains data set names and their
passwords. This data set must contain card-image records in DFSMSdss command
syntax format.
dsn/pswd
Printing of actual data set passwords specified in the input command stream is
When a system utility is being used to perform the DFSMSdss copy operation, the
user must supply the password for each password-protected data set selected or
have the proper RACF data set access authority.
PERCENTUtilized
PERCENTUtilized(1)
55
6n)
PERCENTUtilized(
PCTU
59
COPY Command
PERCENTUTILIZED specifies that DFSMSdss must stop allocating data sets to the
target volumes when the allocated space reaches n percent of the total space on
the target volume. The default value is 100. Specify more than one n if you have
more than one target volume (for instance, a volume for overflow). If there are more
target volumes than you have values in this keyword, the last value is used for the
remaining target volumes. This keyword is used as a guide only and might not be
precise for all situations.
Notes:
1. PERCENTUTILIZED is ignored when the target data set is preallocated.
2. PERCENTUTILIZED is not supported in an SMS environment.
3. PERCENTUTILIZED is ignored if no output volume is specified.
PROCESS
55
PROCESS(SYS1)
,UNDEFinedsorg
UNDEFinedsorg
,SYS1
SYS1
specifies that DFSMSdss is to allow data sets with a high-level qualifier of SYS1 to
be copied to a preallocated target and that SYS1 data sets can be deleted and
uncataloged. SYS1.VVDS and SYS1.VTOCIX data sets cannot be copied, deleted,
or uncataloged. To specify PROCESS(SYS1), RACF authorization may be required.
Refer to DFSMS/MVS DFSMSdss Storage Administration Guide for more
information.
UNDEFinedsorg
PROCESS also specifies that DFSMSdss allows data sets with undefined data set
organizations to be copied to an unlike target with a larger capacity. Refer to
Table 2 on page 78 and Table 3 on page 79 for the action taken by DFSMSdss.
Note: Even though the data is being copied to a device with a larger track
capacity, the data may not fit on the output device. For example, if the
source device is a 3380, and the output device is a 3390 and the data sets
block size is less than 277 bytes, a track on the target cannot contain as
much data as a track on the source and the message ADR366W (Invalid
Track Format) is issued.
PURge
55
PURge
PRG
PURGE specifies, for a full or tracks copy operation, that unexpired data sets on
the target volume can be overlaid. If PURGE is not specified and unexpired data
sets reside on the target tracks, the copy operation is ended.
For a data set copy operation, PURGE specifies that unexpired source data sets
are to be deleted after they are successfully copied. This keyword is only valid
when the DELETE keyword is also specified.
60
COPY Command
READIOPacing
READIOPacing()
55
READIOPacing(nnn)
RIOP
READIOPACING specifies the pacing (that is, I/O delay) to be used for DFSMSdss
DASD read channel programs. You can use this keyword to allow more time for
other applications to complete I/O processing. DFSMSdss waits the specified time
before issuing each channel program that reads from DASD.
nnn
specifies the amount of time in milliseconds. The maximum delay that can be
specified is 999 milliseconds.
Notes:
1. If READIOPACING is not specified, there is no I/O delay.
2. The additional wait time does not apply to error recovery channel programs.
3. READIOPACING does not apply to concurrent copy I/O.
REBLock
55
6dsn)
REBLock(
REBLOCK specifies that DFSMSdss is to reblock one or more of the selected

sequential or partitioned data sets.
dsn
specifies the fully or partially qualified names of a sequential or partitioned data set
to be copied and reblocked.
The REBLOCK keyword is ignored for:
Unmovable data sets
Data sets with record format of U (except for partitioned load modules)
Data sets with a record format of V, VS, VBS, or F
Partitioned data sets with note lists (except for partitioned load modules)
Partitioned data sets that are also specified in the NOPACKING keyword
Additionally, both the installation options exit and the installation reblock exit can
override the specification of the REBLOCK keyword. The installation options exit
can specify that no data set is to be reblocked. The installation reblock exit can
specify whether a given data set is to be reblocked.
Some sequential and partitioned data sets have an attribute indicated in the VTOC
making them capable of being reblocked. These data sets may be automatically
reblocked by DFSMSdss independent of the REBLOCK keyword.
information on DFSMSdss processing of reblockable data sets.
61
COPY Command
When copying partitioned load modules to an unlike device, DFSMSdss uses

IEBCOPY with COPYMOD specified. This may result in a reblocked data set. When
copying to a like device, IEBCOPY with COPY specified is used.
DFSMSdss uses the DASDCALC macro to determine the optimal block size for the
target. The reblocking method used, DFSMSdss or DASDCALC, is presented to the
installation reblock exit.
RECATalog
RELBlockaddress
55
6dsn)
RELBlockaddress(
RELBLKA
RELBLOCKADDRESS identifies the direct access data sets whose names match
the fully or partially qualified names specified (dsn). These direct access data sets
are organized by relative block address instead of TTR and are to be copied block
by block. DFSMSdss updates the block reference count (the relative position of the
physical record as stored on its track) of dummy records. This keyword applies only
to direct access data sets with fixed record formats and without standard user
labels.
Note: If the data set is actually organized by TTR, the data set may become
unusable.
RENAMEUnconditional
55
RENAMEUnconditional(pfx)
RENUNC
,
(6(on,nn))
((pfx),6(on,nn))
RENAMEUNCONDITIONAL specifies that the data set must be copied with the new
name, regardless of whether the data set exists on DASD with the old name. If the
data set exists on the target volume with the new name, an allocation error occurs,
and the data set is not copied, regardless of whether the REPLACE keyword is
specified.
pfx
specifies the prefix used to replace the first-level qualifier of the data set name. It is
optional, but if specified, must be the first parameter in the list of subkeywords. The
prefix is used only if the (on,nn) parameters are not specified or the old name filters
do not match the data set name.
on
specifies the old name to be used as a filtering criterion to check if it matches the
data set name.
nn
specifies the new name to be used to derive the new data set name when the data
set name matches the corresponding old name filtering criterion.
62
COPY Command
The syntax rules for pfx (prefix), on (old name), and nn (new name) are the same
as in the RENAME keyword in a restore operation. See REName on page 156
under the RESTORE command for more information.
REPlace
55
REPlace
REPLACE specifies that DFSMSdss is to search the target volumes for usable
preallocated data sets. If no preallocated target is found, DFSMSdss attempts to
allocate a data set.
Notes:
1. If REPLACE is specified with the COPY command, the classes already
associated with the preallocated data set remain the same.
2. CATALOG and RECATALOG are ignored for preallocated data sets.
3. If the source data set is an extended-addressable VSAM KSDS, then the target
must also be an extended-addressable VSAM KSDS.
4. The target data set name must match the source data set name.
SELECTMulti
See the LOGINDDNAME and LOGINDYNAM keywords.
SHAre
55
SHAre
SHR
SHARE specifies that DFSMSdss is to share the data sets to be copied for read
access with other programs.
SHARE and FULL are mutually exclusive; you cannot specify these keywords
together.
Do not specify DELETE if you specify SHARE. You must have exclusive control
over data sets that are to be deleted; SHARE does not require such exclusive
control.
Note: The SHARE keyword is not honored for VSAM data sets. Exclusive control
is obtained for VSAM data sets even if the SHARE keyword is specified.
Neither read access nor write access by other programs is allowed while
the VSAM data set is being copied, regardless of the share options defined
for the data set.
SPHERE
55
SPHERE
SPHERE specifies that, for any VSAM cluster copied, all associated AIX clusters
and paths are to be copied. Individual names of sphere components do not need to
63
COPY Command
be specified. Only the base cluster name is required. If output volumes are
specified, the volumes on which the AIX clusters reside do not need to be
specified.
Note: The base cluster name must be specified to process the entire sphere. If
the sphere is specified but the base cluster name is not, DFSMSdss
processes only those components of the sphere whose names are
specified.
STORCLAS
55
NULLSTORCLAS
NSC
STORCLAS specifies the storage class that you want to replace the source storage
class as input to the ACS routines. You must have the proper RACF authorization
for the storage class specified. The keyword itself does not require authorization.
NULLSTORCLAS/NSC specifies that the input to the ACS routines is to be a null
storage class rather than the source data sets storage class.
STORCLAS and NULLSTORCLAS are mutually exclusive; you cannot specify both
keywords simultaneously. See Assignment of Class Names by Using the
RESTORE and COPY Commands on page 168 for information on assigning class
names using the copy function.
Note: If BYPASSACS(dsn) is specified, also all data sets that pass the
BYPASSACS selection criteria are guaranteed the specified storage class.
The combination of NULLSTORCLAS and BYPASSACS(dsn) forces the
selected data sets to be non-SMS-managed.
|
STORGRP
|
|
|
55
6groupname)
STORGRP(
|
|
|
|
|
STORGRP specifies that all of the online volumes in the storage group be
dynamically allocated. If a volume in the storage group is not online, that volume is
not used for processing. Up to 255 storage group names may be specified.
Specifying STORGRP with a storage group name is equivalent to specifying
LOGINDYNAM with all the online volumes in the storage group included in the list.
|
|
|
You can specify the STORGRP keyword with the SELECTMULTI keyword, but
STORGRP is mutually exclusive with the INDDname, INDYnam, LOGINDDname
and LOGINDYnam keywords.
TGTAlloc
64
COPY Command
TGTAlloc(SOURCE)
55
TGTAlloc(BLK)
CYL
TRK
SOURCE
SRC
TGTALLOC specifies how DFSMSdss is to allocate the target data set.

BLK
CYL
TRK
SOURCE/SRC
by blocks
by cylinders
by tracks
with the same space allocation type as that of the source data set
Notes:
1. If the TGTALLOC keyword is omitted, the target allocation defaults to
SOURCE.
2. If SRC is specified and if the source data set is allocated by track or if TRK is
specified, then the final VSAM allocation might be different from the requested
one because of VSAM allocation rules.
3. If BLK is specified for VSAM data sets, TRK is used instead. The final VSAM
allocation might be different from the requested one because of VSAM
allocation rules.
TGTGDS
55
TGTGDS(DEFERRED)
ACTIVE
ROLLEDOFF
SOURCE
SRC
TGTGDS specifies in what status, during a data set operation, that DFSMSdss is to
place nonpreallocated SMS-managed GDG data sets:
DEFERRED
specifies that the target data set is to be assigned the DEFERRED status.
ACTIVE
specifies that the target data set is to be assigned the ACTIVE status, for example,
rolled into the GDG base.
ROLLEDOFF
specifies that the target data set is to be assigned the rolled-off status.
SOURCE/SRC
specifies that the target data set is to be assigned the same status as that of the
source data set.
65
COPY Command
Notes:
1. If DELETE is specified without RENAMEUNCONDITIONAL and the source data
set is an SMS-managed generation data set, the TGTGDS keyword is ignored
and the source GDS status is copied to the target.
2. The requested target status of generation data sets must not violate generation
data group rules.
3. Refer to DFSMS/MVS DFSMSdss Storage Administration Guide for a
description of the default status when TGTGDS is not specified.
TOLerate
55
TOLerate(IOERror)
,ENQFailure
ENQFailure
,IOERror
TOLERATE specifies that DFSMSdss tolerates certain error conditions. For a copy
operation (except of a user catalog or loadlib) in which a utility performs the copy,
this keyword is ignored.
ENQFailure
specifies that source and target data sets are to be processed even though shared
or exclusive access fails.
Notes:
1. Unlike PDS data sets, PDSE data sets that are open for update cannot be
copied even if TOL(ENQF) is specified.
2. If you must copy a PDSE data set and it must be open for update, convert the
PDSE back to PDS and then copy the PDS data set with TOL(ENQF).
ENQF and FULL or TRACKS
are mutually exclusive; you cannot specify these keywords together.
For more information on TOL(ENQF), see Appendix B, Data
IntegritySerialization on page 241.
IOERROR
specifies that if the input volume can be opened, DFSMSdss is to continue copying
even though permanent input errors (busout parity and equipment checks only)
occur. DFSMSdss ends after 100 errors when this keyword is specified. The
default ends on permanent input errors. On a data set copy in which a utility
performs the copy, DFSMSdss ignores this keyword.
Notes:
1. TOL(IOERror) is ignored if CANcelerror is specified.
2. You cannot use the TOLERATE(ENQF) keyword when performing a logical
copy operation with VSAM extended-format data sets.
66
COPY Command
TRACKS
555%
,,c1,max head #
6
TRACKS((c1))
TRKS
,c1,max head #
,h1
,max head #
,c2
,h2
TRACKS specifies ranges of tracks to be copied (that is, a tracks copy). Refer to
DFSMS/MVS DFSMSdss Storage Administration Guide for additional information on
using TRACKS during physical processing.
c1,h1
specifies the cylinder and head number of the beginning of the range. Specify
hexadecimal numbers as X'c1' or X'h1'.
c2,h2
specifies the cylinder and head number of the end of the range. Specify
hexadecimal numbers as X'c2' or X'h2'. The c2 must be greater than or equal to
c1. If c2 equals c1, h2 must be greater than or equal to h1.
DFSMSdss verifies that the range is within the limits of the device. If you do not
specify all four values for a range, DFSMSdss provides the missing values unless
the omitted value causes a syntax error. No intervening values can be omitted. For
example:
Specified
Results
None
c1
c1,h1
c1,h1,c2
c1,,c2
,h1
Syntax error
c1,0,c1,maximum head number
c1,h1,c1,maximum head number
Syntax error
Syntax error
TTRAddress
55
6dsn)
TTRAddress(
TTRADDRESS identifies the direct access data sets whose names match the fully
or partially qualified names specified (dsn). These data sets are organized by TTR
rather than by relative block addressing and are to be processed track by track.
The target device track capacity must be equal to or greater than the source.
Notes:
1. If a direct access data set is specified by both the RELBLOCKADDRESS and
the TTRADDRESS parameters, the data set is not processed. Refer to the
RELBLOCKADDRESS keyword for more information.
AUTORELBLOCKADDRESS keyword processing for the specified data sets
(dsn).
67
COPY Command
UNCATalog
55
UNCATalog
UNCATALOG specifies that DFSMSdss is to uncatalog but not scratch successfully

copied non-VSAM data sets that are currently cataloged on the source volume. Any
non-SMS, non-VSAM data set that has a high-level qualifier of SYS1 cannot be
uncataloged unless PROCESS(SYS1) is specified. UNCATALOG is ignored for
VSAM data sets and SMS-managed non-VSAM data sets.
Note: Do not specify UNCATALOG with CONCURRENT, because after the
concurrent copy operation has begun, the original data can still be updated.
VOLcount
VOLcount(\)
55
VOLcount(SRC)
N(nn)
ANY
VOLCOUNT specifies the method DFSMSdss uses to determine the number of

volumes (volume count) for allocating the SMS target data set for a copy operation
of VSAM or non-VSAM data sets.
The character "*"
is the default and specifies that DFSMSdss determine the volume count for
If the source data set is a single-volume data set, one volume is allocated.
If the source data set is a multivolume data set and either a list of volumes is
not specified to DFSMSdss through OUTDDNAME or OUTDYNAM or there are
no SMS volumes in the list, DFSMSdss allocates the same number of volumes
that the multivolume source data set had.
If the source data set is a multivolume data set and a volume list is specified
through OUTDDNAME or OUTDYNAM, the volume count is the number of
SMS volumes in the list.
DFSMSdss does not adjust the final number of candidate volumes after the
allocation is complete.
SRC
specifies that DFSMSdss rely on the source volume count to determine the number
of volumes to allocate for the target data set as follows:
If no output volume list is specified, DFSMSdss allocates the same number of
volumes that the source data set had.
If a volume list is specified through OUTDDNAME or OUTDYNAM, the volumes
in the list that are SMS-managed must be in the same storage group, and the
allocation must be directed to that storage group.
68
COPY Command
N(nn)
nn represents the number of volumes to be used for SMS data set allocation. Any
value between 0 and 59 may be specified with the following conditions:
If nn is not zero and a volume list is specified through OUTDDNAME or
OUTDYNAM, DFSMSdss allocates either the number of SMS volumes in the
volume list or nn, whichever is less.
If nn is zero and a volume list is specified through OUTDDNAME or
volume list or the number of volumes that were allocated for the source data
set, whichever is less.
If a volume list is specified through OUTDDNAME or OUTDYNAM and there
are no SMS volumes in the list, or there is no volume list, DFSMSdss allocates
either the number of volumes used by the source data set or nn, whichever is
more.
ANY
specifies that DFSMSdss use a maximum volume count to allocate the SMS target
data set as follows:
DFSMSdss initially sets a volume count of 59 for the allocation.
If the data set is allocated on more volumes than were used to allocate the
source data set, DFSMSdss reduces the number of volumes used to the
number of primary volumes needed to satisfy the allocation.
If the data set is allocated on the same number or fewer volumes than were
used to allocate the source data set, DFSMSdss reduces the number of
volumes used to the number of volumes used for allocation of the source data
set.
Notes:
1. VOLCOUNT does not convert single-volume data sets whose organization is
partitioned into multivolume data sets. This includes PDS, PDSE, and HFS data
sets, single-volume data sets whose organization is undefined, and empty
non-VSAM single-volume data sets.
2. VOLCOUNT does not change the number of volumes for keyrange KSDS data
sets.
3. VOLCOUNT does not increase the number of volumes allocated for linear data
sets.
4. VOLCOUNT(ANY) does not support keyed VSAM data sets that have an
imbedded index. If VOLCOUNT(ANY) is specified and a data set has an
imbedded index, the data set is processed as if VOLCOUNT(*) were specified.
5. Guaranteed space is not honored when VOLCOUNT(ANY) is used.
6. VOLCOUNT(ANY) does not support any type of multi-striped data set (physical,
sequential, extended, or VSAM). If VOLCOUNT(ANY) is specified and a data
set is multi-striped, the data set is processed as if VOLCOUNT(*) were
specified.
You can override VOLCOUNT keyword settings with the options installation exit
routine, as described in DFSMS/MVS Installation Exits.
69
COPY Command
WAIT
WAIT(2,2)
55
WAIT specifies to DFSMSdss the length of the wait in seconds, and the number of
passes to be made through the list of selected data sets to obtain control of a data
set for COPY DATASET command.
numsecs
is a decimal number (0255) that specifies the interval, in seconds, to wait before
attempting another pass through the entire list of selected data sets.
numretries
is a decimal number (099) that specifies the number of passes to make through
the list of selected data sets in an attempt to obtain control of a data set.
The default for numsecs,numretries is (2,2), which specifies two retries at 2-second
intervals. If you do not want to wait for a resource, specify 0 for either numsecs or
numretries.
For a data set copy operation the WAIT keyword has a different meaning when: (1)
data sets are being serialized, (2) multiple data sets are being processed, and (3)
WAIT(0,0) is not specified. In this case, DFSMSdss makes multiple passes through
the list of data sets. On each pass, DFSMSdss processes the data sets that (1) can
be serialized without waiting for the resource and (2) were not processed before. At
the end of a pass, if none of the data sets can be processed without waiting for a
resource, then, in the next pass, at the first occurrence of a data set that was not
processed, a WAIT is issued. That data set and the remainder of the list are
processed if possible.
The above procedure is repeated until all data sets are processed or the WAIT
limits are reached. For example, if WAIT(3,10) is specified and five data sets are
left to be processed, up to ten passes are made. On each pass, an unprocessed
data set is waited upon for 3 seconds. Thus, only a 30-second maximum is ever
waited, not 150 (5 times 3 times 10).
system resources.
WRItecheck
55
WRItecheck
WRC
WRITECHECK specifies that the data copied is to be verified for successful

completion. This keyword increases the overall elapsed time.
70
COPY Command
Notes:
1. On a data set copy in which a utility performs the copy, DFSMSdss ignores this
keyword.
2. The WRITECHECK keyword is not supported for extended-sequential data
sets.
Data Integrity Considerations for Full or Tracks Copy Operation

For a full or tracks copy operation, DFSMSdss serializes the VTOC to preclude
DADSM functions (such as ALLOCATE, EXTEND, RENAME, and SCRATCH) from
changing the contents of the VTOC on the volume during the copy operation. Data
sets are not serialized on these full or tracks operations. Therefore, some data
sets might be opened by other jobs during the copy, resulting in copies of partially
updated data sets. You can minimize this possibility by performing the copy when
there is low system activity.
Full data integrity can only be guaranteed by performing copy operations by data
set when TOL(ENQF) or SHARE are not specified.
Examples of Full and Tracks Copy Operations

The following examples are for full and tracks copy operations.
Example 1:
//JOB1
JOB
//STEP1
EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=A
//DASD1
DD
//DASD2
DD
//SYSIN
DD
\
command input (see Examples 1A and 1B below)
/\
Example 1A: A Full Copy Operation

COPY
INDDNAME(DASD1) OUTDDNAME(DASD2) ALLDATA(\) ALLEXCP CANCELERROR
Example 1B: A Tracks Copy Operation

COPY
TRACKS(1,,1,15) INDDNAME(DASD1) OUTDDNAME(DASD2) CANCELERROR
The data from DASD volume 111111 is to be copied to DASD volume 222222. For
the full copy operation, all allocated space in sequential or partitioned data sets and
data sets with a data set organization that is null is copied (ALLDATA(*)). The
preceding applies only to data sets that are not empty. For data sets that are
empty, DFSMSdss copies all data within the allocated space (ALLEXCP). The copy
operation is to be ended if a permanent read error occurs (CANCELERROR).
71
COPY Command
Example 2: A Tracks Copy with Track Relocation

//JOB2
//STEP1
EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=A
//SYSIN
DD
\
COPY TRACKS(1,,1,14) /\ SOURCE TRACKS \/ OUTTRACKS(3,)
/\ TARGET TRACKS \/ INDYNAM(338)
/\ ALLOC VOL 338 DYNAMICALLY \/ OUTDYNAM(3381)
/\ ALLOC VOL 3381 DYNAMICALLY \/ CANCELERROR
/\ STOP ON INPUT ERROR
\/ WRITECHECK
/\ VERIFY DATA WRITTEN TO OUT VOL \/
/\
The following example shows a tracks copy operation in which the contents of
cylinder 1, tracks 0 through 14, on source volume 338000 are copied to cylinder 3,
tracks 0 through 14, on target volume 338001. The operation stops if a permanent
error occurs on the source volume (CANCELERROR). The data written to the
target volume is to be verified (WRITECHECK).
Examples of Data Set Copy Operations

The following examples are for data set copy operations.
Example 1: A Data Set MoveOnly Single Volume Data Sets

//JOB3
//STEP1
EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=A
//SYSIN
DD
\
COPY data set(
INCLUDE(USER1.\\)
/\ FILTER ON DS W/1ST LEV Q USER1
BY(MULTI,=,NO))
/\ FILTER ON SINGLE VOLUME
INDYNAM (338)
/\ ALLOC VOL 338 DYNAMICALLY
OUTDYNAM(3381)
DELETE
/\
\/
\/
\/
\/
The following example shows a data set copy operation in which all single-volume
data sets with the first-level qualifier USER1 on the source volume labeled 338000
are copied to the target volume labeled 338001. All source data sets that are
selected are deleted. The copied non-SMS, non-VSAM data sets are not cataloged.
Example 2: A Data Set Copy to Move Data Sets to a Single

VolumeDevice Conversion
//JOB4
//STEP1
EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=A
//SYSIN
DD
\
COPY data set(
INCLUDE(USER1.\\)) /\ FILTER ON DS W/1ST LEV Q USER1
OUTDYNAM(3381)
DELETE CATALOG FORCE TGTALLOC(SOURCE)
/\
\/ \/ -
The following example shows a data set copy in which all cataloged data sets with
a first-level qualifier of USER1 (USER1.**) data sets are to be consolidated on a
72
COPY Command
single target volume labeled 338001. The data sets can be scattered on multiple
source volumes. The target volume can be of unlike device type to any of the
volumes on which the source data sets reside. A few of the data sets might already
be on volume 338001. The data sets are to be cataloged (CATALOG) in the
standard order of search. The expired source data sets are scratched and
uncataloged (DELETE) after successfully moving them to volume 338001, where
they have the same allocation type (BLK, TRK, or CYL) that they had on the source
volumes. FORCE is specified to include unmovable data sets.
Example 3: A Data Set Copy of a Multivolume Data Set

//JOB5
//STEP1
EXEC PGM=ADRDSSU
//IVOL1
DD
UNIT=(SYSDA,2),VOL=SER=(VOL111,VOL222),DISP=SHR
//IVOL2
DD
UNIT=SYSDA,VOL=SER=VOL222,DISP=SHR
//SYSPRINT DD
SYSOUT=A
//SYSIN
DD
\
COPY data set(
INC(USER.MULTI.VOLUME1)) /\ SELECT THIS DATA SET
\/ INDD(IVOL1,IVOL2)
/\ IDENTIFY INPUT VOLUMES
\/ OUTDYNAM((3381),(3382),(3383)) /\ DYNAM ALLOC VOLS \/ PCTU(8,8,8)
/\ PERCENTUTIL = 8 PERCENT \/ RECATALOG(USERCAT2)
/\
The following example shows a data set copy in which a multivolume data set is
copied to a set of target volumes labeled 338001, 338002, and 338003. The source
data set is not deleted. The copied data set is cataloged in a new catalog,
USERCAT2. The data set currently exists on multiple source volumes. Multiple
output volumes are specified for overflow purposes. However, the output cannot be
on more volumes than the source data set. These target volumes may already
have some data sets on them. Some space is left on these volumes to allow
expansion of the data sets (PCTU) remaining on the volumes.
|
|
|
|
|
Change the example as shown below to include SELECTMULTI processing on

missing volumes. The INCLUDE keyword is changed to select all data sets on input
volumes VOL111 and VOL222. SELECTMULTI(ANY) specifies that a cataloged
data set residing on volumes VOL111, VOL444, and VOL555 is copied even
though VOL444 and VOL555 are omitted from the LOGINDD volume list.
COPY data set(
INC(\\))
/\ SELECT ALL DATA SETS
\/ LOGINDD(IVOL1,IVOL2)
/\ IDENTIFY INPUT VOLUMES
\/ OUTDYNAM((3381),(3382),(3383)) /\ DYNAM ALLOC VOLS \/ SELECTMULTI(ANY)
/\ PROCESS MISSING VOLUMES \/ PCTU(8,8,8)
/\ PERCENTUTIL = 8 PERCENT \/ RECATALOG(USERCAT2)
Example 4: A Data Set Copy with DELETE and RENAMEU

Options
73
COPY Command
//JOB6
//STEP1
EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=A
//SYSIN
DD
\
COPY data set(
INCLUDE(USER1.\\)) /\ FILTER ON DS W/1ST LEV Q USER1 \/ OUTDYNAM((3381),(3382),(3383)) /\ DYNAM ALLOC VOLS \/ DELETE
RENAMEU(USER2)
RECATALOG(USERCAT2)
/\
The following example shows a data set copy operation in which all data sets with
the high-level qualifier USER1 that are in the standard order of search are copied
to the target volumes labeled 338001, 338002, and 338003. The copied data sets
are renamed (RENAMEU) to the high-level qualifier USER2, followed by the second
through last qualifiers of the old names. If data sets with the same name as the
new names are on the target volumes or if they are already cataloged in
USERCAT2, they are not copied. The copied, expired data sets are deleted
(DELETE) from the source volumes, uncataloged, and cataloged (RECATALOG) in
the catalog USERCAT2. This provides for the movement of data sets from one set
of volumes to another set of volumes and from one catalog to another catalog, and
for the renaming of the data sets.
Example 5: A Data Set Copy With REBLOCK Option

//JOB7
//STEP1
//SYSPRINT DD
SYSOUT=A
//DISK
DD
UNIT=338,VOL=(PRIVATE,,,,SER=3381),DISP=SHR
//DISK2
DD
UNIT=339,VOL=(PRIVATE,,,,SER=3391),DISP=SHR
//SYSIN
DD
\
COPY data set(
INCLUDE(\\) )
/\ INCLUDE ALL DATA SETS \/ INDDNAME(DISK)
/\ INPUT VOLUME
\/ OUTDDNAME(DISK2)
/\ OUTPUT VOLUME
\/ REBLOCK(\\.USER1.\\)
/\
The following example shows a data set copy in which all data sets on the 3380
source volume labeled 338001 are copied to the 3390 target volume labeled
339001. If data sets with the same name are on the target volume, they are not
copied. The sequential and partitioned data sets that meet the filtering criteria
specified in the REBLOCK keyword are reblocked on the target volume. The block
size is selected by DFSMSdss, unless it is modified by the user reblock exit routine.
Example 6: A Data Set Copy to a Preallocated Target Data Set
74
COPY Command
//JOB8
//STEP1
EXEC PGM=ADRDSSU
//STEPCAT
DD
DSN=USERCAT,DISP=SHR
//SYSPRINT DD
SYSOUT=A
//DASD1
DD
//DASD2
DD
//SYSIN
DD
\
COPY data set(
INCLUDE(USER.TEST.DATA) ) INDDNAME(DASD1) OUTDDNAME(DASD2) REPLACE DELETE
/\
The following example shows a data set copy in which a source data set
(USER.TEST.DATA) allocated on volume 111111 and cataloged in catalog
USERCAT is copied to a preallocated target data set (with the same name as the
source) on volume 222222. The REPLACE keyword specifies that DFSMSdss is to
search the target volume for a usable preallocated data set. The data set is deleted
(DELETE) from the source volume if it is expired.
Example 7: Using the COPY Command to Convert to SMS

//JOB9
//STEP1
EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=\
//SYSIN
DD
\
COPY DS(INC(\\)) LOGINDYNAM ( (3381) (3382) ) STORCLAS(DB2PERF) MGMTCLAS(DBBACKUP) BYPASSACS(\\) DELETE PURGE
/\
In the first step of this example, all of the data sets on the non-SMS-managed
volumes 338001 and 338002 are copied to SMS-managed volumes on the system.
DELETE and PURGE are used to avoid duplicate catalog entries. The ACS
routines are not invoked to determine the target data set classes for this copy
operation. The storage and management classes are provided by the users using
the STORCLAS and MGMTCLAS keywords. In addition, BYPASSACS(**) is
specified in order to suppress calls made to the ACS routines. All data sets that are
supported by SMS are given the new storage and management classes. All data
sets that cannot be SMS-managed (for example, ISAM) are not copied.
75
COPY Command
//JOB1
//STEP1
EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=\
//SYSIN
DD
\
COPY DS(INC(\\)) LOGINDYNAM ( (3381) (3382) ) RENUNC(AUG387)
/\
In this next step all data sets on the non-SMS-managed volumes 338001 and
338002 are copied to SMS-managed volumes on the system. The RENUNC
command is used to avoid duplicate catalog entries. The ACS routines select a
target storage and management class for each data set. Those data sets that
cannot be SMS-managed (storage class ACS routine returns a null storage class)
are not copied because no output volume is specified. Each data set that is copied
is given a new high-level qualifier (AUG0387) and automatically cataloged.
Example 8: A Data Set Copy Using CONVERT PDSE

//JOB2
//STEP1
EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=\
//SYSIN
DD
\
COPY DS(INC(USER.PDS.\\)) LOGINDYNAM ( (3381) (3382) ) CONVERT (PDSE(\\)) RENUNC (USER.PDS.\\, USER.PDSE.\\)
/\
In this step all data sets with the first two qualifiers of USER.PDS on
non-SMS-managed volumes 338001 and 338002 are copied to SMS-managed
volumes on the system. CONVERT PDSE is used to convert data sets to PDSE.
The RENUNC keyword is used to avoid duplicate catalog entries. The ACS routines
select a target storage and management class for each data set. Each data set that
is copied and converted is given a new secondary qualifier (PDSE) and
automatically cataloged.
Example 9: A Data Set Copy with CONCURRENT

//DSSJOB JOB accounting information,REGION=nnnnK
//COPYSTEP EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=\
//SYSIN
DD
\
COPY dataset(INCLUDE(USER.LOG,USER.TABLE,USER.XREF)) OUTDYNAME(OVOL1,OVOL2,OVOL3,OVOL8) ALLDATA(\) ALLEXCP CONCURRENT STORCLAS(BACKUP) RENAMEUNCONDITIONAL(USERX)
/\
76
This JCL does a DFSMSdss logical data set copy using the concurrent copy
feature. This job continues (with a warning message) if concurrent copy initialization
fails.
ALLDATA and ALLEXCP Interactions

Table 2 on page 78 and Table 3 on page 79 describe the functions of the
ALLDATA and ALLEXCP keywords during a data set copy to LIKE and UNLIKE
devices, respectively.
77
Table 2. ALLDATA and ALLEXCP Interactions When Copying to LIKE Device. Read the first eleven columns to
find the row that matches your situation. Read the last column to find what DFSMSdss does.
Y
Y
DFSMSdss action is:
REBLOCK used?
NOPACKING used?
ALLEXCP used?
ALLDATA (dsn) used?
ALLDATA (*) used?
Load module?
Partitioned data set? (b)
Sequential data set? (a)
Undefined DSORG?
Empty data set?
EOF as first record?
Yes
No
Either
Not Applicable
Allocate and copy all the allocated space
Allocate and copy only the used space
Allocate and copy only one track
Allocate all the allocated space, and copy only the used space
Allocate all the allocated space, and copy only one track
Do not process the data set
Y
N
X
1
2
3
4
5
6
Notes:
(a) When ALLDATA or ALLEXCP is specified for an extended-sequential data set, data beyond the last used block
pointer is not retained. The target data set is allocated with the same amount of space as the source data set during
a logical restore or copy operation.
(b) Partitioned data sets that have directories (whether or not there are empty members in the directory) are treated
as not empty.
78
Table 3. ALLDATA and ALLEXCP Interactions When Copying to UNLIKE Device. Read the first twelve columns
to find the row that matches your situation. Read the last column to determine what DFSMSdss does.
DFSMSdss action is:
ALLDATA (dsn) used?
ALLEXCP used?
PROCESS (UNDEF)
used?
Load module?
Empty data set?
Target tracksize >

source?
ALLDATA (*) used?
Partitioned data set? (b)
Sequential data set? (a)
Undefined DSORG?
EOF as first record?
BLKSIZE=0 data set?
Yes
No
Either
Not Applicable
Allocate the same number of tracks as the source, and make a track image copy.
Allocate and copy only the used space
Allocate and copy only one track
Allocate all the allocated space, and copy only the used space
Allocate all the allocated space, and copy only one track
Do not process the data set
Y
N
X
1
2
3
4
5
6
Notes:
(a) When ALLDATA or ALLEXCP is specified for an extended-sequential data set, data beyond the last used block
pointer is not retained. The target data set is allocated with the same amount of space as the source data set during
a logical restore or copy operation.
(b) Partitioned data sets that have directories (whether or not there are empty members in the directory) are treated
as not empty.
79
COPYDUMP Command
COPYDUMP Command
With the COPYDUMP command, you can make from 1 to 255 copies of
DFSMSdss-produced dump data. The data to be copied, a sequential data set, can
be on a tape or a DASD volume, and copies can be written to a tape or a DASD
volume. If the dump data is produced from multiple DASD volumes by using a
physical data set dump operation, you can selectively copy the data from one or
more of those volumes.
The COPYDUMP command cannot change the block size of the DFSMSdss dump
data set. If you are copying a dump data set to a DASD device, the source block
size must be small enough to fit on the target device.
Note: Extra dump tapes can be used for such things as disaster recovery backup
or distribution of dumped data (for example, a newly generated system).
COPYDUMP Syntax
,
5COPYDumpINDDname(ddn)OUTDDname(6ddn)5
CPYD IDD
ODD
LOGicalvolume(6volser)
LVOL
Explanation of COPYDUMP Command Keywords

This section describes the keywords for the COPYDUMP command.
INDDname
5INDDname(ddn)5
IDD
ddn
specifies the name of the DD statement that identifies the sequential data set to be
copied. This data set can reside on one or more tapes, or on DASD volumes.
LOGicalvolume
55
6volser)
LOGicalvolume(
LVOL
volser
specifies the source DASD volume serial number from which dumped data is to be
copied. Omission of the LOGICALVOLUME keyword causes DFSMSdss to copy
data from all logical volumes in the dump data set. This keyword is useful only if
the data being copied was created by a physical data set dump operation from
multiple DASD volumes. When copying a logical dump, LOGICALVOLUME is
ignored.
80
COPYDUMP Command
OUTDDname
,
6ddn)5
5OUTDDname(
ODD
ddn
specifies the name of the DD statement that identifies the output sequential data
set. This data set can be on a tape or a DASD volume.
Examples of COPYDUMP Operations

The following are examples of the COPYDUMP command.
Example 1: Making Two Copies of a Dump

//JOB1
JOB
//STEP1
EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=A
//BACKUP
DD
UNIT=348,VOL=SER=TAPE5,DISP=OLD,
// DSNAME=V111111.BACKUP
//COPY1
DD
// DISP=(NEW,CATLG),DSNAME=V111111.BACKUP1
//COPY2
DD
// DISP=(NEW,CATLG),DSNAME=V111111.BACKUP2
//SYSIN
DD
\
COPYDUMP INDD(BACKUP) OUTDD(COPY1,COPY2)
/\
In this example, two copies are to be made from a DFSMSdss dump tape
(OUTDD(COPY1,COPY2)).
Example 2: Copying a Dump Created by Using Physical Data

Set Processing
//JOB2
JOB
//STEP1
EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=A
//TAPE2
DD
// LABEL=(1,SL),DISP=(OLD,KEEP),DSN=USER.BACKUP.REL3A
//OUTT2
DD
// LABEL=(1,SL),DISP=(NEW,CATLG),DSN=USER.BACKUP.REL3A.A
//SYSIN
DD
\
COPYDUMP INDD(TAPE2)
/\ DUMP TAPE TO BE COPIED
\/ OUTDD(OUTT2)
/\ NEW DUMP TAPE
\/ LVOL(3381)
/\ SER NO OF VOL TO BE COPIED \/
/\
Assume that a physical data set dump operation was used to create a dump tape,
volume TAPE20. Also assume that source DASD volumes 338000, 338001, and so
on were specified, resulting in VTOCs being used for data set selection. Only the
dump data from DASD volume 338001 is to be copied (LVOL(338001)).
81
DEFRAG Command
Example 3: Copying a Dump Created by Using Logical Data Set

Processing
//JOB3
JOB
//STEP1
EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=A
//TAPE3
DD
// LABEL=(1,SL),DISP=(OLD,KEEP),DSN=USER.BACKUP.REL3B
//OUTT3
DD
// LABEL=(1,SL),DISP=(NEW,CATLG),DSN=USER.BACKUP.REL3B.A
//SYSIN
DD
\
COPYDUMP INDD(TAPE3)
/\ DUMP TAPE TO BE COPIED
\/ OUTDD(OUTT3)
/\ NEW DUMP TAPE
\/
/\
Assume that a logical data set dump operation was used to create a dump tape,
volume TAPE30. All dump data is copied.
DEFRAG Command
With the DEFRAG command, you can relocate data set extents on a DASD volume
to reduce or eliminate free-space fragmentation and print a report about free space
and other volume statistics. Also, you can specify which data sets, if any, are to be
excluded from data-set-extent relocation.
DEFRAG Syntax
55DEFragDDName(ddn)5
DYNAM(volser) ADMINistrator
,unit
55
,
DYNALloc
6
6
BY(LISt((shar,op,((arg)))))
(DDName(ddn))
55
,
FORCECP(days) FRAGMENTATIONIndex(n)
EXClude(LISt(6dsn))
FRAGI
(DDName(ddn))
55
,1
PASSDelay(999) PASsword(ddn)
MAXmove(n)
PSWD
,
,p
PASSDelay(nnnn)
6dsn/pswd
WAIT(2,2)
55%
WAIT(numsecs,numretries) WRITECHECK
WRC
Explanation of DEFRAG Command Keywords

This section describes the keywords for the DEFRAG command.
ADMINistrator
55
ADMINistrator

for the DEFRAG command. If you are not authorized to use the ADMINISTRATOR
82
DEFRAG Command

BY
55
6
6
BY(LISt((shar,op,((arg)))))
(DDName(ddn))
BY specifies data set filtering criteria.
DDName(ddn)
specifies the name of the DD statement that identifies a sequential data set or
BY keywords described below.
LIST((schar,op,((arg))))
specifies data set filtering. To select the data set for inclusion in the DEFRAG
operation, all BY criteria must be met. See Filtering by Data Set Characteristics
on page 14 for a full discussion of schar, op, and arg.
DDName
5DDName(ddn)5
ddn
specifies the name of the DD statement that describes the volume to be processed.
DYNALloc
55
DYNALloc

of data sets. The data sets whose extents are to be relocated are serialized
throughout the DEFRAG operation. This allows cross-system serialization in a
Consider:
not disabled.
Run time increases when you use the DYNALLOC keyword to serialize data
sets (as opposed to enqueue) because overhead is involved in dynamic
allocation and serialization across multiple processors.
83
DEFRAG Command
DYNAM
55
DYNAM(volser)
,unit
DYNAM specifies that the volume to be processed is to be dynamically allocated.

serial number using an asterisk (*).
Using the DYNAM keyword instead of DD statements to allocate DASD volumes
does not appreciably increase run time and permits easier coding of JCL and
command input.
volser
unit
optional.
EXClude
55
6dsn))
EXClude(LISt(
(DDName(ddn))
dsn
specifies a fully or partially qualified name of a data set to be excluded from the
DEFRAG operation. You can specify either a cluster or component name for VSAM
data sets.
ddn
specifies the name of the DD statement that identifies a sequential data set or
member of a partitioned data set, which contains the list of data sets to be
excluded.
For a list of data sets to be placed in the EXCLUDE list if they are present on the
volume being defragmented, refer to the DFSMS/MVS DFSMSdss Storage
Administration Guide.
FORCECP
55
FORCECP(days)
FORCECP specifies that extents of checkpointed data sets resident on the SMS
volume or volumes can be moved. The checkpoint indication is left in place for IMS
GSAM data sets, as the data set is still usable for a restart. The checkpoint
indication is removed from all volumes for MVS checkpointed data sets, as the data
sets are no longer usable for a restart.
days
is a one-to three-digit number in the range of zero to 255, and specifies the
data set can be defragmented.
84
DEFRAG Command
FRAGMENTATIONIndex
55
FRAGMENTATIONIndex(n)
FRAGI
FRAGMENTATIONINDEX specifies that the DEFRAG operation is to end if the

fragmentation index is less than n, where n is a 1- to 3-digit number. DFSMSdss
prefixes your number, n, with a decimal point. For example, 1 becomes .1, 999
becomes .999, 001 becomes .001, and so forth. For more information, refer to
DFSMS/MVS DFSMSdss Storage Administration Guide.
MAXmove
55
,1
PASSDelay(999)
MAXmove(n)
,p
PASSDelay(nnnn)
n
is a 1- to 6-digit number that specifies that DFSMSdss is to attempt to assemble up
to n free tracks in a contiguous area. If n is greater than the total number of free
tracks on the volume, for example MAXMOVE(999999), a message is issued and
the DEFRAG operation adjusts n to the number of free tracks.
p
is a 1- to 2-digit number that specifies that DFSMSdss is to make up to p passes in
attempting to assemble the tracks. If p is not specified, for example MAXMOVE(99),
only one pass is made, that is, MAXMOVE(99,1).
PASSDelay
specifies the time delay between the passes (p) specified in MAXMOVE (n,p).
PASSDELAY is only meaningful if (p) is greater than one.
nnnn
is a 1- to 4-digit number from 0 to 9999 that specifies the time delay in milliseconds
(1/1000 of a second). When MAXMOVE (n,p) is specified and PASSDELAY is not
specified, a default PASSDELAY value of 999 (almost a second) is used to allow
access to the volume between MAXMOVE passes.
DEFRAG processing attempts to move a fraction of the total free tracks during
each pass. DEFRAG processing calculates an integer limit that is the larger of n
divided by p or the value of 15. After each extent is moved, the limit is compared
with the cumulative number of tracks moved thus far during the pass, and if the
limit is reached or exceeded, the current pass is ended and a new pass is started.
Between each pass, the DEFRAG function releases and reobtains volume
serialization. This action reduces the overall time that a volume is made unavailable
to other applications by a DEFRAG operation.
The DEFRAG operation may end before completing p passes. If the DEFRAG
operation cannot assemble n contiguous free tracks without moving more than n
tracks, DFSMSdss issues a message and ends the DEFRAG operation. If n
contiguous free tracks exist, the DEFRAG operation still attempts to reduce the
fragmentation of the volume if it can do so without relocating more than n tracks.
85
DEFRAG Command
The operation or the current pass is also ended when DEFRAG processing criteria
(for example, FRAGI) is met. If more than one pass has been specified, only the
current pass is ended and message ADR233W is issued for the current pass when
the FRAGI criteria has been met. The DEFRAG function continues to run and
attempts to complete the specified number of passes; therefore, message
ADR233W is issued for each pass that has the FRAGI criteria met. The function
continues to run because activity on the volume between the DEFRAG passes may
change the fragmentation index and the subsequent DEFRAG passes may be able
to further reduce the fragmentation of the volume.
In order to reobtain volume serialization between DEFRAG passes, DFSMSdss
uses a default value of WAIT(3,30). This means that DFSMSdss is to retry the
volume serialization 30 times at 3 second intervals for a total wait time of 90
seconds. The DEFRAG operation issues a message and ends if volume
serialization cannot be obtained; any remaining passes are not run. The WAIT
Option on page 243 explains how to change the wait/retry values for the volume
serialization if the default is not satisfactory.
If MAXMOVE is not specified, DFSMSdss tries to assemble a contiguous free area
of a size equal to the total number of free tracks on the volume in a single pass.
The DEFRAG function uses two methods to assemble free tracks on the volume.
The first method attempts to assemble the largest contiguous amount of free space
with a minimum amount of data movement. The second method attempts to
assemble multiple groups of large areas of contiguous free space and generally
moves more data around than the first method. When MAXMOVE is specified, only
the first method is used during each pass.
PASSDelay
See the MAXMOVE keyword.
PASsword
55
PASsword(ddn)
PSWD
,
6dsn/pswd
PASSWORD specifies the passwords DFSMSdss is to use for password-protected

data sets. (Password checking is bypassed for RACF-protected data sets.) This
keyword must be specified only if:
You do not have the required RACF DASDVOL or RACF DATASET access.
authorization exit.
For VSAM data sets, password checking is done only at the cluster level.
ddn
86
DEFRAG Command
format.
dsn/pswd
Printing of actual data set passwords specified in the input command stream is
WAIT
WAIT(2,2)
55
numsecs
is a decimal number from 1 to 255 that specifies the interval, in seconds, between
retries.
numretries
control of a data set is to be retried.
intervals. If you do not want to wait for a data set, specify 0 for either numsecs or
numretries.
in a total wait time of 90 seconds. Refer to the DFSMS/MVS DFSMSdss
system resources.
WRITECHECK
55
WRItecheck
WRC
WRITECHECK specifies that the data moved by the DEFRAG operation is to be

verified for successful completion. This keyword increases the overall elapsed time.
Examples of DEFRAG Operations

Example 1: A DEFRAG Operation with Excluded Data Sets
87
DEFRAG Command
//JOB1
JOB
//STEP1
EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=A
//DASD
DD
//A1
DD
DSN=USER2.EXCLUDE,DISP=SHR
//SYSIN
DD
\
command input (see examples 1A and 1B below)
/\
Example 1A: With the Names of Excluded Data Sets in the Input
Stream
DEFRAG
DDNAME(DASD) EXCLUDE(LIST(USER2.\\.LIST,\.LOAD))
Example 1B: With the Names of Excluded Data Sets in a Data

Set
DEFRAG
DDNAME(DASD) EXCLUDE(DDNAME(A1))
In examples 1A and 1B, DASD volume 111111 is defragmented. All data sets
whose first and last qualifiers are USER2 and LIST, respectively, are to be
excluded from this operation, as are data sets with two qualifiers whose second
qualifier is LOAD. In example 1B, cataloged data set USER2.EXCLUDE contains a
single card-image record with the following in columns 2 through 72:
USER2.\\.LIST,\.LOAD
Example 2: A DEFRAG Operation Using a BY Criterion

//JOB2
JOB
//STEP1
EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=A
//DASD
DD
//SYSIN
DD
\
DEFRAG DDNAME(DASD)
/\ VOLUME TO BE PROCESSED
\/ BY(LIST(REFDT LT \,-1)) /\ DATE LAST REF LT RUN DATE -1 \/
/\
Only data sets last referenced more than one day before the run date are included
in this DEFRAG operation. That is, those that were last referenced one day before
or on the run date are excluded.
Results of a Successful DEFRAG Operation

Figure 1 on page 89 is the printout from a DEFRAG run for a DASD volume. It
gives an indication of the free space fragmentation before and after a DEFRAG
operation, as well as the distribution of data set extents by size.
The following JCL was used for this job:
//DSSJOB
//DEFRAG EXEC PGM=ADRDSSU,PARM='TRACE=YES'
//SYSPRINT DD SYSOUT=\
//SYSIN
DD \
DEFRAG DYNAM(D9S6)
/\
88
DUMP Command
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
PAGE 1
5695-DF175
DEFRAG
DYNAM(D9S6)
ADR11I (R/I)-RI1 (1),
ADR19I (R/I)-RI1 (1),
ADR16I (1)-PRIME(1),
ADR6I (1)-STEND(1),
ADR28I (1)-EANAL(1),
ADR29I (1)-EFRAG(1),
PAGE 2
5695-DF175
ADR6I (1)-STEND(2),
ADR13I (1)-CLTSK(1),
ADR12I (SCH)-DSSU (1),
DFSMSDSS V1R5.
DATA SET SERVICES
1998.293 15:28
TASKID 1 HAS BEEN ASSIGNED TO COMMAND 'DEFRAG '

1998.293 15:28:21 INITIAL SCAN OF USER CONTROL STATEMENTS COMPLETED.
RACF LOGGING OPTION IN EFFECT FOR THIS TASK
1998.293 15:28:22 EXECUTION BEGINS
1998.293 15:28:22 BEGINNING STATISTICS ON D9S6:
FREE CYLINDERS
58
FREE TRACKS
3
FREE EXTENTS
2
LARGEST FREE EXTENT (CYL,TRK) 53,3
FRAGMENTATION INDEX
.5
PERCENT FREE SPACE
97
INTERVAL BEGINS AT CC:HH 1: AND ENDS AT CC:HH 6:C
1998.293 15:28:23 MOVED EXTENT 1 FROM 6:-6:4 TO 1:-1:4
PUBSEXMP.ESDS.S1.DATA
1998.293 15:28:23 MOVED EXTENT 1 FROM 6:5-6:6 TO 1:5-1:6
PUBSEXMP.KSDS.S1.DATA
1998.293 15:28:23 MOVED EXTENT 1 FROM 6:7-6:8 TO 1:7-1:8
PUBSEXMP.SAM.S1
1998.293 15:28:23 MOVED EXTENT 1 FROM 6:9-6:A TO 1:9-1:A
PUBSEXMP.PDS.S1
1998.293 15:28:23 MOVED EXTENT 2 FROM 6:B-6:B TO 1:B-1:B
PUBSEXMP.PDS.S1
1998.293 15:28:23 ENDING STATISTICS ON D9S6:
DATA SET EXTENTS RELOCATED
5
TRACKS RELOCATED
12
FREE CYLINDERS
58
FREE TRACKS
3
FREE EXTENTS
1
FRAGMENTATION INDEX
.
DFSMSDSS V1R5. DATA SET SERVICES
1998.293 15:28
EXTENT DISTRIBUTION MAP FOR D9S6:
EXTENT
\FREE SPACE BEFORE\ \FREE SPACE AFTER\
\ ALLOCATED \
SIZE
IN
NO.
CUM.
NO.
CUM.
NO.
CUM.
TRACKS
EXTS PCT/1
EXTS PCT/1
EXTS PCT/1
1
4
.148
2
4
.444
5
1
.629
1
1
1.
75
1
.85
>499
1
1.
1
1.
1998.293 15:28:23 EXECUTION ENDS
1998.293 15:28:23 TASK COMPLETED WITH RETURN CODE
1998.293 15:28:23 DFSMSDSS PROCESSING COMPLETE. HIGHEST RETURN CODE IS
FOR
FOR
FOR
FOR
FOR
Figure 1. Printed Output Resulting from a Successful DEFRAG Run
The value in the first column of message ADR212I is the size of the extent in tracks
(free space or data set) and is printed only if an extent of that size occurs. The
second and third columns show the number of free space extents existing before
processing that were of the size shown in the first column, along with their
cumulative percentage divided by 100. The fourth and fifth columns give the same
information for free space, but after processing. The sixth and seventh columns
give the distribution of allocated data set extents, which do not change during a
run.
DUMP Command
With the DUMP command, you can dump DASD data to a sequential data set. The
storage medium for the sequential data set can be a tape or DASD. You can dump
data sets, an entire volume, or ranges of tracks.
Note: The FULL keyword for the DUMP command specifies that an entire DASD
volume is to be dumped. The TRACKS keyword with the DUMP command
specifies ranges of tracks to be dumped.
89
DFSMSdss offers two ways to process DUMP commands:

sets independently of physical device format.
Physical processing can operate against data sets, volumes, and tracks, but is
oriented toward moving data at the track-image level.
The processing method is determined by the keywords specified on the command.
DFSMSdss logical dump processing cannot be used to process partitioned data
sets containing location-dependent information that does not reside in note lists or
in the directory. Furthermore, DFSMSdss cannot be used to dump migrated data
sets.
Integrated catalog facility catalogs should not have a high-level qualifier of
SYSCTLG because this causes DFSMSdss to treat them as CVOLs.
For information on using the DUMP command, refer to DFSMS/MVS DFSMSdss
Storage Administration Guide .
Special Considerations for Dump

The following special considerations apply when you are performing a dump
operation:
Extended-format VSAM data sets are not supported for physical data set
processing.
You cannot do a physical data set dump of a KSDS with keyranges.
DUMP FULL and DUMP TRACKS Syntax

55DUMpFULl5
,,c1,max head #
6
TRACKS((c1))
TRKS
,c1,max head #
B
,h1
,max head #
,c2
,h2
,
5INDDname(ddn)OUTDDname(6ddn)5%
IDD
ODD
INDYnam(volser)
IDY
,unit
A: Optional Keywords with DUMP FULL

55
ADMINistrator
,
ALLExcp CANcelerror CHECKvtoc COMpress
ALLData(6dsn) ALLX
ALLData(\)
OPTimize(1)
READIOPacing()
55
CONCurrent OPTimize(n) PASsword(ddn) READIOPacing(nnn)
CC
PSWD ,
RIOP
6dsn/pswd
55
RESEt TOLerate(IOERror)
B: Optional Keywords with DUMP TRACKS

90
55
ADMINistrator CANcelerror CHECKvtoc COMpress CONCurrent CPVOLume
CC
OPTimize(1)
READIOPacing()
55
OPTimize(n) PASsword(ddn) READIOPacing(nnn)
PSWD
,
RIOP
6dsn/pswd
55
TOLerate(IOERror)
DUMP DATASET Syntax for Logical Data Set

,
55DUMpDATASet( C )OUTDDname(6ddn)5%
DS
FILterdd(ddn)
D ODD
FDD
C: Additional Keywords with DUMP DATASET for Logical Data Set

,
INClude(\\)
,

,

,
INClude(\\)
EXClude(6dsn)
,

,

INClude(6dsn)

6
6
6
INClude(dsn)
,

,
EXClude(6dsn)
6
6
D: Optional Keywords with DUMP DATASET for Logical Data Set
91
55
ADMINistrator
,
ALLExcp CANcelerror CHECKvtoc COMpress
ALLData(6dsn) ALLX
ALLData(\)
55
CONCurrent DELete DYNALloc FORCECP(days)
CC NOTIFYCONCurrent
NOTIFYCC
55
INCAT(6catname)
ONLYINCAT
55
,
SELECTMulti(ALL)
LOGINDDname(6ddn)
LIDD
SELECTMulti(ALL)
SELM
ANY
6
LOGINDYnam((volser))
FIRST
LIDY
,unit
OPTimize(1)
55
OPTimize(n) PASsword(ddn) PROCESS(SYS1) PURge
PSWD
,
PRG
6dsn/pswd
|
|
READIOPacing()
55
READIOPacing(nnn) RESEt SHAre SPHERE
,
RIOP
SHR
STORGRP(6groupname)
VALIDate WAIT(2,2)
55
TOLerate(IOERror) UNCATalog NOVALIDate WAIT(numsecs,numretries)
,ENQFailure
ENQFailure
,IOERror
DUMP DATASET Syntax for Physical Data Set

,
55DUMpDATASet( E )INDDNAME(6ddn)5
DS
FILterdd(ddn)
IDD
FDD
6
INDYNAM((volser))
IDY
,unit
,
5OUTDDname(6ddn)5%
ODD
F
E: Additional Keywords with DUMP DATASET for Physical Data Set

,
INClude(\\)
,

,

6dsn) INClude(6dsn)
EXClude(
,
INClude(\\)
EXClude(6dsn)
,

,

INClude(6dsn)

6
6
6
INClude(dsn)
,

,
EXClude(6dsn)
6
6
F: Optional Keywords with DUMP DATASET for Physical Data Sets
92
DUMP Command
55
ADMINistrator
, ALLExcp CANcelerror CHECKvtoc COMpress
ALLData(6dsn) ALLX
ALLData(\)
OPTimize(1)
55
CONCurrent DELete DYNALloc OPTimize(n) PASsword(ddn)
CC
PSWD ,
6dsn/pswd
READIOPacing()
55
PROCESS(SYS1) PURge READIOPacing(nnn) RESEt SHAre
PRG
RIOP
SHR
WAIT(2,2)
55
TOLerate(IOERror) UNCATalog WAIT(numsecs,numretries)
,ENQFailure
ENQFailure
,IOERror
Explanation of DUMP Command Keywords

This section describes the keywords for the DUMP command.
ADMINistrator
55
ADMINistrator

for the DUMP command. If you are not authorized to use the ADMINISTRATOR
ALLData
55
6dsn)
ALLData(
ALLData(\)
ALLDATA applies to full and data set dump operations.
dsn
specifies the fully qualified name of a data set whose data set organization is PS7,
When ALLDATA or ALLEXCP is specified for an extended-sequential data set, data beyond the last used block pointer is not
retained. The target data set is allocated with the same amount of space as the source data set during a logical restore or copy
operation.
93
DUMP Command
PSU, PO, POU, or null, for which all allocated space is to be dumped.8
* (asterisk)
specifies that all allocated space is to be dumped for:8
All sequential7 and partitioned data sets that are not empty, and
Data sets whose data set organization is null and are not empty (the last used
block pointer in the data set's VTOC entry is not zero).
Notes:
1. Using the ALLDATA keyword will result in all the allocated space being dumped
for applicable data sets. However, whether or not all the allocated space is
restored depends on data set characteristics and device characteristics during
the restore. If you require that all of the unused space is restored, then you
should be sure that the data set is restored to a like device type and not
reblocked or compressed. Compress is the default for PDS data sets on restore
unless you use the NOPACKING keyword.
|
|
2. For physical dump of PDSE and HFS data sets, all of the allocated space is
always dumped, regardless of the ALLDATA keyword.
ALLExcp
55
ALLExcp
ALLX
ALLEXCP is an option for full and data set dump operations. It instructs DFSMSdss
to dump all allocated space for data sets whose data set organization is PS7, PSU,
PO, POU, or null and are empty (the last used block pointer in the data set's VTOC
entry is zero).8
Note: Using the ALLEXCP keyword will result in all the allocated space being
dumped for applicable data sets. However, whether or not all the allocated
space is restored depends on data set characteristics and device
characteristics during the restore. If you require that all of the unused space
is restored, then you should be sure that the data set is restored to a like
device type and not reblocked or compressed. Compress is the default for
PDS data sets on restore unless you use the NOPACKING keyword.
BY
,
6(schar,op,(
6arg)))5
5BY(
BY specifies that the data sets selected up to this point by the processing of the
INCLUDE and EXCLUDE keywords are to be further filtered. To select the data set,
all BY criteria must be met. See Filtering by Data Set Characteristics on page 14
Any time a data set can have data beyond the last used block pointer in the data set's VTOC entry, or has a data set organization
that is null, or is the first or intermediate volume of a multivolume data set that has a data set organization that is null, you must
specify ALLDATA(dsn) or ALLDATA(*) if the data set is not empty or ALLEXCP if the data set is empty) to dump all its data.
JES2/JES3 data sets can have these characteristics, as can CICS journal and MSVCJRNL data sets.
94
DUMP Command
for a full discussion of schar, op, and arg. See the separate discussions of
INCLUDE and EXCLUDE for information on how these keywords are specified.
CANcelerror
55
CANcelerror
CANCELERROR specifies that the dump operation is to be ended if a track-related

permanent read error occurs. If this keyword is not specified and a permanent read
error occurs, the track image record is flagged on the output volume as having an
I/O error, and the dump operation continues. This track is not restored in a restore
operation. When CANCELERROR is specified, the TOLERATE(IOERROR)
keyword is ignored.
This keyword may be used in conjunction with the CHECKVTOC keyword to
specify whether or not operation is to continue in the event of terminating VTOC
errors discovered during VTOC checking. Refer to CHECKVTOC keyword.
Note: CANCELERROR has no effect on the following types of errors on a DASD
volume:
Equipment check
Command reject
Busout parity
CHECKvtoc
55
CHECKvtoc
CHECKVTOC specifies that a VTOC analysis of the source volume be performed

during dump processing. In the event of terminating VTOC errors found during
analysis, operation continues unless the CANcelerror keyword is specified.
CHECKVTOC is ignored if CPVOLUME is also specified.
COMpress
55
COMpress
COMPRESS specifies that the dumped data is to be written in compressed form to

the output medium. This decreases the space occupied by the dump data at the
expense of increased processor and elapsed times.
Notes:
1. The COMPRESS keyword is ignored if it is specified during a logical data set
dump for extended-format data sets, extended-sequential data sets, or
compressible extended-format VSAM data sets.
2. If you have a tape drive with the compaction feature and you want to use
hardware data compaction, you do not need to specify the COMPRESS
95
DUMP Command
keyword. If software data compression is desired, you do not need to specify

DCB=TRTCH=COMP in the JCL. However, you may specify both the
COMPRESS keyword and DCB=TRTCH=COMP.
CONCurrent
55
CONCurrent
CC NOTIFYCONCurrent
NOTIFYCC
CONCURRENT specifies that the data is to be processed with concurrent copy if it

is possible, otherwise, the data will be processed as if CONCURRENT was not
specified.
|
|
|
|
If the source volume is a RAMAC Virtual Array and CONCURRENT is specified,

DFSMSdss uses the Snapshot capability of the RVA to provide a function
equivalent to concurrent copy. This function is called CC-compatible Snapshot and
is transparent to the user.
If a concurrent copy operation fails after signaling that the concurrent copy
initialization was complete (and update activity on the data has resumed), it is not
possible to recover the data at the point-in-time at which the concurrent copy
operation was started. This is because the data may have been updated while the
dump operation was progressing.
Attention: Performing concurrent copy operations against many large data sets
when there is also heavy update activity (such as reorganizing data sets or
initializing the volume the data sets reside on) can result in a shortage of storage.
The shortage occurs because data is transferred to data-space storage faster than
DFSMSdss can process it. Refer to the section about managing availability with
DFSMSdss in DFSMS/MVS DFSMSdss Storage Administration Guide for additional
information on determining concurrent copy storage requirements.
Note: The CONCURRENT keyword cannot be specified with the DELETE or
UNCATALOG keywords.
NOTIFYCONCURRENT
For a logical data set dump operation, specifies that DFSMSdss issues message
ADR767I for every data set that is successfully included in the concurrent copy
operation. If not specified, messages are issued only for data sets that are not
successfully included in the concurrent copy operation.
CPVOLume
55
CPVOLume
CPVOLUME specifies that the input volume is a VM-format volume and that the
OS-compatible VTOC must begin on track zero, record five. You must specify the
track range to be copied with the TRACKS keyword, as the OS-compatible VTOCs
do not describe the extents of any data on the volume. You must also specify the
ADMINISTRATOR keyword with CPVOLUME because DFSMSdss cannot check
access authorization for VM data.
96
DUMP Command
DATASet
5DATASet5
DS
DATASET specifies a data set dump operation, using filtering. See Chapter 2,
explanation of the filtering process used. Unless the ALLDATA or ALLEXCP
keyword is specified, only used tracks are dumped for sequential and partitioned
data sets and for data sets with no defined data set organization (for example,
JES2/JES3 data sets). If the free space map in the VTOC is invalid, all tracks are
dumped.
Notes:
1. Either the FILTERDD, INCLUDE, EXCLUDE, or BY keyword must be specified
when DATASET is selected.
2. Nonintegrated catalog facility VSAM catalogs are not supported for data set
processing. If nonintegrated catalog facility VSAM catalogs are processed, the
DELete
55
DELete
For a physical data set dump, DELETE instructs DFSMSdss to delete expired
single-volume, non-VSAM data sets that are successfully serialized and dumped. In
addition, DFSMSdss is to uncatalog successfully deleted data sets. DELETE is
ignored for VSAM data sets.
|
|
For a logical data set dump, DELETE can be used to delete expired single- and
multivolume VSAM and non-VSAM data sets that are successfully serialized and
dumped. Unmovable data sets can also be deleted. User catalogs cannot be
deleted. Unexpired source data sets are deleted only if you also specify PURGE.
Notes:
1. For both a physical and a logical data set dump operation, you cannot delete
data sets with a high-level qualifier of SYS1 unless you specify
PROCESS(SYS1). Even if PROCESS(SYS1) is specified, SYS1.VVDS and
SYS1.VTOCIX data sets cannot be dumped and deleted. To delete or scratch a
password-protected data set, the operator must supply the password for
DADSM scratch password checking.
2. Do not specify SHARE if you specify DELETE.
3. Do not specify DELETE with CONCURRENT, because after the concurrent
copy operation has begun, the original data can still be updated.
97
DUMP Command
DYNALloc
55
DYNALloc

of data sets. This allows cross-system serialization in a JES3/MVS environment.
Notes:
1. The serialization is of value only when the dynamic allocation/JES3 interface is
not disabled.
2. Run time increases when you use DYNALLOC to serialize data sets (as
3. If a data set passes INCLUDE/EXCLUDE filtering and is migrated before BY
filtering and DYNALLOC is used, the dynamic allocation causes the data set to
be recalled. DFSMSdss waits for the recall processing to complete. If the data
set is recalled to a different volume, a message is issued indicating that the
VTOC entry was not found.
EXClude
,
6dsn)5
5EXClude(
dsn
specifies the name of a data set to be excluded from the data sets selected by
INCLUDE. Either a fully or a partially qualified data set name can be used. See
INCLUDE and BY for information on how these keywords are specified.
FILterdd
5FILterdd(ddn)5
FDD
FILTERDD specifies the name of the DD statement that identifies the sequential
data set or member of a partitioned data set that contains the filtering criteria to
use. The filtering criteria are in the form of card-image records, in DFSMSdss
command syntax, containing the INCLUDE, EXCLUDE, and BY keywords that
complete the DUMP command syntax.
Note: You must use FILTERDD when you have more than 255 entries in the
INCLUDE, EXCLUDE, or BY list of subkeywords.
FORCECP
55
FORCECP(days)
98
DUMP Command
FORCECP specifies that checkpointed data sets resident on the SMS volume or
volumes can be logically dumped. Checkpoint indications are not removed from the
data set during conversion.
days
is a one-tothree-digit number in the range of zero to 255, and specifies the
data set can be dumped.
FULl
5FULl5
FULL specifies that an entire DASD volume is to be dumped. This is the default.
Unallocated tracks are not dumped. Unless the ALLDATA or ALLEXCP keyword is
specified, only used tracks are dumped for sequential and partitioned data sets and
for data sets with no defined data set organization. (for example, JES2/JES3 data
sets). If the free space map in the VTOC is invalid, all tracks are dumped. Used
tracks consist of the tracks from the beginning of the data set to the last-used track
(as indicated by the last used block pointer in the data sets VTOC entry).
Notes:
1. You cannot specify SHARE or TOL(ENQF) for FULL operations.
2. Nonintegrated catalog facility VSAM catalogs are not supported for full-volume
INCAT
55
6catname)
INCAT(
ONLYINCAT
INCAT specifies one or more user catalogs to be searched before the standard
order of search for locating data sets. STEPCAT and JOBCAT are not allowed for
processing SMS-managed data sets. INCAT allows you to identify specific source
catalogs. To specify INCAT, RACF authorization may be required. Refer to
catname
ONLYINCAT
specifies that DFSMSdss is to only search catalogs specified in the INCAT catalog
name list.
99
DUMP Command
INClude
,
6dsn)5
5INClude(
dsn
specifies the name of a data set eligible to be dumped. Either a fully or a partially
page 12. If INCLUDE is omitted (but EXCLUDE or BY is specified) or if
INCLUDE(**) is specified, all data sets are eligible to be selected for dumping. See
the separate discussions of EXCLUDE and BY for information on how these
INDDname
,
6ddn)5
5INDDname(
IDD
ddn
specifies the name of the DD statement that identifies the input volume to be
dumped. To assure correct processing, each of the DD statements corresponding
to a DDNAME (ddn) must identify only one volume serial number.
Notes:
1. Only one ddn can be specified for INDDname when you use full or tracks dump
operation. One or more are allowed for a physical data set dump operation.
2. Specifying INDDNAME or INDYNAM results in a physical dump. To do a logical
data set dump, either do not specify any input volumes with the DATASET
keyword or use the LOGINDDNAME or LOGINDYNAM keywords.
INDYnam
,
6(volser))5
5INDYnam(
IDY
,unit
INDYNAM specifies that volumes to be dumped are to be dynamically allocated for

a full, tracks, or physical data set dump.
volser
specifies the volume serial number of a DASD volume to be dumped.
unit
specifies the device type of a DASD volume to be dumped. This parameter is
optional.
100
DUMP Command
Notes:
1. The volume must be mounted and online. You cannot specify a nonspecific
volume serial number using an asterisk (*).
2. Only one volume is allowed for a full or tracks dump operation; one or more
volumes are allowed for a physical data set dump operation.
3. Using INDYNAM instead of DD statements to allocate DASD volumes does not
appreciably increase run time and permits easier coding of JCL and command
input.
4. If either INDDNAME or INDYNAM is specified, physical processing is used to
perform the dump. If both INDDNAME and INDYNAM are omitted, a logical
data set dump is performed. A logical data set dump is also performed if you
specify LOGINDDNAME or LOGINDYNAM.
LOGINDDname
55
,
SELECTMulti(ALL)
LOGINDDname(6ddn)
LIDD
SELECTMulti(ALL)
SELM
ANY
FIRST
ddn
specifies the name of the DD statement that identifies the input volume that
contains the data sets for a logical dump operation. To ensure correct processing,
each of the DD statements corresponding to a DDNAME (ddn) must identify only
one volume serial number.
See the SELECTMULTI description and the notes under LOGINDYNAM.
LOGINDYnam
55
,
SELECTMulti(ALL)
6(volser))
LOGINDYnam(
LIDY
,unit
SELECTMulti(ALL)
SELM
ANY
FIRST
LOGINDYNAM specifies that volumes that contain the data sets to be dumped
using logical processing are to be dynamically allocated.
Note: The volume must be mounted and online. You cannot specify a nonspecific
volume serial number using an asterisk (*).
volser
specifies the volume serial number of a DASD volume to be dumped.
unit
specifies the device type of a DASD volume to be dumped. This parameter is
optional.
SELECTMULTI
specifies the method for determining how cataloged multivolume data sets are to be
selected during a logical data set dump operation. SELECTMULTI is accepted only
when logical volume filtering is specified with either LOGINDDNAME or
LOGINDYNAM keywords. If logical volume filtering is not used, the specification of
SELECTMULTI is not accepted.
101
DUMP Command
ALL is the default, and specifies that DFSMSdss not dump a multivolume data set
unless the volume list specified by LOGINDDNAME or LOGINDYNAM lists all the
volumes that contain a part of the data set or VSAM cluster. For VSAM data sets:
If SPHERE is not specified, all parts of the base cluster or alternate index must
be contained in the volume list.
If SPHERE is specified, all parts of the base cluster must be contained in the
volume list.
ANY specifies that DFSMSdss dump a multivolume data set when any volume in
the volume list specified by LOGINDDNAME or LOGINDYNAM contains a part of
the data set or VSAM cluster. For VSAM data sets:
If SPHERE is not specified, any part of the base cluster or alternate index can
be contained in the volume list.
If SPHERE is specified, any part of the base cluster can be contained in the
volume list.
FIRST specifies that DFSMSdss dump a multivolume data set only when the
volume list specified by LOGINDDNAME or LOGINDYNAM lists the volume that
contains the first part of the data set. For VSAM data sets:
If SPHERE is not specified, the volume list must include the volume containing
the first extent of the data component for the base cluster or the volume
containing the first extent of the data component of an alternate index.
If SPHERE is specified, the volume list must include the volume containing the
first extent of the data component for the base cluster.
Notes for LOGINDDNAME and LOGINDYNAM keywords:
1. If LOGINDDNAME or LOGINDYNAM is specified, DFSMSdss uses logical
processing to perform the dump operation. Logical processing is also used if no
input volume is specified.
2. A multivolume data set that has extents on volumes not specified with
LOGINDDNAME or LOGINDYNAM will not be dumped unless you specify
SELECTMULTI.
NOTIFYCONCURRENT
See the CONCURRENT keyword.
NOVALIDate
See the VALIDATE keyword.
ONLYINCAT
OPTimize
OPTimize(1)
55
OPTimize(n)
OPTIMIZE specifies the number of tracks to be read at a time, as follows:

If n is 1, DFSMSdss reads one track at a time.
If n is 2, DFSMSdss reads two tracks at a time.
If n is 3, DFSMSdss reads five tracks at a time.
102
DUMP Command
If n is 4, DFSMSdss reads one cylinder at a time.

If OPTIMIZE is not specified, OPTIMIZE(1) is the default. Specifying OPTIMIZE (2),
(3), or (4) reduces the time for a dump. Notice that this keyword uses more real
and virtual storage. It also keeps the channel busy for longer blocks of time.
OUTDDname
,
6ddn)5
5OUTDDname(
ODD
ddn
specifies the name of the DD statement that identifies the (output) dump data set.
This data set can be on a tape or a DASD volume. Up to 255 DDNAMEs can be
specified; that is, up to 255 dump copies can be made.
Notes:
1. The default block size for output records written to tape is 65 520 bytes. You
can change this default to 32 760 bytes by using the installation options exit
routine. Refer to DFSMS/MVS Installation Exits for details.
2. The default block size for output records written to DASD is the track length for
devices whose track length is less than 32KB (KB equals 1 024 bytes), or
one-half the track length for devices whose track length is greater than 32KB.
3. If the DCB keyword BLKSIZE is specified on the DD statement for tape or
DASD, it must be in the range of 7 892 to 32 760 inclusive.
4. The COPYDUMP command cannot change the block size of the DFSMSdss
dump data set. If you intend to copy the dump data set to a DASD device, you
must ensure that the block size will be small enough to fit on the target device.
5. If the DCB keyword RECFM is specified on the DD statement, it must have a
value of U.
6. If the DCB keyword LRECL is specified on the DD statement, it must have a
value of 0 (zero).
7. The output data set must be a standard format sequential data set and cannot
use any extended-format features, such as compression.
PASsword
55
PASsword(ddn)
PSWD
,
6dsn/pswd
PASSWORD specifies the passwords DFSMSdss uses for password-protected data

sets for all dump operations. (Password checking is bypassed for RACF-protected
data sets.) This keyword is required only if:
You do not have the required volume-level RACF DASDVOL or RACF
DATASET access.
103
DUMP Command
authorization exit.
ddn
format.
dsn/pswd
Note: Printing of actual data set passwords specified in your input command
stream is suppressed in the SYSPRINT output.
PROCESS
55
PROCESS(SYS1)
SYS1
specifies that DFSMSdss is to allow data sets with a high-level qualifier of SYS1 to
be dumped and that SYS1 data sets can be deleted and uncataloged. SYS1.VVDS
and SYS1.VTOCIX data sets can be physically, but not logically, dumped.
SYS1.VVDS and SYS1.VTOCIX data sets cannot be deleted or uncataloged. To
specify PROCESS(SYS1), RACF authorization may be required. Refer to
PURge
55
PURge
PRG
PURGE for a data set dump operation, specifies deletion of unexpired data sets
that are dumped successfully. This keyword is valid only when DELETE has been
specified.
READIOPacing
READIOPacing()
55
READIOPacing(nnn)
RIOP
READIOPACING specifies the pacing (that is, I/O delay) to be used for DFSMSdss
DASD read channel programs. You can use this keyword to allow more time for
104
DUMP Command
other applications to complete I/O processing. DFSMSdss waits the specified time
before issuing each channel program that reads from DASD.
nnn
specifies the amount of time in milliseconds. The maximum delay that can be
specified is 999 milliseconds.
Notes:
1. If READIOPACING is not specified, there will be no I/O delay.
2. The additional wait time does not apply to error recovery channel programs.
3. READIOPACING does not apply to concurrent copy I/O.
RESEt
55
RESEt
RESET specifies that the data-set-changed flag in the VTOC entry is to be reset for
all data sets serialized and successfully dumped. This applies to both a full dump
and a data set dump operation.
Notes:
1. Do not specify SHARE if you specify RESET. You might not want to specify
RESET if you use a storage management program, such as DFSMShsm.
2. The RESET keyword is ignored when a data set is dumped using RLS access.
|
|
|
|
|
|
|
3. For a logical data set dump operation, the use of the RESET keyword causes
the enqueue on a data set to be held until all data sets are dumped.
DFSMSdss does not reset the data set change indicator until after all data sets
are dumped. This may be of particular interest when dumping user catalogs.
The fact that DFSMSdss will hold the enqueue for the user catalog until all the
data sets are dumped may cause delays for other jobs that need access to the
user catalog and may cause a lockout condition when another job is dumping
the same catalog at the same time. For information about a patch to modify the
reset algorithm, refer to the appendix in DFSMS/MVS DFSMSdss Diagnosis
Guide.
4. You may specify both CONCURRENT and RESET, but RESET is ignored and
a warning message is printed unless your installation uses a patch to tell
DFSMSdss to accept RESET with CONCURRENT and to reset the data set
changed indicator after the concurrent copy initialization is complete. If your
installation uses the patch, it is possible that the data set changed indicator is
left reset (off) even when the dump of the data set is not successful. If this is
unacceptable, do not specify RESET with CONCURRENT. Refer to the
appendix in DFSMS/MVS DFSMSdss Diagnosis Guide for more information on
DFSMSdss patches.
105
DUMP Command
SELECTMulti
See the LOGINDDNAME and LOGINDYNAM keywords.
SHAre
55
SHAre
SHR
SHARE specifies that DFSMSdss is to share the data sets to be dumped for read
access with other programs. Do not specify the DELETE, RESET, or UNCATALOG
keyword if you specify SHARE. Use SHARE carefully to ensure that the contents of
the dumped copy of the data set are valid.
SHARE and FULL are mutually exclusive and cannot be specified together.
Note: Unlike the COPY and RESTORE commands, the SHARE keyword is
honored for VSAM data sets. However, the SHARE keyword is only
honored for VSAM data sets that were defined with share options other than
(1,3) or (1,4).
Specifying the SHARE keyword does not cause DFSMSdss to honor the
share options defined for VSAM data sets. For VSAM data sets defined with
share options other than (1,3) or (1,4), specifying the SHARE keyword
allows other programs to obtain read access, but not write access to the
data sets while they are being dumped. For VSAM data sets defined with
share options (1,3) or (1,4), neither read access nor write access by other
programs is allowed while the data set is being dumped, regardless of
whether or not SHARE was specified.
SPHERE
55
SPHERE
SPHERE is an option for a logical data set dump. SPHERE specifies that for any
VSAM cluster dumped DFSMSdss must also dump all associated AIX clusters and
paths. Individual sphere components need not be specified, only the base cluster
name.
Notes:
1. The base cluster name must be specified to process the entire sphere. If the
SPHERE keyword is specified but the base cluster name is not, none of the
associations will be processed.
2. If an AIX is dumped without the SPHERE keyword, during a restore DFSMSdss
treats the AIX as a normal VSAM KSDS.
|
STORGRP
|
|
|
55
6groupname)
STORGRP(
106
DUMP Command
|
|
|
|
|
STORGRP specifies that all of the online volumes in the storage group be
dynamically allocated. If a volume in the storage group is not online, that volume is
not used for processing. Up to 255 storage group names may be specified.
Specifying STORGRP with a storage group name is equivalent to specifying
LOGINDYNAM with all the online volumes in the storage group included in the list.
|
|
|
STORGRP is mutually exclusive with the INDDname, INDYnam, LOGINDDname
and LOGINDYnam keywords.
TOLerate
55
TOLerate(IOERror)
,ENQFailure
ENQFailure
,IOERror
ENQFailure
specifies that data sets are to be processed even though shared or exclusive
access fails.
TOL(ENQF) and FULL or TRACKS are mutually exclusive; you cannot specify
these keywords together.
Notes:
|
|
1. Unlike PDS data sets, PDSE data sets that are open for update cannot be
dumped even if TOL(ENQF) is specified.
2. If you must dump a PDSE data set and it must be open for update, process the
data set with concurrent copy (specify CONCURRENT). If you cannot use
concurrent copy, convert the PDSE back to PDS and then dump the PDS data
set with TOL(ENQF).
|
|
|
|
|
3. TOL(ENQF) is not supported for HFS data sets. HFS data sets cannot be
dumped when the HFS is mounted on a system other than the system where
the dump is being performed. TOL(ENQF) is not required when dumping an
HFS data set that is mounted on the same system where the dump is being
performed.
IOERror
specifies that DFSMSdss is to continue processing even though input errors occur,
but is to end after 100 errors. This applies only to input errors and only to
equipment check and busout parity.
Notes:
1. TOL(IOERror) is ignored if CANcelerror is specified.
2. If a permanent read error occurs, the track image record is flagged on output
as having an I/O error and the dump processing continues.
3. This track is cleared in a restore operation.
107
DUMP Command
TRACKS
55
,,c1,max head #
6
TRACKS((c1))
TRKS
,c1,max head #
,h1
,max head #
,c2
,h2
TRACKS specifies ranges of tracks to be dumped. When you restore the data, this
entire range or its subset must be specified with the RESTORE command. Refer
to DFSMS/MVS DFSMSdss Storage Administration Guide for additional information
on using TRACKS during physical processing.
c1,h1
c2,h2
Notes:
1. The c2 must be greater than or equal to c1.
2. If c2 equals c1, h2 must be greater than or equal to h1.
example:
Specified Results
None
Syntax error
c1
c1,h1
c1,h1,c2
c1,,c2
Syntax error
,h1
Syntax error
UNCATalog
55
UNCATalog
UNCATALOG applies to physical and logical data set dump operations.

For a physical data set dump operation, UNCATALOG instructs DFSMSdss to
uncatalog any single-volume, non-VSAM, cataloged data sets successfully dumped
from the current volume.
For a logical data set dump operation, UNCATALOG instructs DFSMSdss to
uncatalog any successfully dumped single or multivolume non-VSAM data sets that
108
DUMP Command
are currently cataloged. (For VSAM or SMS-managed data sets, use the DELETE
keyword.)
Notes:
1. UNCATALOG is ignored for VSAM and SMS-managed data sets.
2. Do not specify UNCATALOG with CONCURRENT, because after the
concurrent copy operation has begun, the original data can still be updated.
3. For a logical data set dump operation, the use of the UNCATALOG keyword
causes the enqueue in a data set to be held until all data sets are dumped.
DFSMSdss does not uncatalog the data set until after all data sets are
dumped. Refer to the appendix in DFSMS/MVS DFSMSdss Diagnosis Guide
for information about a patch to modify the UNCATALOG algorithm.
4. Any non-SMS, non-VSAM data set that has a high-level qualifier of SYS1
cannot be uncataloged unless PROCESS(SYS1) is specified.
VALIDate
VALIDate
55
NOVALIDate
VALIDATE on a logical data set dump, specifies that all indexed VSAM data sets
are to be validated as they are dumped. If the NOVALIDATE keyword is specified,
the indexed VSAM data sets are dumped without validation. VALIDATE is the
default.
Notes:
1. If an indexed VSAM data set is dumped using VALIDATE, it must be restored
on a system that supports VALIDATE. Otherwise, an error message is issued,
and the restore fails.
2. Do not specify the NOVALIDATE keyword when processing VSAM
extended-format or extended-addressable data sets.
3. When a data set is restored, the free space in the control areas and control
intervals are reset to the values in the catalog entry. You can override the
values in the catalog entry by specifying the FREESPACE keyword on the
restore.
4. Use the NOVALIDATE keyword on the DUMP command if you wish to restore
to a DFDSS Version 2 Release 5 system that does not have the appropriate
VALIDATE support, or to any level of DFDSS prior to Release 2 Version 5.
WAIT
WAIT(2,2)
55
For Physical Data Set Dump Processing: WAIT specifies to DFSMSdss the
length of a wait and the number of retries to obtain control of a data set.
109
DUMP Command
numsecs
is a decimal number from 0 to 255 that specifies the interval, in seconds, between
retries.
numretries
is a decimal number (099) that specifies the number of times DFSMSdss must
retry to gain control of a data set.
For Logical Data Set Dump Processing: WAIT specifies to DFSMSdss the
length of wait and the number of passes to be made through the list of selected
data sets to obtain control of a data set.
numsecs
is a decimal number from 0 to 255 that specifies the interval, in seconds, to wait
before attempting another pass through the list of selected data sets.
numretries
is a 1- or 2-digit number (099) that specifies the number of passes to make
through the list of selected data sets in an attempt to obtain control of a data set.
numretries.
For logical data set dump operation, the WAIT keyword has a different meaning
when: (1) data sets are being serialized, (2) multiple data sets are being processed,
and (3) WAIT(0,0) is not specified. In this case, DFSMSdss makes multiple passes
through the list of selected data sets. On each pass, DFSMSdss processes the
data sets that (1) can be serialized without waiting for the resource and (2) were
not processed before. At the end of a pass, if none of the data sets could be
processed without waiting for a resource, then, in the next pass, at the first
occurrence of a data set that was not processed, a WAIT will be issued. That data
set and the remainder of the list will be processed if possible. The above procedure
will be repeated until all data sets are processed or the WAIT limits are reached.
For example, if WAIT(3,10) is specified and 5 data sets are left to be processed, up
to 10 passes are made. On each pass, an unprocessed data set is waited upon for
3 seconds. Thus, only a 30-second maximum will ever be waited, not 150 (5 times
3 times 10).
system resources.
Data Integrity Considerations for Full or Tracks Dump Operation

For a full or tracks dump operation, DFSMSdss serializes the VTOC to preclude
DADSM functions (such as ALLOCATE, EXTEND, RENAME, and SCRATCH) from
changing the contents of the VTOC on the volume during the dump operation.
Data sets are not serialized on these full or tracks operations. Therefore, some
data sets might be opened by other jobs during the dump operation, resulting in
copies of partially updated data sets. You can minimize this possibility by
performing the dump operation when there is low system activity.
110
DUMP Command
Full data integrity can only be guaranteed by performing dump operations by data
set when TOL(ENQF) or SHARE keywords are not specified.
Format of the Output Data Set

Refer to DFSMS/MVS DFSMSdss Diagnosis Guide for the format of the output data
set.
Examples of Full and Tracks Dump Operations

In the following example, data from DASD volume 111111 is to be dumped to the
first data set of standard label tape volumes TAPE01 and TAPE02.
The command input to be substituted for a full and tracks dump are shown below in
Example 1A and Example 1B, respectively. To restore the same volume, refer to
Examples 1, 1A, and 1B of the RESTORE command.
Example 1:
//JOB1
JOB
//STEP1
EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=A
//DASD
DD
//TAPE
DD
UNIT=(348,2),VOL=SER=(TAPE1,TAPE2),
// LABEL=(1,SL),DISP=(NEW,CATLG),DSNAME=USER2.BACKUP
//SYSIN
DD
\
command input (See Examples 1A and 1B below)
/\
Example 1A: A Full Dump Operation

DUMP
INDDNAME(DASD) OUTDDNAME(TAPE)
Example 1B: A Tracks Dump Operation

DUMP
TRACKS(1,,1,5) INDDNAME(DASD) OUTDDNAME(TAPE)
Example 1C: Full-Volume Dump Operation with CONCURRENT

//DSSJOB JOB
//DUMPSTEP EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=\
//DASD
DD
UNIT=SYSDA,VOL=SER=(SSDASD),DISP=OLD
//TAPE
DD
UNIT=TAPE,VOL=SER=(TAPE1,TAPE2,TAPE3),LABEL=(1,SL),
// DISP=(NEW,KEEP),DSN=USER.BACKUP
//SYSIN
DD
\
DUMP FULL INDDNAME(DASD) OUTDDNAME(TAPE) COMPRESS CONCURRENT
/\
This JCL does a DFSMSdss full-volume dump using concurrent copy. This job
continues (with a warning message) if concurrent copy initialization fails. No special
action is required to perform a restore operation after a concurrent copy dump
operation.
111
DUMP Command
Examples of Physical Data Set Dump Operations

Example 2 shows specified data sets on DASD volumes 111111 and 222222 being
dumped to the first data set of standard label tape volume TAPE02.
Examples 2A through 2G below complement Examples 2A through 2D in the
restore section, in any combination; for example, the dump tape produced in
Example 2C can be used as the input tape for Example 2A under the RESTORE
command.
Example 2:
//JOB2
JOB
//STEP1
EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=A
//DASD1
DD
//DASD2
DD
//TAPE
DD
//SYSIN
DD
\
command input (see Examples 2A, 2B, ... 2G that follow)
/\
Example 2A: Using the INCLUDE Subkeyword

DUMP
INDDNAME(DASD1,DASD2) OUTDDNAME(TAPE) DATASET(INCLUDE(USER2.\\,USER3.\))
Example 2B: Using the INCLUDE and EXCLUDE Subkeywords

DUMP
INDDNAME(DASD1,DASD2) OUTDDNAME(TAPE) DATASET(INCLUDE(USER2.\\,USER3.\) EXCLUDE(USER2.\\.REP))
Example 2C: Using the INCLUDE, EXCLUDE, and BY

Subkeywords
DUMP
INDDNAME(DASD1,DASD2) OUTDDNAME(TAPE) DATASET(INCLUDE(USER2.\\,USER3.\) EXCLUDE(USER2.\\.REP) BY((DSCHA,EQ,1)))
Example 2D: With Filtering Data in a Data Set

DUMP
INDDNAME(DASD1,DASD2) OUTDDNAME(TAPE) DATASET(FILTERDD(A1))
Note: The following DD statement must be added to the JCL shown above:
//A1
DD
DSNAME=USER2.FILTER,DISP=SHR
This cataloged data set (USER2.FILTER) contains three card-image records. The
information shown is positioned in columns 2 through 72 of each record:
INCLUDE(USER2.\\,USER3.\) EXCLUDE(USER2.\\.REP) BY((DSCHA,EQ,1))
112
DUMP Command
Example 2E: With Passwords in the Input Stream

DUMP
INDDNAME(DASD1,DASD2) OUTDDNAME(TAPE) DATASET(INCLUDE(USER2.\\,USER3.\)) PASSWORD(USER2.ABC.DEF/PSWD1,USER2.XYZ/PSWD2)
Example 2F: With Passwords in a Data Set

DUMP
INDDNAME(DASD1,DASD2) OUTDDNAME(TAPE) DATASET(INCLUDE(USER2.\\,USER3.\)) PASSWORD(PDD)
Note: The following DD statement must be added to the JCL shown above:
//PDD
DD
DSNAME=USER2.PASSWORD,DISP=SHR
This cataloged data set (USER2.PASSWORD) contains a single card-image record.

The information shown is positioned in columns 2 through 72:
USER2.ABC.DEF/PSWD1,USER2.XYZ/PSWD2
Example 2G: Wait for Data Sets if They or Other Data Sets with
the Same Name Are in Use by Other Jobs
DUMP
INDDNAME(DASD1) OUTDDNAME(TAPE) DATASET(INCLUDE(\\)) WAIT(1,99)
If a data set is in use, DFSMSdss waits for one second, then tries to gain access to
the resource again. This is done as many as 99 times for each data set.
Example 2H: Clearing Volumes of Uncataloged Data Sets

DUMP
DATASET(INCLUDE(\\) BY((DSORG NE VSAM) (CATLG EQ NO))) INDDNAME(DASD1,DASD2) OUTDDNAME(TAPE) DELETE PURGE
If you do not want a dump of the uncataloged data sets, the DD named TAPE can
be a dummy. DASD1 and DASD2 identify the input volumes. A physical data set
dump can handle multiple uncataloged single-volume data sets with the same
name if multiple volumes are specified. This is because each volume is processed
in order, one at a time. The dump cannot handle a multivolume data set even if all
the volumes on which it resides are specified as input volumes.
Examples of Logical Data Set Dump Operations

This section contains examples of logical data set dump operations.
Example 1: Dumping Data Sets That are Constantly in Use
113
DUMP Command
//JOB1
JOB
//STEP1
EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=A
//DASD1
DD
//DASD2
DD
//TAPE
DD
//SYSIN
DD
\
DUMP LOGINDDNAME(DASD1) OUTDDNAME(TAPE) DATASET(INCLUDE(\\)) TOL(ENQF) WAIT(,)
/\
DFSMSdss does not wait (WAIT(0,0)) if a data set is in use. Instead, it processes
the data set without serialization or enqueuing (TOL(ENQF)).
Example 2: Dumping a User Catalog and its Aliases

To dump a user catalog, you perform a logical data set dump with the fully qualified
user catalog name as the data set name. No filtering is allowed. If the user catalog
has any aliases, the aliases are automatically dumped.
//JOB2
JOB
//STEP1
EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=A
//DASD1
DD
//TAPE
DD
//SYSIN
DD
\
DUMP OUTDDNAME(TAPE) DS(INCLUDE(MY.USER.CAT))
/\
Example 3: A Logical Data Set Dump Operation with Catalog

Filtering
//JOB3
JOB
//STEP1
EXEC PGM=ADRDSSU
//TAPE
DD
// LABEL=(1,SL),DISP=(NEW,CATLG),DSN=USER3.BACKUP
//SYSPRINT DD
SYSOUT=A
//SYSIN
DD
\
DUMP OUTDD(TAPE) DS(INCL(USER1.\\))
/\
All data sets cataloged in the standard search order whose first-level qualifier is
USER1 are to be dumped. Because some of these data sets are multivolume,
source DASD volumes are not specified, resulting in data set selection by catalog.
Example 3 can be modified as follows to dump only data sets changed since the
last backup. In addition, data sets that end with a qualifier of LISTING are not to be
dumped (EXCL(**.LISTING)).
//SYSIN
DD \
DUMP OUTDD(TAPE) DS(INCL(USER1.\\) EXCL(\\.LISTING) BY((DSCHA EQ 1)))
/\
114
DUMP Command
Example 4: A Logical Data Set Dump Operation with VTOC

Filtering
//JOB4
JOB
//STEP1
EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=A
//DASD1
DD
VOL=SER=3381,UNIT=338,DISP=OLD
//TAPE
DD
//SYSIN
DD
\
LOGINDDNAME(DASD1) OUTDDNAME(TAPE) DELETE PURGE
/\
All data sets on volume 338001 whose first qualifier is USER3 are included in a
logical data set DUMP. DFSMSdss filters using the VTOC of volume 338001.
Catalogs are also used, as needed, for multivolume and VSAM data sets.
The previous example can be modified as follows to dynamically allocate volume
338001 and to do SELECTMULTI processing. All single volume data sets on
volume 338001 are included in a logical data set dump operation.
SELECTMULTI(ANY) specifies that a cataloged data set residing on volumes
338001, 338003, and 338005 will be dumped even though 338003 and 338005 are
not in the LOGINDYNAM volume list.
//JOB4
JOB
//STEP1
EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=A
//TAPE
DD
//SYSIN
DD
\
DUMP DATASET(INCLUDE(\\)) SELECTMULTI(ANY) LOGINDYNAM(3381) OUTDDNAME(TAPE) DELETE PURGE
/\
Example 5: A Logical Data Set Dump Operation for Storage

Management Subsystem (SMS)
//JOB5
JOB
//STEP1
EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=A
//TAPE
DD
DSN=BACKUP(+1),DISP=(,CATLG),
// DCB=(SYS1.DFDSS.DSCB)
//SYSIN
DD
\
DUMP LOGINDYNAM(3381) SELECTMULTI(FIRST) DATASET(INCLUDE(\\)) OUTDDNAME(TAPE) DELETE
/\
This example backs up the volume to a generation data set. You can use
generation data set groups to create and manage multiple backup versions of a
volume or data sets.
115
DUMP Command
A volume is backed up for converting to or from SMS management by using a

logical data set dump function.
Example 6: Logical Dump Operation with CONCURRENT

//JOB6
JOB
//DUMPSTEP EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=\
//TAPE
DD
UNIT=TAPE,VOL=SER=(TAPE1,TAPE2,TAPE3),LABEL=(1,SL),
// DISP=(NEW,KEEP),DSN=USER.BACKUP
//SYSIN
DD
\
DUMP DATASET(INCLUDE(USER.LOG,USER.TABLE,USER.XREF)) OUTDDNAME(TAPE) OPTIMIZE(4) CONCURRENT
/\
This JCL does a DFSMSdss logical data set dump of three fully qualified data sets
using concurrent copy. This job continues with a warning message if concurrent
copy initialization fails. No special action is required to perform a restore operation
after a concurrent copy dump operation.
Example 7: Clearing Volumes of Uncataloged Data Sets

//JOB7
JOB
//STEP1
EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=A
//DASD1
DD
VOL=SER=MYVOL1,UNIT=SYSDA,DISP=OLD
//DASD2
DD
VOL=SER=MYVOL2,UNIT=SYSDA,DISP=OLD
//TAPE
DD
UNIT=348,VOL=SER=TAPE4,LABEL=(1,SL),
// DISP=(NEW,CATLG),DSN=USER3.BACKUP
//SYSIN
DD
\
DUMP DATASET(INCLUDE(\\) BY((DSORG NE VSAM) (CATLG EQ NO))) LOGINDDNAME(DASD1,DASD2) OUTDDNAME(TAPE) DELETE PURGE
/\
Logical data set dump cannot be used to dump SMS data sets that are not
cataloged or are cataloged outside the standard order of search. DFSMSdss
physical data set dump or IDCAMS DELETE NVR can be used for such cleanup
operations.
If you do not want a dump of the uncataloged data sets, the DD named TAPE can
be a dummy. DASD1 and DASD2 identify the input volumes. A logical data set
dump cannot handle multiple uncataloged data sets with the same name in the
same job even if all the volumes on which they reside are specified as input
volumes.
A logical dump can handle a legitimate multivolume uncataloged data set if all the
volumes on which it resides are specified as input volumes and if no cataloged data
set by the same name exists on the system.
116
PRINT Command
PRINT Command
With the PRINT command, you can print:
A single-volume non-VSAM data set, as specified by a fully qualified name.
You must specify the volume where the data set resides, but you do not need
to specify the range of tracks it occupies.
A single-volume VSAM data set component (not cluster). The component name
specified must be the name in the VTOC, not the name in the catalog.
Ranges of tracks.
All or part of the VTOC. The VTOC location need not be known.
Note: In order to print a multivolume data set, multiple PRINT commands with the
appropriate INDD/INDY keywords must be used.
Unless the ALLDATA keyword is specified, only the used space is printed for
sequential or partitioned data sets or data sets with data set organizations of null.
If an error occurs in reading a record, DFSMSdss attempts to print the record in
error. You can print all requested tracks or just a subset of the tracks that have
data checks. For information about authorization checking, see Chapter 6, Data
Security and Authorization Checking on page 207.
PRINT Syntax
VTOC(1,X'FFFF')
55PRInt5
PRT
,a
TOLerate(IOERror)
ADMINistrator
VTOC(a)
,b
DATASet(dsn)
DS
A
,,c1,max head #
TRACKS(c1)
TRKS
,c1,max head #
TOLerate(IOERror)
,h1
,max head #
,c2
,h2
55
DATALength(n) ERRortracks KEYlength(n) OUTDDname(ddn) PASsword(ddn)
ODD
PSWD
,
6dsn/pswd
5INDDname(ddn)5%
IDD
INDYnam(volser)
IDY
,unit
A: Optional Keywords with PRINT DATASET

55
ALLData DYNALloc SHAre TOLerate(IOERror)
SHR
,ENQFailure
ENQFailure
,IOERror
WAIT(2,2)
55
117
PRINT Command
Explanation of PRINT Command Keywords

This section describes the keywords for the PRINT command.
ADMINistrator
55
ADMINistrator

for the PRINT command. If you are not authorized to use the ADMINISTRATOR
ALLData
55
ALLData
ALLDATA specifies, when the DATASET keyword is also specified, that all
allocated space in the data set is to be printed.
DATALength
55
DATALength(n)
n
specifies the logical length, in decimal format, of the data portion of a record. It is
used only if the count field of a record on any track has a data check.
DATASet
5DATASet(dsn)5
DS
dsn
specifies the fully qualified name of the data set to be printed. The data set is
printed in logical sequence.
Note: Data set filtering is not allowed with the PRINT command.
Nonintegrated catalog facility VSAM catalogs are not supported for data set
processing. Attempting to print such a data set will result in message ADR377W.
118
PRINT Command
DYNALloc
55
DYNALloc

Consider:
not disabled.
Run time increases when you use the DYNALLOC keyword to serialize data
sets (as opposed to enqueue) because overhead is involved in dynamic
allocation and serialization across multiple processors.
ERRortracks
55
ERRortracks
ERRORTRACKS specifies that only tracks on which data checks occur are to be
printed.
INDDname
5INDDname(ddn)5
IDD
ddn
specifies the name of the DD statement that identifies a volume that contains the
data set, range of tracks, or the VTOC to be printed. If you want to print a
multivolume data set, you must print one volume at a time.
INDYnam
5INDYnam(volser)5
IDY
,unit
INDYNAM specifies that the volume that contains the data set, range of tracks, or
the VTOC to be printed is to be dynamically allocated. The volume must be
mounted and online. You cannot specify a nonspecific volume serial number using
an asterisk (*).
Using INDYNAM instead of DD statements to allocate DASD volumes does not
noticeably increase run time and permits easier coding of JCL and command input.
volser
specifies the volume serial number of a DASD volume to be printed.
unit
specifies the device type of a DASD volume to be printed. This parameter is
optional.
119
PRINT Command
KEYlength
55
KEYlength(n)
n
specifies the key length, in decimal format, of a record. It is used only if the count
field of a record on any track has a data check.
OUTDDname
55
OUTDDname(ddn)
ODD
ddn
specifies the name of the DD statement that identifies the (output) print data set.
Each of the DD statements corresponding to a DDNAME (ddn) must identify only
one volume serial number. If this keyword is not specified, the default is
SYSPRINT.
Notes:
1. If the DCB keyword LRECL is specified on the DD statement, it must be in the
range of 84 to 137 inclusive. If BLKSIZE is specified, it must be at least four
greater than the LRECL.
2. If an LRECL less than 84 is chosen, the return code is 8 and an error message
is issued.
3. If the specified LRECL is greater than 137, LRECL and BLKSIZE are set to 137
and 141, respectively.
PASsword
55
PASsword(ddn)
PSWD
,
6dsn/pswd

data sets. (Password checking is bypassed for RACF-protected data sets.) This is
required only if:
DATASET access.
authorization exit.
For VSAM data sets, passwords are checked at the cluster level only.
Note: The PASSWORD keyword is not valid for a PRINT VTOC command.
120
PRINT Command
ddn
member of a partitioned data set, that contains data set names and their
passwords. This data set must contain card-image records in DFSMSdss command
syntax format.
dsn/pswd
SHAre
55
SHAre
SHR
SHARE specifies that DFSMSdss is to share, for read access with other programs,
the data set that is to be printed.
TOLerate
55
TOLerate(IOERror)
,ENQFailure
ENQFailure
,IOERror
ENQFailure
specifies that data sets are to be processed even though shared or exclusive
access fails. For more information on TOL(ENQF), see Appendix D, Examples of
the Application Program with the User Interaction Module (UIM) on page 287.
IOERror
specifies that DFSMSdss is to continue processing even though I/O errors occur,
but is to end after 100 errors.
TRACKS
55
,,c1,max head #
TRACKS(c1)
TRKS
,c1,max head #
,h1
,max head #
,c2
,h2
TRACKS specifies ranges of tracks to be printed.
c1,h1
121
PRINT Command
c2,h2
hexadecimal numbers as X'c2' or X'h2'. The c2 must be greater than or equal to
c1. If c2 equals c1, h2 must be greater than or equal to h1.
example:
Specified Results
None
Syntax error
c1
c1,h1
c1,h1,c2
c1,,c2
Syntax error
,h1
Syntax error
VTOC
VTOC(1,X'FFFF')
55
,a
VTOC(a)
,b
VTOC specifies that all or part of the VTOC is to be printed. Omitting the VTOC,
DATASET, and TRACKS keywords causes the entire VTOC to be printed. Part of
the VTOC can be printed by specifying:
VTOC(a,b)
where a and b are the relative track numbers (1 is the first track) of the first and
last tracks to be printed. The value of b must be equal to or greater than the value
of a and equal to or less than 65535 (X'FFFF'). Either of these numbers can be
specified in decimal or hexadecimal. To specify a hexadecimal number, code
X'nn'.
If only the first value (a) is specified, only that track is printed.
If the second value (b) is greater than the relative track number of the last physical
track of the VTOC, DFSMSdss prints up to and including the last track of the
VTOC. Therefore, another way of printing the entire VTOC would be to specify:
VTOC(1,X'FFFF')
Note: The PASSWORD keyword is not valid for a PRINT VTOC command.
WAIT
WAIT(2,2)
55
122
PRINT Command
numsecs
numretries
numretries.
system resources.
Examples of Print Operations

The following are examples of the PRINT command.
Example 1: Print a Range of Tracks

//JOB2
JOB
//STEP1
EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=A
//DASD
DD
//SYSIN
DD
\
PRINT TRACKS(1,,1,5) INDDNAME(DASD)
/\
Print a hard copy of tracks 0 through 5 from cylinder 1 on volume 111111.
Example 2: Print a Component of a VSAM Cluster

//JOB3
JOB
//STEP1
EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=A
//SYSIN
DD
\
PRINT INDYNAM(338) /\ ALLOC VOL 338 DYNAMICALLY
DS(PARTS.VSAM1.INDEX) /\ DATA SET THAT HAS BAD TRACK
WAIT(,)
/\ DO NOT WAIT IF ENQ FAILS
TOL(ENQF)
/\ IGNORE ENQ FAILURES
PSWD(PARTS.VSAM1/USERPSWD) /\ PASSWORD FOR CLUSTER
/\
\/
\/
\/
\/
\/
A component of a VSAM data set is to be printed. The printing is to proceed even if

the component cannot be serialized (enqueued).
123
RELEASE Command
Example 3: Print a Data Set

//DSSJOB
//PRINTDS EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=\
//SYSIN
DD
\
PRINT DATASET(PUBSEXMP.SAM.S1) INDYNAM(D9S6)
/\
The output shown in Figure 2 was produced from the example above.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
PAGE 1
5695-DF175 DFSMSDSS V1R5. DATA SET SERVICES
1998.293 15:28
PRINT
DATASET(PUBSEXMP.SAM.S1) INDYNAM(D9S6)
ADR11I (R/I)-RI1 (1), TASKID 1 HAS BEEN ASSIGNED TO COMMAND 'PRINT '
ADR19I (R/I)-RI1 (1), 1998.293 15:28:31 INITIAL SCAN OF USER CONTROL STATEMENTS COMPLETED.
ADR16I (1)-PRIME(1), RACF LOGGING OPTION IN EFFECT FOR THIS TASK
ADR6I (1)-STEND(1), 1998.293 15:28:31 EXECUTION BEGINS
\\\ TRACK(CCHH) E
R DATA
COUNT E119
FFFF FF1D7E4 C2E2C5E7 D4D74BE2 C1D44BE2 FF1C1C2 C3C4C5C6 C7C8C9D1 \1PUBSEXMP.SAM.S1ABCDEFGHIJ\
2 D2D3D4D5 D6D7D8D9 E2E3E4E5 E6E7E8E9 C1C2C3C4 C5C6C7C8 C9D1D2D3 D4D5D6D7 \KLMNOPQRSTUVWXYZABCDEFGHIJKLMNOP\
4 D8D9E2E3 E4E5E6E7 E8E9C1C2 C3C4C5C6 FFFF FF2D7E4 C2E2C5E7 D4D74BE2 \QRSTUVWXYZABCDEF2PUBSEXMP.S\
6 C1D44BE2 FF1C1C2 C3C4C5C6 C7C8C9D1 D2D3D4D5 D6D7D8D9 E2E3E4E5 E6E7E8E9 \AM.S1ABCDEFGHIJKLMNOPQRSTUVWXYZ\
8 C1C2C3C4 C5C6C7C8 C9D1D2D3 D4D5D6D7 D8D9E2E3 E4E5E6E7 E8E9C1C2 C3C4C5C6 \ABCDEFGHIJKLMNOPQRSTUVWXYZABCDEF\
A FFFF FF3D7E4 C2E2C5E7 D4D74BE2 C1D44BE2 FF1C1C2 C3C4C5C6 C7C8C9D1 \3PUBSEXMP.SAM.S1ABCDEFGHIJ\
C D2D3D4D5 D6D7D8D9 E2E3E4E5 E6E7E8E9 C1C2C3C4 C5C6C7C8 C9D1D2D3 D4D5D6D7 \KLMNOPQRSTUVWXYZABCDEFGHIJKLMNOP\
E D8D9E2E3 E4E5E6E7 E8E9C1C2 C3C4C5C6 FFFF FF4D7E4 C2E2C5E7 D4D74BE2 \QRSTUVWXYZABCDEF4PUBSEXMP.S\
1 C1D44BE2 FF1C1C2 C3C4C5C6 C7C8C9D1 D2D3D4D5 D6D7D8D9 E2E3E4E5 E6E7E8E9 \AM.S1ABCDEFGHIJKLMNOPQRSTUVWXYZ\
12 C1C2C3C4 C5C6C7C8 C9D1D2D3 D4D5D6D7 D8D9E2E3 E4E5E6E7 E8E9C1C2 C3C4C5C6 \ABCDEFGHIJKLMNOPQRSTUVWXYZABCDEF\
14 FFFF FF5D7E4 C2E2C5E7 D4D74BE2 C1D44BE2 FF1C1C2 C3C4C5C6 C7C8C9D1 \5PUBSEXMP.SAM.S1ABCDEFGHIJ\
16 D2D3D4D5 D6D7D8D9 E2E3E4E5 E6E7E8E9 C1C2C3C4 C5C6C7C8 C9D1D2D3 D4D5D6D7 \KLMNOPQRSTUVWXYZABCDEFGHIJKLMNOP\
18 D8D9E2E3 E4E5E6E7 E8E9C1C2 C3C4C5C6
\QRSTUVWXYZABCDEF
\
ADR6I (1)-STEND(2), 1998.293 15:28:31 EXECUTION ENDS
ADR13I (1)-CLTSK(1), 1998.293 15:28:31 TASK COMPLETED WITH RETURN CODE
ADR12I (SCH)-DSSU (1), 1998.293 15:28:31 DFSMSDSS PROCESSING COMPLETE. HIGHEST RETURN CODE IS
Figure 2. Output Resulting from a PRINT Command
RELEASE Command
|
|
|
|
|
|
|
The RELEASE command releases allocated but unused space from all eligible
sequential, partitioned, and extended-format VSAM data sets that pass INCLUDE,
EXCLUDE, and BY filtering criteria. The RELEASE command does not release
space from guaranteed-space VSAM extended-format data sets. For an explanation
of these criteria, see Chapter 2, FilteringChoosing the Data Sets You Want
Processed on page 11. DFSMSdss only selects data sets that have space that
can be released.
DFSMSdss offers two ways to process RELEASE commands:
|
|
|
|
|
Logical processing operates on a single selected data set at a time. The data
set can be multivolume. The user has the option to not specify volumes or to
specify one or more volumes with the LOGDDNAME, LOGDYNAM, or
STORGRP keywords. Releasing unused space from extended-format VSAM
data sets requires logical processing.
|
|
|
|
If no input volumes are specified and the INCAT keyword is not specified,
DFSMSdss selects from all data sets cataloged in the catalogs accessible
through the standard search order. For INCAT keyword details, see the INCAT
keyword description in this section.
124
RELEASE Command
|
|
|
|
|
Physical processing operates on all selected data sets that reside on a single
volume. The user must specify one or more volumes with the DDNAME or
DYNAM keywords. You cannot use physical processing to release unused
space from extended-format VSAM data sets.
To process multivolume data sets, do one of the following:
Specify no input volumes.
|
|
Specify LOGDDNAME, LOGDYNAM, or STORGRP with an appropriate

SELECTMULTI option or a volume list.
|
|
Specify DDNAME or DYNAM with the volume or volumes on which the

data set has releasable space.
You must exclude, by using the EXCLUDE keyword, data sets whose last used
block pointer in the data sets VTOC entry are not properly maintained. This can
occur if you use an access method other than BSAM, QSAM, or BPAM.
DFSMSdss does not release any space for data sets that are empty (the last used
block pointer in the data sets VTOC entry is zero). This restriction does not apply
to PDSE data sets; used space in PDSE data sets is maintained internally, rather
than by reference to the data sets VTOC entry.
The following apply to the RELEASE command:
|
|
|
|
|
|
|
A data set with the maximum number of extents already in use will not have
any space released. For an extended-format VSAM data set, the maximum is
255 extents. For a partitioned data set extended (PDSE) and an
extended-sequential data set, the maximum is 123 extents. For other
partitioned and sequential data sets, the maximum is 16 extents.
For extended-format VSAM data sets, DFSMSdss releases space from only the
data component of a base cluster or an alternate index (AIX).
Free tracks in cylinder-allocated extents are not released. Only free cylinders
are released.
DFSMSdss excludes system data sets beginning with SYS1, unless the
PROCESS keyword is used.
DFSMSdss releases space from each volume on which an extended-sequential
data set contains data.
DFSMSdss does not support the release of HFS data sets, as the DADSM
PARTREL macro no longer supports HFS data sets.
RELEASE Syntax for Physical Processing

,
5RELease A DDName(6ddn)5
FILterdd(ddn) B
,
FDD
DYNam(6(volser))
,unit
||
|
|
|
RELEASE Syntax for Logical Processing
A: Additional Keywords with RELEASE for Physical or Logical Processing
5RELease A 5
FILterdd(ddn) B C
FDD
125
RELEASE Command
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
INClude(\\)
,

,

,
INClude(\\)
EXClude(6dsn)
,

,

INClude(6dsn)

6
6
6
INClude(dsn)
,

,
EXClude(6dsn)
|
|
|
|
|
|
|
|
|
|
B: Optional Keywords with RELEASE for Physical or Logical Processing
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
C: Optional Keywords with RELEASE for Logical Processing
MINSECqty(1) MINTRAcksunused(1)
555
ADMINistrator DYNALloc FORCECP(days) MINSECqty(n) MINTRAcksunused(n)
MINTRKS
WAIT(2,2)
55%
PASsword(ddn) PROCESS(SYS1) WAIT(numsecs,numretries)
PSWD
,
6dsn/pswd
55
,
SELECTMulti(ALL)
LOGDDname(6ddn)
LDD
SELECTMulti(ALL)
SELM
ANY
FIRST
,
SELECTMulti(ALL)
LOGDYnam(6(volser))
LDY
,unit
SELECTMulti(ALL)
SELM
ANY
FIRST
55
,
SPHERE
,
INCAT(6catname)
STORGRP(6groupname)
ONLYINCAT
Explanation of RELEASE Command Keywords

This section describes the keywords for the RELEASE command.
ADMINistrator
55
ADMINistrator

for the RELEASE command. If you are not authorized to use the ADMINISTRATOR
126
RELEASE Command
BY
,
6(schar,op,(
6arg)))5
5BY(
page 14 for a full discussion of schar, op, and arg. See the separate discussions of
INCLUDE and EXCLUDE for information on how these keywords are specified.
DDName
,
6ddn)5
5DDName(
DDNAME requests physical processing.
ddn
specifies the name of the DD statement that identifies a volume whose sequential
and partitioned data sets, if selected, are to have their unused space released. To
assure correct processing, each of the DD statements corresponding to a DDname
(ddn) must identify only one volume serial number.
DYNALloc
55
DYNALloc
DYNALLOC specifies dynamic allocation, instead of the ENQ macro, to serialize

the use of data sets. This allows cross-system serialization in a JES3/MVS
environment.
Consider:
This serialization is of value only when the dynamic allocation/JES3 interface is
not disabled.
Run time increases when you use DYNALLOC to serialize data sets (as
DYNam
,
6(volser))5
5DYNam(
,unit
DYNAM requests physical processing and specifies that the volume to be

processed be dynamically allocated. The volume must be mounted and online. You
cannot specify a nonspecific volume serial number using an asterisk (*). Using
127
RELEASE Command
DYNAM instead of DD statements to allocate DASD volumes will not appreciably

increase run time and permits easier coding of JCL and command input.
volser
unit
optional.
EXClude
,
6dsn)5
5EXClude(
dsn
INCLUDE. Either a fully or a partially qualified data set name can be used. See the
separate discussions of INCLUDE and BY for information on how these keywords
are specified.
FILterdd
5FILterdd(ddn)5
FDD
ddn
INCLUDE, EXCLUDE, and BY keywords that complete the RELEASE command
syntax.
FORCECP
55
FORCECP(days)
FORCECP specifies that allocated but unused space in checkpointed data sets
resident on the SMS volume or volumes can be released. Checkpoint indications
are removed from the data set.
days
is a one- to three-digit number in the range of zero to 255, and specifies the
space can be released.
128
RELEASE Command
INCAT
|
|
|
|
55
6catname)
INCAT(
ONLYINCAT
|
|
|
|
|
|
INCAT specifies that DFSMSdss search one or more user catalogs before the
standard order of search for locating data sets. DFSMSdss does not allow
STEPCAT and JOBCAT when processing SMS-managed data sets. The INCAT
keyword allows you to identify specific source catalogs. RACF authorization may be
required to specify INCAT. Refer to DFSMS/MVS DFSMSdss Storage
Administration Guide for more information about the RACF Facility Class profiles.
|
|
catname
|
|
|
ONLYINCAT
specifies that DFSMSdss only search catalogs specified in the INCAT catalog name
list.
|
|
|
INClude
,
6dsn)5
5INClude(
dsn
specifies the name of a data set whose unused space is eligible to be released.
Either a fully or a partially qualified data set name can be used. See Filtering by
Data Set Names on page 12. If INCLUDE is omitted (but EXCLUDE or BY is
specified) or if INCLUDE(**) is specified, all data sets are eligible to be selected for
releasing. See the separate discussions of EXCLUDE and BY for information on
how these keywords are specified.
|
|
|
|
|
|
|
LOGDDname
LOGDDname requests logical processing that is based on a specified volume list.
|
|
|
|
|
ddn
specifies the name of the DD statement that identifies a single volume that contains
the data sets to be released by logical processing. You can specify up to 255
DDNAME entries with the LOGDDNAME keyword. Each DD statement can
correspond to only one volume serial number.
55
,
SELECTMulti(ALL)
LOGDDname(6ddn)
LDD
SELECTMulti(ALL)
SELM
ANY
FIRST
129
RELEASE Command
|
|
|
|
|
SELECTMULTI
specifies the method that determines how DFSMSdss selects cataloged
multivolume data sets. DFSMSdss accepts SELECTMULTI only when you specify
logical processing with either the LOGDDNAME or LOGDYNAM keyword.
Otherwise, DFSMSdss cannot accept the SELECTMULTI keyword.
|
|
|
|
ALL
is the default, and specifies that DFSMSdss not process a multivolume data set
unless the volume list specified by LOGDDNAME or LOGDYNAM lists all the
volumes that contain a part of the data set of VSAM cluster.
|
|
|
|
ANY
specifies that DFSMSdss process a multivolume data set when any part of the
non-VSAM data set or VSAM cluster is on a volume in the volume list specified by
LOGDDNAME or LOGDYNAM.
|
|
|
|
|
FIRST
specifies that DFSMSdss process a multivolume data set only when the volume list
specified by LOGDDNAME or LOGDYNAM lists the volume that contains the first
part of the data set. For VSAM data sets, the volume list must include the volume
that contains the first extent of the data component for the cluster.
|
|
|
|
Note: If you specify either the LOGDDNAME or LOGDYNAM keyword, DFSMSdss

will release a multivolume data set that has extents on volumes not included
in the volume list only if you specify the SELECTMULTI keyword with the
appropriate option (ANY or FIRST).
|
|
|
|
|
|
|
55
,
SELECTMulti(ALL)
LOGDYnam(6(volser))
LDY
,unit
SELECTMulti(ALL)
SELM
ANY
FIRST
LOGDYnam
|
|
LOGDYNAM requests logical processing and specifies that the volumes that
contain the data sets to be processed are dynamically allocated.
|
|
|
|
|
volser
specifies the volume serial number of a DASD volume to be dynamically allocated.
serial number by using an asterisk(*). You can specify up to 511 volumes with the
LOGDYNAM keyword.
|
|
|
unit
optional.
|
|
|
|
|
SELECTMULTI
specifies how DFSMSdss selects cataloged multivolume data sets. DFSMSdss
accepts SELECTMULTI only when you specify logical processing with either the
LOGDDNAME or LOGDYNAM keyword. Otherwise, DFSMSdss cannot accept the
specification of SELECTMULTI.
|
|
|
|
ALL
is the default, and specifies that DFSMSdss not process a multivolume data set
unless the volume list specified by LOGDDNAME or LOGDYNAM lists all the
volumes that contain a part of the data set of VSAM cluster.
130
RELEASE Command
|
|
|
|
ANY
specifies that DFSMSdss process a multivolume data set when any part of the
non-VSAM data set or VSAM cluster is on a volume in the volume list specified by
LOGDDNAME or LOGDYNAM.
|
|
|
|
|
FIRST
specifies that DFSMSdss process a multivolume data set only when the volume list
specified by LOGDDNAME or LOGDYNAM lists the volume that contains the first
part of the data set. For VSAM data sets, the volume list must include the volume
that contains the first extent of the data component for the cluster.
|
|
|
|
Note: If you specify either the LOGDDNAME or LOGDYNAM keyword, DFSMSdss

will release a multivolume data set that has extents on volumes not included
in the volume list only if you specify the SELECTMULTI keyword with the
appropriate option (ANY or FIRST).
MINSECqty
MINSECqty(1)
55
MINSECqty(n)
|
|
|
|
|
|
|
|
|
|
When you have not specified a secondary allocation quantity, all the allocated but
unused space is released, and after the release operation you will not be able to
add records to the data set. MINSECQTY solves this problem. The release
operation is not performed unless the secondary allocation quantity in the VTOC
(VVDS for extended-format VSAM) is equal to or greater than n tracks and the data
set has not reached the maximum number of used extents (16 extents for
sequential and partitioned data sets, 123 extents for extended-format sequential
data sets and PDSEs, or 255 extents for extended-format VSAM data sets). The
letter n represents a 1-to-5-digit decimal number with a range from zero to 99999.
The default is one track if you do not specify MINSECQTY (n).
MINTRAcksunused
MINTRAcksunused(1)
55
MINTRAcksunused(n)
MINTRKS
MINTRACKSUNUSED specifies that the release operation is to be performed only

if the number of unused tracks for a selected data set is equal to or greater than n,
where n is a 1-to-5-digit decimal number with a range from 0 to 99999. When
MINTRKS is not specified, a default value of 1 is used. If a release operation is
done, all unused tracks will be released.
|
|
ONLYINCAT
131
RELEASE Command
PASsword
55
PASsword(ddn)
PSWD
,
6dsn/pswd
PASSWORD specifies the passwords DFSMSdss uses for selected

password-protected sequential and partitioned data sets. (Password checking is
bypassed for RACF-protected data sets.) This keyword is required only if:
DATASET access.
authorization exit. For details, refer to DFSMS/MVS Installation Exits.
ddn
format.
dsn/pswd
PROCESS
55
PROCESS(SYS1)
PROCESS specifies that the release operation is to be performed for data sets with
a high-level qualifier of SYS1. To specify PROCESS(SYS1), RACF authorization
may be required. Refer to DFSMS/MVS DFSMSdss Storage Administration Guide
for more information.
SELECTMULTI
|
See the LOGDDNAME or LOGDYNAM keyword.
SPHERE
|
|
55
SPHERE
|
|
|
SPHERE specifies that DFSMSdss also select all associated alternate index
clusters whenever you select a VSAM base cluster. You do not need to specify
individual names of sphere components, only the base cluster name. If you specify
132
RELEASE Command
|
|
a volume list (with LOGDDNAME or LOGDYNAM), you do not need to specify the
volumes on which the AIX clusters reside.
|
|
|
|
To select an entire sphere, specify the base cluster name by using fully or partially
qualified data set names. If you specify SPHERE but not the base cluster name,
DFSMSdss processes only those data components of the sphere whose names are
specified.
STORGRP
|
|
|
55
6groupname)
STORGRP(
|
|
|
|
|
STORGRP specifies that DFSMSdss dynamically allocate all of the online volumes
in the storage group. DFSMSdss does not process a volume in the storage group
that is not online. You can specify up to 255 storage group names. Specifying
STORGRP with a storage group name is equivalent to specifying LOGINDYNAM
with all the online volumes in the storage group that is included in the list.
|
|
|
STORGRP is mutually exclusive with the DDname, DYnam, LOGDDname, and
LOGDYnam keywords.
WAIT
WAIT(2,2)
55
numsecs
numretries
intervals. If you do not want to wait for a resource, specify 0 for either numsecs or
numretries.
system resources.
133
RELEASE Command
Example of a Release Operation

The following is an example of a release operation on selected sequential and
partitioned data sets.
//JOB1
JOB
//STEP1
EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=A
//SYSIN
DD
\
RELEASE INCLUDE(\\) DYNAM(338)
/\ DYNAM ALLOC VOL 338
\/ MINTRKS(1)
/\ THERE ARE 1 OR MORE UNUSED TRKS \/ /\ MINSEC NOT SPEC. IT DEFAULTS TO 1 \/
/\
Unused tracks of sequential and partitioned data sets on volume 338000 are to be
released if both:
The number of unused tracks in the data set is greater than or equal to 10.
The data set can be extended later if required (MINSEC(1)). This need not be
specified, because it is the default.
The above example can be modified as follows to release unused tracks of all
sequential and partitioned data sets, other than system data sets, that have any
unused tracks and that can be extended:
//SYSIN
DD
\
RELEASE INCLUDE(\\)
DYNAM(338)
/\
/\ DYNAM ALLOC VOL 338 \/
|
|
|
|
The following is an example of the commands used to release unused space from
extended-format VSAM data sets residing wholly or in part on a specific volume,
and to release unused space from the data sets alternate indexes that reside on
any volumes:
|
|
|
|
|
|
|
//SYSIN
DD
\
RELEASE INCLUDE(\\) BY(DSORG EQ VSAM)
/\ RELEASE ONLY VSAM
\/LOGDYNAM(339)
/\ DYN ALLOC VOL 339 \/SELECTMULTI(ANY)
/\EVEN IF MULTIVOL
\/SPHERE
/\ RELEASE AIXES
\/
/\
|
|
To release unused space from all eligible data sets that are cataloged in a
particular user catalog, without specifying any volume:
|
|
|
|
//SYSIN
DD
\
RELEASE INCLUDE(\\)
INCAT(CATALOGA) ONLYINCAT /\ ONLY FROM CATALOG \/
/\
134
RESTORE Command
RESTORE Command
With the RESTORE command, you can restore data to DASD volumes from
DFSMSdss-produced dump volumes. You can restore data sets, an entire volume,
or ranges of tracks. You can restore to unlike devices from a logical dump tape.
Note: The FULL keyword with the RESTORE command specifies that an entire
DASD volume is to be restored. The TRACKS keyword for RESTORE
command specifies ranges of tracks to be restored.
DFSMSdss offers two ways to process RESTORE commands:
sets independently of physical device format.
Physical processing can operate against data sets, volumes, and tracks, but is
oriented toward moving data at the track-image level.
The processing method is determined by what type of dump tape is used as input
and by the keywords specified on the command.
Target data set allocation differs between physical data set and logical data set
restore of non-VSAM data sets. Logical data set restore allocates target data sets
according to the amount of used space in the source data set, thereby freeing
unused space. Physical data set restore preserves the original size of the source
data set. To force unused space to be kept during logical data set restore, the
ALLDATA or ALLEXCP keyword must be specified during a dump. However, the
action that restore takes with respect to these keywords depends on data set
characteristics and device characteristics. If you require that all of the unused
space is restored, then you should be sure that the data set is restored to a like
device type and not reblocked or compressed. Compress is the default for PDS
data sets on restore unless you use the NOPACKING keyword.
DFSMSdss logical restore processing cannot be used to process partitioned data
sets containing location-dependent information that does not reside in note lists or
in the directory.
HFS, SAM compressed extended function, and data sets with DFM attributes
cannot be restored to non-SMS target volumes during a physical or logical data set
restore.
For more information on using the RESTORE command, refer to the DFSMS/MVS
DFSMSdss Storage Administration Guide .
Special Considerations for Restore

The following special considerations apply when you perform a restore operation:
When restoring a partitioned data set that has a secondary allocation of zero,
the amount of unused space allocated to the target data set may be different
from that of the source data set if the ALLDATA and ALLEXCP keywords were
not specified for the dump.
When restoring a VSAM data set with no secondary allocation, a secondary
allocation may be added as follows:
When the primary allocation is less than one cylinder, a secondary
allocation equal to the primary is created.
135
When the primary allocation is greater than or equal to one cylinder, a

secondary allocation is created by computing one percent of the primary
and rounding up to the next cylinder (in tracks).
The index component may also have secondary space added if it has no
secondary allocation.
When performing a logical restore operation of a VSAM compressed data set,
the target data set allocation must be consistent with the source data set
If the source is an extended-format VSAM KSDS, then the target must be
an extended-format VSAM KSDS.
If the source is a compressed VSAM KSDS, then the target must be a
compressed VSAM KSDS.
If the source is an alternate index for an extended-format KSDS, then the
target must be an alternate index for an extended-format KSDS.
The target control interval size must be equal to the source.
Extended-format VSAM data sets are not supported in physical processing.
The actions DFSMSdss performs for RENAME, RENAMEUNCONDITIONAL, or
REPLACE depend on the keywords you specify and the configurations of data
sets on volumes. This section contains figures that describe specific
environments for DFSMSdss restore operations.
Data Integrity Considerations for Full or Tracks Restore Operations

For a full or tracks restore operation, DFSMSdss serializes the VTOC to preclude
DADSM functions such as ALLOCATE, EXTEND, RENAME, and SCRATCH from
changing the contents of the VTOC on the volume during the restore operation.
Data sets are not serialized on these full or tracks operations. Therefore, some
data sets might be opened by other jobs during the RESTORE. The result might
be that partially updated data sets are restored. Full data integrity can always be
guaranteed by performing restore operations by data set only when
TOLERATE(ENQFAILURE) or SHARE is not specified.
During full or tracks restore operations, and Stand-Alone restore, it is possible to
duplicate a volume serial number in the sysplex. If there is data in the coupling
facility for the duplicated volume serial number, data integrity can be compromised.
The recommended procedure before restoring a suspected volume is as follows:
1. Use the D SMS,CFVOL(volid) command to determine if there is any data in the
coupling facility caches for the volume serial number to be restored.
2. Determine the disposition of any data that is in the caches.
3. Do not restore the suspected volume until the duplicated volume can be varied
offline to the sysplex, thus ensuring that there is no data in any coupling facility
cache for the duplicated volume.
RESTORE FULL and RESTORE TRACKS Command Syntax
136
55RESToreFULlINDDname(ddn)5
A
IDD
,,c1,max head #
6
TRACKS((c1))
TRKS
,c1,max head #
B
,h1
,max head #
,c2
,h2
5OUTDDname(ddn)5%
ODD
OUTDYnam(volser)
ODY
,unit
A: Optional Keywords with RESTORE FULL Command

555
ADMINistrator CANcelerror COPYVolid PASsword(ddn) PURge
CPYV
PSWD
,
PRG
6dsn/pswd
55%
WRItecheck
WRC
B: Optional Keywords with RESTORE TRACKS Command

555
ADMINistrator CANcelerror COPYVolid CPVOLume
,
CPYV
6
OUTTRacks((cc))
OUTTRKS
,hh
55%
PASsword(ddn) PURge WRItecheck
PSWD
,
PRG WRC
6dsn/pswd
RESTORE DATASET Command Syntax for Logical Data Set

55RESToreDATASet( C INDDname(ddn)5%
DS
FILterdd(ddn) D IDD
FDD
C: Additional Keywords Used with RESTORE DATASET for Logical Data Set
,
INClude(\\)
,

,

,
INClude(\\)
EXClude(6dsn)
,

,

INClude(6dsn)

6
6
6
INClude(dsn)
,

,
EXClude(6dsn)
6
6
D: Optional Keywords Used with RESTORE DATASET for Logical Data Set
137
555
ADMINistrator AUTORELBlockaddress
,
CANcelerror
AUTORELBLKA BYPASSACS(6dsn)
55
CATalog DELETECATALOGENTRY DYNALloc FORce FORCECP(days)
RECATalog(newcatname) DELCATE
RECATalog(\)
55
FREESPACE(CI) IMPORT MAKEMULTI MENtity(modeldsn)
FSPC
,CA
MVOLser(volser)
55
,
NULLMGMTCLAS NOPACKing(6dsn)
NMC
55
,
PASsword(ddn)
OUTDDname(6ddn)
PSWD
,
ODD
6dsn/pswd
OUTDYnam(6(volser))
ODY
,unit
PERCENTUtilized(1)
55
,
PROCESS(UNDEFinedsorg)
,
PERCENTUtilized(6n)
REBLock(6dsn)
PCTU
55
,
REName(pfx)
RELBlockaddress(6dsn)
RELBLKA
(6(on,nn))
((pfx),6(on,nn))
55
RENAMEUnconditional(pfx) REPlace SHAre SPHERE
RENUNC
,
SHR
(6(on,nn))
((pfx),6(on,nn))
TGTAlloc(SOURCE) TGTGDS(DEFERRED)
55
STORCLAS(storage-class-name) TGTAlloc(BLK) TGTGDS(DEFERRED)
NULLSTORCLAS
CYL
ACTIVE
NSC
TRK
ROLLEDOFF
SOURCE
SOURCE
SRC
SRC
VOLcount(\)
55
TOLerate(ENQFailure)
,
VOLcount(SRC)
TTRAddress(6dsn)
N(nn)
ANY
WAIT(2,2)
55%
WAIT(numsecs,numretries) WRItecheck
WRC
RESTORE DATASET Command Syntax for Physical Data Set

55RESToreDATASet( E INDDname(ddn)5
DS
FILterdd(ddn) F IDD
FDD
)
5OUTDDname(ddn)5%
ODD
OUTDYnam(volser)
ODY
,unit
E: Additional Keywords Used with RESTORE DATASET for Physical Data Set
138
RESTORE Command
INClude(\\)
,

,

,
INClude(\\)
EXClude(6dsn)
,

,

INClude(6dsn)

6
6
6
INClude(dsn)
,

,
EXClude(6dsn)
F: Optional Keywords Used with RESTORE DATASET for Physical Data Set
555
ADMINistrator
,
CANcelerror DYNALloc FORCECP(days)
BYPASSACS(6dsn)
55
,
LOGicalvolume(6volser) NULLMGMTCLAS
LVOL
NMC
55
PASsword(ddn) REName(pfx)
PSWD
,
6dsn/pswd
(6(on,nn))
((pfx),6(on,nn))
55
RENAMEUnconditional(pfx) REPlace SHAre
RENUNC
,
SHR
(6(on,nn))
((pfx),6(on,nn))
TGTGDS(DEFERRED)
55
STORCLAS(storage-class-name) TGTGDS(DEFERRED) TOLerate(ENQFailure)
NULLSTORCLAS
ACTIVE
NSC
ROLLEDOFF
SOURCE
SRC
WAIT(2,2)
55%
WAIT(numsecs,numretries) WRItecheck
WRC
Explanation of RESTORE Command Keywords

This section describes the keywords for the RESTORE command.
ADMINistrator
55
ADMINistrator

for the RESTORE command. If you are not authorized to use the
ADMINISTRATOR keyword, the command is ended with an error message.
Otherwise, access checking to data sets and catalogs is bypassed.
139
RESTORE Command

AUTORELBlockaddress
55
AUTORELBlockaddress
AUTORELBLKA
AUTORELBLOCKADDRESS specifies that direct access data sets are to be

automatically processed as being organized by relative block address provided that
they were accessed with an OPTCD setting indicating relative block addressing.
(Refer to DFSMS/MVS Macro Instructions for Data Sets.) These direct access data
sets are to be processed by relative block address rather than by TTR, and without
maintaining the relative track and record number for each record. The blocks must
fit on the tracks of the target volume.
Notes:
1. If any such data set is actually organized by TTR, the data set may become
unusable.
AUTORELBLOCKADDRESS keyword. Refer to the RELBLOCKADDRESS and
TTRADDRESS keywords for more information.
3. AUTORELBLOCKADDRESS is ignored for direct access data sets with variable
records formats or with standard user labels.
BY
,
6(schar,op,(
6arg)))5
5BY(
page 14 for a full discussion of schar, op, and arg. Also, separate discussions of
INCLUDE and EXCLUDE provide information on how these keywords are specified.
BYPASSACS
55
6dsn)
BYPASSACS(
BYPASSACS specifies that Automatic Class Selection (ACS) routines are not to be
invoked to determine the target data sets storage class or management class
names. To specify BYPASSACS, RACF authorization may be required. Refer to
dsn
specifies a fully or partially qualified data set name. (See Filtering by Data Set
Names on page 12 for rules.)
140
RESTORE Command
If a data set is being renamed, the old name must be specified.

Note: If BYPASSACS(dsn) is specified, all data sets that pass the BYPASSACS
selection criteria are guaranteed the specified storage class. The
combination of NULLSTORCLAS and BYPASSACS(dsn) forces the
selected data sets to be non-SMS managed.
CANcelerror
55
CANcelerror
CANCELERROR specifies that the restore function be ended for a permanent read
error, or that the restore of a data set be ended for a write error.
Permanent read error (permanent I/O error):
If CANCELERROR is specified, the restore task is ended. If this keyword is not
specified, DFSMSdss attempts to recover from the input errors, but the results
can be unpredictable as a result of the difficulty in repositioning and assembling
the data.
Write error, such as an invalid track format:
|
|
|
|
|
|
When invalid tracks are created during RESTORE processing, message

ADR367E is issued and the invalid tracks are erased from the target volume,
regardless of whether CANCELERROR is specified. For data set restore,
processing of the data set ends and the target data set is deleted. The restore
operation continues with the next data set. For full volume and tracks restore,
processing for the volume ends. Subsequent tracks are not processed.
DFSMSdss allows you to change this default operation. A patch byte is
provided to allow you to change the default handling of invalid tracks created
during RESTORE processing. Refer to the DFSMS/MVS DFSMSdss Diagnosis
Guide for additional information.
CANCELERROR has no effect on the following types of errors on a DASD volume:
Equipment check
Command reject
Busout parity
CATalog or RECATalog
55
CATalog
RECATalog(\)
For a logical restore operation, CATALOG instructs DFSMSdss to catalog data sets
that it allocates. For a physical restore operation, CATALOG is used for non-VSAM
single volume data sets; RECATALOG is ignored. DFSMSdss does not catalog
VSAM data sets during physical restore. If the CATALOG keyword is specified, it is
ignored when processing VSAM data sets. You must use IDCAMS DEFINE
RECATALOG to catalog the data sets after the physical restore.
141
RESTORE Command
CATALOG
catalogs the target data set in a catalog as determined by the standard catalog
search order. This is the default for VSAM data sets, multivolume data sets, and
SMS-managed data sets (during logical data set restore). It is also the default for
single-volume, non-VSAM, SMS-managed data sets (in physical data set restore).
RECATALOG(newcatname)
catalogs the target data set in the newcatname catalog.
RECATALOG(*)
catalogs the target data set in the same catalog that points to the source data set.
If the source data set was not cataloged, the new data set is not cataloged either.
Notes:
1. CATALOG or RECATALOG fails if the target data set is already cataloged in
the same catalog and RENAME is not specified.
2. CATALOG and RECATALOG are ignored when the target data set is
preallocated.
3. RECATALOG is ignored for SMS-managed data sets.
4. Be careful when using RECATALOG(newcatname) because the target data set
may already be cataloged outside of the standard order of search.
5. If RECATALOG is specified for a physical restore it is ignored. DFSMSdss does
not attempt to catalog the data set. If the data set is already cataloged on
another volume:
The catalog entry is not updated, and
The data set is restored, but it is not cataloged.
6. If CATALOG is specified for a physical restore of a single-volume non-VSAM
data set, DFSMSdss attempts to catalog the data set. If the data set is already
cataloged on another volume:
Message ADR385E, reason code 08, is issued,
The catalog entry will not be updated, and
The data set will be restored, but it will not be cataloged.
7. DFSMSdss physical data set restore does not create catalog entries for VSAM,
multivolume non-VSAM, or preallocated data sets. The user must create them.
8. For multivolume non-VSAM data sets, use IDCAMS DEFINE NONVSAM.
COPYVolid
55
COPYVolid
CPYV
COPYVOLID specifies that the volume ID from the dumped DASD volume is to be
copied to the output DASD volume. This applies to a full restore operation; it
applies to a tracks restore only if track 0 (zero) is to be restored.
When the volume serial number on a DASD volume is changed, the operator is
notified. The operating system then initiates either:
A demount if there is another volume with the same serial number
A mount to get the volume with the new serial number mounted
142
RESTORE Command
This might change the mount attributes of the volume. You should exercise
operating precautions if there are two or more processors sharing the same DASD
volume.
When the volume serial number is changed by using a COPYVOLID keyword or
when both the dumped volume and the restored volume have different serial
numbers, profiles are not built for the RACF-protected data sets on the restored
volume or for the RACF DASDVOL for RACF-protected DASD volumes.
Notes:
1. If you are doing a full restore operation and the input has VSAM data sets, the
VOLID must be copied.
2. The COPYVOLID keyword is required for a full-volume restore operation of
SMS-managed source volumes.
3. Exercise caution using the COPYVOLID keyword in a multiple task job step
when two or more of the tasks are using the same output volume. If the output
volume is made unavailable by the first task, all succeeding tasks that use the
same output volume will fail.
CPVOLume
55
CPVOLume
CPVOLUME specifies that the output volume is a VM-format volume and that the
OS-compatible VTOCs must begin on track zero, record five. You must specify the
track range to be copied with the TRACKS keyword, as the OS-compatible VTOCs
do not describe the extents of any data on the volume. You must also specify the
ADMINISTRATOR keyword with CPVOLUME because DFSMSdss cannot check
access authorization for VM data.
DATASet
5DATASet5
DS
DATASET specifies a data set restore operation, using filtering. See Chapter 2,
explanation of the filtering process used.
Notes:
1. Either the FILTERDD, INCLUDE, EXCLUDE, or BY keyword must be used
when DATASET is selected.
2. Nonintegrated catalog facility VSAM catalogs are not supported for data set
143
RESTORE Command
DELETECATALOGENTRY
55
DELETECATALOGENTRY
DELCATE
DELETECATALOGENTRY specifies that a disaster recovery is being performed

and the existing catalog entries for the target data sets may no longer be valid. If a
target data set is cataloged but not available, then DFSMSdss is to perform a
DELETE NOSCRATCH operation for the data set.
To specify DELETECATALOGENTRY you must have the proper RACF facility class
authorization. Refer to DFSMS/MVS DFSMSdss Storage Administration Guide and
to OS/390 Security Server (RACF) Security Administrator's Guide for information
about keywords you can protect with RACF.
Caution: This parameter should be used with extreme care because any of the
following conditions will result in a DELETE NOSCRATCH operation being
performed:
1. The target data set is cataloged but it is not found on the volume indicated by
the catalog.
2. The target data set is cataloged but the volume indicated by the catalog does
not exist on the restoring system and the restoring system is not sharing
catalogs with another system.
3. The target data set is cataloged but the volume indicated by the catalog is
offline on the restoring system and the restoring system is not sharing catalogs
with another system.
4. The target data set is cataloged but the volume indicated by the catalog does
not exist on the restoring system and the restoring system is sharing catalogs
with another system.
5. The target data set is cataloged but the volume indicated by the catalog is
offline on the restoring system and the restoring system is sharing catalogs with
another system.
6. The target data set is a multivolume data set and some, but not all of the data,
is no longer available. For this purpose, a multivolume data set is one in which
any part of the data set resides on more than one volume. Some examples
are:
A VSAM KSDS with the data- and index-components on one volume and
an alternate index (AIX) on another volume.
A VSAM KSDS with the index-component on a different volume than the
data-component.
A Keyrange VSAM data set with the keyranges residing on more than one
volume.
For conditions 1-2, it is appropriate to use DELETECATALOGENTRY to have
DFSMSdss perform a DELETE NOSCRATCH operation for the catalog entries.
Condition 1 typically occurs during a disaster recovery when the catalogs are
restored or imported before the data sets are recovered. The target data set
does not exist on the volume(s) indicated by the catalog. The restore will not be
144
RESTORE Command
successful unless the data set entries in the catalogs are deleted either by you
or by DFSMSdss.
Condition 2 on page 144 typically occurs during a disaster recovery when the
data sets are restored to different volumes on a different operating system. The
target data sets are cataloged but point to volumes that do not exist on the
target system. The restore will not be successful unless the data set entries in
the catalogs are deleted either by you or by DFSMSdss.
If you specify DELETECATALOGENTRY for conditions 3 through 6, damage is
most likely to occur:
Condition 3 on page 144 typically occurs during a disaster recovery when the
data sets are restored to different volumes on a different operating system. The
target data sets are cataloged but point to offline volumes on the target system.
The restore will not be successful unless the data set entries in the catalogs
are deleted either by you or by DFSMSdss.
Condition 3 on page 144 can also occur in any environment where volumes
are varied on and offline.
If you specify DELETECATALOGENTRY and then vary the volume back online,
you may find that there will be two copies of a data set: the original data set on
the volume that was varied offline, and the restored data set. The original data
set will no longer be cataloged.
Conditions 4 on page 144 and 5 on page 144 typically occur in a shared
system environment with a nonsymmetric system configuration. For example,
There are shared catalogs between two systems.
A data set is dumped from system A and it is being restored into system B.
The data set is cataloged in system A in a catalog that is shared by system
B.
The volume containing the data set and, if applicable, its VVDS is on
system A and is unavailable to system B.
If you specify DELETECATALOGENTRY, you may find that there will be
two copies of a data set: the original data set on the system A and the
restored data set on system B. The original data set will no longer be
cataloged.
DFSMSdss will attempt to detect condition 6 and issue an error message
instead of performing the DELETE NOSCRATCH. However, it will not always
be possible to do so. In that event, the DELETE NOSCRATCH will be issued
and DFSMSdss will attempt to restore the data set with one of the following
results:
The data set will be successfully restored, and there is no residual data
from the original data set. In this case, there is nothing further for you to
do.
The data set will be successfully restored, but there is residual data from
the original data set. Although the data set has been restored, you may
find, for example, that there is an uncataloged AIX from the original data
set. In this case, you will have to perform other corrective actions: These
are the same actions that you would have had to perform even if you had
not used the DELETECATALOGENTRY parameter.
145
RESTORE Command
An error will occur during the restore that prevents the data set from being
restored. The error results from the fact that the data set was only partially
missing. For example, residual data and the VSAM Volume Record (VVR)
may exist on a second volume so that when the data set being restored is
extended to that volume, a duplicate entry condition is encountered. Again,
if this occurs you will have to perform other corrective actions before the
data set can be successfully restored.
Notes:
1. DELETECATALOGENTRY is only supported for logical data set restore.
2. DELETECATALOGENTRY should not be used to restore partially damaged
volumes or data sets.
3. DELETECATALOGENTRY will not delete any catalog entry for user catalogs.
4. DELETECATALOGENTRY will not delete any catalog entry for migrated data
sets (VOLSER=MIGRAT).
5. DELETECATALOGENTRY will not delete any catalog entry for the SYSRES
volume (VOLSER=******).
6. DELETECATALOGENTRY will not delete any catalog entry for a data set
where the volser(s) in the catalog do not match either the source volser(s) from
the dump tape or the target volser(s) specified with OUTDD/OUTDYNAM.
7. If you are performing a disaster recovery and the original volumes are not
available on the restoring system, you should also specify the IMPORT
parameter. If you do not specify IMPORT keyword, you may be prompted by
the system to mount the volume(s) which the catalog indicates the target data
set is on, because the volumes are not online. Even if you reply CANCEL,
DFSMSdss will attempt to perform a DELETE NOSCRATCH on the data set
because it is unable to recognize the CANCEL request. Even if the DELETE
NOSCRATCH is successful, DFSMSdss may fail to allocate the volume and
issue message ADR405E, and the data set may not be restored.
8. DELETECATALOGENTRY will not delete any catalog entry when the phantom
entry indicates a different type of data set than the source data set.
DYNALloc
55
DYNALloc

Consider:
not disabled.
Run time increases when you use DYNALLOC to serialize data sets (as
146
RESTORE Command
EXClude
,
6dsn)5
5EXClude(
dsn
INCLUDE. Either a fully or a partially qualified data set name can be used. See the
separate discussion of INCLUDE and BY for information on how these keywords
are specified.
FILterdd
5FILterdd(ddn)5
FDD
ddn
the form of card-image records, in DFSMSdss command syntax, containing the
keywords INCLUDE, EXCLUDE, and BY that complete the RESTORE command
syntax below.
FORce
55
FORce
For a logical data set restore operation, FORCE specifies that DFSMSdss allows
an unmovable data set or a data set allocated by absolute track allocation to be
moved.
FORCE does not apply to ISAM data sets.
FORCECP
55
FORCECP(days)
FORCECP specifies that any checkpointed data sets resident on the SMS volume
or volumes can be logically restored or that MVS checkpointed data sets can be
physically restored. Checkpoint indications are removed from the data sets.
days
is a one-to-three-digit number in the range of zero to 255, and specifies the number
of days that must have elapsed since the last referenced date before the data set
can be restored.
Note: For IMS GSAM checkpointed data sets that are physically restored,
FORCECP is not required, and checkpoint indications are not removed from
the data sets regardless of whether or not FORCECP is specified.
147
RESTORE Command
FREESPACE
55
FREESPACE(CI)
FSPC
,CA
FREESPACE specifies free space values for DFSMSdss-allocated target VSAM

data sets. If this keyword is omitted, the control interval and control area free space
are the same as the source data set.
CI
specifies the percentage of freespace to be kept in each control interval during
allocation of the data set.
CA
specifies the percentage of freespace to be kept in each control area during
allocation of the data set. When omitted, the control area free space is the same as
the source data set.
FULl
5FULl5
FULL specifies that an entire DASD volume is to be restored. This is the default for
the RESTORE command.
Notes:
1. You cannot specify SHARE or TOL(ENQF) for FULL operations.
2. Nonintegrated catalog facility VSAM catalogs are not supported for full-volume
3. It is possible to duplicate a volume serial number during a restore FULL
operation. Follow the procedure in Data Integrity Considerations for Full or
Tracks Restore Operations on page 136 to maintain data integrity when
restoring a volume with FULL restore.
IMPORT
55
IMPORT
IMPORT specifies that the data sets being restored were dumped from a different
system and they should be considered new data sets.
Since the data sets being restored are new to the system, certain source data set
processing is modified. For example:
DFSMSdss bypasses checking to see if you are authorized to read a data set
with the same name as the one that was dumped.
If you are authorized to read the input dump data set that contains the data
sets that are being restored, you are considered to have the authority to read
any data set being restored. DFSMSdss continues to check that you are
authorized to create a new target data set or replace an existing target data
set.
148
RESTORE Command
If you are restoring the data set without renaming it, the restore may be
unsuccessful. Some common reasons for such a failure are:
You do not have sufficient authority to create a target data set with the
same name as the source data set. You must obtain the required access
authority to do so before you can restore the data set.
A data set already exists with the same name as the source data set and
you did not specify the REPLACE parameter. You must also specify the
REPLACE parameter if you want the restore to replace an existing data
set.
A data set with the same name as the source data set is cataloged but is
not available to the restoring system. You must make the volume(s)
containing the data set and, as applicable, its VVDS, available to the
restoring system before you can restore the data set.
A catalog contains a phantom entry for a data set with the same name as
the source data set. In this case, the data set does not exist on any
volume. You may either perform a separate DELETE NOSCRATCH
operation for that data set name, or you can specify the
DELETECATALOGENTRY parameter to request that DFSMSdss perform a
DELETE NOSCRATCH operation for you.
Attention: Do not use DELETECATALOGENTRY keyword if the restoring
system is sharing catalogs, but not the data set volumes, with another
system.
DFSMSdss can try to access a VVDS for a source data set in order to obtain
information such as the resource owner. If IMPORT is specified, DFSMSdss
suppresses a VVDS not available error.
To specify IMPORT, you must have the proper RACF facility class authorization
(see Protecting Usage of DFSMSdss on page 209 and refer to OS/390 Security
Server (RACF) Security Administrator's Guide).
Notes:
1. IMPORT should be RACF-protected.
2. IMPORT is only supported for logical data set restore.
3. DELETECATALOGENTRY may have to be specified to successfully restore a
data set with the old data set name. Refer to the DFSMS/MVS DFSMSdss
Storage Administration Guide for more information.
4. When IMPORT is specified, DFSMSdss does not create a discrete data set
profile unless the source data set is RACF-protected when it is dumped and
you specify the MENTITY parameter.
INClude
,
6dsn)5
5INClude(
dsn
specifies the name of a data set eligible to be restored. Either a fully or a partially
page 12. If INCLUDE is omitted (but EXCLUDE or BY is specified) or if
INCLUDE(**) is specified, all data sets are eligible to be selected for restoring. See
149
RESTORE Command
the separate discussions of EXCLUDE and BY for information about how these
INDDname
5INDDname(ddn)5
IDD
ddn
specifies the name of the DD statement that identifies the (input) dump data set.
This data set can be on a tape or DASD volume.
LOGicalvolume
55
6volser)
LOGicalvolume(
LVOL
LOGICALVOLUME specifies, for a physical data set restore operation, the volume
serial numbers of the source DASD volumes that are to be processed. For
example, if you have taken a data set dump from volumes 111111, 222222, and so
forth, but you want to restore only some data sets from source volume 222222,
specify LOGICALVOLUME (222222). LOGICALVOLUME is useful for restoring
multivolume data sets.
MAKEMULTI
55
MAKEMULTI
MAKEMULTI allows DFSMSdss to convert single volume data sets into multivolume
data sets. The default is not to convert single volume data sets into multivolume
data sets.
This keyword applies only to SMS-managed target data sets. Only single volume,
non-VSAM data sets are eligible to be changed into multivolume data sets.
SMS-managed target data sets are given a volume count (VOLCOUNT) that is
either:
The number of SMS output volumes specified in the RESTORE command, if
output volumes are specified through OUTDDNAME or OUTDYNAM.
|
The number of volumes in the target storage group or 59, whichever is less.
A data set's volume count is the maximum number of volumes to which the data
set may extend. At any one time, there may be a mixture of primary volumes
(volumes on which space is allocated for the data set) and candidate volumes
(volumes on which space may be allocated at a future time). The total sum of the
primary volumes and candidate volumes is the data set's volume count.
Note: When MAKEMULTI is specified and VOLCOUNT is also specified with an
option other than VOLCOUNT(*), the VOLCOUNT option overrides
MAKEMULTI.
150
RESTORE Command
MENtity
55
MENtity(modeldsn)
MVOLser(volser)
MENTITY specifies a model entity and, optionally, the serial number of the volume
containing that entity (volser) to be used when DFSMSdss defines discrete profiles.
These keywords are used to define the data sets to RACF. Specification of
MVOLSER is optional when the model entity (MENTITY) is either (1) cataloged in
an integrated catalog facility catalog or (2) a non-VSAM data set cataloged in the
standard catalog search order. When MVOLSER is specified for a VSAM model
entity, the volser specified must be the volume serial number of the catalog in
which the model entity is cataloged. If these keywords are not specified,
DFSMSdss defines the data set to RACF without using a model.
For a description of RACF data sets, refer to OS/390 Security Server (RACF)
Introduction.
MGMTCLAS
55
NULLMGMTCLAS
NMC
MGMTCLAS specifies the user-desired management class that is to replace the

source management class as input to the ACS routines. You must have the proper
RACF authority for the management class specified. The keyword itself does not
require RACF authorization.
NULLMGMTCLAS/NMC specifies that the input to the ACS routines is to be a null
management class rather than the source data sets management class.
MGMTCLAS and NULLMGMTCLAS are mutually exclusive.
Note: All SMS-managed data sets specified in the BYPASSACS keyword will be
assigned the specified management class because the ACS routines will
not be invoked. Non-SMS-managed data sets do not have a management
class.
NOPACKing
55
6dsn)
NOPACKing(
NOPACKING specifies that DFSMSdss is to allocate the target partitioned data set
only to devices that are the same or like device type as the source, and that
DFSMSdss is to use track level I/O to perform data movement. This results in an
exact track-for-track image of the source data set on the target volume.
dsn
specifies the fully or partially qualified names of a PDS to be processed.
151
RESTORE Command
NOPACKing is only valid with a PDS. If specified, REBLOCK is ignored for the data
set.
A PDS restored using NOPACKing is not compressed during data movement.
NOPACKing can be used for a damaged PDS that is currently usable by an
application but would be made unusable by compression or other rearrangement of
the physical layout of the data.
Note: NOPACKing only applies to logical restore operations. Physical restore uses
only track-level I/O. Therefore, no compression will take place against the
PDS.
NULLMGMTCLAS
See the MGMTCLAS keyword.
NULLSTORCLAS
See the STORCLAS keyword.
OUTDDname
,
6ddn)5
5OUTDDname(
ODD
ddn
specifies the name of the DD statement that identifies a volume to be restored to.
To assure correct processing, each of the DD statements corresponding to a
DDNAME (ddn) must identify only one volser. For a logical data set restore or when
you specify spill files, you can specify multiple names, separated by commas. For
any other type of restore, you can specify only one name.
See the Notes under OUTDYNAM for additional information.
OUTDYnam
,
6(volser))5
5OUTDYnam(
ODY
,unit
OUTDYNAME specifies that the volume to be restored to is to be dynamically

allocated. The volume must be mounted and online. You cannot specify a
nonspecific volume serial number using an asterisk (*). For a logical data set
restore or when you specify spill files, one or more volumes are allowed. For any
other type of restore, only one volume is allowed.
volser
specifies the volume serial number of a DASD volume to be restored.
unit
specifies the device type of a DASD volume to be restored. This parameter is
optional.
152
RESTORE Command
Notes for OUTDDNAME and OUTDYNAM Keywords:

1. OUTDDNAME or OUTDYNAM is required for a physical restore, even for
SMS-managed data. They are optional for a logical restore operation, except:
For multivolume data sets that are preallocated on volumes that are
different from the original source volumes; or
When the original source volume is not available, and the restored data set
is not going to be SMS-managed.
2. DFSMSdss now distinguishes between non-SMS and SMS volumes specified in
the OUTDDNAME or OUTDYNAM keywords. For non-SMS allocations, only the
volumes that are non-SMS are considered for allocation. Similarly, only SMS
volumes are considered for SMS allocations.
This distinction is also used when determining the volume count for a
multivolume allocation. Where volume count is determined from the number of
specified volumes, only those volumes eligible for the type of allocation being
done are counted. If there are no volumes that match the type of allocation
(SMS volumes for SMS allocation, or non-SMS volumes for non-SMS
allocation), processing proceeds with a null volume list.
3. If a non-VSAM data set is migrated by DFSMShsm after a logical dump
operation is performed on the data set, it should be recalled before a restore is
attempted for the data set. If it is not recalled and if either OUTDDNAME or
OUTDYNAM is specified indicating an output volume with REPLACE and
RECATALOG(*), DFSMSdss issues a message indicating that an error
occurred while trying to catalog the restored data set because it was already
cataloged as a migrated data set. The data set will be restored on the volume
specified by the OUTDDNAME or the OUTDYNAM, but the data set will not be
cataloged. If neither OUTDDNAME nor OUTDYNAM is specified, DFSMSdss
issues a message indicating that data sets with a volume serial of MIGRAT
cannot be restored.
If the DD statement corresponding to the ddn of the OUTDDNAME contains the
data set name and disposition but not the volser, DFSMShsm recalls the data
set automatically and DFSMSdss restores the data set.
OUTTRacks
55
6(cc))
OUTTRacks(
OUTTRKS
,hh
OUTTRACKS specifies, for a track restore operation, the beginning location of the
cylinder (cc) and head (hh) number of the target volume to which the track is to be
restored. The number of (cc,hh) combinations specified in the OUTTRACKS
keyword must be the same as the number of (c1,h1,c2,h2) combinations specified
in the TRACKS keyword.
If OUTTRKS is not specified, the track is restored to its original cylinder and head
number.
153
RESTORE Command
PASsword
55
PASsword(ddn)
PSWD
,
6dsn/pswd

data sets for all restore operations. (Password checking is bypassed for
RACF-protected data sets.) The PASSWORD keyword is required only if:
DATASET access.
Note: Specify the passwords for all data sets that do not have RACF protection
but do have password protection. During processing, a utility invoked by
DFSMSdss may prompt the operator for a password. You can control
authorization checking by using the installation authorization exit.
ddn
member of a partitioned data set, that contains data set names and their passwords
in the format dsn/pswd[,...]. This data set must contain card-image records in
DFSMSdss command syntax format.
dsn/pswd
dsn is a fully or partially qualified data set name. pswd is its password. If no
password follows the slash (/), dsn is treated as though it were ddn.
Note: Printing of actual data set passwords specified in your input command
stream is suppressed in the SYSPRINT output.
PERCENTUtilized
PERCENTUtilized(1)
55
6n)
PERCENTUtilized(
PCTU
PERCENTUTILIZED specifies that DFSMSdss must stop allocating data sets to the
target volumes when the allocated space reaches n percent of the total space on
the target volume. The default is 100. Specify more than one n if you have more
than one target volume (for instance, a volume for overflow). If there are more
target volumes than you have values in this keyword, the last value will be used for
the remaining target volumes.
154
RESTORE Command
Notes:
1. PERCENTUTILIZED is ignored when the target data set is preallocated.
2. PERCENTUTILIZED is not supported in an SMS environment. This keyword is
valid only for logical data set restore operations.
3. PERCENTUTILIZED is ignored if no output volume is specified.
PROCESS
55
PROCESS(UNDEFinedsorg)
UNDEFinedsorg
specifies that the logical data set restore operation is to be allowed for data sets
with undefined data set organization going to an unlike target device of a larger
capacity and that DFSMSdss is to use track level I/O to perform data movement.
This results in an exact track-for-track image of the source data set on target
volume. To specify PROCESS, RACF authorization may be required. Refer to
Note: Even though the data is being copied to a device with a larger track
capacity, the data may not fit on the output device. For example, if the
source device is a 3380, and the output device is a 3390 and the data sets
block size is less than 277 bytes, a track on the target cannot contain as
much data as a track on the source and the message ADR366W (Invalid
Track Format) is issued.
PURge
55
PURge
PRG
PURGE specifies that a full or tracks restore is not to be stopped if there are
unexpired data sets on the target volume. See the REPLACE keyword for a data
set restore operation.
REBLock
55
6dsn)
REBLock(
REBLOCK specifies that DFSMSdss is to reblock one or more of the selected

sequential or partitioned data sets.
dsn
specifies the fully or partially qualified names of a sequential or partitioned data set
to be restored and reblocked.
The REBLOCK keyword is ignored for:
Unmovable data sets
Data sets with record format of U (except for partitioned load modules)
Data sets with a record format of V, VS, VBS, or F
155
RESTORE Command
Partitioned data sets with note lists (except for partitioned load modules)
partitioned data sets that are also specified in the NOPACKING keyword
Additionally, both the installation options exit and the installation reblock exit can
override the specification of the REBLOCK keyword. The installation options exit
can specify that no data set is to be reblocked. The installation reblock exit can
specify whether a given data set is to be reblocked.
Some sequential and partitioned data sets have an attribute of being reblockable.
These data sets may be automatically reblocked by DFSMSdss independent of the
REBLOCK keyword.
information on DFSMSdss processing of reblockable data sets.
DFSMSdss uses the DASDCALC macro to determine the optimal block size for the
target. The reblocking method used, DFSMSdss or DASDCALC, is presented to the
installation reblock exit.
RECATalog
RELBlockaddress
55
6dsn)
RELBlockaddress(
RELBLKA
REBLOCKADDRESS identifies the direct access data sets whose names match the
fully or partially qualified names specified (dsn). These direct access data sets are
organized by relative block address instead of TTR and are to be restored block by
block. DFSMSdss updates the block reference count (the relative position of the
physical record as stored on its track) of dummy records. This keyword applies only
to direct access data sets with fixed record formats and without standard user
labels.
Note: If the data set is actually organized by TTR, the data set may become
unusable.
REName
55
REName(pfx)
6(on,nn))
(
6(on,nn))
((pfx),
RENAME specifies that, if a data set with the old name exists on the output DASD
volume, DFSMSdss is to allocate a new data set with the new name and restore
the data set. If the data set with the old name does not exist on the volume, the
data set is restored with the old name. For a VSAM data set that already exists on
another DASD volume and is cataloged, the VSAM data set is restored with the
new name unless the new name also exists and is cataloged.
156
RESTORE Command
VSAM data sets cannot be renamed during a physical data set restore. If a data set
is preallocated with the new name, it is not restored. If a data set is not
preallocated, it is restored using the old name. This keyword only applies to
movable data sets; therefore, unmovable or ISAM data sets will not be renamed.
See Special Considerations for Restore on page 135 for details. RENAME and
RENAMEUNCONDITIONAL are mutually exclusive; you cannot specify these
keywords together.
pfx
specifies the prefix to be used to replace the first-level qualifier of the data set
name. It is optional, but if specified, must be the first parameter in the list of
subkeywords. The prefix is used only if the (on,nn) parameters are not specified or
the old name filters do not match the data set name.
on
specifies the old name to be used as filtering criteria for matching data set names
on the target volume.
nn
specifies the new name to be used to derive the new data set name if the data set
name selected by the corresponding old name filtering criteria matches the name of
a data set that already exists on the target volume.
If none of the old name filters match the data set name and the prefix is specified,
the prefix is used to derive the new name. If old name filters do not match and the
prefix is not specified, the data set is not renamed. If the old name filter matches
and there is an error in the new name filter, the data set is not renamed.
The syntax for the prefix is as follows:
Single-level, fully qualified, unquoted DSNAME.

8 characters or less.
The first character must be alphabetic or national.
The remaining characters can be alphanumeric or national.
The syntax for the old name filter is exactly like that of the INCLUDE filter, and
their rules match. For more information, see the INCLUDE keyword for the
RESTORE command, or see Filtering by Data Set Names on page 12.
Examples of valid syntax for the new name filter are:
**
Restore the data set with the old name. This provides a powerful
tool whereby some data sets can be restored with the old name
and others can be restored with the new name.
If DSNAME has one level, then restore with old name.
A.**
First level of DSNAME replaced by A.
A.B.**
First two levels of DSNAME replaced by A.B.
*.A.**
Second level of DSNAME replaced by A.
**.BCD
Last level of DSNAME replaced by BCD.
DATE.**.LIST
First and last levels are replaced by DATE and LIST.
Q.*
If DSNAME has two levels, replace the first by Q.
Q.*.B
If DSNAME has three levels, replace the first and last by Q and B.
157
RESTORE Command
*.*.SYSLIST
If DSNAME has three levels, replace the last by SYSLIST.
ABC.DEF
No asterisk in substring; replace the entire name with ABC.DEF.
Examples of invalid syntax for the new name filter are:

**.DATA.** Invalid (level to be replaced is ambiguous).
*SYS*
Invalid (a qualifier is not completely replaced).
SYS*
*SYS
SYS*TEM Invalid (a qualifier is not completely replaced).

You cannot change the number of qualifiers unless you use fully-qualified names,
for example, RENUNC((A.B.C,A.B.C.D)).
If the new name filter has errors, the data set is not restored. The new name that is
derived is truncated to fit 44 characters. If it ends with a period, that period is also
truncated.
If the new name is not fully qualified, then it must contain the same number of
qualifiers as the old name. For example, given the old name filter DATE.\\ and the
new name filter DATE.\.\.LIST, DATE.MARCH.TODAY.OLDLIST would be renamed, but
DATE.MARCH.OLDLIST would not.
GDG relative generation filtering cannot be used for old or new names.
RENAMEUnconditional
55
RENAMEUnconditional(pfx)
RENUNC
,
(6(on,nn))
((pfx),6(on,nn))
RENAMEUNCONDITIONAL specifies that the data set should be restored with the
new name, whether or not the data set exists on DASD with the old name. If the
data set exists on the volume with the new name, it is not restored.
RENAMEUNCONDITIONAL is not supported for VSAM data sets during a physical
data set restore. This keyword only applies to movable data sets; therefore,
unmovable or ISAM data sets will not be renamed. If the old name filter matches
and there is an error in the new name filter, the data set is not restored. See
Special Considerations for Restore on page 135 for details.
Notes:
1. RENAME and RENAMEUNCONDITIONAL are mutually exclusive; you cannot
specify these keywords together. RENAMEUNCONDITIONAL is not supported
for physical restore of VSAM data sets, and, if specified, the data sets will not
be restored.
2. RENAMEUNCONDITIONAL specifies that the data set must be restored with
the new name, regardless of whether the data set exists on DASD with the old
name. If the data set exists on the target volume with the new name, an
allocation error occurs and the data set is not restored, regardless of whether
REPLACE is specified.
158
RESTORE Command
pfx
specifies the prefix used to replace the first-level qualifier of the data set name. It is
optional but, if specified, must be the first parameter in the list of subkeywords. The
prefix is used only if the (on,nn) parameters are not specified or the old name filters
do not match the data set name.
on
specifies the old name to be used as a filtering criterion to check if it matches the
data set name.
nn
specifies the new name to be used to derive the new data set name if the data set
name matches the corresponding old name filtering criterion.
For syntax rules, see the discussion of pfx, on, and nn under REName on
page 156.
REPlace
55
REPlace
REPLACE specifies that if the data set exists on DASD, it can be replaced with the
data set from the source volume. DFSMSdss first searches for a catalog entry for
the data set. If no entry is found, DFSMSdss then searches the output volumes for
preallocated data sets. If no output volumes are specified, DFSMSdss searches the
volumes on which the data set resided at dump time. If no preallocated target is
found, DFSMSdss attempts to allocate a data set. If allocation is successful, the
data set is restored. PURGE is accepted and is treated the same as REPLACE.
REPLACE only works if the data set is not being renamed.
For non-VSAM data sets, if the target data set is smaller than the source data set,
DFSMSdss scratches the target data set and reallocates it with the size of the
source data set.
Notes:
1. REPLACE must be specified to restore preallocated data sets.
2. If the source data set is an extended-addressable VSAM KSDS, then the target
must also be an extended-addressable VSAM KSDS.
3. If REPLACE is specified with the RESTORE command, the classes already
associated with the preallocated data set remain the same. See Special
Considerations for Restore on page 135 for more information.
4. CATALOG and RECATALOG are ignored for preallocated data sets.
5. The target data set name must match the source data set name.
SHAre
55
SHAre
SHR
159
RESTORE Command
SHARE specifies that DFSMSdss is to share, for read access with other programs,
the data sets that are to be restored. The resetting of the data set change indicator
is bypassed if SHARE is specified on a data set restore operation.
SHARE and FULL are mutually exclusive; you cannot specify these keywords
together.
SPHERE
55
SPHERE
SPHERE specifies that for any VSAM cluster dumped with the SPHERE keyword,
DFSMSdss must also restore all associated AIX clusters and paths. Individual
sphere component names need not be specified; only the base cluster name is
required.
Notes:
1. If an AIX is dumped without the SPHERE keyword, during a restore DFSMSdss
treats the AIX as a normal VSAM KSDS.
2. The base cluster name must be specified to process the entire sphere. If the
SPHERE keyword is specified but the base cluster name is not, none of the
associations will be processed.
3. The SHARE keyword is not honored for VSAM data sets. Exclusive control is
obtained for VSAM data sets even if the SHARE keyword is specified. Neither
read access nor write access by other programs is allowed while the VSAM
data set is being restored, regardless of the share options defined for the data
set.
STORCLAS
55
NULLSTORCLAS
NSC
STORCLAS specifies the user-desired storage class that is to replace the source
storage class as input to the ACS routines. The user must have the proper RACF
authorization for the storage class specified. The keyword itself does not require
authorization.
NULLSTORCLAS/NSC specifies that the input to the ACS routines is to be a null
storage class rather than the source data sets storage class.
STORCLAS and NULLSTORCLAS are mutually exclusive.
Note: If BYPASSACS(dsn) is specified, all data sets that pass the BYPASSACS
selection criteria are guaranteed the specified storage class. The
combination of NULLSTORCLAS and BYPASSACS(dsn) forces the
selected data sets to be non-SMS managed.
160
RESTORE Command
TGTAlloc
TGTAlloc(SOURCE)
55
TGTAlloc(BLK)
CYL
TRK
SOURCE
SRC
TGTALLOC specifies, during a logical data set restore function, how DFSMSdss
will allocate the target data set.
BLK
specifies to allocate by blocks.
CYL
specifies to allocate by cylinders.
TRK
specifies to allocate by tracks.
SOURCE/SRC
specifies to allocate with the same space allocation type as that of the source data
set.
Notes:
1. If the TGTALLOC keyword is omitted, the target allocation defaults to source.
2. If SRC is specified and if the source data set is allocated by track or if TRK is
specified, then the final VSAM allocation might be different from the requested
one because of VSAM allocation rules.
3. If BLK is specified for VSAM data sets, TRK is used instead. The final VSAM
allocation can be different from the requested one because of VSAM allocation
rules.
TGTGDS
TGTGDS(DEFERRED)
55
TGTGDS(DEFERRED)
ACTIVE
ROLLEDOFF
SOURCE
SRC
TGTGDS specifies in what status, during a data set operation, that DFSMSdss is to
place nonpreallocated SMS-managed GDG data sets.
DEFERRED
specifies that the target data set is to be assigned the DEFERRED status.
ACTIVE
specifies that the target data set is to be assigned the ACTIVE status, for example,
rolled into the GDG base.
ROLLEDOFF
specifies that the target data set is to be assigned the rolled-off status.
161
RESTORE Command
SOURCE/SRC
specifies that the target data set is to be assigned the same status as that of the
source data set.
Notes:
1. If the TGTGDS keyword is omitted, the target data set is assigned the
DEFERRED status.
2. The requested target status of generation data sets must not violate generation
data group rules.
TOLerate
55
TOLerate(ENQFailure)
ENQFailure
specifies that target data sets are to be processed even though shared or exclusive
access fails. TOL(ENQF) and FULL or TRACKS are mutually exclusive; you cannot
specify these keywords together.
TRACKS
55
,,c1,max head#
6
TRACKS((c1))
TRKS
,c1,max head #
,h1
,max head #
,c2
,h2
TRACKS specifies ranges of tracks to be restored (that is, a tracks restore

operation). If any of the requested tracks are not in the input file, the restore
operation is stopped. Refer to the DFSMS/MVS DFSMSdss Storage Administration
Guide for additional information on using TRACKS during physical processing.
c1,h1
c2,h2
Notes:
1. The c2 must be greater than or equal to c1.
2. If c2 equals c1, h2 must be greater than or equal to h1.
example:
162
RESTORE Command
Specified Results
None
c1
c1,h1
c1,h1,c2
c1,,c2
,h1
Syntax error
Syntax error
Syntax error
Data Integrity Note: It is possible to duplicate a volume serial number during a

restore TRACKS operation. Follow the procedure in Data Integrity
Considerations for Full or Tracks Restore Operations on page 136 to
maintain data integrity when restoring a volume with TRACKS restore.
TTRAddress
55
6dsn)
TTRAddress(
TTRADDRESS identifies the direct access data sets whose names match the fully
or partially qualified names specified (dsn). These direct access data sets are
organized by TTR rather than by relative block addressing and are to be processed
track by track. The target device track capacity must be equal to or greater than the
source.
Notes:
1. If a direct access data set is specified by both the RELBLOCKADDRESS and
the TTRADDRESS parameters, the data set is not processed. Refer to the
RELBLOCKADDRESS keyword for more information.
AUTORELBLOCKADDRESS keyword processing for the specified data sets
(dsn).
VOLcount
VOLcount(\)
55
VOLcount(SRC)
N(nn)
ANY
VOLCOUNT specifies the method DFSMSdss uses to determine the number of

volumes (volume count) for allocating the SMS target data set for a logical data set
restore of VSAM or non-VSAM data sets.
*
is the default and specifies that DFSMSdss determine the volume count for
If the source data set is a single-volume data set, one volume is allocated.
If the source data set is a multivolume data set and either a list of volumes is
not specified to DFSMSdss through OUTDDNAME or OUTDYNAM, or there are
no SMS volumes in the list, DFSMSdss allocates the same number of volumes
that were in the multivolume source data set.
163
RESTORE Command
If the source data set is a multivolume data set and a volume list is specified
through OUTDDNAME or OUTDYNAM, the volume count is the number of
SMS volumes in the list.
SRC
specifies that DFSMSdss rely on the source volume count to determine the number
of volumes to allocate for the target data set as follows:
If no output volume list is specified, DFSMSdss allocates the same number of
volumes that the source data set had.
If a volume list is specified through OUTDDNAME or OUTDYNAM, the volumes
in the list that are SMS-managed must be in the same storage group, and the
allocation must be directed to that storage group.
N(nn)
nn represents the number of volumes to be used for SMS data set allocation. Any
value between 0 and 59 may be specified with the following conditions:
If nn is not zero and a volume list is specified through OUTDDNAME or
volume list or nn, whichever is less.
If nn is zero and a volume list is specified through OUTDDNAME or
volume list or the number of volumes that were allocated for the source data
set, whichever is less.
If a volume list is specified through OUTDDNAME or OUTDYNAM and there
are no SMS volumes in the list, or there is no volume list, DFSMSdss allocates
either the number of volumes used by the source data set or nn, whichever is
more.
ANY
specifies that DFSMSdss use a maximum volume count to allocate the SMS target
data set as follows:
DFSMSdss initially sets a volume count of 59 for the allocation.
If the data set is allocated on more volumes than were used to allocate the
source data set, DFSMSdss reduces the number of volumes used to the
number of primary volumes needed to satisfy the allocation.
If the data set is allocated on the same number or fewer volumes than were
used to allocate the source data set, DFSMSdss reduces the number of
volumes used to the number of volumes used for allocation of the source data
set.
164
RESTORE Command
Notes:
|
|
|
|
|
|
1. VOLCOUNT does not convert single-volume data sets whose organization is

partitioned into multivolume data sets, excluding HFS data sets. Furthermore,
any partitioned data set that was allocated in JCL as multivolume is allocated
as single-volume in DFSMSdss. This includes PDS and PDSE data sets,
single-volume data sets whose organization is undefined, and empty
non-VSAM single-volume data sets.
2. VOLCOUNT does not change the number of volumes for KSDS data sets.
3. VOLCOUNT does not increase the number of volumes allocated for linear data
sets.
4. VOLCOUNT(ANY) does not support keyed VSAM data sets that have an
imbedded index. If VOLCOUNT(ANY) is specified and a data set has an
imbedded index, the data set is processed as if VOLCOUNT(*) were specified.
5. Guaranteed space is not honored when VOLCOUNT(ANY) is used.
6. VOLCOUNT(ANY) does not support any type of multi-striped data set (physical,
sequential, extended, or VSAM). If VOLCOUNT(ANY) is specified and a data
set is multi-striped, the data set is processed as if VOLCOUNT(*) were
specified.
You can override VOLCOUNT keyword settings with the options installation exit
routine, as described in DFSMS/MVS Installation Exits.
WAIT
WAIT(2,2)
55
numsecs
is a decimal number (0255) that specifies the time interval, in seconds, between
retries.
numretries
numretries.
in a total wait time of 90 seconds. Refer to the DFSMS/MVS DFSMSdss
system resources.
165
WRItecheck
55
WRItecheck
WRC
WRITECHECK specifies that the data restored is to be verified for successful

completion. This keyword increases the overall elapsed time. The default is no
WRITECHECK.
Note: The WRITECHECK keyword is not supported for extended-sequential data
sets.
DFSMSdss RESTORE Process

Table 4 describes, in decision table format, DFSMSdss restore actions for physical
processing of SMS-managed data sets. The specified RESTORE command
keywords and the existence of the data set are shown in the upper half. The
actions taken are shown in the lower half.
Table 4. Physical Data Set Restore Actions on SMS-Managed Data Sets
Non-VSAM Physical Restore
RENAME
N N Y Y Y Y
N N Y
Y Y
RENUNC
N N
Y Y Y Y N N
Y Y N N N
REPLACE
Y Y N N Y Y N N Y Y N N N X
OLD DATA SET EXISTS
Y N Y N Y N Y N Y N Y N Y X Y N Y N Y Y N
NEW NAME ON
VOLUME
Overlay old data set
ALLOC with new name on

USERVOL and restore
T T
ALLOC with old name
T T T
Do not restore
T T
N X N
VSAM Physical
Restore
N N N
Y N
Y Y
T T T
T T T T
Legend:
Y = Yes
T = Action taken
N = No
X = Doesn't matter
= Not Applicable
Figure 3 on page 167 describes general DFSMSdss actions for both physical and
logical restore on non-VSAM data sets. It is not a program flowchart. Use it to
clarify the restore actions on non-VSAM data sets under varying conditions.
166
START
Yes
RENUNC
Specified
No
Yes
B
Data set
on volume
No
Yes
RENAME
Specified
Data set
is SMS
No
Allocate data
set and restore
Yes
Match
on oldname
filter
No
No
Data set
in catalog
REPLACE
Specified
Derive
new name
from filter
Yes
Error
on newname
definition
No
No
Prefix
Specified
Yes
Yes
Yes
No
Yes
No
Yes
RENAME
Specified
Overlay the
data set
Derive
new name
from prefix
No
Cataloged
data set
is SMS
Is
newname
on volume
already
No
Yes
REPLACE
Specified
Yes
No
No
Allocate using
newname and
Restore
Yes
Overlay the
data set
ADR1SR01
(Do Not Restore Data Set)

Continue with
next data set
Figure 3. Restore Actions on Non-VSAM Data Sets. These actions apply to a data set RESTORE command with
RENAME, RENAMEUNCONDITIONAL, and REPLACE keywords.
167
RESTORE Command
Assignment of Class Names by Using the RESTORE and COPY

Commands
In an SMS environment, you can use STORCLAS, MGMTCLAS, NULLSTORCLAS,
NULLMGMTCLAS, and BYPASSACS keywords with the RESTORE and COPY
commands to influence the class names assigned to a data set. Figure 4 shows
how these keywords can influence the storage and management class names of
the target data set in a restore or copy operation. However, Figure 4 only
addresses how the management and storage class names are assigned, not how
the storage group name is assigned or how volumes are selected. Refer to
DFSMS/MVS DFSMSdss Storage Administration Guide for information about how
target volumes are selected during restore and copy functions.
|
|
|
|
Source
data set
classes
No
MGMTCLAS
STORCLAS
NULLSTORCLAS
and/or
NULLMGMTCLAS
Yes
User
specified
classes
Source
classes
Yes
No
BYPASSACS
NULLSTORCLAS
Target
data set
classes
END
Figure 4. DFSMSdss Target Class Selection
168
Yes
No classes
assigned
ADR1SR02
No
ACS
routines
RESTORE Command
Notes to Figure 4:
If you specify BYPASSACS, the source data sets class names or the class
names specified with STORCLAS and MGMTCLAS are assigned to the target
data set. If you do not specify BYPASSACS, ACS uses the source data sets
class names, or the class names specified with STORCLAS and MGMTCLAS
as input to assign the target data sets class names.
If you specify NULLSTORCLAS, DFSMSdss passes a null storage class to
ACS, which selects a storage class for the data set. If you specify
NULLSTORCLAS and BYPASSACS together, the data set becomes non-SMS
managed.
NULLMGMTCLAS can only be used with SMS-managed data sets. Specifying
NULLMGMTCLAS and BYPASSACS together causes the removal of the
original management class of the data set.
Examples of Full and Tracks Restore Operations

Example 1 shows that DASD volume 111111 is to be restored from the first data
set of standard label tape volumes TAPE01 and TAPE02.
The command input to be substituted for a full and tracks restore operation are
shown below in Example 1A and 1B respectively. To dump the same volume, refer
to Examples 1, 1A, and 1B of the DUMP command.
Example 1:
//JOB1
JOB
//STEP1
EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=A
//TAPE
DD
UNIT=348,VOL=SER=(TAPE1,TAPE2),
// LABEL=(1,SL),DISP=(OLD,KEEP),DSNAME=USER2.BACKUP
//DASD
DD
//SYSIN
DD
\
command input (see Examples 1A and 1B below)
/\
Example 1A: A Full Restore Operation

RESTORE
INDDNAME(TAPE) OUTDDNAME(DASD) PURGE
Example 1B: A Tracks Restore Operation

RESTORE
TRACKS(1,,1,5) INDDNAME(TAPE) OUTDDNAME(DASD) PURGE
Example 1C: A Tracks RESTORERestore to Different Tracks
169
RESTORE Command
//JOBTRKS JOB
//STEP1
EXEC PGM=ADRDSSU
//TAPE
DD
// LABEL=(1,SL),DISP=(OLD,KEEP),DSN=USER2.BACKUP
//SYSPRINT DD
SYSOUT=A
//SYSIN
DD
\
RESTORE INDD(TAPE) OUTDYNAM(338) TRKS(2,1,2,1) /\ INPUT TRK 2,1 ON SOURCE VOL\/
OUTTRKS(1,)
/\RESTORE TO 1, ON TARGET VOL \/
PURGE
/\ OK TO OVERLAY THE TRK
\/
/\ EVEN IF UNEXPIRED DATA SET AT THE LOCATION \/
PSWD(ABC/WRITPSWD) /\ PASSWORD FOR THE DATA SET
\/
/\
A track of dump data is restored to a cylinder and head number other than that
from which it was dumped. The dump tape (which might have resulted from a full,
tracks, or data set dump operation) contains a track dumped from cylinder 200
head 10 that is restored to cylinder 100 head 0.
Examples of Physical Data Set Restore Operations

Example 2 specifies that data sets on standard label tape volume TAPE02 are to
be restored to DASD volume 111111.
Examples 2A through 2D below complement Examples 2A through 2G in
Examples of Physical Data Set Dump Operations on page 112 in any
combination. For example, the dump tape produced in Example 2C in DUMP
Command can be used as the input tape for Example 2A below.
Example 2:
//JOB2
JOB
//STEP1
EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=A
//TAPE
DD
//DASD1
DD
//SYSIN
DD
\
command input (see Examples 2A, 2B, ... below)
/\
Example 2A: Using the INCLUDE Subkeyword to Restore All

Data Sets on a Dump Tape
RESTORE
INDDNAME(TAPE) OUTDDNAME(DASD1) DATASET(INCLUDE(\\))
Example 2B: Using the INCLUDE and EXCLUDE Subkeywords

RESTORE
INDDNAME(TAPE) OUTDDNAME(DASD1) DATASET(INCLUDE(\\) EXCLUDE(\\.LIST))
All data sets are restored, except those ending with a qualifier of LIST.
170
RESTORE Command
Example 2C: Using the INCLUDE, EXCLUDE, and BY

Subkeywords
RESTORE
INDDNAME(TAPE) OUTDDNAME(DASD1) DATASET(INCLUDE(\\) EXCLUDE(\\.LIST) BY((EXPDT,LE,845)))
All data sets that satisfy the BY subkeyword except those specified in the
EXCLUDE subkeyword are restored.
Example 2D: With Filtering Data in a Data Set

RESTORE
INDDNAME(TAPE) OUTDDNAME(DASD1) DATASET(FILTERDD(A1))
Note to Example 2D: The following DD statement must be added to the JCL
shown in Example 2:
//A1
DD
DSNAME=USER2.FILTER,DISP=SHR
This cataloged data set (USER2.FILTER) contains three card-image records. The
information shown below is positioned in columns 2 through 72 of each record:
INCLUDE(\\) EXCLUDE(\\.LIST) BY((DSCHA,EQ,1))
Example 2E: Using the LOGICALVOLUME and REPLACE

Keywords
RESTORE
INDDNAME(TAPE) OUTDDNAME(DASD1) DATASET(INCLUDE(\\)) LOGICALVOLUME(111111) REPLACE
Although the dump tape contains data sets from source volumes 111111 and
222222, only the data sets from source volume 111111 are restored. If preallocated
data sets exist on the volume, DFSMSdss replaces them. Unmovable data sets that
are not preallocated are not restored.
Example 2F: Using the REPLACE and RENAME Keywords

RESTORE
INDDNAME(TAPE) OUTDDNAME(DASD1) DATASET(INCLUDE(\\)) LOGICALVOLUME(111111) REPLACE RENAME((USER2),(USER4.\\,USER3.\\))
In the above example, renaming takes place only for data sets that exist on DASD
with the old name. Data sets with a first-level qualifier of USER4 are renamed to a
first-level qualifier of USER3. The first-level qualifiers of all other data sets are
replaced by USER2. Unmovable data sets are not renamed.
Example 2G: Using the REPLACE and

RENAMEUNCONDITIONAL Keywords
RESTORE
INDDNAME(TAPE) OUTDDNAME(DASD1) DATASET(INCLUDE(\\)) LOGICALVOLUME(111111) REPLACE RENAMEUNCONDITIONAL((USER2),(\.PEAR.\\,\.PLUM.\\), (MY.SPECIFIC.DS,YOUR.ANY))
171
RESTORE Command
RENAMEUNCONDITIONAL is used for movable data sets; REPLACE is used for

unmovable data sets. With the RENUNC keyword, movable data sets are renamed
whether or not they exist on DASD with the old name. In the example, data sets
with a second-level qualifier of PEAR are renamed by using a second-level qualifier
of PLUM. MY.SPECIFIC.DS is renamed as YOUR.ANY. The first-level qualifier of
all other movable data sets is changed to USER2. Unmovable data sets are not
renamed.
Example 2H: Restore for All Data Sets

RESTORE
INDDNAME(TAPE) OUTDDNAME(DASD1) WAIT (1,99) DATASET(INCLUDE(\\))
Example 2H shows you what to do if the data sets are in use for a short time
interval during a restore operation. DFSMSdss waits for a second at a time and
retries as many as 99 times if the data set is in use by another job.
Example 2I: Restore Data Sets

RESTORE INDDNAME(TAPE) OUTDDNAME(DASD1) DATASET(INCLUDE(\\)) TOL(ENQF) WAIT(,)
In Example 2I, DFSMSdss tries to serialize (ENQ) each data set. If the ENQ fails,
DFSMSdss does not wait (WAIT(0,0)), and the data set is processed without
serialization or enqueuing (TOL(ENQF)).
Examples of Logical Data Set Restore Operations

The following are examples of logical data set RESTORE operations.
Example 1: A Logical Data Set RESTOREOutput Volumes Not

Specified
//JOB5
JOB
//STEP1
EXEC PGM=ADRDSSU
//TAPE
DD
//SYSPRINT DD
SYSOUT=A
//SYSIN
DD
\
RESTORE INDD(TAPE)
DS(INCL(USER1.MULTVOL)) REPLACE
/\
In Example 1, data set USER1.MULTVOL is restored. The location to which it is to
be restored is not given. This RESTORE statement also applies when the data set
has been scratched inadvertently after the dump operation. A multivolume data set
is restored to the volumes from which it was dumped, provided the data set is
preallocated on the output volumes. If it is not preallocated, the data set is restored
to the first volume from which it was dumped that has adequate space to restore
the data set as a single-volume data set.
The RESTORE statement can be modified as follows to support multiple restores of
both single and multivolume data sets from dump tapes:
172
RESTORE Command
//SYSIN
DD
\
RESTORE INDD(TAPE)
DS(INCL(USER1.CNTL.\\))
REPLACE
/\
/\ RESTORE
\/ /\ USERS CONTROL DATA SETS
\/ /\ OVERLAY DATA SETS IF THEY EXIST \/
Example 2: A Logical Restore of an Unmovable Data Set

//JOB6
JOB
//STEP1
EXEC PGM=ADRDSSU
//TAPE
DD
//SYSPRINT DD
SYSOUT=A
//SYSIN
DD
\
RESTORE INDD(TAPE) OUTDYNAM(338) DS(INCL(HIGH.PERF))
FORCE
/\ TO FORCE RESTORE OF UNMOVABLE DATA SET \/
/\
The unmovable data set, HIGH.PERF, does not exist on volume 338000. This data
set existed on volume 338000 at the time of dump. The location, relative to the
beginning of the volume, where this data set is to be restored is occupied by other
data sets. The data set is restored to another place on the volume because the
FORCE keyword is specified. The data set is marked as unmovable on volume
338000 because either:
You do not want DFSMShsm to move it to an unlike device type.
You do not want the data set to be relocated by a DEFRAG operation for
performance reasons.
It was allocated as an ABSTR data set for performance reasons.
Example 3: A Logical Data Set Dump, Followed by a Restore to

an Unlike Device
//JOB1
//STEP1
EXEC PGM=ADRDSSU
//TAPE
DD
UNIT=348,VOL=TAPE1,
//SYSPRINT DD
SYSOUT=A
//SYSIN
DD
\
DUMP DATASET(INCL(USER2.OLDDS)) OUTDD(TAPE)
/\
//JOB2
//STEP1
EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=A
//TAPE
DD
UNIT=348,VOL=TAPE1,
//DASD
DD
//SYSIN
DD
\
RESTORE DATASET(
INCLUDE(USER2.OLDDS) ) INDDNAME(TAPE) OUTDDNAME(DASD) RENAME(\.OLDDS,\.NEWDS)
/\
173
RESTORE Command
In the first part of example 3, DFSMSdss dumps a cataloged data set

(USER2.OLDDS) from the source volume to an IBM standard label dump tape
(TAPE01). Next, DFSMSdss restores USER2.OLDDS from TAPE01 to a 3380
target volume (DASD volume 222222). The RENAME keyword is used to change
the name of the data set to USER2.NEWDS.
Example 4: Dump/Restore for Converting to SMS

//JOB1
//STEP1
EXEC PGM=ADRDSSU
//SYSPRINT DD
SYSOUT=\
//DTAPE1
DD
DISP=(,CATLG),DSN=V3381.USER3.BACKUP,
//
LABEL=(1,SL),UNIT=348,VOL=SER=TAPE1
//SYSIN
DD
\
DUMP DS(INC(\\)) LOGINDYNAM ( (3381) ) DELETE PURGE COMPRESS OUTDDNAME (DTAPE1)
/\
This part of the example dumps all the single-volume data sets on the non-SMS
volume 338001 to TAPE01 with the DELETE option. The DELETE and PURGE
keywords are required to avoid duplications in the restore operation.
//SYSPRINT DD
SYSOUT=\
//DTAPE1
DD
DISP=(OLD,KEEP),DSN=V3381.USER3.BACKUP,
//
LABEL=(1,SL),UNIT=348,VOL=SER=TAPE1
//SYSIN
DD
\
RESTORE DS(INC(\\)) STORCLAS(SC1MJA1) INDDNAME (DTAPE1)
/\
This second part of the example restores all of the data sets that were dumped in
the first half of this example. Because no output volume is specified, most of the
data sets will be allocated on SMS volumes throughout the system. The
STORCLAS keyword indicates that the storage administrator wants the data sets to
have a storage class of SC01MJA1. The ACS routines might or might not assign
the target data sets the storage class specified. All data sets not converted to SMS
(ACS STORCLAS routine returns a null storage class) will be restored to the
original volume.
Example 5: Using the RENAME Keyword to Restore a VSAM

Data Set
174
RESTORE Command
//JOB3
JOB
//STEP1
EXEC PGM=ADRDSSU
//TAPE
DD
//SYSPRINT DD
SYSOUT=A
//SYSIN
DD
\
RESTORE INDD(TAPE) OUTDYNAM(338) DS(INCL(PARTS.VSAM1))
RENAME(\.VSAM1,\.VSAM2)
CATALOG
/\
A VSAM key-sequenced data set, PARTS.VSAM1, is restored from a logical dump
tape in this example. It is renamed as PARTS.VSAM2 and cataloged in the
standard order of search. The clusters components, PARTS.VSAM1.DATA and
PARTS.VSAM1.INDEX, are also renamed.
Example 6: Using the RECATALOG Keyword

//JOB4
JOB
//STEP1
EXEC PGM=ADRDSSU
//TAPE
DD
//SYSPRINT DD
SYSOUT=A
//SYSIN
DD
\
RESTORE INDD(TAPE) OUTDYNAM((3381),(3382)) DS(INC(PARTS.\\))
/\ OR DS(INC(\\))
\/
PCTU(8)
RECATALOG(USERCAT2)
TGTALLOC(SOURCE)
/\
In this example, data sets with a first-level qualifier of PARTS were dumped
logically. All are restored to volume 338001 and cataloged in catalog USERCAT2.
These data sets were on volume 338000 at the time of dump. If the data sets do
not fit on volume 338001, a spill volume 338002 is specified. To ensure that the
data sets on volume 338001 can be extended, 20% of the total space on volume
338001 is to be left as free space (PCTU(80)). TGTALLOC(SOURCE) specifies
that the data sets are to be restored with the same allocation type they had when
they were dumped.
175
RESTORE Command
176
SyntaxAuxiliary Commands
Chapter 4. SyntaxAuxiliary Commands

This chapter describes the following auxiliary commands you can use to further
refine DFSMSdss processing:
Write-to-Operator (WTO)
SERIAL
PARALLEL
SET
IF-THEN-ELSE
EOJ
Writing to the Operator with the WTO Command

The WTO (write to operator) command lets you write a message to the system
console. You can use it, for example, to allow the mounting of a required volume or
to stop other jobs in the system before continuing processing of your DFSMSdss
job. The message is limited to 72 characters. The command syntax is:
55WTO 'message'5%
DFSMSdss does not prefix the message with a message ID. You can, however,
supply a message ID as part of the message text.
The following routing codes will be assigned to the message:
2
11
Master console information

Programmer information
The following descriptor code is assigned to the message:

3
Event action required
When a WTO command is encountered, DFSMSdss waits until the last-requested

function command completes before issuing the WTO command.
Scheduling Tasks
You can use the SERIAL or PARALLEL commands to schedule tasks. The SERIAL
or PARALLEL command must precede the commands to be executed in the
SERIAL or PARALLEL mode.
SERIAL Command
The SERIAL command lets you re-initiate serial task scheduling (only one task at a
time) after you have used parallel task scheduling. Tasks are processed in the
order in which they appear in the input stream.
If neither the SERIAL nor PARALLEL command has been issued, SERIAL is the
default. The command syntax is:
55SERial5%
177
PARALLEL Command
The PARALLEL command lets you initiate parallel task scheduling; that is, two or
more tasks are processed concurrently, provided the required system resources
(such as virtual storage, DASD, or tape volumes) are available. The commands
may not necessarily be processed in the order in which they appear in the input
stream. The command syntax is:
55PARallel5%
If you switch from SERIAL to PARALLEL mode or vice versa, DFSMSdss waits for
all previously scheduled tasks to be completed before switching modes. If the
PARALLEL mode is specified but required system resources are not available,
some tasks may be delayed in processing until the resources are available (that is,
until other tasks have ended). If DFSMSdss is in PARALLEL mode, an IF statement
ensures that all prior commands are processed.
Controlling Task Processing

With the IF-THEN-ELSE, SET, and EOJ commands, you can direct DFSMSdss
through a logical path in your command sequence, based on the condition (return)
codes of previously completed operations.
Condition Codes
The following condition codes are tested in the IF-THEN-ELSE command
sequence:
0 The function was processed as expected. Informational messages may have
been issued.
4 A problem occurred, but processing continued. The result may not be exactly
what you wanted, but no permanent harm was done. A warning message was
issued.
8 A function did not process, began processing but ended prematurely, or the job
ran without processing all requested functions. An error message is issued. If an
abend occurs in any of the DFSMSdss subtasks, the return code is set to 8.
12 The job did not process. No functions were processed.
16 A function processed and left at least one volume or data set in an unusable
condition. For example, a full-volume dump operation ended prematurely,
leaving the output tape in an unusable condition.
If you are running a batch job, the condition codes that are tested in the
IF-THEN-ELSE command sequence and that can be set by the SET command
cannot be passed from one job step to the next. However, the final maximum
condition code is passed to the MVS system when DFSMSdss returns control to
the system at the completion of step processing.
178
Setting Condition Codes

With the SET command, you can set the LASTCC and MAXCC variables to any
value from 0 to 16, inclusive. By doing this, you can influence the logical path
DFSMSdss takes in the command sequence following the SET command.
Attention: Do not use SET LASTCC before the first function command.
The condition code of the last-requested operation (LASTCC) and the maximum
code of all completed operations (MAXCC) can be determined with an IF
command. When an IF MAXCC or SET MAXCC command is encountered,
DFSMSdss waits for all previously requested function commands to complete
before the highest return code is determined. Also, when an IF LASTCC or SET
LASTCC command is encountered, DFSMSdss waits for the last-requested function
command to complete before the return code is determined. After the return code is
determined and if the condition code is tested and satisfied, DFSMSdss ends the
command or commands following the THEN keyword. If the tested condition is not
satisfied, DFSMSdss bypasses the command or commands following the THEN
keyword.
SET Command
The syntax of the SET command is:
55SETMAXCC=number5%
LASTCC=number
SET
specifies that MAXCC or LASTCC is to be set to a new condition-code value.
A SET command that occurs within an unprocessed THEN or ELSE clause is
not processed.
MAXCC
specifies that the variable MAXCC is to be set to a new condition-code value.
Setting MAXCC does not affect the value of LASTCC.
LASTCC
specifies that the variable LASTCC is to be set to a new condition-code value.
If the value assigned to LASTCC is higher than the value of MAXCC, MAXCC
is also set to the higher value.
number
specifies the value to be assigned to MAXCC or LASTCC. The maximum value
that can be assigned is 16; a higher value is reduced to 16.
Examples of Controlling Tasks for the SET Command: The examples that
follow show the use of the SET command.
To set the last condition code established to 12, specify:
SET LASTCC=12
To replace the highest condition code established in processing so far with 8,
specify:
SET MAXCC=8
179
Using Condition Codes

Condition codes are used to set up the IF-THEN-ELSE statements. LASTCC
specifies a comparison to the last condition code and MAXCC specifies the
maximum condition code for comparison.
Using the IF-THEN-ELSE Command Sequence

The syntax of the IF-THEN-ELSE command sequence is:
55IFLASTCCopnumberTHENcommand5
MAXCC
6commandEND
DO
55%
ELSEcommand
6commandEND
DO
IF specifies that a comparison is to be made. The outcome determines which
logical path (in your command sequence) DFSMSdss takes.
LASTCC
specifies that LASTCC (condition code of the last-requested function, such as
COMPRESS, CONVERTV, COPY, COPYDUMP, DEFRAG, DUMP, PRINT,
RELEASE, RESTORE) is to be compared to a specified number.
MAXCC
specifies that MAXCC (maximum condition code of all completed operations) is
to be compared to a specified number. MAXCC is initialized to zero upon entry
to DFSMSdss.
op specifies an operator that describes the comparison to be made between the

condition code specified by LASTCC or MAXCC and the number that follows
the operator. This may be any one of six possible comparisons:
EQ or =
Equal to
LE or <=
Less than or equal to
LT or <
Less than
GT or >
Greater than
GE or >= Greater than or equal to

NE or = Not equal to
number
specifies the decimal integer that is to be compared with MAXCC or LASTCC.
Values greater than 16 are reduced to 16.
THEN
specifies that a single command or a group of commands (enclosed by DO and
END) is to be processed if the tested condition is satisfied. THEN can be
followed by another IF command.
ELSE
specifies that a single command or a group of commands (enclosed by DO and
END) is to be processed if the tested condition is not satisfied. ELSE can be
followed by another IF command. The ELSE clause cannot be on the same line
180
as the THEN clause nor on the same line as the continuation of the THEN
clause.
DO
specifies that the group of commands that follows is to be treated as a single
unit, that is, to be processed as a result of a single IF command. The set of
commands is ended by END. A command following a DO must begin on a new
line.
END
specifies the end of a set of commands initiated by the nearest unended DO.
END must be on a line by itself.
Creating a Null Command

If THEN or ELSE is not followed by a continuation character or by a command on
the same line, the result is a null command. A semicolon after the THEN or ELSE
keyword also results in a null command. A null command specifies that no action is
taken if the IF clause is satisfied (a null THEN command) or if the IF clause is not
satisfied (a null ELSE command).
To specify a null THEN command, specify:
IF ... THEN
ELSE ...
or
IF ... THEN;
ELSE ...
To specify a null ELSE command, specify:

IF ... THEN ...
ELSE
or
IF ... THEN ...

ELSE;
Continuation Rules for IF-THEN-ELSE Command Sequencing

The following continuation rules apply for the IF-THEN-ELSE command
sequencing.
1. IF (condition) must be followed by a THEN on the same line or a continuation
of that line.
Examples:
IF LASTCC = THEN COPYDUMP ...
or
IF LASTCC =
THEN COPYDUMP ...
2. THEN must be followed by a command or DO on the same line or a
continuation of that line.
Examples:
IF LASTCC =
THEN
COPYDUMP ...
or
IF LASTCC =
THEN DO
COPYDUMP ...
PRINT ...
END
181
3. ELSE must be the first word on a line and no continuation character should be
used on the preceding line.
Example:
IF LASTCC =
THEN
COPYDUMP ...
PRINT ...
ELSE
Nesting IF Commands
An IF command in a THEN or ELSE clause is a nested IF command. The
maximum level of nesting is 10, starting with the first time you specify IF.
Within a nest of IF commands, the innermost ELSE clause is associated with the
innermost THEN clause, the next innermost ELSE clause with the next innermost
THEN clause, and so on. If there is an IF command that does not require an ELSE
clause, use a null ELSE clause (see Creating a Null Command on page 181),
unless the nesting structure does not require one. If a nesting structure does not
require a null ELSE clause, the DFSMSdss job stream tells you.
Examples of Controlling Task Processing for the IF-THEN-ELSE

Command
The following are examples of controlling task processing for the IF-THEN-ELSE
command.
Example 1: Nested IF commands are used to determine whether a COPYDUMP,

EOJ, or PRINT command is to be processed:
IF LASTCC > 4 THEN IF MAXCC < 12 THEN COPYDUMP ...
ELSE EOJ
ELSE IF LASTCC = 4 THEN
ELSE PRINT...
If the value of LASTCC is greater than 4, the value of MAXCC is to be tested. If the
value of MAXCC is less than 12, the COPYDUMP command is processed,
Otherwise, the EOJ command is processed. If LASTCC is 4, no action is taken. If
LASTCC is less than 4, the PRINT command is processed.
Example 2: Nested IF commands are used to determine whether a COPYDUMP

or a PRINT command is to be processed:
IF LASTCC > 4 THEN IF MAXCC < 12 THEN COPYDUMP ...
ELSE
ELSE IF LASTCC = 4 THEN PRINT ...
If the first IF clause finds that LASTCC is greater than 4 and the second IF
command finds that MAXCC is 12 or greater, no function command is processed.
The null ELSE command specifies that the next ELSE corresponds to the first
THEN.
182
Common Continuation Errors

The continuation rules, described in Chapter 1, Specifying DFSMSdss Commands
on page 1, must be followed carefully when auxiliary commands, comments, or
blank records appear in your input. You must also be careful not to inadvertently
specify a null clause when continuing auxiliary commands.
The following examples show common continuation errors.
Error Example 1:
IF LASTCC = THEN
PRINT ...
A continuation character (hyphen) is missing after THEN; consequently, a null
THEN clause is assumed. The PRINT command is unconditionally processed.
Error Example 2:
IF LASTCC = THEN COPYDUMP ...
/\ ALTERNATE PATH \/
ELSE PRINT ...
Because no continuation character (hyphen) follows the comment, a null ELSE
clause is assumed. ELSE is not matched with THEN, and an error message is
issued. The PRINT command is ignored. Notice the correct use of the continuation
character on the other lines.
Error Example 3:
PRINT INDD( - /\COMMENT\/
DDN1)
The DDN1 on the second line is ignored and nothing is printed because characters
other than blanks appear after the continuation character (hyphen).
Ending Your DFSMSdss Step

With the end-of-job (EOJ) command, you can end your DFSMSdss step after the
currently processing operation or scheduled tasks are completed. The command
syntax is:
55EOJ5%
183
184
Stand-Alone Services
Chapter 5. Stand-Alone Services of DFSMSdss
This section, which describes the new Stand-Alone Services function, is intended
for the storage administrator, the system programmer, and anyone who runs the
Stand-Alone Services program. IBM offers this improved Stand-Alone data recovery
solution to all users of the DFSMS/MVS Version 1 Release 4 and above
DFSMSdss software package. This chapter, along with related information in
OS/390 MVS System Messages, Vol 1 (ABA-ASA), supports the new Stand-Alone
Services program.
Stand-Alone Services can perform either a full-volume or a tracks restore from
dump tapes produced by DFSMSdss or DFDSS, and offers the following benefits
when compared to the previous DFSMSdss Stand-Alone functions:
Provides user-friendly commands to replace the previous control statements
Supports IBM 3494 and 3495 Tape Libraries, and 3590 Tape Subsystems
Supports IPLing from a DASD volume, in addition to tape and card readers
Allows you to predefine the operator console to be used during Stand-Alone
Services processing
Preparing to Run the New Stand-Alone Services Program

The new version of IBMs Stand-Alone restore function is a single-purpose program
designed to allow the system programmer to restore vital system packs during
disaster recovery without needing to rely on an MVS environment. Stand-Alone
Services runs independently from a system environment either as a true
stand-alone system or under a VM system.
This section helps you to prepare your environment before you IPL and run the
Stand-Alone Services program. Information is provided about running Stand-Alone
Services in different processor operating modes, running with a predefined console,
setting up tape library and device options, and using command syntax and
processing options.
The Stand-Alone Services program operates on an IBM System/370 processor in
either ESA/370 mode, 370-XA mode, or System/370 (S/370) mode. It also runs on
an IBM System/390 processor in ESA/390 mode or S/370 mode. The Stand-Alone
Services program can run on a processor that is in BASIC or LPAR mode, or you
can run the Stand-Alone Services program in a virtual machine under VM.
The Stand-Alone Services program operates in extended control (EC) mode and
requires 2MB of real storage.
VM Note: To specify EC mode when you are running the Stand-Alone Services
program under VM/370, enter: CP SET ECMODE ON
185
Running Stand-Alone Services in 370 Mode

The following conditions apply to Stand-Alone Services operations in 370 mode:
Tape libraries are not supported by Stand-Alone Services in 370 mode.
The IPL device and the console must be attached to the same processor you
IPLed from (when there are two or more processors).
For DASD and tape devices:
In 370 mode, Stand-Alone Services does not issue Assign or Unassign
commands for tape devices, or Device Reserve or Device Release
commands for DASD devices.
The user must ensure that all devices to be used by Stand-Alone Services
are not accessed by other systems during IPL and while Stand-Alone
Services operations are in process.
Potential interference from other devices can occur as follows:
When the Stand-Alone Services is IPLed and loaded with the operator
console not predefined, a Wait PSW is loaded with the rightmost bytes
containing X'FFFFFF'. The Stand-Alone Services program waits for the
operator to identify the operator console. The first interrupt presented at this
time is expected to be a console and is treated as such.
When the operator console is predefined and a problem is detected while
attempting initial communication with the predefined console, Stand-Alone
Services loads a Wait PSW with the rightmost bytes containing
X'DDDDDD', giving the operator an opportunity to identify a console (other
than the predefined console) to be used as the operator console.
Other devices can generate interrupts that interfere with Stand-Alone Services
operations. If this happens, determine which device is causing the interference
and follow your installations procedures to prevent the device from interrupting
until the Stand-Alone Services operation is complete.
Running Stand-Alone Services in XA or ESA Mode

The following conditions apply to Stand-Alone Services operations in XA or ESA
mode:
For DASD and tape devices:
In XA or ESA mode, Stand-Alone Services issues Assign and Unassign
commands for tape devices, and Device Reserve and Device Release
commands for DASD devices (if the command is supported by the device).
VM Note: When running Stand-Alone Services under VM, if the
Stand-Alone Services program does not run to completion or is
unable to free the device, an Assign or Reserve condition may be
left outstanding.
The user must ensure that the devices to be used by Stand-Alone Services
are not accessed by other systems while Stand-Alone Services IPL and
operations are in progress.
Potential interference from other devices can occur as follows:
When the Stand-Alone Services is IPLed and loaded with the operator
console not predefined, a Wait PSW is loaded with the rightmost bytes
containing X'FFFFFF'. The Stand-Alone Services program waits for the
186
operator to identify the operator console. The first interrupt presented at this
time is expected to be a console and is treated as such.
When the operator console is predefined and a problem is detected while
attempting initial communication with the predefined console, Stand-Alone
Services loads a Wait PSW with the rightmost bytes containing
X'DDDDDD', giving the operator an opportunity to identify a console (other
than the predefined console) to be used as the operator console.
Other devices can generate interrupts that interfere with Stand-Alone Services
operations. If this happens, determine which device is causing the interference.
If the interrupting device is not on the same channel path ID (CHPID) as the
devices you are using for Stand-Alone Services processing, configure that
CHPID offline, re-IPL the Stand-Alone Services program, and configure the
CHPID back online after processing is complete. If the interrupting device is on
the same CHPID as the devices you are using for Stand-Alone Services
processing, follow your installations procedures to prevent the device from
interrupting until after the operator console has been identified.
Running Stand-Alone Services with a Predefined Console

Use the OPERCNSL parameter of the BUILDSA command to predefine the console
when creating the Stand-Alone Services program. The OPERCNSL parameter
allows you to specify the address of the device to be used as the operator console,
or you can specify OPERCNSL(SERV) to use an ES/9000 service console. The
device you specify must be one of the supported device types listed in Supported
Devices on page 203.
The device must also be a valid device within the configuration that runs the
Stand-Alone Services program. Limited validation of the OPERCNSL parameter is
performed during the BUILDSA processing. This is because the Stand-Alone
Services program may be run with a system configuration that is different from the
system configuration that was used to build the core image9(with the BUILDSA
command).
After it is IPLed, Stand-Alone Services attempts to use the predefined device as the
operator console instead of waiting for the first interrupt to identify the operator
console. If a problem with the predefined device is detected, the processor enters a
wait-state with the rightmost bytes of the PSW containing DDDDDD. This PSW
indicates that Stand-Alone Services is unable to use the predefined device and is
waiting for the operator to identify another console to be used as the operator
console. If this happens, do the following:
1. Determine the cause of the problem with the predefined device and take steps
to correct the problem. Some of the possible reasons for a problem being
detected are listed below.
2. Generate an interrupt on a different console that you can use as the operator
console.
The following are some of the reasons for a problem being detected with the
predefined console:
The core image is the executable module that is loaded into the processors storage during the IPL and load process.
187
An error has occurred during the Stand-Alone Services programs initial

communication with the predefined console.
The console address may have been incorrectly specified when the
Stand-Alone Services program IPL-able core image was built. For example, the
address that was specified with the OPERCNSL parameter of the BUILDSA
command does not exist in the configuration in which the Stand-Alone Services
program is being IPLed.
The device at the address specified with the OPERCNSL parameter cannot be
identified as a supported operator console.
If the console was predefined to be the service console, the necessary features
may not exist on the processor for Stand-Alone Services to communicate with
the console. See the list of supported consoles in Supported Devices on
page 203.
Using a Tape Library

This section explains how to use the IBM 3494 and 3495 Tape Libraries to IPL
Stand-Alone Services and restore your dump data set tapes, and how to use the
tape library menu options.
Notes:
1. Stand-Alone Services supports IBM tape libraries in XA or ESA mode only.
2. Tape drives to be used for Stand-Alone Services must remain offline to other
systems.
3. The IPL tape must be mounted and ready prior to performing the IPL.
The Stand-Alone Services RESTORE and TAPECNTL commands are supported by
devices within IBM 3494 and 3495 Tape Libraries. Table 5 on page 189 shows the
options available when you use a tape library to IPL the core image or restore from
dump tapes. Stand-Alone Services can use the tape library in different ways
depending on the features that exist on the tape library.
IPLing and Restoring from a Tape Library

Use one of the options shown in Table 5 on page 189 to either IPL the
Stand-Alone Services program or to restore data from dump data set tapes.
188
Table 5. Stand-Alone Services Options when Using an IBM 3494 or 3495 Tape
Library. Procedures referred to in this table appear later in this section.
Can You Perform the Task Using an IBM Tape Library with:
Task
IPL the
Core
image
Restore
from
Dump
Tapes
No Setup
Stand-Alone
Device
Feature?
No.
Only for tapes

inside the
library. Use the
TAPEVOLSER
parameter of the
RESTORE
command.
Setup Stand-Alone
Device Feature
Only?
Both Setup
Stand-Alone Device
and Transient Mount
Features?
Only for tapes inside

the library. Use
Procedure A.
For tapes inside the

library, use Procedure A.
For tapes outside the
library, use Procedure B.
Only for tapes inside

the library. Either use
Procedure A or use the
TAPEVOLSER
parameter of the
RESTORE command.
For tapes inside the

library, either use
Procedure A or use the
TAPEVOLSER
parameter of the
RESTORE command.
For tapes outside the
library, use Procedure B.
Only one method can

be used for a single
invocation of the
RESTORE command.
Only one method can be

used for a single
invocation of the
RESTORE command.
Note: When the Setup Stand-Alone Device feature is used to mount tapes,
Stand-Alone Services treats the tape drive as if the drive is not part of a tape
library.
Identifying Procedures to Mount and Demount Tapes Using the

IBM Tape Library Stand-Alone Device Setup Features
The following procedures to mount and demount the Stand-Alone Services IPL tape
and dump data set tapes are referenced within Table 5.
Note: When both the IPL tape and the dump data set tapes are mounted from the
input station (Transient Mount), the same tape drive must be used for both
the IPL tape and the dump data set tapes, rather than using different tape
drives.
PROCEDURE A
Use this procedure for tapes residing inside the library.
Mounting Mount tapes with the Library Manager Console Setup
Stand-Alone Device window using the Mount a single volume option.
Specify the device and the volume serial number. Mount subsequent tapes
in the same manner. When separate tape drives are used for the IPL tape
and the dump data set tapes, mount the first dump data set tape prior to
IPLing the Stand-Alone Services program.
Demounting Select the Demount a single volume option to unload and
demount tapes that are not unloaded by Stand-Alone Services (for example,
the IPL tape). Specify the device when selecting the option. Another option
is to use the TAPECNTL command to unload and demount the volume.
189
PROCEDURE B
Use this procedure for tapes residing outside the library.
Mounting Mount tapes with the Library Manager Console Setup
Stand-Alone Device window using the Mount from Input Station option.
Specify the device when selecting the option. This is called a Transient
Mount operation. Mount the first dump data set tape prior to IPLing the
Stand-Alone Services program.
Demounting When the IPL tape is the only tape mounted from the input
station, unload and demount the tape after the Stand-Alone Services
Restore operation has completed. Do this by canceling the mount from the
input station using the Library Manager Console.
For additional information about tape library operations, refer to the appropriate IBM
Tape Library operators guide.
Using an Automatic Cartridge Loader

A tape drive with an automatic cartridge loader can be set to manual mode or auto
mode. When the loader is set to manual mode, you must manually remove the tape
and mount subsequent tapes when Stand-Alone Services has unloaded the tape in
the drive and is waiting for a subsequent tape to be mounted.
When the loader is set to auto mode, you can premount the tapes in the order that
they will be needed. When Stand-Alone Services unloads the tape in the drive, the
cartridges continue to feed and load without requiring intervention.
Controlling Command Sequence Processing

You can control Stand-Alone Services command processing by using SET and
IF-THEN-ELSE command sequences. For more information about these
commands, see Controlling Task Processing on page 178.
IPLing and Running the Stand-Alone Services Program

This section contains an overview of the Stand-Alone Services process, the
procedure to IPL Stand-Alone Services, and specific information about the
RESTORE and TAPECNTL commands.
Figure 5 on page 191 shows an overview of the Stand-Alone Services data
restoration process.
190
CREATE
IPL
the coreimage on
current MVS system
from the coreimage
RESTORE
vital system packs
Dump Data Sets
System DASD
CONTINUE
normal operations
Figure 5. Stand-Alone Services Restore Process Overview
Refer to OS/390 MVS System Messages, Vol 1 (ABA-ASA) for information about
messages received while running Stand-Alone Services.
The following is an overview of the steps necessary to implement the Stand-Alone
Services program:
1. Prepare for Stand-Alone Services by setting up the environment as described
in Preparing to Run the New Stand-Alone Services Program, and creating a
Stand-Alone Services IPL-able core image with the BUILDSA command. The
BUILDSA function is not part of Stand-Alone Services, yet it is necessary
before Stand-Alone Services can be IPLed in a stand-alone environment. The
BUILDSA command is described in BUILDSA Command on page 23.
2. IPL the Stand-Alone Services program from your specified tape, DASD, or card
reader device.
3. Restore your dumped volumes with the RESTORE command. The RESTORE
command performs a full-volume or tracks restore from a DFSMSdss-formatted
or DFDSS-formatted dump tape.
The TAPECNTL command allows you to rewind and unload a tape under
Stand-Alone Services control rather than having to perform this function
manually.
191
IPLing Stand-Alone Services

This section lists the steps to IPL the Stand-Alone Services program. The
programming status word (PSW) wait-state codes (encountered during Stand-Alone
Services processing) are found in Interpreting Wait-State Codes on page 194. An
example of the Stand-Alone Services system IPL is included on page 193.
To IPL from the Stand-Alone Services core image (created with the BUILDSA
command), proceed as follows:
1. Load the Stand-Alone Services Program.
Load Stand-Alone Services from the processors IPL console by specifying the
IPL address for the device (card, tape, or DASD) that contains the IPL-able
core image and then, by performing a Load Clear operation (also referred to as
an IPL Clear).
2. Select the Operator Console.
When the Stand-Alone Services program has finished loading, one of the
following conditions exist:
If the Stand-Alone Services core image was created without specifying the
OPERCNSL parameter, then the processor enters a wait-state with the
rightmost bytes of the PSW containing FFFFFF. Press the Enter key on
the operator console you wish to use. (See Supported Devices on
page 203 for a list of supported console devices.) The first interrupt
presented is expected to be a console and is treated as such.
If the Stand-Alone Services core image was created with OPERCNSL
specified, then Stand-Alone Services attempts to use the device address
specified by OPERCNSL as the operator console, rather than waiting for
the first interrupt. See Running Stand-Alone Services with a Predefined
Console on page 187 for more information.
3. Specify the Input Device.
After the operator console is identified, the following message appears:
ADRY5E
DEFINE INPUT DEVICE, REPLY dddd,ccuu or CONSOLE
To specify the console as the input device, enter CONSOLE or a null line. To
specify a different device type, enter dddd,ccuu, where dddd is either the
device type or card, and ccuu is the unit address. For example, to select a
3505 card reader at address 502, enter:
card,52
The input device can be one of the supported console devices or a card reader
device. See Supported Devices on page 203 for supported input devices.
4. Specify the Message Output Device.
After the input device is identified, the following message appears:
ADRY6E
DEFINE OUTPUT DEVICE, REPLY dddd,ccuu or CONSOLE
To specify the console as the output device for operator communication, enter
CONSOLE or a null line. To specify a different device type, enter dddd,ccuu,
where dddd is either the device type or prnt, and ccuu is the unit address. For
example, to select a 3800 print subsystem at address 510, enter:
192
prnt,51
The output device can be a supported console device or a supported printer
device. See Supported Devices on page 203 for supported message output
devices.
5. Specify the correct date and time, if needed.
Stand-Alone Services automatically picks up the time and date from the
processors time-of-day (TOD) clock, usually in the Greenwich Mean Time
(GMT) format. When the TOD clock is incorrect or is not set, the following
message appears:
ADRY15E
SUPPLY TODAYS DATE, REPLY MM/DD/YY
When you have entered the correct date in the format indicated, the following
message appears:
ADRY16E
SUPPLY TIME OF DAY, REPLY HH:MM:SS
Enter the correct time in the format indicated. If you press Enter without
specifying a date or time, the value is set to zero.
At this point the IPL is complete. You can now enter Stand-Alone Services
commands from the specified input device. Multiple commands can be entered
without requiring a re-IPL of the Stand-Alone Services program.
IPL Example
In the following example, the console is defined as both the input device and output
device. System messages are highlighted in bold followed by the users response.
The example shows how more than one command can be entered without requiring
a re-IPL.
193
ADRY5E DEFINE INPUT DEVICE, REPLY DDDD,CCUU OR CONSOLE

ENTER INPUT/COMMAND:
{The Enter key is pressed}
ADRY6E DEFINE OUTPUT DEVICE, REPLY DDDD,CCUU OR CONSOLE
{The Enter key is pressed}
SA/XA/ESA
5695-DF1 DFSMSDSS STAND-ALONE V1.3.
TIME: 16:36:23 6/7/95
restore frmdv(tape) frmadr(faf) toadr(f4a) vfy(tstb4)
RESTORE FRMDV(TAPE) FRMADR(FAF) TOADR(F4A) VFY(TSTB4)
ADRY1I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS
16:38:5
6/7/95
restore frmdv(tape) frmadr(faf) toadr(f4a) RESTORE FRMDV(TAPE) FRMADR(FAF) TOADR(F4A) ENTER INPUT/COMMAND:
vfy(tstb4)
VFY(TSTB4)
ADRY1I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS
16:39:48
6/7/95
Interpreting Wait-State Codes

The following programming status word (PSW) wait-state codes can occur during
the Stand-Alone Services IPL:
Code
Explanation
000033
A program check occurred while Stand-Alone Services was being

loaded. Contact your software service representative.
The IPL device is not operational. Contact your hardware service
representative. If the IPL device is a tape drive, try to IPL from
another tape drive.
An I/O error occurred on the IPL device or channel while
Stand-Alone Services was being loaded. Contact your hardware
service representative to correct the cause of the problem.
The IPL loader is unable to determine if the entire Stand-Alone
Services core image has been loaded. This could be due to a
software or hardware error. Determine the cause of the problem and
contact the appropriate service representative.
The IPL loader is unable to locate the SYS1.ADR.SAIPLD.Vvolser
data set on the IPL volume.
000044
000055
000066
000077
194
000088
0000AE
0000AF
0000E2
00BCBC
111111
888888
999999
BBBBBB
DDDDDD
EE4990
EEEEnn
The device type being used to IPL is not a supported DASD device
for IPLing the Stand-Alone Services.
An external interrupt occurred while Stand-Alone Services was being
loaded. Contact your software service representative.
A supervisor call instruction (SVC) interrupt occurred while
Stand-Alone Services was being loaded. Contact your software
service representative.
A machine check has occurred. Contact your hardware service
representative.
An attempt was made to IPL a processor that is in BC mode. IPL on
a processor that supports EC mode. When you IPL from a VM user
ID, set it to EC mode. This PSW is only loaded if you are IPLing
from card or tape.
Stand-Alone Services is waiting for an I/O interrupt. If the processor
stops with this code loaded it may be necessary to re-IPL and rerun
the command. Contact your hardware service representative if the
problem persists.
A temporary wait for a service-signal interrupt.
A temporary wait for a service-signal interrupt.
Stand-Alone Services is waiting for the operator to enter the input in
response to a prompting message on the service console.
Stand-Alone Services has detected an error related to the predefined
console, and is waiting for the operator to identify another console to
be used as the operator console. Possible reasons for the error with
the predefined console and actions to take are listed in Running
Stand-Alone Services with a Predefined Console on page 187.
Stand-Alone Services cannot find a required module. Refer to
message ADRY4990I for more information.
The processor is in a wait-state. The error is indicated by nn as
follows:
nn
Indicates:
13
An SVC interrupt has occurred. Run the SADMP* service aid
to dump the contents of real storage to tape, and contact your
software service representative.
14
A program interrupt has occurred. Run the SADMP* service
aid to dump the contents of real storage to tape, and contact
your software service representative.
15
There is insufficient main storage. Stand-Alone Services
requires 2MB of storage.
16
An I/O error has occurred.
17
Stand-Alone Services is unable to open a data set or access a
device, possibly because the device type is not supported.
18
Stand-Alone Services cannot send an operator message
because the console is either not defined or is unavailable.
19
An end-of-data routine is missing. Run the SADMP* service
aid to dump the contents of real storage to tape, and contact
your software service representative.
1A
The predefined console is not attached or is not operational.
Possible reasons for this error are listed in Running
Stand-Alone Services with a Predefined Console on
page 187.
195
1B
EECC03
EECCCC
F1F1F1
FFFFFF
Stand-Alone Services is unable to communicate with the

predefined service console. This may be due to an error, or
because the necessary features do not exist on the processor
to communicate with the predefined console.
* Refer to your appropriate MVS Service Aids publication
for information on creating a stand-alone dump with the
AMDSADMP (SADMP) service aid.
A condition code 3 (not operational) has been received when
attempting to communicate with the service console. Contact your
hardware service representative.
An error occurred while trying to communicate with the service
console. This can result from a hardware or a software problem.
Waiting for an I/O interrupt while Stand-Alone Services is being
loaded.
Stand-Alone Services is waiting for the operator to identify the
operator console. Generate an interrupt from the console that is to
be used as the operator console.
RESTORE Restoring a Formatted Dump Tape

Use the RESTORE command to perform either a full-volume or a tracks restore
from dump tapes produced by DFSMSdss or DFDSS without the use of a system
environment.
The RESTORE command can restore from tape volumes created by a full-volume
or tracks dump, or it can restore a track or tracks from the first logical volume of a
physical data set dump. It cannot restore from tapes created by a DFSMSdss or
DFDSS logical dump, from a DFSMSdss tracks dump using the CPVOLUME
parameter, or from dump tapes produced by other utilities.
With the RESTORE command you specify both the source tape volume (containing
the dump data set) and the DASD target volume. Use either IBM standard label or
nonlabeled tapes as the source tape volumes (dump tapes) for the Stand-Alone
Services restore operation. If the volume serial number of the DASD target volume
is different from the volume serial number of the original DASD source volume, the
restore operation changes the DASD target volume serial number to that of the
DASD source volume.
When IPLing from tape, the data to be restored can be mounted on a tape drive
other than the IPL tape drive. Alternatively, a single tape drive can be used to
mount the tape to be IPLed and the tape to be restored.
The device type of the DASD source volume used for the system dump must match
the device type of the receiving volume used in a Stand-Alone Services restore
operation. However, dump data from a smaller capacity (less cylinders) device can
be restored to a larger capacity (more cylinders) device of the same device type.
Note: When data is restored from a smaller capacity device to a larger capacity
device, the free space information becomes invalid. The free space
information in the VTOC is rebuilt when the next data set is allocated on the
volume.
196
RESTORE Command Syntax

The syntax of the Stand-Alone RESTORE command is:
5RESTOREFROMDEV(34)FROMADDR(ccuu)TOADDR(ccuu)5
FROMDEV(TAPE)
FULL
5VERIFY(volser)5
NOVERIFY STARTTRK(cccc,hhhh)
ENDTRK(cccc,hhhh)
READCHECK
FILE(1)
55
NOREADCHECK TAPEVOLSER(tserial) FILE(nnnn)
6(tserial))
TAPEVOLSER(
See Command Syntax on page 1 for command and comment formatting specifics
Required Parameters
FROMDEV
Specifies the device type that the dump data set resides on. Eligible
device names are 3400 and TAPE. When either 3400 or TAPE is
specified, Stand-Alone Services attempts to determine the device type
from the self-description information. If the device self-description
information indicates a supported device type, Stand-Alone Services
uses the returned device type for processing. When a device does not
support self-description, Stand-Alone Services processes the device
differently depending on whether 3400 or TAPE is specified.
Abbreviations: FRMDEV and FRMDV.
3400 specifies device types 3420, 3422, and 3430. If the device type
cannot be determined from the self-description information,
Stand-Alone Services processes the device as a 3400-type device.
TAPE specifies all other supported tape devices listed in Supported
Devices on page 203 for source data sets. If the device type cannot
be determined from the self-description information, Stand-Alone
Services processing ends.
FROMADDR
Specifies the address of the device that the dump data set resides on.
You can specify a 3-digit or 4-digit address. Abbreviations: FRMADDR
and FRMADR.
TOADDR Specifies the address of the DASD target device to be restored. The
device type must be the same as the device type of the volume
originally dumped. You can specify a 3-digit or 4-digit address.
Abbreviation: TOADR.
VERIFY
Specifies that the volume serial number that is currently on the DASD
target volume should be verified before restoring the data. Specify either
VERIFY or NOVERIFY, not both.
DASD volumes to be restored must be initialized with a readable volume
label and VTOC. Abbreviation: VFY.
NOVERIFY
Specifies that no action be taken to either verify the volume serial
number, or to verify that any volume serial number exists. When
197
NOVERIFY is specified, a prompting message is issued for the user to

reply with permission to continue. Specify either VERIFY or NOVERIFY,
not both. Abbreviations: NOVFY and NVFY.
Optional Parameters
FULL
Specifies that the full volume be restored. The dump data set must be a
DFSMSdss or DFDSS full-volume physical dump. The default is FULL.
STARTTRK
Specifies that a range of tracks beginning with the specified track be
restored. The dump data set can be a full-volume physical dump, a
tracks dump, or a physical data set dump. The STARTTRK parameter is
required with a tracks dump or a physical data set dump. STARTTRK is
not valid when FULL is specified.
Specify the track in the form (cccc,hhhh), where cccc is the cylinder
number and hhhh is the head number. The cylinder and head numbers
can be specified in either decimal or hexadecimal (for example,
X'AC',X'E' for hexadecimal or 172,14 for decimal.) Leading zeros are
not required. The STARTTRK parameter is processed as follows:
When ENDTRK is not specified, the ending track is set to the last
track on the volume.
When the starting track value is higher than the ending track value,
then an error message is issued and the restore operation is ended.
When the starting track value exceeds the volume limits, an error
message is issued and the restore operation is ended.
Abbreviations: STRTRK and STRK.
ENDTRK Specifies the ending track to be restored when STARTTRK is specified.
This parameter is not valid when FULL is specified.
Specify the track in the form (cccc,hhhh), where cccc is the cylinder
number and hhhh is the head number. The cylinder and head numbers
can be specified in either decimal or hexadecimal (for example,
X'AC',X'E' for hexadecimal or 172,14 for decimal.) Leading zeros are
not required. The ENDTRK parameter is processed as follows:
When STARTTRK is specified and ENDTRK is not specified, the
ending track is set to the last track on the volume.
When the ending cylinder value exceeds the volume limits, then the
ending cylinder value is set to the last cylinder on the volume, and a
warning message is issued.
When the ending head value exceeds the volume limits (exceeds
the last head in a cylinder), then the ending head value is set to the
last head on the ending cylinder, and a warning message is issued.
When the starting track value is higher than the ending track value,
an error message is issued and the restore operation is ended.
Abbreviation: ETRK.
READCHECK
Specifies that a read-back check of the restored data be performed.
READCHECK is the default. Abbreviations: READCHK, RDCHECK,
RDCHK, and READ.
198
NOREADCHECK
Specifies that a read-back check of the restored data not be performed.
Abbreviations: NOREADCHK, NREADCHK, and NREAD.
TAPEVOLSER
Specifies the tape volume serial numbers of the tapes to be mounted by
Stand-Alone Services when the tapes are in an IBM Tape Library.
Volumes are mounted by Stand-Alone Services in the order in which
they are specified.
The maximum number of tape volume serial numbers that can be
specified is 32. All of the specified tape volumes must be part of the
same dump data set to be used for the restore.
The TAPEVOLSER parameter is ignored if the FROMDEV parameter
does not specify a valid tape drive in a tape library.
Do not specify TAPEVOLSER when the tapes are mounted from the
Library Manager Console with the Setup Stand-Alone Device Pop-up
Window. See Using a Tape Library on page 188 for information about
tape libraries. Abbreviations: TAPEVOL and TPVOL.
FILE
Specifies the relative position, from the beginning of the tape volume,
where the dump data set begins. Allowable values are from 1 to 9999.
When the FILE parameter is not specified, the default value is 1.
Leading zeroes are not required. If the file number specified does not
exist on the tape, unpredictable results can occur; on 3400 tape devices
with tape reels, an incorrectly specified file number can cause the tape
to run off the end of the reel.
RESTORE Command Examples

In the following example, device address 2FAF is a 3490 tape drive with a tape
mounted that contains the dump data set to be restored. Device address 4791 is a
3380 DASD with volume serial number D3380K. Before writing on the volume, the
RESTORE command verifies that the DASD at address 4791 has volume serial
number D3380K. The full volume is restored.
RESTORE FRMDV(TAPE) FRMADR(2FAF) TOADR(4791) VFY(D338K)
In the following example, device address F01 is a 3420 tape drive with a tape
mounted that contains the dump data set to be restored. Device address 9B9 is a
9345 DASD with volume serial number TS9345. Before writing on the volume, the
RESTORE command verifies that the DASD at address 9B9 has volume serial
number TS9345. The range of tracks to be restored is cylinder 0, head 0 through
the end of the volume.
RESTORE FRMDV(34) FRMADR(F1) TOADR(9B9) VFY(TS9345) STRK(,)
In the following example, device address F77 is a 3480 tape drive with a tape
mounted that contains the dump data set to be restored on file 3 of the tape.
Device address F4A is a 3390 DASD. The NOVERIFY parameter prompts the
operator for permission to write on the device at address F4A.
199
RESTORE FRMDV(TAPE) FRMADR(F77) TOADR(F4A) NVFY FILE(3)
In the following two examples, device address F77 is a 3480 tape drive with a tape
mounted that contains the dump data set to be restored. Device address 9B9 is a
9345 DASD with volume serial number TS9345. Before writing on the volume, the
RESTORE command verifies that the DASD at address 9B9 has volume serial
number TS9345. The range of tracks to be restored is from cylinder 200, head 5
through cylinder 205, head 14. The first example specifies the tracks in decimal:
RESTORE FRMDV(TAPE) FRMADR(F77) TOADR(9B9) VFY(TS9345) STRK(2,5) ETRK(25,14)
The second example specifies the tracks in hexadecimal:
RESTORE FRMDV(TAPE) FRMADR(F77) TOADR(9B9) VFY(TS9345) STRK(X'C8',X'5') ETRK(X'CD',X'E')
In the following example, device address FDD is a tape drive in a 3495 Tape
Library, and the tape volume with volume serial number BCD103 contains the
dump data set to be restored. Device address F4A is a 3390 DASD. The
NOVERIFY parameter of the RESTORE command prompts the operator for
permission to write on the device at address F4A. Stand-Alone Services mounts the
tape volume with volume serial number BCD103 on the tape drive with address
FDD. The range of tracks to be restored is cylinder 0, head 0 through cylinder 5,
head 5.
RESTORE FRMDV(TAPE) FRMADR(FDD) TOADR(F4A) NVFY TAPEVOL(BCD13) STRK(,) ETRK(5,5)
In the following example, device address FDD is a tape drive in a 3495 Tape
Library, and the tape volumes with volume serial numbers BCD101 and BCD102
contain the dump data set to be restored. Volume BCD101 is the first volume in the
sequence, and BCD102 is the second volume. Device address 791 is a 3380
DASD. The NOVERIFY parameter of the RESTORE command prompts the
operator for permission to write on the device at address 791. Stand-Alone
Services mounts the tape volumes on the tape drive with address FDD. Volume
BCD101 is mounted first, and when the end of the tape is reached volume BCD102
is mounted.
RESTORE FRMDV(TAPE) FRMADR(FDD) TOADR(791) NVFY TAPEVOL((BCD11) (BCD12))
200
TAPECNTL Rewinding and Unloading a Tape

Use the TAPECNTL command to either rewind, or rewind and unload a tape.
Stand-Alone Services gives you the ability (with the REWIND and UNLOAD
parameters) to rewind and unload tapes under Stand-Alone Services control rather
than doing so manually.
The TAPECNTL command supports devices that are part of IBM 3494 and 3495
Tape Libraries.
TAPECNTL Command Syntax

The syntax of the TAPECNTL command is:
5TAPECNTLDEVTYPE(34)UNITADDR(ccuu)REWIND5
DEVTYPE(TAPE)
UNLOAD
See Command Syntax on page 1 for command and comment formatting

specifics.
Required Parameters
DEVTYPE
Specifies the tape device type that the TAPECNTL operation is to be
performed against. Eligible device names are 3400 and TAPE. When
either 3400 or TAPE is specified, Stand-Alone Services attempts to
determine the device type from the self-description information. If the
device self-description information indicates a supported device type,
Stand-Alone Services uses the returned device type for processing.
When a device does not support self-description, Stand-Alone Services
processes the device differently depending on whether 3400 or TAPE is
specified. Abbreviation: DEV.
3400 specifies device types 3420, 3422, and 3430. If the device does
not support self-description, Stand-Alone Services may not be able to
determine if the device is a tape drive. Stand-Alone Services issues
the rewind or unload instruction to the device anyway. When the
device is not a tape drive, unpredictable results may occur.
TAPE specifies all other supported tape devices listed in Supported
Devices on page 203. Stand-Alone Services does not issue rewind
or unload instructions to the device when Stand-Alone Services
cannot determine the device type from the self-description.
UNITADDR
Specifies the unit address of the device that the TAPECNTL operation
be performed against. You can specify a 3-digit or 4-digit address.
Abbreviations: UNIT and ADDR.
REWIND Specifies that a rewind operation be performed. Specify either REWIND
or UNLOAD, not both. Abbreviation: REW.
UNLOAD Specifies that a rewind and unload operation be performed. If the tape
drive is in an IBM tape library, the tape is demounted if necessary.
Abbreviation: UNL.
201
TAPECNTL Command Examples

In the following example, the TAPECNTL command rewinds the tape mounted in
the 3490 tape drive at address 2FAF:
TAPECNTL DEV(TAPE) UNIT(2FAF) REW
In the following example, the TAPECNTL command rewinds and unloads the tape
mounted in the 3480 tape drive at address F77:
TAPECNTL DEV(TAPE) UNIT(F77) UNL
In the following example, the TAPECNTL command rewinds and unloads the tape
mounted in the 3420 tape drive at address F01:
TAPECNTL DEV(34) UNIT(F1) UNL
Building the IPL-able Core Image

This section describes how to use the BUILDSA command to build the Stand-Alone
Services IPL-able core image. The core image is the executable module that is
loaded into the processors storage during the IPL and load process.
The BUILDSA Function

The BUILDSA function is not part of Stand-Alone Services, yet it is necessary
before Stand-Alone Services can be IPLed in a stand-alone environment. The
DFSMSdss BUILDSA command and examples are presented in BUILDSA
Command on page 23.
Understanding BUILDSA Command Authorization Levels

Your ability to use the BUILDSA command is determined by your level of access
authorization to source (input) data sets and target (output) data sets or volumes
used by the BUILDSA operation. Storage administrators with any of the following
access levels may use the BUILDSA command:
Without special authorization
DASDVOL-access authority to a volume
DFDSS or DFSMSdss authorization
Using BUILDSA without Special Authorization

To use the BUILDSA command, you must have the following data-set-level
authorization to build the IPL-able core image for card or tape:
READ access to the input data sets used by the SYS1.SADRYLIB target library
UPDATE access to the output card or tape data sets
Without special authorization, you cannot create an IPL-able core image for DASD.
Even though you may have UPDATE or ALTER access to the output
202
SYS1.ADR.SAIPLD.Vvolser data set, you are not authorized to update cylinder 0

head 0 of the DASD volume.
Using BUILDSA with DASDVOL-Access Authorization

To use the BUILDSA command for IPL(DASD), you must have the following
access:
READ access to the input data set (SYS1.SADRYLIB)
UPDATE access at the DASDVOL level for each DASD volume on which you
create an IPL-able core image
Using BUILDSA with the ADMINISTRATOR Parameter

Instead of having DASDVOL update access to volumes for IPL(DASD), you can act
as a DFDSS- or DFSMSdss-authorized storage administrator for the BUILDSA
command by specifying the ADMINISTRATOR parameter.
The FACILITY-class profile STGADMIN.ADR.STGADMIN.BUILDSA for the BUILDSA
command ADMINISTRATOR parameter lets you build the Stand-Alone Services
IPL-able core image without having UPDATE access to the output data sets or
UPDATE access to a DASD volume when you create a core image for IPLing from
DASD. You must still have access at the data set level for the input data set.
See the ADMINISTRATOR parameter in Explanation of BUILDSA Command
Keywords on page 24 for more information.
Stand-Alone Services Hardware Requirements

The following processors and devices are supported by the Stand-Alone Services
program.
Supported Processors
The following processors are supported by Stand-Alone Services. Processors not
listed are not supported.
ES/9000
309X
4381
4361
4341
308X
Supported Devices
This section identifies the hardware devices supported by Stand-Alone Services.
Devices not listed are not supported.
IPL Devices
The following devices can be used to IPL the Stand-Alone Services program:
DASD Devices
RAMAC Array DASD
RAMAC Array Subsystem
9345 Storage Subsystem
3390
203
3380
Tape Devices
3590
3490
3480
3430
3424
3422
3420
Tape Subsystem
Tape Subsystem
Tape Subsystem
(Models 3, 4, 5, 6, 7, and 8)
Tape Libraries
3494 (must include the Setup Stand-Alone Device feature with or without the
Transient Mount feature)
Card Readers
3525 Card Reader
3505 Card Reader
Virtual card reader under VM
Command Input Devices

The following devices can be used to input Stand-Alone Services commands.
Consoles (except service consoles) must be channel-attached.
Consoles
3290
3190
327x or compatible console
ES/9000 Service console
Card Readers
3525 Card Reader
3505 Card Reader
Virtual card reader under VM
Message Output Devices

The following devices can be used for the message data device. Consoles (except
service consoles) must be channel-attached.
Consoles
3290
3190
327x or compatible console
ES/9000 Service console
Printers
6262
4248
4245
3900
3800
204
Printer
Printer
Printer
Printing Subsystem (in line mode)
Printing Subsystem (in line mode)
3262 Line Printer

3203 Printer
Source Tape Devices (for RESTORE and TAPECNTL Commands)

The following devices can contain the data to be restored with the RESTORE
command and are supported with the TAPECNTL command:
Tape Devices
3590
3490
3480
3430
3424
3422
3420
Tape Subsystem
Tape Subsystem
Tape Subsystem
(Models 3, 4, 5, 6, 7, and 8)
Tape Libraries
3494 Tape Library
3495 Tape Library
DASD Receiving Volume (for RESTORE Command)

The following devices can be used for the DASD receiving volume:
RAMAC Array DASD
RAMAC Array Subsystem
9345 Storage Subsystem
3390
3380
205
206
Data Security

This section describes the data security protection and access authorization checks
done by DFSMSdss. The DFSMSdss functions available to a user depend on the
access authorizations as defined by:
User and group profiles, which define the authorized users of a RACF-protected
system. The user or group identifier (ID) used for access-authority checking must
be defined to RACF.
Data set and general resource profiles, which protect the resources in a
RACF-protected system and identify the access levels that users have to those
resources.
DFSMSdss supports data-security protection and access-authorization checking
through the system authorization facility (SAF), Resource Access Control Facility
(RACF), and system services such as catalog management services and allocation.
The phrase RACF-protected implies that SAF and RACF (or equivalent) are
installed and active. Refer to OS/390 Security Server (RACF) Security
Administrator's Guide for more about data security and RACF.
DFSMSdss uses the SAF interface and checks to ensure that RACF at the 1.8.1
level or later is installed and active. If an equivalent to RACF is used, either it must
set the same level information that DFSMSdss checks, or your installation must use
the DFSMSdss installation options exit to tell DFSMSdss that SAF with a RACF
equivalent is installed. For more information on this exit, refer to DFSMS/MVS
Installation Exits. The proper level of RACF must be installed for the data-security
features to work as described. The primary features and their levels of RACF are
listed below:
Generic profile handling: RACF 1.5 or later
DASDVOL-access authority: RACF 1.6 or later
Facility class authority: RACF 1.7 or later
Erase-on-scratch: RACF 1.7 or later
Group data set creation: RACF 1.8.1 or later.
Storage class and management class: RACF 1.8.1 or later
Effects of SPECIAL, OPERATIONS, and DASDVOL

The SPECIAL and OPERATIONS attributes and DASDVOL-access authority can
affect the results when you use DFSMSdss to access and process data sets.
SPECIAL
When you use DFSMSdss, the SPECIAL attribute does not give you the authority
to define or rename discrete profiles during a copy, move, or restore of user data
sets that you do not own. This is because DFSMSdss uses the DEFINE function of
SAF and RACF and the ALTER function of catalog management services to define
and rename discrete profiles on your behalf. Instead of the system-SPECIAL
attribute, you need the system-OPERATIONS attribute to define or rename discrete
profiles for user data sets that you do not own.
207
Data Security
OPERATIONS
If you have the system-OPERATIONS attribute, you have authority to the protected
resources in resource classes such as DATASET, DASDVOL, and TAPEVOL. You
are limited to the access specified in the access list if either:
Your current connect group (or any connect group when list-of-groups checking
is active) is in the access list of a resource profile.
Your user ID is in the access list.
As a user with the system-OPERATIONS attribute, you have full control over data
sets, and you can do the following:
Copy, reorganize, catalog, and scratch (delete) data sets

Perform input and output operations on protected tape volumes
Define profiles for group data sets to which you are not connected
Create user data sets and data sets in groups to which you are not connected.
However, if your ID is in the access list, you need at least UPDATE access.
You need the system-OPERATIONS attribute to define or rename discrete profiles

when you use DFSMSdss, even if you are acting as a DFSMSdss-authorized
storage administrator (see DFSMSdss Storage Administrator on page 216).
DFSMSdss can define or rename discrete profiles during copy or restore
operations. However, the OPERATIONS attribute does not necessarily let you
perform all DFSMSdss functions:
If you have group-OPERATIONS, your authority is restricted to the resources
within the scope of the group.
The data set to be processed may be a data set over which you have no
authority. For example, your user ID only has READ access to a data set that
you want to copy and delete.
A copy of a group data set may be disallowed because you are connected to
the group and thus not authorized to define a discrete profile for the data set.
Access can be denied due to security-level, security-category, or security-label
checking.
DASDVOL
DASDVOL is supported directly for volume-level operations, physical operations for
both SMS-managed and non-SMS-managed data sets, and logical operations for
non-SMS-managed data sets. With DASDVOL-access authority to a volume, you
can perform DFSMSdss operations as described in Volume Access and
DASDVOL on page 218 and DASDVOL Limitations on page 220. When you do
so, DFSMSdss bypasses access checking to the data sets and catalogs on that
volume.
You have DASDVOL-access authority to one or more DASD volumes if all of the
following are true:
DASDVOL class is active.
Profiles for the DASD volumes are defined in the DASDVOL class.
You have the level of access needed for the function you are trying to perform.
208
Data Security
Instead of DASDVOL-access authority, your installation can authorize you to act as

a storage administrator for one or more DFSMSdss operations. See DFSMSdss
Storage Administrator on page 216 for details.
General Data Security Information

This section contains information on the following topics:
Protecting Resources and Data Sets

Protecting Usage of DFSMSdss
Password Protection on page 210
Protected User and Group Data Sets on page 210
Generic and Discrete Profile Considerations on page 211
Security-Level, Category, and Label Checking on page 213
Protect-All and Always-Call on page 213
Standard Naming Conventions on page 213
DFSMSdss Temporary Data Set Names on page 213
Discretely Protected Multivolume Data Set on page 215
Erase-on-Scratch on page 215
SMS-Managed Data Set Protection on page 215
Logging on page 216
Protecting Resources and Data Sets

A security administrator or resource owner can control access to resources by
creating a discrete profile, which protects one resource, or a generic profile, which
protects one or more resources. Each profile has a defined, universal access level
and an access list that permit user and group IDs specific levels of access
authority. When profiles control resources, DFSMSdss usage can be restricted.
Protecting Usage of DFSMSdss

Your installation can put DFSMSdss in a protected library to restrict access and
use. Your installation can also limit use of certain DFSMSdss commands and
keywords by defining resource profiles in the FACILITY class and restricting access
to those profiles. To use a protected command or keyword, you need READ-access
authority to the applicable profile. Table 6 on page 210 provides an overview of
the keywords and profiles. For details see FACILITY-Class Profiles for the
ADMINISTRATOR Keyword on page 217.
209
Data Security
Table 6. DFSMSdss FACILITY-Class Profiles. This table shows the DFSMSdss commands and keywords and
the FACILITY-class profile that can restrict them.
Keyword
Profile Name
BYPASSACS with COPY
STGADMIN.ADR.COPY.BYPASSACS
BYPASSACS with RESTORE
STGADMIN.ADR.RESTORE.BYPASSACS
CONCURRENT with COPY
STGADMIN.ADR.COPY.CNCURRNT
CONCURRENT with DUMP
STGADMIN.ADR.DUMP.CNCURRNT
CONVERTV
STGADMIN.ADR.CONVERTV
DEFRAG
STGADMIN.ADR.DEFRAG
DELETECATALOGENTRY with RESTORE
STGADMIN.ADR.RESTORE.DELCATE
IMPORT with RESTORE
STGADMIN.ADR.RESTORE.IMPORT
INCAT(catname) with COPY
STGADMIN.ADR.COPY.INCAT
INCAT(catname) with DUMP
STGADMIN.ADR.DUMP.INCAT
INCAT(catname) with RELEASE
STGADMIN.ADR.RELEASE.INCAT
PROCESS(SYS1) with COPY
STGADMIN.ADR.COPY.PROCESS.SYS
PROCESS(SYS1) with DUMP
STGADMIN.ADR.DUMP.PROCESS.SYS
PROCESS(SYS1) with RELEASE
STGADMIN.ADR.RELEASE.PROCESS.SYS
TOLERATE(ENQF) with COPY
STGADMIN.ADR.COPY.TOLERATE.ENQF
TOLERATE(ENQF) with DUMP
STGADMIN.ADR.DUMP.TOLERATE.ENQF
TOLERATE(ENQF) with RESTORE
STGADMIN.ADR.RESTORE.TOLERATE.ENQF
Password Protection
DFSMSdss supports password checking at the data set level, but not the catalog
level. If a data set is password-protected and RACF-protected, access to the data
set is determined only through RACF-authorization checking (password checking is
bypassed).
Data set passwords in the DFSMSdss input command do not appear in the
SYSPRINT data set listing. However, if your job abnormally ends, those passwords
may appear in any resultant dump. To prevent this, you can put the passwords in a
data set that is referred to with a DD statement.
Protected User and Group Data Sets

DFSMSdss does authorization checks to ensure that you have the authority to
access data sets. Your ability to access and protect a data set is affected by
whether the data set is a user data set or a group data set.
User Data Set

The high-level qualifier of the name of a user data set is a RACF-defined user ID.
As a RACF-defined user, you can protect your own data sets. However, when you
use DFSMSdss to discretely protect a data set for another user, you need the
system-OPERATIONS attribute.
Usually, you can use DFSMSdss to create new user data sets if you own them or
have ALTER access to them through a data set profile or an entry in the global
210
Data Security
access checking table. You can also create a new user data set in any of the
following situations:
You are acting as a DFSMSdss-authorized storage administrator through the
ADMINISTRATOR keyword.
You have DASDVOL-access authority to the non-SMS-managed volume that
the data set is being created on.
You have the system-OPERATIONS attribute, and you have not been explicitly
denied access to the data set.
The system has always-call, the data set name is protected by a generic
profile, and you do not have Automatic Data Set Protection (ADSP). For details,
see Protect-All and Always-Call on page 213 and Automatic Data Set
Protection (ADSP) Attribute on page 212.
The data set is not protected by a generic profile, and you do not have ADSP.
Group Data Set

The high-level qualifier of the name of a group data set is a RACF-defined group
ID. As a RACF-defined user, you can RACF-protect a group data set under any of
these conditions:
You have JOIN, CONNECT or CREATE authority in the group.
You have the group-SPECIAL attribute in the group that owns the user profile.
You have the system-OPERATIONS attribute, and you are not connected to
the group.
You can create new group data sets with the DFSMSdss COPY or RESTORE
command in the following situations:
You are acting as a DFSMSdss-authorized storage administrator through the
You have DASDVOL-access authority to the non-SMS-managed volume that
the data set is being created on.
You have the OPERATIONS attribute, and you have not been explicitly denied
access to the data set.
The system has always-call, the data set name is protected by a generic
profile, you have ALTER-access authority to the data set profile, and you do
not have ADSP. Instead of ALTER access, you can have CREATE authority in
the group and UPDATE access to the data set.
The data set is not protected by a generic profile, and you do not have ADSP.
Generic and Discrete Profile Considerations

A generic or a discrete data set profile can protect a data set. The type of profile
affects DFSMSdss functions, especially copy, dump, and restore.
Generic Profiles
Generic profiles can be used to protect existing data sets without turning on the
RACF-indicator flag in the data set VTOC entry for a non-VSAM data set or in the
catalog entry for a VSAM data set. Generic profiles can be used to permit access
to data sets, deny access to data sets, and control who can create data sets. A
small number of generic profiles can be used to protect many data sets.
211
Data Security
Generic profile checking for the DATASET class must be activated by the RACF
SETROPTS GENERIC(DATASET) command. An entry in the global access
checking table can let a user access a data set that the generic data set profile
does not. See Global Access Checking Table on page 212 for more information.
Discrete Profiles
A discrete profile should be used to protect a data set only if the data set has a
unique security requirement from any other resource. You can protect data sets
with discrete profiles when you use the DFSMSdss COPY or RESTORE command
if you have the authority to define a discrete profile to protect that data set.
When a data set is protected with a discrete profile, an indicator is set in the VTOC
entry for a non-VSAM data set, in the catalog entry for a VSAM data set, or in the
tape volume profile for the tape volume that contains a tape data set. This condition
is called RACF-indicated.
The following are special considerations that apply to discrete profiles:
If the data set is scratched, RACF deletes the discrete profile.
If you rename a data set to your high-level qualifier, the data set and the
discrete profile are renamed, and the owner information of the profile is
changed to your user ID.
If you rename a data set to a high-level qualifier other than your own, the
owner of the high-level qualifier becomes the owner of the data set.
Discrete and Generic Profile Checking

For RACF-indicated data sets, RACF searches first for a discrete profile, and then,
if one is not found, for a generic profile. If neither is found, access is denied. If a
data set is not RACF-indicated, the data set is RACF-protected only if there is a
covering generic profile. The search is done in the following order:
1. Discrete profile if the data set is RACF-indicated.
2. Fully-qualified generic profile.
3. Other generic profiles from the most specific to the least specific profile name.
Global Access Checking Table

Your installation can use entries in the global access checking table to permit, but
not deny, access to data sets. Only data set profiles can be used to deny access to
data sets. Each entry in the table should have a corresponding generic profile to
ensure consistent processing results.
Automatic Data Set Protection (ADSP) Attribute

If you have the ADSP attribute, RACF automatically defines a discrete profile
whenever you create a permanent DASD or tape data set that is not already
protected. For a tape data set, TAPEDSN and TAPEVOL must be active. If you
have the ADSP attribute, you can create and protect data sets:
Whose names begin with your user ID.
Whose high-level qualifier belongs to a RACF group in which you have
CREATE or higher authority. Besides CREATE in the group, you also need
UPDATE access to the data set when you use DFSMSdss to copy or restore a
data set.
212
Data Security
Security-Level, Category, and Label Checking

DFSMSdss does not perform any explicit security-level, security-category, or
security-label (SECLABEL) checking. For example, SECLABELs are not dumped or
restored. However, DFSMSdss and the system services it uses (such as allocation)
call RACF to make authorization checks that can result in access being denied
because of a mismatch between the security level, security category, or security
label of the resource and that of your user ID.
Protect-All and Always-Call

If protect-all has been activated, you can access a data set only through a data set
profile or through an entry in the global access checking table. When always-call is
in effect, RACF is called whenever a data set is accessed or DASD space is
allocated. When RACF is called because of always-call (and not because of
RACF-indication), it only checks generic profiles and the global access checking
table. If protect-all is not in effect and RACF cannot find an appropriate data set
profile or entry in the global access checking table, RACF accepts the request by
default. Be aware of the following conditions:
Always-call is in effect if the data sets are cataloged.
Data sets that are not RACF-indicated, but which are protected by generic
profiles and always-call, are not protected if they are transferred to another
system that does not have RACF, always-call, and appropriate generic profiles.
VSAM data sets are protected only by the RACF profile for the cluster name.
Profiles for the index- and data-component names are ignored, as are the
profiles associated with any PATHs or with the clusters alternate indexes
(AIXs).
Standard Naming Conventions

By default, RACF expects a data set name to consist of at least two qualifiers, with
the high-level qualifier either a RACF-defined user or group ID. Single-qualifier data
set names, especially for DASD data sets, affect your ability to manage or protect
your data sets. For example:
Data set name filtering is less usable for selecting data sets to be processed.
DFSMSdss definitions of discrete data set profiles fail due to lack of correct
prefix information.
Your installation has trouble protecting the temporary data set names that
DFSMSdss uses.
DFSMSdss Temporary Data Set Names

DFSMSdss must allocate temporary data sets to perform certain functions such as
copy and restore. The high-level qualifiers of those data set names can be
protected, and your installation must ensure that these temporary data sets can be
allocated.
Message data set allocated by DFSMSdss to store messages. This data set lets
DFSMSdss print out messages by task rather intermixing them. This data set is
deleted when DFSMSdss completes the operation. System-generated temporary
names are used.
213
Data Security
Special DEFRAG data set allocated by DFSMSdss to contain information about

the DASD extents that are being moved. The data set name is in the following
format:
SYS1.DFDSS.DEFRAG.xxxxxxxx.volser.DUMMY
where xxxxxxxx represents eight bytes of X'FF', and volser is the volume serial
number of the volume being defragmented. The data set is deleted when the
DEFRAG operation completes successfully. If the DEFRAG operation is interrupted
(for example, when DFSMSdss is cancelled), this data set is left on the volume,
and:
You must run a new DEFRAG operation.
You may have to convert an index VTOC (IXFORMAT) volume to nonindexed
(OSFORMAT) before rerunning the DEFRAG operation. Otherwise, the volume
free-space values may be incorrect.
The hexadecimal qualifier is used to prevent you from deleting this data.
Temporary copied data sets allocated by DFSMSdss when a copy is performed
and deleted when the copy is completed.
The format of the temporary name depends on the number of qualifiers of the data
set being copied:
Number of qualifiers (n)
Temporary name
dsnhlq.chhmmsst
25
First n1 qualifiers.chhmmsst
>5
First 4 qualifiers.chhmmsst
where c is:
T Target cluster name
D Target data component name
I Target index component name
U Source cluster name
E Source data component name
J Source index component name
hhmmsst Time stamp information in hours (hh), minutes (mm), seconds (ss), and tenths of
a second (t)
Note: In the course of copying data sets, DFSMSdss will rename the source data
set using the above conventions. Whenever DFSMSdss renames a RACF
protected data set to a temporary name, a RACF profile must exist for the
temporary data set name.
Temporary catalogs allocated by DFSMSdss when copying a catalog. The
catalog name is in the following format:
CATHLQ.EXPORT.Thhmmsst
where,
CATHLQ The first four high-level qualifiers of the catalog being copied.
hhmmsst The time-stamp information in hours (hh), minutes (mm), seconds
(ss), and tenths of second (t).
214
Data Security
Dummy data set allocated by DFSMSdss when copying or restoring volumes

and an indexed VTOC needs to be rebuilt or the volume free-space values need to
be recalculated. The data set name is in the following format:
SYS1.VTOCIX.DSS.TEMP.volser
where volser is the volume serial number of the volume being restored. Allocation
of this data set is never successful because DFSMSdss uses dummy allocation
values.
Discretely Protected Multivolume Data Set

To create a discrete profile for a multivolume, non-VSAM, DASD data set, you must
define each volume of the data set to RACF. When the data set is extended to
another volume or deleted from a volume, that volumes serial number is
automatically added to or deleted from the data set profile.
Erase-on-Scratch
When the erase indicator is set in a DASD data set profile, the tracks of any
scratched or released data set extents that are part of the protected DASD data set
are erased. Erase-on-scratch is supported for the following DFSMSdss commands:
DUMP with DELETE

COPY with DELETE
DEFRAG
RELEASE
When DFSMSdss deletes a data set or moves data extents, the original tracks are
erased if the erase indicator set. This also applies during a copy or restore when
preallocated data sets are deleted and reallocated.
SMS-Managed Data Set Protection

A data set profile may contain a DFP segment. The DFP segment contains a
RESOWNER field, which may be used to specify the owner of an SMS-managed
data set that is protected by the data set profile. If a new SMS-managed data set is
allocated, the user or group ID in the RESOWNER field must have at least READ
access to any MGMTCLAS and STORCLAS profile used in the allocation when:
Your installation has activated the RACF general resource classes MGMTCLAS
and STORCLAS.
Profiles have been defined in those classes to protect against unauthorized
usage of an SMS management class name or a storage class name.
If RESOWNER is not specified when the data set is allocated, the user or group ID
that matches the high-level qualifier is used as the data set owner. Regardless of
who owns an SMS-managed data set, you can select different default values for
MGMTCLAS and STORCLAS by using those parameters with the COPY or
RESTORE command. When you do, RACF checks to ensure that the data set
owner, rather than you, is authorized to use the specified MGMTCLAS and
STORCLAS. The user or group ID must not be revoked.
Storage class and Management class authorization checking can be bypassed for
logical restore and physical data set restore processing by using the ADRPATCH
Serviceability Aid in conjunction with the ADMINISTRATOR keyword. Refer to
DFSMS/MVS DFSMSdss Diagnosis Guide.
215
Data Security
Logging
DFSMSdss automatically supports RACF logging as follows:
Logging of DASDVOL-access checks is allowed for successful authorizations
only. Unsuccessful attempts are not logged because the user can still gain
access at the data set catalog level.
Logging of access checking for data sets occurs as specified in the applicable
data set profile. However, because catalog management services are used,
DFSMSdss does not fully control logging for VSAM data sets.
Logging of access to the FACILITY-class profiles for DFSMSdss is allowed as
defined for those profiles.
DFSMSdss does not control logging of RACF DEFINE requests. DEFINE
requests are made to define discrete profiles and to determine if a user has
CREATE authority in a group.
Logging of access-level checks for a catalog occurs only once.
Logging cannot be disabled by specifying RACFLOG=NO in the PARM
statement of a DFSMSdss job. The only way to turn off logging is through the
DFSMSdss installation options exit.
DFSMSdss Storage Administrator

Your installation can use DASDVOL-access authority to designate users who can
act as DFSMSdss storage administrators. DASDVOL-access authority lets you
perform any DFSMSdss function against the data sets on that volume. However,
DASDVOL-access is not supported for logical operations against SMS-managed
data sets. Further, DASDVOL-access authority must be granted in every volume for
all the data sets for which you are the storage administrator.
DFSMSdss provides an alternative to DASDVOL-access authority. Your installation
can define special FACILITY-class profiles to let you act as a
DFSMSdss-authorized storage administrator.
ADMINISTRATOR Keyword
To act as a DFSMSdss-authorized storage administrator, specify the
ADMINISTRATOR keyword on the appropriate DFSMSdss command. If you are not
authorized to use the ADMINISTRATOR keyword, the command is ended with an
error message. Otherwise, access checking to data sets and catalogs is bypassed.
To use the ADMINISTRATOR keyword, all of the following must be true:
Applicable FACILITY-class profile is defined (see below).
As a DFSMSdss-authorized storage administrator, your authority is for both
physical and logical operations. For example, a DFSMSdss-authorized storage
administrator for the COPY command can copy tracks, a full volume, or data set
without having access to the individual data sets or their catalogs.
DFSMSdss tries to define a discrete profile when you copy a discretely-protected
data set or when you use the MENTITY keyword. The authority to do so is not
216
Data Security
given to you by the DFSMSdss ADMINISTRATOR support. For example, to define

or rename a discrete profile for a user data set that you do not own, you also need
the system-OPERATIONS attribute. The ADMINISTRATOR support also does not
give you authority to bypass checking for MGMTCLAS and STORCLAS authority.
Storage class and Management class authorization checking can be bypassed for
logical restore and physical data set restore processing by using the ADRPATCH
Serviceability Aid in conjunction with the ADMINISTRATOR keyword. Refer to
DFSMS/MVS DFSMSdss Diagnosis Guide.
FACILITY-Class Profiles for the ADMINISTRATOR Keyword

The following are the names and descriptions of the FACILITY-class profiles for the
STGADMIN.ADR.STGADMIN.COMPRESS
Lets you compress data sets without having UPDATE access authority to those
data sets.
STGADMIN.ADR.STGADMIN.COPY
Lets you copy data sets without having access authority to the source (READ) or
target (UPDATE or ALTER) data sets and their catalogs. This profile does not give
you the authority to rename a data set.
STGADMIN.ADR.STGADMIN.COPY.DELETE
Lets you copy or copy and delete data sets without having access authority to the
source (ALTER) or target (UPDATE or ALTER) data sets and their catalogs. This
profile does not give you the authority to rename a data set.
STGADMIN.ADR.STGADMIN.COPY.RENAME
Lets you copy or copy and rename data sets, through the
RENAMEUNCONDITIONAL keyword, without having access authority to the source
(READ) or the target (ALTER) data sets and their catalogs. This profile does not
give you the authority to delete a data set.
STGADMIN.ADR.STGADMIN.DEFRAG
Lets you perform a DEFRAG operation without having READ access to the data
sets that are moved. RACF can still be called for DFSMSdss to determine if
erase-on-scratch processing for a given data set must be done.
STGADMIN.ADR.STGADMIN.DUMP
Lets you dump data sets without having READ access to the data sets. This profile
does not give you the authority to delete a data set.
STGADMIN.ADR.STGADMIN.DUMP.DELETE
Lets you dump or dump and delete data sets without having ALTER access to the
data sets and their catalogs.
STGADMIN.ADR.STGADMIN.PRINT
Lets you print data without having READ access to the data sets containing the
data to be printed.
STGADMIN.ADR.STGADMIN.RELEASE
Lets you release unused space without having UPDATE access to the data sets.
STGADMIN.ADR.STGADMIN.RESTORE
Lets you restore data without having READ, UPDATE, or ALTER access to source
and target data sets and their catalogs. This profile does not give you the authority
to rename a data set.
217
Data Security
STGADMIN.ADR.STGADMIN.RESTORE.RENAME
Lets you restore or restore and rename data sets, through the RENAME or
RENAMEUNCONDITIONAL keyword, without having READ, UPDATE, OR ALTER
access to source and target data sets and their catalogs.
DFSMSdss Volume, Data Set and Catalog Access Authority

DFSMSdss checks your access authority to the volume before it performs any data
set access-authorization checking. You have the required volume-level authority
whenever any of the following is true:
NOPASS was specified on the PPT statement of the SCHEDxx parmlib
member for the ADRDSSU or user program which calls ADRDSSU. ADRDSSU
(or its caller) is coded in the PGM parameter of the EXEC statement and
should be authorized.
Bypass authorization checking is requested by the DFSMSdss installation
authorization exit. This exit cannot be used to bypass authorization checking
initiated by utilities such as IEBCOPY that are invoked by DFSMSdss. Refer to
DFSMS/MVS DFSMSdss Storage Administration Guide for information on when
DFSMSdss invokes utilities.
You have the required DASDVOL-access authority for the function you are
trying to perform.
You are acting as a DFSMSdss-authorized storage administrator.
For SMS-managed data sets, access authorization to create, update, or delete data
sets also authorizes you to create, update, or delete entries in user catalogs.
However, to add or delete any entry for an SMS-managed data set in a protected
master catalog, you also need UPDATE access to the master catalog. To add or
delete any non-SMS entry in any protected catalog, you need UPDATE access to
the catalog.
Figure 6 on page 219 shows the major decisions that are made to determine if you
are authorized to perform a function against a data resource. The figure does not
represent the actual program flow in DFSMSdss. Use the diagram to clarify the
data security decisions under varying conditions.
Volume Access and DASDVOL

You can use DFSMSdss to perform volume-level operations such as a full-volume
dump. Instead of requiring you to have sufficient access authority to each data set
on the volume, DFSMSdss supports DASDVOL-access authority.
218
Data Security
D F S M S dss fu nction req uested
Ye s
A u th or iz e d s tora ge ad m in is tra to r ?
No
Ye s
Authorized
U s e norm al R AC F read source / update
C O P Y D U M P fu n ctio n ?
ta rg e t a u tho r iza tio n proc es sin g
N ot authoriz ed
No
Te r m i n a t e r e q u e s t
H as insta lla tion e xit req uested that
Ye s
authoriz ation checking be b ypassed ?
No
Is th is an a utho riz ed p rog ram c a ll
Ye s
f o r w h i c h N O PA S S = O N ?
No
I s t h is o n e o f t h e f o l l o w in g d a t a s e t s ?
- C he ckpoint / re sta rt
A u th ority g ran te d
Ye s
- Integrated catalog fa cilty
P ro m p t the o pe rato r for a utho rity
V S A M w it h o u t V V D S
A u th o rity re je cte d
- V TO C in d e x
- VVDS
No
Ye s
No
Is this an SM S-m ana ged data set ?
I s R A C F a c ti v e in t h e s y s t e m ?
Ye s
Ye s
No
D oes user have the autho rity a llow ed
R A C F f a c i li t y c la s s f o r f u n c t i o n ?
b y t h e s p e c if i c f a c i li t y c l a s s ?
I s t h e d a t a s e t p a s s w o r d - p r o t e c t e d , o r,
Ye s
No
No
No
fo r a cop y o r re store o peration , is the

targ et vo lu m e pa ss w o rd-pro tec te d ?
Ye s
D o es use r ha ve D A S D V O L au th ority fo r
Ye s
O btain p asswo rd tha t wa s
doing a volum e le vel function ?
Va l i d p a s s w o r d
passed to D FS M Sdss or by
No
a password operator prom pt
Invalid passw ord

D o e s use r h a ve R A C F da ta se t au th ority
for a lo gica l o pe ra tio n for sou rce
plus target data sets that are:

- V S A M a n d n o n -V S A M
ADR1SR04
Ye s
D oes operation require a catalog update ?
- C ataloged and uncataloged

U pdate
N o u pd a te
required
C a t a lo g i s R A C F - p r o t e c t e d .
No
P r o t e c t io n i s t o b e :
Bypass c atalo g
protection
Honored
N ot authoriz ed
C alle r a uth orize d to
Authorized
Pe rform
re qu e ste d
R A C F - p ro t e c t e d c a t a l o g ?
functio n
Figure 6. DFSMSdss Data Security Decisions
219
Data Security
DASDVOL Access Authority

When you have the required level of DASDVOL authority to a volume, as shown in
Table 7, you can perform maintenance operations such as dump, restore, scratch
and rename of the data sets on that volume regardless of your access authority to
those data sets. DFSMSdss lets you catalog, recatalog, and uncatalog the data
sets on the volumes to which you have DASDVOL authority. You also have access
to the catalogs on the volumes to which you have DASDVOL-access authority.
When you restore a data set, DASDVOL-access checking is determined as follows:
The volume serial number of the source volume from which the data set was
originally dumped, regardless of the current status of that data set or volume.
The volume serial number of the volume on which the data set is being
restored. This volume (or volumes) may not be the same as the source volume.
Table 7. DASDVOL Access Authority. This table shows the DASDVOL-access authorities needed to perform
volume and data-set-level functions.
Function
DASDVOL Access Needed
Command
Volume
FULL
TRACKS
Data Set
COMPRESS
Source
N/A
N/A
UPDATE
CONVERT
N/A
N/A
N/A
N/A
COPY
Source
READ
READ
READ
Target
ALTER
ALTER
UPDATE
COPY with
DELETE
Source
N/A
N/A
ALTER
Target
N/A
N/A
UPDATE
COPYDUMP
N/A
N/A
N/A
N/A
DEFRAG
Source
N/A
N/A
UPDATE
DUMP
Source
READ
READ
READ
DUMP with
DELETE
Source
N/A
N/A
ALTER
PRINT
Source
N/A
READ
READ
RELEASE
Source
N/A
N/A
UPDATE
RESTORE
Source
N/A
N/A
READ
Target
ALTER
ALTER
UPDATE
DASDVOL Limitations
DASDVOL-access authority is not supported for logical operations on
SMS-managed data sets, nor does it let you define discrete profiles. For
DFSMSdss to define or rename discrete profiles, you need the authority to do so.
For more about discrete profiles, see Copy and Data Set Profile Considerations
on page 227 and Restore and Data Set Profile Considerations on page 233.
While DASDVOL-access authority to a non-SMS-managed volume lets you move,
copy, dump, or delete a catalog, you do not automatically have access to the data
sets that are cataloged in it. Also, for certain operations (such as CONVERTV on
an SMS-managed data set), an authorization check is performed to see if the data
220
Data Security
set owner is authorized to use the applicable MGMTCLAS and STORCLAS

routines. This is true even if you have DASDVOL-access authorization.
Data Set Access Authorization Levels

Access to a data set is controlled by a data set profile which permits or denies
access. Access-authorization checking to data sets is performed if you do not have
the required volume-level authority, the volume is unprotected, or DFSMSdss is
unable to determine the protection status of the volume.
If the data set and its catalog are unprotected, no authorization is required to read,
update, delete, rename, move, or scratch the data set. For protected data sets, the
following access authorization may be required to perform DFSMSdss functions:
Password specification is required. If the data set is password-protected and
not RACF-protected, you must specify the appropriate password to read,
update, delete, rename, move, or scratch the data set.
The data set is RACF-protected. Your ability to perform operations is
determined by your access-authorization level:
NONE
denies you access to the data set.
READ
lets you read the data set, and even make a copy of it, provided you
have authority to create or replace the target data set.
UPDATE lets you modify (update) an existing RACF-protected data set.

UPDATE access does not let you delete, rename, move, or scratch
a data set.
ALTER
lets you read, update, delete, rename, move, or scratch a

RACF-protected data set.
ALTER access lets you create a user or group data set. CREATE
authority in the group and UPDATE access also lets you create a
new group data set.
The level of access authority you need to access data sets is also dependent on
the following:
Whether the data set is SMS-managed or not.
Whether a catalog entry for the data set is added (cataloged) or deleted
(uncataloged).
Whether the catalog is an integrated catalog facility catalog, a VSAM catalog,
or an OS CVOL.
Whether the catalog is RACF-protected.
DFSMSdss supports VSAM data sets only if they are cataloged in an integrated
catalog facility catalog. Non-VSAM data sets can also be cataloged in a VSAM
catalog or an OS CVOL. For VSAM data sets, access authorization is determined
solely by your authority to access the base-cluster name: Data set profiles are
ignored for any data component, index component, alternate index (processed as
part of a sphere) or PATH.
221
Data Security
Protected Catalogs
DFSMSdss only supports RACF-protection of catalogs; catalog passwords are
never checked.
Catalog Access Authority

DFSMSdss supports cataloged non-VSAM and VSAM data sets in an integrated
catalog facility catalog. The data set and catalog access authority you need is
discussed in Access Authorization for DFSMSdss Commands on page 223.
VSAM Catalog Access Authority

DFSMSdss supports non-VSAM data sets that are cataloged in a VSAM catalog.
VSAM data sets must be cataloged in an integrated catalog facility catalog. The
level of access checking that is performed by DFSMSdss is as though the data sets
had been cataloged in an integrated catalog facility catalog.
OS CVOLs (Control Volumes)

The naming convention used for OS CVOLs (control volumes) by RACF processing
is
SYSCTLG.Vnnnnnn
where nnnnnn is the volume serial number of the CVOL. When RACF receives
SYSCTLG as a keyword, SYSCTLG.Vnnnnnn is appended as a qualifier. Only
non-VSAM data sets can be cataloged into an OS CVOL.
The levels of access authority needed to perform catalog operations on an OS
CVOL for non-VSAM data sets are shown in Table 8. The table assumes the
following conditions:
The table does not apply when you are working with data sets that reside, or
will reside, on the volumes for which you have DASDVOL-access authority.
Access checking to the catalog itself is not performed.
An UNCATALOG operation is performed against the catalog when a data set is
deleted.
Table 8. OS CVOL Access Authority. This table shows the CVOL access authority required to perform catalog
operations on an OS CVOL catalog for non-VSAM data sets.
Nongeneration Data Group Data Set
Catalog Operation
222
Generation Data Group Set
RACF-
Not RACF-
RACF-
Not RACF-
Protected
Protected
Protected
Protected
CATALOG
No authority required
UPDATE to GDG
base
RECATALOG
UPDATE to data set
UPDATE to GDG
base
UNCATALOG
ALTER to data set
ALTER to GDG base
Data Security
Non-SMS Versus SMS Authorization

Access authorization requirements differ for SMS-managed data sets and
non-SMS-managed data sets.
SMS-managed data sets: Access to SMS-managed data sets gives you access to
the user catalog for the data sets. However, for a RACF-protected master catalog,
you also need UPDATE-access authority to add or delete an SMS-managed data
set entry. DASDVOL-access authority is not supported for logical operations.
Non-SMS-managed data sets: Besides access authority for data sets, you need
UPDATE access to RACF-protected user or master catalogs to add or delete an
entry in the catalog.
System Operator Authorization, Special Data Set Types

Some system and VSAM data sets accept authorization from the system operator
when RACF or password checking cannot be performed. Unless you are using
DFSMSdss with special authorization, such as DASDVOL or the ADMINISTRATOR
keyword, system-operator authorization is required in order for you to update the
following:
Volume table of contents (VTOC)

VTOC index data set
VSAM volume data set (VVDS)
Checkpoint/restart data set.
The system operator is only prompted for the first data set encountered in one of
the above classes for the DFSMSdss command that is being processed. The reply
given is used for that command invocation for all other data sets of that type on the
volume.
Access Authorization for DFSMSdss Commands

This section covers the following commands:
COMPRESS
CONVERTV
COPY
COPYDUMP
DEFRAG
DUMP
PRINT
RELEASE
RESTORE
The tables in this section can help you determine if you have sufficient access
authority to use the DFSMSdss commands. The access authority you need
depends on what you are trying to do. For example:
If the data set is SMS-managed and you have access to the data set, you have
access to its user catalog.
If you have ALTER access to the data set, you can copy and delete (or dump
and delete) the data set.
If the source data set is cataloged, you may need UPDATE or ALTER access
to its catalog if the data set is going to be deleted, uncataloged, or cataloged.
223
Data Security
To replace an existing data set using the COPY or RESTORE command, you
need UPDATE access to the data set.
If you are doing a restore with rename, ALTER-access authority lets you create
a new user or group data set. If the data set belongs to a group, CREATE
authority in the group and UPDATE access to that group data set name also
lets you create that group data set.
To restore a data set, you need READ access to a data set with the same
name as the one that was dumped. You also need either UPDATE or ALTER
access to the target data set.
If the target data set is going to be discretely protected, and you do not own
the data set, you need additional authority to define a discrete profile. This is
true even if you are acting as a DFSMSdss-authorized storage administrator for
the COPY or RESTORE command.
To copy or dump a master catalog, you need ALTER access if you are not
acting as a DFSMSdss storage administrator. This level of access is needed
because the master catalog may contain passwords.
If you are acting as a DFSMSdss storage administrator, you have access to the
applicable data sets and catalogs.
COMPRESS
To compress partitioned data sets on a specified volume, either you need
DASDVOL-access authority to the volume or UPDATE access authority to the data
sets, or you must be acting as a DFSMSdss-authorized storage administrator.
CONVERTV
Anyone can use the CONVERTV command. However, your installation can limit
usage of the CONVERTV command by use of a RACF FACILITY-class profile if:
RACF FACILITY class is active.
The FACILITY-class profile STGADMIN.ADR.CONVERTV has been defined.
Then need READ access authorization to that profile to use the CONVERTV
command.
To convert a volume to SMS-managed, the user and group IDs of the owners of all
the data sets on that volume must be RACF-defined, and they must not be
revoked.
COPY
Table 9 on page 226, which shows the access authority needed to perform the
copy function, is based on the following assumptions:
The data set is a user data set.
Both the data set and the catalog are RACF-protected.
If the data set is going to be cataloged in the master catalog, then you need
UPDATE access to that catalog.
Table 9 on page 226 also applies to group data sets. To create a new group data
set, you need one of the following:
224
Data Security
UPDATE access to the catalog when a non-SMS-managed group data set is

unprotected, but the catalog is RACF-protected.
CREATE in the group and UPDATE access to the data set.
ALTER access to the data set and be a member of the group that owns the
data set. To discretely protect a group data set, you need additional authority
such as CREATE in the group.
225
Data Security
Table 9. COPY Command Access Authority. This table shows the minimum access levels required to perform a
COPY command.
SOURCE DATA SET
TARGET DATA SET
Non-SMS
Non-SMS
Access Level
Access Level
Data Set
Catalog
Preallocated
Target
NO
READ
Automatic
NO
ALTER
UPDATE
NO
READ
Automatic
YES
UPDATE
Automatic
YES
ALTER
Automatic
NO
ALTER
UPDATE
YES
ALTER
Automatic
YES
UPDATE
Automatic
With DELETE
Non-SMS
Data Set
Catalog
SMS
Access Level
Access Level
Data Set
Catalog
Preallocated
Target
NO
READ
Automatic
NO
ALTER
Automatic
NO
READ
Automatic
YES
UPDATE
Automatic
YES
ALTER
Automatic
NO
ALTER
Automatic
YES
ALTER
Automatic
YES
UPDATE
Automatic
With DELETE
SMS
Data Set
Catalog
Non-SMS
Access Level
Access Level
Data Set
Catalog
Preallocated
Target
NO
READ
Automatic
NO
ALTER
UPDATE
NO
READ
Automatic
YES
UPDATE
Automatic
YES
ALTER
Automatic
NO
ALTER
UPDATE
YES
ALTER
Automatic
YES
UPDATE
Automatic
With DELETE
SMS
Data Set
Catalog
SMS
Access Level
Access Level
Data Set
Catalog
Preallocated
Target
NO
READ
Automatic
NO
ALTER
Automatic
NO
READ
Automatic
YES
UPDATE
Automatic
YES
ALTER
Automatic
NO
ALTER
Automatic
YES
ALTER
Automatic
YES
UPDATE
Automatic
With DELETE
Data Set
Catalog
Notes:
1. Automatic means that you have automatic access to the user catalog if you can access the data sets.
2. In the course of copying data sets, DFSMSdss will rename the source data set using the conventions
described under DFSMSdss Temporary Data Set Names. (See 214 under Temporary Copied Data Sets.)
Whenever DFSMSdss renames a RACF protected data set to a temporary name, a RACF profile must exist
for the temporary data set name.
226
Data Security
COPY and Deleting Data Sets

For SMS-managed data sets, ALTER access lets you delete the data set. For
non-SMS-managed data sets, either ALTER access to the data set or ALTER
access to the catalog and READ access to the data set lets you copy and delete
the data set. The ability to delete and uncatalog a data set with READ access to
the data set and ALTER access to the catalog lets you move a data set without
having ALTER access to the data set. You only need UPDATE access to the
catalog to delete an unprotected, non-SMS-managed data set.
Copy and Data Set Profile Considerations

When you copy a RACF-indicated data set, DFSMSdss performs special target
data set processing. A predefined, discrete profile is not used to check your access
authority unless the data set is already RACF-indicated.
Copy and Data Set Profiles: If a data set is protected by a generic or discrete
profile when it is copied, DFSMSdss tries to ensure that the target data is also
protected (see Table 10). To do so, DFSMSdss uses the RACF DEFINE function
or the catalog ALTER function. You need authority to define or rename discrete
profiles, even if you are acting as a DFSMSdss-authorized storage administrator.
Table 10. COPY Command and RACF Profiles. This table summarizes how DFSMSdss defines discrete profiles
to protect the target set.
COPY with:
RACF Profile:
RENAME
DELETE
Source Data Set

Protected?
NO
NO
NO
None
As predefined
NO
NO
GENERIC
No change
As predefined
NO
NO
DISCRETE
No change
DEFINE
NO
YES
NO
None
As predefined
NO
YES
GENERIC
No change
As predefined
NO
YES
DISCRETE
DELETE
DEFINE
YES
NO
NO
None
As predefined
YES
NO
GENERIC
No change
MENTITY
YES
NO
DISCRETE
No change
DEFINE
YES
YES
NO
None
As predefined
YES
YES
GENERIC
No change
MENTITY
YES
YES
DISCRETE
DELETE
DEFINE
Source
Target
Terms defined:
None
As predefined
No change
DEFINE
DELETE
MENTITY
The data set remains unprotected.

DFSMSdss does not ensure that the target data set is RACF-protected. If a covering data set
profile is not already predefined, the data set may be unprotected.
The data set profile that is protecting the source data set remains unchanged.
A discrete profile is defined by DFSMSdss.
The data set and the discrete profile are deleted.
If the target data set is not RACF-protected by a generic or discrete profile and MENTITY is
specified, DFSMSdss defines a discrete profile. Otherwise, no profile is defined.
COPY and the MENTITY Keyword: By default, when DFSMSdss defines a

discrete profile to protect a copied data set, it uses the discrete profile of the source
data set as a model. The MENTITY keyword lets you specify a different data set
227
Data Security
profile as the model. Besides the model profile, you can also specify a volume
serial (through MVOLSER). If you do so, specify the volume serial number of the
volume containing the non-VSAM model entity or the volume containing the catalog
in which the VSAM model entity is cataloged.
Use the MENTITY keyword of the COPY command when one of the following is
true:
The source data set is RACF-protected by a generic profile, but the target data
set name is unprotected.
The source data set is RACF-protected by a discrete profile, but you wish to
use a different data set profile as the model for defining a new discrete profile.
COPY and Define Discrete Profile Summary: Table 11 summarizes the

circumstances during copy operation when a discrete profile is defined, when
MENTITY is effective, when the target data set is RACF-indicated, and when
related messages are issued. To define discrete profiles for data sets that you do
not own, you need additional authorization such as the system-OPERATIONS
attribute or CREATE in the group.
Table 11 (Page 1 of 2). Copy and Define Discrete Profile Summary. This table summarizes what happens
when DFSMSdss defines discrete profiles for a copy operation.
Protection
228
Source
Target
None
None
None
Generic
None
RACF
Indicated
Generic
None
Generic
Generic
Generic
RACF
Indicated
RACF
Indicated
None
RACF
Indicated
Generic
RACF
Indicated
RACF
Indicated
MENTITY
Specified?
Define Profile?
RACF
Indicated?
Warning
Message?
Yes
No
No
No
No
No
No
No
Yes
No
No
No
No
No
No
No
Yes
No
Yes
No
No
No
Yes
No
Yes
Yes
Yes
No (W)
No
No
No
Yes
Yes
No
No
No
No
No
No
No
Yes
No
Yes
No
No
No
Yes
No
Yes
Yes
Yes
No (W)
No
Yes (C)
Yes
No (E)
Yes
Yes
Yes
No (W)
No
Yes (C)
Yes
No (E)
Yes
No
Yes
No
No
No
Yes
No
Data Security
Table 11 (Page 2 of 2). Copy and Define Discrete Profile Summary. This table summarizes what happens
when DFSMSdss defines discrete profiles for a copy operation.
Terms defined:
Yes (C)
No (W)
No (E)
If there is a discrete profile for the source data set, a discrete profile is defined for the target
data set.
If the define of the discrete profile fails and the copy is successful, then the target data set is
left as RACF-indicated and a warning message is issued. This is true even if DELETE is
specified.
If the define of the discrete profile fails and DELETE is specified, then the copy is unsuccessful
and an error message is issued.
If the define of the discrete profile fails and DELETE is not specified, then the target data set is
left as RACF-indicated and a warning message is issued.
Protection States after a Copy or Move: When a data set is copied or moved,
the protection state of the target depends on the initial protection states of the
source and the target data sets, whether MENTITY was specified, and whether
discrete profiles are predefined. The following conditions may exist:
The source data set is unprotected. The target data set may or may not be
protected after the copy. A discrete profile is not defined by DFSMSdss, even if you
specify MENTITY.
The source data set is protected but not RACF-indicated. The target data set
may or may not be protected after the copy:
If the target data set is not already protected and MENTITY is not specified, the
data set remains unprotected. If you do specify MENTITY, DFSMSdss defines
a discrete profile:
If the define is successful, the target data set is RACF-indicated. It is
accessible according to the access list for the model profile that was used.
If the define is unsuccessful, the target data set remains RACF-indicated.
It may be inaccessible until a data set profile is successfully defined.
If the target data set is already protected because it is RACF-indicated or
RACF-protected, DFSMSdss does not define a discrete profile (even if you
specify MENTITY). The target data set is accessible according to the access
list of a predefined, protecting, data set profile.
The source data set is RACF-indicated. The target data set is RACF-indicated
after the copy:
If the target data set is not RACF-indicated and if either there is a discrete
profile for the source or MENTITY is specified, DFSMSdss defines a discrete
profile:
If the define is successful, the data set is RACF-indicated. It is accessible
according to the access list for the model profile that was used.
If the define is unsuccessful and MENTITY was specified or DELETE was
not specified, the data set is RACF-indicated. It may be inaccessible until a
data set profile is successfully defined.
If the define is unsuccessful and DELETE was specified (without
MENTITY), the copy or move is unsuccessful. The target data set is
deleted, and the source data set is kept.
229
Data Security
If the target data set is already RACF-indicated, a discrete profile is not defined
by DFSMSdss (even if you specify MENTITY or DELETE). The target data set
remains RACF-indicated.
Other COPY Command Considerations

To copy or move a data set that is discretely protected, you need authority to
define discrete profiles because the move operation temporarily renames the data
set and the discrete profile.
COPYDUMP
The access authority you need to the input and output dump data sets depends on
many factors not under DFSMSdss control because access-authorization checking
is performed by Open/Close/End-of-Volume (O/C/EOV) processing. The primary
considerations are as follows:
You need READ access if the input dump data set is protected.
You need either UPDATE or ALTER access if the output dump data set is
protected.
You may need UPDATE access to the catalog if the output data set is going to
be cataloged.
DEFRAG
To use the DEFRAG command to relocate data extents on a DASD volume, you
need DASDVOL-access authority to that volume or READ-access to the data sets
that are relocated. Otherwise, only unprotected data sets are relocated.
As part of the DEFRAG operation, DFSMSdss creates a work data set
(SYS1.DFDSS.DEFRAG.xxxxxxxx.volser.DUMMY), which is deleted after successful
completion of the DEFRAG function. If the DEFRAG operation is prematurely
ended, rerun the DEFRAG function to clean up this data set.
DUMP
The access authority you need to the output dump data set depends on many
factors not controlled by DFSMSdss because access-authorization checking is done
by O/C/EOV. The primary considerations are as follows:
You need access to a protected dump data set with:
ALTER access to create it.
UPDATE access if it is already allocated.
CREATE authority in the group and UPDATE access if it is a group data
set.
You may need UPDATE access to a catalog if the dump data set is going to be
cataloged.
You may have sufficient authority to the dump data set if you have the
You also need access authority to the data sets that are going to be dumped
as shown in Table 12 on page 231.
Table 12 on page 231 is for the following conditions:
230
Data Security
You have the indicated level of access authority to the data set.
The data set is cataloged in a user catalog.
Table 12. DUMP Command and Access Authority. This table shows the minimum access levels required to
perform a DUMP command.
SMS-Managed Data Set?
With DELETE?
Access Level:
Source Data Set
Catalog
NO
NO
READ
Automatic
NO
YES
ALTER
UPDATE
YES
NO
READ
Automatic
YES
YES
ALTER
Automatic
Note: Automatic means that you have automatic access to the catalog if you can access the data set.
Dumping and Deleting Data Sets

For SMS-managed data sets, ALTER access to the data set lets you delete a data
set. If the data set is cataloged in the master catalog, you also need UPDATE
access to the catalog.
For non-SMS-managed data sets, you need one of the following to dump and
delete a data set:
ALTER access to a protected data set.
READ access to a protected data set and ALTER access to a protected
catalog.
UPDATE access to a protected catalog if the data set is unprotected.
DASDVOL-access authority to the volume containing the data set.
Authority to specify DELETE as a DFSMSdss-authorized storage administrator.
PRINT
To use the PRINT command, you need either DASDVOL-access authority at the
READ level or READ access to the data sets.
RELEASE
To use the RELEASE command, you need either DASDVOL-access authority at
the UPDATE level or UPDATE access to the data sets.
RESTORE
The access authority you need to restore a data set from an input dump data set
depends on many factors not controlled by DFSMSdss because
access-authorization checking to the input dump data set is performed by O/C/EOV
processing. The primary considerations are as follows:
You need at least READ access to the dump data set if the dump data set is
protected.
You may need READ access to the catalog if the dump data set is cataloged.
231
Data Security
You may have sufficient authority to the dump data set if you have the
You also need access authority to the source and target data sets and their
catalogs as shown in Table 13 on page 233.
Restore and Access Authorization

When a data set is either restored or both restored and renamed, DFSMSdss tries
to verify that you have READ access to a DASD data set with the same name as
the data set that was dumped. This is done to ensure that an unauthorized person
is not allowed to restore and rename one of your data sets. For example, the
restore described below would be unsuccessful:
Data set USER1.PERSONAL.PAYHIST is RACF-protected so that USER2 cannot
read it.
Data set USER1.PERSONAL.PAYHIST is dumped.
USER2 tries to restore USER1.PERSONAL.PAYHIST as USER2.TEST.DATA.
When you restore a data set, your authority to read that data set is checked using
the current data set profiles rather than the data set profiles that were defined when
the data set was dumped:
If a discrete profile is predefined for the source data set name, it is used
regardless of the current state of the data set.
Otherwise, if a generic profile is defined, it is used.
If neither a discrete nor a generic profile is defined, you are given access.
However, for VSAM data sets that are already cataloged and RACF-indicated,
access is denied in this situation.
For VSAM data sets, if the catalog no longer exists or the data set is no longer
cataloged, only generic-profile checking is performed.
Table 13 on page 233 is based on the following assumptions:
The data set is a user data set.
You have the indicated access authority to the source and target data sets.
If an SMS-managed data set is going to be cataloged in the master catalog,
then you need UPDATE access to that catalog.
Table 13 on page 233 also applies to group data sets. To create a group data set
by restoring it, you need one of the following:
UPDATE access to the catalog for unprotected, non-SMS, group data sets.
For unprotected, SMS-managed data sets, you automatically have access to
the user catalog.
CREATE authority in the GROUP and UPDATE access to the data set.
ALTER access to the data set and be a member of the group that owns the
data set. To discretely protect a group data set, you need additional authority
such as CREATE in the group.
232
Data Security
Table 13. Restore Command and Access Authority. This table shows the minimum access-levels required to
perform a RESTORE command.
SOURCE DATA SET
TARGET DATA SET
Non-SMS
Non-SMS
Access Level
RENAME or
RENAMEU
Data Set
Catalog
NO
No check
No check
NO
No check
YES
YES
Preallocated
Target
Data Set
Catalog
NO
ALTER
UPDATE
No check
YES
UPDATE
Automatic
READ
Automatic
NO
ALTER
UPDATE
READ
Automatic
YES
UPDATE
Automatic
Non-SMS
RENAME or
RENAMEU
Access Level
SMS
Access Level
Access Level
Data Set
Catalog
Preallocated
Target
NO
No check
No check
NO
ALTER
Automatic
NO
No check
No check
YES
UPDATE
Automatic
YES
READ
Automatic
NO
ALTER
Automatic
YES
READ
Automatic
YES
UPDATE
Automatic
SMS
Data Set
Catalog
Non-SMS
Access Level
RENAME or
RENAMEU
Data Set
NO
Access Level
Catalog
Preallocated
Target
Data Set
Catalog
No check
No check
NO
ALTER
UPDATE
NO
No check
No check
YES
UPDATE
Automatic
YES
READ
Automatic
NO
ALTER
UPDATE
YES
READ
Automatic
YES
UPDATE
Automatic
SMS
SMS
Access Level
RENAME or
RENAMEU
Data Set
NO
Access Level
Catalog
Preallocated
Target
Data Set
Catalog
No Check
No check
NO
ALTER
Automatic
NO
No check
No check
YES
UPDATE
Automatic
YES
READ
Automatic
NO
ALTER
Automatic
YES
READ
Automatic
YES
UPDATE
Automatic
Notes:
1. No check means that no check is made.
2. Automatic means that you have automatic access to the catalog if you can access the data sets.
Restore and Data Set Profile Considerations

If the data set being restored was RACF-indicated when it was dumped,
DFSMSdss does special target data set processing.
Restore and the MENTITY Keyword: You can restore a data set and use the
MENTITY keyword to request that DFSMSdss is to define a data set profile when
one of the following is true:
233
Data Security
The data set to be restored was RACF-protected by a generic profile when it

was dumped, and the target data set name is unprotected.
The data set to be restored was RACF-indicated when it was dumped, and the
target data set name is either unprotected or it is only protected by a generic
profile.
DFSMSdss uses the data set profile specified by the MENTITY keyword, and any
volume serial specified with MVOLSER, as a model to define a discrete profile to
protect the target data set. If MVOLSER is not specified, the volume serial is one of
the following:
The volume on which a non-VSAM data set resides.
The volume that contains the catalog for a VSAM data set.
To define discrete profiles for data sets that you do not own, you need additional
authorization such as the system-OPERATIONS attribute or CREATE in the group.
Restore and Physical Data Sets: DFSMSdss provides limited support for
defining discrete profiles during physical restore of a data set:
For VSAM data sets, a discrete profile is never defined.
For non-VSAM data sets, a discrete profile is only defined if MENTITY is
specified and the data set was RACF-indicated when it was dumped.
Restore and Define Discrete Profile Summary: Table 14 on page 235

summarizes the circumstances during a restore when MENTITY is effective, when
a discrete profile is defined, when the target data set is RACF-indicated, and when
related messages are issued.
234
Data Security
Table 14. Copy and Define Profile Summary. This table summarizes when DFSMSdss defines discrete profiles
for a copy operation.
Protection
Source
Target
None
None
None
Generic
None
RACF
Indicated
Generic
None
Generic
Generic
Generic
RACF
Indicated
RACF
Indicated
None
RACF
Indicated
Generic
RACF
Indicated
RACF
Indicated
MENTITY
Specified?
Define Profile?
RACF
Indicated?
Warning
Message?
Yes
No
No
No
No
No
No
No
Yes
No
No
No
No
No
No
No
Yes
No
Yes
No
No
No
Yes
No
Yes
Yes
Yes
No (W)
No
No
No
Yes
Yes
No
No
No
No
No
No
No
Yes
No
Yes
No
No
No
Yes
No
Yes
Yes
Yes
No (W)
No
No
Yes
Yes
Yes
Yes
Yes
No (W)
No
No
Yes
Yes
Yes
No
Yes
No
No
No
Yes
No
Note: No (W) means that if the define of the discrete profile fails, the restore is successful, but the target data
set remains RACF-indicated. A warning message is issued.
Protection States after a Restore: When a data set is restored, the protection
state of the target depends on the initial protection states of the source and the
target data sets, whether MENTITY is specified, and whether discrete profiles are
predefined. The following conditions may exist:
The data set was unprotected when it was dumped. The target data set may or
may not be protected after the restore. Even if you specify MENTITY, a discrete
profile is not defined.
The data set was generically protected when it was dumped. The target data
set name may or may not be protected after the restore:
If the target data set is not already protected and MENTITY is not specified, the
data set remains unprotected. If MENTITY is specified, a discrete profile is
defined:
If the define is successful, the data set is RACF-indicated. It is accessible
according to the access list for the model profile that was used.
If the define is unsuccessful, the data set remains RACF-indicated. It may
be inaccessible until a data set profile is successfully defined.
If the target data set is already protected, a discrete profile is not defined (even
if you specify MENTITY). The target data set is accessible according to the
access list of a predefined, protecting, data set profile.
235
Data Security
The source data set was RACF-indicated when it was dumped. The target data
set is RACF-indicated after the data set is restored:
If the target data set is not already RACF-indicated and if MENTITY is not
specified, a discrete profile is not defined. If MENTITY is specified, DFSMSdss
defines a discrete profile:
If the define is successful, the data set is accessible according to the
access list for the model profile that was used.
If the define is unsuccessful, the data set may be inaccessible until a data
set profile is successfully defined.
If the target data set is already RACF-indicated, a discrete profile is not defined
by DFSMSdss (even if you specify MENTITY). The target data set remains
RACF-indicated.
DFSMSdss gives you the ability to change its default operation. Via the
ADRPATCH Serviceability Aid, DFSMSdss logical restore can be instructed not
to turn on the RACF indicator for the target data set when the source data set
was RACF-indicated at dump time. The MENTITY keyword is not specified and
the target data set is protected by a generic profile. Refer to DFSMS/MVS
DFSMSdss Diagnosis Guide for additional information.
RESTORE command and the IMPORT Keyword

By default, anyone can use the IMPORT keyword of the RESTORE command to
bypass access checking of source data sets. You still need access authorization to
create or update the target data sets and catalogs. Your installation may limit use
of the IMPORT keyword as previously discussed in Protecting Usage of
DFSMSdss on page 209.
236
Compatibility Considerations
Appendix A. Compatibility Considerations

|
|
This appendix presents several considerations whenever you migrate from DFDSS
Version 2, or an earlier version of DFSMSdss, to Version 1 Release 5.
Access Authority
The type of access authority required by DFSMSdss for processing
RACF-protected data sets and password-protected data sets is the same as in
DFDSS Version 2 Release 5. Access authorization processing was significantly
enhanced in DFDSS Version 2 Release 5. See Chapter 6, Data Security and
Authorization Checking on page 207 for additional information about access
authority.
ALLMULTI Keyword
The ALLMULTI keyword is no longer supported in DFSMSdss Version 1 Release 4,
and has been replaced by the SELECTMULTI keyword. For information see the
descriptions for the SELECTMULTI keyword in the CONVERTV, COPY, and DUMP
command sections.
Concurrent Copy
DFSMSdss Version 1 Release 1 introduced the CONCURRENT keyword in the
COPY and DUMP commands. This keyword lets you to specify that the data is to
be dumped or copied concurrently with ongoing update activity. When used with
supported hardware, the dump or copy operation proceeds as if no updates had
occurred.
Track Overflow Support

DFSMS/MVS Version 1 Release 1 and later releases do not support track overflow
devices. In DFSMSdss Version 1 Release 4, most track overflow support has been
removed. You may still specify the TRACKOVERFLOW keyword, but it will be
ignored. In a future release, the TRACKOVERFLOW keyword will be a syntax error,
so remove the keyword from your JCL. You can still restore from a previously
created logical format dump of a data set that contained track overflow records.
DASD I/O Pacing

DFSMSdss Version 1 Release 1 introduced the READIOPACING keyword in the
COPY and DUMP commands. This keyword lets you to specify the pacing (that is,
the I/O delay) to be used for DFSMSdss read channel programs. You can use this
keyword to allow other applications to complete I/O processing.
237
Disaster Recovery
DFDSS Version 2 Release 5 introduced the DELETECATALOGENTRY and
IMPORT keywords to support disaster recovery operations. These keywords are
also supported by DFSMSdss Version 1 Release 1.
Validation of Indexed VSAM Data Sets

DFDSS Version 2 Release 5 introduced the VALIDATE keyword on the DUMP
command to perform validation of indexed VSAM data sets during a logical data set
dump. The validation function is the default for DFSMSdss Version 1 Release 1
although the VALIDATE keyword is still supported. You can override the validation
function by specifying the NOVALIDATE keyword on the DUMP command.
Note: Use the NOVALIDATE keyword on the DUMP command if you wish to
restore to a DFDSS Version 2 Release 5 system that does not have the
appropriate VALIDATE support, or to any level of DFDSS prior to Version 2
Release 5.
Restoring Existing DFDSS Dumps using DFSMSdss

Dumps created with an older version or release of DFDSS or DFSMSdss can be
restored with a newer version or release. IBM does not recommend and does not
guarantee that dumps created with a newer version or release of DFSMSdss can
be restored with an older version or release of DFDSS or DFSMSdss. However, if
the dump does not contain any functional changes introduced in a newer release, a
restore using an older release may be successful.
HFS, OpenEdition, SAM compressed, and extended-format KSDS data sets cannot
be restored by an older version or release of DFDSS, or by DFSMSdss prior to
Version 1 Release 2.
Table 15 on page 239 shows whether a dump created using one DFDSS or
DFSMSdss version can be restored using the system version of either DFDSS
Version 2 Release 5 or DFSMSdss Version 1.
238
Table 15. Dump and Restore Compatibility among System Versions

Restore Using
Dump Using
DFDSS Version 2 Release 5
DFSMSdss Version 1
Full
Tracks
Data Set
Full
Tracks
Data Set
Full
Yes
Yes
Yes
Yes
Yes
Yes
Tracks
No
Yes
No
No
Yes
No
Physical Data Set
No
Yes
Yes
No
Yes
Yes
Full
Yes
Yes
Yes
Yes
Yes
Yes
Tracks
No
Yes
No
No
Yes
No
Physical Data Set
No
Yes
Yes
No
Yes
Yes
Logical Data Set
No
No
Yes
No
No
Yes
Full
Yes
Yes
Yes
Yes
Yes
Yes
Tracks
No
Yes (1)
No
No
Yes (1)
No
Physical Data Set
No
Yes
Yes
No
Yes
Yes
Logical Data Set
No
No
Yes (2)
No
No
Yes
DFDSS Version 1
DFDSS Version 2
DFSMSdss Version 1
Notes:
1. (1) The DFSMSdss V1R3 without APAR OW18174, and all releases of DFDSS and DFSMSdss V1R3 cannot
restore dumps of VM-format volumes created with DFSMSdss V1R3 with APAR OW18174 or later releases
using the CPVOLUME keyword.
2. (2) DFDSS cannot restore the following data sets dumped logically by DFSMSdss:
PDSEs dumped with concurrent copy
PDSE load modules
Extended-sequential data sets
Indexed VSAM dumped with VALIDATE if the VALIDATE support is not installed
Table 16 on page 240 shows whether a dump created using one DFDSS or
DFSMSdss version can be restored using the Stand-Alone version of either DFDSS
Version 2 Release 5 or DFSMSdss Version 1.
Appendix A. Compatibility Considerations
239
Table 16. Dump and Restore Compatibility among Stand-Alone Versions

Restore Using
Dump Using
DFDSS Version 2 Release 5
DFSMSdss Version 1
Full
Tracks
Data Set
Full
Tracks
Data Set
Full
NO
NO
N/A
NO
NO
N/A
Tracks
NO
NO
N/A
NO
NO
N/A
Physical Data Set
NO
NO
N/A
NO
NO
N/A
Full
YES
YES
N/A
YES
YES
N/A
Tracks
NO
YES
N/A
NO
YES
N/A
Physical Data Set
NO
YES
N/A
NO
YES
N/A
Logical Data Set
NO
NO
N/A
NO
NO
N/A
Full
NO
NO
N/A
YES
YES
N/A
Tracks
NO
NO
N/A
NO
YES(1)
N/A
Physical Data Set
NO
NO
N/A
NO
YES
N/A
Logical Data Set
NO
NO
N/A
NO
NO
N/A
DFDSS Version 1
DFDSS Version 2
DFSMSdss Version 1
Note: (1) The DFSMSdss Stand-Alone Restore program cannot restore dumps of VM-format volumes created
with DFSMSdss V1R3 with APAR OW18174 or later releases using the CPVOLUME keyword.
240
Data IntegritySerialization
Appendix B. Data IntegritySerialization

DFSMSdss uses volume serialization and data set serialization functions to
ensure that data sets are not modified during the processing of DFSMSdss
commands. Volume serialization is accomplished by using the RESERVE macro.
Data set serialization is accomplished by using the ENQ macro and the DFSMSdss
DYNALLOC function. In the case of shared DASD, volume serialization ensures
that data sets are not being added, deleted, renamed, or extended from either the
same processor or other processors.
You can control volume serialization with the enqueue exit routine. (Refer to
DFSMS/MVS Installation Exits for additional information regarding installation
enqueue exit routines.) This allows other programs to access volumes while
DFSMSdss is running. Volume serialization, however, cannot be overridden.
DFSMSdss supports data sets that are always open, or open for long periods of
time, with backup-while-open serialization.
DFSMSdss supports backup-while-open processing for two types of data base
applications: CICS and IMS.
CICS support includes both RLS CICS and non-RLS CICS backup-while-open, and
is described in Backup-While-Open Data Sets CICS on page 249.
DFSMSdss also supports backup-while-open serialization for IMS data sets for:
Indexed VSAM data sets, such as KSDS
Non-indexed VSAM data sets, such as ESDS
Non-VSAM data sets, such as OSAM
IMS backup-while-open support is described in Backup-While-Open Data Sets
IMS on page 253.
Volume Serialization
For volume serialization, DFSMSdss issues the RESERVE macro against the
volume to prevent direct access device storage management (DADSM) functions
(such as addition, deletion, extension, or renaming of data sets) from changing the
VTOC entries during DFSMSdss processing. The RESERVE is issued before
processing is begun on a particular volume, and released when processing is
completed, during the following operations:
DUMP (except logical)

COPY (except logical)
RESTORE (except logical and physical data set)
PRINT (except data set)
DEFRAG
Note that you can use the DFSMSdss enqueue installation exit to request that
DFSMSdss only reserve the VTOC for the duration of VTOC access during the
following operations:
Full, tracks, and physical data set DUMP
Full and tracks COPY
241
Tracks PRINT
For more information on this exit, refer to DFSMS/MVS Installation Exits.
In addition, DFSMSdss issues the RESERVE macro against a volume while
updating information in the VTOC, such as the RACF-defined flag and the
data-set-changed flag. DFSMSdss also issues the RESERVE macro against a
volume while accessing the information in the VTOC to perform data set selection
during the following operations:
Logical DUMP with input volumes specified

Logical COPY with input volumes specified
CONVERTV
COMPRESS
RELEASE
Avoiding Lockout
When an application program attaches a DFSMSdss dump or restore task and a
task that invokes dynamic allocation to allocate a data set (for example, logical
restore operation) or invokes DADSM to scratch a data set, the two tasks could
lock each other out. To avoid this lockout, DFSMSdss uses the following ENQ
scheme:
Before DFSMSdss invokes DADSM SCRATCH, an exclusive ENQ is requested
for the resource with a major name of ADRLOCK and a minor name of the
volume serial number (padded with blanks to 8 bytes).
Before DFSMSdss invokes dynamic allocation to allocate a new data set on a
specific volume, a shared ENQ is requested for the resource with a major name
of ADRLOCK and a minor name of the volume serial number (padded with
blanks 8 bytes). If this is a nonspecific dynamic allocation request, an exclusive
ENQ with the resource with a major name of ADRLOCK and a minor name of
NONSPEC is requested.
If an application program invokes a DFSMSdss FULL dump operation and
plans on attaching another DFSMSdss logical restore task, the application
should request the first resource in exclusive mode (ADRLOCK, volser). The
application should request the second resource in shared mode (ADRLOCK,
NONSPEC) before attaching the FULL DUMP command task. Multiple dumps
can be active in the same address space, and a logical restore request will not
lock out that task.
If an application program issues a DADSM request, the application must
enqueue on ADRLOCK/volser in a shared ENQ or ADRLOCK/NONSPEC in
an exclusive ENQ.
Notes:
1. When DFSMSdss is invoked with JCL, lockout does not occur because
DFSMSdss allocates a volume before invoking DADSM. If a FULL DUMP
command has the volume enqueued and a restore task has been applied
against the same volume, the restore task is held until the volume is available.
2. Only non-SMS, non-VSAM DADSM requests require serialization.
242
The WAIT Option

DFSMSdss lets you change the WAIT/RETRY values for system resources. For
more information on this aid, refer to DFSMS/MVS DFSMSdss Diagnosis Guide.
Data Set Serialization

This section describes the ENQUEUE and SERIALIZATION options for data set
serialization, the WAIT option, and provides an example of RESERVE-ENQUEUE
processing.
EnqueuingENQ
The following material describes using enqueue options for data set serialization.
Enqueues are done on the data set name for the data set copy, data set dump,
data set restore, defragment, print, compress, and release operations to prevent
multiple, simultaneous updates to the same data set.
For RESTORE and COPY commands, the SHARE option applies to non-VSAM
data sets only. For the DUMP command, the SHARE option applies to non-VSAM
data sets and VSAM data sets defined with share options other than (1,3) and
(1,4).
If SHARE is not specified by the user with a DFSMSdss command, DFSMSdss
tries to provide the highest level of data integrity by defaulting to exclusive
enqueuing. If the enqueue fails, the command is put in a wait state for X seconds,
where X is specified in WAIT(numsecs,numretries), and the enqueue is retried. If
the wait-enqueue sequence fails after Y retries, where Y is specified in
WAIT(numsecs,numretries), processing ends for the data set.
In the case of a multistep job where the initiator holds a shared enqueue on the
data set, DFSMSdss upgrades the enqueue to exclusive unless SHARE is
specified. The initiator holds the exclusive enqueue until the last step in the job that
references the data set has completed.
If you specify the SHARE keyword, DFSMSdss tries an enqueue for share. If it
fails, it goes through the same logic as if SHARE had not been specified. If the
retries all fail, processing ends for the data set.
You can specify TOLERATE(ENQFAILURE) in addition to the default, ENQ, or the
SHARE option. If TOLERATE(ENQFAILURE) is specified, DFSMSdss attempts to
get the specified level of enqueue, exclusive or share. If the enqueue fails after the
specified or default number of retries, DFSMSdss processes the data set without an
enqueue. Specify TOLERATE(ENQFAILURE) if you are willing to tolerate the
exposure of not having data integrity in order to force the successful completion of
that particular data set operation. This is particularly useful when an installation has
duplicate data sets (different data sets with the same name but on different
volumes) and you want to run DFSMSdss on a data set on one volume while the
data set with the same name is being used by the system or another job on a
different volume.
243
Note: Because of ENQ contention, SYSPRINT data sets should not be allocated
on volumes being processed. TOLERATE(ENQFAILURE) cannot apply to
data movements that involve the use of utilities.
Table 17 shows the data set enqueue options.
TOLERATE(ENQFAILURE) can be used on VSAM and non-VSAM data sets.
Table 17. Data Set Enqueue Options for Non-VSAM Data Sets Specified on DFSMSdss Commands
Options
None
SHARE
TOLERATE(ENQFAILURE)
SHARE and
TOLERATE(ENQFAILURE)
Type of
enqueue
attempted
Exclusive
Share
Exclusive
Share
If enqueue is
successful
Process
Process
Process
Process
If enqueue is
not successful
Do not
process
Do not
process
Process without enqueue
Process without enqueue
Dynamic AllocationDYNALLOC
DYNALLOC is an option for the data set DUMP, data set COPY, data set
RESTORE, data set PRINT, DEFRAG, COMPRESS, and RELEASE commands. It
allows serialization of data sets across processors with shared DASD, with JES3,
and with the interface between dynamic allocation and JES3 enabled. Dynamic
allocation is used by DYNALLOC to serialize data sets. Processing time increases
because overhead is involved in dynamic allocation and serialization across
multiple processors.
If you use DYNALLOC to serialize data sets (as opposed to ENQ) the job run time
increases. If you use INDYNAM instead of DD statements to allocate DASD
volumes you do not appreciably increase run time and coding of JCL and command
input is easier.
Enqueuing versus Dynamic Allocation of Data Sets

For data set operations, the default method of serializing usage of data sets is to
enqueue on the data set name. If the DYNALLOC keyword is coded in the control
cards, the time taken to serialize is much greater than that taken by using the ENQ
macro. So use DYNALLOC keyword judiciously. Use it only on a JES3 system if
the interface between the allocation function and JES3 is not disabled. If the
interface is disabled, then the end result of serialization using ENQ is the same as
using dynamic allocation; ENQ takes much less time to serialize data sets.
When you use DYNALLOC keyword, the selected data sets are allocated to
DFSMSdss. If some data sets are allocated to the system, they can only be
processed by DFSMSdss with DYNALLOC if SHARE is also specified. Table 19 on
page 247 provides additional information on data set serialization.
244
Read/Write Serialization Scheme

Table 18 shows the serialization scheme used by all operations, except
COPYDUMP, for read/write access.
Table 18 (Page 1 of 2). Read/Write Access Serialization Scheme
ENQ Control,
Exclusive (E)
or Share (S)
ENQ Names
Major Name
ENQ Names
Minor Name
ADRDSN
Data set name
SYSDSN
Data set name
ADRDSN
GDG base name
SYSDSN
GDG base name
ADRDSN
Data set name
SYSDSN
Data set name
SYSVSAM
See Note
SYSVSAM
See Note
ADRDSN
Cluster name
SYSDSN
Cluster name
Integrated catalog facility

catalog
In addition to above
SYSIGGV2
Catalog name
SYSTEMS
On the Volume
SYSVTOC
SYSTEMS
VVDS Data Set
SYSZVVDS
Volume serial
number
SYS1.VVDS.
Vvolser
Non-VSAM Data Sets

followed by
GDG Data Sets
On the GDG Base
followed by
On each GDG Data Set
followed by
VSAM Data Sets
On each component
during data set dump
On each component
during other operations
On the cluster
followed by
Input access
Output access
ENQ Scope
E
S
E
S
(see
(see
(see
(see
Note
Note
Note
Note
1)
1)
1)
1)
STEP
E
S
E
S
E
S
E
S
(see
(see
(see
(see
(see
(see
(see
(see
Note
Note
Note
Note
Note
Note
Note
Note
1)
1)
1)
1)
1)
1)
1)
1)
STEP
SYSTEM
SYSTEM
STEP
SYSTEM
E (see Note 1)
S (see Note 1)
E
SYSTEMS
E
S
E
S
STEP
(see
(see
(see
(see
Note
Note
Note
Note
1)
1)
1)
1)
SYSTEMS
SYSTEM
SYSTEMS
S
E
245
Table 18 (Page 2 of 2). Read/Write Access Serialization Scheme

ENQ Names
Major Name
ENQ Names
Minor Name
ENQ Control,
Exclusive (E)
or Share (S)
ENQ Scope
Notes:
1. If the control for the ENQs is Exclusive or Share, the SHARE keyword determines the type of control. If
SHARE is not specified, exclusive control of the data set is obtained. If SHARE is specified, shared control of
the data set is obtained.
If shared control is obtained for a VSAM data set because the SHARE keyword was specified, other programs
will be able to obtain read access, but not write access, to the data set, while it is being processed. The
SHARE keyword is honored for VSAM data sets only during dump and only for VSAM data sets that were
defined with share options other than (1,3) or (1,4).
2. If DYNALLOC is used:
For non-VSAM data sets and GDG bases, instead of ENQ, the data set is dynamically allocated automatically,
with a disposition of OLD if SHARE is not used; otherwise, SHARE is the disposition.
For VSAM data sets, in addition to the ENQ on the components, the cluster is allocated dynamically just as
for non-VSAM data sets.
3. The minor name used to ENQ VSAM components consists of:
component name
catalog name
L1
L2
L3
L1: Total length of minor name

L2: Component name length
L3: Catalog name length
On a data set dump, a data set restore, and a DEFRAG operation, an ENQ is done once with the character
A=I and again with A=O. On a data set copy operation, an ENQ is done once with A=O.

Note: Although the ENQ on the major name ADRDSN is mostly intended to
coordinate access to data sets between multiple DFSMSdss commands, it
might be necessary for application programs that invoke DFSMSdss to
make use of the ENQ; data sets which are serialized by the application
program using dynamic allocation or an ENQ on the major name SYSDSN
could be processed by DFSMSdss unless the application uses the ENQ on
ADRDSN.
The WAIT Option

This option allows you to specify how long, in seconds, DFSMSdss is to wait for a
resource and the number of times DFSMSdss is to retry, should an ENQ or
RESERVE fail. The default is WAIT(2,2).
This means DFSMSdss is to retry twice at 2-second intervals. The WAIT keyword
does not apply to system resources such as the VTOC and the VVDS (see below).
For a data set copy or logical data set dump operation, the WAIT option has a
different meaning for serializing data sets when multiple data sets are to be
processed and WAIT(0,0) is not specified. Multiple passes are made through the
246
list of data sets that are selected. On each pass, those data sets that can be
serialized without waiting for the resource and that were not processed before are
processed. At the end of a pass, if none of the data sets could be processed
without waiting for a resource, then, in the next pass, at the first occurrence of a
data set that was not processed a WAIT is issued.
That data set and the remainder of the list is processed if possible. The above
procedure is repeated until all data sets are processed or the WAIT limits are
reached.
For example, if WAIT(3,10) is specified and 5 data sets are left to be processed, up
to 10 passes are made. On each pass, the first unprocessed data set is waited
upon for 3 seconds. Thus, only a 30-second maximum is ever waited, not 150 (5
times 3 times 10).
For system resources, such as the VTOC and the VVDS data set, the default is
WAIT(3,30). This means DFSMSdss is to retry 30 times at 3 second intervals,
resulting in a total wait time of 90 seconds.
Table 19 (Page 1 of 2). Resource Serialization
Data Set
Type
Function
|
|
|
Volume Level
Serialization
VTOC VVDS
Data Set Level

Serialization
(ENQ or
DYNALLOC)
COMPRESS
Non-VSAM
Yes
N/A
DSName
CONVERTV
Non-VSAM
Yes
N/A
DSName
Data Set COPY
Non-VSAM
VSAM
Yes
Yes
N/A
Yes
DSName
Component and
Cluster Names
DEFRAG
Non-VSAM
VSAM
Yes
Yes
N/A
Yes
DSName
Component and
Cluster Names
Full DUMP
Non-VSAM
VSAM
Yes
Yes
N/A
Yes
N/A
N/A
Data Set DUMP
Non-VSAM
VSAM
Yes
Yes
N/A
Yes
DSName
Component and
Cluster Names
Data Set PRINT
Non-VSAM
VSAM
Yes
Yes
N/A
Yes
DSName
Component Name
Tracks Print
N/A
Yes
N/A
N/A
RELEASE
Non-VSAM
VSAM
Yes
Yes
N/A
Yes
DSName
Component and
Cluster Names
Full Restore Operation
Non-VSAM
VSAM
Yes
Yes
N/A
Yes
N/A
N/A
Data Set Restore

Operation
Non-VSAM
VSAM
N/A
N/A
N/A
Yes
DSName
Component and
Cluster Names
247
Table 19 (Page 2 of 2). Resource Serialization

Data Set
Type
Function
Volume Level
Serialization
VTOC VVDS
Data Set Level

Serialization
(ENQ or
DYNALLOC)
Notes:
1. Refer to Backup-While-Open Data Sets CICS on page 249 for more information on resource
serialization.
2. VSAM data sets must be cataloged in an integrated catalog facility catalog.
3. N/A means not applicable.
An Example of RESERVE-ENQUEUE Processing

If you were to enter the following:
DUMP INDD(IN1) OUTDD(OUT1) DATASET(INCLUDE(MY.DUMP.DATASET1,MY.DUMP.DATASET2)) WAIT(5,2) SHARE
The following would result:
1. DFSMSdss issues a RESERVE command on SYSVTOC (this is the default)
If the reserve operation fails, DFSMSdss retries thirty times at 3-second
intervals, assuming that the installation has not changed the default for
system resources.
If the RESERVE command is successful, DFSMSdss continues.
If either of the data set was a VSAM or SMS-managed data set, the VVDS
would also be serialized by DFSMSdss. If VVDS serialization fails, none of the
data sets are dumped.
2. DFSMSdss issues a shared enqueue on data set name. If the shared enqueue
fails, DFSMSdss retries two times at 5-second intervals.
If the shared enqueue is successful:
DFSMSdss adds the data set name to the list to be dumped.
DFSMSdss loops back to the beginning of this step until an enqueue is
tried for all data sets.
If the shared enqueue fails, DFSMSdss:
Issues a message indicating that the data set failed serialization, and
does not process the data set.
Loops back to the beginning of this step until an enqueue is tried for all
data sets.
3. After an enqueue is tried for all specified data sets and at least one was
successful, DFSMSdss:
Dumps the VVDS (if an integrated catalog facility data set was selected)
and the VTOC and dequeues the VTOC.
Dequeues VVDS if it was enqueued.
Dumps each data set that was successfully enqueued.
Dequeues the enqueued data sets.
248
Issues message indicating which data sets were successfully processed.

Note: If you specify TOLERATE(ENQFAILURE) option with the DUMP command
and the installation options exit routine does not override it, the VTOC is not
dequeued until all the data tracks for all the data sets are dumped.
Backup-While-Open Data Sets CICS

DFSMSdss supports backup-while-open serialization, which can perform backup of
data sets that are open for update for long periods of time. It can also perform a
logical data set dump of these data sets even if another application has them
serialized. Backup-while-open is a better method than using SHARE or
TOLERATE(ENQFAILURE) for dumping Customer Information Control System
(CICS) VSAM file-control data sets that are in-use and open for update. When you
dump data sets that are designated by CICS as eligible for backup-while-open
processing, data integrity is maintained through serialization interactions between
CICS (data-base control program), CICSVR (forward-recovery program), VSAM
record management, DFSMSdfp, and DFSMSdss.
Figure 7 shows the backup-while-open serialization for dumping CICS data sets
that are open for update. Backup-while-open processing also ensures that any
update activity that may invalidate the dump is detected. Simultaneous recovery or
deletion of the data set while it is being dumped is also prevented.
(1)
(4)
SYSDSN
DFSMSdss
SYSVSAM
C IC S
Dump
Enqueue
(2)
(8)
(9)
(5)
C IC S
DFSMSdfp
BWODSN
A pp lic atio n
Services
Enqueue
(3)
M VS Alloc.
Services
and VSAM
(10)
(6)
BWO
DFSMSdss
In dica tors
R e s to re
(7 )
D ata Set
Figure 7. Block Diagram for Backup-While-Open Serialization
In Figure 7, a VSAM file-control data set (7) is allocated for CICS (1) through MVS
allocation services (3) using JCL or dynamic allocation methods. This results in
serialization through an enqueue on the name of the data set and the resource
name SYSDSN (4). When the VSAM data set is opened (3), another level of
249
serialization occurs through an enqueue on the names of the components of the

VSAM data set and the resource name SYSVSAM (4). For eligible data sets, CICS
uses DFSMSdfp (5) to set a status in the backup-while-open indicators (6) in the
catalog entry for the data set.
For a dump operation, DFSMSdss (8) attempts to acquire the SYSDSN,
SYSVSAM, and backup-while-open (9) enqueues for the data set. When the
enqueue on the cluster name of the data set and resource name of BWODSN is
acquired, but not the enqueues for both SYSDSN and SYSVSAM, DFSMSdss uses
DFSMSdfp to get the backup-while-open indicators, and starts to dump the open
data set if it is backup-while-open eligible.
The backup-while-open enqueue is used to prevent more than one DFSMSdss
operation, such as a simultaneous dump and restore (10), and to prevent the data
set from being deleted while it is being dumped by DFSMSdss.
While the data set is being dumped, a data-base application program may update
the data set in a manner that invalidates the data set. For example, a
control-interval or control-area split may occur. When this happens, VSAM record
management uses DFSMSdfp to change the backup-while-open status. When the
backup of the open data set is completed, DFSMSdss obtains the current
backup-while-open indicators and invalidates the dump of the data set if the
indicators are different from when the dump was started. When concurrent copy is
used, updates made while the data set is being dumped do not cause the dump to
be invalidated.
Backup-While-Open Status Meanings

The backup-while-open status consists of 3-bits that mean the following to
DFSMSdss:
250
Status
Meaning to DFSMSdss
000
Normal serialization and processing is used to dump the data set.
001
The data set is being forward recovered by CICSVR.
010
A control-interval split, control-area split, or extend of the data set was

either interrupted before the dump started or is currently in process. The
data set is dumped only if it is not currently in-use.
011
A control-interval split, control-area split, or extend of the data set

completed successfully, the data set was closed by CICS, and there is
no mismatch between the base cluster and any alternate index.
100
The data set may be dumped while it is open for update.
101
The data set has already been restored and is down-level; it must be
processed by CICSVR before being used by a data-base application
program.
110
The data set was updated and a split or extend is completed, which
invalidates any dump that was in progress. If concurrent copy is used,
the invalidation does not happen.
111
The data set is in an indeterminate state.
Backup-While-Open Processing
When you dump a data set, the actions that DFSMSdss takes is dependent upon
the following:
The success or failure to acquire an exclusive enqueue on the resource names
of SYSDSN, SYSVSAM, and BWODSN
The backup-while-open status before the dump
The backup-while-open indicators after the dump when the data set is dumped
while it is open for update
If DFSMSdss acquires all of the exclusive enqueues, that means the data set is not
open for update, even though it has a nonzero backup-while-open status. The
processing actions are dependent upon the initial backup-while-open status:
Status is 000. The data set is dumped as a normal data set. When it is
restored, the backup-while-open status is restored as 000.
Status is 001. The data set is dumped and the backup-while-open status is
preserved and restored when the data set is subsequently restored. This data
set is in an indeterminate state because of an incomplete forward recovery by
CICSVR and cannot be forward recovered by CICSVR after it is restored.
DFSMSdss lets you dump and restore this data set for nonstandard recovery
purposes. After the data set is restored and you have finished correcting all
errors in the data set, reset the BWO status to 000 using methods provided by
CICS. The preferred action is for you to restore an earlier dump of the data set
and use CICSVR to do forward-recovery processing to ensure data integrity is
maintained.
preserved and restored when the data set is subsequently restored. You need
to determine and take appropriate corrective action before using the data set:
If alternate indexes (AIX) are present for the sphere, do either of the
following: rebuild the AIXs from the base cluster, and reset the BWO status
to 000 using methods provided by CICS; or restore an earlier dump of the
sphere, and use CICSVR to do forward-recovery processing.
If there are no AIXs, the data set is usable as-is. Reset the BWO status to
000 using methods provided by CICS.
preserved and restored when the data set is subsequently restored. This lets
you process the data set by CICSVR prior to the data set being used by a
data-base application program.
Status is 011, 100, 110, 111. The backup-while-open status is altered to 000
before the data set is dumped. When it is restored, the backup-while-open
status is restored as 000.
If DFSMSdss acquires an exclusive enqueue on BWODSN, but not SYSDSN and
SYSVSAM, that means the data set is already open or in-use by another program.
Again, the processing actions are dependent upon the initial backup-while-open
status:
Status is 000. The data set is not eligible for backup-while-open. The data set
is not dumped unless SHARE or TOLERATE(ENQFAILURE) is specified and
the necessary conditions for those keywords are met.
251
Status is 001, 010, 011, 101, or 111. The data set is not dumped.
Status is 110. The backup-while-open status is altered to 100 and the data set
is dumped (see below).
Status is 100. The data set is dumped even though it is already in-use,
including being open for update by another program. When the data set is
restored, the backup-while-open status is set to 101 so that the data set can be
processed by CICSVR prior to use by a data-base application program. The
dump is invalidated if the backup-while-open indicators change while the data
set is being dumped. This invalidation does not occur when you use concurrent
copy.
Backup-While-Open and Concurrent Copy

Concurrent copy improves backup-while-open processing by eliminating the
invalidation of a backup-while-open dump because of updates to the data set. The
following is a comparison of the various kinds of dumps you can ask for:
Normal dump. Use of the data set must be quiesced so that serialization is
obtained, the data set is dumped, and serialization is released. The data set
cannot be used for the entire time.
Concurrent copy dump. Use of the data set must be quiesced so that
serialization is obtained, concurrent copy initialization is completed within a very
short time (compared to the actual time to dump the data set), serialization is
released, and the data set is dumped. The data set can be used after
concurrent copy initialization is complete.
Backup-while-open dump. Serialization is attempted but is not required, and the
data set is dumped. If eligible for backup-while-open, the data set is dumped
without serialization and can remain in-use for the entire time, but the dump
can be invalidated by update activity to the data set.
Backup-while-open dump using concurrent copy. Serialization is attempted but
is not required, concurrent copy initialization is completed, and the data set is
dumped. If eligible for backup-while-open, the data set is dumped without
serialization and can remain in-use for the entire time, and updates that occur
do not cause the dump to be invalidated.
To use concurrent copy, specify the CONCURRENT keyword when you dump
backup-while-open data sets.
TOLERATE(ENQFAILURE) and SHARE Considerations

Using TOLERATE(ENQFAILURE) modifies the processing and serialization for
backup-while-open data sets. The data sets are dumped when the
backup-while-open status is 100, even though none of the enqueues are
successfully acquired.
To maintain data integrity and data security, do not specify either SHARE or
TOLERATE(ENQFAILURE) when you dump backup-while-open data sets.
An exclusive enqueue on BWODSN for the data set is required for DFSMSdss to
alter the backup-while-open status. DFSMSdss only attempts an exclusive enqueue
on the BWODSN resource name. Unless the backup-while-open status is already
100, the dump fails even though you specified SHARE or
TOLERATE(ENQFAILURE).
252
Recovery Data
CICS maintains recovery data in the form of a date and time-stamp in the catalog
entry for backup-while-open data sets. This information is not used or processed by
DFSMSdss, but it is dumped and restored to preserve that information for CICSVR.
The recovery data is also printed in selected messages to assist you in your
recovery efforts.
Backup-While-Open Data Sets IMS

DFSMSdss supports backup-while-open processing of IMS data sets by providing
for concurrent copy dumps. IMS requests backup through DFSMSdsss application
programming interface, described in Appendix C, Application Programming
Interface on page 255.
Backup-while-open serialization is applicable to HISAM, SHISAM, and index
(primary and secondary) databases.
Backup as an open data set for IMS is triggered through a UIM request, rather than
through a backup-while-open status or BWO(TYPEIMS) definition as CICS does.
Specifics of IMS backup-while-open support are outlined in Table 20.
Note: VALIDATE must be specified (directly or by default) to ensure that an IMS
backup-while-open data set that is dumped while updates are being made
can be successfully restored. VALIDATE allows DFSMSdss to validate and
correct the data set during the dump process, or to end the dump (with an
ADR943E message) if the data set is in an unrecoverable state.
DFSMSdss issues an ADR943E message if the NOVALIDATE parameter is
used with an indexed VSAM data set defined as BWO(TYPEIMS).
Table 20. DFSMSdss Support for IMS Backup-While-Open Data Sets
Topic:
For IMS data sets:
Can non-VSAM data sets be dumped as open data sets?
Yes
Can nonindexed VSAM data sets be dumped as open data

sets?
Yes
Must indexed VSAM data sets be specifically designated as

being BWO-eligible to be dumped as open data sets?
No
How are indexed VSAM data sets designated as being

eligible for update activity detection through a BWO
counter?
By defining the data set as

BWO(TYPEIMS)
How is backup as an open data set triggered?
Through a UIM request
How is bypassing of enqueues on SYSDSN and SYSVSAM

managed?
Automatically
Attention: The user must be aware that COPY with DELETE, DUMP with
DELETE, and RESTORE with REPLACE can cause irreparable damage to an IMS
data set for the following reasons:
The enqueue serialization obtained by COPY and DUMP are insufficient to
ensure that the data set is not also being used by an IMS application in an
environment where GRS (or equivalent) is not being used.
253
COPY and DUMP do not provide any special handling for any data set defined
as BWO(TYPEIMS).
RESTORE does not provide any protection against reallocating or overwriting
any IMS data set for which RESTORE is able obtain an enqueue serialization
on SYSDSN and SYSVSAM.
254
Application Interface
Appendix C.
Application Programming Interface

This appendix provides information that you may need when you use the user
interaction modules. General-use programming interface and associated guidance
information is contained in this appendix. Product-sensitive programming interface
and associated guidance information is also included and is explicitly marked.
Calling Block Structure

The parameter structure outlined below is shown in block form in Figure 8 on
page 257.
ADRDSSU
The name of the DFSMSdss module main entry point.
OPTPTR
The pointer to the option list and similar to OPTIONADDR described in
DFSMS/MVS Utilities. This parameter lets you specify processing options and must
be specified even if the list is a null list. If you do not want to specify any
parameters to DFSMSdss, this pointer must point to a halfword of binary zeros. The
same values that can be specified in the EXEC PARM field in the JCL for
DFSMSdss can be specified in the option list.
The first field, called the option-list length field, is a halfword field specifying the
length of the list (excluding the field itself) as a binary value. If you do not want to
specify any options, set the option-list length field to binary zeros. In your JCL for
the calling program, if you code parameters (PARM=value) on the EXEC statement,
DFSMSdss does not recognize them unless OPTPTR points to them.
The options must comply with the parameter syntax of the DFSMSdss EXEC
parameter values. If you do not want to specify subsequent parameters, you can
omit them from the list.
DDPTR
The pointer to the DDNAME list and similar to DDNAMEADDR described in
DFSMS/MVS Utilities. The DDNAME list provides a way to specify alternate names
for the SYSIN and SYSPRINT data sets. The DDNAME list is a variable length field
made up of a halfword field followed by unseparated 8-character left-justified (right
padded with blanks) fields. Each 8-character field is reserved for a specific
DDNAME. DFSMSdss uses only two of these fields: SYSIN and SYSPRINT. The
other fields are provided as a standard implementation consistent with existing
system utility invocation procedures, must be filled with binary zeros, and are
ignored by DFSMSdss.
The first field, called the DDNAME-list length field, is a halfword field specifying the
length of the list (excluding the field itself) as a binary value for the number 48.
If you specify this parameter but do not want to specify any alternate DDNAMEs for
the SYSIN or SYSPRINT data sets, set the DDNAME-list length field to the correct
length and set all of the 8-character fields to binary zeros.
If you want to specify an alternate DDNAME for the SYSIN data set, specify this
parameter and enter the alternate DDNAME in the fifth 8-character field.
Otherwise, enter all binary zeros in the field.
255
If you want to specify an alternate DDNAME for the SYSPRINT data set, specify
this parameter and enter the alternate DDNAME in the sixth 8-character field.
Otherwise, enter all binary zeros in the field.
If you do not want to specify subsequent parameters, you can omit them from the
list.
PAGEPTR
The pointer to the page-number list and similar to HDINGADDR described in
DFSMS/MVS Utilities. This list provides a way to specify the starting page number
for system output on the SYSPRINT data set. The page-number list is a
fixed-length 6-byte field made up of a halfword field followed by a 4-byte EBCDIC
page count, which specifies the starting page number for DFSMSdss to use for the
SYSPRINT data set. If a value is specified both here and in the OPTPTR list, this
value is used, and the OPTPTR value is ignored.
The first field, called the page-number-list length field, is a halfword field specifying
the length of the list (excluding the field itself) as a binary value. The length is
usually 4.
If you do not want to specify a starting page number, set the page-number-list
length field to binary zeros. If you want to specify a starting page number, you must
specify this parameter and a 4-character page value. If the page number is
specified (page-number-list length field is not binary zeros), DFSMSdss resets this
field to the current page number upon completion of the present invocation. If the
page number is not specified, this field is not changed by DFSMSdss.
If you do not want to specify subsequent parameters, you can omit them from the
list.
UIMPTR
The pointer to the user interaction module (UIM) list. There is no comparable
parameter described in DFSMS/MVS Utilities. This parameter provides a way to
specify the name or address of a vector-implemented exit module that is to interact
with DFSMSdss for the various I/O and data set operations. The UIM list is of
variable length and consists of a halfword field followed by a 4-byte address or
8-character left-justified (padded on the right with blanks) string field that specifies
the address of the UIM entry point or the load module name (locatable through the
normal LINKLIB structure) of the UIM. If you do not want to specify a UIM, do not
specify this parameter.
The first field, called the UIM-list length field, is a halfword field specifying the
length of the list (excluding the field itself) as a binary value. If you do not want to
specify any options, set the option-list length field to binary zeros. It specifies the
length as 4 if the address of the UIM is being passed, or as 8 if the name of the
UIM is being passed.
If you want to specify a UIM, you must specify the name or address of the UIM in
the field following the UIM-list length field. See System Programming Information
on page 259 for more details on the use of this module.
UAPTR
The pointer to the user-area list. There is no comparable parameter in
DFSMS/MVS Utilities. This parameter provides a way to specify the address of an
area to be passed to the UIM at each DFSMSdss exit point. The user-area list is of
fixed length, consisting of a halfword field called the user-area-list length field, and
a single 4-byte address that locates the user area starting address.
256
If you use the user area, the length must be set to 4 and the address of the user
area must be specified in second field.
ASIDPTR
The pointer to the address-space-identifier list. There is no comparable parameter
described in DFSMS/MVS Utilities. This optional parameter, which is applicable
only when you use ADRXMAIA instead of ADRDSSU, lets you specify an identifier
for the address space that ADRXMAIA uses for the DFSMSdss program. The
address-space-identifier list is of fixed length, consisting of a halfword field and a
single 8-byte character field. The default value is DFSMSDSS.
The first field, called the address-space-identifier list length field, is a halfword field
specifying the length (0 to 8) of the list (excluding the field itself) as a binary value.
The second field, called the address-space identifier, contains an 8-character,
left-justified (padded on the right with blanks) string that is used to identify the
address space for DFSMSdss.
PARAM
On the ATTACH and LINK macros, the keyword with which you specify the names
of the pointers that are passed to DFSMSdss
VL
Indicates that the list is variable length. Both the ATTACH and LINK macros
require specifying VL=1.
L e n g th
R E G 1
o p t io n s
O P TP TR
X
D D P TR
'0 0 3 0 '
PA G E P TR
U IM P T R
U A P TR
'0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 '
'0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 '
'0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 '
'0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 '
'S Y S I N '
'S Y S P R I N T '
A S ID P T R
L e n g th
Id e n tifie r
X
X
'0 0 0 4 '
'0 0 0 4 '
a d d re s s
C 'N N N N '
A D R 1 S R 0 7
le n g th
C 'M O D U L E - N A M E '
o r
a d d re s s
Figure 8. DFSMSdss Application Interface Structure
Appendix C.
257
User Interactions
For user interactions to take place, the Application Interface must invoke
DFSMSdss by using the name of the user interaction module (UIM) exit routine
supplied to DFSMSdss. DFSMSdss can be invoked by any of the following system
macros:
ATTACH EP=ADRDSSU,PARAM=(OPTPTR,DDPTR,PAGEPTR,UIMPTR,UAPTR),VL=1
LINK EP=ADRDSSU,PARAM=(OPTPTR,DDPTR,PAGEPTR,UIMPTR,UAPTR),VL=1
CALL (15),(OPTPTR,DDPTR,PAGEPTR,UIMPTR,UAPTR),VL
Optionally, to use the DFSMSdss Cross Memory Application Interface use one
of the following system macros:
ATTACH EP=ADRXMAIA,PARAM=(OPTPTR,DDPTR,PAGEPTR,UIMPTR,UAPTR),VL=1
LINK EP=ADRXMAIA,PARAM=(OPTPTR,DDPTR,PAGEPTR,UIMPTR,UAPTR),VL=1
CALL (15),(OPTPTR,DDPTR,PAGEPTR,UIMPTR,UAPTR),VL
Optionally, to use the DFSMSdss Cross Memory Application Interface and
specify an 8-character Address Space name, use one of the following system
macros:
ATTACH EP=ADRXMAIA,PARAM=(OPTPTR,DDPTR,PAGEPTR,UIMPTR,UAPTR,ASNPTR),VL=1
LINK EP=ADRXMAIA,PARAM=(OPTPTR,DDPTR,PAGEPTR,UIMPTR,UAPTR,ASNPTR),VL=1
CALL (15),(OPTPTR,DDPTR,PAGEPTR,UIMPTR,UAPTR,ASNPTR),VL
As shown in Figure 8 on page 257, a pointer to the UIM exit is passed in the
parameter list (UIMPTR). User interactions involve:
Record management
Controlling processing of data sets
Gathering statistics on DFSMSdss operations
See Appendix D, Examples of the Application Program with the User Interaction
Module (UIM) on page 287 for an explanation of the various UIM exits.
When a UIM exit routine is specified, DFSMSdss processes normally, then at each
point in the process (DFSMSdss exit points), the UIM exit routine is called
conditionally to allow some types of user operations.
If a DFSMSdss subtask abnormally ends for any reason, it cannot make any further
calls to the UIM, including the function ending call.
Notes:
1. DFSMSdss runs as an authorized problem program.
2. Any program invoking DFSMSdss must also be authorized and in a
nonsupervisor state.
3. ADRXMAIA is the name of the DFSMSdss Cross-Memory Application Interface
module main entry point. Use ADRXMAIA instead of ADRDSSU when
DFSMSdss functions are to be executed in a specific address space.
4. ADRXMAIA runs as an authorized program and supports both supervisor-state
callers and problem-state callers.
258
System Programming Information

Some bit definitions in the installation options control block (ADRUFO) permit
DFSMSdss to communicate with the installation options exit routine. When the
installation options exit does not want a function to be scheduled, it returns a code
of 8. For the UIM to do this requires a bit definition of UFSTOP to be set in the
ADRUFO. If a SYSIN or SYSPRINT data set is not to be allocated or all
SYSIN/SYSPRINT is to be handled in storage, UFSYSIN and UFSYSPR specify
this to DFSMSdss.
If the application allows DFSMSdss to handle SYSPRINT by not setting UFSYSPR,
then the application can not write to SYSPRINT directly. The application can only
insert SYSPRINT records at UIM exit points 2 or 10. If the application chooses to
handle SYSPRINT by setting UFSYSPR, then the application is responsible for
printing DFSMSdss messages from UIM exit points 2 or 10.
Three additional bits determine allowances within the UIM interaction: UFAIINV,
UFUIMAL and UFUIMCH. Two additional bits indicate the existence or absence of
an input restore/copydump data set or an output dump/copydump data set:
UFNOIN and UFNOOUT respectively. Refer to DFSMS/MVS Installation Exits for
more information about the installation options exit routine.
When DFSMSdss has been invoked by using the Application Interface and the UIM
has been specified and is to be called, the following information is passed to the
UIM on every exit call:
Register 1, which points to the interface parameter list pointer.
The interface parameter list pointer, which points to the DFSMSdss exit
identification block. See ADREID0 Data Area on page 278 for a detailed
description of this block. This list consists of:
A halfword field specifying the length of the remainder of the list.
The remainder of the list that is mapped by the macro ADREID0. See Exit
Identification Block on page 260 below for the information contained in this
block.
Upon return from the UIM, the user return code field is examined to determine the
disposition of the current I/O record or data set (within the limits allowed to the
exit).
Application Interface Blocks
REG 1
Length
Interface Pointer
Exit Identification Block
ADR1SR08
The parameter structure described in Figure 8 on page 257 can be viewed in block
form as shown in Figure 9.
Figure 9. DFSMSdss Exit Interface Structure
Appendix C.
259
Exit Identification Block

The exit identification block is passed to the user interaction module every time
DFSMSdss gives control to it. Each field is described below, but see ADREID0
Data Area on page 278 for the formal declarations.
Control Block Eye-Catcher A 4-character string field that is supplied by
DFSMSdss. It contains the character string EIDB and can aid in locating the
control block when you are viewing a storage dump during DEBUG
processing.
TASK-ID A fullword binary field that is supplied by DFSMSdss. The number
contained in this field is assigned by DFSMSdss to each function command
statement submitted in SYSIN, whether obtained from the data set or from the
UIM. This number is binary zero when DFSMSdss is calling the UIM for a
function that is not related to a user command statement. Each command is
numbered in sequence. When a task is scheduled to process this command,
all messages associated with this task and all calls to the user interaction
module for this task are accompanied by this unique number. In this way, the
UIM can identify which task is being processed and what function is
associated with that task.
User Exit Allowance A fullword binary field supplied by DFSMSdss. The 32 bits
defined in this field can be used as flags to determine what actions the UIM
can perform with respect to the record presented. The following actions are
conditionally allowed:
View and conditionally override the installation options.

Insert data prior to current record.
Replace the current data record with an exit-record supplied.
Delete the current data record.
Modify the current data record.
Disconnect the exit from further interaction.
Recognize when a disallowed option has been attempted.
End processing of the data set.
End processing of the task.
DFSMSdss Processing Option A halfword binary field that is supplied by

DFSMSdss. The number contained in this field can be used by the user
interaction module (UIM) to vector branch to the appropriate processing
routine for the record or data set being presented to the exit.
At appropriate locations in the DFSMSdss processing modules, the user
interaction module is considered for receiving control. These locations are
referred to as DFSMSdss exit points.
User Return Code A halfword binary field that is supplied by the UIM. This return
code identifies the action expected by the exit on the record or data set being
presented to the exit. DFSMSdss examines this field when control returns
from the UIM. Not all the following return codes are allowed at any given exit
call. If a disallowed code is returned from the UIM, DFSMSdss passes the
EIDB back to the UIM with the EIXERR flag set. This allows the UIM one
chance to correct the option. If a disallowed code is returned again, it is
ignored by DFSMSdss and the record is processed as though the exit had
returned the code zero (0). If a valid code is returned, DFSMSdss processing
is the same as if the valid code had been passed back on the initial UIM
invocation. This sequence is followed for any subsequent incorrect return
260
codes. The return codes that are allowed at any given exit call are specified in
the EIXALLOW field.
The meaning of each return code for those exits presenting records to the
UIM (Eioptions 1 to 26) is:
0
The record is processed as would normally have happened if there

had not been a UIM. The original record is not changed in any way
by the exit.
The record was replaced by the exit. The new record must be
placed in the area pointed to by the original record pointer field and
its length stored in the original record length field.
The record is to be inserted. The address of the new record must be

stored in the original record pointer field or the new record must be
stored in the area pointed to by the original record pointer field and
its length must be stored in the original record length field. When
this exit is next called, the original record is presented again.
12
The record is to be deleted. The record presented to the UIM is

ignored in the processing, thus deleting it.
16
The record was modified by the exit. This return code is the only
one allowing the original record to be altered and then to be
processed by DFSMSdss. Any changes made to the record must be
logically correct because DFSMSdss cannot assure the validity of
these changes.
Notes:
1. You cannot change the record length when you modify the
record (as contrasted with reason code 4).
2. If the record being processed is the installation options record
(ADRUFO) and any values have been changed, return code 16
must be returned or the changes are ignored.
20
The record is to be processed as though a return code zero (0) had

been given, but this particular DFSMSdss exit point is no longer
called from the current functional task, although it might be called
from others. You must be cautious in using this code because
multiple record types use the same DFSMSdss exit point. It would
be better for the UIM to inspect each record type and only give a
return code zero (0) when a record is not of interest to the exit.
24
The record is to be processed but at all future visits of DFSMSdss at

this exit point, only user statistical records are to be presented to the
UIM.
28
The notification-of-response return code. The WTOR has been

handled by the UIM and the UIM has supplied the proper response
from the WTOR in the area pointed to by the original record pointer.
The interface allows you to handle all WTOR processing in the UIM
exit routine and to supply the required response to DFSMSdss in
lieu of DFSMSdsss issuing the WTOR itself. Note that the UIM must
set the original record length to the proper value.
32
DFSMSdss ends the current functional task and issues message

ADR356E.
Appendix C.
261
The meaning of each return code for those exits controlling data set
processing (Eioptions 21, 22, 23, and 26) is:
0
The data set is processed as would normally have happened if there

had not been a UIM. Data set processing is not altered in any way.
16
This return code is valid from exit 22 only. It indicates to DFSMSdss

to examine the bypass processing flags and to modify processing of
the data set according to which flags are on. These bypass flags are
only examined by DFSMSdss if a return code of 16 is returned. See
Bypass Verification Exit (Eioption 22) on page 271 for more details
about these flags.
20
The record is to be processed as though a return code zero (0) had

been given, but this particular DFSMSdss exit point is no longer
called from the current functional task, although it might be called
from others. You must be cautious in using this code because
multiple record types use the same DFSMSdss exit point. It would
be better for the UIM to inspect each record type and only give a
return code zero (0) when a record is not of interest to the exit.
32
DFSMSdss ends the current functional task and issues message

ADR356E.
36
DFSMSdss ends processing of the data set named in the parameter

passed to the exit. Processing continues with the next data set (if
any). If Exit 23 sets this return code after the data set has already
been processed, then DFSMSdss does not undo the processing, but
deletes the data set from the successfully-processed message list (if
applicable) and includes it in the unsuccessfully-processed message
list even though the data set may have been successfully processed
up to that point
Record Area Length A fullword binary field that is supplied by DFSMSdss. The
number contained in this field represents the total length of the area in which
the original record is stored. The number can be used by the UIM to verify
that replacement and inserted records fit in the provided buffer area pointed to
by the original record pointer field.
Original Record Length A fullword binary field that is supplied by DFSMSdss but
can be changed by the UIM. The number contained in this field represents the
total length of the record pointed to by the original record pointer. The length
includes just the length of the record pointed to by the original record pointer
field and does not include the length of this field itself. The value of this field
is zero when the UIM is called to supply in-storage SYSIN data.
Original Record Pointer A fullword address field that is supplied by DFSMSdss
but can be changed by the UIM. This field contains the address of the record
being passed to the UIM on this call. This address normally is not changed by
the exit unless an insertion is being used. Refer to the proper return code
descriptions for the effect on this field. The value of this field is zero when the
UIM is called to supply in-storage SYSIN data. The location of the original
record, above or below the 16-megabyte (MB) virtual storage line, is
controlled by using the installation options exit. If this record is to be above
16MB, the UIM has to run in 31-bit addressing mode in order to address the
record.
262
User Area Pointer A fullword address field that is supplied by the application
program and is maintained by DFSMSdss. This field contains the address of
the user data/work area that was supplied by the application program as a
communications area for UIM internal process controls. DFSMSdss saves this
pointer and supplies it in the EIUSEPTR field of the exit identification block on
each call to the UIM. If any UIM exit changes the user area pointer,
DFSMSdss presents the updated pointer on subsequent calls to the UIM.
Each DFSMSdss functional task keeps its own copy of the user area pointer.
If the pointer is changed by the UIM for one task, it is not changed for any
other task. At the beginning of each task, the user area pointer is the one
passed to DFSMSdss by the application program.
DDNAME/VOLID Pointer A fullword address field supplied by DFSMSdss. It
contains the address of an area containing the DDNAME of the output dump
data set, left-justified in an 8-byte area, followed by a 6-byte area containing
the volume serial number of the volume containing the dump data set, also
left-justified. This pointer is valid only for the full-volume dump exit, EIOP06.
Cross-Memory Application Interface Restrictions

Use SDUMP and SMSGCNT in place of ABEND and AMSGCNT when the
Cross-Memory Application Interface is used. Although ABEND and AMSGCNT are
supported by DFSMSdss, no dump is printed because DD allocations (SYSABEND,
SYSUDUMP) in the application address space are unavailable to the address
space producing the abend.
Serialization may operate differently, as application address space DD allocations
are unavailable to the address space executing the DFSMSdss functions. Evaluate
your serialization requirements when considering the use of the Cross-Memory
Application Interface.
When multiple ADRDSSU tasks are executing in a DFSMSdss server address
space, and identical DDNAMEs are passed in the SYSIN stream, allocation errors
(such as MSGIKJ56246I file in use) can result. To avoid this possibility, use
8-character DDNAMEs or leave enough room after the DDNAME to allow ddname
replacement. The Cross Memory Application Interface replaces common DDNAMEs
passed in the SYSIN stream with unique 8-character, system-generated DDNAMEs
whenever possible.
|
|
|
|
|
If you use the DFSMSdss Cross Memory Application Interface to DUMP and
RESTORE HFS type data sets, you must define a DFSMSDSS user ID in order for
the DFSMSdss SERVER address spaces to be able to access the HFS data sets.
The DFSMSDSS user ID must be set up for the OpenEdition MVS access as
follows:
|
|
The default group for the DFSMSDSS user ID must have an OMVS segment
defined and a group ID associated with it.
The home directory should be the root file system.
The DFSMSDSS user ID should be defined as a superuser (with a UID of 0):
ADDUSER DFSMSDSS DFLTGRP(OMVSGRP) OMVS(UID() HOME('/'))

For more information, refer to MVS/ESA System Product Version 5, Planning:
OpenEdition MVS SC233015.
Appendix C.
263
|
|
JOBCAT and STEPCAT are not supported when performing DFSMSdss functions
in a SERVER address space.
User Interaction Module Exit Option Descriptions

Following are the descriptions for all of the exit points available with DFSMSdss.
Function Startup (Eioption 0)

This exit point is called during DFSMSdss initialization and again during function
initialization (such as a dump or restore operation). The EIRECPTR points to the
EIREC00 data area. The EIREC00 data area contains a field, EI00SBPL, which the
application may use to return a subpool number that is to be shared between all
DFSMSdss tasks. EI00SBPL is only valid when EITSKID is zero.
The application may also set EI00SENQ to request that VTOC serialization be held
only for the duration of VTOC access. This flag is only valid for full volume dump
operations and when EITSKID is nonzero. This flag provides a function similar to
that provided by the Enqueue InstallationWide Exit Routine (see DFSMS/MVS
Installation Exits). The VTOC serialization is released after VTOC access is
complete if either the EI00SENQ flag is set or the Enqueue InstallationWide Exit
Routine requests it.
The valid return codes for function startup are:
0
16
Continue normal processing

Record modified
20
Inhibit all UIM calls Not valid when EITSKID is zero and either
UFSYSIN or UFSYSPR was set in the installation options exit, or
EITSKID is nonzero and either UFNOIN or UFNOOUT was set in the
installation options exit.
32
End processing. Only valid for a full dump and a full restore operation.
Reading SYSIN Record (Eioption 1)

This exit point is called after DFSMSdss reads a SYSIN record. You can
replace, insert, delete, or modify a SYSIN record at this exit point. The
EIRECPTR points to the SYSIN record. The valid return codes are:
0
4
8
12
16
264

Record replaced
Insert record
Delete record
Record modified
20
Disconnect exit
Printing SYSPRINT Record (Eioption 2)

This exit point is called when DFSMSdss is ready to print a SYSPRINT record. You
can replace, insert, delete, or modify a SYSPRINT record at this exit point. The
EIRECPTR points to the SYSPRINT record. Task-related SYSPRINT records are
presented in task order unless the UIM requested that there be no SYSPRINT (see
System Programming Information on page 259).
The valid return codes for printing SYSPRINT records are:
0
4
8
12
16
20

Record replaced
Insert record
Delete record
Record modified
Disconnect exit
Notes:
1. When DFSMSdss is printing a page header record, you can only modify or
delete the record.
|
|
|
|
|
2. EIXNTERR is set ON if an Etype message other than ADR324E,

ADR347E, ADR348E when the TOL(IOERR) keyword is specified, or
ADR367E when the TOL(IOERR) keyword is specified, is issued by
DFSMSdss. EIXNTERR is also set ON if a Ttype message is issued by
DFSMSdss.
|
|
|
|
EIXNTERR will be set OFF if an Itype or Wtype message is issued by

DFSMSdss. EIXNTERR is also set OFF if ADR324E, ADR347E, ADR348E
when the TOL(IOERR) keyword is specified, or ADR367E when the
TOL(IOERR) keyword is specified, is issued by DFSMSdss.
|
|
EIXNTERR is unchanged if a nonprefixed message is issued by

DFSMSdss.
Reading Physical Tape Record (Eioption 3)

This exit point is called when DFSMSdss has read a record from a data set that
has been dumped (on tape or DASD) by using the DUMP command. The
EIRECPTR points to the tape record. The valid return codes are:
0

Insert record Only valid when UFNOIN is set in the installation options
exit
Appendix C.
265
20
Disconnect exitOnly valid when UFNOIN is not set in the user

installation options exit
32
End function
Reading Logical Tape Record (Eioption 4)

This exit point is called when DFSMSdss has read a record from a data set
which was created with a DUMP command and dumped on tape or DASD. The
EIRECPTR points to the tape record. The valid return codes are:
0
8
20
24
32

Insert record
Disconnect exit
Select user statistics records
End function.
Note: If code 24 is returned, DFSMSdss only calls this exit point when
DFSMSdss processes user statistics records.
Writing Logical Tape Record (Eioption 5)

This exit point is called when DFSMSdss writes a logical record to a dump data
set, on tape, or on DASD, while performing a dump operation. If you insert a
record at this exit point, DFSMSdss marks it as a statistics record, not a data
record. The EIRECPTR points to the tape record. The valid return codes are:
0
8
20
32

Insert record
Disconnect exit
End function.
Writing Physical Tape Record (Eioption 6)

This exit point is called when DFSMSdss writes a physical record to a dump
data set, on tape, or on DASD. The EIRECPTR points to the tape record and
the EIDDID points to EIDDINFO. The valid return codes are:
0

12
Delete record Only valid when UFNOOUT is set in the installation

options exit
20
Disconnect exitOnly valid when UFNOOUT is not set in the user

266
32
End function.
Reading Disk Track (Eioption 7)

This exit point is called when DFSMSdss has read a track from DASD. The
EIRECPTR points to the track buffer. The first 64 bytes (X'40') of the track
buffer are IBM internal information which is followed by the ADRTAPB area, the
DTTTRK area, and the track image. The ADRTAPB and the DTTRK areas are
defined in the DFSMS/MVS DFSMSdss Diagnosis Guide. The valid return
codes are:
0
20
32

Disconnect exit
End functionOnly valid for a full dump
Writing Disk Track (Eioption 8)

This exit point is called when DFSMSdss is ready to write a track to DASD.
The EIRECPTR points to the track buffer. The valid return codes are:
0
20
32

Disconnect exit
End functionOnly valid for a full restore operation
Reading Utility SYSPRINT (Eioption 9)

This exit point is called when DFSMSdss is reading output from an attached
utility. You can replace, insert, delete, or modify a utility SYSPRINT record at
this exit point. The EIRECPTR points to the Utility SYSPRINT record. The valid
return codes are:
0
4
8
12
16
20

Record replaced
Insert record
Delete record
Record modified
Disconnect exit
Writing SYSPRINT Record (Eioption 10)

This exit point is called when DFSMSdss is ready to write a SYSPRINT record.
You can replace, insert, delete, or modify the SYSPRINT record at this exit
point. The EIRECPTR points to the SYSPRINT record. Task-related SYSPRINT
records are not presented in task order. The valid return codes are:
0
4
8
12
16
20

Record replaced
Insert record
Delete record
Record modified
Disconnect exit
Appendix C.
267
Writing WTO Message (Eioption 11)

This exit point is called when DFSMSdss is ready to write a WTO message.
You can replace, insert, delete, or modify the WTO message at this exit point.
The EIRECPTR points to the WTO message. The valid return codes are:
0
4
8
12
16
20

Record replaced
Insert record
Delete record
Record modified
Disconnect exit
Writing WTOR Message (Eioption 12)

This exit point is called when DFSMSdss is ready to write a WTOR message
(that is, ADR369D, ADR345D, and ADR371D). You can insert or modify the
WTOR message at this exit point. You can also return the response to
DFSMSdss with return code 28. The EIRECPTR points to the WTOR message.
The valid return codes are:
0
8
16
20
28

Insert record
Record modified
Disconnect exit
WTOR response
Presenting ADRUFO Record (Eioption 13)

This exit point is called when DFSMSdss is ready to set up the installation
options specified in the ADRUFO control block. You can modify the control
block to override any options that have been specified thus far. You must use
return code 16 for DFSMSdss to recognize the new options. The EIRECPTR
points to ADRUFO. The valid return codes are:
0
16
32

Record modified
End functionOnly valid for a full dump and a full restore operation.
Function Ending (Eioption 14)

This exit point is called when DFSMSdss is ready to end the task. The
EIRECPTR points to the last message with highest nonzero return code. The
record contains the DFSMSdss return code and the DFSMSdss message
(message number and message type). The valid return code is:
0
268
Presenting WTOR Response (Eioption 15)

This exit point is called when the operator has responded to the WTOR (either
a DFSMSdss WTOR or a user inserted WTOR, see exit point 12). You can only
examine the response at this exit point. If you would like to change the
response, you must use exit point 12, change the response, and use a return
code of 28 to DFSMSdss. The EIRECPTR points to the response. The valid
return code is:
0
OPEN/EOV Tape Volume Security and Verification Exit (Eioption 16)

This exit point is called when DFSMSdss is ready to open a tape. You can bypass
password and expiration date checking for tape volumes or reject the volume and
request a scratch tape with this exit by placing a return code in the first word of the
record pointed to by EIRECPTR. DFSMSdss passes this return code to
OPEN/EOV. The EIRECPTR points to the parameter list described by the
IECOEVSE macro.
Refer to the DFSMS/MVS Planning for Installation for more information. The
valid return codes are:
0
16
20
32

Record modified
Disconnect exit
End functionOnly valid for a full dump and a full restore operation
OPEN/EOV Nonspecific Tape Volume Mount (Eioption 17)

This exit point is called when a nonspecific tape is passed to DFSMSdss. The
EIRECPTR points to the DCB exit parameter list. You can specify a specific volume
serial with this exit by placing the volume serial in the first 6 bytes of the record
pointed to by EIRECPTR. DFSMSdss passes this volume serial and return a code
of 4 to OPEN/EOV informing it to use the specified volume serial. The EIRECPTR
points to the parameter list described by the IECOENTE macro.
Note: DEFER must be specified in the JCL for this exit to be called. Refer to the
DFSMS/MVS Planning for Installation for more information.
0
16
20
32

Record modified
Disconnect exit
End functionOnly valid for a full dump and a full restore operation
Insert Logical VSAM Record During Restore (Eioption 18)

This exit point is called during a logical restore operation of a VSAM KSDS
using record-level I/O. You can replace or modify a record at this exit point.
The EIRECPTR points to the logical record that DFSMSdss is preparing to
write to the data set. Additional information can be found in DFSMS/MVS Using
Data Sets . The valid return codes are:
0
4
16
20

Record replaced
Record modified
Disconnect exit
Appendix C.
269
Output Tape I/O Error (Eioption 19)

This exit point is called during a dump when a tape has a permanent I/O error.
The EIRECPTR points to EIDDINFO. The valid return codes are:
0
20
32

Disconnect exit
End function
Volume Notification (Eioption 20)

During physical data set restore operations, this exit is called to provide information
about the data set being allocated. This information includes:
Cluster/data set name (for RENAME and RENAMEUNCONDITIONAL
keywords, the new data set name is presented)
An indication of whether the data set is VSAM or non-VSAM
Number of data and index components (VSAM only)
For each component or data set:
The number of volumes it resides on
The volume serial number of each volume
An RBA token for each volume.
EIRECPTR points to EIREC20. EI20DA@ and EI20IX@ point to EI20DSI.
Note: SMS-managed multivolume non-VSAM data sets have an RBA token only
for the first volume. Non-SMS-managed data sets never have an RBA
token.
0
20
32

Disconnect exit
End functionOnly valid for full or physical data set dump and full or
physical data set restore operations
Data Set Verification (Eioption 21)

This exit lets the UIM end logical copy, dump, and restore processing for
individual data sets. This exit is given control through the UIM at the start of
logical copy, dump, and restore processing for each data set. DFSMSdss
provides the UIM with the data set name through the EIREC21 structure within
the exit identification block, ADREID0. EIREC21 is shown in Table 21 on
page 278. The name provided is the original data set name prior to rename
processing, if any, for copy and restore functions. The UIM returns to
DFSMSdss with a return code in the exit identification block. The valid return
codes are:
0
20
32
36

Disconnect exit
End function
End data set
DFSMSdss continues processing with the next data set, if any. If the user
specifies the SPHERE keyword and processing for a base cluster is
ended through this exit, processing for all AIXs related to the base cluster
is also ended. If the user specifies the SPHERE keyword and the UIM
attempts to end processing for an AIX that is related to a base cluster that
was selected for processing, DFSMSdss invokes the UIM again. If the
270
UIM attempts to end processing for the AIX again, DFSMSdss issues
warning message ADR770W and ignores the request. If the user does not
specify the SPHERE keyword, AIXs can be ended even if they are related
to base clusters selected for processing. Ending a base cluster without
the SPHERE keyword does not cause any related AIXs to be ended.
Note: See the Note for Eioptions 21, 22, 23 on page 275.
Bypass Verification Exit (Eioption 22)

This exit lets a user force DFSMSdss bypass serialization and security
verification during logical copy, dump, and restore processing for individual data
sets. It also lets a user turn on a tolerate-migrated-volser indicator that forces
DFSMSdss to restore a data set with a migrated volser. This exit is given
control through the UIM at the start of logical copy, dump, and restore
processing for each data set. DFSMSdss provides the UIM with the data set
name through the EIREC22 structure within the exit identification block,
ADREID0. EIREC22 is shown in Table 21 on page 278. The data set name
provided is the original name prior to rename processing, if any, for COPY or
RESTORE. The UIM returns to DFSMSdss with a return code in the exit
identification block. The valid return codes are:
0
16

Bypass one or more of the following:
If the Reset indicator (EI22RSET) is set on by the UIM for a VSAM
data set during a logical data set dump, DFSMSdss resets the
data-set-changed flag in the VTOC if the data set is successfully
serialized and processed. DFSMSdss will not reset the
data-set-changed flag for data sets dumped with RLS access and
BWO data sets, even if EI22RSET is set on by the UIM.
If the Shared SYSDSN ENQ indicator (EI22SSYS) is set on by the
UIM for a VSAM data set during logical data set dump, DFSMSdss
attempts to obtain a shared SYSDSN enqueue. If EI22SSYS is not
set on, then the type of SYSDSN enqueue (shared or exclusive) that
DFSMSdss attempts to obtain depends upon whether or not the
SHARE keyword was specified.
If the Mark-As-Recovery-Required indicator (EI22RRB) is set on by
the UIM during logical restore, DFSMSdss marks the target data set
as recovery required, provided that the target data set is
SMS-managed.
If the Log Information Passed indicator (EI22LINF) is set on by the
UIM during a logical restore, then DFSMSdss uses the log parameter
(EI22LPRM) and the log stream ID (EI22LSID) as the log information
for the target data set, provided that the target data set is
SMS-managed. If EI22LINF is not set, or the target data set is not
SMS-managed, then the contents of EI22LPRM and EI22LSID are
ignored.
If the BWO_ALLOWED Passed indicator (EI22BWOP) is set on by
the UIM during a logical restore, the DFSMSdss uses the
BWO_ALLOWED field (EI22BWOA) for the target data set, provided
the target data set is SMS-managed. If EI22BWOP is not set or the
target data set is not SMS-managed, then the contents of EI22BWOA
are ignored.
Appendix C.
271
Serialization is bypassed if the UIM exit turns on the Bypass

Serialization indicator, EI22BSER. Serialization is bypassed for the
source data set for copy and dump processing, and for the target data
set for copy and restore processing. DFSMSdss assumes that all
necessary serialization has been performed by the invoker of
DFSMSdss, but does not ensure that this is true. DFSMSdss
performs normal serialization if the UIM exit does not turn on the
bypass serialization indicator.
DFSMSdss does not delete or uncatalog data sets that were
bypassed for serialization even if the DELETE or UNCAT keywords
are specified. If a preallocated data set is not large enough during a
data set restore operation and the bypass serialization indicator is on,
DFSMSdss does not scratch and reallocate that target data set and
the restore operation fails.
RACF verification and all other data set security checking is bypassed
if the UIM exit turns on the Bypass RACF indicator, EI22BSEC. If
EI22BSEC is set on, DFSMSdss checks to ensure that the application
program is authorized to bypass RACF and security processing. The
application program is authorized to bypass RACF and security
processing if NOPASS was specified on the PPT statement of the
SCHEDxx parmlib member. If the EI22BSEC indicator is on and
NOPASS was specified, RACF verification and all other data set
security processing including password checking is bypassed.
DFSMSdss does not do any RACF authorization checks. DFSMSdss
does not create any RACF profiles for the copied or restored target
data set. DFSMSdss assumes that all necessary RACF authorization
and security checking has already been performed by the invoker of
DFSMSdss. For a copy or restore operation, RACF profiles are not
created for the target data set.
If the user turns on the bypass RACF indicator and PASS was
specified on the PPT statement of the SCHEDxx parmlib member,
DFSMSdss sets the error flag, EIXERR, on in the exit identification
block and invokes the UIM again. If the user sets the bypass RACF
indicator again, DFSMSdss issues error message ADR772W and
processing continues as normal. DFSMSdss still allows serialization to
be bypassed and tolerates migrated volume serial number processing
if those indicators are set.
DFSMSdss performs normal RACF and security processing if the UIM
exit does not turn on the bypass RACF indicator.
If the Tolerate-Migrated-Volser indicator is set on by the UIM,
DFSMSdss takes special action to support the restoration of a
non-VSAM data set with a volume serial number of MIGRAT for a
logical data set restore operation in an SMS-managed environment or
when the CATALOG option has been specified. DFSMSdss ignores
the EI22BMIG indicator for copy and dump operations and VSAM
data sets.
When DFSMSdss is restoring a non-VSAM data set and the
Tolerate-Migrated-Volser indicator is set on, a catalog LOCATE is
issued to determine the status of the data set being restored. Based
on the result of that LOCATE, different actions are taken.
272
No catalog entry is found: The data set being restored is not

considered to be migrated. A normal DFSMSdss logical restore is
performed. The Tolerate-Migrated-Volser indicator is ignored.
A catalog entry is found but the VOLSER is not MIGRAT: The data
set being restored is not considered to be migrated. Normal
processing continues as though the indicator had not been set.
A catalog entry is found and the VOLSER is MIGRAT: The data set is
migrated and requires special processing. Instead of cataloging the
data set after allocating it, DFSMSdss alters the existing MIGRAT
volume serial number entry to the actual volume the data set was
restored to. Once the catalog entry has been changed from MIGRAT
to the new data sets volume serial numbers, the restore continues as
normal.
Note: Because the migrated data set is not recalled during this
restore, the user of this interface is responsible for deleting the
migrated copy of the data set and updating the necessary
control files.
DFSMSdss performs normal non-VSAM data set cataloging if the UIM
exit does not turn on the tolerate-migrated-volser indicator.
If the Extent Reduction bit (EI22EXTR) is set on by the UIM for a
given data set and DFSMSdss is running in an SMS-managed
environment, DFSMSdss tries to allocate the original volume where
the data set was dumped.
If the Restore-To-Like-Device bit (EI22LIKE) is set on by the UIM for
a given data set and DFSMSdss is running in an SMS-managed
environment, DFSMSdss tries to allocate the target data set on a
device whose unit is the same as that of the source data set. If
DFSMSdss can not allocate the target data set on a device whose
unit type matches that of the source, the data set is not processed.
Serialization by enqueuing on the major name of SYSDSN for a data
set is bypassed if the UIM exit turns on the bypass SYSDSN
indicator, EI22NSYS; other enqueues for a data set (for example,
SYSVSAM), are not bypassed. The SYSDSN-level of enqueue
serialization is bypassed for the source data set for DUMP, and the
target data set for RESTORE. DFSMSdss performs normal
serialization if both EI22BSER and EI22NSYS are off.
DFSMSdss does not delete or uncatalog data sets if EI22NSYS is
set, even if the DELETE or UNCATALOG keywords are specified. If
EI22NSYS is on and the preallocated data set is too small, the data
set is not scratched and reallocated; the RESTORE fails.
20
32
If the UIM exit sets the return code to EIRC16 but fails to turn on any of
the bypass verification indicators, DFSMSdss ignores all bypass options
and performs normally. If the UIM exit sets the return code to EIRC16 for
a VSAM data set and turns on the tolerate-migrated-volser indicator,
DFSMSdss does not treat it as an error condition and ignores the
tolerate-migrated-volser indicator.
Disconnect exit
End function
Appendix C.
273
36
End data set

Refer to EIRC36 in Data Set Verification (Eioption 21) on page 270 for
details on ending spheres.
Note: See the Note for Eioptions 21, 22, 23 on page 275.
Data Set Processed Notification Exit (Eioption 23)

This exit indicates to the UIM whether or not the logical copy, dump, or restore
processing for individual data sets was successful. This exit is given control through
the UIM at the conclusion of logical copy, dump, and restore processing for each
data set. DFSMSdss provides the UIM with information through the EIREC23
structure within the exit identification block, ADREID0. EIREC23 is shown in
Table 21 on page 278.
DFSMSdss provides the UIM with the following information at the conclusion of
processing for logical dump of each data set:
0
4
8
12
16
The data set name that was dumped

The RLS time stamps associated with the dump
A flag indicating whether or not the data set is marked recovery required
A return code for the data set that indicates whether processing was
successful
Data set completely successful (informational)
Data set partially successful (warning)
Data set unsuccessful (error)
Ending error
Ending error
The source SMS flag (DS1SMSFG) from the Format 1 DSCB

The source data set organization (DS1DSORG) from the Format 1 DSCB
for a non-VSAM data set
Flags to indicate data set type for a VSAM data set
DFSMSdss provides the UIM with the following information at the conclusion of
processing for a logical copy and a logical restore of each data set:
The original data set name that was copied or restored. This is the data set
name prior to rename processing, if any.
The new data set name being copied or restored if rename processing was
performed.
A return code for the data set that indicates whether processing succeeded:
0
Data set completely successful (informational)
4
Data set partially successful (warning)
8
Data set unsuccessful (error)
12 Ending error
16 Ending error
274

The source and target SMS flags (DS1SMSFG) from the Format 1 DSCB.
The source and target data set organization (DS1DSORG) from the Format 1
DSCB for a non-VSAM data set.
Flags to indicate data set type for a VSAM data set.
A count of the volumes that the data set was copied or restored to.
A list of the volume serial numbers (VOLSERs) that the data set was copied or
restored to.
The UIM returns to DFSMSdss with a return code in the exit identification block.
0
20
32
36

Disconnect exit
End function
End data set
It does not undo any successful processing, but deletes the data set from
the successfully-processed message list (if applicable) and includes it in
the unsuccessfully-processed message list. It is the responsibility of the
user of this interface to delete the copied, dumped, or restored data set
from the target volumes. DFSMSdss continues processing with the next
data set, if any. Refer to EIRC36 in Data Set Verification (Eioption 21)
on page 270 for details on ending spheres.
Note for Eioptions 21, 22, 23: If Eioptions 21, 22, and 23 end the function (UIM
passes back a return code 32 to DFSMSdss) during data set copy
operation, DFSMSdss can be processing more than one data set at the
time. This can happen if utilities are needed to process some of the data
sets. DFSMSdss does the following before ending:
No unprocessed data sets are scheduled for processing.
All data sets in utility processing are allowed to complete normally.
No new calls are made to exits 21, 22, or 23. This includes data sets in utility
processing that are allowed to complete.
Spheres that are being processed because of the SPHERE keyword and that
are not complete at the end of the function have the target parts deleted to
preserve sphere integrity. Preallocated spheres are left partially copied.
Spheres being processed without the SPHERE keyword or individual sphere
components being copied are left partially completed.
Concurrent Copy Initialization Complete (Eioption 24)

DFSMSdss calls the UIM with option code 24 to inform it that the initialization of the
concurrent copy session for a given data set or volume has completed. For
full-volume or tracks operation, there is only one call (because there is only one
input volume). For a physical data set operation, there is one call for each input
volume. For a logical data set operation, there is one call for every data set.
Appendix C.
275
DFSMSdss does not call the UIM with this option code if the CONCURRENT
keyword is not specified. DFSMSdss provides the UIM with information through the
EIREC24 structure within the Exit Identification Block, ADREIB (in the ADREID0
macro).
DFSMSdss provides the UIM with the following information:
A return code indicating whether or not the concurrent copy session
initialization succeeded:
0
4
Concurrent copy session initialization was successful and any

serialization on the data has been released.
Concurrent copy session initialization failed. If this is a logical data set
operation, this data set is not processed using concurrent copy, but
other data sets may be. If this is a full-volume, tracks, or physical data
set operation, concurrent copy is not used. In either case, serialization
is obtained and released as if CONCURRENT were not specified.
When this exit is called, DFSMSdss may not be holding any
serialization.
A reason code providing further details about the status of the concurrent
copy session initialization (always valid, even for a zero return code):
|
|
|
|
|
|
|
|
|
|
|
|
|
|
0
4
8
12
16
20
24
28
32
36
The concurrent copy operation is logically complete at this time (data

movement has not been done yet).
All parts of the data being dumped or copied were not on hardware
supporting concurrent copy.
Hardware limits exceeded.
System data mover failed.
Host limits exceeded.
System data mover not available.
Other host error.
Data set type not supported for concurrent copy.
The concurrent copy operation is logically and physically complete at
this time (data movement has been done).
The data being processed requires the use of Snapshot, but the
Snapshot software support is not available on the system.
The volume serial of the volume on which the concurrent copy initialization
was attempted (valid only if the reason code is not 16).
The name of the data set on which the concurrent copy initialization was
attempted (valid only if a logical data set operation is being performed).
A flag indicating whether or not DFSMSdss has reset the data-set-changed
flag in the VTOC for the data set (valid only if a logical data set dump
operation is being performed).
The UIM returns to DFSMSdss with a return code in the Exit Identification Block.
DFSMSdss continues to process based on that return code, as follows:
00
20
32

Disconnect this exit
The DFSMSdss function is ended (not valid for a physical data set dump or
logical data set copy)
Error handling is the same as described under User Return Code on page 260.
276
Dump Volume Output Notification (Eioption 26)

Exit 26 of the DFSMSdss UIM may be used to determine the following:
When a new dump output volume has been added for each DDNAME being
processed. (DFSMSdss sets EI26VOL with EI26DDN and EI26VSER.)
When a dump output volume associated with a specific DDNAME receives a
terminating error condition. (DFSMSdss sets EI26TERM with EI26DDN and
EI26VSER. EI26VTRC contains the failing function return code.)
When an R0 count mismatch occurs during dump processing for
BWO(TYPEIMS) KSDS data sets when EI22IMS is on. (DFSMSdss sets
EI26ROCE. The data set name is located by EI26DSN.)
The UIM presents a return code to DFSMSdss in the Exit Identification Block.
DFSMSdss continues to process based on that return code, as follows:
00
20
32
DFSMSdss continues normal processing

Disconnect this exit
DFSMSdss ends the function (valid only for EI26TERM)
More information about the Exit 26 record can be found Dump Volume Output
Notification (Eioption 26).
Avoiding Lockout
Refer to Avoiding Lockout on page 242 for a description of the ENQ scheme to
prevent lockout.
Application Interface Summary

For Record Processing, if the UIM makes any changes to the presented record
(assuming it can validly do so), return code 16 must be returned or the changes are
ignored. If the record is to be replaced in total, return code 4 must be returned or
the original record is used. If a record is to be inserted before the current record,
return code 8 must be returned or the record is ignored. If the current record is to
be deleted, return code 12 must be returned or the current record is processed. If
the exit is no longer interested in processing any records appearing at the current
DFSMSdss exit point, return code 20 must be returned or the exit is called at the
next visitation of DFSMSdss to the exit point. The current record is still processed
in either event. If you want to receive only user statistical records at any specific
exit, return code 24 must be returned. If you want to process a WTOR within the
UIM, the response must be returned to DFSMSdss with a return code 28.
If a record is being returned that is longer than the original record, the exit must
either replace the record in the area pointed to by the original record pointer (as
long as it does not exceed the length in EIRECALN) or supply another area and
store the address to the record in the original record pointer field. In either case,
the length must be stored in the original record length field and a return code of 4
must be used.
Appendix C.
277
If a record is being returned that is shorter than the original record, the exit can
supply an area and store the address to the record in the original record pointer
field or, if allowed, can replace the original record with the shorter one. In either
case, the length of the new record must be placed in the original record length field.
If the new area option was used, return code 4 must be used. If the new record
overlaid the original, return code 16 must be used. Table 21 on page 278
describes the data area corresponding to the DFSMSdss exit identification block.
For Data Set Processing, Eioptions 21, 22, and 23 are three exits that give you
added control over data set processing during a logical data set copy, dump, and
restore operations. These exits are called immediately before and immediately after
processing each data set, on a data set by data set basis, and allow you to make a
number of processing changes.
Eioptions 21 and 22 are called, one after the other, at the start of processing of
each data set. DFSMSdss passes each exit the name of the data set being
processed. Based on that name, each exit lets you:
End processing of just that data set (return code 36)
End processing of the whole functional task (return code 32)
Disconnect the exit so that it is no longer called prior to subsequent data sets
being processed by that task (return code 20)
Do nothing (return code 0).
Eioptions 22 only: Modify how the data set is to be processed (return code 16).
See Bypass Verification Exit (Eioption 22) on page 271 for details.
Eioption 23 is called immediately after a data set is processed and lets you end
processing of the data set, end processing of the task, disconnect the exit, or do
nothing.
ADREID0 Data Area

Table 21 describes the data area corresponding to the DFSMSdss exit
identification block.
Table 21 (Page 1 of 4). ADREID0 Mapping Macro
Offsets
278
Dec
Hex
Type
Len
Name (Dim)
Description
0
0
2
6
10
10
(0)
(0)
(2)
(6)
(A)
(A)
42
2
4
4
4
1
11
(B)
12
12
13
(C)
(C)
(D)
14
16
(E)
(10)
STRUCTURE
SIGNED
CHARACTER
SIGNED
BITSTRING
BITSTRING
1... ....
.1.. ....
..1. ....
...1 ....
.... 1...
.... .1..
.... ..1.
.... ...1
BITSTRING
1... ....
.111 1111
BITSTRING
BITSTRING
BITSTRING
1... ....
.111 1111
SIGNED
SIGNED
ADREIB
EIDLLEN
EIID
EITSKID
EIXALLOW
EIXALOW0
EIXREP
EIXINS
EIXDEL
EIXMOD
EIXDIS
EIXWTOR
EIXSTAT
EIXTERM
EIXALOW1
EIXTDSET
*
EIXALOW2
*
EIXALOW3
EIXERR
*
EIOPTION
EIRETCOD
LENGTH OF ADREIB - 2
BLOCK IDENTIFIER EBCDIC "EIDB"
TASK ID NUMBER
USER EXIT ALLOWANCE OPTIONS
ALLOWANCE OPTION BYTE 1
ALLOW REPLACE OF RECORD
ALLOW INSERTION OF RECORD
ALLOW DELETION OF RECORD
ALLOW MODIFICATION OF RECORD
ALLOW DISCONNECT OF EXIT
ALLOW WTOR RESPONSE
ALLOW SELECTION OF USER STATS
ALLOW FUNCTION TERMINATION
ALLOW DATA SET TERMINATION
UNUSED
RESERVED
DISALLOWED OPTION ATTEMPTED
RESERVED
PROCESSING OPTION
EXIT RETURN CODE
1
1
1
2
2

Offsets
Dec
Hex
Type
Len
Name (Dim)
Description
18
22
26
30
34
38
38
(12)
(16)
(1A)
(1E)
(22)
(26)
(26)
SIGNED
SIGNED
ADDRESS
ADDRESS
ADDRESS
BITSTRING
BITSTRING
1... ....
4
4
4
4
4
4
1
EIRECALN
EIRECLEN
EIRECPTR
EIUSEPTR
EIDDID
EIXFLAGS
EIXFLAG0
EIXABEND
RECORD AREA LENGTH

ORIGINAL RECORD LENGTH
ORIGINAL RECORD ADDRESS
USER DATA AREA ADDRESS
EIOP06 DDNAME/VOLID PTR
OTHER FLAGS
FLAG BYTE 0
FOR EIOP02 ONLY, 1=MESSAGE IS ADR013
INDICATING AN ABEND CONDITION
FOR EIOP02 ONLY, 1=MESSAGE IS TYPE 'E'
AND IS NOT 324 OR 347
FOR EIOP14 ONLY, 1=WARNING MSGS WERE
ISSUED AND NONE ARE FATAL
TRACK IS IN ERROR
RESERVED
FLAG BYTE 1
RESERVED
RESERVED
DUMMY SOURCE TAPE
DUMMY TARGET TAPE
APPL USING XMAPI
XMAPI - DYNALOC SYS
RESERVED
FLAG BYTE 2
RESERVED
FLAG BYTE 3
RESERVED
FORCE SIZE OF CONTROL BLOCK TO WORD
BOUNDARY
39
(27)
40
40
41
41
42
(28)
(28)
(29)
(29)
(2A)
.1.. ....
EIXNTERR
..1. ....
EIXWNGOK
...1 ....
.... 1111
BITSTRING
1... ....
.1.. ....
..1. ....
...1 ....
.... 1...
.... .1..
.... ..11
BITSTRING
BITSTRING
BITSTRING
BITSTRING
CHARACTER
1
1
1
1
EIXTRKER
*
EIXFLAG1
*
*
EIXTDUMS
EIXTDUMT
EIXTISXM
EIXDASYS
*
EIXFLAG2
*
EIXFLAG3
*
*
Note: THE FOLLOWING MAPS THE RECORD PRESENTED BY EXIT 6 AND POINTED TO BY EIDDID.
0
(0)
STRUCTURE
0
(0)
CHARACTER
8
(8)
CHARACTER
14
(E)
UNSIGNED
15
(F)
UNSIGNED
Note: THE FOLLOWING MAPS THE RECORD PRESENTED BY EXIT 00
0
0
1
16
8
6
1
1
(FUNCTION
EIDDINFO
EIDDNAME
EIVOLID
EIRETC
*
STARTUP).
(0)
(0)
(1)
UIM-06 INFO
O/P DEVICE DDNAME
O/P VOLSER
RESERVED FOR RETCODE
RESERVED FOR FLAGS
STRUCTURE
16
EIREC00
UNSIGNED
1
EI00SBPL
BITSTRING
1
EI00FLGS
1... ....
EI00SENQ
.1.. ....
EI00NONF
..11 1111
*
2
(2)
CHARACTER
14
*
Note: THE FOLLOWING MAPS THE RECORD PRESENTED BY EXIT 14: DSS MESSAGE NUMBER ASSOCIATED
0
0
4
4
7
8
(0)
STRUCTURE
16
EIREC14
(0)
CHARACTER
4
EI14RC
(4)
CHARACTER
4
EI14MESS
(4)
CHARACTER
3
EI14MNUM
(7)
CHARACTER
1
EI14MTYP
(8)
CHARACTER
8
EI14CPUT
Note: THE FOLLOWING MAPS THE RECORD PRESENTED BY EXIT 20: VOLUME NOTIFICATION EXIT.
0
0
44
(0)
(0)
(2C)
STRUCTURE
CHARACTER
BITSTRING
1... ....
56
44
1
SHARED SUBPOOL NUMBER

STARTUP FLAGS
SHORT VTOC ENQUEUE
DON'T ALLOW IGWNOTIF CALL
RESERVED
RESERVED
WITH NON-ZERO RETCODE.
DSS RETURN CODE
DSS MESSAGE
MESSAGE NUMBER
MESSAGE TYPE
DSS CPU TIME
EIREC20
EI20DSN
EI20FLGS
EI20VSAM
DATA SET NAME/CLUSTER NAME

SOME FLAGS:
1=DATA SET IS VSAM 0=DATA SET IS
NONVSAM
.1.. ....
EI20RACF
1=DATA SET IS PROTECTED BY A DISCRETE
RACF PROFILE
..11 1111
*
RESERVED
45
(2D)
CHARACTER
1
*
RESERVED
46
(2E)
UNSIGNED
1
EI20DA#
NUMBER OF DATA COMPONENTS
47
(2F)
UNSIGNED
1
EI20IX#
NUMBER OF INDEX COMPONENTS (0 IF
NONVSAM)
48
(30)
ADDRESS
4
EI20DA@
POINTER TO DATA COMPONENT INFO FOR
VSAM/DATA SET INFO FOR NONVSAM
52
(34)
ADDRESS
4
EI20IX@
POINTER TO INDEX COMPONENT
Note: INFO FOR VSAM/0 FOR NONVSAM FOR A NON-VSAM DATA SET, EI20DA@ POINTS TO A SINGLE EI20DSI STRUCTURE. FOR A VSAM CLUSTER,
EI20DA@ POINTS TO AN ARRAY OF STRUCTURES (ONE FOR EACH DATA COMPONENT), AND EI20IX@ POINTS TO A SIMILAR ARRAY FOR THE INDEX
COMPONENTS.
0
(0)
STRUCTURE
60
0
(0)
CHARACTER
44
44
(2C)
UNSIGNED
2
46
(2E)
CHARACTER
2
48
(30)
CHARACTER
12
48
(30)
CHARACTER
6
54
(36)
CHARACTER
2
56
(38)
UNSIGNED
4
Note: THE FOLLOWING MAPS THE RECORD PRESENTED BY EXIT 21: DATA SET
0
0
(0)
(0)
STRUCTURE
CHARACTER
44
44
EI20DSI
EI20CON
EI20NVOL
*
EI20VLI
EI20VOL
*
EI20RBA
VERIFICATION EXIT.
EIREC21
EI21DSN
Appendix C.
DATA SET INFO

COMPONENT NAME (BLANKS FOR NONVSAM)
# OF VOLUMES IN DS
RESERVED
VOLUME INFORMATION
VOLSER
RESERVED
RBA TOKEN
DATA SET/CLUSTER NAME
279

Offsets
Dec
Hex
Type
Len
Name (Dim)
Description
Note: THE FOLLOWING MAPS THE RECORD PRESENTED BY EXIT 22: BYPASS VERIFICATION EXIT.
0
0
44
(0)
(0)
(2C)
45
45
46
48
(2D)
(2D)
(2E)
(30)
49
(31)
50
(32)
STRUCTURE
CHARACTER
BITSTRING
1... ....
.1.. ....
102
44
1
..1. ....
EI22BMIG
...1 ....
.... 1...
EI22NSYS
EI22LIKE
.... .1..
EI22EXTR
.... ..1.
.... ...1
CHARACTER
CHARACTER
CHARACTER
BITSTRING
1... ....
.1.. ....
..1. ....
...1 ....
.... 1...
.... .1..
.... ..1.
.... ...1
1... ....
.1.. ....
..11 1111
BITSTRING
1... ....
.1.. ....
..1. ....
...1 ....
5
1
2
2
.... 1...
.... .1..
.... ..1.
EI22SIRS
*
EI22SFLG
E22SSMSF
E22SDSRG
E22SVFLG
E22SESDS
E22SKSDS
E22SKRDS
E22SLDS
E22SRRDS
E22SPSSI
E22SVVDS
E22SBCS
E22SAIX
E22SVRRD
*
EI22FLG2
EI22RSET
EI22SSYS
EI22RRB
EI22LINF
EI22BWOP
EI22IMS
EI22BWOE
.... ...1
CHARACTER
1
CHARACTER
26
BITSTRING
1
1111 ....
.... 1111
79
(4F)
CHARACTER
23
Note: THE FOLLOWING MAPS THE RECORD PRESENTED BY EXIT 23: DATA SET
280
EIREC22
EI22DSN
EI22FLGS
EI22BSER
EI22BSEC
*
EI22LPRM
EI22LSID
EI22FLG3
EI22BWOA
*
*
PROCESSED
51
52
78
(33)
(34)
(4E)
0
0
(0)
(0)
STRUCTURE
CHARACTER
*
141
EIREC23
EI23CNST
0
44
88
90
90
91
93
(0)
(2C)
(58)
(5A)
(5A)
(5B)
(5D)
CHARACTER
CHARACTER
SIGNED
CHARACTER
CHARACTER
CHARACTER
BITSTRING
1... ....
.1.. ....
..1. ....
...1 ....
.... 1...
.... .1..
44
44
2
5
1
2
2
EI23DSN
EI23NEWN
EI23DSRC
EI23SFLG
E23SSMSF
E23SDSRG
E23SVFLG
E23SESDS
E23SKSDS
E23SKRDS
E23SLDS
E23SRRDS
E23SPSSI
94
(5E)
95
95
96
98
(5F)
(5F)
(60)
(62)
.... ..1.
.... ...1
1... ....
.1.. ....
..1. ....
...1 ....
.... 1111
CHARACTER
CHARACTER
CHARACTER
BITSTRING
1... ....
.1.. ....
..1. ....
5
1
2
2
E23SVVDS
E23SBCS
E23SAIX
E23BCSEL
E23SVRRD
EI23RRB
*
EI23TFLG
E23TSMSF
E23TDSRG
E23TVFLG
E23TESDS
E23TKSDS
E23TKRDS

EXIT 22 FLAGS:
1=BYPASS SERIALIZATION
1=BYPASS DATASET LEVEL, STORCLAS &
MGMTCLAS SECURITY CHECKS. ALSO
BYPASS JES3 INTEGRITY CHECKS AND DO
NOT CREATE DISCRETE DATASET PROFILES.
1=TOLERATE MIGRATED VOLSER FOR
NONVSAM DSETS (RESTORE ONLY) @DS007
BYPASS SYSDSN ENQ SWAPPED W/ EI22SIRS
RESTORE/COPY DATA SET TO A LIKE DEVICE
TYPE
RESTORE DATA SET TO EXTENT REDUCTION
VOLUME
SET INCMPLT RECALL SWAPPED W/ EI22NSYS
RESERVED
SOURCE DATA SET FLGS
SOURCE SMS FLAGS
SOURCE DATA SET ORG
SRCE VSAM DSET FLAGS
1=ESDS DATA SET
1=KSDS DATA SET
1=KRDS DATA SET
1=LINEAR DATA SET
1=RRDS DATA SET
1=PAGE/SWAP/STGINDEX, ETC. UNSUPPRTED
DATA SETS
1=VVDS DATA SET
1=BCS DATA SET
1=AIX DATA SET
VRRDS DATASET
RESERVED
MORE EXIT 22 FLAGS
RESET DS CHANGED FLAG
GET SHARED SYSDSN ENQ
MARK TGT RECOVRY REQ'D
LOG INFO PASSED, SEE EI22LPRM AND
EI22LSID
BWO_ALLOWED PASSED, SEE EI22BWOA
CALLER IS IMS
ENQ ON BWODSN ONLY, NO ADR OR SYS
ENQ'S
UNUSED
LOG PARAMETER FOR TGT
LOG STREAM ID FOR TGT
MORE EXIT 22 FLAGS
BWO_ALLOWED
UNUSED
AVAILABLE
NOTIFICATION EXIT.
CONSTANT LENGTH PORTION OF CONTROL
BLK
NEW DSET/CLUSTER NAME
RETURN CODE FOR DATA SET PROCESSING
SOURCE DATA SET FLAGS
SOURCE SMS FLAGS
SOURCE DATA SET ORG
SOURCE VSAM DSET FLAGS
1=ESDS DATA SET
1=KSDS DATA SET
1=KRDS DATA SET
1=LINEAR DATA SET
1=RRDS DATA SET
1=PAGE/SWAP/STGINDEX, ETC.
UNSUPPORTED DATA SETS
1=VVDS DATA SET
1=BCS DATA SET
1=AIX DATA SET
1=BASE CLUSTER SELECTED
VRRDS DATASET
RECOVERY REQUIRED
UNUSED
TARGET DATA SET FLAGS
TARGET SMS FLAGS
TARGET DATA SET ORG
TARGET VSAM DSET FLAGS
1=ESDS DATA SET
1=KSDS DATA SET
1=KRDS DATA SET

Offsets
Dec
Hex
Type
Len
...1 ....
.... 1...
.... .1..
Name (Dim)
Description
1=LINEAR DATA SET

1=RRDS DATA SET
1=PAGE/SWAP/STGINDEX, ETC.
UNSUPPORTED DATA SETS
.... ..1.
E23TVVDS
1=VVDS DATA SET
.... ...1
E23TBCS
1=BCS DATA SET
99
(63)
1... ....
E23TAIX
1=AIX DATA SET
.1.. ....
E23TVRRD
VRRDS DATASET
..11 1111
*
RESERVED
100
(64)
CHARACTER
16
EI23RLST
RLS TIME STAMPS
100
(64)
CHARACTER
8
EI23GMT
RLS GMT TIME STAMP
108
(6C)
CHARACTER
8
EI23LOC
RLS LOCAL TIME STAMP
116
(74)
CHARACTER
8
E23BYTES
DS BYTE COUNT
124
(7C)
CHARACTER
1
E23FLGS
MISC FLAGS
1... ....
E23BSET
1=E23BYTES SET
.1.. ....
E23BPDS
1=BROKEN PDS
..11 1111
*
RESERVED.
125
(7D)
CHARACTER
6
EI23DNAM
NAME OF DEVICE NEEDED TO DO
NOPACKING FOR THE BROKEN PDS (I.E. A
LIKE DEVICE)
131
(83)
CHARACTER
9
*
RESERVED
140
(8C)
UNSIGNED
1
EI23VOL#
NUMBER OF VOLUMES
141
(8D)
CHARACTER
6
EI23VSER (*)
VOLSER ARRAY
Note: THE FOLLOWING MAPS THE RECORD PRESENTED BY EXIT 24: CONCURRENT COPY INITIALIZATION COMPLETE.
0
0
2
4
8
14
58
(0)
(0)
(2)
(4)
(8)
(E)
(3A)
0
0
(0)
(0)
0
4
68
69
72
E23TLDS
E23TRRDS
E23TPSSI
STRUCTURE
83
EIREC24
UNSIGNED
2
EI24RTCD
RETURN CODE
UNSIGNED
2
EI24RSCD
REASON CODE
UNSIGNED
4
*
RESERVED
CHARACTER
6
EI24VOL
VOLUME SERIAL
CHARACTER
44
EI24DSN
DATA SET NAME
BITSTRING
1
EI24FLGS
FLAGS
1... ....
EI24RSET
DS CHANGE FLAG RESET
.111 1111
*
UNUSED
59
(3B)
CHARACTER
24
*
AVAILABLE
Note: THE FOLLOWING MAPS THE RECORD PRESENTED BY EXIT 26: DUMP OUTPUT VOLUME MOUNT NOTIFICATION EXIT.
128
4
(0)
(4)
(44)
(45)
(48)
STRUCTURE
BITSTRING
1... ....
.1.. ....
..1. ....
...1 1111
BITSTRING
CHARACTER
UNSIGNED
UNSIGNED
CHARACTER
3
64
1
3
8
EIREC26
EI26TYPE
EI26VOL
EI26TERM
EI26R0CE
*
*
EI26DSN
EI26DSNL
*
EI26DDN
80
(50)
CHARACTER
EI26VSER
86
88
92
(56)
(58)
(5C)
CHARACTER
UNSIGNED
ADDRESS
2
4
36
*
EI26VTRC
*
Appendix C.
EXIT TYPE
OUTPUT VOLUME NOTIFICATION
OUTPUT VOLUME TERMINATED
BWO R0 COUNT ERROR
UNUSED
RESERVED FOR EXPANSION
DSNAME IF EI26ROCE = '1'B
LENGTH OF DSNAME
RESERVED FOR ALIGNMENT
OUTPUT DDNAME IF EI26VOL OR EI26TERM
SET
VOLSER - PRESENT IF EI26VOL OR EI26TERM
SET
RESERVED FOR ALIGNMENT
VOLUME TERMINATION RETURN
RESERVED FOR EXPANSION
281
Constants
Len
Type
Value
Name
Description
CHARACTER
EIDB
ADREIBID
BLOCK IDENTIFIER
DECIMAL
EIRC00
CONTINUE NORMAL PROCESS
DECIMAL
EIRC04
RECORD REPLACED
DECIMAL
EIRC08
INSERT RECORD
DECIMAL
12
EIRC12
DELETE RECORD
DECIMAL
16
EIRC16
RECORD MODIFIED
DECIMAL
20
EIRC20
DISCONNECT EXIT
DECIMAL
24
EIRC24
SELECT USER STATS RECS
DECIMAL
28
EIRC28
WTOR RESPONSE
DECIMAL
32
EIRC32
TERMINATE FUNCTION
DECIMAL
36
EIRC36
TERMINATE DSET ONLY
DECIMAL
EIOP00
FUNCTION STARTUP ENTRY
DECIMAL
EIOP01
READING SYSIN RECORD
DECIMAL
EIOP02
PRINTING SYSPRINT RECORD
DECIMAL
EIOP03
READING PHYSICAL TAPE
DECIMAL
EIOP04
READING LOGICAL TAPE
DECIMAL
EIOP05
WRITING LOGICAL TAPE
DECIMAL
EIOP06
WRITING PHYSICAL TAPE
DECIMAL
EIOP07
READING DISK TRACK
DECIMAL
EIOP08
WRITING DISK TRACK
DECIMAL
EIOP09
READING UTILITY SYSPRINT
DECIMAL
10
EIOP10
WRITING UTILITY SYSPRINT
DECIMAL
11
EIOP11
WRITING WTO MESSAGE
DECIMAL
12
EIOP12
WRITING WTOR MESSAGE
DECIMAL
13
EIOP13
PRESENTING ADRUFO REC
DECIMAL
14
EIOP14
FUNCTION TERMINATION
DECIMAL
15
EIOP15
PRESENTING WTOR RESPONSE
DECIMAL
16
EIOP16
TAPE VOL SECURITY
DECIMAL
17
EIOP17
TAPE MOUNT(NON-SPEC)
DECIMAL
18
EIOP18
INSERT LOGICAL REC
DECIMAL
19
EIOP19
TAPE OUTPUT ERROR
DECIMAL
20
EIOP20
VOLUME NOTIFICATION
DECIMAL
21
EIOP21
DSET VERIFICATION
DECIMAL
22
EIOP22
BYPASS VERIFICATION
DECIMAL
23
EIOP23
DS PROC NOTIFICATION
DECIMAL
708
VOLSLST
MAX SIZE OF VOLSER LIST FOR EIREC23 (118 6)
DECIMAL
24
EIOP24
CC INIT DONE
DECIMAL
25
EIOP25
BACKSPACE TAPEIN
DECIMAL
26
EIOP26
VOLUME OPEN FOR O/P
DECIMAL
48
EXITRECL
EXIT RECORD LEN
DECIMAL
42
EIDBLEN
LENGTH OF BLOCK
Cross Reference
Name
Hex Offset Hex Value Level
ADREIB
EIDDID
EIDDINFO
EIDDNAME
EIDLLEN
EIID
EIOPTION
EIRECALN
EIRECLEN
EIRECPTR
EIREC00
EIREC14
EIREC20
282
0
22
0
0
0
2
E
12
16
1A
0
0
0
1
2
1
2
2
2
2
2
2
2
1
1
1
Name
EIREC21
EIREC22
EIREC23
EIREC24
EIREC26
EIRETC
EIRETCOD
EITSKID
EIUSEPTR
EIVOLID
EIXABEND
EIXALLOW
EIXALOW0

0
0
0
0
0
E
10
6
1E
8
26
A
A
80
1
1
1
1
1
2
2
2
2
2
4
2
3
Name
EIXALOW1
EIXALOW2
EIXALOW3
EIXDASYS
EIXDEL
EIXDIS
EIXERR
EIXFLAGS
EIXFLAG0
EIXFLAG1
EIXFLAG2
EIXFLAG3
EIXINS
EIXMOD
EIXNTERR
EIXREP
EIXSTAT
EIXTDSET
EIXTDUMS
EIXTDUMT
EIXTERM
EIXTISXM
EIXTRKER
EIXWNGOK
EIXWTOR
EI00SBPL
EI14CPUT
EI14MESS
EI14MNUM
EI14MTYP
EI14RC
EI20CON
EI20DA#
EI20DA@
EI20DSI
EI20DSN
EI20FLGS
EI20IX#
EI20IX@
EI20NVOL
EI20RACF
EI20RBA
EI20VLI
EI20VOL
EI20VSAM
EI21DSN
EI22BMIG
EI22BSEC
EI22BSER
EI22BWOA
EI22BWOE
EI22BWOP
EI22DSN
EI22EXTR
EI22FLGS
EI22FLG2
EI22FLG3
EI22IMS
EI22LIKE
EI22LINF
EI22LPRM
EI22LSID
EI22NSYS
EI22RRB
EI22RSET
EI22SFLG
EI22SIRS
EI22SSYS
EI23CNST
EI23DNAM
EI23DSN
EI23DSRC
EI23GMT
EI23LOC
EI23NEWN

B
C
D
27
A
A
D
26
26
27
28
29
A
A
26
A
A
B
27
27
A
27
26
26
A
0
8
4
4
7
0
0
2E
30
0
0
2C
2F
34
2C
2C
38
30
30
2C
0
2C
2C
2C
4E
32
32
0
2C
2C
32
4E
32
2C
32
33
34
2C
32
32
2D
2C
32
0
7D
0
58
64
6C
2C
04
20
08
80
40
10
40
80
02
80
20
10
01
08
10
20
04
40
80
20
40
80
F0
02
08
04
04
08
10
10
20
80
02
40
3
3
3
4
4
4
4
2
3
3
3
3
4
4
4
4
4
4
4
4
4
4
4
4
4
2
2
2
3
3
2
2
2
2
1
2
2
2
2
2
3
3
2
3
3
2
3
3
3
3
3
3
2
3
2
2
2
3
3
3
2
2
3
3
3
2
3
3
2
3
3
3
4
4
3
Name
EI23RLST
EI23RRB
EI23SFLG
EI23TFLG
EI23VOL#
EI23VSER
EI24DSN
EI24FLGS
EI24RSCD
EI24RSET
EI24RTCD
EI24VOL
EI26DDN
EI26DSNL
EI26DSNP
EI26R0CE
EI26TERM
EI26TYPE
EI26VOL
EI26VSER
EI26VTRC
EI26VTRS
E22SAIX
E22SBCS
E22SDSRG
E22SESDS
E22SKRDS
E22SKSDS
E22SLDS
E22SPSSI
E22SRRDS
E22SSMSF
E22SVFLG
E22SVRRD
E22SVVDS
E23BCSEL
E23BPDS
E23BSET
E23BYTES
E23FLGS
E23SAIX
E23SBCS
E23SDSRG
E23SESDS
E23SKRDS
E23SKSDS
E23SLDS
E23SPSSI
E23SRRDS
E23SSMSF
E23SVFLG
E23SVRRD
E23SVVDS
E23TAIX
E23TBCS
E23TDSRG
E23TESDS
E23TKRDS
E23TKSDS
E23TLDS
E23TPSSI
E23TRRDS
E23TSMSF
E23TVFLG
E23TVRRD
E23TVVDS
Appendix C.
64
5E
5A
5F
8C
8D
E
3A
2
3A
0
8
C
8
4
0
0
0
0
14
1C
24
31
30
2E
30
30
30
30
30
30
2D
30
31
30
5E
7C
7C
74
7C
5E
5D
5B
5D
5D
5D
5D
5D
5D
5A
5D
5E
5D
63
62
60
62
62
62
62
62
62
5F
62
63
62
10
80
20
40
80
80
01
80
20
40
10
04
08
40
02
40
40
80
80
01
80
20
40
10
04
08
20
02
80
01
80
20
40
10
04
08
40
02
3
5
3
3
3
2
2
2
2
3
2
2
2
2
2
3
3
2
3
2
2
2
4
4
3
4
4
4
4
4
4
3
3
4
4
5
4
4
3
3
5
5
4
5
5
5
5
5
5
4
4
5
5
5
5
4
5
5
5
5
5
5
4
4
5
5
283
Example: Invoking DFSMSdss by Using an Application Program

The following example shows that a full DASD volume is to be dumped to a tape
volume or volumes. DFSMSdss is LINKed somewhere in MYJOB to perform the
dump, and, conditionally, the DEFRAG functions.
//JOB1
JOB
//STEP1
EXEC PGM=MYJOB
//STEPLIB DD
DSN=MY.LINKLIB,DISP=SHR
//SYSPRINT DD
SYSOUT=A
//DASD
DD
//TAPE
DD
UNIT=348,VOL=SER=(TAPE1,TAPE2),
//
LABEL=(1,NL),DISP=(NEW,KEEP)
//SYSIN
DD
\
DUMP INDD(DASD) OUTDD(TAPE)
IF LASTCC = THEN DEFR DDN(DASD)
/\
The preceding example does not show how the invocation of DFSMSdss was
brought about, but does show that the user program, MYJOB, was run. At some
point MYJOB needs to run DFSMSdss to perform the functions specified in the
SYSIN data set. The next example shows the code needed at that point to LINK to
DFSMSdss. Because no EXEC PARMs were specified and the standard SYSIN
and SYSPRINT data set names are to be used, there is no need to pass special
parameters.
.
.
.
LINK EP=ADRDSSU,PARAM=(OPTPTR),VL=1
.
.
.
CNOP 2,4
OPTPTR
DC
H()
Note: For additional information on the Application Interface, see Appendix D,
Examples of the Application Program with the User Interaction Module
(UIM) on page 287.
How to Determine DFSMSdss Version, Release, and Modification Level

Subsystems that invoke DFSMSdss dynamically must determine if DFSMSdss is
installed on the system, and if it is, its version, release, and modification level, and
features supported. A DFSMSdss-provided macro tries to determine the DFSMSdss
version, release, and modification level and features supported and pass the
requested information in a register.
ADRMCLVL (in SYS1.MACLIB) is an in-line executable assembler-language macro
that can be invoked by a caller. The caller can be in problem program state and
can have a user key. The caller must save registers 0, 1, 14, and 15 before
invoking the macro. No other registers are disturbed. The caller can determine the
installed level and features of DFSMSdss from the information returned in registers
1 and 14.
On return, register 1 contains information as follows:
284
If the release level of ADRDSSU cannot be determined, register 1 contains

X'04000000'.
Otherwise, register 1 contains:
Byte 0
Product number (in binary):

0 = DFDSS
2 = DFSMSdss
Byte 1
Version number (in binary):

1 = Version 1
2 = Version 2
Byte 2
Release number (in binary):

1
2
3
4
5
Byte 3
=
=
=
=
=
Release
Release
Release
Release
Release
1
2
3
4
5
Modification level (in binary)

0 = Modification level 0
On return, register 14 contains information as follow:

If the release level of ADRDSSU is less than DFSMSdss Version 1, Release 4,
Modification level 0 (see above), then the contents of register 14 are
unpredictable.
Otherwise, register 14 contains feature information as follows:
Byte 0
Feature Flags:
Bit 0, when set to 1, means DFSMSDSS cross-memory
Application Programming Interface support for concurrent copy
is available.
Bits 17 are reserved.
Bytes 13 Reserved.
Appendix C.
285
286
UIM
Appendix D. Examples of the Application Program with the

User Interaction Module (UIM)
General-use Programming Interface and Associated Guidance Information is
contained in this appendix. Product-sensitive Programming Interface is also
contained in this appendix and is explicitly marked. Figure 10 shows the process
by which DFSMSdss can call user interaction module (UIM) functions.
Application
ADRDSSU
Program
Calls
C a lls U IM
DFDSS
E x it F u n c t i o n s
Re a d S ysin E xit
W ri t e L o g ic a l Ta p e E x it
ADRXMAIA
ADR1SR03
F u n c t i o n Te r m i n a t i o n E x i t
Figure 10. The Application Program Process
This appendix contains the following examples:

The JCL to invoke an application program that invokes DFSMSdss ( Figure 11
on page 288)
A complete sample program listing showing how a user can use all of the UIM
exit functions to receive control from DFSMSdss ( Figure 12 on page 289 and
Figure 13 on page 291)
An output listing ( Figure 14 on page 304) resulting from the sample program
in Figure 12 on page 289 and Figure 13 on page 291
Note: The example shown is not written in reentrant code. If you are planning to
share a UIM between tasks, you should code the module in reentrant code.
The example has not been submitted to any formal test and is distributed as
it is, without any warranty either expressed or implied. The use of this
example or the implementation of these techniques is a customer
responsibility and depends on the customers ability to evaluate and
integrate them into the customers operational environment. Although each
item may have been reviewed by IBM for accuracy in a specific situation,
there is no guarantee that the same or similar results will be obtained
elsewhere. Customers attempting to adapt these techniques to their own
environment do so at their own risk.
287
UIM
//APIJOB
//APISTEP EXEC PGM=USRAIPGM
//STEPLIB DD
DSN=D7R.TEMPFIX.LINKLIB,DISP=SHR
//SYSPRINT DD
SYSOUT=\
//DASD
DD
UNIT=SYSDA,VOL=SER=D8F4,DISP=OLD
//TAPE
DD
UNIT=SYSDA,VOL=SER=D8H6,DISP=(NEW,CATLG),
//
SPACE=(TRK,(1,1)),DSN=PUBEXMP.TDS.DUMP
//MYDATA
DD
\
EOJ
/\
Figure 11. JCL to Invoke an Application Program That Invokes DFSMSdss
288
UIM
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\
\
\ Module Name
= USRAIPGM
\
\
\
\ Descriptive Name = DFSMSdss Application Interface Program Example \
\
\
\ Function
= Invoke DFSMSdss supplying alternate UIM: USRUIM \
\
or
\
\
= Invoke DFSMSdss Cross Memory Application
\
\
Interface UIM: USRUIM
\
\
\
\
Operation
= Place SYSIN records in the user area. The UIM \
\
will pass these records to DFSMSdss.
\
\
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
USRAIPGM CSECT
USRAIPGM AMODE 31
USRAIPGM RMODE ANY
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ Standard entry linkage
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
STM
14,12,12(13)
BALR 12,
USING \,12
LA
3,SAVEAREA
ST
3,8(13)
ST
13,4(3)
LR
13,3
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ Load and call DFSMSdss
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
LOAD EP=ADRDSSU
LR
15,
LA
3,USERAREA
ST
3,UA@
CALL (15),(OPTPTR,DDNPTR,PAGEPTR,UIMPTR,UAPTR),VL
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ Load and call DFSMSdss Cross Memory Application Interface
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\
LOAD EP=ADRXMAIA
\
LR
15,
\
LA
3,USERAREA
\
ST
3,UA@
\
CALL (15),(OPTPTR,DDNPTR,PAGEPTR,UIMPTR,UAPTR,ASNPTR),VL
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ Standard exit linkage
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
L
13,4(13)
RETURN (14,12),,RC=(15)
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ Option area (same format as EXEC parameters)
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
CNOP 2,4
OPTPTR
DC
AL2(OPTLEN)
OPTIONS DC
C'SIZE=496K,TRACE=YES'
OPTLEN
EQU
\-OPTIONS
Figure 12 (Part 1 of 2). Application Interface Program Example
Appendix D. Examples of the Application Program with the User Interaction Module (UIM)
289
UIM
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ DDNAME area (SYSIN is replaced by MYDATA)
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
CNOP 2,4
DDNPTR
DC
AL2(DDNLEN)
DDNAMES DC
XL8''
DC
XL8''
DC
XL8''
DC
XL8''
DC
CL8'MYDATA'
DC
CL8'SYSPRINT'
DDNLEN
EQU
\-DDNAMES
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ Page number area (first page will be 1)
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
CNOP 2,4
PAGEPTR DC
AL2(PAGELEN)
PAGENO
DC
CL4'1'
PAGELEN EQU
\-PAGEPTR
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ User Interaction Module area (UIM is called USRUIM)
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
CNOP 2,4
UIMPTR
DC
AL2(UIMLEN)
UIM
DC
CL8'USRUIM'
UIMLEN
EQU
\-UIM
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ User area pointer area
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
CNOP 2,4
UAPTR
DC
AL2(UALEN)
UA@
DS
A
UALEN
EQU
\-UA@
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ User area
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
USERAREA DC
AL1(COM1)
Length of first command
DC
C' WTO 'USRAIPGM INVOKING DFSMSdss'
COM1
EQU
\-USERAREA-1
SECNDCOM DC
AL1(COM2)
Length of first command
DC
C' DUMP DS(EXC(SYS1.\\)) LOGINDD(DASD) OUTDD(TAPE)'
COM2
EQU
\-SECNDCOM-1
THIRDCOM DC
AL1(COM3)
Length of third command
DC
C'
IF LASTCC= -'
COM3
EQU
\-THIRDCOM-1
FOURCOM DC
AL1(COM4)
Length of fourth command
DC
C'
THEN DEFRAG DDN(DASD)'
COM4
EQU
\-FOURCOM-1
ENDCOMM DC
X''
End of command flag
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ Register save area
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
SAVEAREA DS
18F
\
END
Figure 12 (Part 2 of 2). Application Interface Program Example
290
UIM
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\
\
\ Module Name
= USRUIM
\
\
\
\ Descriptive Name = DFSMSdss User Interaction Module Example
\
\
\
\ Function
= Perform various functions at different exit
\
\
points.
\
\
\
\
Exit Point
Operation
\
\
------------------------------------------------\
\
Initialize counters for task

\
\
1
Insert SYSIN records from user area
\
\
2
Insert table of accounting data
\
\
3
Count Tape Blocks Read
\
\
4
Count Logical Tape Blocks Read
\
\
5
Count Logical Tape Blocks Written
\
\
6
Count Tape Blocks Written
\
\
7
Count DASD Tracks Read
\
\
8
Count DASD Tracks Written
\
\
9
Nothing
\
\
1
Nothing
\
\
11
Insert a WTO message
\
\
12
Never allow ADR369D
\
\
13
Force Reblocking
\
\
14
Convert counts to printable characters
\
\
15
Nothing
\
\
16
Always bypass password protection for tape
\
\
17
Supply TAPE1 as a tape volser
\
\
18
Nothing
\
\
19
Save Tape DDNAME and volser which had error
\
\
2
Save Data Set name
\
\
21
Do not process temporary data sets
\
\
22
Bypass serialization of SYS1 data sets
\
\
23
End function if processing errors
\
\
24
End function if initialization fails
\
\
25
Nothing
\
\
26
Nothing
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\
USRUIM CSECT
USRUIM AMODE 31
USRUIM RMODE ANY
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ Registers with special uses
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\
EIDBASE EQU
2
Base reg for ADREIB.
OPTION
EQU
3
Reg to test option
WORKREG EQU
4
Work register
LENGTH
EQU
5
Reg to get length of records
TEMPBASE EQU
6
Temporary base reg for exits
RC
EQU
7
Register for return code
SYSPBASE EQU
8
Register for sysprint recs
MSGOFF
EQU
9
Register for offsets to table
Figure 13 (Part 1 of 13). User Interaction Module Example
291
UIM
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ Save Registers and Establish Addressability.
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
USING \,15
Initial Addressability
STM
14,12,12(13)
Save regs
BALR 12,
New base addressability
USING \,12
DROP 15
B
BEGIN
DC
CL16'CSECT - USRUIM'
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ Establish Addressability to EIDB
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
BEGIN
LR
15,13
Save caller SA pointer
LA
13,SAVEAREA
Set my SA pointer
ST
15,SAVEAREA+4
Backward Chain
ST
13,8(15)
Forward Chain
USING ADREIB,EIDBASE
Addressability to EIDB
L
EIDBASE,(,1)
Address of EIDB
LH
OPTION,EIOPTION
Get DFSMSdss processing option
SLL
OPTION,2
Multiply times four
LA
15,VECTABLE
Point to vector table start
L
15,(OPTION,15)
Point to processor routine
BALR 14,15
Go to processor routine
L
13,SAVEAREA+4
Restore SA pointer
RETURN (14,12)
Return to DFSMSdss
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ Processing Routines
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ AIOPT: Function Startup
\
\
Initialize counters for tape and dasd accounting.
\
\
Insert message identifying task into table
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
AIOPT XC
RTBCNT,RTBCNT
Init Tape Blocks Read
XC
WTBCNT,WTBCNT
Init Tape Blocks Written
XC
RLTBCNT,RLTBCNT
Init Log Tape Blocks Read
XC
WLTBCNT,WLTBCNT
Init Log Tape Blocks Written
XC
RDTCNT,RDTCNT
Init Disk Tracks Read
XC
WDTCNT,WDTCNT
Init Disk Tracks Written
ICM
WORKREG,15,EITSKID
Get current task identifier
CVD
WORKREG,CVDWORK
Convert to decimal
UNPK OPTTSK(2),CVDWORK+6(2) Unpack into message insert
OI
OPTTSK+1,X'F'
Make last character printable
L
MSGOFF,MSGCOUNT
Get current MSGCOUNT
MH
MSGOFF,MSGLEN
Multiply by MSGLEN to get
LA
WORKREG,MSGTABLE
offset into message table
LA
TEMPBASE,(MSGOFF,WORKREG)
USING TABLEMAP,TEMPBASE
MVC
TABENTRY(133),OPTMSG Move into msgtable
DROP TEMPBASE
L
WORKREG,MSGCOUNT
Increment MSGCOUNT
LA
WORKREG,1(WORKREG)
ST
WORKREG,MSGCOUNT
Save new count
LH
RC,EIRC
Set normal process retcode
292
UIM
STH
RC,EIRETCOD
Store retcode in EIDB
BR
14
Return to intercept processor
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ AIOPT1: Read SYSIN Record
\
\
Get SYSIN records from the user area and give them to DFSMSdss \
\
using the Insert Record return code.
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
AIOPT1 TM
SYSINFL,SYSIFRST
Q. First entry to SYSIN exit?
BO
NXTSYS
A. No, get next input
OI
SYSINFL,SYSIFRST
Indicate first time taken
ICM
TEMPBASE,15,EIUSEPTR
Get address of UA
ST
TEMPBASE,CURCOMM
Save pointer to first record
NXTSYS
L
TEMPBASE,CURCOMM
Get current command pointer
LA
WORKREG,1(,TEMPBASE)
Get past length
STCM WORKREG,15,EIRECPTR
Initialize the pointer
SR
LENGTH,LENGTH
Clear workreg
IC
LENGTH,(,TEMPBASE)
Get length of record
LTR
LENGTH,LENGTH
Q. End of SYSIN data?
BZ
SYSDEL
A. Yes, bypass SYSIN DS
STCM LENGTH,15,EIRECLEN
Set record length
LA
TEMPBASE,1(LENGTH,TEMPBASE) Point to new record
ST
TEMPBASE,CURCOMM
Save new pointer
LH
RC,EIRC8
Set insert record retcode
B
SYSEXIT
Continue setup
SYSDEL
ICM
LENGTH,15,EIRECLEN
Get current record length
LTR
LENGTH,LENGTH
Q. EOF condition ? (reclen=)
BZ
SYSRC
A. Yes, process it.
LH
RC,EIRC12
Set delete record retcode
B
SYSEXIT
Continue Setup
SYSRC LH
RC,EIRC
SYSEXIT STH
RC,EIRETCOD
BR
14
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ AIOPT2: Write SYSPRINT
\
\
Insert SYSPRINT records before message ADR12I
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
AIOPT2 ICM
SYSPBASE,15,EIRECPTR
USING SYSPMAP,SYSPBASE
CLC
MSGID(8),ADR12I
Q. Last SYSPRINT rcd?
BNE
NOTLAST
A. No, don't insert records
TM
SYSPRFL,INSDONE
Q. Are we done inserting?
BO
NOTLAST
A. Yes, don't insert records
L
WORKREG,INSERTCT
LR
MSGOFF,WORKREG
Save INSERTCT for offset
LA
WORKREG,1(WORKREG)
Increment INSERTCT and
C
WORKREG,MSGCOUNT
Q. Have we printed all rcds?
BNH
INSERT
A. No, insert another record
OI
SYSPRFL,INSDONE
Indicate we are done insert
LA
WORKREG,TRAILER
Point to trailer record
Store into EIRECPTR
LH
WORKREG,MSGLEN
Update EIRECLEN
STCM WORKREG,15,EIRECLEN
LH
RC,EIRC8
B
SYSPEXIT
293
UIM
INSERT
MH
MSGOFF,MSGLEN
LA
WORKREG,MSGTABLE
LA
WORKREG,(MSGOFF,WORKREG)
Store address in EIRECPTR
LH
WORKREG,MSGLEN
Store length in EIRECLEN
L
WORKREG,INSERTCT
Increment MSGCOUNT
LA
WORKREG,1(WORKREG)
ST
WORKREG,INSERTCT
Save new count
LH
RC,EIRC8
B
SYSPEXIT
NOTLAST LH
RC,EIRC
SYSPEXIT STH
RC,EIRETCOD
BR
14
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ AIOPT3: Read Tape Block Exit
\
\
Count Tape Block records read
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
AIOPT3 LH
WORKREG,RTBCNT
Increment Read Tape Block
LA
WORKREG,1(WORKREG)
count
STH
WORKREG,RTBCNT
LH
RC,EIRC
STH
RC,EIRETCOD
BR
14
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ AIOPT4: Read Logical Tape Block Exit
\
\
Count Logical Tape Block records read
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
AIOPT4 LH
WORKREG,RLTBCNT
Increment Read logical Tape
LA
WORKREG,1(WORKREG)
Block count
STH
WORKREG,RLTBCNT
LH
RC,EIRC
STH
RC,EIRETCOD
BR
14
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ AIOPT5: Write Logical Tape Block Exit
\
\
Count Logical Tape Block records written
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
AIOPT5 LH
WORKREG,WLTBCNT
Increment Write logical Tape
LA
WORKREG,1(WORKREG)
Block count
STH
WORKREG,WLTBCNT
LH
RC,EIRC
STH
RC,EIRETCOD
BR
14
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ AIOPT6: Write Tape Block Exit
\
\
Count Tape Block records written
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
AIOPT6 LH
WORKREG,WTBCNT
Increment Write Logical
LA
WORKREG,1(WORKREG)
Tape Block count
STH
WORKREG,WTBCNT
LH
RC,EIRC
STH
RC,EIRETCOD
BR
14
\
294
UIM
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ AIOPT7: Read DASD Track Exit
\
\
Count DASD Tracks read
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
AIOPT7 LH
WORKREG,RDTCNT
Increment Read DASD Track
LA
WORKREG,1(WORKREG)
count
STH
WORKREG,RDTCNT
LH
RC,EIRC
STH
RC,EIRETCOD
BR
14
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ AIOPT8: Write DASD Track Exit
\
\
Count DASD Tracks written
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
AIOPT8 LH
WORKREG,WDTCNT
Increment Write DASD Track
LA
WORKREG,1(WORKREG)
count
STH
WORKREG,WDTCNT
LH
RC,EIRC
STH
RC,EIRETCOD
BR
14
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ AIOPT9: Read Utility SYSPRINT
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
AIOPT9 LH
RC,EIRC
STH
RC,EIRETCOD
BR
14
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ AIOPT1: Write SYSPRINT Record
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
AIOPT1 LH
RC,EIRC
STH
RC,EIRETCOD
BR
14
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ AIOPT11: Write WTO Message
\
\
Delete the WTO and insert my own
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
AIOPT11 LH
WORKREG,WTOCT
Check WTO count
LTR
WORKREG,WORKREG
Q. Is WTOCT ?
BZ
OPT11INS
A. Yes, insert one
OPT11DEL LH
RC,EIRC12
Set delete record retcode
B
OPT11XIT
(delete all other WTOs)
OPT11INS LA
WORKREG,1(WORKREG)
Increment WTOCT
STH
WORKREG,WTOCT
LA
WORKREG,UIMWTO
Get address of WTO
Store it in EIRECPTR
LA
WORKREG,WTOLEN
Get length of WTO
Store length it in EIRECLEN
LH
RC,EIRC8
B
OPT11XIT
OPT11XIT STH
RC,EIRETCOD
BR
14
295
UIM
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ AIOPT12: Write WTOR Message
\
\
Check for ADR369D, never allow it to write over VTOC, etc
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
AIOPT12 ICM
WORKREG,15,EIRECPTR
CLC
12(8,WORKREG),ADR369D
Q. Authorize request?
BNE
OPT12RC
A. No, let DFSMSdss do WTOR
LA
WORKREG,UIMRESP
Get address of response
Store in EIRECPTR
LA
WORKREG,RESPLEN
Get length of response
Store in EIRECLEN
LH
RC,EIRC28
Set WTOR Response retcode
B
OPT12XIT
OPT12RC LH
RC,EIRC
OPT12XIT STH
RC,EIRETCOD
BR
14
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ AIOPT13: Present ADRUFO Record
\
\
If parm call, set IO and AI buffers above 16M
\
\
If function call and Copy, force reblocking.
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
AIOPT13 ICM
TEMPBASE,15,EIRECPTR
USING ADRUFOB,TEMPBASE
Get addressability to UFO
CLC
UFFUNCT,PARM
Q. Is this a PARM call?
BE
PARMCALL
A. Yes, go to parm call
FUNCTION TM
UFFUNCT1,UFFUCOPY
Is this a copy?
BNO
OPT13RC
No, don't change options
SR
WORKREG,WORKREG
ICM
WORKREG,3,UFBDYOFF
Get offset for PARM list
AR
WORKREG,TEMPBASE
Add to address of UFO
USING UFOFUNCT,WORKREG
Establish addressability
OI
UFO3FLGS,UFOFRBLK
Force reblocking
DROP WORKREG
LH
RC,EIRC16
Set modify record retcode
B
OPT13XIT
PARMCALL SR
WORKREG,WORKREG
This is a parm call.
ICM
WORKREG,3,UFBDYOFF
Get offset for PARM list
AR
WORKREG,TEMPBASE
Add to address of UFO
USING UFOFUNCT,WORKREG
Establish addressability
OI
UFXAFLAG,UFXABUFF
Make sure IO buffers are >16M
OI
UFXAFLAG,UFAI31B
Make sure AI buffers are >16M
DROP WORKREG
LH
RC,EIRC16
LA
WORKREG,2
Initialize message table:
ST
WORKREG,MSGCOUNT
Initialize msgcount
DROP TEMPBASE
LA
TEMPBASE,MSGTABLE
Get address of table
MVC
TABENTRY(133),HEADER
Move header into msgtable
LA
TEMPBASE,133(TEMPBASE) Move past first message
296
UIM
MVC
TABENTRY(133),BLANKS
Move blank line into table
DROP TEMPBASE
B
OPT13XIT
Exit.
OPT13RC LH
RC,EIRC
OPT13XIT EQU
\
STH
RC,EIRETCOD
BR
14
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ AIOPT14: Function Ending
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
AIOPT14 LH
WORKREG,RTBCNT
Get Tape Blocks Read
CVD
WORKREG,CVDWORK
Convert to decimal
UNPK RTBINS,CVDWORK
Unpack into message insert
OI
RTBINS+7,X'F'
LH
WORKREG,WTBCNT
Get Tape Blocks Written
CVD
WORKREG,CVDWORK
Convert to decimal
UNPK WTBINS,CVDWORK
OI
WTBINS+7,X'F'
LH
WORKREG,RLTBCNT
Get Tape Logical Blocks Read
CVD
WORKREG,CVDWORK
Convert to decimal
UNPK RLTBINS,CVDWORK
OI
RLTBINS+7,X'F'
LH
WORKREG,WLTBCNT
Get Tape Log Blocks Written
CVD
WORKREG,CVDWORK
Convert to decimal
UNPK WLTBINS,CVDWORK
OI
WLTBINS+7,X'F'
LH
WORKREG,RDTCNT
Get Disk Tracks Read
CVD
WORKREG,CVDWORK
Convert to decimal
UNPK RDTINS,CVDWORK
OI
RDTINS+7,X'F'
LH
WORKREG,WDTCNT
Get Disk Tracks Written
CVD
WORKREG,CVDWORK
Convert to decimal
UNPK WDTINS,CVDWORK
OI
WDTINS+7,X'F'
L
MSGOFF,MSGCOUNT
MH
MSGOFF,MSGLEN
LA
WORKREG,MSGTABLE
LA
MVC
TABENTRY(133),READMSG
Move into msgtable
LA
TEMPBASE,133(TEMPBASE) Increment pointer for 2nd msg
MVC
TABENTRY(133),WRITEMSG Move into msgtable
DROP TEMPBASE
L
WORKREG,MSGCOUNT
Increment MSGCOUNT
LA
WORKREG,2(WORKREG)
ST
WORKREG,MSGCOUNT
Save new count
LH
RC,EIRC
STH
RC,EIRETCOD
BR
14
297
UIM
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ AIOPT15: Present WTOR Response
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
AIOPT15 LH
RC,EIRC
STH
RC,EIRETCOD
BR
14
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ AIOPT16: OPEN/EOF Tape Security and Verification
\
\
Always bypass password protection
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
AIOPT16 ICM
Get address of record
LH
RC,EIRC16
Bypass password protection
ST
RC,(TEMPBASE)
Store in EIRECPTR
LH
RC,EIRC16
STH
RC,EIRETCOD
BR
14
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ AIOPT17: OPEN/EOF Nonspecific Tape Mount
\
\
Supply DFSMSdss with TAPE1
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
AIOPT17 ICM
Get address of record
MVC
(6,TEMPBASE),TAPE1
Supply TAPE1 as volser
LH
RC,EIRC16
STH
RC,EIRETCOD
BR
14
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ AIOPT18: Insert logical VSAM Record during Logical Restore
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
AIOPT18 LH
RC,EIRC
STH
RC,EIRETCOD
BR
14
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ AIOPT19: Output Tape I/O Error
\
\
Save DDNAME, Volser, and Return code, print record.
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
AIOPT19 ICM
Get address of EIRECORD
USING EIDDINFO,TEMPBASE
Est addressability to DDINFO
MVC
OPT19DD,EIDDNAME
Move DDNAME to message
MVC
OPT19VS,EIVOLID
Move VOLSER to message
SR
WORKREG,WORKREG
Clear out work register
IC
WORKREG,EIRETC
Get return code
CVD
WORKREG,CVDWORK
Convert to decimal
UNPK OPT19RC(2),CVDWORK+6(2) Unpack into message insert
OI
OPT19RC+1,X'F'
DROP TEMPBASE
L
MSGOFF,MSGCOUNT
MH
MSGOFF,MSGLEN
LA
WORKREG,MSGTABLE
LA
MVC
TABENTRY(133),OPT19MSG Move into msgtable
DROP TEMPBASE
298
UIM
L
WORKREG,MSGCOUNT
Increment MSGCOUNT
LA
WORKREG,1(WORKREG)
ST
WORKREG,MSGCOUNT
Save new count
LH
RC,EIRC
STH
RC,EIRETCOD
BR
14
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ AIOPT2: Volume Information Exit
\
\
Save Data Set name
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
AIOPT2 ICM
Establish addressability to
USING EIREC2,TEMPBASE
EIREC2
MVC
OPT2DSN(44),EI2DSN
Move data set name into msg
DROP TEMPBASE
L
MSGOFF,MSGCOUNT
MH
MSGOFF,MSGLEN
LA
WORKREG,MSGTABLE
LA
MVC
TABENTRY(133),OPT2MSG Move into msgtable
DROP TEMPBASE
L
WORKREG,MSGCOUNT
Increment MSGCOUNT
LA
WORKREG,1(WORKREG)
ST
WORKREG,MSGCOUNT
Save new count
LH
RC,EIRC
STH
RC,EIRETCOD
BR
14
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ AIOPT21: Data Set Verification Exit
\
\
Do Not Process TEMP Data Sets
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
AIOPT21 EQU
\
ICM
Get record pointer
Get addressability
CLC
EI21DSN(4),TMPL
If first 4 char of dsn='TEMP'
DROP
TEMPBASE
Release addressability
BNE
LABEL1
Then
LH
RC,EIRC36
Do not process data set
B
LABEL2
Else
LABEL1
LH
RC,EIRC
Set normal return code
LABEL2
STH
RC,EIRETCOD
BR
14
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ AIOPT22: Bypass Verification Exit
\
\
Bypass Serialization of SYS1 Data Sets
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
AIOPT22 EQU
\
ICM
Get record pointer
Get addressability
CLC
EI22DSN(4),SYSL
If first 4 char of dsn='SYS1'
BNE
LAB1
Then
LH
RC,EIRC16
Bypass serialization of dsn
NI
EI22FLGS,B'1111111'
Set EI22BSER bit on
B
LAB2
Else
DROP
TEMPBASE
299
UIM
LAB1
LAB2
LH
RC,EIRC
STH
RC,EIRETCOD
BR
14
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ AIOPT23: Data Set Processed Notification Exit
\
\
End Function If Errors in Processing
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
AIOPT23 EQU
\
ICM
Get record pointer
Get addressability
LH
WORKREG,EI23DSRC
If data set processing RC=
DROP TEMPBASE
LTR
WORKREG,WORKREG
Then
BZ
LABL1
LH
RC,EIRC32
End function
B
LABL2
Else
LABL1
LH
RC,EIRC
LABL2
STH
RC,EIRETCOD
BR
14
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ AIOPT24: Concurrent Copy initialization complete
\
\
End function if initialization is not successful
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
AIOPT24 EQU
\
Start EIOP24 processing
LH
RC,EIRC
Assume goodness
ICM
Get record pointer
Get addressability
LH
WORKREG,EI24RTCD
Get the return code
DROP TEMPBASE
LTR
WORKREG,WORKREG
If zero
BZ
OPT24END
End function
LH
RC,EIRC32
Else end the function
OPT24END STH
RC,EIRETCOD
BR
14
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ AIOPT25: Backspace tape input
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
AIOPT25 EQU
\
LH
RC,EIRC
STH
RC,EIRETCOD
BR
14
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ AIOPT26: Volume open for output
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
AIOPT26 EQU
\
LH
RC,EIRC
STH
RC,EIRETCOD
BR
14
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ Start of local variables
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
300
UIM
\
CURCOMM
SYSINFL
SYSIFRST
SYSPRFL
INSDONE
TMPL
SYSL
\
SAVEAREA
\
VECTABLE
VEC1
VEC2
VEC3
VEC4
VEC5
VEC6
VEC7
VEC8
VEC9
VEC1
VEC11
VEC12
VEC13
VEC14
VEC15
VEC16
VEC17
VEC18
VEC19
VEC2
VEC21
VEC22
VEC23
VEC24
VEC25
VEC26
\
UIMWTO
WTOLEN
\
UIMRESP
RESPLEN
\
ADR369D
ADR12I
\
MSGLEN
INSERTCT
MSGCOUNT
\
DC
DC
EQU
DC
EQU
DC
DC
F''
X''
X'8'
X''
X'8'
C'TEMP'
C'SYS1'
Address of current command

SYSIN Flag
First entry SYSIN Performed
SYSPRINT Flag
Done inserting SYSPRINT recs
TEMP high-level qualifier
SYS1 high-level qualifier
DC
18F''
My save area
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
A(AIOPT)
A(AIOPT1)
A(AIOPT2)
A(AIOPT3)
A(AIOPT4)
A(AIOPT5)
A(AIOPT6)
A(AIOPT7)
A(AIOPT8)
A(AIOPT9)
A(AIOPT1)
A(AIOPT11)
A(AIOPT12)
A(AIOPT13)
A(AIOPT14)
A(AIOPT15)
A(AIOPT16)
A(AIOPT17)
A(AIOPT18)
A(AIOPT19)
A(AIOPT2)
A(AIOPT21)
A(AIOPT22)
A(AIOPT23)
A(AIOPT24)
A(AIOPT25)
A(AIOPT26)
Function Startup Exit

Read SYSIN Exit
Write SYSPRINT Exit
Read Tape Block Exit
Read Logical Tape Exit
Write Logical Tape Exit
Write Tape Block Exit
Read DASD Track Exit
Write DASD Track Exit
Read Utility Sysprint Exit
Write SYSPRINT Record
Write WTO Message Exit
Write WTOR Message Exit
Present ADRUFO Record Exit
Function Ending Exit
Present WTOR Response
OPEN/EOF Tape Sec/Ver Exit
OPEN/EOF NonSpec Tape Mount
Insert log VSAM Rcd -Restore
Output Tape I/O Error Exit
Volume Information Exit
Data Set Verification Exit
Bypass Verification Exit
Data Set Processed Exit
Concurrent Copy Init Complete
Backspace tape input
Volume open for output
DC
EQU
C'>>>
USRUIM is active
<<<'
\-UIMWTO
Show that we are active
DC
EQU
C'T'
\-UIMRESP
Reply T to ADR369
DC
DC
CL8'ADR369D'
CL8'ADR12I'
DFSMSdss Authorization WTOR

Last DFSMSdss message id
DC
DC
DC
H'133'
F''
F''
Length of messages
Count of msgs given to DFSMSdss
Count of messages in table
301
UIM
RTBCNT
WTBCNT
\
RLTBCNT
WLTBCNT
\
RDTCNT
WDTCNT
\
WTOCT
\
PARM
\
TAPE1
\
\
HEADER
\
TRAILER
\
BLANKS
\
READMSG
RDTINS
RTBINS
RLTBINS
DC
DC
H''
H''
Count of Tape Blocks Read

Count of Tape Blocks Written
DC
DC
H''
H''
Count Log Tape Blocks Read

Count Log Tape Blocks Written
DC
DC
H''
H''
Count Disk Tracks Read

Count Disk Tracks Written
DC
H''
Count of WTOs
DC
X''
Parm call test for Opt 13
DC
CL6'TAPE1'
Tape volser for Opt 17
DC
DC
C' \\\\\\\\\\\\\\\\\\\\\\\ Begin USRUIM Messages '

CL(133-(\-HEADER))'\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\C
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\'
DC
DC
C' \\\\\\\\\\\\\\\\\\\\\\\ End

USRUIM Messages '
CL(133-(\-TRAILER))'\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\C
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\'
DC
CL133' '
DC
DC
DC
DC
DC
DC
DC
C'
Disk Tracks Read:
'
C'XXXXXXXX'
C'
Tape Blocks Read:
'
C'XXXXXXXX'
C'
Logical Tape Blocks Read:
C'XXXXXXXX'
CL(133-(\-READMSG))' '
\
WRITEMSG DC
WDTINS
DC
DC
WTBINS
DC
DC
WLTBINS DC
DC
\
OPTMSG DC
OPTTSK DC
DC
\
OPT19MSG DC
OPT19DD DC
DC
OPT19VS DC
DC
Blank message
'
C'
Disk Tracks Written: '
C'XXXXXXXX'
C'
Tape Blocks Written: '
C'XXXXXXXX'
C'
Logical Tape Blocks Written: '
C'XXXXXXXX'
CL(133-(\-WRITEMSG))' '
C'
Messages follow for task: '
C'XX'
CL(133-(\-OPTMSG))' '
C'
Permanent Tape Error for DDNAME: '
C'XXXXXXXX'
C' VOLSER: '
C'XXXXXX'
C' Return Code: '
302
UIM
OPT19RC
DC
DC
C'XX'
CL(133-(\-OPT19MSG))' '
\
OPT2MSG DC
C'
EI2DSN = '
OPT2DSN DC
C'XXXXXXXX.XXXXXXXX.XXXXXXXX.XXXXXXXX.XXXXXXXX'
DC
C'
DC
CL(133-(\-OPT2MSG))' '
\
CVDWORK DS
D
Workarea for decimal conversion
\
ADREID
Macro to map EIDB
\
ADRUFO
Macro to map UFO
\
USRUIM
CSECT
MSGTABLE DS
CL133
Room in table for 1 msgs
\
TABLEMAP DSECT
DSECT to insert msgs into table
TABENTRY DS
CL133
\
SYSPMAP DSECT
DSECT to find MSGID in DFSMSdss
DS
CL1
messages
MSGID
DS
CL7
\
END
303
UIM
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
PAGE 1
5695-DF175 DFSMSDSS V1R5. DATA SET SERVICES
1998.293 15:28
ADR1I (SCH)-PRIME(1), SIZE VALUE OF 496K WILL BE USED FOR GETMAIN
WTO 'USRAIPGM INVOKING DFSMSdss'
ADR11I (R/I)-RI1 (1), TASKID 1 HAS BEEN ASSIGNED TO COMMAND 'WTO '
DUMP DS(EXC(SYS1.\\)) LOGINDD(DASD) OUTDD(TAPE)
ADR11I (R/I)-RI1 (1), TASKID 2 HAS BEEN ASSIGNED TO COMMAND 'DUMP '
IF LASTCC= ADR11I (R/I)-RI1 (1), TASKID 3 HAS BEEN ASSIGNED TO COMMAND 'IF '
THEN DEFRAG DDN(DASD)
ADR11I (R/I)-RI1 (1), TASKID 4 HAS BEEN ASSIGNED TO COMMAND 'DEFRAG '
ADR19I (R/I)-RI1 (1), 1998.293 15:28:52 INITIAL SCAN OF USER CONTROL STATEMENTS COMPLETED.
ADR5I (2)-PRIME(1), DFSMSDSS INVOKED VIA APPLICATION INTERFACE
ADR788I (2)-DIVSM(3), PROCESSING COMPLETED FOR CLUSTER PUBSEXMP.KSDS.S1, 1 RECORD(S) PROCESSED, REASON
ADR81I (2)-DTDSC(1), DATA SET FILTERING IS COMPLETE. 4 OF 4 DATA SETS WERE SELECTED: FAILED SERIALIZATION AND FAILED FOR
OTHER REASONS.
ADR454I (2)-DTDSC(1), THE FOLLOWING DATA SETS WERE SUCCESSFULLY PROCESSED
PUBSEXMP.SAM.S1
PUBSEXMP.PDS.S1
CLUSTER NAME
PUBSEXMP.ESDS.S1
CATALOG NAME
SYS1.MVSRES.MASTCAT
COMPONENT NAME PUBSEXMP.ESDS.S1.DATA
CLUSTER NAME
PUBSEXMP.KSDS.S1
CATALOG NAME
SYS1.MVSRES.MASTCAT
COMPONENT NAME PUBSEXMP.KSDS.S1.DATA
COMPONENT NAME PUBSEXMP.KSDS.S1.INDEX
ADR6I (2)-STEND(2), 1998.293 15:28:54 EXECUTION ENDS
ADR13I (2)-CLTSK(1), 1998.293 15:28:54 TASK COMPLETED WITH RETURN CODE
ADR5I (4)-PRIME(1), DFSMSDSS INVOKED VIA APPLICATION INTERFACE
ADR28I (4)-EANAL(1), 1998.293 15:28:54 BEGINNING STATISTICS ON D9S6:
FREE CYLINDERS
58
FREE TRACKS
3
FREE EXTENTS
2
Figure 14 (Part 1 of 2). Output Resulting from Use of the UIM Exits
304
UIM
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
PAGE 2
|
|
|
|
|
|
|
|
|
Messages follow for task:

Messages follow for task: 2
Disk Tracks Read:
14
Tape Blocks Read:
Disk Tracks Written:

Tape Blocks Written: 39
Logical Tape Blocks Written: 12
Messages follow for task: 4
Disk Tracks Read:
52
Tape Blocks Read:
Disk Tracks Written: 12

Tape Blocks Written:
Logical Tape Blocks Written:
\\\\\\\\\\\\\\\\\\\\\\\ End
USRUIM Messages \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
ADR12I (SCH)-DSSU (1), 1998.293 15:28:55 DFSMSDSS PROCESSING COMPLETE. HIGHEST RETURN CODE IS
5695-DF175
PAGE 3
5695-DF175
ADR6I (4)-STEND(2),
ADR13I (4)-CLTSK(1),
\\\\\\\\\\\\\\\\\\\\\\\

1998.293 15:28
FRAGMENTATION INDEX
.5
PERCENT FREE SPACE
97
INTERVAL BEGINS AT CC:HH 1: AND ENDS AT CC:HH 6:C
1998.293 15:28:55 MOVED EXTENT 1 FROM 6:-6:4 TO 1:-1:4 FOR
PUBSEXMP.ESDS.S1.DATA
1998.293 15:28:55 MOVED EXTENT 1 FROM 6:5-6:6 TO 1:5-1:6 FOR
PUBSEXMP.KSDS.S1.DATA
1998.293 15:28:55 MOVED EXTENT 1 FROM 6:7-6:8 TO 1:7-1:8 FOR
PUBSEXMP.SAM.S1
1998.293 15:28:55 MOVED EXTENT 1 FROM 6:9-6:A TO 1:9-1:A FOR
PUBSEXMP.PDS.S1
1998.293 15:28:55 MOVED EXTENT 2 FROM 6:B-6:B TO 1:B-1:B FOR
PUBSEXMP.PDS.S1
1998.293 15:28:55 ENDING STATISTICS ON D9S6:
DATA SET EXTENTS RELOCATED
5
TRACKS RELOCATED
12
FREE CYLINDERS
58
FREE TRACKS
3
FREE EXTENTS
1
FRAGMENTATION INDEX
.
1998.293 15:28
EXTENT DISTRIBUTION MAP FOR D9S6:
EXTENT
\FREE SPACE BEFORE\ \FREE SPACE AFTER\
\ ALLOCATED \
SIZE
IN
NO.
CUM.
NO.
CUM.
NO.
CUM.
TRACKS
EXTS PCT/1
EXTS PCT/1
EXTS PCT/1
1
4
.148
2
4
.444
5
1
.629
1
1
1.
75
1
.85
>499
1
1.
1
1.
1998.293 15:28:55 EXECUTION ENDS
1998.293 15:28:55 TASK COMPLETED WITH RETURN CODE
Begin USRUIM Messages \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Figure 14 (Part 2 of 2). Output Resulting from Use of the UIM Exits
305
UIM
306
Data Set Attributes

This section lists various attributes that DFSMSdss can set or change for a given
data set, and identifies where DFSMSdss gets the attribute information from.
Locate the data set attribute of interest in the first column of Table 22. The
remaining columns indicate where and under which conditions DFSMSdss finds the
attribute information. For example, the data set size is usually determined by the
source data set, unless the preallocated target data set is larger. The ALLDATA(x)
and ALLEXCP keywords have an effect on the data set size.
Table 22 (Page 1 of 3). Data Set Attributes and How They Are Determined.
Is the Attribute Determined by...
Attribute
the Source Data

Set?
the PreAllocated
Target?
a Keyword?
another Factor?
Data set
name
Yes, if no
RENAME or
RENAMEU
No
RENAME or
RENAMEU
No
Yes, unless the

preallocated
target data set is
larger
Yes, if it is
big enough
ALLDATA(x) or
ALLEXCP
No
Data set
size
Yes
Yes, if not SMS,

OUTDDNAME(x,...)
or OUTDYNAM(x,...)
Volumes
Yes, if doing a
RESTORE and
no output
volumes were
specified, no
target exists, and
not
SMS-managed
If SMS-managed, ACS routines

and SMS allocation choose
volumes with most available
space. If not SMS-managed,
DFSMSdss chooses volumes
with most available space.
Yes, if no target
and either
ABSTR, ISAM,
PSU, POU, or
DAU
Yes
Data set
location on
volume
FORCE can override

ABSTR, ISAM, PSU,
POU, and DAU
DFSMSdss locates wherever

space is available; DEFRAG
may move extents
PDS
directory
size
(blocks)
Yes
No
No
No
PDSE
directory
size
(blocks)
Yes
No
No
No
SMS
Storage
Class or
Management
Class
Yes, if no target
and BYPASSACS
is specified
Yes
Yes, if STORCLAS(x)
or MGMTCLAS(x), or
both, are specified
with BYPASSACS
ACS routines if no target and

BYPASSACS is not specified
SMS Data
Class
Yes, if no target
Yes
No
No
307
Data Set Attributes
Attribute
the Source Data

Set?
the PreAllocated
Target?
a Keyword?
another Factor?
Yes, if REBLOCK
is not specified
and data set is
not system
reblockable
No
If REBLOCK keyword
is specified,
DFSMSdss chooses
a new optimal
blocksize
If system reblockable,
DFSMSdss chooses a new
optimal blocksize, or else the
user can change blocksize with
the installation reblock exit and
can specify REBLOCK with the
LRECL
Yes
No
No
No
RECFM
Yes
No
No
No
DSORG
Yes
No
No
No
Yes
Number of
volumes
Yes, if no target,
source is single
volume, and
MAKEMULTI is
not specified
MAKEMULTI can
make a single
volume source into a
multivolume target
DFSMSdss always tries to

consolidate
Yes
No
Number of
extents
Yes, for
imbedded
extended KSDSs
during physical
data set restore
DFSMSdss always tries to

consolidate during
COPY/RESTORE. RELEASE
may reduce the number of
extents.
Yes, if no target
or if doing a
RESTORE
Yes, if doing
a COPY
CONVERT(PDS(x))
or
CONVERT(PDSE(x))
No
Yes
Cataloged
Yes, if
RECATALOG(*)
is specified, no
target, and the
user is not doing
a physical data
set restore
RECATALOG(x),
CATALOG,
UNCATALOG
(applies to source
only)
If SMS or VSAM, cataloged by

default. If physical data set
restore, only single volume
non-VSAM is cataloged (if
CATALOG is specified).
Yes
TGTALLOC(x)
No
Allocation
unit
Yes, if no target
and TGTALLOC
(SOURCE)
specified or
defaulted
Yes, if doing
VSAM I/O
and uses
values in
target
catalog
entry
VALIDATE,
NOVALIDATE,
FREESPACE
No
Free space
in VSAM
Yes, if going to
like device,
nonVALIDATE,
no dummy blocks,
and CI and CA
sizes do not
change
BLKSZ
PDS/PDSE
308
Data Set Attributes
Attribute
the Source Data

Set?
the PreAllocated
Target?
a Keyword?
another Factor?
Yes
MENTITY,
MVOLSER
Full RACF profile information

(access lists) are not preserved
Security
(RACF)
If no target and
source was
generic or
discrete, and no
applicable profile
protecting new
target, a new
discrete will be
defined
No
SPHERE
No
AIX data
sets on
VSAM
clusters
If SPHERE is
specified during
COPY or DUMP
and RESTORE,
sphere and
connections are
preserved
Yes, if no target
and TGTGDS
(source) specified
Yes
TGTGDS(x)
No
GDS state
Yes, if no
preallocated
target and no UIM
input
Yes, if no
UIM input
No
RLS BWO
field
UIM can pass a value in Exit 22

during logical RESTORE
Yes, if not a
logical restore
No
No
For logical restore, if dumped

using RLS access, timestamps
reflect the time of the dump.
Otherwise the timestamps are
zero.
Yes, if no UIM
input
No
No

Yes, if no
preallocated
target and no UIM
input
Yes, if no
UIM input
No
RLS log
parameter

Yes, if no
preallocated
target and no UIM
input
Yes, if no
UIM input
No
RLS log
stream ID

RLS
timestamps
RLS
recovery
required
309
Data Set Attributes
310
Customizing ISMF
Appendix F. Customizing ISMF

There may be times when you wish to customize ISMF. This section lists the
libraries you can customize and some restrictions. DFSMS/MVS Using ISMF
describes ISMF restrictions and customization with DFSMSdss in detail.
ISMF Libraries That Can Be Customized

You can customize the following libraries of ISMF:
Panel Library
ISMF allows you to make the following changes:
Change the initial priming values that ISMF ships

Change the default values for data entry panels
Provide additional restrictions to values entered for certain fields on panels
Remove fields from functional panels
Change highlighting and color
Change the format of the panel
Modify existing functional panel text and help text
Add new fields to panels
Add new panels.
Message Library
You can modify existing messages and add new messages.
Skeleton Library
You can modify the job skeletons for ISMF commands and line operators.
Table Library
You can modify the ISPF command tables.
Load Library
You can modify the ISMF command and line operator tables. The tables are
contained in nonexecutable CSECTs in the load library.
CLIST Library
You can modify the options on the CLIST CONTROL statement.
Restrictions to Customizing ISMF

The following are some general restrictions to customizing ISMF:
1. Before you change anything, you should make a backup copy of ISMF. Keep
this unmodified version of the product for diagnostic purposes. IBM support and
maintenance is provided for only the unmodified version of ISMF.
2. Do not delete or rename any of the parts of ISMF. Deleting or renaming a part
can severely affect processing or cause ISMF to fail.
3. ISMF is copyrighted. Under the IBM licensing agreement you may modify ISMF
for your own use. You may not modify it for commercial resale.
311
Customizing ISMF
312
Glossary
This glossary includes definitions of some terms found
in this document. If you do not find the term you are
looking for, see IBM Dictionary of Computing, New
York: McGraw-Hill, 1994.
ACS. Automatic class selection.
This glossary includes terms and definitions from:
ALLOC. A space allocation parameter that indicates

type, such as cylinders or tracks.
The American National Standard Dictionary for

Information Systems, ANSI X3.172-1990, copyright
1990 by the American National Standards Institute
(ANSI). Copies may be purchased from the
American National Standards Institute, 11 West
42nd Street, New York, New York 10036.
The Information Technology Vocabulary, developed
by Subcommittee 1, Joint Technical Committee 1, of
the International Organization for Standardization
and the International Electrotechnical Commission
(ISO/IEC JTC1/SC1).
A
ABEND. Abnormal end of task. End of a task, a job, or
a subsystem because of an error condition that cannot
be resolved by recovery facilities while the task is
performed.
ABENDxxx. The keyword that identifies the abnormal
end of DFSMSdss because of a system-detected error.
ABSTR. A subparameter of the SPACE parameter in a
DD statement. It indicates that specified tracks be
assigned to a data set.
ACCEPT processing. An SMP/E process necessary
for installing the FMIDs. SMP/E ACCEPT processing
uses JCL to accept the modules and macros necessary
to run the FMIDs. The FMIDs are accepted into the
DLIBs from the temporary data sets.
access method services. A multifunction service
program that is used to manage both VSAM and
non-VSAM data sets and integrated catalog facility or
VSAM catalogs. It is used to define data sets and
allocate space for them; convert indexed-sequential
data sets to key-sequenced data sets; modify data set
attributes in the catalog; reorganize data sets; facilitate
data portability between operating systems; create
backup copies of data sets, data set records, and
catalog entries; help make inaccessible data sets
accessible; list the records of data sets and catalogs;
define and build alternate indexes; and convert OS
CVOLs and VSAM catalogs to integrated catalog facility
catalogs.
alias. An alternate name for a member of a partitioned

data set.
alternate index. In systems with VSAM, a

key-sequenced data set containing index entries
organized by the alternate keys of its associated base
data records. It provides an alternate means of locating
records in the data component of a cluster on which the
alternate index is based.
alternate index cluster. In VSAM, the data and index
components of an alternate index.
APAR. authorized program analysis report
APF. Authorized program facility.
application interface. An interface used to invoke
DFSMSdss from another program.
apply processing. In SMP and SMP/E, the process,
initiated by the APPLY command, that places system
modifications (SYSMODS) into the target system
libraries.
attach. In programming, to create a task that can be
performed asynchronously with the performance of the
mainline code.
authorization. (1) The right granted to a user to
communicate with or make use of a computer system.
(2) The process of giving a user either complete or
restricted access to an object, resource, or function.
authorized program analysis report (APAR). A
request for correction of a problem caused by a
suspected defect in a current unaltered release of a
program.
automatic class selection (ACS). A mechanism for
assigning SMS classes and storage groups.
B
backup. The process of creating a copy of a data set
to ensure against accidental loss.
backup while open. DFSMSdss can perform backup
of data sets that are open for update for a long period
of time (like CICS). DFSMSdss can perform a logical
ACDS. Active control data set.

313
data set dump of these data sets even if another

application has them serialized.
base cluster. In systems with VSAM, a
key-sequenced or entry-sequenced data set over which
one or more alternate indexes are built.
which a one represents a punch and a zero represents

the absence of a punch.
|
|
|
|
basic catalog structure (BCS). The name of the

catalog structure in the integrated catalog facility
environment. An integrated catalog facility catalog
consists of a BCS and its related VSAM volume data
sets (VVDSs).
CC-compatible snapshot. An operation that uses

snapshot to provide a concurrent copy-like function
when the source volume supports snapshot, but not
concurrent copy.
CCHHR. Cylinder, cylinder, head, head, record.
CCW. Channel command word.
CDE. Contents directory entry.
basic direct access method (BDAM). An access

method used to directly retrieve or update particular
blocks of a data set on a direct access device.
CDS. Control data set.

channel command word (CCW). A doubleword at the
location in main storage specified by the channel
address word. One or more CCWs make up the
channel program that directs data channel operations.
basic partitioned access method (BPAM). An

access method that can be applied to create program
libraries in direct access storage for convenient storage
and retrieval of programs.
CI. Control interval.
basic sequential access method (BSAM). An access

method for storing or retrieving data blocks in a
continuous sequence, using either a sequential access
or a direct access device.
CLIST. Command list.

component identification keyword. The first
keyword, represented as a number, in a set of
keywords used to describe a DFSMSdss program
failure.
BCS. Basic catalog structure.

BDAM. Basic direct access method.
COMPRESS command. The DFSMSdss function that

reduces partitioned data sets by taking unused space
and consolidating it at the end of the data set.
BLK. A subparameter of the SPACE parameter in a

DD statement. It specifies that space is allocated by
blocks.
concatenation. An operation that joins two characters

or strings in the order specified, forming one string
whose length is equal to the sum of the lengths of the
two characters or strings.
block length. Synonym for block size.

block size. (1) The number of data elements in a
block. (2) A measure of the size of a block, usually
specified in units such as records, words, computer
words, or characters. (3) Synonymous with block length.
(4) Synonymous with physical record size.
BPAM. Basic partitioned access method.
bpi. Bits per inch.
BSAM. Basic sequential access method.
C
CA. Control area.
call. (ISO) The action of bringing a computer program,
a routine, or a subroutine into effect, usually by
specifying the entry conditions and jumping to an entry
point.
card image. A one-to-one representation of the hole
patterns of a punched card; for example, a matrix in
314
|
|
|
|
concurrent copy. A function to increase the

accessibility of data by letting you make a consistent
backup or copy of data concurrent with normal
application program processing.
|
|
|
|
concurrent copy-compatible (CC-compatible)

snapshot. An operation that uses snapshot to provide
a concurrent copy-like function when the source volume
supports snapshot, but not concurrent copy.
control area (CA). A group of control intervals used
as a unit for formatting a data set before adding records
to it. Also, in a key-sequenced data set, the set of
control intervals, pointed to by a sequence-set index
record, that is used by VSAM for distributing freespace
and for placing a sequence-set index record adjacent to
its data.
control interval (CI). A fixed-length area of auxiliary
storage space in which VSAM stores records. It is the
unit of information transmitted to or from auxiliary file,
storage by VSAM.
control volume (CVOL). A volume that contains one

or more indexes of the catalog.
data set backup. Backup to protect against the loss of

individual data sets.
constructs. A collective name for data class, storage

class, management class, and storage group.
data set change indicator. A bit that is set by OPEN

when the data set is opened for processing other than
input. This flag is supported on MVS systems that have
data-set-changed flag support installed.
CONVERTV command. The DFSMSdss function that

converts volumes to and from Storage Management
Subsystem management without data movement.
COPY command. The DFSMSdss function that
performs data set, volume, and track movement.
DAU. Direct access unmovable.

DB2. IBM DATABASE 2.
DCB. Data control block.
CP. Control program.

CREDT. Creation date.
DEFRAG command. The DFSMSdss function that

consolidates the free space on a volume to help prevent
out-of-space abends on new allocations.
CSW. Channel status word.

CVAF. Common VTOC access facility.
DEQ. An assembler language macro instruction used

to remove control of one or more serially reusable
resources from the active task.
CVOL. Control volume.

CVT. Communication vector table.
CYL. A subparameter of the SPACE parameter in a
DD statement. It specifies that space is allocated by
cylinders.
D
DADSM. The direct access space management
program that maintains the VTOC, VTOCIX, and space
on a volume.
DAM. Direct access method.
DFSMS. Data Facility Storage Management

Subsystem.
DFSMS environment. An environment that helps
automate and centralize the management of storage.
This is achieved through a combination of hardware,
software, and policies. See also system-managed
storage.
DFSMSdfp. A DFSMS/MVS functional component that
provides functions for storage management, data
management, program management, device
management, and distributed data access.
DASD ERP. DASD error recovery procedure.
DFSMSdss. A DFSMS/MVS functional component

used to copy, move, dump, and restore data sets and
volumes. DFSMSdss is the primary data mover of
DFSMS/MVS.
DASD volume. A DASD space identified by a

common label and accessed by a set of related
addresses.
DFSMShsm. A DFSMS/MVS functional component

used for backing up and recovering data, and managing
space on volumes in the storage hierarchy.
data class. A list of data set allocation parameters and

the values that are used when allocating a new
SMS-managed data set.
DFSMS/MVS. Data Facility Storage Management

Subsystem/MVS.
DASD. Direct access storage device.
DFSORT. Data Facility Sort.
data compression (run-length). A method of

encoding repetitive series of identical characters so that
they occupy less space on a dump tape. Data
compression is supported by both physical dump and
logical dump processing.
DIAGNOSE. An access method services command

that scans an integrated catalog facility basic catalog
structure (BCS) or a VSAM volume data set (VVDS) to
validate the data structure.
Data Facility Storage Management Subsystem/MVS

(DFSMS/MVS). The complementary functions of
DFSMSdfp, DFSMSdss, DFSMShsm, and DFSMSrmm
which, together with RACF provide a system-managed,
administrator-controlled storage environment.
DIRF. DADSM interrupt recording facility. If a system

fails, or a permanent I/O error occurs during allocation
of space or during performance of a routine that
updates the VTOC, the VTOC may be in error. To
ensure that an error is recorded, the DADSM routines
turn on a bit in the VTOC upon entry to a DADSM
Glossary
315
function, and, if no errors occur during processing, turn

off that bit upon exiting from that function.
distribution libraries. IBM-supplied partitioned data
sets on tape containing one or more components that
the user restores to disk for subsequent inclusion in a
new system.
entry-sequenced data set (ESDS). In VSAM, a data

set whose records are loaded without respect to their
contents and whose RBAs cannot change. Records are
retrieved and stored by addressed access, and new
records are added at the end of the data set.
EOF. End-of-file.
DLIB. Distribution library.
EOJ. End of job.
DOC. In diagnosing program failures, the keyword that

identifies an error in the documentation of a program.
erase-on-scratch. The physical erasure of data on a

DASD data set when the data set is deleted
(scratched).
DOS. Disk Operating System.

ESA. Enterprise Systems Architecture.
DOS bit. On a volume without an indexed VTOC, a bit
that indicates that the free space map is invalid.
ESDS. Entry-sequenced data set.
DOS/VSE. DOS/Virtual Storage Extended.
ESTAE. Extended specify task abnormal exit.
DSCB. Data set control block.
EQ. Equal to.
DSCHA. A DFSMSdss keyword that is used in BY

filtering. It indicates that the data set is to be selected if
the data set has been changed.
EWS. Early warning system.
dsname. Data set name.
execute channel program (EXCP). A macro used to

access a data set without specifying the organization.
DSORG. Data set organization. It is specified in the

JCL as DSORG=.
DUMP command. The DFSMSdss function used to
back up data sets, tracks, and volumes.
dynamic allocation. Assignment of system resources
to a program when the program is performed rather
than when it is loaded main storage.
E
early warning system (EWS). A microfiche copy of
the information contained in the software support facility
(SSF), organized by component identification number,
and indexed by APAR symptom code. EWS is
published monthly and available to customers of IBM
licensed programs.
ECB. Event control block.
EXCP. Execute channel program.
EXPDT. Expiration date.

extended sequential data set. A sequential data set
that is structured logically the same as a physical
sequential data set but that is stored in a different
physical format. Extended sequential data sets consist
of one or more stripes and can take advantage of the
sequential data striping access technique. See also
sequential data striping and stripe.
extended specify task abnormal exit (ESTAE). A
task recovery routine that provides recovery for those
programs that run enabled, unlocked, and in task mode.
extent. A continuous space on a DASD volume
occupied by a data set or portion of a data set. An
extent of a data set contains a whole number of control
areas.
EC mode. Engineering change mode.

FC. CVAF function code.
empty data set. A data set in which the pointer to the
last-used block is 0.
ENQ. An assembler language macro instruction that
requests the control program to assign control of one or
more serially reusable resources to the active task. It is
also used to determine the status of a resource; that is,
whether it is immediately available or in use, and
whether control has been previously requested for the
active task in another ENQ macro instruction.
316
FCEC. CVAF function-error code.

filtering. The process of selecting data sets based on
specified criteria. These criteria consist of fully- or
partially-qualified data set names, or of certain data set
characteristics, or of both.
FMID. Function modification identifier.
fragmentation index. The qualitative measure of the

scattered free space on a volume.
fully-qualified data set name. A data set in which all
the qualifiers are completely spelled out.
function modification identifier (FMID). A code that
identifies the release levels of a program product.
FVL. Function vector list.
G
GDG. Generation data group.
GDS. Generation data set.
generalized trace facility (GTF). An optional OS/VS
service program that records significant systems events,
such as supervisor calls and start I/O operations, for the
purpose of problem determination.
generation data group (GDG). A collection of
historically related non-VSAM data sets that are
arranged in chronological order; each data set is a
generation data set.
generation data set. One generation of a generation
data group.
GT. Greater than.
GTF. Generalized trace facility.
the functions of the IBM software product. Such

modifications consist of exit routines written to replace
one or more existing modules of an IBM software
product, or to add one or more modules or subroutines
to an IBM software product, for the purpose of
modifying (including extending) the functions of the IBM
software.
integrated catalog facility. A facility by which VSAM
data set volume-related fields are separated from the
catalog and maintained in the VVDS on the volume on
which the data set resides.
integrated catalog facility catalog. A catalog that is
composed of a basic catalog structure (BCS) and its
related volume table of contents (VTOC) and VSAM
volume data sets (VVDSs).
Interactive Problem Control System (IPCS). A
component of MVS that permits online problem
management, interactive problem diagnosis, problem
tracking, and problem reporting.
Interactive Storage Management Facility (ISMF). An
interactive interface of DFSMS/MVS that allows users
and storage administrators access to the storage
management functions.
Interactive System Productivity Facility (ISPF). An
IBM licensed program used to develop, test, and run
application programs interactively. ISPF is the
interactive interface for all storage management
functions.
I/O. Input/output.
IPCS. Interactive Problem Control System.
HFS. Hierarchical file system.

IPL. Initial program load.
ISMF. Interactive Storage Management Facility.
ICKDSF. Device Support Facilities.
ISAM. Indexed sequential access method.
IDCAMS. Access Method Services.
ISMF. Interactive Storage Management Facility.
IMS/VS. Information Management System/Virtual

Storage.
ISPF. Interactive Systems Productivity Facility.
INCORROUT. In diagnosing program failures, the

keyword that identifies incorrect or missing program
output.
ISPF/PDF. Interactive Systems Productivity

Facility/Program Development Facility.
incremental backup. A process in which data sets are

backed up only if they have changed since their last
backup.
JCL. Job control language.
installation-wide exit. The means specifically

described in an IBM software product's documentation
by which an IBM software product may be modified by
a customer's system programmers to change or extend
JES2. An MVS subsystem that receives jobs into the

system, converts them to internal format, selects them
for operation, processes their output, and purges them
JES. Job entry subsystem.
Glossary
317
from the system. In an installation site with more than

one processor, each JES2 processor independently
controls its job input, scheduling, and output processing.
JES3. An MVS subsystem that receives jobs into the
system, converts them to internal format, selects them
for operation, processes their output, and purges them
from the system. In complexes that have several loosely
coupled processing units, the JES3 program manages
processors so that the global processor exercises
centralized control over the local processors and
distributes jobs to them via a common job queue.
link-pack area (LPA). An area of virtual storage that

contains reenterable routines that are loaded at IPL
(initial program load) time and can be used concurrently
by all tasks in the system.
load module. A computer program in a form suitable
for loading into main storage for operation.
load module library. A partitioned data set used to
store and retrieve load modules.
logical (data set) DUMP operation. A DUMP
operation in which logical processing is performed.
JFCB. Job file control block.

job control language (JCL). A problem-oriented
language used to identify the job or describe its
requirements to an operating system.
job entry subsystem (JES). A system facility for
spooling, job queuing, and managing I/O.
logical (data set) processing. Processing that treats

each data set and its associated information as a logical
entity. As an example, DFSMSdss processes an entire
data set before beginning with the next one.
logical (data set) RESTORE operation. A RESTORE
operation that uses as input a data set produced by a
logical DUMP operation.
JSCB. Job step control block.

logical volume. The output produced from a physical
DUMP operation, for which all data is derived from a
single DASD volume.
K
K. Kilobyte: 1 024 bytes.
key-sequenced data set. A VSAM file or data set
whose records are loaded in ascending key sequence
and controlled by an index. Records are retrieved and
stored by keyed access or by addressed access, and
new records are inserted in key sequence by means of
distributed free space. Relative byte addresses can
change because of control interval or control area splits.
keyword. A symptom that describes one aspect of a
program failure.
KRDS. Keyrange data set. Also known as a
key-sequenced data set with key ranges.
KSDS. Key-sequenced data set.
L
LASTCC. Last condition code.
LDS. Linear data set.
like devices. Devices that have the same track
capacity and number of tracks per cylinder (for
example, 3380 Model D, Model E, and Model K).
LINK. An assembler language macro instruction that
causes control to be passed to a specified entry point.
The linkage relationship established is the same as that
created by a basic assembler language (BAL)
instruction.
318
LOOP. In diagnosing program failures, the keyword

that identifies a program failure in which some part of
the program repeats endlessly.
LPA. Link-pack area.
LT. Less than.
LRECL. Logical record length.
LVOL. Logical volume.
M
Mb. Megabit; 1 048 576 bits.
MB. Megabyte; 1 048 576 bytes.
maintenance-level keyword. In diagnosing program
failures, a keyword that identifies the maintenance level
of DFSMSdss.
management class. A list of the migration, backup,
and retention parameters and the values for an
SMS-managed data set.
map record. The record that maps the tracks dumped
by DFSMSdss.
MAXCC. Maximum condition code.
MCS. Multiple console support.
MENTITY. Model entity.
minivolume. In an MVS system running on VM/370,

an OS/VS-formatted VM/370 minidisk whose size is
equal to or less than that of the real volume.
DFSMSdss uses the device size specified in the VTOC.
Minivolumes are supported only by the system version
of DFSMSdss.
MSGADRnnnt. In diagnosing program failures, the
DFSMSdss message keyword that tells of an error, or
seems itself to be in error.
MVS. Multiple Virtual Storage.
N
|
|
|
|
native snapshot. An operation that snaps data

directly from the source location and copies it to the
target location whenever the source and target data are
on like devices.
NVR. Non-VSAM volume record.
PDSE. Partitioned data set extended.

PERFM. In diagnosing program failures, the keyword
that identifies degradation in program performance.
physical (data set) DUMP operation. A DUMP
operation in which physical processing is performed.
physical (data set) processing. Processing that
moves data at the track-image level and can operate
against volumes, tracks, and data sets. As an example,
DFSMSdss may only process one volume of a
multivolume data set.
PLPA. Pageable link-pack area.
POU. Partitioned organization unmovable.
PRB. Program request block.
private library. A user-owned library that is separate
and distinct from the system library.
PSU. Physical sequential unmovable.
PSW. Program status word.
operating system (OS). Software that controls the

execution of programs; an operating system may
provide services such resource allocation, scheduling,
input/output control, and data management.
OS. Operating system.
OS/VS2. Operating System/Virtual Storage 2.
P
pageable link-pack area (PLPA). Link-pack area.
PAM. Partitioned access method.
partially qualified data set name. A data set name in
which the qualifiers are not spelled out. Asterisks and
percent signs are used in place of the undefined
qualifiers.
partitioned data set (PDS). A data set in direct
access storage that is divided into partitions, called
members, each of which can contain a program, part of
a program, or data.
partitioned data set extended (PDSE). A
system-managed, page-formatted data set on direct
access storage. A PDSE contains an indexed directory
and members similar to the directory and members of
partitioned data sets. A PDSE can be used instead of a
partitioned data set.
PDS. Partitioned data set.
PTF. Program temporary fix.
Q
QSAM. Queued sequential access method.
qualified name. A data set name consisting of a string
of names separated by periods; for example,
TREE.FRUIT.APPLE is a qualified name.
qualifier. Each component name in a qualified name
other than the rightmost name. For example, TREE
and FRUIT are qualifiers in TREE.FRUIT.APPLE.
queued sequential access method (QSAM). An
extended version of the basic sequential access method
(BSAM). Input data blocks awaiting processing or output
data blocks awaiting transfer to auxiliary storage are
queued on the system to minimize delays in I/O
operations.
R
RACF. Resource Access Control Facility.
| RAMAC Virtual Array (RVA). A DASD that uses a

| virtual array architecture.
RB. Request block.
RBA. Relative byte address.
RDJFCB. Read job file control block.
Glossary
319
RECEIVE processing. An SMP/E process necessary

to install new product libraries. During this process, the
code, organized as unloaded partition data sets, is
loaded into temporary SMPTLIB data sets. SMP/E
RECEIVE processing automatically allocates the
temporary partitioned data sets that correspond to the
files on the tape, and loads them from the tape.
RECFM. Record format.
recovery. The process of rebuilding data after it has
been damaged or destroyed, often by restoring a
backup version of the data or by reapplying transactions
recorded in a log.
REFDT. A DFSMSdss keyword used in BY filtering. It
indicates the last-referenced date.
relative byte address (RBA). The displacement
(expressed as a fullword binary integer) of a data record
or a control interval from the beginning of the data set
to which it belongs, independent of the manner in which
the data set is stored.
relative record data set (RRDS). A VSAM data set
whose records are loaded into fixed-length slots.
S
SAF. System authorization facility.
SAM. Sequential access method.
scheduler task. A DFSMSdss subtask that interprets
and schedules commands.
SCP. System control program.
SEQ. Sequential or sequential processing.
sequential data striping. A software implementation
of a disk array that distributes data sets across multiple
volumes to improve performance.
SEREP. System environmental recording, editing, and
printing
SMF. System management facilities.
SML. MVS Storage Management Library.
SMP. System Modification Program.
SMP/E. System Modification Program/Extended.
RELEASE command. The DFSMSdss function that

releases the unused space in sequential and partitioned
data sets for use by other data sets.
RESERVE. A method of serializing DADSM update
accesses to the VTOC. It is also a method of serializing
processor accesses to a shared DASD volume.
Resource Access Control Facility (RACF). An IBM
program product that provides for access control by
identifying and verifying users to the system, authorizing
access to DASD data sets, logging the detected
unauthorized attempts to enter the system, and logging
the detected accesses to protected data sets.
RESTORE command. The DFSMSdss function used
to recover data sets, tracks, and volumes.
RMID. Replacement module identifier.
RRDS. Relative record data set.
| RVA. RAMAC Virtual Array.

run-length data compression. Data compression
(run-length).
SMPE. A cataloged procedure that includes the

required DD statements for running SMP/E and is used
in the RECEIVE, APPLY, and ACCEPT steps of SMP/E
processing.
SMS. Storage Management Subsystem.
| snapshot. A function of the RAMAC Virtual Array

| (RVA) that allows an instantaneous copy to be made of
| data sets using DFSMS software.
software support facility (SSF). An IBM online data
base that allows for storage and retrieval of information
about all current APARs and PTFs.
SP. System Product.
sphere. A VSAM cluster with one or more associated
alternate indexes and paths. The VSAM cluster
(sometimes called the base cluster), alternate indexes,
and paths are sometimes referred to as sphere
components.
SSF. Software support facility.
standalone restore. One of two DFSMSdss programs.
The standalone restore program runs independently of
the MVS system environment and is limited to one
functiona full or partial (tracks) RESTORE from a
dump tape.
storage class. A named list of data set storage
attributes that identify performance goals and availability
320
requirements, defined by the storage administrator,

used to select a device that can meet those goals and
requirements.
System Modification Program (SMP). A program

used to install software and software changes on the
MVS system.
storage constructs. The group of predefined models

(data class, management class, storage class, and
storage group) that are used to classify storage
management needs and procedures for data sets under
the Storage Management Subsystem. Each data set
has construct names associated with it by explicit
specification or defaulting.
System Modification Program Extended (SMP/E).

An IBM licensed program used to install software and
software changes on the MVS system. In addition to
providing the services of SMP, SMP/E consolidates
installation data, allows more flexibility in selecting
changes to be installed, provides a dialog interface, and
supports dynamic allocation of data sets.
storage group. A named collection of DASD volumes

that have been grouped to meet a defined service
strategy.
T
TCB. Task control block.
storage management. The task of managing auxiliary

storage resources for an installation.
Storage Management Subsystem (SMS). An MVS
subsystem that helps automate and centralize the
management of storage. To manage storage, the
storage management subsystem provides the storage
administrator with control over data class, storage class,
management class, storage group, and automatic class
selection routine definitions.
stripe. The portion of a striped data set (for example,
an extended sequential data set) that resides on one
disk. The records in that portion are not necessarily
logically consecutive. The system distributes records
among the stripes such that the disks can be read or
written simultaneously to gain better performance.
subtask. A task initiated and ended by a higher order
task.
SVC. Supervisor call instruction.
SVRB. Supervisor request block.
SYSRES. System residence disk
system data. The data sets required by MVS or its
subsystems for initialization.
system-managed data set. A data set that has been
assigned a storage class.
Time sharing option (TSO). An option on the

operating system for a System/370 that provides
interactive time sharing from remote terminals.
TIOT. Task input/output table.
TLIB. Target library.
track packing. A technique used by DFSMSdss that
builds target tracks for any DASD device using input
physical record information.
TRK. A subparameter of the SPACE parameter in a
DD statement. It specifies that space is to be allocated
by tracks.
TSO. Time-sharing option.
TSO/E. TSO/Extensions.
TTR. Track-track-record.
type-of-failure keyword. In diagnosing program
failures, a keyword that identifies the type of program
failure that has occurred in DFSMSdss.
U
UACC. Universal access authority.
UCB. Unit control block.
system-managed storage. Storage managed by the

Storage Management Subsystem. SMS attempts to
deliver required services for availability, performance,
space, and security to applications.
UIM. User interaction module.
system library. A collection of data sets or files in

which the parts of an operating system are stored.
used tracks. Tracks from the beginning of data sets to

the last-used track.
system link library. System library.
user exit. A programming service provided by an IBM

software product that may be requested by an
application program for the service of transferring
unlike devices. Devices that have different track

capacities or a different number of tracks per cylinder.
Glossary
321
control back to the application program upon the later

occurrence of a user-specified event.
VRRDS. A VSAM variable record RRDS.

VSAM. Virtual storage access method.
V
VDRL. Volume restore limits.
VSAM volume data set (VVDS). A data set that

describes the VSAM and SMS-managed non-VSAM
data sets on a volume. The name of the data set is
SYS1.VVDS.Vvolser.
VDSS. VTOC/Data Set Services.

VSE. Virtual storage extended.
virtual storage access method (VSAM). An access
method for direct or sequential processing of fixed and
variable-length records on direct access devices. The
records in a VSAM data set or file can be organized in
logical sequence by a key field (key sequence), in the
physical sequence in which they are written on the data
set or file (entry-sequence), or by the relative-record
number.
VTOC. Volume table of contents.

VTOCIX. The data set on which the location of the
data set VTOC entries are kept in an index for quick
access by DADSM. The name of the data set is
SYS1.VTOCIX.Vvolser.
VVDS. VSAM volume data set.
VM. Virtual machine.

VVR. VSAM volume record.
VOLID. Volume ID.
VOLSER. Volume serial number.
volume. The storage space on DASD, tape or optical
devices, which is identified by a volume label.
volume backup. Backup of an entire volume to
protect against the loss of the volume.
W
WAIT. In diagnosing program failures, the keyword
that identifies DFSMSdss suspended activity, while
waiting for some condition to be satisfied. DFSMSdss
does not issue a message to tell why it is waiting.
WTO. Write to operator.
volume header record. The record in the DFSMSdss

dump tape that identifies and contains data pertinent to
the whole volume, and identifies the type of operation
that created a dump.
X
XA. Extended Architecture.
volume trailer record. The record in the DFSMSdss

dump tape that identifies the end of the data for a
DASD volume.
322
Index
Special Characters
* (single asterisk) used in partially qualified data set
names 12
** (double asterisk) used in partially qualified data set
names 12
% (percent sign) used in partially qualified data set
names 12
Numerics
16 megabytes virtual storage
buffers above 9
31-bit addressing mode 262
3494 Tape Library 188
3495 Tape Library 188
A
ABEND keyword 7
ABOVE16 keyword 9
access authority
compatibility with Version 1 237
access authorization
for DFSMSdss commands 223
ACL (automatic cartridge loader) 190
ACTIVE subkeyword of TGTGDS
COPY command 65
RESTORE command 161
ADMINISTRATOR keyword 211, 216
COMPRESS command 30
COPY command 43
DEFRAG command 82
DUMP command 93
FACILITY-class profiles for 217
PRINT command 118
RELEASE command 126
RESTORE command 139
ADMINISTRATOR parameter (Stand-Alone BUILDSA
command) 24
ADRDSSU 255
ADREID0 data area 278
example 283
ADRMCLVL macro 284
ADRUFO record
presenting, eioption 13 268
ADRUIM module 258
ADRXMAIA 258
ADSP (Automatic Data Set Protection) 211
attribute 212
AIX (alternate index), recataloging 47
ALLDATA keyword
COPY command 43
ALLDATA keyword (continued)

copying data set to like device 77
copying data set to unlike device 78
DUMP command 93
PRINT command 118
ALLEXCP keyword
COPY command 44
copying data set to like device 77
copying data set to unlike device 78
DUMP command 94
ALLMULTI Keyword 237
ALLOC keyword 14
allocation
space 65, 161
alternate index
recataloging 47
always-call 211, 213
AMDSADMP (SADMP) service aid 195
AMSGCNT keyword 7
application interface 289
blocks 259
example 288, 290
structure 257
summary
data set processing 278
record processing 277
application program
process 287
ASIDPTR 257
assignment of class names using the RESTORE and
COPY commands 168
asterisks, in a data set qualifier 12
authorization levels for BUILDSA command 202
automatic cartridge loader 190
Automatic Data Set Protection 212
See also ADSP
AUTORELBLOCKADDRESS keyword
COPY command 45
RESTORE command 140
auxiliary commands 177
continuation errors 183
EOJ 183
IF-THEN-ELSE 180
PARALLEL 177
SERIAL 177
SET 179
WTO 177
avoiding lockout 277
323
B
backing up (dumping) data 89
backup
copies
multiple 80, 103
BELOW16 keyword 9
BLK subkeyword of TGTALLOC
COPY command 65
RESTORE command 161
BLKSIZE and LRECL keywords, specifying in a print
operation 120
block size (DFSMSdss dump data set)
controlling at dump time 103
default when dumping to tape or DASD 103
with COPYDUMP command 80
block structure, calling 255
blocks
application interface 259
buffers
above 16 megabytes 9
building a Stand-Alone Services IPL-able core
image 23
BY keyword
COMPRESS command 30
COPY command 45
criteria 11
DEFRAG command 83
DUMP command 94
filtering criteria 19
RELEASE command 127
RESTORE command 140
bypass verification exit
eioption 22 271
BYPASSACS keyword
COPY command 45
RESTORE command 140
C
calling block structure 255
CANCELERROR keyword
COPY command 46
DUMP command 95
RESTORE command 141
catalog
access authority 222
search order
standard 19
temporary copied 214
CATALOG keyword
CONVERTV command 35
COPY command 46
RESTORE command 141
catalog management 207
services 207
324
catalog management services

ALTER function 207
CATLG keyword 15
characteristics
data sets 11
filtering by 14
CHECKVTOC keyword
COPY command 47
DUMP command 95
class selection, process diagram 168
codes, condition 178
See also condition codes
command
IF-THEN-ELSE 181
null 181
syntax, general instructions 3
commands
auxiliary 177
function 21
See also function commands
overview 21
compaction 95
compatibility
DFDSS and DFSMSdss 237
DFSMSdss and DFDSS 237
COMPRESS command
ADMINISTRATOR keyword 30
BY keyword 30
DDNAME keyword 31
DYNALLOC keyword 31
DYNAM keyword 31
EXCLUDE keyword 32
FILTERDD keyword 32
INCLUDE keyword 32
PASSWORD keyword 32
sample operations 33
WAIT keyword 33
COMPRESS keyword
DUMP command 95
COMPRESS, access authorization for 224
concurrent copy 61, 116
dynamic pacing 61
full-volume dump 111
initialization 116
concurrent copy initialization complete
eioption 24 275
concurrent copy-compatible 48
CONCURRENT keyword 41, 42, 43, 47, 90, 91, 92,
93, 96
COPY command 47
DUMP command 96
condition codes
general description 178
LASTCC 179
MAXCC 179
setting 179
continuation errors in auxiliary commands 183

control area 52, 148
control interval 52, 148
control volumes 222
controlling task processing
description 178
CONVERT keyword
COPY command 48
CONVERTV command
CATALOG keyword 35
DDNAME keyword 35
DYNAM keyword 35
explanation 34
FORCECP keyword 36
INCAT keyword 35, 36
NONSMS keyword 36
PREPARE keyword 36
REDETERMINE keyword 36
SELECTMULTI keyword 37
serialization 247
SMS keyword 37
syntax diagram 34
TEST keyword 37
COPY command 52, 65, 70
ACTIVE subkeyword of TGTGDS 65
ALLDATA keyword 43
ALLEXCP keyword 44
AUTORELBLOCKADDRESS keyword 45
BLK subkeyword of TGTALLOC 65
BY keyword 45
BYPASSACS keyword 45
CANCELERROR keyword 46
CATALOG keyword 46
CHECKVTOC keyword 47
CONCURRENT keyword 47
CONVERT keyword
partitioned data set 48
partitioned data set extended 48
COPY command 56
COPYVOLID keyword 48
CPVOLUME keyword 49
CPYV keyword 48
CYL keyword 65
data set to like device 77
data set to unlike device 78
DATASET keyword 49
DEFERRED subkeyword of TGTGDS 65
DELETE keyword 50
DYNALLOC keyword 50
ENQFAILURE subkeyword 66
example 9
EXCLUDE keyword 51
explanation 39
FILTERDD keyword 51
COPY command (continued)

FORCE keyword 51
FORCECP keyword 51
FREESPACE keyword 52
FULL keyword 52
INCAT keyword 52
INCLUDE keyword 53
INDDNAME keyword 53
INDYNAM keyword 54
IOERROR subkeyword 66
LOGINDDNAME keyword 54
LOGINDYNAM keyword 54
MAKEMULTI keyword 55
MENTITY keyword 56
MGMTCLAS keyword 56
MVOLSER keyword 56
NOPACKing command 57
NULLMGMTCLAS keyword 56
NULLSTORCLAS keyword 64
OUTDDNAME keyword 57
OUTDYNAM keyword 58
OUTTRACKS keyword 58
PASSWORD keyword 59
PDS subkeyword 48
PDSE subkeyword 48
PERCENTUTILIZED keyword 59
PROCESS keyword 60
PURGE keyword 60
READIOPACING keyword 61
REBLOCK keyword 61
RECATALOG keyword 46
RELBLOCKADDRESS keyword 62
RENAMEUNCONDITIONAL keyword 62
REPLACE keyword 63
SHARE keyword 63
SOURCE subkeyword of TGTALLOC 65
SOURCE subkeyword of TGTGDS 65
special considerations 39
SPHERE keyword 63, 132
STORCLAS keyword 64
STORGRP keyword 64
syntax diagram 40
SYS1 subkeyword 60
TGTALLOC keyword 65
TGTGDS keyword 65
TOLERATE keyword 66
TRACKS keyword 67
TRK subkeyword of TGTALLOC 65
TTRADDRESS keyword 67
UNCATALOG keyword 68
UNDEFINDSORG keyword 60
VOLCOUNT keyword 68
WRITECHECK keyword 70
Index
325
copy operation
logical data set 39
COPY, access authorization for 224, 230
COPYDUMP command
explanation 80
INDDNAME keyword 80
LOGICALVOLUME keyword 80
syntax diagram 80
COPYDUMP, access authorization for 230
copying the Stand-Alone Services core image
(example) 27
COPYVOLID keyword
COPY command 48
RESTORE command 142
CPVOLUME keyword
COPY command 49
DUMP command 96
RESTORE command 143
CPYV keyword
COPY command 48
CREDT keyword 15
criteria for filtering 11
Cross-Memory Application Interface
module main entry point 258
restrictions 263
usage guidelines 263
customizing
ISMF 311
restrictions 311
CYL subkeyword of TGTALLOC
COPY command 65
RESTORE command 161
D
DASD (direct access storage device)
space fragmentation 82
DASDVOL authority 207, 208, 220
limitations 220
DASDVOL-access authority 211, 216, 218, 230
data integrity
considerations
COPY command 71
DUMP command 110
RESTORE command 136
duplicate volser considerations 136
DYNALLOC keyword 244
ENQ keyword 243
RESERVE macro 241
RESERVE-ENQUEUE processing 248
serialization 241
WAIT option 243, 246
data set 167
BY filtering 19
326
data set (continued)

characteristics (BY criteria) 11
dummy 215
filtering 11
moving 9
name
fully qualified 12
partially qualified 12
non-VSAM enqueue options 244
profiles
discrete 211, 212
generic 211
qualifier, rules regarding asterisks in 12
RESTORE 10
SMS-managed data sets
non-VSAM 166
physical restore actions 166
VSAM 166
temporary 214
to like device, ALLDATA and ALLEXCP interactions
when copying 77
to unlike device, ALLDATA and ALLEXCP
interactions when copying 78
data set attribute sources 307
data set processed notification exit
eioption 23 274
data set verification
eioption 21 270
data-set-changed flag, DUMP command 105
DATACLAS keyword 15
DATALENGTH keyword
PRINT command 118
DATASET keyword
COPY command 49
DUMP command 97
PRINT command 118
RESTORE command 143
DCB keywords LRECL and BLKSIZE, specifying in a
print operation 120
DDNAME keyword
COMPRESS command 31
CONVERTV command 35
DEFRAG command 83, 84
RELEASE command 127
DDNAME list 255
DDNAME/VOLID Pointer 263
DDPTR parameter 255
DEFERRED subkeyword of TGTGDS
COPY command 65
RESTORE command 161
DEFRAG
access authorization for 230
DEFRAG command
BY keyword 83
DDNAME keyword 83
DEFRAG command (continued)

DDNAME subkeyword 83, 84
DYNALLOC keyword 83
DYNAM keyword 84
EXCLUDE keyword 84
explanation 82
FORCECP keyword 84
FRAGMENTATIONINDEX keyword 85
LIST subkeyword 83, 84
MAXMOVE keyword 85
PASSDELAY subkeyword 85
PASSWORD keyword 86
syntax diagram 82
WAIT keyword 87
DEFRAG data set 213
DELETE keyword
COPY command 50
DUMP command 97
DELETECATALOGENTRY keyword
RESTORE command 144
determining version, release, modification level
using the ADRMCLVL macro 284
devices supported by Stand-Alone Services 203
DEVTYPE parameter (Stand-Alone TAPECNTL
command) 201
DFM 50
DFP segment 215
DFSMSdss
commands
access authorization 223
compatibility
with DFDSS 237
with Version 1 237
module, main entry point 255
pointer to address-space-identifier list 257
Processing Option 260
direct access data set
copying 62
restoring 156
disk track
reading, eioption 07 267
writing, eioption 08 267
DO-END group of commands 178, 182
condition for processing 179
syntax 180
DSCHA keyword 15
DSORG keyword 15
dummy data set 215
DUMP command
access authorization for 230
ALLDATA keyword 93
ALLEXCP keyword 94
BY keyword 94
DUMP command (continued)

CHECKVTOC keyword 95
COMPRESS command 95
CONCURRENT keyword 96
CPVOLUME keyword 96
data set example 9
data-set-changed flag 105
DATASET keyword 97
DELETE keyword 97
DYNALLOC keyword 98
EXCLUDE keyword 98
explanation 89
FILTERDD keyword 98
FORCECP keyword 98
FULL keyword 99
INCAT keyword 99
INCLUDE keyword 100
INDDNAME keyword 100
INDYNAM keyword 100
LOGINDDNAME keyword 101
LOGINDYNAM keyword 101
multiple copies 103
NOVALIDATE keyword 102, 109
ONLYINCAT keyword 99, 102
OPTIMIZE keyword 102
PASSWORD keyword 103
PROCESS keyword 104
PURGE keyword 104
READIOPACING keyword 104
RESET keyword 105
SHARE keyword 106
SPHERE keyword 106
STORGRP keyword 106
syntax diagram 90
SYS1 subkeyword 104
TOLERATE keyword 107
TRACKS keyword 108
UNCATALOG keyword 108
VALIDATE keyword 109
WAIT keyword 109
dump data, multiple copies 80, 103
dump operation
physical data set 90
COMPRESS command 31
COPY command 50
DEFRAG command 83
DUMP command 98
PRINT command 119
Index
327
DYNALLOC keyword (continued)

RELEASE command 127
RESTORE command 146
DYNAM keyword
COMPRESS command 31
CONVERTV command 35
DEFRAG command 84
RELEASE command 127
dynamic allocation 244
E
eioption 00
function startup 264
eioption 01
reading SYSIN record 264
eioption 02
printing SYSPRINT record 265
eioption 03
reading physical tape record 265
eioption 04
reading logical tape record 266
eioption 05
writing logical tape record 266
eioption 06
writing physical tape record 266
eioption 07
reading disk track 267
eioption 08
writing disk track 267
eioption 09
reading utility SYSPRINT 267
eioption 10
writing SYSPRINT record 267
eioption 11
writing WTO message 268
eioption 12
writing WTOR message 268
eioption 13
presenting ADRUFO record 268
eioption 14
function ending 268
eioption 15
presenting WTOR response 269
eioption 16
OPEN/EOV tape volume security and verification
exit 269
eioption 17
OPEN/EOV nonspecific tape volume mount 269
eioption 18
insert logical VSAM record during restore 269
eioption 19
output tape I/O error 270
eioption 20
volume notification 270
328
eioption 21
data set verification 270
eioption 22
bypass verification exit 271
eioption 23
data set processed notification exit 274
eioption 24
concurrent copy initialization complete 275
eioption 26
IMS volume notification user exit 277
ejection, page suppressing 7
ELSE command 180
END command
in DO-END 181
ending
function, eioption 14 268
ending your DFSMSdss step 183
ENDTRK parameter (Stand-Alone RESTORE
command) 198
ENQ keyword 243
ENQFAILURE subkeyword
COPY command 66
DUMP command 107
PRINT command 121
RESTORE command 162
enqueue exit routine
options for non-VSAM data sets 244
enqueue scheme 243
enqueuing 244
EOJ command 183
EQ operator 15
erase-on-scratch 215
ERRORTRACKS keyword
PRINT command 119
EXCLUDE criteria 11
EXCLUDE keyword
COMPRESS command 32
COPY command 51
DEFRAG command 84
DUMP command 98
RELEASE command 128
RESTORE command 147
EXEC statement 5, 9
PARM information in the EXEC statement 7
exit identification block 260
exit interface, structure 259
EXPDT keyword 15
extended-sequential data set 48, 71, 125, 166
EXTNT keyword 15
F
FACILITY-class profiles 216, 217
for DFSMSdss keywords 209
FILE parameter (Stand-Alone RESTORE
command) 199
filter DD, JCL statement 7

FILTERDD keyword
COMPRESS command 32
COPY command 51
DUMP command 98
RELEASE command 128
RESTORE command 147
filtering
BY 19
characteristics 14
general description 11
relative generation 14
VSAM data sets 11
FORCE keyword
COPY command 51
RESTORE command 147
FORCECP keyword
CONVERTV command 36
COPY command 51
DEFRAG command 84
DUMP command 98
RELEASE command 128
RESTORE command 147
FRAGMENTATIONINDEX keyword
DEFRAG command 85
free-space fragmentation 82
FREESPACE keyword
COPY command 52
RESTORE command 148
FROMADDR parameter (Stand-Alone RESTORE
command) 197
FROMDEV parameter (Stand-Alone RESTORE
command) 197
FSIZE keyword 15
FULL keyword
COPY command 52
DUMP command 99
RESTORE command 148
FULL parameter (Stand-Alone RESTORE
command) 198
fully qualified data set names 12
function commands 175
function ending
eioption 14 268
function startup
eioption 00 264
G
GDG (generation data group)
data set status assignment 65, 161
filtering 14
GE operator 15
generating the Stand-Alone Services program
generation data group 14
See also GDG
23
global access checking table

GT operator 15
210, 212
H
hardware requirements for Stand-Alone Services
Hierarchical File system (HFS) data set 39
203
I
I/O error
output tape, eioption 19 270
ICKDSF REFORMAT command 25
IF command
nested 182
IF-THEN-ELSE command
description 178
examples 182
IF-THEN-ELSE group of commands
syntax 180
IF-THEN=ELSE command sequencing 181
IMPORT keyword 236
RESTORE command 148
IMS volume notification user exit
eioption 26 277
INCAT keyword
CONVERTV command 35, 36
COPY command 52
DUMP command 99
RELEASE command 129
INCLUDE criteria 11
INCLUDE keyword
COMPRESS command 32
COPY command 53
DUMP command 100
RELEASE command 129
RESTORE command 149
INDDNAME keyword
COPY command 53
COPYDUMP command 80
DUMP command 100
PRINT command 119
RESTORE command 150
INDDNAME parameter (Stand-Alone BUILDSA
command) 24
INDYNAM keyword
COPY command 54
DUMP command 100
PRINT command 119
initialization
concurrent copy failure 111, 116
initialization complete
concurrent copy, eioption 24 275
input error toleration
COPY command 66
DUMP command 107
Index
329
input error toleration (continued)

PRINT command 121
input to DFSMSdss (in DD statement) 6
insert logical VSAM record during restore
eioption 18 269
integrity
data, serialization 241
Interactive Storage Management Facility 311
See also ISMF
invoking DFSMSdss
JCL examples 9
via ATTACH, LINK, or CALL macro 258
IOERROR subkeyword
COPY command 66
DUMP command 107
PRINT command 121
IPL
devices for Stand-Alone Services 203
example 193
parameter (BUILDSA command) 24
IPLing Stand-Alone Services on a stand-alone
system 192
ISMF (Interactive Storage Management Facility)
customization 311
restrictions to customizing 311
J
JCL (job control language)
concurrent copy 111, 116
EXEC statement 5
filter DD statement 7
input DD statement 6
invoking DFSMSdss 9
JOBCAT DD statement 5
JOBstatement 5
output DD statement 6
password DD statement 7
requirements for DFSMSdss 5
STEPCAT DD statement 5
SYSIN DD statement 5
SYSPRINT DD statement 5
volume count subparameter 6
job control language 5
See also JCL
JOB statement
JCL 5
JOBCAT DD statement, JCL 5
K
KEYLENGTH keyword
PRINT command 120
330
L
LASTCC
definition 179
in IF-THEN-ELSE command sequence 180
in SET command 179
LE operator 15
LINECNT keyword 7
LIST subkeyword
DEFRAG command 83, 84
lockout, avoiding 242, 277
LOGDDNAME keyword
RELEASE command 129
logical VSAM record
insert during restore, eioption 18 269
LOGICALVOLUME keyword
COPYDUMP command 80
RESTORE command 150
LOGINDDNAME keyword
COPY command 54
DUMP command 101
LOGINDYNAM keyword
COPY command 54
DUMP command 101
LRECL and BLKSIZE keywords, specifying in a print
operation 120
LT operator 15
M
MAKEMULTI keyword
COPY command 55
RESTORE command 150
mapping macro
ADREID0 278
MAXCC keyword
definition 179
in IF-THEN-ELSE command sequence 180
in SET command 179
MAXMOVE keyword
DEFRAG command 85
MENTITY keyword 216, 227, 229, 233, 235
COPY command 56
RESTORE command 151
message data set 213
MGMTCLAS keyword 15
COPY command 56
RESTORE command 151
MGMTCLAS profile 215
MINSECQTY keyword
RELEASE command 131
MINTRACKSUNUSED keyword
RELEASE command 131
mode switching 178
moving
data sets 9, 50
MULTI keyword 15
multiple backup copies 80, 103
multiple subkeywords 2
multiple tracks read, on dump 102
multivolume data set 215
copying 55
MVOLSER keyword
COPY command 56
RESTORE command 151
N
NE operator 15
nested IF commands 182
non-SMS authorization 223
non-VSAM data sets
restore actions on 167
NONSMS keyword
CONVERTV command 36
NOPACKing keyword
COPY command 57
RESTORE command 151
NOREADCHECK parameter (Stand-Alone RESTORE
command) 199
NORUN keyword 8
notification
data set processed exit, eioption 23 274
volume, eioption 20 270
NOTIFYCONCURRENT keyword 41, 47, 92, 96
NOVALIDATE keyword
DUMP command 102, 109
NOVERIFY parameter (Stand-Alone RESTORE
command) 197
null command 181
NULLMGMTCLAS keyword
COPY command 56
RESTORE command 151
NULLSTORCLAS keyword
COPY command 64
RESTORE command 160
O
ONLYINCAT keyword
COPY command 52
DUMP command 99, 102
OPEN/EOV nonspecific tape volume mount
eioption 17 269
OPEN/EOV tape volume security and verification exit
eioption 16 269
operating in serial or parallel mode 177
OPERATIONS attribute 207, 208
OPERCNSL parameter (Stand-Alone BUILDSA
command)
limited validation of 187
purpose of 187
OPERCNSL parameter (Stand-Alone BUILDSA

command) (continued)
specifying 25
OPTIMIZE keyword
DUMP command 102
option list 255
OPTPTR parameter 255
Original Record Length 262
Original Record Pointer 262
OS CVOL
access authority 222
naming convention 222
OUTDDNAME keyword
COPY command 57
COPYDUMP command 81
DUMP command 103
PRINT command 120
RESTORE command 152
OUTDDNAME parameter (Stand-Alone BUILDSA
command) 26
OUTDYNAM keyword
COPY command 58
RESTORE command 152
OUTDYNAM parameter (Stand-Alone BUILDSA
command) 26
output from DFSMSdss (in DD statement) 6
output tape I/O error
eioption 19 270
OUTTRACKS keyword
COPY command 58
RESTORE command 153
overview of the Stand-Alone Services process 190
P
page ejection, suppressing 7
page-number list 256
PAGENO keyword 7
PAGEPTR parameter 256
PARALLEL command 177, 178
PARAM keyword 257
PARM information in the EXEC statement
partially qualified data set names 12
PASSDELAY subkeyword
DEFRAG command 85
password DD, JCL statement 7
PASSWORD keyword
COMPRESS command 32
COPY command 59
DEFRAG command 86
DUMP command 103
PRINT command 120
RELEASE command 132
RESTORE command 154
password protection 210
Index
331
PDS subkeyword
COPY command 48
PDSE subkeyword
COPY command 48
PERCENTUTILIZED keyword
COPY command 59
RESTORE command 154
performing a restore from dump tapes 196
PREPARE keyword
CONVERTV command 36
preparing for Stand-Alone Services 21, 202, 203
presenting ADRUFO record
eioption 13 268
presenting WTOR response
eioption 15 269
PRINT command
ALLDATA keyword 118
DATALENGTH keyword 118
DATASET keyword 118
ERRORTRACKS keyword 119
explanation 117
INDYNAM keyword 119
KEYLENGTH keyword 120
SHARE keyword 121
syntax diagram 117
TRACKS keyword 121
VTOC keyword 122
WAIT keyword 122
PRINT, access authorization for 231
printing SYSPRINT record
eioption 02 265
PROCESS keyword
COPY command 60
DUMP command 104
RELEASE command 132
RESTORE command 155
protect-all 213
protected
catalogs 222
group data set 211
user data set 210
protecting
data sets 209
passwords 210
resources 209
SMS-managed data sets 215
usage of DFSMSdss 209
332
PURGE keyword
COPY command 60
DUMP command 104
RESTORE command 155
Q
qualified data set names
12
R
RACF (Resource Access Control Facility) 207
authorization checking 56, 151
DEFINE function 207
logging 216
RACF-indicated, meaning of 212
RACF-protected, meaning of 207
RAMAC Virtual Array 39
READCHECK parameter (Stand-Alone RESTORE
command) 198
reading disk track
eioption 07 267
reading logical tape record
eioption 04 266
reading physical tape record
eioption 03 265
reading SYSIN record
eioption 01 264
reading utility SYSPRINT
eioption 09 267
READIOPACING keyword 42, 43, 61
COPY command 61
DUMP command 104
REBLOCK keyword
COPY command 61
RESTORE command 155
RECATALOG keyword
COPY command 46
RESTORE command 141
Record Area Length 262
REDETERMINE keyword
CONVERTV command 36
REFDT keyword 15
relative generation filtering 14
RELBLOCKADDRESS keyword
COPY command 62
RESTORE command 156
RELEASE command
BY keyword 127
cross-system serialization 127
DDNAME keyword 127
DYNAM keyword 127
EXCLUDE keyword 128
explanation 124
RELEASE command (continued)

FILTERDD keyword 128
FORCECP keyword 128
INCAT keyword 129
INCLUDE command 129
LOGDDNAME keyword 129
MINSECQTY keyword 131
MINTRACKSUNUSED keyword 131
PROCESS keyword 132
STORGRP keyword 133
syntax diagram 125
SYS1 subkeyword 132
WAIT keyword 133
RELEASE, access authorization for 231
RENAME keyword
RESTORE command 156
RENAMEUNCONDITIONAL keyword
COPY command 62
RESTORE command 158
REPLACE keyword
COPY command 63
RESTORE command 159
requirements
real storage for Stand-Alone Services program
operation 185
Stand-Alone Services hardware and software 203
RESERVE macro 241
RESET keyword
DUMP command 105
Resource Access Control Facility 207
See also RACF
resource serialization 247
RESOWNER field 215
RESTORE
actions on SMS-managed data sets 166
RESTORE command
actions on non-VSAM data sets 167
ACTIVE subkeyword of TGTGDS 161
AUTORELBLOCKADDRESS keyword 140
BLK subkeyword of TGTALLOC 161
BY keyword 140
BYPASSACS keyword 140
CATALOG keyword 141
COPYVOLID keyword 142
CPVOLume keyword 143
cross-system serialization 146
CYL subkeyword of TGTALLOC 161
data set example 10
DATASET keyword 143
DEFERRED subkeyword of TGTGDS 161
DELETECATALOGENTRY keyword 144
RESTORE command (continued)

EXCLUDE keyword 147
explanation 135
FILTERDD keyword 147
FORCE keyword 147
FORCECP keyword 147
FREESPACE keyword 148
FULL keyword 148
IMPORT keyword 148, 236
INCLUDE keyword 149
LOGICALVOLUME keyword 150
MAKEMULTI keyword 150
MENTITY keyword 151
MGMTCLAS keyword 151
MVOLSER keyword 151
NOPACKING keyword 151
NULLMGMTCLAS keyword 151
NULLSTORCLAS keyword 160
OUTDYNAM keyword 152
OUTTRACKS keyword 153
PERCENTUTILIZED keyword 154
PROCESS keyword 155
PURGE keyword 155
REBLOCK keyword 155
RECATALOG keyword 141
RELBLOCKADDRESS keyword 156
RENAME keyword 156
RENAMEUNCONDITIONAL keyword 158
REPLACE keyword 159
ROLLEDOFF subkeyword of TGTGDS 161
SHARE keyword 159
SOURCE subkeyword of TGTALLOC 161
SOURCE subkeyword of TGTGDS 161
SPHERE keyword 160
STORCLAS keyword 160
syntax diagram 137
TGTALLOC keyword 161
TGTGDS keyword 161
TRACKS keyword 162
TRK subkeyword of TGTALLOC 161
TTRADDRESS keyword 163
UNDEFINEDSORG subkeyword 155
VOLCOUNT keyword 163
WAIT keyword 165
restore operation
actions on non-VSAM data sets 167
actions on SMS-managed data sets 166
data set
key-sequenced with no secondary allocation
Index
135
333
restore operation (continued)

data set (continued)
partitioned with secondary allocation of zero 135
RACF-protected VSAM, logical restore of 135
RENAME, RENUNC, REPLACE keywords 136
RESTORE, access authorization for 231, 236
REWIND parameter (Stand-Alone TAPECNTL
command) 201
RIOP keyword 42, 43
ROLLEDOFF subkeyword of TGTGDS 65
COPY command 65
RESTORE command 161
running Stand-Alone Services
in 370 mode 186
in XA or ESA mode 186
under VM 186
with a predefined console 187
running the Stand-Alone Services program 190
RVA 48
S
SADMP service aid 195
SAF (system authorization facility) 207
DEFINE function 207
SAM compressed data set
copying 39
SCAN keyword 8
SDUMP keyword 7
search order, standard catalog 19
SELECTMULTI keyword
CONVERTV command 37
COPY command 55
DUMP command 101
separator
definition 1
SERIAL command 177
serialization
data integrity 241
ENQ keyword 243
lockout, avoiding 242
Read/Write scheme 245
RESERVE macro 241
resource 247
SET command 179, 190
setting condition codes 179
SHARE keyword
COPY command 63
DUMP command 106
PRINT command 121
RESTORE command 159
SIZE keyword 7
334
SMS authorization 223

SMS keyword
CONVERTV command 37
SMS-managed data sets 215
SMSGCNT keyword 7
Snapshot 48
CC-compatible 96
RVA 96
software requirements for Stand-Alone Services 203
SOURCE subkeyword of TGTALLOC
COPY command 65
RESTORE command 161
SOURCE subkeyword of TGTGDS
COPY command 65
RESTORE command 161
source, definition 6
space allocation 65, 161
space fragmentation on DASD 82
space utilization, percent
COPY command 59
RESTORE command 154
SPECIAL attribute 207
SPHERE keyword
COPY command 63, 132
DUMP command 106
RESTORE command 160
Stand-Alone Services feature 23, 185
370 mode operation 186
benefits 185
building a Stand-Alone Services IPL-able core
image 23
BUILDSA command 23
ADMINISTRATOR parameter 24, 203
determining authorization level 202
examples 26
INDDNAME parameter 24
IPL parameter 24
OPERCNSL parameter 25
optional parameters 24
OUTDDNAME parameter 26
OUTDYNAM parameter 26
required parameters 23
syntax 23
card readers supported 204
command sequence processing 190
commands
BUILDSA 23
RESTORE 196
TAPECNTL 201
consoles supported 204
controlling command sequence processing 190
core image 23
definition of 21, 202
specifying information for 24
specifying the JCL output location for 26
specifying the output DASD volume 26
Stand-Alone Services feature (continued)

DASD
devices in 370 mode 186
devices in XA or ESA mode 186
supported devices 203, 205
target device address, specifying 197
determining BUILDSA command authorization
level 202
dump data set
device address, specifying 197
device type, specifying 197
duplicate volser considerations 136
EC mode operation 185
ESA mode operation 186
examples
BUILDSA command 26
copying the Stand-Alone Services core image 27
IPL 193
RESTORE command 199
TAPECNTL command 202
extended control (EC) mode 185
hardware and software requirements 203
IF-THEN-ELSE command 190
input devices for RESTORE command 204
interference from other devices 186
introduction 185
IPL devices 203
IPLing on a stand-alone system 192
IPLing with a tape library 188
message data devices 204
operator console
potential problems 187
predefining 186, 187
optional parameters
BUILDSA command 24
RESTORE command 198
predefined console
potential problems with 195
purpose of 187
preparing for 21, 202, 203
printers supported 204
procedure to IPL Stand-Alone Services on
stand-alone system 192
procedures to mount and demount tapes using tape
libraries 189
process overview 190
processors supported 203
PSW wait-state codes 194
purpose 185
real storage requirements 185
receiving volume (DASD) 205
required parameters
BUILDSA command 23
RESTORE command 197
RESTORE command
description 196

RESTORE command (continued)
ENDTRK parameter 198
example 199
FILE parameter 199
FROMADDR parameter 197
FROMDEV parameter 197
FULL parameter 198
input devices 204
NOREADCHECK parameter 199
NOVERIFY parameter 197
optional parameters 198
READCHECK parameter 198
STARTTRK parameter 198
syntax 197
TAPEVOLSER parameter 199
TOADDR parameter 197
VERIFY parameter 197
restoring with a tape library 188
rewinding a tape with the TAPECNTL
command 201
running in 370 mode 186
running in XA or ESA mode 186
running the program 190
running with a predefined console 187
security levels for BUILDSA command 202
selecting the operator console 192
setup Stand-Alone device feature 188
source tape devices 205
specifying
information for the Stand-Alone Services core
image 24
the DASD target device address 197
the date and time 193
the dump data set device address 197
the dump data set device type 197
the input device 192
the JCL output location for IPL-able core
image 26
the message output device 192
the output DASD volume for IPL-able core
image 26
where Stand-Alone Services is IPLed from 23
supported devices 203
supported platforms 185
supported processors 203
syntax
BUILDSA command 23
RESTORE command 197
SYS1.ADR.SAIPLD.Vvolser data set 23
SYS1.SADRYLIB target library 23
System Modification Program (SMP) 23
System Modification Program Extended (SMP/E) 23
system requirements 203
Index
335

tape (source devices) 205
tape library
setup Stand-Alone device feature 188
transient mount feature 188
tape mount and demount procedures 189
TAPECNTL command
description 201
DEVTYPE parameter 201
example 202
REWIND parameter 201
rewinding 201
syntax 201
UNITADDR parameter 201
UNLOAD parameter 201
unloading 201
transient mount feature 188
using a tape library 188
using an automatic cartridge loader 190
VM, running under 186
wait-state codes 194
with a tape library 188
with an automatic cartridge loader 190
XA mode operation 186
standard catalog search order 19
standard naming conventions 213
STARTTRK parameter (Stand-Alone RESTORE
command) 198
startup
function, eioption 00 264
status assignment, GDG data sets 65, 161
STEPCAT DD statement, JCL 5
storage administrator 216
storage requirements for Stand-Alone Services program
operation 185
STORCLAS keyword 15
COPY command 64
RESTORE command 160
STORCLAS profile 215
STORGRP keyword
COPY command 64
DUMP command 106
RELEASE command 133
structure, exit interface 259
subkeywords 2
maximum number 2
multiple 2
specifying 2
supported
devices for Stand-Alone Services 203
platforms for Stand-Alone Services 185
processors for Stand-Alone Services 203
suppressing page ejection 7
switching modes 178
336
syntax diagram 1
CONVERTV command 34
COPY command 40
COPYDUMP command 80
DEFRAG command 82
DUMP command 90
PRINT command 117
RELEASE command 125
RESTORE command 136
SYS1 subkeyword
COPY command 60
DUMP command 104
RELEASE command 132
SYSIN DD statement, JCL 5
SYSIN record
reading eioption 01 264
SYSPRINT DD statement, JCL 5
SYSPRINT record
printing, eioption 02 265
SYSPRINT utility
reading, eioption 09 267
system authorization facility 207
See also SAF
system programming information 259
system requirements for Stand-Alone Services
203
T
tape devices (with Stand-Alone Services)
in 370 mode 186
in XA or ESA mode 186
supported models 205
tape libraries (with Stand-Alone Services)
not supported in 370 mode 186
supported 204, 205
tape mount and demount procedures 189
tape record
logical, reading, eioption 04 266
logical, writing, eioption 05 266
physical, reading, eioption 03 265
physical, writing, eioption 06 266
tape volume mount
OPEN/EVOC nonspecific, eioption 17 269
tape volume security
OPEN/EOV, eioption 16 269
TAPEVOLSER parameter (Stand-Alone RESTORE
command) 199
target allocation 65, 161
target class selection 168
target definition 6
task processing, controlling 178
TASK-ID 260
temporary copied catalogs 214
temporary data set 214
DEFRAG data set 213
temporary data set (continued)

message data set 213
names 213
TEST keyword
CONVERTV command 37
TGTALLOC keyword
COPY command 65
RESTORE command 161
TGTGDS keyword
COPY command 65
RESTORE command 161
THEN command 180
TMPMSGDS keyword 8
TOADDR parameter (Stand-Alone RESTORE
command) 197
TOLERATE keyword
COPY command 66
DUMP command 107
PRINT command 121
RESTORE command 162
TRACE keyword 8
track overflow support 237
TRACKS keyword
COPY command 67
DUMP command 108
PRINT command 121
RESTORE command 162
tracks read at a time, on dump 102
TRK subkeyword of TGTALLOC
COPY command 65
RESTORE command 161
TTRAddress keyword
COPY command 67
RESTORE command 163
TYPRUN keyword 8
U
UAPTR parameter 256
UIMPTR parameter 256
UNCATALOG keyword
COPY command 68
DUMP command 108
UNDEFINEDSORG subkeyword
COPY command 60
RESTORE command 155
UNITADDR parameter (Stand-Alone TAPECNTL
command) 201
UNLOAD parameter (Stand-Alone TAPECNTL
command) 201
unloading a tape with the TAPECNTL command 201
User Area Pointer 263
User Exit Allowance 260
user interaction module (UIM) 258
example 291, 303
sample output 304, 305
user interaction module list 256

User Return Code 260
user-area list 256
utilization, percent
COPY command 59
RESTORE command 154
UTILMSG keyword 8
V
VALIDATE keyword
DUMP command 109
variable length (VL) parameter 257
verification
bypass exit, eioption 22 271
data set, eioption 21 270
verification exit
OPEN/EOV, eioption 16 269
VERIFY parameter (Stand-Alone RESTORE
command) 197
versions of DFDSS, compatibility 237
VL parameter 257
VM, running Stand-Alone Services under 186
VOLCOUNT keyword
COPY command 68
RESTORE command 163
volume
DUMP with concurrent copy 111
serialization 241
volume count subparameter, JCL 6
volume notification
eioption 20 270
VSAM (Virtual Storage Access Method)
catalog access authority 222
data set
filtering 11
restore actions on 166
VTOC
entry (data-set-changed flag) 105
VTOC keyword
PRINT command 122
W
WAIT keyword 70
COMPRESS command 33
COPY command 70
DEFRAG command 87
DUMP command 109
PRINT command 122
RELEASE command 133
RESTORE command 165
wait-state codes for Stand-Alone program
WORKUNIT keyword 8
194
Index
337
WORKVOL keyword 8
WRITECHECK keyword
COPY command 70
DEFRAG command 87
RESTORE command 166
writing disk track
eioption 08 267
writing logical tape record
eioption 05 266
writing physical tape record
eioption 06 266
writing SYSPRINT record
eioption 10 267
writing to the operator 177
writing WTO message
eioption 11 268
writing WTOR message
eioption 12 268
WTO command 177
WTO message
WTOR message
WTOR response
presenting, eioption 15 269
X
XABUFF keyword
338
Readers' Comments We'd Like to Hear from You

Reference
Publication No. SC26-4929-04
Overall, how satisfied are you with the information in this book?
Very
Satisfied
Satisfied
Neutral
Dissatisfied
Very
Dissatisfied
Very
Satisfied
Satisfied
Neutral
Dissatisfied
Very
Dissatisfied
Overall satisfaction
How satisfied are you that the information in this book is:
Accurate
Complete
Easy to find
Easy to understand
Well organized
Applicable to your tasks
Please tell us how we can improve this book:
Thank you for your responses. May we contact you? Yes No

When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments
in any way it believes appropriate without incurring any obligation to you.
Name
Company or Organization
Phone No.
Address
Readers' Comments We'd Like to Hear from You

SC26-4929-04
Fold and Tape
Please do not staple
IBM
Cut or Fold
Along Line
Fold and Tape
NO POSTAGE
NECESSARY
IF MAILED IN THE
UNITED STATES
BUSINESS REPLY MAIL

FIRST-CLASS MAIL
PERMIT NO. 40
ARMONK, NEW YORK
POSTAGE WILL BE PAID BY ADDRESSEE
International Business Machines Corporation

Information Development
Department 61C
9000 South Rita Road
TUCSON AZ 85775-4401
Fold and Tape
SC26-4929-04
Please do not staple
Fold and Tape
Cut or Fold
Along Line
IBM
Program Number: 5695-DF1

5647-A01
Printed in the United States of America
on recycled paper containing 10%
recovered post-consumer fiber.
SC26-4929-4

DFSMSdss Storage Administration Manual

Uploaded by

Copyright:

Available Formats

DFSMSdss Storage Administration Manual

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

DFSMSdss Storage Administration Manual

Uploaded by

Copyright:

Available Formats

DFSMS/MVS Version 1 Release 5