10. MODIFICATION › 10.4 Output Exits
10.4 Output Exits
This section provides an in-depth description of the CA MICS
Web Analyzer standard output processing exits that are
invoked during phase 2 of the DAILY update processing flow.
The exits are organized by information area.
Each exit description includes the user exit name, title, a
description of its purpose, when it is invoked, and whether
it has an interface to CA MICS Accounting and Chargeback. It
also shows what data elements are available and any special
considerations to be aware of.
+---------+
| USRSWPR | WebSphere Performance File Exit
+---------+
DESCRIPTION: USRSWPR allows access to the data elements used
to build the records in the WebSphere Performance File.
INVOCATION: This exit gains control immediately prior to the
output of records to the Web Performance File.
ACCOUNTING INTERFACE: No interface is provided.
USES: This exit is used to add or change data elements, or
to delete observations from the WebSphere Performance File.
This file is built from the SMF Type 103 Records (subtype 2).
The location of the self-defining section of the WebSphere
Performance data is found at offset 24 ('18'X).
ELEMENTS AVAILABLE: All elements in the WebSphere
Performance File.
CODING RESTRICTIONS: Refer to the CA MICS System
Modification Guide, Section 4.3.2.2.
+---------+
| USRSSAF | WAS Server Activity File
+---------+
DESCRIPTION: USRSSAF allows access to the data elements used
to build the records in the WAS Server Activity File.
INVOCATION: This exit gains control immediately prior to the
output of records to the WAS Server Activity File.
ACCOUNTING INTERFACE: The CA MICS Accounting and Chargeback
interface follows the invocation of this user exit in a later
step while creating the WEBSAF file in the DETAIL database.
If you decide to eliminate data, you may affect the content
of the WEBSAF file and the accounting information for your
system.
USES: This exit is used to add or change data elements, or
to delete observations from the WAS Server Activity File.
This file is built from the SMF Type 120 Records (subtype 1).
The location of the self-defining section of the WAS Server
Activity File is found at offset 40 ('28'X).
ELEMENTS AVAILABLE: All elements in the WAS Server Activity
File.
CODING RESTRICTIONS: Refer to the CA MICS System
Modification Guide, Section 4.3.2.2.
+---------+
| USRSSIF | WAS Server Interval File
+---------+
DESCRIPTION: USRSSIF allows access to the data elements used
to build the records in the WAS Server Interval File.
INVOCATION: This exit gains control immediately prior to the
output of records to the WAS Server Interval File.
ACCOUNTING INTERFACE: No interface is provided.
USES: This exit is used to add or change data elements, or
to delete observations from the WAS Server Interval File.
This file is built from the SMF Type 120 Records (subtype 3).
The location of the self-defining section of the WAS Server
Interval File is found at offset 40 ('28'X).
ELEMENTS AVAILABLE: All elements in the WAS Server Interval
File.
CODING RESTRICTIONS: Refer to the CA MICS System
Modification Guide, Section 4.3.2.2.
+---------+
| USRSMIJ | J2EE Method Interval File
+---------+
DESCRIPTION: USRSMIJ allows access to the data elements used
to build the records in the J2EE Method Interval File.
INVOCATION: This exit gains control immediately prior to the
output of records to the J2EE Method Interval File.
ACCOUNTING INTERFACE: No interface is provided.
USES: This exit is used to add or change data elements, or
to delete observations from the J2EE Method Interval File.
This file is built from the SMF Type 120 subtype 6 records.
The location of the self-defining section of the J2EE Method
Interval File is found at offset 40 ('28'X).
ELEMENTS AVAILABLE: All elements in the J2EE Method Interval
File.
CODING RESTRICTIONS: Refer to the CA MICS System
Modification Guide, Section 4.3.2.2.
+---------+
| USRSHTP | HTTP Session Manager Interval File
+---------+
DESCRIPTION: USRSHTP allows access to the data elements used
to build the records in the J2EE Method Interval File.
INVOCATION: This exit gains control immediately prior to the
output of records to the HTTP Session Manager Interval File.
ACCOUNTING INTERFACE: No interface is provided.
USES: This exit is used to add or change data elements, or
to delete observations from the HTTP Session Manager Interval
File. This file is built from the SMF Type 120 subtype 8
records. The location of the self-defining section of the
HttpSessionManager section is found at offset 52 ('28'X).
ELEMENTS AVAILABLE: All elements in the HTTP Session Manager
Interval File.
CODING RESTRICTIONS: Refer to the CA MICS System
Modification Guide, Section 4.3.2.2.
+---------+
| USRSSRV | WebContainer Servlet Interval File
+---------+
DESCRIPTION: USRSSRV allows access to the data elements used
to build the records in the WebContainer Servlet Interval
File.
INVOCATION: This exit gains control immediately prior to the
output of records to the WebContainer Servlet Interval File.
ACCOUNTING INTERFACE: No interface is provided.
USES: This exit is used to add or change data elements, or
to delete observations from the WebContainer Servlet Interval
File. This file is built from the SMF Type 120 subtype 8
records. The location of the self-defining section of the
Servlet section is found at offset 264 ('108'X) inside the
WebApplication interval section that is found at offset 64
('40'X).
ELEMENTS AVAILABLE: All elements in the WebContainer Servlet
Interval File.
CODING RESTRICTIONS: Refer to the CA MICS System
Modification Guide, Section 4.3.2.2.
+---------+
| USRSHPI | JVM Heap Interval File
+---------+
DESCRIPTION: USRSHPI allows access to the data elements used
to build the records in the JVM Heap Interval File.
INVOCATION: This exit gains control immediately prior to the
output of records to the JVM Heap Interval File.
ACCOUNTING INTERFACE: No interface is provided.
USES: This exit is used to add or change data elements, or
to delete observations from the JVM Heap Interval File. This
file is built from the SMF Type 120 subtype 3 records. The
location of the self-defining section of the JVM heap section
is found at offset 8 ('8'X) inside the Server region section
that is found at offset 52 ('34'X).
ELEMENTS AVAILABLE: All elements in the WebContainer Servlet
Interval File.
CODING RESTRICTIONS: Refer to the CA MICS System
Modification Guide, Section 4.3.2.2.
+---------+
| USRSAGL | Agent Log File Exit
+---------+
DESCRIPTION: USRSAGL allows access to the data elements used
to build the records in the Agent Log File.
INVOCATION: This exit gains control immediately prior to the
output of records to the Agent Log File.
ACCOUNTING INTERFACE: No interface is provided.
USES: This exit is used to add or change data elements, or
to delete observations from the Agent Log File Exit. This
file is built from the WebSphere Agent Log data.
ELEMENTS AVAILABLE: All elements in the Agent Log File.
CODING RESTRICTIONS: Refer to the CA MICS System
Modification Guide, Section 4.3.2.2.
+---------+
| USRSERL | Error Messages Log File Exit
+---------+
DESCRIPTION: USRSERL allows access to the data elements used
to build the records in the Error Messages Log File.
INVOCATION: This exit gains control immediately prior to the
output of records to the Error Messages Log File.
ACCOUNTING INTERFACE: No interface is provided.
USES: This exit is used to add or change data elements, or
to delete observations from the Error Messages Log File
Exit. This file is built from the WebSphere Error Log data.
ELEMENTS AVAILABLE: All elements in the Error Messages Log
File.
CODING RESTRICTIONS: Refer to the CA MICS System
Modification Guide, Section 4.3.2.2.
+---------+
| USRSRFL | Referer Log File Exit
+---------+
DESCRIPTION: USRSRFL allows access to the data elements used
to build the records in the Referer Log File.
INVOCATION: This exit gains control immediately prior to the
output of records to the Referer Log File.
ACCOUNTING INTERFACE: No interface is provided.
USES: This exit is used to add or change data elements, or
to delete observations from the Referer Log File Exit. This
file is built from the WebSphere Referer Log data.
ELEMENTS AVAILABLE: All elements in the Referer Log File.
CODING RESTRICTIONS: Refer to the CA MICS System
Modification Guide, Section 4.3.2.2.
+---------+
| USRSSAL | Server Access Log File Exit
+---------+
DESCRIPTION: USRSSAL allows access to the data elements used
to build the records in the Server Access Log File.
INVOCATION: This exit gains control immediately prior to the
output of records to the Server Access Log File.
ACCOUNTING INTERFACE: The CA MICS Accounting and Chargeback
interface follows the invocation of this user exit in a later
step while creating the WLGSAL file in the DETAIL database.
If you decide to eliminate data, you may affect the content
of the WLGSAL file and the accounting information for your
system.
USES: This exit is used to add or change data elements, or
to delete observations from the Server Access Log File Exit.
This file is built from the WebSphere Server Access Log, FRCA
Access Log, Proxy Access Log, and Proxy (Cache) Log data.
ELEMENTS AVAILABLE: All elements in the Server Access Log
File.
CODING RESTRICTIONS: Refer to the CA MICS System
Modification Guide, Section 4.3.2.2.
