8. CA MICS NSM Integration (MTI) › 8.5 Integration Checklists › 8.5.2 Creating an MTI Component
8.5.2 Creating an MTI Component
This checklist is used to create an MTI component from NSM
Systems Performance data. This data is transferred to the
z/OS system using the CA MICS Data Transfer program (see PIOM
Section 4.7).
Before creating an MTI component, the input data should be
configured to contain the resource subtypes that will be
collected by MTI.
Use this checklist one time for each MTI component.
*********************************************************
* *
* ! ! ! W A R N I N G ! ! ! *
* *
* IF YOU ARE GENERATING MULTIPLE MTI COMPONENTS, YOU *
* MUST COMPLETE THIS CHECKLIST FOR EACH MTI COMPONENT *
* BEFORE GENERATING A NEW COMPONENT. *
* *
* The MTICREAT process does not add file definitions *
* to CA MICS. This is only done AFTER the cccCGEN is *
* completed. *
* *
* To avoid unpredictable results when generating *
* multiple MTI components, the cccCGEN for the first *
* component MUST be run before running MTICREAT for *
* the next component. *
* *
*********************************************************
___1. Select a name for the new MTI component. Component
names are three characters in length, start with a 'U'
or 'Z', and cannot be an existing component,
information area, or file name.
___2. Select the input that will be used by the new
component. Record the data set names. This
information will be used in the next step.
NOTE: The INPUTCSV DD does NOT support concatenated
datasets.
NSM data used by MTI is supplied via MICSXFR (CA MICS
Data Transfer). Section 4.7 of the PIOM provides
instructions for installing MICSXFR. Once the utility
is installed, refer to its online help system for
information on using the MICSXFR.
___3. Edit sharedprefix.MICS.CNTL(MTICREAT).
Specify the name of the new MTI component (selected in
Step 1) in the EXEC statement SYSPARM= parameter.
Optionally, you can specify the step number for the new
MTI component by adding it after the component name
(e.g., SYSPARM='UZZ 151'). The step number can be any
number between 150 through 190 that has not already
been used. If there is a concern about eventually
using most or all of the numbers in this range, one
should define multiple information areas within a user
component wherever it is possible.
Update the INPUTCSV DD with the input data set
information from Step 2.
NOTE: The INPUTCSV DD does NOT support concatenated
datasets.
NOTE: The MTICREAT job can be very resource intensive.
Make sure that MTICREAT runs in a jobclass that
will allow one or more minutes of CPU time.
Submit the job and make sure that all steps complete
with a condition code of zero and there are no error
messages in any of the MICSLOGs.
*******************************************************
* *
* If the MTICREAT job fails in the JCLGEN step, it *
* cannot be restarted because of CA MICS internal *
* locking mechanisms. If this situation occurs, a *
* JCLGENUC must be manually run to complete the *
* MTICREAT process. *
* *
* Edit sharedprefix.MICS.PARMS(JCLGENUC) and remove *
* all lines. Copy sharedprefix.MICS.PARMS(JCL$0ccc) *
* where ccc is the component name you selected into *
* this member. Save the member and exit. *
* *
* Edit sharedprefix.MICS.CNTL(JCLGENUC). Submit *
* the job and ensure it completes with a return *
* code of zero. *
* *
*******************************************************
___4. (Optional) Run Shared MICF Inquiry MTILD3.
This inquiry provides a list of all machine names
encountered to date. This information is useful
for creating entries in prefix.MICS.PARMS(SYSID) and
the optional prefix.MICS.PARMS(cccSYSID) exit.
___5. Proceed with the checklist in PIOM Section 3.8.2 for
installing the new component into an existing database
unit, or the checklist in PIOM Section 3.8.3 for
installing the new component into a new database unit.
