CICS transaction groupings values
The standard fields are:
- TRAN—A CICS transaction is the one- to four-character identifier that CICS users type in during CICS work sessions.
- TERM—A CICS terminal is the four-character address of the terminal where the transaction was initiated. System, mirror (CSM*), and other types of transactions feature a CICS-generated TERM that has nothing to do with a particular terminal address. Having UIE group your transactions by TERM can be useful in a situation where you have field offices and you want to study the performance and capacity impact of changes in activity at one or more remote sites.
- PROGRAM—A CICS program is the eight-character program name that was used by the CICS transaction.
- USERID—A CICS userid is the eight-character value that identifies the user that executes a CICS transaction. Having UIE group your transactions by USERID can be useful in a situation where you want to study the performance and capacity impact of changes in activity for a group of users.
- USERFLD—The user field is a CICS user-defined character field whose value is supplied by user application code. In the IBM CMP monitor, the user field can be 1 to 256 characters. In BMC AMI Ops Monitor for CICS, the user field can be 1 to 28 characters. In TMON for CICS data, the user field can be 1 to 16 characters. UIE can select up to 16 characters from any user field. The starting offset and length of the data that is to be selected from the user field can be specified in the PRIMEKEY/SECONDKEY field definition in the APPLGROUPING command.
- TRANTYPE—The transaction type is a CICS defined value that identifies the type of transaction.
- JOB—The job name.
- NONE—Indicates that nothing is required in this field.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*