How to extract data from Dynamic Capacity Intelligence (DCI)

Products

• Dynamic Capacity Intelligence

Issue/Introduction

Sometimes it is necessary that the development, support or professional service is analyzing your collected Dynamic Capacity Intelligence (DCI) data. Please provide it then to CA Technologies.

Reason for that could be:

- You are running DCI in simulation Mode. Before it becomes active you want that an DCI-Consultant helps you to generate a starting policy for the active mode

- The behavior from DCI is different than you expect. With this data it is easier for CA to retrace the behavior of DCI. Also the policy which was active at this time is the important to sent CA (article: TEC1302702)

 

Environment

Release: CADCIU00200-1.5-Dynamic Capacity Intelligence-MSU
Component:

Resolution

In your Dynamic Capacity Intelligence (DCI) installation at the host there is a library called CFHRSAMP Member: #EXPORTC:

 

...JOBCARD
//********************************************************************
//* CA DYNAMIC CAPACITY INTELLIGENCE FOR ZSYSTEMS V1.5 GEN 0200
//* COPYRIGHT (C) 2017 CA. ALL RIGHTS RESERVED.
//********************************************************************
//*------------------------------------------------------------------*
//*CREATE MSU DB EXPORT DATA SET                                 *
//*
//*
//* - ADD A JOBCARD
//*
//* - CHANGE  $MSUDB$      TO THE NAME OF YOUR MSU DB CLUSTER
//*
//*
//*
//*------------------------------------------------------------------*
//*
//*------------------------------------------------------------------*
//* DELETE OLD FILES IF ALLOCATED
//*------------------------------------------------------------------*
//S1        EXEC PGM=IDCAMS
//SYSPRINT  DD   SYSOUT=*
//SYSIN     DD   *
    DELETE   $MSUDB$.REPRO -
             PURGE
    DELETE   $MSUDB$.TRS -
             PURGE
    SET MAXCC = 0000
/*
//*
//*------------------------------------------------------------------*
//*    CREATE TEMPORARY REPRO FILE
//*------------------------------------------------------------------*
//CRE1     EXEC PGM=IEFBR14,COND=(0,NE)
//TEMPFILE DD DSN=$MSUDB$.REPRO,
//            DISP=(NEW,CATLG),
//            DCB=(LRECL=8189,RECFM=VB),
//            SPACE=(CYL,(10,50)),
//            UNIT=SYSDA
//*------------------------------------------------------------------*
//*    REPRO MSU DB CLUSTER
//*------------------------------------------------------------------*
//GETMSU1  EXEC PGM=IDCAMS,COND=(0,NE)
//SYSPRINT DD SYSOUT=*
//IN       DD DISP=SHR,
//            DSN=$MSUDB$
//TEMP     DD DISP=OLD,
//            DSN=$MSUDB$.REPRO
//SYSIN DD *
  REPRO INFILE(IN) OUTFILE(TEMP)
/*
//*------------------------------------------------------------------*
//* PACK DATA WITH TRSMAIN
//*------------------------------------------------------------------*
//PACK  EXEC PGM=TRSMAIN,PARM=PACK
//SYSPRINT DD SYSOUT=*
//INFILE   DD DSN=$MSUDB$.REPRO,
//         DISP=SHR
//OUTFILE  DD DSN=$MSUDB$.TRS,
//         DISP=(NEW,CATLG),UNIT=SYSDA,
//         SPACE=(CYL,(50,50),RLSE)
//*------------------------------------------------------------------*
//* DELETE TEMPORARY DATA
//*------------------------------------------------------------------*
//DELTEMP   EXEC PGM=IDCAMS
//SYSPRINT  DD   SYSOUT=*
//SYSIN     DD   *
    DELETE   $MSUDB$.REPRO -
             PURGE
/*
//*

To customize this job:

- enter a valid jobcard

- change $MSUDB$ to the name of your MSU-Database

- submit this job

- if your database is very big you also have to increase the space-parameter: SPACE=(CYL,(10,50))

 

You will get an extract in tersed format (Filename: $MSUDB$.TRS). This file you can sent to CA Technologies.