|
|
|
This report produces a tabular summary of CP system use of
IUCV (Inter-User Communication Vehicle), and user usage of
both IUCV and VMCF (VM Communication Facility), for the
reporting period specified as run-time execution parameters.
INTENDED USE:
To provide an overview of the utilization of system
services, such as *MSG, and *BLOCKIO, as well as user
activity using IUCV and VMCF. The report can be utilized
to monitor the data transfer activity, and to determine
whether an inordinate number of transfer failures are
occurring. Such failures may point to problem areas in
need of further analysis.
FORMAT:
A tabular report in which the first column lists either a
CP system service name that makes use of IUCV, 'USER
IUCV', or 'USER VMCF'. The next two columns contain the
number of successful data transmissions sent to and from a
given system service, or users. The last column displays
the number of failed transmissions that took place during
the reporting period.
An example of this report is shown in Figure 3-7.
INQUIRY ID:
Tabular Report: VMXTX6
DATA SOURCE (File/Timespan):
VMXSGP01 - DETAIL
DATA ELEMENTS USED:
SGPSTxxx - Successful Data Transfers By IUCV to Service
xxx
SGPSTUSR - Successful Data Transfers By IUCV to a User
SGPSTVMC - Successful Data Transfers By VMCF to a User
SGPSFxxx - Successful Data Transfers By IUCV from Service
xxx
SGPSFUSR - Successful Data Transfers By IUCV from a User
SGPSFVMC - Successful Data Transfers By VMCF from a User
SGPUTxxx - Unsuccessful Data Transfers By IUCV to Service
xxx
SGPUTUSR - Unsuccessful Data Transfers By IUCV to a User
SGPUTVMC - Unsuccessful Data Transfers By VMCF to a User
Where service xxx has the following values:
MSA - *MSGALL
MSG - *MSG
RPI - *RPI
BLK - *BLOCKIO
MON - *MONITOR
SIG - *SIGNAL
SPL = *SPL
ACC = *ACCOUNT
CRM = *CRM
IDN = *IDENT
LOG = *LOGREC
SYM = *SYMPTOM
CALCULATIONS:
The detail records for the user specified reporting period
are extracted from the XDV files and summarized, using
CA MICS summarization, across the reporting period,
producing one record per day per system, for the entire
reporting period. Records are then produced for each
system service, and new data elements are created to
contain the service name (SERVICE), the successful send
tos (SENDTO), the successful send froms (SENDFROM), and
the unsuccessful send tos (FAILED). The items in
parentheses are column heads in the report found in Figure
3-17. The names of these elements follow the standards
established in the section DATA ELEMENTS USED, above.
USAGE CONSIDERATIONS:
None
+------------------------------------------------------------------------------+ | Detail VM IUCV/VMCF Summary Report | | Product Manufacturing Corporation | | | |INQUIRY: VMXTX6 RUN DATE: 2FEByy | | System ID = VM ,Day = 21 | | DATA TRANSFERS | | SERVICE SENT TO SENT FROM FAILED | | | | *ACCOUNT 0 1,437 0 | | *BLOCKIO 641 641 0 | | *CRM 0 0 0 | | *IDENT 0 0 0 | | *LOGREC 0 5 0 | | *MONITOR 2,406 2,406 0 | | *MSG 0 5,905 0 | | *MSGALL 0 0 0 | | *RPI 5,933 6,944 0 | | *SIGNAL 13,020 13,020 0 | | *SPL 0 13,020 0 | | *SYMPTOM 0 0 0 | | USER IUCV 148,835 13,020 0 | | USER VMCF 18,376 18,376 0 | | | | SYSID/DAY 189,211 74,774 0 | | | | | | Total 189,211 74,774 0 | | | | | | | | | | | | | | | | | +------------------------------------------------------------------------------+
Figure 3-7. Detail VMX IUCV/VMCF Summary Report
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |