TEC553532 - How can CA DB2 tools health ... - CA Communities

clutteredreverandData Management

Oct 31, 2013 (3 years and 7 months ago)

77 views

Document ID
:


TEC553532


CA Xmanager for DB2 for z/OS

Title:

How can CA

DB2
t
ools health check routin
es be prevented from executing.

Description:

The CA

DB2
t
ools health check routines are registered to IBM Health Checker for z/OS
during CA Execution Manager for DB2 for z/OS (PXM) startup. The intended
implementation of IBM Health Checker for z/OS is that by default, health check routin
es
should execute as part of the product "out of the Box" installation. CA

DB2 Health
Checks conform to this standard. CA

DB2 Tools health check routines, depending on
execution
i
nterval time, may run once or periodically for the duration of the Xmanager
s
tarted task.

Solution:

DELETE the CA

DB2 Tools health check routine(s).

Stopping a CA

DB2 health check from executing can be accomplished by using IBM
Health Checker for z/OS operator modify commands to temporarily delete the health
check(s), or long term
through the use of the IBM Health Checker for z/OS parmlib
member HZSPRMxx.

CA

DB2 Tools health check routines deleted using IBM Health Checker for z/OS
operator modify commands will remain deleted only for the duration of the Xmanager
task that owns the h
ealth checks.

When using a DELETE CHECK in the IBM Health Checker for z/OS parmlib member
HZSPRMxx, health check routines will be deleted with each execution of Xmanager. Be
sure to recycle the IBM Health Checker for z/OS address space to affect these chan
ges.

If the IBM Health Checker for z/OS address space is stopped, abnormally terminates or is
recycled, CA Health Checker retains the deleted state of health check routines for the
duration of the Xmanager task that added the health checks.

For additional
information on using IBM Health Checker for z/OS operator modify
commands or parmllib member HZSPRMxx see the IBM Health Checker for z/OS User's
Guide.

DELETE a health check using an operator modify command.

F hcheck,DELETE,CHECK=(HEALTH CHECK OWNER, HEALT
H CHECK NAME

Following are some examples of deleting CA

DB2 Health checks.

Delete a specific CA

DB2 health check:

F hcheck,DELETE,CHECK=(CA_DB2,DB2_PLC_PLC_DCOMP_ACT@PTXRUN14)

Delete all CA

DB2 health checks:

F hcheck,DELETE,CHECK=(CA_DB2,*)

Delete all CA

DB2 health checks with a health check name beginning with DB2_:

F hcheck,DELETE,CHECK=(CA_DB2,DB2_*)

DELETE a health check using SYS1.PARMLIB member HZSPRMxx.

Following is the format of an ADDREPLACE POLICY statement used to delete health
checks.

ADDREPLAC
E POLICY

DELETE CHECK(HEALTH CHECK OWNER, HEALTH CHECK NAME)

DATE(YYYYMMDD)

REASON('Do not run DB2 tools health checks.')

The following ADDREPLACE POLICY statement will cause all CA

DB2 heath checks
to be deleted:

ADDREPLACE POLICY

DELETE CHECK(
CA_DB2,*)

DATE(20110718)

REASON('Do not run DB2 tools health checks.')

The following ADDREPLACE POLICY statement will cause a specific CA

DB2 heath
check to be deleted:

ADDREPLACE POLICY

DELETE CHECK(CA_DB2,DB2_PLC_PLC_DCOMP_ACT@PTXRUN14)

DATE(20110718
)

REASON('Do not run DB2 tools health checks.')

The following ADDREPLACE POLICY statement will cause all CA

DB2 heath checks
to be deleted with a health check name beginning with DB2_:

ADDREPLACE POLICY

DELETE CHECK(CA_DB2,DB2_*)

DATE(20110718)

REASON(
'Do not run DB2 tools health checks.')

Health check(s) may remain active with ADDREPLACE POLICY DELETE statements
in HZSPRMxx.

When CA

DB2 health checks remain active it is recommended that the date specified on
the ADDREPLACE POLICY DELETE be set to the c
urrent date. The date specified on
the ADDREPLACE POLICY DELETE can become out of date due to subsequent
maintenance to CA

DB2 health check routines.