We have 3 clients in Central America and there are more than 10 CICS partitions in use.
The type of alarm or situation that needs to be created is based on Abend codes; search for a code and when it appears, trigger a situation.
Currently, we have CICS partition monitoring, and an important element in monitoring transactions within a CICS partition is identifying the transactions and the ABENDCODE. Currently, these are viewed on the TEPS portal, but it is NOT possible to create alert/situation scenarios when errors occur.
We request the ability to create situations from TEPS or Grafana GUI in order to determine the failures.
CICSplex Transaction Umbrella Data attribute group
Last Updated: 2026-01-29
The CICSplex Transaction Umbrella Data attributes report the contents of the three OMEGAMON Umbrella fields that can be updated from within an application. Use the CICSplex Transaction Umbrella Data attributes to view the contents of the OMEGAMON Umbrella fields.
* Slack bytes to provide doubleword alignment.
ABEND Code Indicates the transaction abnormal termination code, if applicable.
CICS Region Name Indicates the job name or modify ID of the CICS region being monitored. Each CICS region in a z/OS operating system has a unique name. This name is an alphanumeric string, with a maximum of eight characters, and case-sensitive. CICS region names are always in uppercase characters.
CPU Time Indicates the amount of accumulated CPU time (in seconds) used by this task.
End Time Indicates the time of day when the transaction completed.
History Token Indicates the parameter for history record selection. Internal use only.
Origin Node Is the combination of z/OS System ID (SMFID) and CICS region name. The value format is an alphanumeric string, maximum 32 bytes, and case-sensitive.
When a situation is true, the system compares the origin node name in the attribute to the names of managed systems assigned to the item. If the origin node name matches the name of a managed system, the status of the item changes accordingly. If the names of the origin node and the managed systems do not match, the status of the item remains unchanged.
Program ID Indicates the CICS program name or the umbrella name.
Response Time Indicates the task response time (in seconds) of the transaction, the difference between the time the performance record was created and the start of the record.
System ID Indicates the four character name that uniquely identifies an active z/OS operating system within a given CICSplex. The value format is an alphanumeric string, maximum four characters, and case-sensitive. z/OS System IDs are always in uppercase characters.
Task Number Is the number sequentially assigned by CICS to uniquely identify each task.
Transaction ID Is the four-character name of the transaction.
Umbrella Program ID Indicates the program ID assigned to this transaction by the application calling OMEGAMON's Umbrella transaction services.
Umbrella Transaction ID Indicates the transaction ID assigned to this transaction by the application calling OMEGAMON's Umbrella transaction services.
User ID Indicates the user's eight-character CICS logon ID.
User Work Area (Hex) Is the contents of the 32 byte Umbrella user data work area in hexadecimal format, which might be used by the application for general storage purposes; the contents are not used by OMEGAMON.
User Work Area Is the contents of the 32 byte Umbrella user data work area, which might be used by the application for general storage purposes; the contents are not used by OMEGAMON.
