Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Administration Guide
IBM
SC27-8844-02
Db2 12 for z/OS
Administration Guide
IBM
SC27-8844-02
Notes
Before using this information and the product it supports, be sure to read the general information under “Notices” at the
end of this information.
Subsequent editions of this PDF will not be delivered in IBM Publications Center. Always download the latest edition from
Db2 12 for z/OS Product Documentation.
iv Administration Guide
Dropping and re-creating a table space to change its attributes . . . . . . . . . . . . . . . . . 138
Redistributing data in partitioned table spaces . . . . . . . . . . . . . . . . . . . . . . 140
Increasing partition size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Altering a page set to contain Db2-defined extents . . . . . . . . . . . . . . . . . . . . . 143
| Converting partitioned (non-UTS) table spaces to partition-by-range universal table spaces . . . . . . . 143
| Converting table spaces to use table-controlled partitioning . . . . . . . . . . . . . . . . . . 144
Altering Db2 tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Adding a column to a table . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Specifying a default value when altering a column . . . . . . . . . . . . . . . . . . . . . 151
Altering the data type of a column . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Altering a table for referential integrity . . . . . . . . . . . . . . . . . . . . . . . . . 160
Adding or dropping table check constraints . . . . . . . . . . . . . . . . . . . . . . . 164
Adding partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Altering partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Adding XML columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Altering the size of your hash spaces . . . . . . . . . . . . . . . . . . . . . . . . . 178
Adding a system period and system-period data versioning to an existing table . . . . . . . . . . . 180
Adding an application period to a table . . . . . . . . . . . . . . . . . . . . . . . . 182
Manipulating data in a system-period temporal table . . . . . . . . . . . . . . . . . . . . 182
Altering materialized query tables . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Altering the assignment of a validation routine . . . . . . . . . . . . . . . . . . . . . . 185
Altering a table to capture changed data . . . . . . . . . . . . . . . . . . . . . . . . 186
Changing an edit procedure or a field procedure . . . . . . . . . . . . . . . . . . . . . 186
Altering the subtype of a string column . . . . . . . . . . . . . . . . . . . . . . . . 187
Altering the attributes of an identity column . . . . . . . . . . . . . . . . . . . . . . . 187
Changing data types by dropping and re-creating the table . . . . . . . . . . . . . . . . . . 188
Moving a table to a table space of a different page size . . . . . . . . . . . . . . . . . . . 192
Altering Db2 views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Altering views by using the INSTEAD OF trigger . . . . . . . . . . . . . . . . . . . . . 193
Changing data by using views that reference temporal tables . . . . . . . . . . . . . . . . . 193
Altering Db2 indexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Alternative method for altering an index . . . . . . . . . . . . . . . . . . . . . . . . 195
Adding columns to an index . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Altering how varying-length index columns are stored . . . . . . . . . . . . . . . . . . . 197
Altering the clustering of an index . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Dropping and redefining a Db2 index . . . . . . . . . . . . . . . . . . . . . . . . . 199
Reorganizing indexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Pending data definition changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Materializing pending definition changes . . . . . . . . . . . . . . . . . . . . . . . . 203
Restrictions for changes to objects that have pending data definition changes . . . . . . . . . . . . 208
| Pending column alterations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Altering stored procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Altering user-defined functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Altering implicitly created XML objects. . . . . . . . . . . . . . . . . . . . . . . . . . 216
Changing the high-level qualifier for Db2 data sets . . . . . . . . . . . . . . . . . . . . . . 216
Defining a new integrated catalog alias. . . . . . . . . . . . . . . . . . . . . . . . . 217
Changing the qualifier for system data sets . . . . . . . . . . . . . . . . . . . . . . . 217
Changing qualifiers for other databases and user data sets . . . . . . . . . . . . . . . . . . 221
Tools for moving Db2 data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Moving Db2 data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Moving a Db2 data set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Contents v
Destinations for command output messages . . . . . . . . . . . . . . . . . . . . . . . . 240
Unsolicited Db2 messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
vi Administration Guide
Altering buffer pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Monitoring buffer pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Controlling user-defined functions . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
Starting user-defined functions . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Monitoring user-defined functions . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Stopping user-defined functions . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Controlling Db2 utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Starting online utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Monitoring and changing online utilities . . . . . . . . . . . . . . . . . . . . . . . . 304
Controlling Db2 stand-alone utilities. . . . . . . . . . . . . . . . . . . . . . . . . . 304
Controlling the IRLM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
z/OS commands that operate on IRLM. . . . . . . . . . . . . . . . . . . . . . . . . 307
Starting the IRLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
Stopping the IRLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
Monitoring threads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Types of threads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Output of the DISPLAY THREAD command . . . . . . . . . . . . . . . . . . . . . . . 311
Displaying information about threads . . . . . . . . . . . . . . . . . . . . . . . . . 311
Monitoring all DBMSs in a transaction . . . . . . . . . . . . . . . . . . . . . . . . . 316
Controlling connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
Controlling TSO connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
Controlling CICS connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
Controlling IMS connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Controlling RRS connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Controlling connections to remote systems . . . . . . . . . . . . . . . . . . . . . . . 342
Controlling traces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Diagnostic traces for attachment facilities . . . . . . . . . . . . . . . . . . . . . . . . 366
Controlling the Db2 trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
Diagnostic trace for the IRLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Setting the priority of stored procedures . . . . . . . . . . . . . . . . . . . . . . . . . 368
Setting special registers with profiles . . . . . . . . . . . . . . . . . . . . . . . . . . 369
| Setting built-in global variables with profiles . . . . . . . . . . . . . . . . . . . . . . . . 371
Chapter 9. Managing the log and the bootstrap data set . . . . . . . . . . . . . . 375
How database changes are made . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
Units of recovery and points of consistency . . . . . . . . . . . . . . . . . . . . . . . 375
How Db2 rolls back work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
How the initial Db2 logging environment is established . . . . . . . . . . . . . . . . . . . 377
How Db2 creates log records . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
How Db2 writes the active log . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
How Db2 writes (offloads) the archive log. . . . . . . . . . . . . . . . . . . . . . . . 379
How Db2 retrieves log records . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
Managing the log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
Quiescing activity before offloading . . . . . . . . . . . . . . . . . . . . . . . . . . 384
Archiving the log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
Adding an active log data set to the active log inventory with the SET LOG command. . . . . . . . . 387
Dynamically changing the checkpoint frequency. . . . . . . . . . . . . . . . . . . . . . 388
Setting limits for archive log tape units . . . . . . . . . . . . . . . . . . . . . . . . . 389
Monitoring the system checkpoint . . . . . . . . . . . . . . . . . . . . . . . . . . 389
Displaying log information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
| What to do before RBA or LRSN limits are reached . . . . . . . . . . . . . . . . . . . . . 390
| Converting page sets to the 10-byte RBA or LRSN format . . . . . . . . . . . . . . . . . . 392
| Resetting the log RBA value in a data sharing environment (6-byte format). . . . . . . . . . . . . 394
| Resetting the log RBA value in a non-data sharing environment (6-byte format) . . . . . . . . . . . 395
Canceling and restarting an offload . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
Displaying the status of an offload . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
Discarding archive log records. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
Locating archive log data sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Management of the bootstrap data set . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Restoring dual-BSDS mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
BSDS copies with archive log data sets . . . . . . . . . . . . . . . . . . . . . . . . . 403
Contents vii
Recommendations for changing the BSDS log inventory . . . . . . . . . . . . . . . . . . . 403
Chapter 13. Recovering from different Db2 for z/OS problems . . . . . . . . . . . 515
Recovering from IRLM failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
Recovering from z/OS or power failure . . . . . . . . . . . . . . . . . . . . . . . . . 515
Recovering from disk failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
Recovering from application errors . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
Backing out incorrect application changes (with a quiesce point) . . . . . . . . . . . . . . . . 518
Backing out incorrect application changes (without a quiesce point) . . . . . . . . . . . . . . . 519
Recovering from IMS-related failures . . . . . . . . . . . . . . . . . . . . . . . . . . 519
Recovering from IMS control region failure . . . . . . . . . . . . . . . . . . . . . . . 520
Recovering from IMS indoubt units of recovery . . . . . . . . . . . . . . . . . . . . . . 520
Recovering from IMS application failure . . . . . . . . . . . . . . . . . . . . . . . . 522
Recovering from a Db2 failure in an IMS environment . . . . . . . . . . . . . . . . . . . 523
Recovering from CICS-related failure . . . . . . . . . . . . . . . . . . . . . . . . . . 523
Recovering from CICS application failures. . . . . . . . . . . . . . . . . . . . . . . . 524
Contents ix
Recovering Db2 when CICS is not operational . . . . . . . . . . . . . . . . . . . . . . 524
Recovering Db2 when the CICS attachment facility cannot connect to Db2 . . . . . . . . . . . . . 525
Recovering CICS indoubt units of recovery . . . . . . . . . . . . . . . . . . . . . . . 526
Recovering from CICS attachment facility failure . . . . . . . . . . . . . . . . . . . . . 529
Recovering from a QMF query failure . . . . . . . . . . . . . . . . . . . . . . . . . . 529
Recovering from subsystem termination . . . . . . . . . . . . . . . . . . . . . . . . . 530
Recovering from temporary resource failure . . . . . . . . . . . . . . . . . . . . . . . . 531
Recovering from active log failures . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
Recovering from being out of space in active logs . . . . . . . . . . . . . . . . . . . . . 532
Recovering from a write I/O error on an active log data set . . . . . . . . . . . . . . . . . . 533
Recovering from a loss of dual active logging . . . . . . . . . . . . . . . . . . . . . . 534
Recovering from I/O errors while reading the active log . . . . . . . . . . . . . . . . . . . 534
Recovering from archive log failures. . . . . . . . . . . . . . . . . . . . . . . . . . . 536
Recovering from allocation problems with the archive log . . . . . . . . . . . . . . . . . . 536
Recovering from write I/O errors during archive log offload . . . . . . . . . . . . . . . . . 537
Recovering from read I/O errors on an archive data set during recovery . . . . . . . . . . . . . 537
Recovering from insufficient disk space for offload processing . . . . . . . . . . . . . . . . . 538
Recovering from BSDS failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Recovering from an I/O error on the BSDS . . . . . . . . . . . . . . . . . . . . . . . 539
Recovering from an error that occurs while opening the BSDS . . . . . . . . . . . . . . . . . 540
Recovering from unequal timestamps on BSDSs . . . . . . . . . . . . . . . . . . . . . . 540
Recovering the BSDS from a backup copy . . . . . . . . . . . . . . . . . . . . . . . . 541
Recovering from BSDS or log failures during restart . . . . . . . . . . . . . . . . . . . . . 543
Recovering from failure during log initialization or current status rebuild . . . . . . . . . . . . . 546
Recovering from a failure during forward log recovery . . . . . . . . . . . . . . . . . . . 558
Recovering from a failure during backward log recovery . . . . . . . . . . . . . . . . . . . 563
Recovering from a failure during a log RBA read request. . . . . . . . . . . . . . . . . . . 566
Recovering from unresolvable BSDS or log data set problem during restart. . . . . . . . . . . . . 567
Recovering from a failure resulting from total or excessive loss of log data . . . . . . . . . . . . . 569
Resolving inconsistencies resulting from a conditional restart . . . . . . . . . . . . . . . . . 573
Recovering from Db2 database failure . . . . . . . . . . . . . . . . . . . . . . . . . . 579
Recovering a Db2 subsystem to a prior point in time . . . . . . . . . . . . . . . . . . . . . 580
Recovering from a down-level page set problem. . . . . . . . . . . . . . . . . . . . . . . 581
Recovering from a problem with invalid LOBs . . . . . . . . . . . . . . . . . . . . . . . 583
Recovering from table space I/O errors. . . . . . . . . . . . . . . . . . . . . . . . . . 584
Recovering from Db2 catalog or directory I/O errors . . . . . . . . . . . . . . . . . . . . . 585
Recovering from integrated catalog facility failure . . . . . . . . . . . . . . . . . . . . . . 586
Recovering VSAM volume data sets that are out of space or destroyed . . . . . . . . . . . . . . 586
Recovering from out-of-disk-space or extent limit problems . . . . . . . . . . . . . . . . . . 587
Recovering from referential constraint violation . . . . . . . . . . . . . . . . . . . . . . . 591
Recovering from distributed data facility failure . . . . . . . . . . . . . . . . . . . . . . . 592
Recovering from conversation failure . . . . . . . . . . . . . . . . . . . . . . . . . 592
Recovering from communications database failure . . . . . . . . . . . . . . . . . . . . . 593
Recovering from database access thread failure . . . . . . . . . . . . . . . . . . . . . . 594
Recovering from VTAM failure . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
| Recovering from VTAM ACB OPEN problems . . . . . . . . . . . . . . . . . . . . . . 595
Recovering from TCP/IP failure . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
Recovering from remote logical unit failure . . . . . . . . . . . . . . . . . . . . . . . 597
Recovering from an indefinite wait condition . . . . . . . . . . . . . . . . . . . . . . . 597
Recovering database access threads after security failure . . . . . . . . . . . . . . . . . . . 598
Performing remote-site disaster recovery . . . . . . . . . . . . . . . . . . . . . . . . . 599
Recovering from a disaster by using system-level backups . . . . . . . . . . . . . . . . . . 599
Restoring data from image copies and archive logs . . . . . . . . . . . . . . . . . . . . . 599
Recovering from disasters by using a tracker site . . . . . . . . . . . . . . . . . . . . . 614
Using data mirroring for disaster recovery . . . . . . . . . . . . . . . . . . . . . . . 623
Scenarios for resolving problems with indoubt threads . . . . . . . . . . . . . . . . . . . . 630
Scenario: Recovering from communication failure . . . . . . . . . . . . . . . . . . . . . 631
Scenario: Making a heuristic decision about whether to commit or abort an indoubt thread . . . . . . . 633
Scenario: Recovering from an IMS outage that results in an IMS cold start . . . . . . . . . . . . . 635
Scenario: Recovering from a Db2 outage at a requester that results in a Db2 cold start . . . . . . . . . 636
Scenario: What happens when the wrong Db2 subsystem is cold started . . . . . . . . . . . . . 640
x Administration Guide
Scenario: Correcting damage from an incorrect heuristic decision about an indoubt thread . . . . . . . 642
Contents xi
Field procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704
Field-definition for field procedures . . . . . . . . . . . . . . . . . . . . . . . . . . 705
Specifying field procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705
When field procedures are taken . . . . . . . . . . . . . . . . . . . . . . . . . . . 706
Control blocks for execution of field procedures . . . . . . . . . . . . . . . . . . . . . . 707
Field-definition (function code 8) . . . . . . . . . . . . . . . . . . . . . . . . . . . 711
Field-encoding (function code 0) . . . . . . . . . . . . . . . . . . . . . . . . . . . 713
Field-decoding (function code 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . 715
Log capture routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717
Specifying log capture routines . . . . . . . . . . . . . . . . . . . . . . . . . . . 718
When log capture routines are invoked . . . . . . . . . . . . . . . . . . . . . . . . . 718
Parameter list for log capture routines . . . . . . . . . . . . . . . . . . . . . . . . . 719
Routines for dynamic plan selection in CICS . . . . . . . . . . . . . . . . . . . . . . . . 720
General guidelines for writing exit routines . . . . . . . . . . . . . . . . . . . . . . . . 721
Coding rules for exit routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721
Modifying exit routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722
Execution environment for exit routines . . . . . . . . . . . . . . . . . . . . . . . . 722
Registers at invocation for exit routines. . . . . . . . . . . . . . . . . . . . . . . . . 722
Parameter list for exit routines. . . . . . . . . . . . . . . . . . . . . . . . . . . . 723
Row formats for edit and validation routines . . . . . . . . . . . . . . . . . . . . . . . . 724
Column boundaries for edit and validation procedures . . . . . . . . . . . . . . . . . . . 724
Null values for edit procedures, field procedures, and validation routines . . . . . . . . . . . . . 725
Fixed-length rows for edit and validation routines . . . . . . . . . . . . . . . . . . . . . 725
Varying-length rows for edit and validation routines . . . . . . . . . . . . . . . . . . . . 725
Varying-length rows with nulls for edit and validation routines . . . . . . . . . . . . . . . . 726
EDITPROCs and VALIDPROCs for handling basic and reordered row formats . . . . . . . . . . . 727
Converting basic row format table spaces with edit and validation routines to reordered row format . . . . 727
Dates, times, and timestamps for edit and validation routines . . . . . . . . . . . . . . . . . 729
Parameter list for row format descriptions . . . . . . . . . . . . . . . . . . . . . . . . 729
Db2 codes for numeric data in edit and validation routines . . . . . . . . . . . . . . . . . . 731
Information resources for Db2 12 for z/OS and related products . . . . . . . . . . 739
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
Programming interface information . . . . . . . . . . . . . . . . . . . . . . . . . . . 742
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743
Terms and conditions for product documentation . . . . . . . . . . . . . . . . . . . . . . 744
Privacy policy considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749
Throughout this information, “Db2” means “Db2 12 for z/OS”. References to other
Db2 products use complete names or specific abbreviations.
Important: To find the most up to date content, always use IBM® Knowledge
Center, which is continually updated as soon as changes are ready. PDF manuals
are updated only when new editions are published, on an infrequent basis.
| Generally, this information assumes that the highest available function level is
| activated , and that your applications run with the equivalent application
| compatibility value. However, changes for function levels are marked in the
| documentation. For more information, see How Db2 function levels are
| documented (Db2 for z/OS What's New?).
Overview of Db2 12 new function availability
The availability of new function depends on the type of enhancement, the
activated function level, and the application compatibility levels of
applications. In the initial Db2 12 release, most new capabilities are
enabled only after the activation of function level 500 or higher.
Virtual storage enhancements
Virtual storage enhancements become available at the activation of
the function level that introduces them or higher. Activation of
function level 100 introduces all virtual storage enhancements in
the initial Db2 12 release. That is, activation of function level 500
introduces no virtual storage enhancements.
Subsystem parameters
New subsystem parameter settings are in effect only when the
function level that introduced them or a higher function level is
activated. Most subsystem parameter changes in the initial Db2 12
release take effect in function level 500. For a list of these changes,
see Subsystem parameter changes in Db2 12 (Db2 for z/OS What's
New?).
Optimization enhancements
Optimization enhancements become available after the activation
of the function level that introduces them or higher, and full
prepare of the SQL statements. When a full prepare occurs
depends on the statement type:
v For static SQL statements, after bind or rebind of the package
v For non-stabilized dynamic SQL statements, immediately, unless
the statement is in the dynamic statement cache
v For stabilized dynamic SQL statements, after invalidation, free,
or changed application compatibility level
Activation of function level 100 introduces all optimization
enhancements in the initial Db2 12 release. That is, function level
500 introduces no optimization enhancements.
Db2 12 utilities can use the DFSORT program regardless of whether you purchased
a license for DFSORT on your system. For more information, see the following
informational APARs:
v II14047
v II14213
v II13495
Db2 utilities can use IBM Db2 Sort for z/OS (5655-W42) as an alternative to
DFSORT for utility SORT and MERGE functions. Use of Db2 Sort for z/OS
requires the purchase of a Db2 Sort for z/OS license. For more information about
Db2 Sort for z/OS, see Db2 Sort for z/OS.
Related concepts:
Db2 utilities packaging (Db2 Utilities)
| About the Db2 brand change: IBM is rebranding DB2 to Db2. As such, there will
| be changes to all the Db2 offerings. For example, “DB2 for z/OS” is now referred
| to as “Db2 for z/OS,” beginning with Db2 11. While IBM implements the change
| across the Db2 family of products, you might see references to the original name
| “DB2 for z/OS” or “DB2” in different IBM web pages and documents. “DB2 for
| z/OS” and “Db2 for z/OS” refer to the same product, when the PID, Entitlement
| Entity, version, modification, and release information match. For more information,
| see Revised naming for IBM Db2 family products.
Accessibility features
The following list includes the major accessibility features in z/OS products,
including Db2 12 for z/OS. These features support:
v Keyboard-only operation.
v Interfaces that are commonly used by screen readers and screen magnifiers.
v Customization of display attributes such as color, contrast, and font size
Tip: The IBM Knowledge Center (which includes information for Db2 for z/OS)
and its related publications are accessibility-enabled for the IBM Home Page
Reader. You can operate all features using the keyboard instead of the mouse.