End of support

   

This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC Discovery for z/OS 1.8 Open link .

Options for BMC Impact Integration for z/OS and BMC Impact Manager

Modify member MDZJVSAM in BBSAMP and member MDZVSAMF in BBPARM if you want to identify and allocate Configuration Items (CIs) for use with BMC Impact Integration for z/OS and BMC Impact Manager.

BBPARM member MDZVSAMF

This member is optional and tells BMC Discovery for z/OS what file to use when writing CI data for BMC Impact Integration for z/OS and BMC Impact Manager. Replace &BBDSN with the dataset name specified in BBSAMP member MDZJVSAM. This job must be run first in order to allocate the VSAM file. The dataset name is followed by a comma and an optional parameter that specifies how many days configuration items are kept in the VSAM file after BMC Discovery for z/OS stops seeing them. The default value is 60 days. There are two different approaches to use:

  • You can create a UBBPARM dataset for each system on which you want to collect data and create an MDZJVSAMF member in each UBBPARM dataset.
  • You can create an MDZJVSAMF member in the BBPARM dataset and place an &SYS variable in the dataset name. The variable will be replaced with the z/OS system name, so if &BBDSN is changed to bmc.&SYS.vsamfile and is run on system SYSA, the BMC Discovery for z/OS system will try to allocate the file bmc.sysa.vsamfile, on z/OS system SYSB it will allocate bmc.sysb.vsamfile, and so on. You need one VSAM file for each system on which you want to write configuration item data.

BBSAMP member MDZJVSAM

This member offers sample JCL to allocate a VSAM configuration item dataset.

//JOBCARD JOB
//*
//*--------------------------------------------------------------------
//*
//* ** ALLOCATE VSAM CONFIGURATION ITEM DATASET **
//*
//* SAMPLE JCL FOR ALLOCATING ONE VSAM CONFIGURATION ITEM DATASET
//* TO BE USED BY DISCOVERY FOR Z/OS
//*
//* INSTRUCTIONS:
//*
//* - REVIEW THE JCL FOR APPLICABILITY TO YOUR INSTALLATION
//* STANDARDS.
//*
//* - CHANGE ?BBCHILV TO THE HIGH-LEVEL QUALIFIER YOU CHOSE FOR THE
//* DISCOVERY FOR Z/OS DATASETS.
//*
//* - FOLLOWING THE //SYSIN DD * STATEMENT,
//*
//* LINE 1 AND 2 CONTAINS USER-CUSTOMIZABLE OPERANDS - THE NAME
//* OF THE DATA SET, THE VOLUME ON WHICH IT IS TO RESIDE, AND HOW
//* MUCH SPACE TO ALLOCATE:
//*
//* - CHANGE ?BBDSN TO THE NAME OF THE OUTPUT DATA SET YOU
//* WISH TO ALLOCATE. THIS IS THE NAME THAT MUST ALSO BE
//* SPECIFIED IN UBBPARM LIBRARY MEMBER MDZVSAMF.
//*
//* - CHANGE ?BBVOL TO THE VOLSER OF THE VOLUME YOU WISH TO
//* ALLOCATE THE DATA SET ON.
//*
//* - IF YOU WISH TO OVERRIDE THE VALUES SPECIFIED FOR THE
//* PRIMARY EXTENTS AND SECONDARY EXTENTS, DO SO IN THE CYL
//* OPERAND ON LINE 1.
//*
//* LINE 3 CONTAINS OPERANDS THAT MUST BE SPECIFIED AS SHOWN:
//* INDEXED KEYS(88,0) SHR(2,3) AND RECSZ(300,2048)
//*
//* LINE 4 CONTAINS OPERANDS THAT ARE RECOMMENDED BUT WHICH
//* CAN BE CHANGED IF SO DESIRED:
//*
//* RCVY - RECOVERY ASSURES THAT THERE WILL BE AN END OF
//* FILE MARK IF FAILURE OCCURS DURING INITIAL LOAD.
//*
//*
//* FREESPACE - ('CIPERCENT' 'CAPERCENT') SPECIFIES THE AMOUNT OF
//* SPACE THAT IS TO BE LEFT FREE AFTER ANY ALLOCATION
//* AND AFTER ANY SPLIT OF CONTROL INTERVALS (CIPERCENT)
//* (CIPERCENT) AND CONTROL AREAS (CAPERCENT).
//*
//*
//*
//* END OF INSTRUCTIONS.
//*
//*--------------------------------------------------------------------
//*
//CMFJVSAM EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DEFINE CLUSTER ( NAME(?BBDSN) -
CYL(10,10) VOL(?BBVOL) -
INDEXED KEYS(80,0) SHR(2,3) RECSZ(300, 2048) -
RCVY FREESPACE(50,50))
/*

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments