

5. FILES › 5.2 IMS Information Area Files › 5.2.5 IMS Incident File (IMSINC) › 5.2.5.3 IMSINC Usage Considerations
5.2.5.3 IMSINC Usage Considerations
This section identifies any special considerations or
techniques related to using the IMSINC file. Additionally,
sample retrieval examples are provided to help you use of
this file.
In the examples, a SAS macro variable is used to specify the
DDname part of the CA MICS file name. These macro variables
are a standard part of CA MICS and are available for all
files. The macro variable name has the form &diiit, where d
is the database identifier, iii is the information area
name, and t is the timespan. For the examples, a database
identifier of P is used. The identifier is installation
dependent, so you should find out what the identifiers are at
your installation.
Special Considerations/Techniques
1. The following data elements only have meaning when using
the IMSINC file in the DETAIL time-span as they lose
significance once summarization has been performed:
IMSVER - IMS Version
PTERM - Physical Terminal Number
DATABASE - Data Base Name
LINE - Terminal Line Identification
PSBNAME - Program Name
TRANSACT - Transaction Name
LTERM - Logical Terminal
INCREGIN - Region Identifier
INCABEND - Abnormal Termination Code
2. The data elements STARTTS and ENDTS have special meanings
when used in the DETAIL time-span. Their purpose in the
DETAIL time-span is described below:
o STARTTS represents the monitored IMS incident start
time, when available.
o ENDTS represents the monitored IMS incident end time.
Retrieval Examples
1. Generate a horizontal bar graph of yesterday's incident
counts, by hour:
PROC CHART DATA=&PIMSX..IMSINC01;
HBAR HOUR / SUMVAR=INCCOUNT DESCRETE;
RUN;
2. Generate a frequency table of the occurrence of incidents
by incident code. Use month-to-date data.
PROC FREQ DATA=&PIMSM..IMSINC00;
TABLES INCCODE / NOROW NOCOL; WEIGHT INCCOUNT;
RUN;
Copyright © 2014 CA.
All rights reserved.
 
|
|