With system availability monitoring (SAM), you can be notified if a CICS® system is not active at any point
during its expected hours of operation. You can also be notified if any of
the following conditions should start or stop:
- One or more CICS/ESA dynamic storage areas become short on storage (SOS).
- A CICS/ESA system dump (SYSDUMP) is taken. For CICS/ESA 3.3 or later,
this condition indicates that an MVS™ SVC dump has been requested.
- A CICS/ESA transaction dump (TRANDUMP) is taken.
- The CICS system has reached the maximum number of tasks (MAXTASK) it is allowed
at any one time.
- One or more resources have impacted the processing of a CICS/ESA application
(STALL).
A STALL condition occurs when resource
contention impacts the processing of application tasks. Parameters you specify
in the MAS startup JCL determine when a CICSPlex® SM STALL message is issued.
You can set the parameters conservatively, so that you receive notification
while the system is still functioning, even though resource contention is
having a serious impact.
Resolution of a STALL condition may prevent
a more serious situation (such as an SOS or MAXTASK) from occurring. For example,
a lack of temporary storage could prevent a task from completing and trigger
a STALL condition.
For more information about the STALL parameters
and a list of possible stall conditions, see CICS Transaction Server for z/OS® Installation Guide.
For more information about CICS/ESA suspend classes, see the CICS/ESA Problem Determination Guide.
If the CICS system becomes unavailable, or if one of the above conditions
occurs, a severity level is assigned and the appropriate CICSPlex SM messages are
issued. These messages, which are prefixed with EYUPN, are described in the CICSPlex SM Messages and Codes book.
This section describes the default severity levels and actions associated
with each condition for which system availability monitoring produces a notification.
- System unavailable
-
- Event
- Yes
- Event Severity
- VHS (very high severe)
- Event View
- n/a
- Priority
- 255
- Event Text
- Currently unavailable
- External Message
- Yes
- Enter Text
- Currently unavailable
- Exit Text
- Currently Available
- Alert
- No
- Enter Text
- Currently unavailable
- Exit Text
- Currently Available
- Short on storage (SOS)
-
- Event
- Yes
- Event Severity
- HS (high severe)
- Event View
- CICSDSA
- Priority
- 255
- Event Text
- dsname SOS at hh:mm:ss
- External Message
- Yes
- Enter Text
- dsname SOS at hh:mm:ss
- Exit Text
- dsname SOS at hh:mm:ss
- Alert
- No
- Enter Text
- dsname SOS at hh:mm:ss
- Exit Text
- dsname SOS at hh:mm:ss
- System dumps (SYSDUMP)
-
- Event
- Yes
- Event Severity
- VHS (very high severe)
- Event View
- SYSDUMP
- Priority
- 255
- Event Text
- ID=dumpid tranid userid termid
- External Message
- Yes
- Enter Text
- ID=dumpid tranid userid termid
- Exit Text
- ID=dumpid tranid userid termid
- Alert
- No
- Enter Text
- ID=dumpid tranid userid termid
- Exit Text
- ID=dumpid tranid userid termid
- Transaction dumps (TRANDUMP)
-
- Event
- Yes
- Event Severity
- HW (high warning)
- Event View
- TRANDUMP
- Priority
- 128
- Event Text
- ID=dumpid tranid userid termid
- External Message
- Yes
- Enter Text
- ID=dumpid tranid userid termid
- Exit Text
- ID=dumpid tranid userid termid
- Alert
- No
- Enter Text
- ID=dumpid tranid userid termid
- Exit Text
- ID=dumpid tranid userid termid
- Maximum number of tasks (MAXTASK)
-
- Event
- Yes
- Event Severity
- HS (high severe)
- Event View
- TASK
- Priority
- 255
- Event Text
- MAXTASK at hh:mm:ss
- External Message
- Yes
- Enter Text
- MAXTASK at hh:mm:ss
- Exit Text
- MAXTASK at hh:mm:ss
- Alert
- No
- Enter Text
- MAXTASK at hh:mm:ss
- Exit Text
- MAXTASK at hh:mm:ss
- System busy (STALL)
-
- Event
- Yes
- Event Severity
- VHS (very high severe)
- Event View
- TASK
- Priority
- 255
- Event Text
- type STALLED at hh:mm:ss
- External Message
- Yes
- Enter Text
- type STALLED at hh:mm:ss
- Exit Text
- type STALLED at hh:mm:ss
- Alert
- No
- Enter Text
- type STALLED at hh:mm:ss
- Exit Text
- type STALLED at hh:mm:ss
Depending on the level of system availability monitoring you want to activate, you can
perform either or both of the following actions:
- To monitor system activity:
- In the WUI, use the CICS system definition view.
To open this view from the main menu click Administration
views-->System availability monitoring administration views-->CICS
system definitions.
- In the EUI, use the CICSSYS view.

These views allow you to permanently change the CICSPlex SM definition of
the CICS system. You need to identify:
- The primary CMAS. This is the CMAS that is assigned the task of monitoring
the availability of the CICS system. (For additional information, see Identifying primary CMASs.)
- The time period definition that identifies the hours during which you
expect the CICS system to be running.
To monitor a CICS system for the predefined conditions, use the CICS system definition detailed view to set the Real time analysis status field to either SAM or YES. In the EUI you
use the CICSSYS or MAS view to set the Analysis Active field on the Analysis
Attributes panel.
If any of the severity levels or actions shown in Default notification values is
not appropriate for your use, you can change it for a specific CICS system using
the CICSSYS or MAS view. If you want the new default to apply to multiple CICS systems,
you can, instead, modify the analysis specification with which the CICS systems
are associated.
As illustrated in the example shown in Figure 1, you can
implement system availability monitoring by simply modifying the appropriate CICSPlex SM definition of
a CICS system.
In this example, the definition of the CICS system named EYUMAS1A shows that:
- System activity monitoring is to occur because a primary CMAS (EYUCMS1A)
and a time period definition (PRIME) are identified.
- Monitoring of predefined conditions is to occur because the Analysis Active
field is set to YES.
- If the predefined condition short-on-storage (SOS) occurs, the default
action and severity level are to be used.
This example also illustrates how other predefined conditions might
be handled:
- For system dumps (SYSDUMP), the severity level is to be set to VHS (very
high severe) and an action identified as SYSDEF1 is to be performed.
- For transaction dumps (TRANDUMP), no action is to be taken and no severity
level is to be set.
[[ Contents Previous Page | Next Page Index ]]