MVS/370 Utilities

\,., J

Program Product

GC26-4065-1 File No. S370-32

MVS/370 Utilities

Data Facility Product 5685-295

Release 1.1

TNL GN26-8133 (30 Mar 84) to GC26-4065-1

Second Edition (October 1983)

This edition, as amended by technical newsletter GN26-8133, applies to Release 1.1 of MVS/370 Data Facility Product, Program Product 5665-295, and to any subsequent releases until otherwise

indicated in new editions or technical newsletters.

The changes for this edition are summarized under "Summary of Amendments" following the preface. Specific changes are

indicated by a vertical bar to the left of the change. These bars will be deleted at any subsequent republication of the page affected. Editorial changes that have no technical significance are not noted.

Changes are made periodically to this publication; before using this publication in connection with the operation of IBM

systems, consult the latest IBM System/370 and 4300 Processors Bibliography, GC20-0001, for the editions that are applicable and current.

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 program product in this publication is not intended to state or imply that only IBM's program product may be used. Any

functionally equivalent program may be used instead.

Publications are not stocked at the address given below;

requests for IBM publications should be made to your IBM representative or to the IBM branch office serving your locality.

A form for readers' comments is provided at the back of this publication. If the form has been removed, comments may be addressed to IBM· Corporation, P.O. Box 50020, Programming

Publishing, San Jose, California, U.S.A. 95150. IBM may use or distribute whatever information you supply in any way it

believes appropriate without incurring any obligation to you.

e

Copyright International Business Machines Corporation 1983

PREFACE

ORGANIZATION

This publication describes how to use the MVS/370 Data Facility Product (MVS/370) utility programs to manipulate system and user data and data sets.

This publication contains the following major parts:

• "Introduction" summarizes the utility programs and

information on the differences among system, data set, and independent utility programs. The introduction contains basic information about how the programs are executed and about the utility control statements used to specify program functions. New or infrequent users of the utility programs should give particular attention to the introduction.

• "Guide to Utility Program Functions" contains a table, arranged in alphabetic order, of utility program functions and the programs that perform them. This table enables you to find the program that can do what you need to have done.

• "Invoking Utility Programs from a Problem Program" contains a description of the macro instructions used to invoke a utility program from a problem program rather than executing the utility program by job control statements or by a

procedure in the procedure library. This section should be read only if you plan to invoke a utility program from a problem program.

• The remainder of the book contains individual chapters for each utility program arranged in alphabetic order. For a discussion of the organization of these chapters, see

"Organization of Program Descriptions" on page iv.

• Appendix

A,

"Exit Routine Linkage" contains information about linking to and returning from optional user-supplied exit routines. This appendix should be read only if you plan to code or use an exit routine. If you are coding an exit routine, this appendix provides linkage conventions, descriptions of parameter lists, and return codes. If you are using an existing exit routine, you may be interested in the meaning of return codes from the exit routine.

• Appendix B, "DD Statements for Defining Mountable Devices"

contains a review of how to define mountable volumes to ensure that no one else has access to them. For a

definitive explanation of this subject, see the publication OS/VS2 MVS JCL.

• Appendix C, "Processing User Labels" describes the user-label processing that can be performed by IEBGENER, IEBCOMPR, IEBPTPCH, IEHMOVE, and IEBUPDTE. This appendix should be read only if you plan to use a utility program for processing user labels.

ORGANIZATION OF PROGRAM DESCRIPTIONS

To enable you to find information more easily, program

descriptions are all organized, as much as possible, in the same way. Most programs are discussed according to the following pattern:

• Introduction to and description of the functions that can be performed by the program. This description typically

includes an overview of the program's use, definitions of terms, illustrations, etc.

• Functions supported by the utility and the purpose of each function.

• Input and output (including return codes) used and produced by the program.

• Control of the program through job control statements and utility control statements. Explanations of utility control statement parameters are presented in alphabetic order in tabular format, showing applicable control statements, syntax, and a description of the parameters. Any general information, restrictions, and relationships of a given utility control statement to other control statements are described in the sections concerning the statements or in the section for restrictions.

• Examples of using the program, including the job control statements and utility control statements.

PREREQUISITE KNOWLEDGE

In order to use this book efficiently, you should be familiar

wi~h the foiiowing;

• Job control language

• Data management

• Virtual storage management REQUIRED PUBLICATIONS

You should be familiar with the information presented in the following publications:

• MVS/370 Utilities Messages contains a complete listing and explanation of the messages and codes issued by MVS/370 utility programs.

• OS/VS2 MVS JCL contains a description of the use and coding of the job control language.

• MVS/370 Data Management Services describes the input/output facilities of the operating system. It contains information on record formats, data set organization, access methods, data set disposition, space allocation, and generation data sets.

• MVS/370 Data Management Macro Instructions contains contains a description of the WRITE macro instruction; it also

contains the format and contents of the DCB.

• OS/VS2 MVS System Programming Library: Supervisor Services and Macro Instructions contains contains information on how to use the services of the supervisor. Among the services of the supervisor are program management, task creation and management, and virtual storage management.

iv MVS/370 Utilities

PREFACE

)

ORGANIZATION

TNL GN26-8133 (30 Mar 84) to GC26-4065-1

This publication describes how to use the MVS/370 Data Facility Product (MVS/370) utility programs to manipulate system and user data and data sets.

This pUblication contains the following major parts'

• "Introduction" summarizes the utility programs and

information on the differences among system, data set, and independent utility programs. The introduction contains basic information about how the programs are executed and about the utility control statements used to specify program functions. New or infrequent users of the utility programs should give particular attention to the introduction.

• "Guide to Utility Program Functions" contains a table, arranged in alphabetic order, of utility program functions and the programs that perform them. This table enables you to find the program that can do what you need to have done.

• "Invoking Utility Programs from a Problem Program" contains a description of the macro instructions used to invoke a utility program from a problem program rather than executing the utility program by job control statements or by a

procedure in the procedure library. This section should be read only if you plan to invoke a utility program from a problem program.

• .The remainder of the book contains individual chapters for each utility program arranged in alphabetic order. For a discussion of the organization of these chapters, see

"Organization of ,Program Descriptions" on page iv.

• Appendix A, "Exi~ Routine linkage" contains information about linking to and returning from optional user-supplied exit routines. This appendix should be read only if you plan to code or use an exit routine. If you are coding an exit routine, this appendix provides linkage conventions, descriptions of parameter lists, and return codes. If you are using an existing exit routine, you may be interested in

the meaning of return codes from the exit routine.

• Appendix B, "DD Statements for Defining Mountable Devices"

contains a review of how to define mountable volumes to ensure' that no one else has access to them. For a

definitive explanation of this subject, see the pUblication OS/VS2 MVS JCL.

• Appendix C, "Processing User Labels" describes the user-label processing that can be performed by IEBGENER, IEBCOMPR, IEBPTPCH, IEHMOVE, and IEBUPDTE. This appendix should be read only if you plan to use a utility program for processing user labels.

ORGANIZATION OF PROGRAM DESCRIPTIONS

To enable you to find information more easily, program

descriptions are all organized, as much as possible, in the sa ••

way. Most programs are discussed according to the following pattern'

• Introduction to and description of the functions that can b.

performed by the program. This description typically includes an overview of the program's use, definitions of terms, illustrations, etc.

• Functions supported by the utility and the purpose of .ach function.

• Input and output (including return codes> used ~nd produced by the program.

• Control of the program through job control statements and utility control statements.. Explanations of utility control statement parameters are presented in alphabetic order in tabular format, showing applicable control statements, . syntax, and a description of the parameters. Any general information, restrictions, and relationships of a given utility control statement to other control statements are described in the sections concerning the statements or in the section for restrictions.

• Examples of using the program, includ1ng the job control statements and utility control statements.

PREREQUISITE KNOWLEDGE

In order to use this book efficiently, you should be familiar with the following'

• Job control language

• Data management

• Virtual storage management

REQUIRED PUBLICATIONS

You should be familiar with the information presented in the following publicationsl

• MVS/370 Utilities Messages contains a complete listing and explanation of the messages and codes issued by MVS/370 utility programs.

• OS/VS2 MVS JCl contains a description of the use and coding of the job control language.

• MVS/370 Data 'Management Services describes the input/output facilities of the operating system. It contains information on record formats, data set organization, access methods, data set disposition, space allocation, and generation data sets.

• MVS/370 Data Management Macro Instructions contains a

description of the WRITE macro instructionJ it also contains the format and contents of the DCB.

• OS/VS2 MVS Supervisor Services and Macro Instructions contains information on how to use the services of the supervisor. Among the services of the supervisor are program management, task creation and management, and virtual storage management.

iv MVS/370 Utilities

\

RELATED PUBLICATIONS

TNL GN26-8133 (30 Mar 84) to GC26-4065-1

Within the text, references are made to the publications listed in the table below.

Short Title publication Title Order Numb.r

Catalog Users ~VS/~70 Catalog User:l ^~y;dg GC26-4053 Guide

Data Facility Dati ^Facilit~ Data Saj; SC26-3949 Data Set ^Servi~es: User's Guidg aDd

Services: Referencg User's Guida

and Reference

Debugging OS/VS2 MVS S~stem GC28-1047

Handbook frogramming librar~: GC28-1048 Debugging Handbook, Volumes GC28-1049

1 through 3

Device Support Device ~ueeort FacilitiBI GC3S-0033 Facilities User's ~uide and Referen~g

User's Guide and Reference

Linkage Editor ^~VS/370 Linkage Editor !nd GC26-4061 and Loader loader

Same IBM 3800 Printing Subs~sj;em GC26-3846 Programmer's Guide

Same IBM 50 Magnetic Data GA27-2725

Inscriber Comeonent Descrietion

Utilities MVS/370 Utilities Message:! GC26-4068 Messages

JCL OS/VS2 MVS JCl GC28-0692

Data Management MVS/370 Data Managemenj; GC26-4057 Macro ftlacro Instructions

Instructions

Supervisor OS/VS2 MVS Sueervisor GC28-0683 Services and Services and Macro

Macro Instructions

Instructions

Same Reference Manual for tbl GA26-1653 IBM 3800 Printing Subs~stem

System MVS/370 ^S~stem Programming GC26-4056 Programming librar~: Data Management

Library: Data Management

VSAM Users MVS/370 VSAM Users Guidg GC26-4066 Guide

UTILITIES NOT IXPLAINID IN THIS BOOK

utility I DCAMS

Device Support Facilities

Data Facility Data Set Services

Offline IBM 3800 Utility

There ara several specialized utilities not discussed in this book. The following list shows their names and functions. and indicates which book contains their explanation.

Function Reference

Allows users to define. manipulate,

~VS/~Zg ~lil!gS

U&.C.

or delete VSAM data sets, define Guide, GC26- 053 and manipUlate VSAM catalogs, and

copy, print. or convert SAM and ISAM data sets to VSAM data sets.

Used for the initialization and

~iUf!~r:~:~;:!oI'

maintenance of DASD volumes.

GC3S-0033

Describes DASD utility functions

~ i

F "I"! ^D it!

such as dump/restore and reduction ::r:lc::~ ~:~t!: IY:~:

of free space fragmentation and B!flteDSCI, SC26-3949

Describes the Offline IBM 3800 Offlin! lin

~Igg

Utility program, used with the IBM Utility, S 20-9138 3800 Tape-to-Printing Subsystem

Feature.

vi MVS/370 Utilities

TNL GN26-8133 (30 Mar 84) to GC26-4065-1

SUMMARY OF AnENpnENTS

RELEAIE 1,1 UPPATE. nARCH 1984

NEW DEVICE SUPPORT

• IBM 4248 Printer

The FCB statement in IEBIMAGE can now be used to create forms control buffer modules in a form appropriate for use on the IBM 4248 Printer. Information to support the 4248 has been added to the IEBIMAGE chapter.

• IBM 3262 Model 5 Printer

Information to support the IBM 3262 Model 5 Printer has been added to the IEBIMAGE chapter.

RELEASE 1,1, OCTOBER 1983

NEW DEVICE SUPPORT

• IBM 4245 Printer

Information to support the IBM 4245 Printer has been added to the IEBIMAGE chapter.

• IBM 3800 Printing Subsystem Model 3

The IBM 3800 Printing Subsystem Model 3 is supported by IEBIMAGE in full function mode.

NEW PROGRAMMING SUPPORT

• IEBCOPY Enhancements

IEBCOPY can now be used to alter and copy load modules.

Information to support the altering and copying functions, including the new AlTERMOD and COPYMOD statements, has bean added to the IEBCOPY chapter.

• IEHMOVE Enhancements

When used to move or copy sequential data sets on DASD, IEHMOVE now uses multiple BSAM buffers to improve

performance. Information to support multiple buffers has been added to the IEHMOVE chapter.

CQNTINI'

TNL GN26-8133 (30 Mar 84) to GC26-4065-1

Introduction • • • • • • • • • • • • •

• • • • • •

•

• • •

System utility Programs . . • •

Data Set Utility Programs . • • . Independent Utility Programs

DASD and Tape Device Support Control . . . • . . .

Job Control Statements .

Utility Control Statements • • • • • • • • • Continuing Utility Control Statements

Restrictions . . . Notational Conventions

keyword=device=list . • • . Installation Considerations

Special Referencing Aids

Guide to utility Program Functions . . . . . . · . . . . .

Invoking utility Programs from a Problem Program

LINK or ATTACH Macro Instruction

• • • • •

LOAD Macro Instruction

CALL Macro Instruction

ICAPRTBL Program • • • • • • • • • • • • • • Executing ICAPRTBL . . • . • • • • . Input and Output . . • . . . • •

Control . . . • . . . Utility Control Statements

JOB Statement DFN Statement UCS Statement FCB Statement END Statement

• • • • • • •

ICAPRTBL Examples ICAPRTBL Example 1 ICAPRTBL Example 2 ICAPRTBL Example 3 ICAPRTBL Example 4

.

^"

.

IEBCOMPR Program

Input and Output . . .

• • • • • • • • • • • •

Return Codes . . • • • • • • . • • • • Control . . • •

Job Control Statements • • • • • Utility Control Statements • • • .

COMPARE Statement • . • . • . • • • EXITS Statement . . • • • • • . LABELS Statement . • • • • • . • • . •

IEBCOMPR Examples • • • .

IEBCOMPR Example 1 • • • •

IEBCOMPR Example 2 . • • • • • IEBCOMPR Example 3

IEBCOMPR Example 4 IEBCOMPR Example

S

IEBCOMPR Example 6 IEBCOMPR Example 7

• • • • • •

IEBCOPY Program • • • • • • • • • • • • • • • • • • • • • Creating a Backup Copy • • • • • . • • • • • • Copying Data Sets . • . • . • • • . • • • • •

Copying or Loading Unloaded Data Sets • • . • • Selecting Members to be Copied, Unloaded, or Loaded

Copying Members That Have Alias Names

1 1 1 2 3 4 4 4 5 5 5 6 6 6 8 13

13

15 16

18

18

19 19 19

20

20 20

21 21

23 24

24

2S 2S 27

28

28 28

29

30

30 30

31 32

33

34

34

3S

36 36

37 39 39

40 40

40 41

Re-creating a Data Set • . • • • • • Altering Load Modules in Place ••

Copying and Reblocking Load Modules

Load Module Requirements • • • • • Inserting RLD Counts . • • • • • • • • Input and Output . • • .

Return Codes . . . .

Control . . . • . . • • •

Job Control Statements • . . • . • • • • PARM Information on the EXEC Statement SYSPRINT DD Statement • . • • anynamel and anyname2 DD Statements SYSIN DD Statement • . . . • . •

IEBCOPY Unloaded Data Set Block Size • • • • • Space Allocation • • • • • • • Restrictions . . . • • • • • • • • • Utility Control Statements • • • • • • • • •

COpy Statement . ALTERMOD Statement COPYMOD Statement SELECT Statement EXCLUDE Statement IEBCOPY Examples

IEBCOPY Example 1 IEBCOPY Example 2 IEBCOPY Example 3 IEBCOPY Example 4 IEBCOPY Example 5 IEBCOPY Example 6 IEBCOPY Example 7 IEBCOPY Example 8 IEBCOPY Example 9 IEBCOPY Example 10 IEBCOPY Example 11 IEBCOPY Example 12 IEBCOPY Example 13 IEBCOPY Example 14 IEBCOPY Example 15 IEBCOPY Example 16 IEBCOPY Example 17 IEBCOPY Example 18

IEBDG Program • • • • • • • • • • • • • • • • •

_{• •}

Types of Patterns .

IBM-Supplied Patterns . . . • . User-Specified Pictures . • Modification of Selected Fields Input and Output

Return Codes . . . . • • • •

Control . . . • . . . • • Job Control Statements • • • . • •

PARM Information on the EXEC Statement SYSPRINT DD Statement

SYSIN DD Statement seqinset DD Statement parinset DD Statement seqout DD Statement parout DD Statement . Utility Control Statements

DSD Statement FD Statement • CREATE Statement REPEAT Statement END Statement IEBDG Examples

IEBDG Example 1 IEBDG Example 2 IEBDG Example 3 IEBDG Example 4 IEBDG Example 5 IEBDG Example 6 IEBDG Example 7

. . ..

.. .

• • •

IEBEDIT Program

• • • • • • • • • • • • • • • • • • • •

x MVS/370 Utilities

43 43 44 43

45 45

46 46 46 46 46 47 48 48

49

50 50 51 53

54

55 56 60 62 63 65 67 69 71 74 76 78

79

81 85 91 92 92

94

95 96

97 97 97 98

100

99

100 100

101 102

102 102

102 103

103 103

104 104

105 107

110 110

121 121

122 123

127 125

128 129

131

TNL GNZ6-8133 (30 Mar 84) to GC26-4065-1 Input and Output

Return Codes . • • •

Control . •

Job Control Statements • • • • utility Control Statement • • • • •

EDIT Statement . • • • IEBEDIT Examples

IEBEDIT Example 1 IEBEDIT Example 2 IEBEDIT Example 3 IEBEDIT Example 4 IEBEDIT Example

S

IEBEDIT Example

6

JEBGENER Program • • • • • • • • • • • • • • • • • • • • Creating a Backup Copy . • . • • • . • • • • • • • • • Producing a Partitioned Data Set from Sequential Input Expanding a Partitioned Data Set • • • • • • • • • Producing an Edi ted Data Set • . • . • • • • • • • Reblocking or Changing Logical Record Length • • • • • Input and Output • • • • . • • • • • • • •

Return Codes . . . • . • • • Control . . . . .

Job Control Statements SYSPRINT DD Statement

SYSUT1 DD Statement . . • • . . • • • • • SYSUT2 DD Statement • • • . . • • • • SYSIN DD Statement . • • • • • Utility Control Statements . • • • •

GENERATE Statement • • • • EXITS Statement

LABELS Statement MEMBER Statement RECORD Statement IEBGENER Examples

IEBGENER Example 1 IEBGENER Example 2 IEBGENER Example 3 IEBGENER Example 4 IEBGENER Example

S

IEBGENER Example

6

IEBGENER Example

7

IEBGENER Example 8 IEBGENER Example

9

IEBGENER Example 10 . . . . .

JEBJMAGE Program • • • • • • • • • • • • • • • • • • • • General Information . . • • • • • • • • • • • • •

Storage Requirements . • • • • •

For IEBIMAGE . . . • • • • • • • • For SYSl.IMAGELIB • . . . • • . • • • • • • • • • • Maintaining the SYS1.IMAGELIB Data Set • • • • General Module Structure . • • • • • • • • Naming Conventions for Modules • • • • . • • • • • Using IEBIMAGE . . . • • • . • • •

Creating a Forms Control Buffer Module 3800 FCB Module Structure

4248 FCB Module Structure

FCB Module Listing . . . •

Creating a COpy Modification Module • • • •

COPYMOD Module Structure • • • •

COPYMOD Module Listing . • .. • • • • • • • • Creating a Character Arrangement Table Module • • • •

TABLE Module Structure • • • • • • • • . • • • • • • TABLE Module Listing • . • • • • • . . • •

Creating a Graphic Character Modification Module GRAPHIC Module Structure • • • • • • • • • • GRAPHIC Module Listing. • . • • • • • • • • • •

131 131

132 132

133 133

136 135

137 136

138 139

139

141 141

141 142

143 144

144 145

145 145

145 145

146 147

148 147

149 148

150 149

157 158

158 159

159 160

160 161

.162

163 165

166 166

166 166

168 167

170 169

170 170

171 171

172.1

173 173

174 174

175 176

178 178

179

TNLGN26-8133 (30 Mar 84) to GC26-406S-1 Job Control Statements

SYSPRINT DD Statement SYSUTI DD Statement

SYSIN DD Statement • . • • • . Utility Control Statements

Operation Groups FCB Statement COPYMOD Statement TABLE Statement GRAPHIC Statement CHARSET Statement INCLUDE Statement NAME Statement OPTION Statement

Using OVERRUN

IEBIMAGE Examples • . • . • • . . • . . • • • • • • •

xii MVS/370 Utilities

Example 11 Building a New 3800 Forms Control Buffer Module . . . . . . .

3800 Modell. . . • . . . • . . • . • Example 21 Replacing a 3800 Forms Control Buffer Module 3800 Modell. . . • . • . • . • • Example 31 Replacing a 3800 Forms Control Buffer Module 3800 Modell. . . • • Example 41 Building a New 3800 Forms Control Buffer

Module . . . . • . . . • . • 3800 Modell. . . • . . • Example 51 Replacing the 3800 Forms Control Buffer

Module STD3 . . . . . . • . . . • • . • • . 3800 M o d e l l . . . . • . • . . • • • • • . Example 61 Building a New 3800 Forms Control Buffer

Module for Additional ISO Paper Sizes . . • • • • 3800 Model 3 . . . • • • . • • • Example 6A: Building a 4248 Forms Control Buffer Module Example 71 Building a New COpy Modification Module

3800 M o d e l l . . . • . • • . . • . Example 81 Building a New COpy Modification Module From

an Existing Copy . . • • . . . . • • . . • • • 3800 Model 3 . . . • . . • • • . Example 9: Adding a New Character to a Character

Arrangement Table Module . . . . • • . • • • .

3800 Model 3 . . . • • . . • . • • . • • • • • Example 101 Building a New Character Arrangement Table

Module From an Existing COpy . • . . • . • • • • • • 3800 Model 3 . . . • . • • . . • • • • Example 11: Building Graphic Characters in a Character

Arrangement Table Module • . . . • • . • • • 3800 Modell . . • . . . • . . • . • . • Example 121 Deleting Graphic References From a Character

Arrangement Table Module . . . • • • • 3800 Model 3 . . . . Example 131 Listing the World Trade National Use

Graphics Graphic Character Modification Module

3800 Modell. . . • • • • • • Example 141 Building a Graphic Character Modification

Module From the World Trade GRAFMOD . . . . • .

3800 Model 3 . . . • • • • • • Example 151 Building a New Graphic Character

Modification Module and Modifying a Character

Arrangement Table to Use It . . . • . • • • 3800 Model 3 . . . • . • • Example 161 Building a Graphic Character Modification

Module From Multiple Sources . . . . . • . . • • 3800 Modell. . . • . • Example 171 Defining and Using a" Character in a Graphic Character Modification Module . . . . . . . • • •

3800 Model 3 . . . • • • Example 18: Listing a Library Character Set Module

3800 Modell. . . • . . . • Example 191 Building a Library Character Set Module

3800 Model 3 . . . . • • . . . • . • . . • Example 20: Building a Library Character Set Module and

Modifying a Character Arrangement Table to Use It 3800 Model 3 . . . • . . • . . . • •

184 184 185 185 185 185 186 187 188 189 190 191 191 191 208.1 192 209 209 210 210 210 210 211 211 212 212 213 213 214.1 214 214.1 215 215 216 216 216 216 217 217 218 218 219 219 219 219

220 220 222 222 223 223 226 226 226 226 227 227

)

TNL GN26-8133 (30 Mar 84) to GC26-4065-1 Example

21s

Building a Library Character Set Module From

Multiple Sources . . . . . . • . . . • • • • 3800 Model I . . . • • . • • • • JEBJSAM Program • • • • • • • • • • • • • • • Copying an ISAM Data Set . . . . • • . . • • • • Creating a Sequential Backup Copy • • • • Overriding DCB Control Information . . . . • • • Creating an ISAM Data Set from an Unloaded Data Set Printing the Logical Records of an ISAM Data Set Input and Output . . . .

Return Codes . . . . Control . . . .

Job Control Statements . . . . . PARM Information on the EXEC Statement IEBISAM Examples . . . .

IEBISAM Example I . . . . IEBISAM Example 2

IEBISAM Example 3 IEBISAM Example 4

IEBISAM Example

5

. .

^...

. ^'. .

JEBPTPCH Program ••

Printing or Punching Printing or Punching . Printing or Punching Printing or Punching Printing or Punching Input and Output

. . . . . . . . . . . .

Return Codes Control

an Entire Data Set

Selected Members . • • . . . • • Selected Records . • . • • • • • a Partitioned Directory • . • • • an Edited Data Set

Job Control Statements SYSPRINT DD Statement SYSUTI DD Statement SYSUT2 DD Statement

SYSIN DD Statement . .

Utility Control Statements . . . • . PRINT Statement . . . • . PUNCH Statement . . . . TITLE Statement

EXITS Statement MEMBER Statement RECORD Statement LABELS Statement IEBPTPCH Examples

IEBPTPCH Example I IEBPTPCH Example 2 IEBPTPCH Example 3 IEBPTPCH Example

4

IEBPTPCH Example

5

IEBPTPCH Example 6 IEBPTPCH Example

7

IEBPTPCH Example 8 IEBPTPCH Example

9

IEBPTPCH Example,IO

JEBTCRIN Program • • • • • • • • • • • • • • • • • • • • MTDI Editing C r i t e r i a . . . . •

MTDI Editing Restrictions . . • • Special Codes . . . . . . . . • •

End-of-Cartridge . . . . . . • • • • • • • • • Error Records . . . . • . • • • • • • • • Error Description Word (EDW) . . . • • • • • • • • Sample Error Records . . • . • • • • • Input and Output . . . .,. • • • • •

Return Codes . . . • • . • • • • Control . . . . • • • •

Job Control Statements

229 229

231

231

231 232

233 233

234 235

'235

236 235

237 238

238 239

239 240

241

241

241 242

242 242

242 242

243 243

244 244

244 244

244 245

246 246

246 247

247 248

258 258

259 260

260 261

262 263

264 264

266

267

267

268 269

273 274

274 277

279 279

280 280

EXITS Statement IEBTCRIN Examples

IEBTCRIN Example 1 IEBTCRIN Example 2

IEBUPDTE Program • • • • • • • • • • • • • • • • • •

Creating and Updating Data Set Libraries

Modifying an Existing Data Set Changing Data Set Organization Input and Output . . . .

Return Codes . . . • . . Control . . . .

Job Control Statements . . . • • . PARM Information on the EXEC Statement

SYSPRINT DD Statement • . • . . . • • SYSUTI DD Statement . . . • . • •

SYSUT2 DD Statement . . •• • • • • SYSIN DD Statement . . . • . • . . • • Utility Control Statements . . • . • .

Function Statement . . . • • . • • • Function Restrictions • • • • •

Detail Statement . • • . . . . • • • • Detail Restrictions • . • . • • • • • •

Data Statement . • • • •

LABEL Statement . . . . ALIAS Statement . • . .

ENDUP Statement . . . • . IEBUPDTE Examples . . . • . . • • .

IEBUPDTE Example 1 . . • . IEBUPDTE Example 2 . . . • . • IEBUPDTE Example 3 . . . . IEBUPDTE Example 4 . . • . IEBUPDTE Example 5 . . . . IEBUPDTE Example 6

IEBUPDTE Example 7 IEBUPDTE Example 8 IEBUPDTE Example 9 IEBUPDTE Example 10 IEBUPDTE Example 11

IEHATLAS Program

Input and Output

Return Codes

Control . • .

. . .

Job Control Statements . Utility Control Statements

. . .

TRACK Statement . . . . VTOC Statement

IEHATLAS Examples IEHATLAS Example 1 IEHATLAS Example 2 IEHATLAS Example 3 IEHATLAS Example 4

• • • • • • • •

IEHINITT Program • • • • • • • • • • • • • • • • • •

Placing a Standard Label Set on Magnetic

Tape

Input and Output . . • . . . • • Return Codes . • • . • •

Control . . . . . • . • . • • • • • Job Control Statements • . . . • . • • • .

PARM Information on ~he EXEC Statement SYSPRINT DD Statement . • • • •

anyname DD Statement • . • . • • • . SYSIN DD Statement • • • • • Utility Control Statement • • • . • • • •

INITT Statement . . • . • . • .

IEHINITT Examples . . • . . . • • • • . • • • IEHINITT Example 1 . • • • • • • • .

IEHINITT Example 2 . • • • •

IEHINITT Example 3 . . • . . • • • • . • • • . IEHINITT Example 4 . . . . • • • . • • • • • • • . IEHINITT Example 5 . . • . . • • • • . • • • IEHINITT Example 6 . • • . • • • • • • IEHINITT Example 7

xiv MVS/370 Utilities

• •

• •

• •

283 290 290 291 293 293 293 293 293 294 294 294 295 295 296 296 297 297 298 299 301 302 303 303 305 306 311 313 314 315 316 317 317 319 320 322 323 324 325 325 327 326 327 327 328 328 330 330 331 331 332 333 334 335 335 336 336 337 337 337 337 337 337 340 341 341 342 342 343 343 344

\

TNL ON26-1133 (30

Mar

14)

to

OC26-4065-1

IEHLIST Program • • • • • • • • • • • • • • • • • •

Listing OS CVOL Entries • . • • . Listing a Partitioned Data Set Directory

Edited Format • . • . Unedited (Dump) Format

Listing a Volume Table of Contents

Edited Format • • • . . . • . . . • Unedited (Dump) Format

Input and Output . • • • .

Return Codes . . . . • • • •

Control . . . • • • • • • • • . Job Control statements . • . . . •

PARM Information on the EXEC Statement

SYSPRINT DD statement . . . . . anynamel DD Statement

anyname2 DD Statement SYSIN DD Statement . . Utility Control Statements

LISTCTLG Statement . . • • LISTPDS Statement . . . . LISTVTOC Statement . . • • • IEHLIST Examples

IEHLIST Example 1 IEHLIST Example 2 IEHLIST Example 3 IEHLIST Example 4

IEHMOVE Program • • • • • • • • • • • • • • • • • • • • Volume Size Compatibility

Space Allocation . . . • Reblocking Data Sets

Using IEHMOVE with RACF Moving or Copying a Data Set

Sequential Data Sets Partitioned Data Sets BDAM Data Sets

Multivolume Data Sets

Unloaded Data Sets . • • . . •

Unmovable Data Sets . . . • . • • • • • . . Moving or Copying a Group of Cataloged Data Sets

Moving or Copying an OS CVOL • . • • . . • • • • • • • • Moving or Copying a Volume of Data Sets • • • • . Moving or Copying BDAM Data Sets with Variable-Spanned

Records . . . . .

Input and Output

Return Codes . • . . • • • • • • Control . • . . . • • • Job Control Statements . . • • • PARM Information on the EXEC Statement SYSPRINT DD Statement • • • • • SYSUTI DD Statement . . • • • anynamel DD Statement . • • •

anyname2 DD Statement . . • • •

tape DD Statement . . . • . . • • • . • • • • • • . SYSIN DD Statement • . . • • • . • • . • • • . • Job Control Language for the Track Overflow Feature Utili ty Control Statements . • . • • • • • .

MOVE DSNAME Statement . .• • • • • • • . COPY DSNAME Statement

MOVE DSGROUP Statement • • . • COPY DSGROUP Statement • . • . • • • MOVE PDS Statement . . • .

COpy PDS Statement . . . • • MOVE CATALOG Statement

COpy CATALOG Statement MOVE VOLUME Statement COpy VOLUME Statement INCLUDE Statement

345 345 345 347 346 347 347 350 351 351 352 352 352 353 353 353 354 354 354 354 355 357 351 358 359 359

361

362 363 364 365 365 366 366 369 369 370 370 370 371 372 373 373 374 374 374 375 376 376 376 377 377 378 378 378 379 380 381 381 382 383 383 384 385 384 385

IEHMOVE Example 3 · · · · ^· · · · ^·

IEHMOVE Example

4

· · · · · · · · · ^·

IEHMOVE Example

⁵

· · · · · · ^·

IEHMOVE Example

⁶

· · · · · · · ^·

IEHMOVE Example IEHMOVE Example

7 8

· · · · · · · · ^· · · · · ^· · · · · ^{· · ·}

IEHMOVE Example

9

· · · · · · · · · ·

IEHMOVE Example 10 · · · · ·

IEHMOVE Example 11 · · · · · · · ·

IEHMOVE Example 12 · · · · · · · · · · · ·

IEHMOVE Example 13 · · · · ·

IEHPROGM Program • • • • • • • • • • • • • • • • • • • • Scratching a Data Set or Member • • • • •

Renaming a Data Set or Member . • • • • Cataloging a Data Set in an OS CVOL ••

Building or Deleting an Index in an OS CVOL • Building or Deleting an Index Alias in an OS CVOL

Connecting or Releasing Two OS CVOLs • • • • • • • • • Building and Maintaining a Generation Data Group Index in

an OS CVOl . . . • • • • • • •

Maintaining Data Set Passwords • • • • • • • • • Adding Data Set Passwords . • • •

Replacing Data Set Passwords Deleting Data Set Passwords Listing Password Entries

Input and Output . . . . • • • • • • • • Return Codes . . . . • . • • •

Control • . . . • • • · . . .

Job Control Statements • • • • • • PARM Information on the EXEC Statement SYSPRINT DD Statement

anynamel DD Statement anyname2 DD Statement SYSIN DD Statement ••

Utility Control Statements

SCRATCH Statement • • • • • • RENAME Statement . • . •

CATlG Statement

UNCATLG Statement • • BLDX (Build Index> Statement

DlTX (Delete Index) Statement ••

BlDA (Build Index Alias) Statement DLTA (Delete Index Alias) statement CONNECT Statement . . • • • . • •

RELEASE (Disconnect) Statement . • • • • • • • • • • BLDG (Build Generation Data Group Index) Statement ADD (Add a Password) Statement • • • • • • • • • • • REPLACE (Replace a Password) Statement ••

~

• • • • DElETEP (Delete a Password) Statement • • • • • • • LIST (List Information from a Password> Statement

IEHPROGM Examples • • • • • • • • ·

IEHPROGM Example 1 • . • • • • • • IEHPROGM Example 2 • • • • • • • • • IEHPROGM Example 3 • • • • • • • •

IEHPROGM Example 4 • • • •

IEHPROGM Example

5 • • • • • • • •

IEHPROGM Example

6 . • . . • • • • .

IEHPROGM Example 7 IEHPROGM Example

8

IEHPROGM Example

⁹

IEHPROGM Example 10

IFHSTATR Program • • • • • • • • • • • • • • • • • • Assessing the Quality of Tapes in a Library

Input and Output . . • . • • • • Control . . . • • • • • • • •

Job Control Statements • • • •

IFHSTATR Example • • • •

Appendix A. Exit Routine Linkage • • • • • • • • • • • Linking to an Exit Routine . • • • • • • • •

label Processing Routine Parameters • • • • Nonlabel Processing Routine Parameters • • • • xvi MVS/370 Utilities

396 395

397 397

398 399

401 400

401 402

403

404 404

404 405

405 405

406

407 409

411 410

411 411

412 412

412 413

413 414

414 414

415 415

415 415

417 417

418 418

418 418

419 419

419 420

420 421

421 426

427 428

428 429

429 430

430 431

431 432

435 435

436 436

436 437

438 438

438 439

TNL ON26-8133 (30 Mar 14) to OC26-4065-1 Returning from an Exit Routine

Appendix B.

DO Statement DD statements for Defining Mountable Devic ••

Examples . • • • • • • • • • DO Example

00 Example 00 Example DO Example DO Example

1 • • • • •

2 • • • • • • • • • • • • • •

3

4

5

Appendix C. Proce •• ing U.er Label. • • • • • • Processing User Labels as Data Set Descriptors Exiting to a User's Totaling Routine

Processing User Labels as Data

• • • •

Index

• • • • • • • • • • • • • • • • • • • • • • •

•

•

440

443 443

443 444

444 444

445

446 446

447 447

449

FIgURES

1. 2.

3. 4.

5. 6.

7. 8.

10. 9.

11.

12.

13. 14.

16. 15.

17. 18.

19. 20.

21. 22.

23. 24.

25.

26. 27.

28.

29. 30.

31.

32.

33. 34.

35. 36.

37. 38.

39.

40.

41. 42.

43.

44.

46. 45.

47. 48.

49. 50.

51. 52.

53. 54.

55. 56.

xviii MVS/370 utilities

System Utility Programs Data Set Utility Programs Independent Utility Program Locating the Correct Example Tasks and Utility Programs Typical Parameter Lists . • • Sequence of DDNMELST Entries

ICAPRTBL Wait-State Codes • • . . . • • ICAPRTBL Utility Control Statements

ICAPRTBL Example Directory • • • . • . . . • • Partitioned Directories Whose Data Sets Can Be Compared Using IEBCOMPR

Partitioned Directories Whose Data Sets Cannot Be Compared Using IEBCOMPR

IEBCOMPR Return Codes . ^{0 •}

Job Control Statements for IEBCOMPR IEBCOMPR Utility Control Statements IEBCOMPR Example Directory

IEBCOPY Return Codes . . . ^{0 0 • •} Job Control Statements for IEBCOPY • . Changing Input Record Format Using IEBCOPY

IEBCOPY Utility Control Statements • • • • . Multiple Copy Operations within a Job Step IEBCOPY Example Directory . . . • . ^{0 • •}

Copying a Partitioned Data Set--Full Copy • • .

Copying from Three Input Partitioned Data Sets • • • COpy Operation with "Replace" Specified on the Data Set Level . . . . Copying Selected Members with Reblocking and Deblocking Selective Copy with "Replace" Specified on the Member Level . . . . Selective Copy with "Replace" Specified on the Data Set Level . . . .. . . . Renaming Selected Members Using IEBCOPY

0... 0 . .

Exclusive Copy with "Replace" Specified for One Input Partitioned Data Set . . . ^{0 • 0 • • • • • • • 0} Compress-in-Place Following Full Copy with "ReplaceR Specified . . • . . . ^{0 0 • • 0 0 0 • 0 0 0} Multiple Copy Operations/Copy Steps

0 . . .

Multiple Copy Operations/Copy Steps within a Job Step IBM-Supplied Patterns . • • • ^{0 • • • •}

IEBDG Actions . . . . • ^{0 • • • • •}

IEBDG Return Codes • . • . • • . • • • • • • • Job Control Statements for IEBDG • • . • • . • . • IEBDG Utility Control Statements . . • . ^{0 • 0 • •} Defining and Selecting Fields for Output Records Using I EB DG • . • • . • • • . • . • • . • • • • • •

Field Selected from the Input Record for Use in the Output Record ^{O . 0 • 0 • • 0 0 • 0 O J • 0 •} Compatible IEBDG Operations . . ^{0 0 • 0 0 • 0} IEBDG User Exit Return Codes . ^{0 0 0 • 0 0 •} Default Placement of Fields within an Output Record Using IEBDG . ^{0 0 0 0 • 0 0 0 0 • • 0 0 • 0 •} Creating Output Records with Utility Control

Statements . . ^{0 • • 0 • 0 • • • • • • • O . •} Repetition Caused by the REPEAT Statement Using IEBDG IEBDG Example Directory . ^{0 • • 0 0 0 • 0 • •}

Output Records at Job Step Completion . • • . Output Partitioned Member at Job Step Completion Partitioned Data Set Members at Job Step Completion Contents of Output Records at Job Step Completion IEBEDIT Return Codes 0 . . . 0 0 •

Job Control Statements for IEBEDIT ^{0 0 0 0 0}

IEBEDIT Example Directory . . ^{0 • • • 0 • • • • • •} Creating a Partitioned Data Set from Sequential Input Using IEBGENER ^{0 0 • 0 • • 0 • • • • • • 0 •}

Expanding a Partitioned Data Set Using IEBGENER Editing a Sequential Data Set Using IEBGENER

1 2 3 7 14 8 15 19 23 20 27 28 28 29 30 32 46 47 49 51 52 61 62 64 66 68 70 72 74 77 80 82 86 98 99 101 100 104 105 106 107 108 108 109 110 121 124 125 127 128 132 132 135 142 143 144

TNL GN26-8133 (30 Mar 14) to OC26-4065-1 57. IEBGENER Return Codes • . • . • • • • • • • • • • • 58. Job Control Statements for IEBGENER

59. IEBGENER Utility Control Statements 60. IEBGENER Example Directory

61. 3800 General Module Header

62. 3800 FCB Module Structure . • • • • • 62.1. 4248 FCB Module Structure • • • •

62.2. 4248 FCB Module Control Byte • • • • • 62.3. 4248 FCB Module Data Byte • . • . • • • • • • • 63. IEBIMAGE Listing of a Forms Control Buffer Module 64. COpy Modification Module Structure . • • • • 65. IEBIMAGE Listing of Three Segments of a Copy 66. 67.

68. 69.

70. 71.

72. 73.

74.

75.

76. 77.

78. 79.

80. 81.

82. 83.

84.

85.

86. 87.

88. 89.

90.

91. 92.

93. 94.

96.

95.

97. 98.

99. 100.

101.

102.

103.

104.

105.

106.

107.

108.

109.

110.

I l l .

112.

113.

114.

Modification Module • . . • • . . • . • • • • • • • Character Arrangement Table Module Structure • • • IEBIMAGE Listing of a Character Arrangement Table

Module . . . • . . • . • •

Graphic Character Modification Module Structure IEBIMAGE Listing of Two Segments of a Graphic Character Modification Module . . . • • • • Library Character Set Module Structure • • • IEBIMAGE Listing of Two Segments of a Library Character Set . . . • . • • . • • IEBIMAGE Return Codes . • . • • • • . Job Control Statements for IEBIMAGE •

Utility Control Statements for IEBIMAGE • • • • • • IEBIMAGE Listing of a COpy Modification Module with Overrun Notes . • • • . . • . • • • •

IEBIMAGE Example Directory • • • • • • • An Unloaded Data Set Created Using IEBISAM Record Heading Buffer Used by IEBISAM IEBISAM User Exit Return Codes

IEBISAM Return Codes • • . • • • Job Control Statements for IEBISAM IEBISAM Example Directory • . . . IEBPTPCH Return Codes . . . • • • Job Control Statements for IEBPTPCH IEBPTPCH Utility Control Statements IEBPTPCH Example Directory

. . . . . . . .

Special Purpose Codes • • • • • . • • MTDI Codes from TCR • • • .•• . • • •

MTST Codes from TCR . • • • . • • • • • • • • • • • MTST Codes after Translation by IEBTCRIN with

TRANS=STDLC . . • . . • • • . • • • • • • • • Tape Cartridge Reader Data Stream . . • • Record Construction . • • • . . • . • • • IEBTCRIN Return Codes . • . • • • • • • • • • IEBTCRIN Job Control Statements •

IEBTCRIN Utility Control Statements IEBTCRIN Example Directory

IEBUPDTE Return Codes . . . . Job Control Statements for IEBUPDTE IEBUPDTE Utility Control Statements

NEW, MEMBER, and NAME Parameters UPDATE=INPLACE Return Codes

IEBUPDTE Example Directory • •

Example of Reordered Sequence Numbers • • • • • • Reordered Sequence Numbers • • • . • • • • •

IEHATLAS Return Codes . • . . • . . Job Control Statements for IEHATLAS Utility Control Statements for IEHATLAS

IEHATLAS Example Directory . . . • . • • • • • • • IBM Standard Label Group after Volume Receives Oat.

IEHINITT Return Codes • . • • . • . • • • • IEHINITT Job Control Statements • . • • • • Printout of INITT Statement Specifications and Initial Volume Label Information

IEHINITT Example Directory . • . Index Structure--Listed by IEHLIST

145 146

148 157

169 171

172 172

172.1

172.2

173

174 176

177 179

110 181

112 114

184 185

208.2 192

233 234

234

235

235 237

243 243

245 251

270 271

272

273 277

271 280

281 283

290 294

295 297

300 305

312 320

322 326

327 327

330 334

336 336

338 340

345

121.

122.

123.

124.

125.

126.

127.

128.

129.

130.

131.

132.

133.

134.

135.

136.

137.

138.

139.

140.

141.

142.

143.

144.

145.

146.

147.

148.

149.

ISO.

151.

152.

153.

154.

ISS.

xx MVS/370 Utilities

IEHlIST Utility Control Statements • • • • • • • • IEHlIST Example Directory • • • • • • • • • • • . Move and COpy Operations--DASD Receiving Volume with Size Compatible with Source Volume • . . • . • . . Move and Copy Operations--DASD Receiving Volume with Size Incompatible with Source Volume • • • • • • • Move and COpy Operations--Non-DASD Receiving Volume Moving and Copying Sequential Data Sets

Moving and Copying Partitioned Data Sets • • Partitioned Data Set Before and After an IEHMOVE Copy Operation • . • • . • • • • • . • • • • • • • Merging Two Data Sets Using IEHMOVE . • • • • Merging Three Data Sets Using IEHMOVE • • • • Moving and Copying a Group of Non-VSAM Cataloged Dat.

Sets . . . .

Moving and Copying the OS CVOL • • • • Moving and Copying a Volume of Data Sets IEHMOVE Return Codes . • • • • •

IEHMOVE Job Control Statements • • • . IEHMOVE Utility Control Statements

IEHMOVE Example Directory • • • • • • • • . • • • Index Structure Before and After an IEHPROGM Build Operation • • • • . • • • • . • • • • • • Building an Index Alias Using IEHPROGM ••

Connecting an OS CVOl to a Second OS CVOl Using I EHPROGM . . • • • • . . • • • • • • • • • • • Connecting Three OS CVOls Using IEHPROGM • • • • • Building a Generation Data Group Index Using IEHPROGM Relationship between the Protection Status of a Data Set and Its Passwords • • • •

listing of a Password Entry • • • • IEHPROGM Return Codes . . . . • . . IEHPROGM Job Control Statements

IEHPROGM Utility Control Statements IEHPROGM Example Directory • • Type 21 SMF Record Format with ESV Data Sample Output from IFHSTATR . • • • •

IFHSTATR Job Control Statements . • . . • • • • • Parameter lists for Nonlabel Processing Exit Routines Return Codes That Must Be Issued by User Exit

Routines • . • • • • • • • • • • . • • • • • System Action at OPEN, EOV, or CLOSE Time • • • • User Totaling Routine Return Codes . . • • .

354 357 362 362 363 366

367

368

368 369 371 371 373

374

379 375 393

406

406 407

408

408

410

412

412

414

416

427 435 436

437

439 441 447 447 .

INTRODUCTION

MVS/370 Data Facility Product provides utility programs to

assist in organizing and maintaining data. Each utility program falls into one of three classes of programs, determined by the function performed and the type of control of the utility.

IYITEn UTILITY pROGRAMS

System utility programs are used to maintain and manipUlate system and user data sets. Entire volume manipulation, for example, copying or restoring, is also provided. These programs must reside in an authorized library and are controlled by

JCL

statements and utility control statements.

They can be executed as jobs or can be invoked as subroutines by authorized programs. The invocation of utility programs and the linkage conventions are discussed in "Invoking utility Programs from a Problem Program" on page 13.

Figure 1 is a list of system utility programs and their purpose.

system utility IEHATLAS IEHINITT IEHLIST IEHMOVE IEHPROGH IFHSTATR

Purpose

To assign alternate tracks and recover usable data records when defective tracks are indicated

To write standard labels on tape volumes To list system control data

To move or copy collections of data

To build and maintain system control data

To select, format, and write information about tape errors from the IFASMFDP tape or the SYS1.MAH data set.

Figure 1. System Utility Programs

DATA SET UTILITY pROGRAMS

Data set utility programs are used to reorganize, change, or compare data at the data set and/or record level. These programs are controlled by

JeL

statements and utility control statements.

These utilities manipUlate partitioned, sequential, or indexed sequential data sets provided as input to the programs. Data ranging from fields within a logical record to entire data sets

can be manipulated. .

Data set utility programs can be executed as jobs or can be invoked as subroutines by a calling program. The invocat;on of utility programs and the linkage conventions are disCUSSQ~ in

TNL ON26-8133 (30 Mar 84) to GC26-4065-1

Two utilities, IEHMOVE and IEBCOPY, do not support Virtual Input/Output (VIO) data sets.

Figure 2 is a list of data set utility programs and their purpose.

Data set

utility Purpose

IEBCOMPR

To compare records in sequential or partitioned.data sets

IEBCOPY

To copy, compress, or merge partitioned data sets, to add RLD count information to load modules, to select or exclude specified members in a copy operation, and to rename and/or replace selected members of

partitioned data sets

IEBDG

To create a test data set consisting of patterned data

IEBED!T

To selectively copy job steps and their associated JOB statements

IEBGENER

To copy records from a sequential data set or to convert a data set from sequential organization to partitioned organization

IEBIMAGE

To modify, print, or link modules for use with the IBM 3800 Printing Subsystem, the 3262 Model 5, or the 4248 printer

IEBISAM

To place source data from an indexed sequential data set into a sequential data set in a format suitable for subsequent reconstruction

IEBPTPCH

To print or punch records that reside in a sequential or partitioned data set

IEBTCRIN

To construct records from the input data stream that have been read from the IBM 2495 Tape Cartridge Reader

IEBUPDTE

To incorporate changes to sequential or partitioned data sets

Figure 2. Data Set Utility Programs

INDEPENPENT UTILITY PROGRAMS

2 MVS/370 Utilities

Independent utility programs are used to prepare devices for system use when the operating system is not available. They operate outside of, and in support of, the operating system, are controlled by utility control statements, and cannot be invoked by a calling program. This pUblication addresses only the ICAPRTBL utility program.

The following figure shows the independent utility program and its purpose.

Independent

utility Purpose

ICAPRTBL

To load the forms control and universal character set buffers of the IBM 3203-5 or 3211 printer after an unsuccessful attempt to IPL, with the 3203-5 or 3211 assigned as the output portion of a composite console.

Figure 3. Independent Utility Program

The selection of a specific program depends on the nature of the job to be performed. For example, renaming a data set involves modifying system control data. Therefore, a system utility program can be used to rename the data set. In some cases, a specific function can be performed by more than one program.

"Guide to Utility Program Functions" on page 8 will help you find the program that performs the function you need.

DASD AND TAPE DEVICE SUPPORT

Except where noted, all the following DASD and tape devices are supported by all utility programs. Restrictions and peculiar device support are noted in the individual utility sections.

The table below indicates specific devices supported, and the notation to be used to reference them. The term

DASD

includes all direct access storage devices listed below.

Device Number Devices

DASD: 2305-1 2305-1

2305-2 2305-2

2314 2314

2319 2319

3330 3330-1, 3330-2, 3333, and 3350 in 3330-1 compatibility mode 3330-1 3330-11, 3333-11, and 3350 in

3330-11 compatibility mode 3330V 3850 MSS Virtual Volumes 3340 3340, 3344 (both 35

&

70

megabyte models)

3350 3350 Native mode

3375 3375

3380 3380

Tape: 2400 2400 (all models)

2495 2495 (IEBTCRIN only)