Apparent contradiction about IDB2UNLD in r12 reference guide

Products

• CA RC/Migrator
• CA Endevor SCM Interface
• DB2 Administration
• CA RC Compare for DB2 for z/OS
• CA RC Extract for DB2 for z/OS
• CA RC/Query
• CA RC Secure for DB2 for z/OS
• CA RC Update for DB2 for z/OS
• CA Bind Analyzer for DB2 for z/OS
• CA Detector
• CA SQL-Ease for DB2 for z/OS
• CA Sysview Performance Management Option for DB2 for z/OS
• CA Database Detector for DB2 for z/OS
• CA Plan Analyzer for DB2 for z/OS
• CA Subsystem Analyzer for DB2 for z/OS
• CA Database Analyzer for DB2 for z/OS
• CA Fast Unload for DB2 for z/OS
• CA Fast Check for DB2 for z/OS
• CA Fast Index for DB2 for z/OS
• CA Fast Load for DB2 for z/OS
• CA Rapid Reorg for DB2 for z/OS

Issue/Introduction

Description:

In the Insight for DB2 R12 System Reference Guide, Chapter 7, section Historical Backups of Performance Data, it talks about the new unload process for linear vsam files: IDUNLJCL.

In Chapter 8: Archiving DB2 Performance Data it references the old process IDB2UNLD and shows its use in the graphics. Is this a contradiction?

Solution:

This is not a contradiction. If you take a look at the program names of R12 and R11.5 IDB2UNLD you'll notice that they are different:

R11.5 IDB2UNLD uses EXEC PGM=IDB2UNLD whereas R12 IDB2UNLD uses the new utility created for reading the linear dataset EXEC PGM=IDB2UIFI.

The references to IDUNLJCL and IDB2UNLD are to sample JCL members in the SOURCE dataset. Both members use the same program, IDB2UIFI.

Environment

Release:
Component: IDB2