Insight IQL Request's Dataset is in use by Data Collector

book

Article ID: 20019

calendar_today

Updated On:

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:

An Insight request was started. Within the IQL request, an output dataset is allocated via the REVIEW statement. When the request is stopped attempts to browse the output dataset fails due to the Insight Data Collector having an exclusive hold on it.

Solution:

It is the IQL REVIEW statement with a disposition of MOD that is placing the dataset under the exclusive control of the Data Collector ( allowing for the 'review' of the output within the IDB2 TSO session.) To utilize the REVIEW statement with the ability to view the dataset outside of IDB2 a disposition of SHR should be used instead of MOD. Or, in lieu of REVIEW use either OUTFILE or PRINT DSN.

Environment

Release: BINDAN00200-15-Bind Analyzer-for DB2 for z/OS
Component: