Request for the IDCAMS delete define JCL to initialize the IDB2 HSTSQLDB VSAM file
book
Article ID: 190255
calendar_today
Updated On:
Products
Bind Analyzer for DB2 for z/OSSQL-Ease for DB2 for z/OSSYSVIEW Performance Management Option for DB2 for z/OSPlan Analyzer for DB2 for z/OSSubsystem Analyzer for DB2 for z/OSDatabase Management for DB2 for z/OS - Performance SuiteDatabase Management for DB2 for z/OS - SQL Performance SuiteInsight Performance Monitor for DB2 UDB for z/OS
Issue/Introduction
I would like sample IDCAMS JCL to create the HSTSQLDB VSAM file for IDB2
Environment
Release : 20.0
Component : CA Insight Database Performance Monitor for DB for z/OS
Cause
Resolution
The Post-Install process for Sysview for DB2 (IDB2) creates a .SOURCE library, and within this library the member IDDCVSAM (or it could be called ssidVSAM). It is this job that deletes/defines the IDB2 DC's history vsam files including the HSTSQLDB file. The Cylinder allocation can be modified per your history needs, but the values found here will be sufficient for initial processing. Here is the JCL to define it:
//jobcard //VSAMALLC EXEC PGM=IDCAMS,COND=(0,LT) //SYSPRINT DD SYSOUT=* //SYSIN DD * DEFINE - CLUSTER (NAME(highlevel.IDB2.ssid.HSTSTATS) - LINEAR CYLINDERS(200) - VOLUME(TSOC28) - SHR(2 3) CISZ(4096) ) DEFINE - CLUSTER (NAME(highlevel.IDB2.ssid.HSTACCTG) - LINEAR CYLINDERS(500) - VOLUME(TSOC28) - SHR(2 3) CISZ(4096) ) DEFINE - CLUSTER (NAME(highlevel.IDB2.ssid.HSTSQLDB) - LINEAR CYLINDERS(500) - VOLUME(TSOC28) - SHR(3 3) CISZ(16384) ) /* These vsam file names are referenced in the Data Collector's ssidSYSP member also found in the .SOURCE library. It is within this member you will find the parameters: HSTSTATS-DSN HSTACCTG-DSN HSTSQLDB-DSN