|
|
|
Note: This utility only executes at SAS Version 9 or later.
---------------- Missing Data Element Report Utility ----------------- Command ===>
This utility generates a report across all units, timespans and online files within a component, and reports on those elements that contain missing values 100% of the time. These elements may be candidates for deactivation, but we strongly urge you to use caution in deactivating elements via cluster codes assigned to releases that you may not have migrated to yet. To begin, enter a 3-character component identifier below. You will get an opportunity to exclude units on a subsequent panel. CA MICS Component ===> ___ (ccc)
. . . . . . . . . . . . . . . . . . . . . . . . . .
Select a component, then press ENTER to continue. A list of units where the component is installed is presented to allow you to EXCLUDE units from the analysis. ------------------- Missing Data Elements Report Utility --- Row 1 to n of n Command ===>
Line Commands: X = Exclude unit from the report Cmd Unit ID Name Label - ------- -------- ---------------------------------------------- _ A UNITA Label for UNIT A _ P UNITP Label for UNIT P _ X UNITX Label for UNIT X _ Z UNITZ Label for UNIT Z _ 0 UNIT0 Label for UNIT 0
. . . . . . . . . . . . . . . . . . . . . . . . . .
The Missing Data Elements Report Utility accepts a CA MICS
component identifier (for example, RMF) and identifies all
units in the CA MICS complex where the component is
installed. The database files associated with the identified
units are examined to identify any data elements that have
missing values in all timespans where the data elements are
active.
After the analysis is complete, a report is produced:
o Section 1 shows component files where every data element
has a non-missing value in at least one observation.
o Section 2 shows component files with data elements that
have missing values in all observations.
To produce the Missing Data Elements Report, choose option 10
from the CA MICS Administrator Utilities menu (MWF 5;4;A).
Enter the CA MICS component as described below and press
ENTER to begin report generation.
CA MICS Component Required - Enter one of the
following three-character (ccc)
component identifiers.
ACT AUM AST BAS CIC DB2
DEX HSM IDM IMS MQS MTI
PWR RMF SMF SNT SRL TDM
TLM TSO VCA VMC VTS WEB
You are provided with a list of units where the component is
installed. By default, the databases of all units are
examined. To exclude a unit from consideration, place an "X"
next to the unit to be excluded. Then press ENTER to refresh
the list of units. When the list is complete, either press
PF3 or type the END command to generate the report JCL.
Note: CA MICS data elements are activated at the complex
level. In general, you should allow all unit databases to be
selected. Only exclude units if they contain data that is not
representative of your normal configuration. Consider a
situation where the component you have selected is deployed
in three units, A, B, and P, but is no longer used in unit
B. If the component files in unit B are still in that unit's
database, the data may not represent your current cccGENIN
configuration and the data values may not represent your
current environment. In this example, you would want to
exclude unit B from the analysis.
After making any JCL modification (for example, update
JOBCARD), enter the SUBMIT command to submit the job.
The report that is generated has two possible sections:
Section 1: Files where every data element has a value in at
least one observation.
Section 2: Files where at least one data element has missing
values in all timespans and observations.
Note: If no component files meet the section criteria, that
report section is not generated. For example, if all files
contain at least one data element that has missing values in
all timespans and observations, section 1 will not be
produced.
If a particular file has zero (0) observations in all
timespans, it is not included in the report, but will be
noted in the MICSLOG as shown below:
BAS00196I ===> File: HARCCU **NO OBS**
If all component files have zero (0) observations in all
timespans, MICSLOG will note that the report will not be
generated.
Each element listed in Section 2 shows the units and
timespans where the data element was present and found to
have missing values in every database observation.
As the job is running, the MICSLOG shows progress as first
the individual databases are examined for component files,
and next as each component file is examined for data elements
with missing values.
A sample of REPORT SECTION 1, executed for the CICS component,
is shown below. Section 1 shows files where every data element,
across all file instances where the elements were active, had
at least one observation with a non-missing value. These files
are ideally configured.
CA MICS Missing Data Element Report Complex sharedprefix: PROD.MICS Page 001 Component Analyzed: CIC Run Date: 17FEByy +******************************************************************************************************+ + Files With 100% Populated Data Elements + + Each Data Element in the Listed Files has at Least One Observation with a Non-Missing Value + + + + FILE FILE LABEL + + ------ -------------------------------------------- + + CICCDC CICS Dictionary File + + CTGGSA Gateway Server Activity + +******************************************************************************************************+
A sample of the beginning of REPORT SECTION 2, executed for the CICS component, is shown below. Section 2 shows files where at least one data element had missing values in every observation across all file instances where the element is active. These file elements should be reviewed to determine if you should keep them activated.
CA MICS Missing Data Element Report Complex sharedprefix: PROD.MICS Page 002 Component Analyzed: CIC Run Date: 17FEByy +******************************************************************************************************+ + Files with at Least One Data Element with Missing Values in ALL Observations + + Every Data Element Listed Below has Missing Values in each File Observation + + + +******************************************************************************************************+ + FILE FILE LABEL + + ------ -------------------------------------------- + + CICCIN CICS Incident File + + + + ELEMENT DATA ELEMENT LABEL XDWMY UNIT IDs + + -------- -------------------------------------------- ----- ------------------------------------ + + OPERID Terminal Operator Initials X.... Z0 + + TERMINAL CICS Terminal ID X.... Z0 + +******************************************************************************************************+ + + +******************************************************************************************************+ + FILE FILE LABEL + + ------ -------------------------------------------- + + CICCSU CICS User Activity File + + + + ELEMENT DATA ELEMENT LABEL XDWMY UNIT IDs + + -------- -------------------------------------------- ----- ------------------------------------ + + CSUCHMDC No. CICS Dispatcher Change Modes XD.M. A0 + + CSUCONWT DB2 Connection Wait Time .D.M. A0 + + CSUDB2RC Total No. DB2 Requests .D.M. A0 + + CSUDB2WT DB2 Wait Time .D.M. A0 + + CSUERSTM Excessive Response Time Total .D.M. AZ0 + + CSUETRN Excessive Transactions Processed .D.M. AZ0 + + CSUIPCNM TCP/IP Connection Name X.... 0 + + CSUMXETM Max Excessive Response Time .D.M. AZ0 + + CSURDQWT DB2 ReadyQ Wait Time .D.M. A0 + + CSUSUSDT Unidentified Suspend Wait Time .D.M. AZ + + CSUTCLAS Transaction Class at Task Creation X.... 0 + + CSUTCSTG TIOA Storage Allocated to Terminal XD.M. A0 + + OPERID Terminal Operator Initials X.... 0 + +******************************************************************************************************+ + Analysis of file: CICCSX + + ELEMENT DATA ELEMENT LABEL TSPNS UNITS + + -------- -------------------------------------------- ----- -------------------------- + + CSYAMXTC Total Task During Active Max Task XDWM. AZ + + CSYAVAMX Average Active Task Limit .DWM. A0 + + CSYAVLDS Average Loader Suspend Time .DWM. A0 + + CSYAVNIU Average NIU Queue Membership Time .DWM. A0 + + CSYCOST Processing Charges XDWM. AZ0 +
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |