XMNOUT is invoked at the following event points:
- Before an exception class monitoring record is passed to SMF
- Before a performance class monitoring record is written to the performance
record buffer
- Before a transaction resource monitoring record is written to the transaction
resource record buffer
Note:
If performance class and transaction resource monitoring
are both active in your CICS® region, XMNOUT can be invoked twice for the same event.
For example, if the event is end-of-task and CICS has both performance class data and transaction
resource data to move to the appropriate buffer, XMNOUT is invoked once for
each monitoring record type.
You can use this exit to examine
the record, to suppress its output to SMF, or to change the data it contains.
You must be ensure that any changes you make do not conflict with the dictionary
description of the data.
You can also add data to performance class data records. To do this you
need to define dummy user event-monitoring points (EMPs) in the monitoring
control table (MCT) to reserve data fields of the required size and type.
- When invoked
- XMNOUT is invoked:
- Before an exception class monitoring record is written to SMF
- Before a performance class monitoring record is buffered for a later write
to SMF
- Before a transaction resource monitoring record is buffered for a later
write to SMF
- Exit-specific parameters
-
- UEPTRANID
- Address of the 4-byte transaction ID. This
field is not available at task termination.
- UEPUSER
- Address of the 8-byte user ID. This
field is not available at task termination.
- UEPTERM
- Address of the 4-byte terminal ID. This field is not available at task
termination.
- UEPPROG
- Address of the 8-byte application program name. This field is not available
at task termination.
- UEPDICT
- Address of the dictionary. The sequence of dictionary entries is mapped
by the DSECT generated from the macro DFHMCTDR. This field only has meaning
for performance class records. If the monitoring record type is exception
class (type 4) or transaction resource (type 5), this field is set to 0 (see
parameter UEPMRTYP).
- UEPDICTE
- Address of the fullword number of dictionary entries. This field only
has meaning for performance class records. If the monitoring record type is
exception class (type 4) or transaction resource (type 5), this field is set
to 0 (see parameter UEPMRTYP).
- UEPFCL
- Address of the field connector list, containing a series of halfword
connector values. This field only has meaning for performance class records.
If the monitoring record type is exception class (type 4) or transaction resource
(type 5), this field is set to 0 (see parameter UEPMRTYP).
- UEPFCLNO
- Address of the fullword number of field connectors. This field only
has meaning for performance class records. If the monitoring record type is
exception class (type 4) or transaction resource (type 5), this field is set
to 0 (see parameter UEPMRTYP).
- UEPMRTYP
- Address of the halfword monitoring record type. The monitoring record
type value can be one of the numbers shown in the following table:
Table 7.
Record type value |
Meaning |
3 |
Perfomance class monitoring record |
4 |
Exception class monitoring record |
5 |
Transaction resource monitoring record |
- UEPMRLEN
- Address of the fullword monitoring record length.
- UEPMREC
- Address of monitoring record, whose length is addressed by the parameter
UEPMRLEN.
- UEPSRCTK
- Address of the MVS™ workload manager service reporting class token for
the current transaction. If CICS support for MVS workload management is not available, this
token is null.
- UEPMPREC
- Address of the monitoring performance record. This field has meaning
only for performance class records. If the monitoring record type is exception
class (type 4) or transaction resource (type 5), this field is set to 0 (see
parameter UEPMRTYP). The performance record addressed by this parameter
must be mapped using the DFHMNTDS dsect, and must not be mapped using the
UEPDICT and UEPDICTE dictionary parameters.
- Return codes
-
- UERCNORM
- Continue processing.
- UERCBYP
- Suppress monitor record output.
- UERCPURG
- Task purged during XPI call.
- XPI calls
- WAIT_MVS can be used. Do not use any other calls.

[[ Contents Previous Page | Next Page Index ]]