SQL to determine if database is a risk as described in Hiper PTF - r12.0 SO11864, r12.1 SO12057
search cancel

SQL to determine if database is a risk as described in Hiper PTF - r12.0 SO11864, r12.1 SO12057

book

Article ID: 144795

calendar_today

Updated On:

Products

CA 7 Workload Automation

Issue/Introduction

Execute the following SQL statement against each logical database to determine if you are at risk for the problem addressed by SO11864 or SO12057. 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  ; 
           

 

 

 

Resolution

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