ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

When unloading a database from an image copy, why is the RECOVER function invoked?

book

Article ID: 53666

calendar_today

Updated On:

Products

CA Distributed Database Management CA Database Analyzer for DB2 for Oracle Database Analyzer (IMS Tools) Mainframe Configuration Manager for IMS for z/OS IMS TOOLS - MISC Compress Data Compression (IMS Tools) Database Analyzer for IMS for z/OS Database Copier for IMS for z/OS Database Organizer for IMS for z/OS Mainframe Extended Terminal Manager (IMS Tools) High Performance Recovery for IMS for z/OS Database Organizer (IMS Tools) Mainframe Program Restart Manager for IMS for z/OS Secondary Index Builder for IMS for z/OS Secondary Index for IMS for z/OS

Issue/Introduction

Description:

When using Database Organizer to unload a database from an image copy, using the UNLOADIC=YES control statement, the RECOVER function is invoked:

FUNCTION=UNLOAD,UNLOADIC=YES,UNLAUTH=NO,DBRC=NO,
DBDNAME=dbdname

RECOVER is then invoked by DBO using these options:

FUNCTION=RECOVER,DBD=dbdname,
DDNAME=ddname,
ICDDNAME=icddname,
UNLOADIC=YES,BYPASSCA=YES,LASTIC=YES,
DBRC=N

Why is the RECOVER function invoked in order to perform an unload?

Solution:

The Unload process when UNLOADIC=YES is specified is as follows:

  • The database datasets are recovered from image copies into dataspaces.

  • For HIDAM : the primary index is created in a dataspace.

  • The unload process reads the data from the dataspaces and, when complete,
    deletes the dataspaces.

  • The unload file is created.

Note that neither the actual database nor DBRC are updated by the process.

Environment

Release:
Component: DBO