SQL to determine if database is a risk as described in Hiper PTF - SO11864

book

Article ID: 144795

calendar_today

Updated On:

Products

CA Workload Automation CA 7 Edition

Issue/Introduction

Execute the following SQL statement against each logical database to determine if you are at risk for the problem addressed by SO11864. This SQL poses no risk - it is selecting only and will not update your database. Before executing

  1. Change the JCL to STEPLIB to the correct MUF 
  2. Change 'DB=YOUR_LOGICAL_DB' to specify your logical database name.

//STEP1 EXEC PGM=DBSQLPR 
//STEPLIB DD to your MUF (same 2 libs used in CA7ONL)    *** CHANGE THIS ***
//SYSPRINT DD SYSOUT=* 
//STDOUT DD SYSOUT=* 
//OPTIONS DD * 
PRTWIDTH=255 
INPUTWIDTH=70 
ROWLIMIT=5000 
AUTHID=MFWA 
NOTYPE 
//SYSIN DD *  

SELECT DATASET, OCCURRENCE# FROM CA7_DATASET_OCCUR
WHERE  DB = 'YOUR_LOGICAL_DB' AND                       *** CHANGE THIS ***         

INTEXTRACT(DEVICE_TYPE_01,1) = 242  ;             

 

 

 

Environment

Release : 12.0 and 12.1  (Hyper for release 12.1 has not been published, this document will be updated with r12.1 PTF number)

Component : CA-7

Resolution

If no rows are returned, the logical database is not at risk for the problem. If rows are returned, contact CA/Broadcom support for assistance with updating the database.