Overview of Abend-AID health checker

The IBM Health Checker for z/OS can identify potential problems in your z/OS environment. It can check system or product parameters and system status against recommended settings. The IBM Health Checker for z/OS is structured as a framework that includes a health check started task and various separate check routines provided by IBM or other vendors. Abend-AID provides health checks for areas that could be potentially problematic. When these conditions are found, the Abend-AID checks provide detailed recommendations on how to correct the problem. The Abend-AID health checks also recommend best practices for using Abend-AID.

Abend-AID health checks

AA_BDCAS_STORAGE_USAGE

Check Owner:

CPWR_ABEND_AID

Check Name:

AA_BDCAS_STORAGE_USAGE

Description:

The check verifies that the region size of the BDCAS has provided sufficient storage.

Reason for Check:

BMC identifies storage requirements for the BDCAS. This health check reports on the storage allocated above and below the 16M line.

User Override of Default Values:

No

Parameters Accepted:

No

Reference:

For more information, see Virtual-memory-requirements-for-BDCAS.

Debug Support:

Not applicable

Verbose Support:Not applicable

Interval:

Once per hour. To change the interval, see Changing the Health Check Interval.

Messages:

This check issues the following messages:

• FDBHC0000I (successful)
• FDBHC0100I (information)
• FDBHC0101I (information)
• FDBHC0102E (exception)

Output:

When available BDCAS storage appears to be adequate, the AA_BDCAS_STORAGE_USAGE check produces the report shown in the following figure.

Sample AA_BDCAS_STORAGE_USAGE Successful Report

When available BDCAS storage appears to be low but not critical, the AA_BDCAS_STORAGE_USAGE check produces the report shown in the following figure.

Sample AA_BDCAS_STORAGE_USAGE Information Report

DCAS storage appears to be low but not critical, the AA_BDCAS_STORAGE_USAGE check produces the report shown in the figure below.

When available BDCAS storage appears to be very low and corrective action is needed, the AA_BDCAS_STORAGE_USAGE check produces the report shown in the following figure.

Sample AA_BDCAS_STORAGE_USAGE Exception Report

AA_TDCAS_STORAGE_USAGE

Check Owner:

CPWR_ABEND_AID

Check Name:

AA_TDCAS_STORAGE_USAGE

Description:

The check verifies that the region size of the TDCAS has provided sufficient storage.

Reason for Check:

BMC identifies storage requirements for the TDCAS. This health check reports on the storage usage above and below the 16M line.

User Override of Default Values:

No

Parameters Accepted:

No

Reference:

For more information, see Virtual-memory-requirements-for-BDCAS.

Debug Support:

Not applicable

Verbose Support:

Not applicable

Interval:

Once per hour. To change the interval, see Changing the Health Check Interval.

Messages:

This check issues the following messages:

• FDBHC0000I (successful)
• FDBHC0100I (information)
• FDBHC0101I (information)
• FDBHC0102E (exception)

Output:

When available TDCAS storage appears to be adequate, the AA_TDCAS_STORAGE_USAGE check produces the report shown in the following figure.

Sample AA_TDCAS_STORAGE_USAGE Successful Report

When available TDCAS storage appears to be low but not critical, the AA_TDCAS_STORAGE_USAGE check produces the report shown in the figure.

Sample AA_TDCAS_STORAGE_USAGE Information Report

When available TDCAS storage appears to be very low and corrective action is needed, the AA_TDCAS_STORAGE_USAGE check produces the report shown in the following figure.

Sample AA_TDCAS_STORAGE_USAGE Exception Report

AA_VIEWER_STORAGE_USAGE

Check Owner:

CPWR_ABEND_AID

Check Name:

AA_VIEWER_STORAGE_USAGE

Description:

The check verifies that the region size of the Abend-AID Viewer has provided sufficient storage.

Reason for Check:

BMC identifies storage requirements for the Abend-AID Viewer. This health check reports on the storage usage above and below the 16M line.

User Override of Default Values:

No

Parameters Accepted:

No

Reference:

For more information, see Virtual-memory-requirements-for-the-viewing-server.

Debug Support:

Not applicable

Verbose Support:

Not applicable

Interval

Once per hour. To change the interval, see Changing the Health Check Interval.

Messages:

This check issues the following messages:

• FDBHC0000I (successful)
• FDBHC0100I (information)
• FDBHC0101I (information)
• FDBHC0102E (exception)

Output:

When available Abend-AID Viewer storage appears to be adequate, the AA_VIEWER_STORAGE_USAGE check produces the report shown in  the following figure.

Sample AA_VIEWER_STORAGE_USAGE Successful Report

When available Abend-AID Viewer storage appears to be low but not critical, the AA_VIEWER_STORAGE_USAGE check produces the report shown in the following figure.

Sample AA_VIEWER_STORAGE_USAGE Information Report

When available Abend-AID Viewer storage appears to be very low and corrective action is needed, the AA_VIEWER_STORAGE_USAGE check produces the report shown in the following figure.

Sample AA_VIEWER_STORAGE_USAGE Exception Report

AA_BDCAS_DB2_CONNECTION

Check Owner:

CPWR_ABEND_AID

Check Name:

AA_BDCAS_DB2_CONNECTION

Description:

The check provides information about the Abend-AID connections to Db2.

Reason for Check:

Abend-AID connects to a Db2 subsystem to retrieve information about the abending program's SQL statements. When a connection cannot be established, information will be missing from the Abend-AID report.

User Override of Default Values:

No

Parameters Accepted:

No

Reference:

For more information, see the Db2 database support configuration tasks — upgrade section in the  Installation and Configuration Guide.

Debug Support:

Not applicable

Verbose Support:

Not applicable

Interval:

Once per hour. To change the interval, see Changing the Health Check Interval.

Messages:

This check issues the following messages:

• FDBHC0200I (successful)
• FDBHC0201I (information)
• FDBHC0202I (information)
• FDBHC0203E (exception)
• FDBHC0204E (exception)

Output:

When Abend-AID successfully connects to Db2, has not had any connections, or has been refreshed, the AA_BDCAS_DB2_CONNECTION check produces the report shown in the following figure.

Sample AA_BDCAS_DB2_CONNECTION Successful Report

When Abend-AID has not had any connection errors during the last interval, but has had connection errors during prior intervals, the AA_BDCAS_DB2_CONNECTION check produces the report shown in the following figure.

Sample AA_BDCAS_DB2_CONNECTION Information Report

When Abend-AID does not successfully connect to Db2 and the number of unsuccessful attempts has not increased by more than 10 during the last interval, the AA_BDCAS_DB2_CONNECTION check produces the report shown in the following figure.

Sample AA_BDCAS_DB2_CONNECTION Information Report

The first time Abend-AID does not successfully connect to Db2 and corrective action is needed, the AA_BDCAS_DB2_CONNECTION check produces the report shown in the following figure.

Sample AA_BDCAS_DB2_CONNECTION Exception Report

When Abend-AID does not successfully connect to Db2 after several attempts and corrective action is needed, the AA_BDCAS_DB2_CONNECTION check produces the report shown in the following figure.

Sample AA_BDCAS_DB2_CONNECTION Exception Report

AA_TDCAS_DB2_CONNECTION

Check Owner:

CPWR_ABEND_AID

Check Name:

AA_TDCAS_DB2_CONNECTION

Description:

The check provides information about the Abend-AID for CICS connections to Db2.

Reason for Check:

Abend-AID for CICS connects to a Db2 subsystem to retrieve information about the abending program's SQL statements. When a connection cannot be established, information will be missing from the Abend-AID for CICS report.

User Override of Default Values:

No

Parameters Accepted:

No

Reference:

For more information, see the Db2 database support configuration tasks — upgrade section in the Installation and Configuration Guide.

Debug Support:

Not applicable

Verbose Support:

Not applicable

Interval:

Once per hour. To change the interval, see Changing the Health Check Interval.

Messages:

This check issues the following messages:

• FDBHC0200I (successful)
• FDBHC0201I (information)
• FDBHC0202I (information)
• FDBHC0203E (exception)
• FDBHC0204E (exception)

Output:

When Abend-AID for CICS successfully connects to Db2, has not had any connections, or has been refreshed, the AA_TDCAS_DB2_CONNECTION check produces the report shown in the following figure.

Sample AA_TDCAS_DB2_CONNECTION Successful Report

When Abend-AID for CICS has not had any connection errors during the last interval, but has had connection errors during prior intervals, the AA_TDCAS_DB2_CONNECTION check produces the report shown in the following figure.

Sample AA_TDCAS_DB2_CONNECTION Information Report

When Abend-AID for CICS does not successfully connect to Db2 and the number of unsuccessful attempts has not increased by more than 10 during the last interval, the AA_TDCAS_DB2_CONNECTION check produces the report shown in the following figure.

Sample AA_TDCAS_DB2_CONNECTION Information Report

The first time Abend-AID for CICS does not successfully connect to Db2 and corrective action is needed, the AA_TDCAS_DB2_CONNECTION check produces the report shown in the following figure.

Sample AA_TDCAS_DB2_CONNECTION Exception Report

When Abend-AID for CICS does not successfully connect to Db2 after several attempts and corrective action is needed, the AA_TDCAS_DB2_CONNECTION check produces the report shown in the following figure.

 Sample AA_TDCAS_DB2_CONNECTION Exception Report

AA_SERVER_MAINTENANCE

Check Owner:

CPWR_ABEND_AID

Check Name:

AA_SERVER_MAINTENANCE

Description

The check identifies the maintenance dates for the Abend-AID common components, batch Abend-AID, and Abend-AID for CICS libraries that are used for the Viewing Server, BDCAS, and TDCAS.

Reason for Check:

This check is being provided to assist in identifying if cumulative maintenance should be applied.

User Override of Default Values:

No

Parameters Accepted:

No

Reference:

For more information, see BMC Support for details on the cumulative maintenance schedule and for information on receiving email notification.

Debug Support:

Not applicable

Verbose Support:

Not applicable

Interval:

Once at startup. To change the interval, see Changing the Health Check Interval.

Messages:

This check issues the following messages:

• FDBHC0300I (information)
• FDBHC0301I (information)
• FDBHC0302I (exception)

Output:

When the maintenance date is within six months of the current date, the AA_SERVER_MAINTENANCE check produces the report shown in the following figure. The description varies based on the startup parameters for the server. Each server type has the Common Components listed. The Abend-AID Viewer and BDCAS show Abend-AID. The Abend-AID Viewer and the TDCAS show Abend-AID for CICS.

Sample AA_SERVER_MAINTENANCE Information Report

When the maintenance date is not within six months of the current date, the check produces the report shown in the following figure. The description varies based on the startup parameters for the server. Each server type has the Common Components listed. The Abend-AID Viewer and BDCAS show Abend-AID. The Abend-AID Viewer and the TDCAS show Abend-AID for CICS.

Sample AA_SERVER_MAINTENANCE Information Report

When the maintenance date is not within 18 months of the current date, the check produces the report shown in the following figure. The description varies based on the startup parameters for the server. Each server type has the Common Components listed. The Abend-AID Viewer and BDCAS show Abend-AID. The Abend-AID Viewer and the TDCAS show Abend-AID for CICS.

Sample AA_SERVER_MAINTENANCE Exception Report

AA_HOOK_INSTALLED_STATUS

The AA_HOOK_INSTALLED_STATUS health check is a LOCAL health check that runs under the control of the IBM Health Checker for z/OS. Refer to the IBM Health Checker for z/OS User's Guide for more details.

HZSPRMxx Health Check PARMLIB Member Format/Fields

The Abend-AID LOCAL health check is controlled/activated using an HZSPRMxx PARMLIB member. Although your site could choose to use an existing member, We recommend that you instead create one specifically for the Abend-AID health check. The Abend-AID installation sample library hlq.CTL includes member HZSPRMAA for this health check, as shown in the following figure. We also recommend that you do not make changes to this member.

Sample Member HZSPRMAA

Abend-AID Hook Installed Health Check

To install this health check, do the following:

1. Ensure that the following Abend-AID load modules are in a link listed library. These modules reside in the SPAALOAD library:
   1. KAZJHC01       Hook installed health check
   2. KAZJHCM4      Hook installed health check messages
2. You may need to issue a MODIFY LLA,REFRESH command to get the new programs to run.
3. Copy the contents of sample PARMLIB member HZSPRMAA to SYS1.PARMLIB.

4. Once you have copied the load modules and PARMLIB member, the health check must be enabled. To immediately activate the health check, use the following command:

   MODIFY hzsproc,ADD,PARMLIB=AA
5. To make enabling of the health check occur after an IPL or a restart of the IBM Health Checker for z/OS address space, you can do one of the following, depending on how you start the IBM Health Checker for z/OS address space after an IPL:

• 
  

  • If you use the SYS1.PARMLIB member IEASYSxx to specify the health check procedure to start, modify the HZS parameter in IDASYSxx. For example:
        

    HZS=(00,AA)

  • If you use SYS1.PARMLIB member COMMNDxx to start the IBM Health Checker for z/OS address space, modify the procedure that is started to include a parameter containing AA. For example:

         HZSPARM=(00,AA)

Health Check Reports Output

Check Owner:

CPWR_ABEND_AID

Check Name:

AA_HOOK_INSTALLED_STATUS

Description:

The check verifies that an Abend-AID production hook has been installed and is active. For the module named ABENDAID, it shows the release level, date and time of assembly, and the CCID.

Interval

One time.

Messages:

This check issues the following messages:

• FDBHC0401I (information)
• FDBHC0402E (exception)
• FDBHC0403E (exception)

Output:

When the hook is available, the health check produces a report similar to the one shown below in the following figure.

Sample AA_HOOK_INSTALLED_STATUS Information Report

When the hook is not available, the health check produces a report similar to the one shown below in the following figure.

Sample AA_HOOK_INSTALLED_STATUS Exception Report

Other vendors offer functionality similar to Abend-AID. Your site may have one or more of those products installed on the same system where Abend-AID is installed. You may see one of the reports shown below in the following figure through Sample AA_SERVER_MAINTENANCE Exception Report figure if the health check detects problems with one of the other products.

Sample AA_HOOK_INSTALLED_STATUS Exception Report

Sample AA_HOOK_INSTALLED_STATUS Exception Report

Sample AA_SERVER_MAINTENANCE Exception Report

Changing the Health Check Interval

To change the health check interval from the default, use the MVS MODIFY Health Check UPDATE command: